From Jessica.Crouch at lyrasis.org Mon Jan 3 11:21:29 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 3 Jan 2022 16:21:29 +0000 Subject: [Archivesspace_Users_Group] Join us for the next ArchivesSpace Trainers Corps Office Hour, Monday, January 24th at 2pm ET/11am PT Message-ID: <386A9ED0-6A68-4B07-9FB5-EA210B4CE90D@lyrasis.org> Dear ArchivesSpace Users, The fourth ArchivesSpace Trainers Corps ?Office Hour? will be Monday, January 24th at 2pm ET/11am PT. In these office hours, members of the ArchivesSpace Trainers Corps will demo a task or tool frequently used by ArchivesSpace users and take questions related to the demo and topic. For this open call, the Trainers Corps will briefly demo the new custom reports functionality available as of ArchivesSpace v3.2.0, which is scheduled for release in January 2022. Following the presentation, you will have the opportunity to ask questions about the topic, followed by a general Q&A about generating reports in ArchivesSpace. ArchivesSpace Trainers Corps ?Office Hour? Date: January 24, 2022 Time: 2:00pm ET / 11:00am PT Topic: Custom reports functionality new with ArchivesSpace v3.2.0 Registration: https://lyrasis.zoom.us/meeting/register/tZArdu2pqz0jHNUVwhux8HzqpRzAunZoVLLK Throughout the past 12 months, the Trainers Corps has been offering regularly scheduled trainings and office hours covering a variety of topics on all things ArchivesSpace. Registration for each training is separate and opens closer to each training date. Information about this training program is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2331148319/ArchivesSpace+Community-Wide+Virtual+Training. If you have any questions, feel free to contact us at ArchivesSpaceHome at lyrasis.org. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Mon Jan 3 14:19:39 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Mon, 3 Jan 2022 14:19:39 -0500 Subject: [Archivesspace_Users_Group] question about searching/browsing digital objects in the SUI In-Reply-To: References: <3b788c64-419d-6a3b-88e2-2bc09f42665e@bodleian.ox.ac.uk> Message-ID: Thanks so much for replying, Valerie! Alas, our repository doesn't have in-house capacity to run database queries or use the API for base-level processing tasks such as this. We rely upon the SUI for our everyday collections management and processing needs, and heartily encourage SUI development! The JIRA ticket you linked to does indeed address what I'm looking for. I will add my comments there. All best, Wendy ____________________________________ WENDY SCHEIR director THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212-229-5942 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives [image: THE NEW SCHOOL] On Tue, Dec 28, 2021 at 4:45 PM Valerie Addonizio wrote: > Hi Wendy, > > > > I?m afraid there is no way to do this in the SUI. There are ways through > queries against the database or the API, but no ready-made view or filter > in the SUI. I believe this existing JIRA ticket may include some of what > you?re looking for if you wish to add any comments to bolster the user > stories there: https://archivesspace.atlassian.net/browse/ANW-1102 > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Wendy > Scheir > *Sent:* Thursday, December 23, 2021 7:24 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] question about > searching/browsing digital objects in the SUI > > > > Thanks, Andrew. I was asking that, but only by way of trying to find a > solution to the issue I'm having, which is to come up with a results list > of digital objects that are related to a particular resources/accessions. > > > > Wendy > > > > On Thu, Dec 23, 2021, 5:58 AM Andrew Morrison < > andrew.morrison at bodleian.ox.ac.uk> wrote: > > There is no equivalent of the Manage Top Containers interface for digital > objects, if that is what you are asking. > > Andrew. > > > > On 22/12/2021 17:01, Wendy Scheir wrote: > > Hi, > > > > Can anyone tell me the way in the SUI to get a list of Digital Objects > related to a particular resource or accession? I figure there must be a way > similar to the way it works with Top Containers? I couldn't find this > answer in the Help Center. > > > > Many thanks, > > Wendy > > ____________________________________ > > *WENDY SCHEIR* > > director > THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS > > 66 FIFTH AVENUE, NEW YORK, NY 10011 > > scheirw at newschool.edu > > > *T* 212-229-5942 > > Explore the Archives | Digital > Collections from the Archives > | New School Histories > | @tnsarchives > > > [image: THE NEW SCHOOL] > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amanifold at slv.vic.gov.au Mon Jan 3 21:37:19 2022 From: amanifold at slv.vic.gov.au (Alan Manifold) Date: Tue, 4 Jan 2022 02:37:19 +0000 Subject: [Archivesspace_Users_Group] Harvard digital objects code with external Solr in AS 2.8.1 Message-ID: Hi folks, We thought it might be easier to separate the Solr split from the upgrade process so we are in the process of doing it on our current version (2.8.1). But we're having trouble with some of the code we cabbaged from the Harvard digital objects plugin not working with the new Solr. We assume there is some tweaking or Solr schema configuration that needs to be done in order to make that work. I expect that at least some other sites are already running both of these bits and know what tweaks might be necessary to get this all working. Can you help? Regards, Alan Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 T +61 3 8664 7122 | amanifold at slv.vic.gov.au slv.vic.gov.au [slv] [https://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?9] This message and any attachment is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please delete all copies of the message and its attachments and notify the sender immediately. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Jan 4 05:57:58 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 4 Jan 2022 10:57:58 +0000 Subject: [Archivesspace_Users_Group] Harvard digital objects code with external Solr in AS 2.8.1 In-Reply-To: References: Message-ID: You could try using the version of solrconfig.xml on the master branch of the ArchivesSpace repository... https://github.com/archivesspace/archivesspace/blob/master/solr/solrconfig.xml#L3-L7 ...or possibly just copy the lines I've highlighted into your current solrconfig.xml (changing the luceneMatchVersion to whatever version of Solr you are running.) Andrew. On 04/01/2022 02:37, Alan Manifold wrote: > Hi folks, > We thoughtit might be easier to separate the Solr split from the > upgrade process so we are in the process of doing it on our current > version (2.8.1). > > But we're having trouble with some of the code we cabbaged from the > Harvard digital objects plugin not working with the new Solr. We > assume there is some tweaking or Solr schema configuration that needs > to be done in order to make that work. I expect that at least some > other sites are already running both of these bits and know what > tweaks might be necessary to get this all working. Can you help? > > Regards, > Alan > > *Alan Manifold | Library Systems & Digital Preservation Manager | > Collection Development & Description * > State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 > T +61 3 8664 7122 | amanifold at slv.vic.gov.au > slv.vic.gov.au > > > slv > > > > This message and any attachment is intended only for the use of the > Addressee and may contain information that is PRIVILEGED and > CONFIDENTIAL. If you are not the intended recipient, you are hereby > notified that any dissemination of this communication is strictly > prohibited. If you have received this communication in error, please > delete all copies of the message and its attachments and notify the > sender immediately. Thank you. > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Jan 4 10:17:05 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 4 Jan 2022 15:17:05 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Using ArchivesSpace to create EAC-CPF records (90 minutes) Message-ID: <4C191CEB-2CEA-477D-8139-D630FE8F931B@lyrasis.org> Dear ArchivesSpace users, The next ArchivesSpace webinar will be a 90-minute learning opportunity on February 9th at 2:00p.m. ET/11:00a.m. PT led by Regine Heberlein, Library IT Data Analyst at Princeton University, and Christine Di Bella, ArchivesSpace Program Manager, demonstrating how to create valid EAC-CPF records using ArchivesSpace and offering some tips and tricks for making the process easier within your repository. Date: February 9, 2022 Time: 2:00p.m. ? 3:30p.m. ET (11:00a.m. ? 12:30pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_e777kyjtQ6qjBMWeiiTWmg This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: The recent expansion of the agents module in ArchivesSpace greatly expanded the application?s support for the metadata standard Encoded Archival Context ? Corporate Bodies, Persons, and Families (EAC-CPF) and the potential for exchanging these records with other systems, including Social Networks and Archival Context (SNAC). Taking full advantage of this potential requires some work on the record creator?s part as ArchivesSpace?s requirements for creating agent records remain minimal. This learning opportunity will demonstrate how to create valid EAC-CPF records using ArchivesSpace and offer some tips and tricks for making the process easier within your repository. An open discussion and Q&A will follow. This learning opportunity introduces EAC-CPF in the context of ArchivesSpace but is not intended to be a full overview of the standard. Resources for learning more about EAC-CPF include: * Encoded Archival Standards: A Primer: https://www.youtube.com/watch?v=WYWQeBRnhz0 * EAC-CPF Community and Support page: https://eac.staatsbibliothek-berlin.de/community-and-mailinglist/ * EAC-CPF Tag Library: https://eac.staatsbibliothek-berlin.de/schemata-and-tag-library/ NOTE: This learning opportunity assumes basic knowledge of ArchivesSpace, including an understanding of agent records. If you do not have this, we recommend watching the videos of the Basics workshop series, available on YouTube at https://www.youtube.com/playlist?list=PL3cxupmXL7WiHyMc0uFmsCEIVOQmrI7FL. We will not be able to answer general questions about ArchivesSpace or specific questions about individual ArchivesSpace implementations during this session. Who should attend: Anyone interested in using ArchivesSpace to create valid EAC-CPF records. Email ArchivesSpaceHome at lyrasis.org if you have any questions. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Tue Jan 4 10:53:55 2022 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Tue, 4 Jan 2022 15:53:55 +0000 Subject: [Archivesspace_Users_Group] Repeating error message Message-ID: All, We?ve been getting the below error message about once a week for the past few weeks, which has required a restart of the AS system, but we?ve been unable to track down what?s causing it. We?re on AS version 3.1.1. When the messages start showing up, we?re unable to load resources or accessions. We are also using an external Solr index that is located on a different server. Any ideas on where to start? ERROR -- : Thread-2956: uri:classloader:/jsonmodel_client.rb:490:in `all' /archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/main.rb:32:in `block in main' There are a lot of other messages in about ruby gems and the indexer like so: archivesspace.gems.gems.sinatra_minus_2_dot_0_dot_5.lib.sinatra.base.RUBY$method$call$0(/archivesspace/gems/gems/sinatra-2.0.5/lib/sinatra/base.rb:194) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.main.invokeOther31:call(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:320) There?s a lot going on in the messages, so any insight from someone that has seen this type of error message before would be helpful. Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Tue Jan 4 10:57:43 2022 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 4 Jan 2022 15:57:43 +0000 Subject: [Archivesspace_Users_Group] Repeating error message In-Reply-To: References: Message-ID: Can you share way more of the area around those errors? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Tuesday, January 4, 2022 10:53 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Repeating error message All, We?ve been getting the below error message about once a week for the past few weeks, which has required a restart of the AS system, but we?ve been unable to track down what?s causing it. We?re on AS version 3.1.1. When the messages start showing up, we?re unable to load resources or accessions. We are also using an external Solr index that is located on a different server. Any ideas on where to start? ERROR -- : Thread-2956: uri:classloader:/jsonmodel_client.rb:490:in `all' /archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/main.rb:32:in `block in main' There are a lot of other messages in about ruby gems and the indexer like so: archivesspace.gems.gems.sinatra_minus_2_dot_0_dot_5.lib.sinatra.base.RUBY$method$call$0(/archivesspace/gems/gems/sinatra-2.0.5/lib/sinatra/base.rb:194) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.main.invokeOther31:call(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:320) There?s a lot going on in the messages, so any insight from someone that has seen this type of error message before would be helpful. Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbreneman at ubalt.edu Wed Jan 5 12:28:53 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Wed, 5 Jan 2022 17:28:53 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? Message-ID: Our archives staff have noticed that AS tends to get hung up when users click the Print button on some of our largest collections. Campus IT tested this today. The server did not hang for them, but the print action also did not complete. They got a very, very generic error message (attached). I have access to the ArchivesSpace files on the server, including the /logs directory, but I'm not sure how to parse the logs for clues. Does anyone have advice for how I can sift through the logs? Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CISARCSPC_Print_Error.png Type: image/png Size: 12884 bytes Desc: CISARCSPC_Print_Error.png URL: From blake.carver at lyrasis.org Wed Jan 5 12:31:07 2022 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 5 Jan 2022 17:31:07 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: References: Message-ID: grep the logs for ERROR or FATAL ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kyle Breneman Sent: Wednesday, January 5, 2022 12:28 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? Our archives staff have noticed that AS tends to get hung up when users click the Print button on some of our largest collections. Campus IT tested this today. The server did not hang for them, but the print action also did not complete. They got a very, very generic error message (attached). I have access to the ArchivesSpace files on the server, including the /logs directory, but I?m not sure how to parse the logs for clues. Does anyone have advice for how I can sift through the logs? Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbreneman at ubalt.edu Wed Jan 5 12:36:41 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Wed, 5 Jan 2022 17:36:41 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: References: Message-ID: Thank you for that reminder, Blake! Another question: the print action was being run from the following pages. Wouldn't clicking the AS print button itself register in the logs? If so, how could I efficiently find those lines? https://archivesspace.ubalt.edu/repositories/2/resources/92 https://archivesspace.ubalt.edu/repositories/2/resources/126 https://archivesspace.ubalt.edu/repositories/2/resources/21 Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Wednesday, January 5, 2022 12:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover over any links before clicking and use caution when opening attachments.] grep the logs for ERROR or FATAL ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Kyle Breneman > Sent: Wednesday, January 5, 2022 12:28 PM To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? Our archives staff have noticed that AS tends to get hung up when users click the Print button on some of our largest collections. Campus IT tested this today. The server did not hang for them, but the print action also did not complete. They got a very, very generic error message (attached). I have access to the ArchivesSpace files on the server, including the /logs directory, but I?m not sure how to parse the logs for clues. Does anyone have advice for how I can sift through the logs? Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? -------------- next part -------------- An HTML attachment was scrubbed... URL: From lross at uvm.edu Wed Jan 5 13:49:49 2022 From: lross at uvm.edu (Lyman Ross) Date: Wed, 5 Jan 2022 18:49:49 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: References: Message-ID: <499f28cf080e46fbac30b767c4ce32a6@uvm.edu> We had a similar problem a month ago which was caused by mixed protocols (http/https). We resolved it by forcing all traffic to use https. -Lyman From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kyle Breneman Sent: Wednesday, January 05, 2022 12:29 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? Our archives staff have noticed that AS tends to get hung up when users click the Print button on some of our largest collections. Campus IT tested this today. The server did not hang for them, but the print action also did not complete. They got a very, very generic error message (attached). I have access to the ArchivesSpace files on the server, including the /logs directory, but I'm not sure how to parse the logs for clues. Does anyone have advice for how I can sift through the logs? Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Jan 5 14:18:18 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 5 Jan 2022 19:18:18 +0000 Subject: [Archivesspace_Users_Group] position announcement: ArchivesSpace Developer Message-ID: Hello ArchivesSpace members, The ArchivesSpace Developer position is now posted on the LYRASIS website: https://lyrasis.isolvedhire.com/jobs/493314-25777.html. This is a full-time, permanent remote position. As you would imagine, we're eager to return our development team to full strength. Please forward the position to anyone you think might be interested, and feel free to reach out to Brian Hoffman or me if you have questions, ideas for candidates, or if you're interested yourself. All applications should be submitted via the LYRASIS website. Thanks for your help, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From andrew.morrison at bodleian.ox.ac.uk Thu Jan 6 05:14:24 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 6 Jan 2022 10:14:24 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: References: Message-ID: <2d2c0124-b5f7-3f54-b7c0-05e98c44d4db@bodleian.ox.ac.uk> If you do see that "Failed to clean XML" message in the logs, then you might be interested in this pull request I submitted recently: https://github.com/archivesspace/archivesspace/pull/2553 I could put the same fix into the form of a plug-in, if that is what you are seeing, you have the ability to install plug-ins, and you are running 2.7.1 or newer. It might be a different markup issue, but in my experience the logs never tell you which archival object the problem is in. It cannot, because by that point it has converted the collection into a temporary HTML file, which is the intermediate step before converting to PDF. You could try exporting as EAD from the staff interface, then validating in an XML editor, but if the issue is something which is valid in EAD, then it can be very difficult to trace. If you have a local development instance of ArchivesSpace, you can modify the code so it doesn't delete the temporary HTML files, then validate those. Andrew. On 05/01/2022 18:14, Blake Carver wrote: > It's going to be a bit of looking for a bunch of needles in a very > short hay stack kinda thing. > The errors should have either FATAL or ERROR and something about pdf > around there somewhere. Sometimes there will be allotta other FATAL > and ERROR around, so you'll need to narrow it down based on what each > one says. > You could also look for "92" "126" and "21" I think the resource > number should show up around the error as well. > Also wouldn't surprise me to see this error in particular, but not always: > > |RuntimeError (Failed to clean XML: The entity name must immediately > follow the '&' in the entity reference.):| > > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Kyle Breneman > *Sent:* Wednesday, January 5, 2022 12:36 PM > *To:* Archivesspace Users Group > > *Subject:* Re: [Archivesspace_Users_Group] Advice on what to look for > in AS logs after printing error? > > Thank you for that reminder, Blake!? Another question: the print > action was being run from the following pages.? Wouldn?t clicking the > AS print button itself register in the logs? If so, how could I > efficiently find those lines? > > https://archivesspace.ubalt.edu/repositories/2/resources/92 > > > https://archivesspace.ubalt.edu/repositories/2/resources/126 > > > https://archivesspace.ubalt.edu/repositories/2/resources/21 > > > *Kyle Breneman* > > Integrated Digital Services Librarian > > The University of Baltimore > > kbreneman at ubalt.edu > > /I believe in freedom of thought and / > > /freedom of speech. Do you?/ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > *On Behalf > Of *Blake Carver > *Sent:* Wednesday, January 5, 2022 12:31 PM > *To:* Archivesspace Users Group > > *Subject:* Re: [Archivesspace_Users_Group] Advice on what to look for > in AS logs after printing error? > > *[**EXTERNAL EMAIL: This message originated from a non-UBalt email > system. Hover over any links before clicking and use caution when > opening attachments.**]* > > grep the logs for? ERROR or FATAL > > ------------------------------------------------------------------------ > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >

> on > behalf of Kyle Breneman > > *Sent:* Wednesday, January 5, 2022 12:28 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > > > *Subject:* [Archivesspace_Users_Group] Advice on what to look for in > AS logs after printing error? > > Our archives staff have noticed that AS tends to get hung up when > users click the Print button on some of our largest collections.? > Campus IT tested this today.? The server did not hang for them, but > the print action also /did not complete/. They got a very, very > generic error message (attached). > > I have access to the ArchivesSpace files on the server, including the > /logs directory, but I?m not sure how to parse the logs for clues. > Does anyone have advice for how I can sift through the logs? > > *Kyle Breneman* > > Integrated Digital Services Librarian > > The University of Baltimore > > kbreneman at ubalt.edu > > /I believe in freedom of thought and / > > /freedom of speech. Do you?/ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Thu Jan 6 06:29:54 2022 From: ph448 at cam.ac.uk (Peter Heiner) Date: Thu, 6 Jan 2022 11:29:54 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: References: Message-ID: <20220106112953.oflrnrnunv53s6gh@sparkly> Kyle Breneman wrote on 2022-01-05 17:36:41: > Thank you for that reminder, Blake! Another question: the print action was > being run from the following pages. Wouldn't clicking the AS print button > itself register in the logs? If so, how could I efficiently find those > lines? > > https://archivesspace.ubalt.edu/repositories/2/resources/92 > > https://archivesspace.ubalt.edu/repositories/2/resources/126 > > https://archivesspace.ubalt.edu/repositories/2/resources/21 For the click you should see a POST request to the URI + '/pdf'. If you have a webserver in front of ArchivesSpace you may be dealing with the backend request timing out on trying to print large collections, which will show up in the webserver logs as HTTP error 504. p From kbreneman at ubalt.edu Thu Jan 6 09:28:01 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Thu, 6 Jan 2022 14:28:01 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: <2d2c0124-b5f7-3f54-b7c0-05e98c44d4db@bodleian.ox.ac.uk> References: <2d2c0124-b5f7-3f54-b7c0-05e98c44d4db@bodleian.ox.ac.uk> Message-ID: Andrew, thank you for taking the time to point me to your Github fix. I do see the "Failed to clean XML" error in my logs, but in each case it is seemingly upset about missing semicolons: "Failed to clean XML: The reference to entity "W" must end with the ';' delimiter." If I understand your Github repo code, it is narrowly targeted at dealing with situations where & is immediately followed by a digit, and so would not help in my situation. Have I got that right? Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: Thursday, January 6, 2022 5:14 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover over any links before clicking and use caution when opening attachments.] If you do see that "Failed to clean XML" message in the logs, then you might be interested in this pull request I submitted recently: https://github.com/archivesspace/archivesspace/pull/2553 I could put the same fix into the form of a plug-in, if that is what you are seeing, you have the ability to install plug-ins, and you are running 2.7.1 or newer. It might be a different markup issue, but in my experience the logs never tell you which archival object the problem is in. It cannot, because by that point it has converted the collection into a temporary HTML file, which is the intermediate step before converting to PDF. You could try exporting as EAD from the staff interface, then validating in an XML editor, but if the issue is something which is valid in EAD, then it can be very difficult to trace. If you have a local development instance of ArchivesSpace, you can modify the code so it doesn't delete the temporary HTML files, then validate those. Andrew. On 05/01/2022 18:14, Blake Carver wrote: It's going to be a bit of looking for a bunch of needles in a very short hay stack kinda thing. The errors should have either FATAL or ERROR and something about pdf around there somewhere. Sometimes there will be allotta other FATAL and ERROR around, so you'll need to narrow it down based on what each one says. You could also look for "92" "126" and "21" I think the resource number should show up around the error as well. Also wouldn't surprise me to see this error in particular, but not always: RuntimeError (Failed to clean XML: The entity name must immediately follow the '&' in the entity reference.): ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

on behalf of Kyle Breneman Sent: Wednesday, January 5, 2022 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? Thank you for that reminder, Blake! Another question: the print action was being run from the following pages. Wouldn't clicking the AS print button itself register in the logs? If so, how could I efficiently find those lines? https://archivesspace.ubalt.edu/repositories/2/resources/92 https://archivesspace.ubalt.edu/repositories/2/resources/126 https://archivesspace.ubalt.edu/repositories/2/resources/21 Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-bounces at lyralists.lyrasis.org

On Behalf Of Blake Carver Sent: Wednesday, January 5, 2022 12:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover over any links before clicking and use caution when opening attachments.] grep the logs for ERROR or FATAL ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

on behalf of Kyle Breneman Sent: Wednesday, January 5, 2022 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? Thank you for that reminder, Blake! Another question: the print action was being run from the following pages. Wouldn?t clicking the AS print button itself register in the logs? If so, how could I efficiently find those lines? https://archivesspace.ubalt.edu/repositories/2/resources/92 https://archivesspace.ubalt.edu/repositories/2/resources/126 https://archivesspace.ubalt.edu/repositories/2/resources/21 Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-bounces at lyralists.lyrasis.org

<735a27de-1188-d138-a0dc-acba8f5d7c7c@bodleian.ox.ac.uk> Message-ID: I have a dumb question: Where do I find the ?Archivesspace solr configuration files?? I can find the ?solr directory? mentioned in the instruction anywhere in our installed ArchivesSpace instance. Bin From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Trevor Thornton Sent: Monday, December 6, 2021 5:53 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Implementing a standalone Solr instance Instructions for running AS with an external Solr instance are here: https://archivesspace.github.io/tech-docs/provisioning/solr.html On Mon, Dec 6, 2021 at 4:54 AM Andrew Morrison > wrote: Presumably there will be documentation. In the meantime, there is a webinar recording you can watch: https://archivesspace.org/archives/7151 Andrew. On 06/12/2021 00:05, Alan Manifold wrote: Related to this, are there instructions out there for implementing ArchivesSpace with external SOLR? I'm sure they'll be coming, but I didn't find any the last time I looked. We're also thinking about moving to this prior to it being required. Regards, Alan Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 T +61 3 8664 7122 | amanifold at slv.vic.gov.au slv.vic.gov.au [slv] [https://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?9] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

on behalf of Jared Hutchens Sent: Saturday, 4 December 2021 4:33 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Implementing a standalone Solr instance Hi Kyle, Here at Anderson University we've been running our external Solr instance on the same server as ArchivesSpace for over a month now with no issues. That being said, the server receives minimal traffic so I can't attest to any volume related performance impacts but appears to be similar to running the embedded Solr (or in our case, potentially running even better than before). If any of the larger users have looked into this I'd be interested in seeing what you've found. [https://lh4.googleusercontent.com/2cqdpPanpPHRmQo0drMK5LKoNeS631xRPI1vOTtHcbn8d9ESe8UB7kSF2L-gp9vSpOrGADAfgyrcbVyGk_9S1X8uiCr3IEpvio7nu-2N-OtSYGMWWsZd-h1S5d-Sv3-j3KXXFWWb] Jared Hutchens | Library Technology Specialist | Nicholson Library Anderson University | 1100 E. 5th St., Anderson, IN 46012 (765) 641-4270 | jmhutchens at anderson.edu | anderson.edu On Fri, Dec 3, 2021 at 11:50 AM Kyle Breneman > wrote: Here at the University of Baltimore, we are working to stand up our own external Solr installation in preparation for ArchivesSpace?s move away from bundled Solr. Campus IT is asking me whether or not we should install Solr on the same server we?re using to host ArchviesSpace. I see that ArchivesSpace officially has no opinion on this matter (See under ?Will you have strict requirements for how to deploy Solr??). Does anyone on this list have a recommendation about whether an external instance of Solr should be installed on the same server as ArchivesSpace, or on its own separate server? I don?t see that it makes much difference, but I am also not experienced in managing servers, or in administering Solr. Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group This message and any attachment is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please delete all copies of the message and its attachments and notify the sender immediately. Thank you. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Fri Jan 7 04:33:24 2022 From: ph448 at cam.ac.uk (Peter Heiner) Date: Fri, 7 Jan 2022 09:33:24 +0000 Subject: [Archivesspace_Users_Group] Implementing a standalone Solr instance In-Reply-To: References:

<735a27de-1188-d138-a0dc-acba8f5d7c7c@bodleian.ox.ac.uk> Message-ID: <20220107093324.sumueil4l3mzgsjb@sparkly> Zhang, Bin wrote on 2022-01-07 05:14:57: > Where do I find the ?Archivesspace solr configuration files?? I can find > the ?solr directory? mentioned in the instruction anywhere in our installed > ArchivesSpace instance. It's not in the distribution, but in the source tree on Github: https://github.com/archivesspace/archivesspace/tree/master/solr p From andrew.morrison at bodleian.ox.ac.uk Fri Jan 7 05:18:50 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Fri, 7 Jan 2022 10:18:50 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: References: <2d2c0124-b5f7-3f54-b7c0-05e98c44d4db@bodleian.ox.ac.uk> Message-ID: <94bb6e49-d098-8bbd-860b-25db94929e2c@bodleian.ox.ac.uk> My fix should prevent all "Failed to clean XML: The reference to entity..." errors triggered by EAD-compliant encoding. But, depending on what version of ArchivesSpace you are running, it may only make a difference in niche cases. As I understand it (although Blake may wish to correct me if I am wrong) the timeline is this: Up to 2.7.0, PDFs generated by the PUI did not fail in this precise way, at least not if your records used EAD-compliant encoding of characters such as ampersands, greater-than, less-than, etc. In 2.7.1, a change was made to allow people to include a HTML entity reference, specifically the one for non-breaking spaces ( ) in their records. That is not strictly EAD-compliant encoding, but some people use them for formatting purposes, or because their records are converted from old web pages. But that broke generation of PDFs for records containing EAD-compliant encoding of ampersands which happened to be immediately followed by an uppercase letter (e.g. "B&W"). In 2.8.1, the case of ampersands immediately followed by an uppercase letter was fixed, but PDFs will still fail if a record contains an ampersand immediately followed by a character which isn't an ASCII upper or lowercase alphabetic character or space. The specific case I've encountered is numbers in citations of printed resources (e.g. "Vols. 1&2") but it could also happen with UTF-8 characters outside the ASCII range. Now, my proposed fix would, I believe, prevent PDFs from breaking whatever immediately follows an ampersand. Also potentially other problems such as records containing < in certain contexts. Admittedly these are rare, but if you've got enough records they will occur somewhere, and they are fiendishly difficult to track down. So, if you are running 2.7.1 or 2.8.0, and you are sure that your records only contain things like "B&W", and never things like "Vols. 1&2", then upgrading to 2.8.1 or higher would probably fix your problem. If you're already running 2.8.1 or higher, my fix is currently untested by anyone but me, but if you want to give it a try, let me know. Andrew. On 06/01/2022 14:28, Kyle Breneman wrote: > > Andrew, thank you for taking the time to point me to your Github fix.? > I /do/ see the ?Failed to clean XML? error in my logs, but in each > case it is seemingly upset about missing semicolons: ?Failed to clean > XML: The reference to entity "W" must end with the ';' delimiter.? > > If I understand your Github repo code, it is narrowly targeted at > dealing with situations where & is immediately followed by a digit, > and so would not help in my situation. Have I got that right? > > *Kyle Breneman* > > Integrated Digital Services Librarian > > The University of Baltimore > > kbreneman at ubalt.edu > > /I believe in freedom of thought and / > > /freedom of speech. Do you?/ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > *On Behalf > Of *Andrew Morrison > *Sent:* Thursday, January 6, 2022 5:14 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* Re: [Archivesspace_Users_Group] Advice on what to look for > in AS logs after printing error? > > *[**EXTERNAL EMAIL: This message originated from a non-UBalt email > system. Hover over any links before clicking and use caution when > opening attachments.**]* > > If you do see that "Failed to clean XML" message in the logs, then you > might be interested in this pull request I submitted recently: > > https://github.com/archivesspace/archivesspace/pull/2553 > > > I could put the same fix into the form of a plug-in, if that is what > you are seeing, you have the ability to install plug-ins, and you are > running 2.7.1 or newer. > > It might be a different markup issue, but in my experience the logs > never tell you which archival object the problem is in. It cannot, > because by that point it has converted the collection into a temporary > HTML file, which is the intermediate step before converting to PDF. > You could try exporting as EAD from the staff interface, then > validating in an XML editor, but if the issue is something which is > valid in EAD, then it can be very difficult to trace. If you have a > local development instance of ArchivesSpace, you can modify the code > so it doesn't delete the temporary HTML files, then validate those. > > Andrew. > > On 05/01/2022 18:14, Blake Carver wrote: > > It's going to be a bit of looking for a bunch of needles in a very > short hay stack kinda thing. > > The errors should have either FATAL or ERROR and something about > pdf around there somewhere. Sometimes there will be allotta other > FATAL and ERROR around, so you'll need to narrow it down based on > what each one says. > > You could also look for "92" "126" and "21" I think the resource > number should show up around the error as well. > > Also wouldn't surprise me to see this error in particular, but not > always: > > |RuntimeError (Failed to clean XML: The entity name must > immediately follow the '&' in the entity reference.):| > > ------------------------------------------------------------------------ > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > > > > on behalf of Kyle Breneman > > *Sent:* Wednesday, January 5, 2022 12:36 PM > *To:* Archivesspace Users Group > > > *Subject:* Re: [Archivesspace_Users_Group] Advice on what to look > for in AS logs after printing error? > > Thank you for that reminder, Blake!? Another question: the print > action was being run from the following pages.? Wouldn?t clicking > the AS print button itself register in the logs?? If so, how could > I efficiently find those lines? > > https://archivesspace.ubalt.edu/repositories/2/resources/92 > > > https://archivesspace.ubalt.edu/repositories/2/resources/126 > > > https://archivesspace.ubalt.edu/repositories/2/resources/21 > > > *Kyle Breneman* > > Integrated Digital Services Librarian > > The University of Baltimore > > kbreneman at ubalt.edu > > /I believe in freedom of thought and / > > /freedom of speech. Do you?/ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > > > > *On Behalf Of * Blake Carver > *Sent:* Wednesday, January 5, 2022 12:31 PM > *To:* Archivesspace Users Group > > > *Subject:* Re: [Archivesspace_Users_Group] Advice on what to look > for in AS logs after printing error? > > *[EXTERNAL EMAIL: This message originated from a non-UBalt email > system. Hover over any links before clicking and use caution when > opening attachments.]* > > grep the logs for? ERROR or FATAL > > ------------------------------------------------------------------------ > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >

> > on behalf of Kyle Breneman > > *Sent:* Wednesday, January 5, 2022 12:28 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > > > *Subject:* [Archivesspace_Users_Group] Advice on what to look for > in AS logs after printing error? > > Our archives staff have noticed that AS tends to get hung up when > users click the Print button on some of our largest collections.? > Campus IT tested this today.? The server did not hang for them, > but the print action also /did not complete/.? They got a very, > very generic error message (attached). > > I have access to the ArchivesSpace files on the server, including > the /logs directory, but I?m not sure how to parse the logs for > clues. Does anyone have advice for how I can sift through the logs? > > *Kyle Breneman* > > Integrated Digital Services Librarian > > The University of Baltimore > > kbreneman at ubalt.edu > > /I believe in freedom of thought and / > > /freedom of speech. Do you?/ > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbreneman at ubalt.edu Fri Jan 7 09:19:05 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Fri, 7 Jan 2022 14:19:05 +0000 Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? In-Reply-To: <94bb6e49-d098-8bbd-860b-25db94929e2c@bodleian.ox.ac.uk> References: <2d2c0124-b5f7-3f54-b7c0-05e98c44d4db@bodleian.ox.ac.uk> <94bb6e49-d098-8bbd-860b-25db94929e2c@bodleian.ox.ac.uk> Message-ID: Thanks for providing detailed context about how specific versions of AS have handled XML, Andrew. We are currently running 2.8.1. Yes, I would like to try your fix.* I would like to install it on our development instance and see what happens. When you have a moment, please let me know how I would go about implementing your code. *I don't know anything about EAD encoding, so remain uncertain whether or not these apparently missing semicolons count as EAD-compliant. Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: Friday, January 7, 2022 5:19 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover over any links before clicking and use caution when opening attachments.] My fix should prevent all "Failed to clean XML: The reference to entity..." errors triggered by EAD-compliant encoding. But, depending on what version of ArchivesSpace you are running, it may only make a difference in niche cases. As I understand it (although Blake may wish to correct me if I am wrong) the timeline is this: Up to 2.7.0, PDFs generated by the PUI did not fail in this precise way, at least not if your records used EAD-compliant encoding of characters such as ampersands, greater-than, less-than, etc. In 2.7.1, a change was made to allow people to include a HTML entity reference, specifically the one for non-breaking spaces ( ) in their records. That is not strictly EAD-compliant encoding, but some people use them for formatting purposes, or because their records are converted from old web pages. But that broke generation of PDFs for records containing EAD-compliant encoding of ampersands which happened to be immediately followed by an uppercase letter (e.g. "B&W"). In 2.8.1, the case of ampersands immediately followed by an uppercase letter was fixed, but PDFs will still fail if a record contains an ampersand immediately followed by a character which isn't an ASCII upper or lowercase alphabetic character or space. The specific case I've encountered is numbers in citations of printed resources (e.g. "Vols. 1&2") but it could also happen with UTF-8 characters outside the ASCII range. Now, my proposed fix would, I believe, prevent PDFs from breaking whatever immediately follows an ampersand. Also potentially other problems such as records containing < in certain contexts. Admittedly these are rare, but if you've got enough records they will occur somewhere, and they are fiendishly difficult to track down. So, if you are running 2.7.1 or 2.8.0, and you are sure that your records only contain things like "B&W", and never things like "Vols. 1&2", then upgrading to 2.8.1 or higher would probably fix your problem. If you're already running 2.8.1 or higher, my fix is currently untested by anyone but me, but if you want to give it a try, let me know. Andrew. On 06/01/2022 14:28, Kyle Breneman wrote: Andrew, thank you for taking the time to point me to your Github fix. I do see the "Failed to clean XML" error in my logs, but in each case it is seemingly upset about missing semicolons: "Failed to clean XML: The reference to entity "W" must end with the ';' delimiter." If I understand your Github repo code, it is narrowly targeted at dealing with situations where & is immediately followed by a digit, and so would not help in my situation. Have I got that right? Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-bounces at lyralists.lyrasis.org

On Behalf Of Andrew Morrison Sent: Thursday, January 6, 2022 5:14 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover over any links before clicking and use caution when opening attachments.] If you do see that "Failed to clean XML" message in the logs, then you might be interested in this pull request I submitted recently: https://github.com/archivesspace/archivesspace/pull/2553 I could put the same fix into the form of a plug-in, if that is what you are seeing, you have the ability to install plug-ins, and you are running 2.7.1 or newer. It might be a different markup issue, but in my experience the logs never tell you which archival object the problem is in. It cannot, because by that point it has converted the collection into a temporary HTML file, which is the intermediate step before converting to PDF. You could try exporting as EAD from the staff interface, then validating in an XML editor, but if the issue is something which is valid in EAD, then it can be very difficult to trace. If you have a local development instance of ArchivesSpace, you can modify the code so it doesn't delete the temporary HTML files, then validate those. Andrew. On 05/01/2022 18:14, Blake Carver wrote: It's going to be a bit of looking for a bunch of needles in a very short hay stack kinda thing. The errors should have either FATAL or ERROR and something about pdf around there somewhere. Sometimes there will be allotta other FATAL and ERROR around, so you'll need to narrow it down based on what each one says. You could also look for "92" "126" and "21" I think the resource number should show up around the error as well. Also wouldn't surprise me to see this error in particular, but not always: RuntimeError (Failed to clean XML: The entity name must immediately follow the '&' in the entity reference.): ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

<735a27de-1188-d138-a0dc-acba8f5d7c7c@bodleian.ox.ac.uk> <20220107093324.sumueil4l3mzgsjb@sparkly> Message-ID: Thanks Peter! Sent from my T-Mobile 5G Device Get Outlook for Android ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Peter Heiner Sent: Friday, January 7, 2022 1:33:24 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Implementing a standalone Solr instance Zhang, Bin wrote on 2022-01-07 05:14:57: > Where do I find the ?Archivesspace solr configuration files?? I can find > the ?solr directory? mentioned in the instruction anywhere in our installed > ArchivesSpace instance. It's not in the distribution, but in the source tree on Github: https://github.com/archivesspace/archivesspace/tree/master/solr p _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corinne.Chatnik at nysed.gov Mon Jan 10 13:14:58 2022 From: Corinne.Chatnik at nysed.gov (Corinne Chatnik) Date: Mon, 10 Jan 2022 18:14:58 +0000 Subject: [Archivesspace_Users_Group] Bioghist Note export with Agent EAC-CPF file Message-ID: Hi, Are the notes in an Agent records (specifically corporate agents) supposed to export with the EAC-CPF download? They don't in my Archivesspace instance. If they are is there a setting I can look at? I've checked that they are marked publish and the published notes also don't appear in the Public interface with the agent record. Thanks! Corinne Chatnik New York State Archives Digital Strategies Corinne.Chatnik at nysed.gov Confidentiality Notice This email including all attachments is confidential and intended solely for the use of the individual or entity to which it is addressed. This communication may contain information that is protected from disclosure under State and/or Federal law. Please notify the sender immediately if you have received this communication in error and delete this email from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: From julie_wetherill at harvard.edu Mon Jan 10 17:11:41 2022 From: julie_wetherill at harvard.edu (Wetherill, Julie M.) Date: Mon, 10 Jan 2022 22:11:41 +0000 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value Message-ID: Hi everyone, In August 2021, a list message from Benn Joseph at Northwestern UL described their trouble getting incorrect Publish values when importing digital objects via spreadsheet. Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It seems like the ASpace code that interprets the incoming spreadsheet data is being extra picky about the Type value of the "publish" (Publish Digital Object Record) attribute that is supplied in the spreadsheet. If the archivist uses the TRUE/FALSE controlled values provided in the official template on github (bulk_import_DO_template.xlsx), digital objects load with the correct "publish" values and their PUI display looks good. When I run the TYPE function on these values, I get type 4 (logical value). But sometimes, an archivist will paste in TRUE/FALSE values copied from another file (especially true in high volume automated workflows). At a glance these TRUE/FALSE values look identical but they aren't. I noticed that these values are left aligned in the cell, rather than centered as Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE function on a cell with these values I get type 2 (text). Seems like ASpace wants only the logical TRUE/FALSE. An imported digital object that has the text value TRUE for "publish" will be set to the default FALSE (unpublished). When this happens in high volume it's a mess to clean up. And despite being marked Published=FALSE in staff mode, in the PUI, these digital objects are partially displaying. By that I mean, there is no digital link but the DO's are labeled DIGITAL and display in the PUI list of digital objects. I guess the work-around is user education (warn users to only supply logical TRUE/FALSE). But I'd prefer we tweaked ASpace code to accept either the logical or text value of TRUE/FALSE as I suspect used to be the case when spreadsheet import was plugin-based. Regards. -julie Julie Wetherill HUIT Library Technology Services Harvard University -------------- next part -------------- An HTML attachment was scrubbed... URL: From kjackson at hallieqbrown.org Mon Jan 10 17:28:32 2022 From: kjackson at hallieqbrown.org (Kayla Jackson) Date: Mon, 10 Jan 2022 22:28:32 +0000 Subject: [Archivesspace_Users_Group] An Exhibit Management Note Field Message-ID: Hello everyone! I would like to know if anyone has succeeded in implementing a notes field on objects/items relating to exhibit management (similar to the conditions for access/use notes). I think it would be helpful if there was such a note that would include the following: * Currently on display? Y/N * Date installed (for public viewing) * Date to be deinstalled/taken down The option to make these available for public viewing would also be great, as I think the local community I serve would appreciate knowing if they can plan to make a trip here or not. Additionally, as a lone-arranger whose duties extend beyond that of one job?s description, it would be awesome if I could centralize future exhibition management of certain objects with my typical archival processing. Any help or advice would be welcome! Sincerely, Kayla Kayla Jackson She/Her/Hers Archivist | Check out our Community Archives Hallie Q. Brown Community Center Administrator of the Martin Luther King Center 270 N. Kent Street kjackson at hallieqbrown.org 651-224-4605 ext. 126 -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Mon Jan 10 17:39:04 2022 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Mon, 10 Jan 2022 22:39:04 +0000 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References: Message-ID: Hi all, Thanks Julie for pointing this out-we eventually figured this out too, although by the time we did I'd forgotten to reply back to the list. One way to visually distinguish between logical and text value for this field is to see whether 'TRUE/FALSE' is centered in the cell (logical) or left-justified (text). The reason we were running into this issue is because we'd typically ensure that all cells in the import spreadsheet were formatted to 'Text', which I think had been part of the original user instructions back when this was a plugin. Once these fields are set to 'Text', the drop-down to select TRUE/FALSE will still function, but the word (TRUE or FALSE) will be left-justified, and will no longer be correctly interpreted (no longer logical), which I believe then defaults to FALSE. Best, --Benn Benn Joseph (he/him/his) Head, Collections Services McCormick Library of Special Collections & University Archives Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Wetherill, Julie M. Sent: Monday, January 10, 2022 4:12 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value Hi everyone, In August 2021, a list message from Benn Joseph at Northwestern UL described their trouble getting incorrect Publish values when importing digital objects via spreadsheet. Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It seems like the ASpace code that interprets the incoming spreadsheet data is being extra picky about the Type value of the "publish" (Publish Digital Object Record) attribute that is supplied in the spreadsheet. If the archivist uses the TRUE/FALSE controlled values provided in the official template on github (bulk_import_DO_template.xlsx), digital objects load with the correct "publish" values and their PUI display looks good. When I run the TYPE function on these values, I get type 4 (logical value). But sometimes, an archivist will paste in TRUE/FALSE values copied from another file (especially true in high volume automated workflows). At a glance these TRUE/FALSE values look identical but they aren't. I noticed that these values are left aligned in the cell, rather than centered as Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE function on a cell with these values I get type 2 (text). Seems like ASpace wants only the logical TRUE/FALSE. An imported digital object that has the text value TRUE for "publish" will be set to the default FALSE (unpublished). When this happens in high volume it's a mess to clean up. And despite being marked Published=FALSE in staff mode, in the PUI, these digital objects are partially displaying. By that I mean, there is no digital link but the DO's are labeled DIGITAL and display in the PUI list of digital objects. I guess the work-around is user education (warn users to only supply logical TRUE/FALSE). But I'd prefer we tweaked ASpace code to accept either the logical or text value of TRUE/FALSE as I suspect used to be the case when spreadsheet import was plugin-based. Regards. -julie Julie Wetherill HUIT Library Technology Services Harvard University -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Mon Jan 10 19:15:18 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Mon, 10 Jan 2022 19:15:18 -0500 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References: Message-ID: I think a related or adjacent issue to this is that there are 2 separate *Publish?* fields for each Digital Object record, but the import spreadsheet has the option to select TRUE/FALSE for only 1 of them. The way we're using DOs, sometimes (often, actually) we want one=TRUE and the other=FALSE within a single record. Wendy The New Archives and Special Collections On Mon, Jan 10, 2022, 5:11 PM Wetherill, Julie M. < julie_wetherill at harvard.edu> wrote: > Hi everyone, > > > > In August 2021, a list message > > from Benn Joseph at Northwestern UL described their trouble getting > incorrect Publish values when importing digital objects via spreadsheet. > Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It > seems like the ASpace code that interprets the incoming spreadsheet data is > being extra picky about the Type value of the ?publish? (Publish Digital > Object Record) attribute that is supplied in the spreadsheet. > > > > If the archivist uses the TRUE/FALSE controlled values provided in the > official template on github (bulk_import_DO_template.xlsx), digital objects > load with the correct ?publish? values and their PUI display looks good. > When I run the TYPE function on these values, I get type 4 (logical value). > > > > But sometimes, an archivist will paste in TRUE/FALSE values copied from > another file (especially true in high volume automated workflows). At a > glance these TRUE/FALSE values look identical but they aren?t. I noticed > that these values are left aligned in the cell, rather than centered as > Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE > function on a cell with these values I get type 2 (text). Seems like ASpace > wants only the logical TRUE/FALSE. An imported digital object that has the > text value TRUE for ?publish? will be set to the default FALSE > (unpublished). When this happens in high volume it?s a mess to clean up. > And despite being marked Published=FALSE in staff mode, in the PUI, these > digital objects are partially displaying. By that I mean, there is no > digital link but the DO?s are labeled DIGITAL and display in the PUI list > of digital objects. > > > > I guess the work-around is user education (warn users to only supply > logical TRUE/FALSE). But I?d prefer we tweaked ASpace code to accept either > the logical or text value of TRUE/FALSE as I suspect used to be the case > when spreadsheet import was plugin-based. > > > > Regards. ?julie > > > > Julie Wetherill > > HUIT Library Technology Services > > Harvard University > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Tue Jan 11 09:38:26 2022 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Tue, 11 Jan 2022 14:38:26 +0000 Subject: [Archivesspace_Users_Group] Where did the AS user manual go? Message-ID: For others who don?t have to consult the user manual often and might be confused.... This is the link to help from the AS staff UI https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/overview If you are not logged in to ?Atlassian? when you go to this link, you land on a ?create? page... which is confusing. The only hint that you are not logged in is a very cryptic arrow and right square bracket in the upper right corner. Once you are logged in, you do get to the AS help pages and can navigate to the manual. Kate -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Tue Jan 11 11:48:41 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Tue, 11 Jan 2022 11:48:41 -0500 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References: Message-ID: Hi, I wanted to clarify and expand upon the email I sent yesterday regarding our current (proposed) use of Digital Objects in ArchivesSpace and the related issues that we've encountered when importing DOs using the importer. My thought is that perhaps there are others out there who are working on a similar or related workflow issue who may have some suggestions for us. When we have a digital object publicly available on our external digital collections site and we wish to provide a link to that object from the component (archival object) level in the ASpace PUI: We leave *Publish? *unchecked *(that is Publish? = FALSE) *in the Basic Information section, but we *do *click Publish? in the File Version section: In the PUI, the above looks like this: Here, what we wanted was the link out to the digital object on the external site. The reason we do not click *Publish? *in the Basic Information section is because we believe users find it confusing when there are two disconnected references to digital objects within the component record. This is what the PUI looks like if both *Publish? *fields are clicked (both are TRUE): [image: image.png] Clicking FALSE under Basic Information suppresses the link to the Digital Object record in ASpace. However, the import spreadsheet has a single field for Publish and the File Version field inherits the imported selection for the Basic Info field, and does not provide the option to mark the Basic Information field FALSE and the File Version field TRUE: This means that we don't have the option to import a batch of digital objects in the same way that we want them to display, which results in having to manually edit DOs after import. Feel free to email me independently with any questions or if you'd like to continue this conversation offline. All best, Wendy ____________________________________ WENDY SCHEIR director THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212-229-5942 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives [image: THE NEW SCHOOL] On Mon, Jan 10, 2022 at 7:15 PM Wendy Scheir wrote: > I think a related or adjacent issue to this is that there are 2 separate > *Publish?* fields for each Digital Object record, but the import > spreadsheet has the option to select TRUE/FALSE for only 1 of them. > > The way we're using DOs, sometimes (often, actually) we want one=TRUE and > the other=FALSE within a single record. > > Wendy > > The New Archives and Special Collections > > On Mon, Jan 10, 2022, 5:11 PM Wetherill, Julie M. < > julie_wetherill at harvard.edu> wrote: > >> Hi everyone, >> >> >> >> In August 2021, a list message >> >> from Benn Joseph at Northwestern UL described their trouble getting >> incorrect Publish values when importing digital objects via spreadsheet. >> Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It >> seems like the ASpace code that interprets the incoming spreadsheet data is >> being extra picky about the Type value of the ?publish? (Publish Digital >> Object Record) attribute that is supplied in the spreadsheet. >> >> >> >> If the archivist uses the TRUE/FALSE controlled values provided in the >> official template on github (bulk_import_DO_template.xlsx), digital objects >> load with the correct ?publish? values and their PUI display looks good. >> When I run the TYPE function on these values, I get type 4 (logical value). >> >> >> >> But sometimes, an archivist will paste in TRUE/FALSE values copied from >> another file (especially true in high volume automated workflows). At a >> glance these TRUE/FALSE values look identical but they aren?t. I noticed >> that these values are left aligned in the cell, rather than centered as >> Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE >> function on a cell with these values I get type 2 (text). Seems like ASpace >> wants only the logical TRUE/FALSE. An imported digital object that has the >> text value TRUE for ?publish? will be set to the default FALSE >> (unpublished). When this happens in high volume it?s a mess to clean up. >> And despite being marked Published=FALSE in staff mode, in the PUI, these >> digital objects are partially displaying. By that I mean, there is no >> digital link but the DO?s are labeled DIGITAL and display in the PUI list >> of digital objects. >> >> >> >> I guess the work-around is user education (warn users to only supply >> logical TRUE/FALSE). But I?d prefer we tweaked ASpace code to accept either >> the logical or text value of TRUE/FALSE as I suspect used to be the case >> when spreadsheet import was plugin-based. >> >> >> >> Regards. ?julie >> >> >> >> Julie Wetherill >> >> HUIT Library Technology Services >> >> Harvard University >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 89321 bytes Desc: not available URL: From Corey.Schmidt at uga.edu Tue Jan 11 12:14:24 2022 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Tue, 11 Jan 2022 17:14:24 +0000 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References:

Message-ID: Hey Wendy, I believe there is a JIRA ticket about adding the File Version publish column to the spreadsheet importer: https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1158 It looks like it?s being worked on by the team and has gone through testing. I posted the ticket awhile back because we found this to be a frustrating experience for us as well, except not with the PUI but with EAD.xml exports. It doesn?t solve Julie?s original issue of logical vs. text based TRUE/FALSE inputs, but if there isn?t a JIRA ticket for that already, we can put one in. Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Wendy Scheir Sent: Tuesday, January 11, 2022 11:49 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Digital objects import with incorrect Published value [EXTERNAL SENDER - PROCEED CAUTIOUSLY] Hi, I wanted to clarify and expand upon the email I sent yesterday regarding our current (proposed) use of Digital Objects in ArchivesSpace and the related issues that we've encountered when importing DOs using the importer. My thought is that perhaps there are others out there who are working on a similar or related workflow issue who may have some suggestions for us. When we have a digital object publicly available on our external digital collections site and we wish to provide a link to that object from the component (archival object) level in the ASpace PUI: We leave Publish? unchecked (that is Publish? = FALSE) in the Basic Information section, but we do click Publish? in the File Version section: [https://lh6.googleusercontent.com/UQmRV-pqw1TD_rwZqoC1cD0A4Z3yGahtsHjYwfSzmP-RmI07PE_gGkXkmcAbEGN-WKDQ0N-Nn3kJCvp8WaoTHEl93Jldebskgk80DSSC4VhW4QHxoVOxE46oeG6vbnJe0QohOtoq] [https://lh4.googleusercontent.com/GaF1UYDhvl1QcGVmWUAKKoxx7cG0EM8zfWEup2AJk3bJw45jIJDrwqKIeKU5Zvi7-TH-z-pEvm0tF0ngPo44N30Mcwzyvu1gypC6W1NqIQABD7glLiEoYrX1VReBjZCxNbuXPHox] In the PUI, the above looks like this: [https://lh4.googleusercontent.com/D2cP_mxbtWK-pEhmRK1ACYGtRbRjCz59DQ4S9N1bom7bT2HOTfZQxNdRFuzwKvQkk1LPi2z6ObT6UqebFnVnXxQfYk8WpHKkY4rd2N84gvC-iGVsOXwukx0WBo7P7FH_oy9XpF7_] Here, what we wanted was the link out to the digital object on the external site. The reason we do not click Publish? in the Basic Information section is because we believe users find it confusing when there are two disconnected references to digital objects within the component record. This is what the PUI looks like if both Publish? fields are clicked (both are TRUE): [image.png] Clicking FALSE under Basic Information suppresses the link to the Digital Object record in ASpace. However, the import spreadsheet has a single field for Publish and the File Version field inherits the imported selection for the Basic Info field, and does not provide the option to mark the Basic Information field FALSE and the File Version field TRUE: [https://lh5.googleusercontent.com/DLgtSIP3kKvG3X5wZYq8B28rC-J8QldZPCn2ZjckfsQ5DLR3WlddkQMKjfpPXyplxYzPNfTDQ0Mzo-8MX2AlQ8mNq89RMXtzKCvLHS14SQM0kgyzuaKbE_g3TUeHjuF6RUWtcci7] This means that we don't have the option to import a batch of digital objects in the same way that we want them to display, which results in having to manually edit DOs after import. Feel free to email me independently with any questions or if you'd like to continue this conversation offline. All best, Wendy ____________________________________ WENDY SCHEIR director THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212-229-5942 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives [THE NEW SCHOOL] On Mon, Jan 10, 2022 at 7:15 PM Wendy Scheir > wrote: I think a related or adjacent issue to this is that there are 2 separate Publish? fields for each Digital Object record, but the import spreadsheet has the option to select TRUE/FALSE for only 1 of them. The way we're using DOs, sometimes (often, actually) we want one=TRUE and the other=FALSE within a single record. Wendy The New Archives and Special Collections On Mon, Jan 10, 2022, 5:11 PM Wetherill, Julie M. > wrote: Hi everyone, In August 2021, a list message from Benn Joseph at Northwestern UL described their trouble getting incorrect Publish values when importing digital objects via spreadsheet. Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It seems like the ASpace code that interprets the incoming spreadsheet data is being extra picky about the Type value of the ?publish? (Publish Digital Object Record) attribute that is supplied in the spreadsheet. If the archivist uses the TRUE/FALSE controlled values provided in the official template on github (bulk_import_DO_template.xlsx), digital objects load with the correct ?publish? values and their PUI display looks good. When I run the TYPE function on these values, I get type 4 (logical value). But sometimes, an archivist will paste in TRUE/FALSE values copied from another file (especially true in high volume automated workflows). At a glance these TRUE/FALSE values look identical but they aren?t. I noticed that these values are left aligned in the cell, rather than centered as Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE function on a cell with these values I get type 2 (text). Seems like ASpace wants only the logical TRUE/FALSE. An imported digital object that has the text value TRUE for ?publish? will be set to the default FALSE (unpublished). When this happens in high volume it?s a mess to clean up. And despite being marked Published=FALSE in staff mode, in the PUI, these digital objects are partially displaying. By that I mean, there is no digital link but the DO?s are labeled DIGITAL and display in the PUI list of digital objects. I guess the work-around is user education (warn users to only supply logical TRUE/FALSE). But I?d prefer we tweaked ASpace code to accept either the logical or text value of TRUE/FALSE as I suspect used to be the case when spreadsheet import was plugin-based. Regards. ?julie Julie Wetherill HUIT Library Technology Services Harvard University _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 56793 bytes Desc: image002.png URL: From scheirw at newschool.edu Tue Jan 11 12:28:37 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Tue, 11 Jan 2022 12:28:37 -0500 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References:

Message-ID: Thanks, Corey--glad to hear this! Will this be included in the upcoming 3.2.0 release? On Tue, Jan 11, 2022 at 12:14 PM Corey Schmidt wrote: > Hey Wendy, > > I believe there is a JIRA ticket about adding the File Version publish > column to the spreadsheet importer: > https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1158 > > It looks like it?s being worked on by the team and has gone through > testing. I posted the ticket awhile back because we found this to be a > frustrating experience for us as well, except not with the PUI but with > EAD.xml exports. It doesn?t solve Julie?s original issue of logical vs. > text based TRUE/FALSE inputs, but if there isn?t a JIRA ticket for that > already, we can put one in. > > Corey > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Wendy > Scheir > *Sent:* Tuesday, January 11, 2022 11:49 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Digital objects import with > incorrect Published value > > > > [EXTERNAL SENDER - PROCEED CAUTIOUSLY] > > Hi, > > > > I wanted to clarify and expand upon the email I sent yesterday regarding > our current (proposed) use of Digital Objects in ArchivesSpace and the > related issues that we've encountered when importing DOs using the > importer. My thought is that perhaps there are others out there who are > working on a similar or related workflow issue who may have some > suggestions for us. > > > > When we have a digital object publicly available on our external digital > collections site and we wish to provide a link to that object from the > component (archival object) level in the ASpace PUI: > > > > We leave *Publish? *unchecked *(that is Publish? = FALSE) *in the Basic > Information section, but we *do *click *Publish? *in the File Version > section: > > > > > > > In the PUI, the above looks like this: > > > > Here, what we wanted was the link out to the digital object on the > external site. The reason we do not click *Publish? *in the Basic > Information section is because we believe users find it confusing when > there are two disconnected references to digital objects within the > component record. > > > > This is what the PUI looks like if both *Publish? *fields are clicked > (both are TRUE): > > [image: image.png] > > > > Clicking FALSE under Basic Information suppresses the link to the Digital > Object record in ASpace. > > > > However, the import spreadsheet has a single field for Publish and the > File Version field inherits the imported selection for the Basic Info > field, and does not provide the option to mark the Basic Information field > FALSE and the File Version field TRUE: > > > > > > This means that we don't have the option to import a batch of digital > objects in the same way that we want them to display, which results in > having to manually edit DOs after import. > > > > Feel free to email me independently with any questions or if you'd like to > continue this conversation offline. > > > > All best, > > Wendy > > > > ____________________________________ > > *WENDY SCHEIR* > > director > THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS > > 66 FIFTH AVENUE, NEW YORK, NY 10011 > > scheirw at newschool.edu > > > *T* 212-229-5942 > > Explore the Archives | Digital > Collections from the Archives > | New School Histories > | @tnsarchives > > > [image: THE NEW SCHOOL] > > > > > > On Mon, Jan 10, 2022 at 7:15 PM Wendy Scheir > wrote: > > I think a related or adjacent issue to this is that there are 2 separate > *Publish?* fields for each Digital Object record, but the import > spreadsheet has the option to select TRUE/FALSE for only 1 of them. > > > > The way we're using DOs, sometimes (often, actually) we want one=TRUE and > the other=FALSE within a single record. > > > > Wendy > > > > The New Archives and Special Collections > > > > On Mon, Jan 10, 2022, 5:11 PM Wetherill, Julie M. < > julie_wetherill at harvard.edu> wrote: > > Hi everyone, > > > > In August 2021, a list message > > from Benn Joseph at Northwestern UL described their trouble getting > incorrect Publish values when importing digital objects via spreadsheet. > Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It > seems like the ASpace code that interprets the incoming spreadsheet data is > being extra picky about the Type value of the ?publish? (Publish Digital > Object Record) attribute that is supplied in the spreadsheet. > > > > If the archivist uses the TRUE/FALSE controlled values provided in the > official template on github (bulk_import_DO_template.xlsx), digital objects > load with the correct ?publish? values and their PUI display looks good. > When I run the TYPE function on these values, I get type 4 (logical value). > > > > But sometimes, an archivist will paste in TRUE/FALSE values copied from > another file (especially true in high volume automated workflows). At a > glance these TRUE/FALSE values look identical but they aren?t. I noticed > that these values are left aligned in the cell, rather than centered as > Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE > function on a cell with these values I get type 2 (text). Seems like ASpace > wants only the logical TRUE/FALSE. An imported digital object that has the > text value TRUE for ?publish? will be set to the default FALSE > (unpublished). When this happens in high volume it?s a mess to clean up. > And despite being marked Published=FALSE in staff mode, in the PUI, these > digital objects are partially displaying. By that I mean, there is no > digital link but the DO?s are labeled DIGITAL and display in the PUI list > of digital objects. > > > > I guess the work-around is user education (warn users to only supply > logical TRUE/FALSE). But I?d prefer we tweaked ASpace code to accept either > the logical or text value of TRUE/FALSE as I suspect used to be the case > when spreadsheet import was plugin-based. > > > > Regards. ?julie > > > > Julie Wetherill > > HUIT Library Technology Services > > Harvard University > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 56793 bytes Desc: not available URL: From Joshua.D.Shaw at dartmouth.edu Wed Jan 12 09:00:39 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 12 Jan 2022 14:00:39 +0000 Subject: [Archivesspace_Users_Group] Adding Route to PUI - tip Message-ID: Since this just tripped me up, I figured I'd share with the group. If you are looking to add a route to the PUI in a plugin, you cannot use a two part path for your new route since this existing route will catch any of those: get ":obj_type/:slug_or_id" => 'objects#show' https://github.com/archivesspace/archivesspace/blob/a2715dd9bf4d2c11671f2034d697a6c06918f39d/public/config/routes.rb#L88 jds -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Jan 12 09:58:24 2022 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 12 Jan 2022 14:58:24 +0000 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References:

Message-ID: Wendy, Not sure if it will be in 3.2.0. One of the ASpace team members might be able to say. Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Wendy Scheir Sent: Tuesday, January 11, 2022 12:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Digital objects import with incorrect Published value [EXTERNAL SENDER - PROCEED CAUTIOUSLY] Thanks, Corey--glad to hear this! Will this be included in the upcoming 3.2.0 release? On Tue, Jan 11, 2022 at 12:14 PM Corey Schmidt > wrote: Hey Wendy, I believe there is a JIRA ticket about adding the File Version publish column to the spreadsheet importer: https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1158 It looks like it?s being worked on by the team and has gone through testing. I posted the ticket awhile back because we found this to be a frustrating experience for us as well, except not with the PUI but with EAD.xml exports. It doesn?t solve Julie?s original issue of logical vs. text based TRUE/FALSE inputs, but if there isn?t a JIRA ticket for that already, we can put one in. Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> On Behalf Of Wendy Scheir Sent: Tuesday, January 11, 2022 11:49 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Digital objects import with incorrect Published value [EXTERNAL SENDER - PROCEED CAUTIOUSLY] Hi, I wanted to clarify and expand upon the email I sent yesterday regarding our current (proposed) use of Digital Objects in ArchivesSpace and the related issues that we've encountered when importing DOs using the importer. My thought is that perhaps there are others out there who are working on a similar or related workflow issue who may have some suggestions for us. When we have a digital object publicly available on our external digital collections site and we wish to provide a link to that object from the component (archival object) level in the ASpace PUI: We leave Publish? unchecked (that is Publish? = FALSE) in the Basic Information section, but we do click Publish? in the File Version section: [https://lh6.googleusercontent.com/UQmRV-pqw1TD_rwZqoC1cD0A4Z3yGahtsHjYwfSzmP-RmI07PE_gGkXkmcAbEGN-WKDQ0N-Nn3kJCvp8WaoTHEl93Jldebskgk80DSSC4VhW4QHxoVOxE46oeG6vbnJe0QohOtoq] [https://lh4.googleusercontent.com/GaF1UYDhvl1QcGVmWUAKKoxx7cG0EM8zfWEup2AJk3bJw45jIJDrwqKIeKU5Zvi7-TH-z-pEvm0tF0ngPo44N30Mcwzyvu1gypC6W1NqIQABD7glLiEoYrX1VReBjZCxNbuXPHox] In the PUI, the above looks like this: [https://lh4.googleusercontent.com/D2cP_mxbtWK-pEhmRK1ACYGtRbRjCz59DQ4S9N1bom7bT2HOTfZQxNdRFuzwKvQkk1LPi2z6ObT6UqebFnVnXxQfYk8WpHKkY4rd2N84gvC-iGVsOXwukx0WBo7P7FH_oy9XpF7_] Here, what we wanted was the link out to the digital object on the external site. The reason we do not click Publish? in the Basic Information section is because we believe users find it confusing when there are two disconnected references to digital objects within the component record. This is what the PUI looks like if both Publish? fields are clicked (both are TRUE): [image.png] Clicking FALSE under Basic Information suppresses the link to the Digital Object record in ASpace. However, the import spreadsheet has a single field for Publish and the File Version field inherits the imported selection for the Basic Info field, and does not provide the option to mark the Basic Information field FALSE and the File Version field TRUE: [https://lh5.googleusercontent.com/DLgtSIP3kKvG3X5wZYq8B28rC-J8QldZPCn2ZjckfsQ5DLR3WlddkQMKjfpPXyplxYzPNfTDQ0Mzo-8MX2AlQ8mNq89RMXtzKCvLHS14SQM0kgyzuaKbE_g3TUeHjuF6RUWtcci7] This means that we don't have the option to import a batch of digital objects in the same way that we want them to display, which results in having to manually edit DOs after import. Feel free to email me independently with any questions or if you'd like to continue this conversation offline. All best, Wendy ____________________________________ WENDY SCHEIR director THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212-229-5942 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives [THE NEW SCHOOL] On Mon, Jan 10, 2022 at 7:15 PM Wendy Scheir > wrote: I think a related or adjacent issue to this is that there are 2 separate Publish? fields for each Digital Object record, but the import spreadsheet has the option to select TRUE/FALSE for only 1 of them. The way we're using DOs, sometimes (often, actually) we want one=TRUE and the other=FALSE within a single record. Wendy The New Archives and Special Collections On Mon, Jan 10, 2022, 5:11 PM Wetherill, Julie M. > wrote: Hi everyone, In August 2021, a list message from Benn Joseph at Northwestern UL described their trouble getting incorrect Publish values when importing digital objects via spreadsheet. Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It seems like the ASpace code that interprets the incoming spreadsheet data is being extra picky about the Type value of the ?publish? (Publish Digital Object Record) attribute that is supplied in the spreadsheet. If the archivist uses the TRUE/FALSE controlled values provided in the official template on github (bulk_import_DO_template.xlsx), digital objects load with the correct ?publish? values and their PUI display looks good. When I run the TYPE function on these values, I get type 4 (logical value). But sometimes, an archivist will paste in TRUE/FALSE values copied from another file (especially true in high volume automated workflows). At a glance these TRUE/FALSE values look identical but they aren?t. I noticed that these values are left aligned in the cell, rather than centered as Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE function on a cell with these values I get type 2 (text). Seems like ASpace wants only the logical TRUE/FALSE. An imported digital object that has the text value TRUE for ?publish? will be set to the default FALSE (unpublished). When this happens in high volume it?s a mess to clean up. And despite being marked Published=FALSE in staff mode, in the PUI, these digital objects are partially displaying. By that I mean, there is no digital link but the DO?s are labeled DIGITAL and display in the PUI list of digital objects. I guess the work-around is user education (warn users to only supply logical TRUE/FALSE). But I?d prefer we tweaked ASpace code to accept either the logical or text value of TRUE/FALSE as I suspect used to be the case when spreadsheet import was plugin-based. Regards. ?julie Julie Wetherill HUIT Library Technology Services Harvard University _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 56793 bytes Desc: image001.png URL: From christine.dibella at lyrasis.org Wed Jan 12 12:10:46 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 12 Jan 2022 17:10:46 +0000 Subject: [Archivesspace_Users_Group] Digital objects import with incorrect Published value In-Reply-To: References: