From Corey.Schmidt at uga.edu Tue Jun 1 13:06:29 2021 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Tue, 1 Jun 2021 17:06:29 +0000 Subject: [Archivesspace_Users_Group] Generating a Custom File with a Report Plugin Message-ID: Hello all, I have a question about making a custom report plugin for ArchivesSpace. Is it possible to create a custom CSV output file for a report? I am grabbing our digital object file versions (aka urls) and checking their responses for errors. I'd then like to log those errors in a CSV file that a user can download once the report is finished. Here's a link to my script so far: https://github.com/uga-libraries/uga-archivesspace-reports/blob/master/check_urls/backend/model/check_urls.rb. For other custom reports, they take what is returned from an SQL query and can generate a JSON, HTML, CSV, and PDF file, depending on what a user selects from a drop-down list. Since I am creating a custom CSV file myself with this script, I want that to be the only output file. I think I have to change the reports.rb /reports/:code endpoint somehow, but I'm not sure because that would mess with all other reports and how they work. Any help/advice would be greatly appreciated. Thanks, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Jun 2 15:00:28 2021 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 2 Jun 2021 19:00:28 +0000 Subject: [Archivesspace_Users_Group] Finding Aid Discovery Platform Survey Message-ID: Dear all, We here at the University of Georgia are interested in how users of ArchivesSpace are making their finding aids available online. This short, 10-to-15-minute survey asks about what discovery platform your organization/institution uses and how you have fit it to your needs. A discovery platform is defined as a web application designed specifically for sharing finding aids online to allow users to search and browse them. Some examples of discovery platforms include the ArchivesSpace PUI (Public User Interface), ArcLight, and XTF (eXtensible Text Framework). The data will be aggregated and confidential and we will not be collecting emails. We may share the results with the community, but if you feel uncomfortable answering a question, you are free to skip it. Please try to complete the survey by June 18. If you have any questions about the survey, please contact the ArchivesSpace Project Manager at the University of Georgia Special Collections Libraries, Corey Schmidt (Corey.Schmidt at uga.edu). Thank you for your participation! Here is the link to the survey: https://forms.gle/azChKrtqJ1qG81tMA Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From katie.nash at wisc.edu Thu Jun 3 10:54:39 2021 From: katie.nash at wisc.edu (Katie Nash) Date: Thu, 3 Jun 2021 14:54:39 +0000 Subject: [Archivesspace_Users_Group] Question about Instances and Digital Objects Message-ID: Hello colleagues, Sending the question below on behalf of a colleague. Please send responses directly to Alison Bridger at alison.bridger at wisconsinhistory.org. When attempting to add a Digital Object under Instance in a Resource record, the following error occurs when attempting to save: "translation missing: validation_errors.protected_read-only_list_#/instances/1/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__ ..." Any idea how to fix the error? Katie Nash | University Archivist and Head of UW Archives University of Wisconsin-Madison Libraries 425 Steenbock Library | 550 Babcock Dr. Madison, WI 53706 1-608-265-1988 Pronouns: she/her/hers Tell us your COVID-19 story! -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Thu Jun 3 11:18:07 2021 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Thu, 3 Jun 2021 15:18:07 +0000 Subject: [Archivesspace_Users_Group] using tooltips on Assessment values Message-ID: Hi everyone, I'm interested in Corinne's question below as well, and have another query regarding tooltips in the Assessments module-is it possible to create tooltips for additional user-added ratings (the ones that go 1 - 5) under "Assessment Information"? I can see how the tooltips are constructed for the original ratings in the en.yml file at archivesspace/common/locales/en.yml, but am not sure if there's a way to add tooltips for any ratings added by staff in the SUI. Thanks! --Benn Benn Joseph 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 Corinne Chatnik Sent: Tuesday, May 18, 2021 8:33 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Use tooltips on Assessment values Hi, Is it possible for tooltips to be used on the values in the Formats/Materials or Conservation Issues section of the Assessments module? Is there an example of this on GitHub anywhere? I tried following the tooltips format used for assessment_attribute in en.yml because it seemed like the closest example of this but nothing happened. Thanks! Corinne Chatnik Digital Strategies New York State Archives 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 christine.dibella at lyrasis.org Fri Jun 4 09:25:01 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 4 Jun 2021 13:25:01 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 3.0.1 now available Message-ID: Hello ArchivesSpace members, ArchivesSpace 3.0.1 is now available. It corrects an issue with the migration of agent contact notes that was present in 3.0.0. When you choose to upgrade past 2.8.1 you should use this version. We have pulled the download file for 3.0.0 to hopefully avoid confusion as much as possible. Otherwise, everything that was true about 3.0.0 is true about 3.0.1. More information about what's in the release and the link to download it are at https://github.com/archivesspace/archivesspace/releases. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you have questions or need any assistance, please let us know. I apologize for the inconvenience but I'm very glad we were able to catch and rectify the issue so soon after the original release. We expect to put out a more typical release with the usual complement of new infrastructure improvements, bug fixes, and feature enhancements in the late summer. 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 ph448 at cam.ac.uk Fri Jun 4 11:19:43 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Fri, 4 Jun 2021 15:19:43 +0000 Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database Message-ID: Dear list users, The Cambridge University Library AS instance has recently been hit with severe performance issues while users were running spreadsheet imports to add archival objects, details are in https://github.com/archivesspace/archivesspace/issues/2275; the summary is that a DELETE query with a dependent subquery running for every line of the spreadsheet input seems to make concurrent database access near impossible. Has anyone else experienced anything similar? Us using MariaDB instead of MySQL might well be the cause, but I'd like confirmation before work is scheduled to migrate the database that this will indeed help. If you're using spreadsheet imports, we'd be grateful if you could let us know either on or off list whether you use MySQL or MariaDB and if you had any problems with the migration queries hogging the database. Thanks, p -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Fri Jun 4 11:43:30 2021 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 4 Jun 2021 15:43:30 +0000 Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database In-Reply-To: References: Message-ID: Hi Peter - We also see issues with concurrent database access. If one user initiates a large delete or import, other users can experience long delays and timeouts. We've also noticed that Edit save times are especially long when there is a language subrecord. (An archival_object with a lang_material can take 30 seconds to save, whereas records without a lang_material save much more quickly). We are in v 2.71 and we also use MariaDB. We see the same issue in our test 2.8.1 instance. I'd be very interested to hear if MySQL offers a better experience for Cambridge, Thanks, Nancy kennedyn at si.edu Nancy Kennedy Smithsonian Institution From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Peter Heiner Sent: Friday, June 4, 2021 11:20 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database External Email - Exercise Caution Dear list users, The Cambridge University Library AS instance has recently been hit with severe performance issues while users were running spreadsheet imports to add archival objects, details are in https://github.com/archivesspace/archivesspace/issues/2275; the summary is that a DELETE query with a dependent subquery running for every line of the spreadsheet input seems to make concurrent database access near impossible. Has anyone else experienced anything similar? Us using MariaDB instead of MySQL might well be the cause, but I'd like confirmation before work is scheduled to migrate the database that this will indeed help. If you're using spreadsheet imports, we'd be grateful if you could let us know either on or off list whether you use MySQL or MariaDB and if you had any problems with the migration queries hogging the database. Thanks, p -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Sat Jun 5 21:35:03 2021 From: james at hudmol.com (James Bullen) Date: Sun, 6 Jun 2021 11:35:03 +1000 Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database In-Reply-To: References: Message-ID: <11A5DAA8-0A91-4F72-B2A6-83388E2DC51F@hudmol.com> Hi Peter and Nancy, Bulk update operations usually run in database transactions. This is great because it guarantees that the database will be in a consistent state when the job completes - if it succeeds then all of the updates are applied, if it fails then none of the updates are applied. The price for this guarantee is that any affected records are locked until the job completes. We recently implemented the ability to submit import jobs to be run after hours for a client to work around this. Ideally, there would be some indication in the UI that a record is locked (maybe hiding the edit button and a helpful message), but we haven?t investigated this. Hope that helps. Cheers, James > On Jun 5, 2021, at 1:43 AM, Kennedy, Nancy wrote: > > Hi Peter ? > We also see issues with concurrent database access. If one user initiates a large delete or import, other users can experience long delays and timeouts. We?ve also noticed that Edit save times are especially long when there is a language subrecord. (An archival_object with a lang_material can take 30 seconds to save, whereas records without a lang_material save much more quickly). > > We are in v 2.71 and we also use MariaDB. We see the same issue in our test 2.8.1 instance. I?d be very interested to hear if MySQL offers a better experience for Cambridge, > > Thanks, > Nancy > > kennedyn at si.edu > Nancy Kennedy > Smithsonian Institution > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Peter Heiner > Sent: Friday, June 4, 2021 11:20 AM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database > > External Email - Exercise Caution > Dear list users, > > The Cambridge University Library AS instance has recently been hit with severe performance issues while users were running spreadsheet imports to add archival objects, details are in https://github.com/archivesspace/archivesspace/issues/2275 ; the summary is that a DELETE query with a dependent subquery running for every line of the spreadsheet input seems to make concurrent database access near impossible. > > Has anyone else experienced anything similar? Us using MariaDB instead of MySQL might well be the cause, but I'd like confirmation before work is scheduled to migrate the database that this will indeed help. If you're using spreadsheet imports, we'd be grateful if you could let us know either on or off list whether you use MySQL or MariaDB and if you had any problems with the migration queries hogging the database. > > Thanks, > 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 ph448 at cam.ac.uk Sun Jun 6 04:02:03 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Sun, 6 Jun 2021 08:02:03 +0000 Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database In-Reply-To: <11A5DAA8-0A91-4F72-B2A6-83388E2DC51F@hudmol.com> References: <11A5DAA8-0A91-4F72-B2A6-83388E2DC51F@hudmol.com> Message-ID: <20210606080203.xvlyjivnvrjt3oc3@sparkly.localdomain> James Bullen wrote on 2021-06-06 11:35:03: > Bulk update operations usually run in database transactions. This is great because it guarantees that the database will be in a consistent state when the job completes - if it succeeds then all of the updates are applied, if it fails then none of the updates are applied. > > The price for this guarantee is that any affected records are locked until the job completes. Thanks for your response. I generally agree with your points but have mine to make. One is that the consistency unit here need not be the entire job, it is sufficient to isolate a single line, and I would normally expect the database to cope fine with such a workload. Secondly, if I read my database output correctly, in this case the problem is not a wholly isolated bulk update but unnecessary table scans occurring for each line that make the database hold a lock for several seconds instead of milliseconds. I've yet to understand the purpose of the subnote_metadata table and why the delete is taking place, but we did notice that the query tried IDs that were not in the database. In any case, it should be possible to unroll the subquery or provide optimiser hints for the bottleneck to go away. > We recently implemented the ability to submit import jobs to be run after hours for a client to work around this. We were thinking of a similar workaround, do you?have anything you could share?with us? Thanks, p From james at hudmol.com Sun Jun 6 05:25:54 2021 From: james at hudmol.com (James Bullen) Date: Sun, 6 Jun 2021 19:25:54 +1000 Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database In-Reply-To: <20210606080203.xvlyjivnvrjt3oc3@sparkly.localdomain> References: <11A5DAA8-0A91-4F72-B2A6-83388E2DC51F@hudmol.com> <20210606080203.xvlyjivnvrjt3oc3@sparkly.localdomain> Message-ID: <04C72FDB-D590-4071-A8C2-83A1DF9B7151@hudmol.com> Hi Peter, I?m not familiar with the spreadsheet importer, but it sounds like you?ve done the analysis to be in a position to fix it. :) Here?s a commit for the ?run tonight? feature implemented in a plugin: https://gitlab.gaiaresources.com.au/qsa/as_runcorn/-/commit/8a2bd97 It was refined in a few subsequent commits (4369dd0, 800ac1c, 5f1207e). Cheers, James > On Jun 6, 2021, at 6:02 PM, Peter Heiner wrote: > > James Bullen wrote on 2021-06-06 11:35:03: > >> Bulk update operations usually run in database transactions. This is great because it guarantees that the database will be in a consistent state when the job completes - if it succeeds then all of the updates are applied, if it fails then none of the updates are applied. >> >> The price for this guarantee is that any affected records are locked until the job completes. > > Thanks for your response. I generally agree with your points but have mine to make. > One is that the consistency unit here need not be the entire job, it is sufficient to isolate a single line, and I would normally expect the database to cope fine with such a workload. > Secondly, if I read my database output correctly, in this case the problem is not a wholly isolated bulk update but unnecessary table scans occurring for each line that make the database hold a lock for several seconds instead of milliseconds. I've yet to understand the purpose of the subnote_metadata table and why the delete is taking place, but we did notice that the query tried IDs that were not in the database. > In any case, it should be possible to unroll the subquery or provide optimiser hints for the bottleneck to go away. > >> We recently implemented the ability to submit import jobs to be run after hours for a client to work around this. > > We were thinking of a similar workaround, do you have anything you could share with us? > > Thanks, > 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 Jessica.Crouch at lyrasis.org Mon Jun 7 10:35:39 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 7 Jun 2021 14:35:39 +0000 Subject: [Archivesspace_Users_Group] There's still time to volunteer for the next ArchivesSpace annual forum planning team Message-ID: <088C6061-825B-4440-8125-6946AF8CCE50@lyrasis.org> Dear ArchivesSpace Members, We are currently looking for volunteers for the working group to plan our seventh annual ArchivesSpace Annual Member Forum! Just as in previous years, this forum will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. While traditionally an in-person event, ArchivesSpace will be holding its seventh Annual Member Forum virtually. Although it will be held during the week of the Society of American Archivists Annual Meeting as in previous years, the Member Forum is not part of SAA and does not require registration for the SAA Annual Meeting. This free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend discussions and trainings on a variety of topics. All community members are welcome to volunteer for this working group. We will schedule meetings and the forum itself in ways that allow for participation across time zones. If you would like to volunteer, please respond by June 14, 2021. And if you have any questions, contact Jessica at jessica.crouch at lyrasis.org. We look forward to another great event, with your help! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29062 bytes Desc: image001.jpg URL: From pshowell at anderson.edu Mon Jun 7 13:00:13 2021 From: pshowell at anderson.edu (Preston Howell) Date: Mon, 7 Jun 2021 13:00:13 -0400 Subject: [Archivesspace_Users_Group] Trouble with creating a Docker container Message-ID: Good afternoon friends! I'm attempting to create a Docker container for ArchivesSpace and I cannot seem to get it to connect to my MySQL container. I'm still very new to Docker, so I'm sure there is a step in the process I am missing. My repo is here: https://github.com/pshowell23/aspace-docker and the error I keep getting is attached. Sorry to be a bother, but I just don't understand where I've gone wrong. I tried adding environment variables in the docker-compose file and I've tried changing the config.rb file. -- Preston Howell | Library Technology Specialist | Nicholson Library Anderson University | 1100 E. 5th St., Anderson, IN 46012 (765) 641-4270 | anderson.edu Confidentiality Notice: Because email is not a secure medium, confidentiality of email cannot be guaranteed. This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution, or copying is prohibited. If you are not the intended recipient, please contact the sender by replying to this email and destroy/delete all copies of this email message. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2021-06-07 at 12.52.46 PM.png Type: image/png Size: 86233 bytes Desc: not available URL: From hanstra at nd.edu Mon Jun 7 13:35:07 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Mon, 7 Jun 2021 13:35:07 -0400 Subject: [Archivesspace_Users_Group] config.rb options Message-ID: As we work with ArchivesSpace here, we are figuring out that the confg.rb file has components which could be updated by various groups. Is there a way to break up the file so that each group can maintain their portion but all of it is combined to properly configure ArchivesSpace? How might others handle this? Thanks Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Mon Jun 7 16:42:02 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Mon, 7 Jun 2021 20:42:02 +0000 Subject: [Archivesspace_Users_Group] Trouble with creating a Docker container In-Reply-To: References: Message-ID: I'm attempting to create a Docker container for ArchivesSpace and I cannot seem to get it to connect to my MySQL container. I'm still very new to Docker, so I'm sure there is a step in the process I am missing. My repo is here: https://github.com/pshowell23/aspace-docker and the error I keep getting is attached. Sorry to be a bother, but I just don't understand where I've gone wrong. I tried adding environment variables in the docker-compose file and I've tried changing the config.rb file. 'localhost', the hostname for the IP address '127.0.0.1', is meaningless in a container, you can't connect to it. What's more, MySQL's convention is that 'localhost' does not mean a TCP connection, but a UNIX socket connection, which will not work either. The solution is to use the hostname of the database container from the compose file in the connection string: AppConfig[:db_url] = "jdbc:mysql://aspace_data:3306/archivesspace?user=as&password=as123&useUnicode=true&characterEncoding=UTF-8" p -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Jun 8 04:27:08 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 8 Jun 2021 09:27:08 +0100 Subject: [Archivesspace_Users_Group] config.rb options In-Reply-To: References: Message-ID: <8b717469-1898-3153-f05f-d00a85915a48@bodleian.ox.ac.uk> Because config.rb is just a Ruby script, that gets run during startup, so you should be able to use: require_relative 'configA.rb' require_relative 'configB.rb' But it won't change the fact that any changes will require a restart before they will take effect. Andrew. On 07/06/2021 18:35, Tom Hanstra wrote: > As we work with ArchivesSpace here, we are figuring out that the > confg.rb file has components which could be updated by various groups. > Is there a way to break up the file so that each group can maintain > their portion but all of it is combined to properly configure > ArchivesSpace? How might others handle this? > > Thanks > Tom > > -- > *Tom Hanstra* > /Sr. Systems Administrator/ > hanstra at nd.edu > > > > _______________________________________________ > 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 brian.hoffman at lyrasis.org Wed Jun 9 16:41:36 2021 From: brian.hoffman at lyrasis.org (Brian Hoffman) Date: Wed, 9 Jun 2021 20:41:36 +0000 Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database In-Reply-To: <04C72FDB-D590-4071-A8C2-83A1DF9B7151@hudmol.com> References: <11A5DAA8-0A91-4F72-B2A6-83388E2DC51F@hudmol.com> <20210606080203.xvlyjivnvrjt3oc3@sparkly.localdomain>, <04C72FDB-D590-4071-A8C2-83A1DF9B7151@hudmol.com> Message-ID: Hi Peter, James, and Nancy, I posted a test release (for testing only) that may help with the issue Peter identified. If anyone wants to test and report back that would be great. https://github.com/quoideneuf/archivesspace/releases/tag/issue-2275 Brian From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James Bullen Date: Sunday, June 6, 2021 at 5:26 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Spreadsheet imports locking up database Hi Peter, I?m not familiar with the spreadsheet importer, but it sounds like you?ve done the analysis to be in a position to fix it. :) Here?s a commit for the ?run tonight? feature implemented in a plugin: https://gitlab.gaiaresources.com.au/qsa/as_runcorn/-/commit/8a2bd97 It was refined in a few subsequent commits (4369dd0, 800ac1c, 5f1207e). Cheers, James On Jun 6, 2021, at 6:02 PM, Peter Heiner > wrote: James Bullen wrote on 2021-06-06 11:35:03: Bulk update operations usually run in database transactions. This is great because it guarantees that the database will be in a consistent state when the job completes - if it succeeds then all of the updates are applied, if it fails then none of the updates are applied. The price for this guarantee is that any affected records are locked until the job completes. Thanks for your response. I generally agree with your points but have mine to make. One is that the consistency unit here need not be the entire job, it is sufficient to isolate a single line, and I would normally expect the database to cope fine with such a workload. Secondly, if I read my database output correctly, in this case the problem is not a wholly isolated bulk update but unnecessary table scans occurring for each line that make the database hold a lock for several seconds instead of milliseconds. I've yet to understand the purpose of the subnote_metadata table and why the delete is taking place, but we did notice that the query tried IDs that were not in the database. In any case, it should be possible to unroll the subquery or provide optimiser hints for the bottleneck to go away. We recently implemented the ability to submit import jobs to be run after hours for a client to work around this. We were thinking of a similar workaround, do you have anything you could share with us? Thanks, 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 Scott.Renton at ed.ac.uk Thu Jun 10 12:26:07 2021 From: Scott.Renton at ed.ac.uk (RENTON Scott) Date: Thu, 10 Jun 2021 16:26:07 +0000 Subject: [Archivesspace_Users_Group] Date concatenation Message-ID: Hi folks, I posted this one to the Google Group, but nobody took the bait. I hope it's ok for me to send to the listserv. I wondered if anyone knew about configuring the concatenation of dates to titles in the frontend and pui? We have noticed since moving to v2.8.1 that items with more than one date item are getting multiple dates appended, and the curators of these collections find it a bit unwieldy and are asking if we can turn it off. In v2.6, they were only getting the first one appended- has there been a change to the logic? I couldn't see anything in config which would help with this, but I know that if it's in the code any such change will affect the whole site, so those curators that like having one date appended may lose that functionality. Thanks Scott ========== Scott Renton Digital Library Development & Systems Floor F East Argyle House 515219 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th' ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lora.Woodford at lyrasis.org Thu Jun 10 13:49:38 2021 From: Lora.Woodford at lyrasis.org (Lora Woodford) Date: Thu, 10 Jun 2021 17:49:38 +0000 Subject: [Archivesspace_Users_Group] Date concatenation In-Reply-To: References: Message-ID: Hi Scott, This was the result of a bugfix request that was implemented and delivered as part of the 2.8.0 release. Here?s the JIRA ticket requesting that functionality be added to the core of ArchivesSpace: https://archivesspace.atlassian.net/browse/ANW-172 It was not implemented as a configurable feature as the ticket described it as a bug that should be remedied for all users. Namely, it was deemed a mistake/oversight that only the first of multiple provided dates was being added to the display string. As far as locally changing things on your end by writing a custom plugin, that would likely be a fairly major undertaking (that might not ultimately be successful) as the change to the display string was made at the model level. I wonder whether anyone else has considered doing that? Best, Lora Woodford From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of RENTON Scott Date: Thursday, June 10, 2021 at 12:26 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Date concatenation Hi folks, I posted this one to the Google Group, but nobody took the bait. I hope it's ok for me to send to the listserv. I wondered if anyone knew about configuring the concatenation of dates to titles in the frontend and pui? We have noticed since moving to v2.8.1 that items with more than one date item are getting multiple dates appended, and the curators of these collections find it a bit unwieldy and are asking if we can turn it off. In v2.6, they were only getting the first one appended- has there been a change to the logic? I couldn't see anything in config which would help with this, but I know that if it's in the code any such change will affect the whole site, so those curators that like having one date appended may lose that functionality. Thanks Scott ========== Scott Renton Digital Library Development & Systems Floor F East Argyle House 515219 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th? ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corinne.Chatnik at nysed.gov Fri Jun 11 11:28:34 2021 From: Corinne.Chatnik at nysed.gov (Corinne Chatnik) Date: Fri, 11 Jun 2021 15:28:34 +0000 Subject: [Archivesspace_Users_Group] Material Types Plugin - Uninstall Message-ID: Hi, I installed the Material Types Plugin from Hudson Molonglo (https://github.com/hudmol/material_types) and while it functioned well, our repository decided we don't need to utilize it. To install it we had to migrate the database and it added at least two tables to the database. Is there a way to safely uninstall it and remove those tables? I can't find uninstall instructions in the documentation. Thanks! Corinne Chatnik Digital Strategies New York State Archives 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 Jessica.Crouch at lyrasis.org Mon Jun 14 12:10:07 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 14 Jun 2021 16:10:07 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement - Virtual Every Step of the Way: Migrating to ArchivesSpace during Remote Work Message-ID: Dear ArchivesSpace users, ArchivesSpace will be offering a webinar on implementing ArchivesSpace in a remote work environment. In this webinar, Tomaro Taylor, Amanda Boczar, and Anastasia Temkina of USF Libraries - Tampa Special Collections will illustrate how they structured their complete migration to ArchivesSpace in a remote environment, including the active incorporation of student workers with various levels of archival experience. When: July 7, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00 pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_p_-DXUf8S1KlEYmsheGujw This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: In February 2020, USF Libraries ? Tampa Special Collections formally began the process to migrate to ArchivesSpace. Those discussions quickly stalled, however, when the University asked that they begin to formulate continuity of operations plans for remote work in preparations for what was then a hypothetical shutdown. Early into lockdown, USF determined that it would actually be the perfect time to migrate to ArchivesSpace. The campus was closed, no Reading Room services could be provided, and staff wanted to engage in meaningful projects. Guiding a team consisting of librarians, staff, and student employees, Special Collections organized a multi-phase plan for preparing data for migration, undergoing migration, and cleaning records in ArchivesSpace. As staff begin to gain more physical access in 2021, they are finalizing the clean up and ready to engage with patrons using ArchivesSpace. In this webinar, Tomaro Taylor, Amanda Boczar, and Anastasia Temkina of USF Libraries - Tampa Special Collections will illustrate how they structured their complete migration to ArchivesSpace in a remote environment, including the active incorporation of student workers with various levels of archival experience. No one on staff had prior experience with ArchivesSpace and all members of the team were trained in stages. They will also address how this project encouraged a more holistic reassessment, including systematically evaluating finding aids for missing information, conscious editing of descriptive content and subject headings, and the addition of classification headers. A Q&A will follow. Presenter Information: Tomaro Taylor is the Head of Special Collections at the University of South Florida Libraries Tampa campus. A Certified Archivist, Tomaro has nearly 20 years of experience implementing policies, procedures, guidelines, and best practices in the archival field. She currently serves as President of the Academy of Certified Archivists and Co-Manager of the Society of American Archivists' Digital Archives Specialist (DAS) Exam. Amanda Boczar is Special Collections Operations Manager at the University of South Florida Libraries Tampa campus. Amanda holds a Ph.D. in History with over 12 years of experience in higher education, and joined the library in 2019. She was responsible for the migration to ArchivesSpace, and supervised student and employee training through the process. Ana Temkina is a student assistant at USF Libraries Tampa campus, Special Collections. She received her bachelor's degree in Library and Information Science, Children?s Literature track, from St. Petersburg State University of Culture and Arts, Russia. At USF she is doing her MA in Applied Anthropology and will soon graduate to continue her academic path at the University of Kentucky. Library work remains one of her great passions. Who should attend: Anyone interested in implementing ArchivesSpace, developing a migration plan or using ArchivesSpace remotely. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29066 bytes Desc: image001.jpg URL: From Corey.Schmidt at uga.edu Mon Jun 14 12:13:28 2021 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Mon, 14 Jun 2021 16:13:28 +0000 Subject: [Archivesspace_Users_Group] Finding Aid Discovery Platform Survey In-Reply-To: References: Message-ID: Dear all, This is a reminder asking anyone who hasn't completed the Finding Aid Discovery Platform Survey who would like to participate to please do so by this Friday, June 18. If you have already responded, thank you for your participation. The survey takes around 10 to 15 minutes to complete and all information will remain confidential. The data may be shared with the larger community after the survey is completed. If you have any questions about the survey, please contact the ArchivesSpace Project Manager at the University of Georgia Special Collections Libraries, Corey Schmidt (Corey.Schmidt at uga.edu). Again, thank you for your participation! Here is the link to the survey: https://forms.gle/azChKrtqJ1qG81tMA Sincerely, Corey Corey Schmidt Special Collections Libraries | ArchivesSpace Project Manager 706-542-8151 | Corey.Schmidt at uga.edu [University of Georgia] ________________________________ From: Corey Schmidt Sent: Wednesday, June 2, 2021 3:00 PM To: Archivesspace Users Group Subject: Finding Aid Discovery Platform Survey Dear all, We here at the University of Georgia are interested in how users of ArchivesSpace are making their finding aids available online. This short, 10-to-15-minute survey asks about what discovery platform your organization/institution uses and how you have fit it to your needs. A discovery platform is defined as a web application designed specifically for sharing finding aids online to allow users to search and browse them. Some examples of discovery platforms include the ArchivesSpace PUI (Public User Interface), ArcLight, and XTF (eXtensible Text Framework). The data will be aggregated and confidential and we will not be collecting emails. We may share the results with the community, but if you feel uncomfortable answering a question, you are free to skip it. Please try to complete the survey by June 18. If you have any questions about the survey, please contact the ArchivesSpace Project Manager at the University of Georgia Special Collections Libraries, Corey Schmidt (Corey.Schmidt at uga.edu). Thank you for your participation! Here is the link to the survey: https://forms.gle/azChKrtqJ1qG81tMA Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdysonsm at utk.edu Mon Jun 14 15:00:36 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Mon, 14 Jun 2021 19:00:36 +0000 Subject: [Archivesspace_Users_Group] logrotate and "binary" logs Message-ID: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> Hi all - I recently setup logrotate according to the helpful blurb in the tech- docs[1], which has been great for our disk usage but seems to have introduced a change in the log file's `file` type.? Before logrotate, we had $ file archivesspace.out aspace-log.out: ASCII text, with very long lines and now with logrotate in play, we have $ file as-log.out as-log.out: data which causes all sorts of trouble if I want to do anything other than tail a log :). I guess I was hoping someone may a suggestion or two about how to approach this, either from the logrotate side or perhaps using another utility to either modify the `file` metadata or parse the binary format to something greppable? Thanks for any advice you can share. My searching hasn't panned out. Best, Bridger [1] https://archivesspace.github.io/tech-docs/administration/logrotate.html [2] my config: archivesspace/logs/archivesspace.out { daily rotate 7 compress notifempty missingok copytruncate } From blake.carver at lyrasis.org Mon Jun 14 15:18:05 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 14 Jun 2021 19:18:05 +0000 Subject: [Archivesspace_Users_Group] logrotate and "binary" logs In-Reply-To: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> References: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> Message-ID: archivesspace.out should for sure be "ASCII text, with very long lines" If it's something else, there's something wrong somewhere. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dyson-Smith, Bridger Sent: Monday, June 14, 2021 3:00 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] logrotate and "binary" logs Hi all - I recently setup logrotate according to the helpful blurb in the tech- docs[1], which has been great for our disk usage but seems to have introduced a change in the log file's `file` type. Before logrotate, we had $ file archivesspace.out aspace-log.out: ASCII text, with very long lines and now with logrotate in play, we have $ file as-log.out as-log.out: data which causes all sorts of trouble if I want to do anything other than tail a log :). I guess I was hoping someone may a suggestion or two about how to approach this, either from the logrotate side or perhaps using another utility to either modify the `file` metadata or parse the binary format to something greppable? Thanks for any advice you can share. My searching hasn't panned out. Best, Bridger [1] https://archivesspace.github.io/tech-docs/administration/logrotate.html [2] my config: archivesspace/logs/archivesspace.out { daily rotate 7 compress notifempty missingok copytruncate } _______________________________________________ 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 Scott.Renton at ed.ac.uk Tue Jun 15 04:41:20 2021 From: Scott.Renton at ed.ac.uk (RENTON Scott) Date: Tue, 15 Jun 2021 08:41:20 +0000 Subject: [Archivesspace_Users_Group] Date concatenation In-Reply-To: References: , Message-ID: Thanks very much Lora. I will feed that back to our archivists- I think they will be happy enough now they know what it is. Cheers Scott ========== Scott Renton Digital Library Development & Systems Floor F East Argyle House 515219 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Lora Woodford Sent: 10 June 2021 18:49 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Date concatenation This email was sent to you by someone outside the University. You should only click on links or attachments if you are certain that the email is genuine and the content is safe. Hi Scott, This was the result of a bugfix request that was implemented and delivered as part of the 2.8.0 release. Here?s the JIRA ticket requesting that functionality be added to the core of ArchivesSpace: https://archivesspace.atlassian.net/browse/ANW-172 It was not implemented as a configurable feature as the ticket described it as a bug that should be remedied for all users. Namely, it was deemed a mistake/oversight that only the first of multiple provided dates was being added to the display string. As far as locally changing things on your end by writing a custom plugin, that would likely be a fairly major undertaking (that might not ultimately be successful) as the change to the display string was made at the model level. I wonder whether anyone else has considered doing that? Best, Lora Woodford From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of RENTON Scott Date: Thursday, June 10, 2021 at 12:26 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Date concatenation Hi folks, I posted this one to the Google Group, but nobody took the bait. I hope it's ok for me to send to the listserv. I wondered if anyone knew about configuring the concatenation of dates to titles in the frontend and pui? We have noticed since moving to v2.8.1 that items with more than one date item are getting multiple dates appended, and the curators of these collections find it a bit unwieldy and are asking if we can turn it off. In v2.6, they were only getting the first one appended- has there been a change to the logic? I couldn't see anything in config which would help with this, but I know that if it's in the code any such change will affect the whole site, so those curators that like having one date appended may lose that functionality. Thanks Scott ========== Scott Renton Digital Library Development & Systems Floor F East Argyle House 515219 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th? ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Tue Jun 15 04:42:56 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Tue, 15 Jun 2021 08:42:56 +0000 Subject: [Archivesspace_Users_Group] logrotate and "binary" logs In-Reply-To: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> References: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> Message-ID: $ file as-log.out as-log.out: data This looks like the file utility was unable to determine the type of as-log.out. As it should normally be able to identify all types emitted by logrotate, this suggests to me that the actual file it was ran on is corrupt. archivesspace/logs/archivesspace.out { This may be a result of pasting, but AFAIK logrotate requires an absolute path. compress This will default to gzip compression, with an extension '..gz' added to the filename. Normally, you would use the z* utilities (zcat, zless, zmore, zgrep, zdiff) to handle rotated logs as these will also handle uncompressed streams. I note that the filename above does not have the usual extension, but this may also be a result of pasting/obfuscation. You should be able to run logrotate -d and see all actions that would be performed according to configfile. p -------------- next part -------------- An HTML attachment was scrubbed... URL: From schanzme at msu.edu Tue Jun 15 10:01:34 2021 From: schanzme at msu.edu (Schanz, Megan) Date: Tue, 15 Jun 2021 14:01:34 +0000 Subject: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site Message-ID: Hi everyone, We are running across an error loading a digital object on the public front end site (but does load and function fine on the backend staff side). Nothing immediately looks out of place with that digital object record as compared to others. I tried re-saving the record to force a reindex of that object, which didn't change the error. Any help or suggestions would helpful! The error users see is the typical "something went wrong" message. This is the error we are seeing in our logs when attempting to load that page: I, [2021-06-15T13:28:26.735417 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Started GET "/repositories/2/digital_objects/3342" for [IP] at 2021-06-15 13:28:26 +0000 I, [2021-06-15T13:28:26.737099 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Processing by ObjectsController#show as HTML I, [2021-06-15T13:28:26.737218 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Parameters: {"repo_slug"=>"2", "obj_type"=>"digital_objects", "slug_or_id"=>"3342"} I, [2021-06-15T13:28:26.782973 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendering objects/show.html.erb within layouts/application I, [2021-06-15T13:28:26.783870 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_idbadge.html.erb (0.3ms) I, [2021-06-15T13:28:26.786098 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_cite_page_action.html.erb (1.8ms) I, [2021-06-15T13:28:26.811105 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_request_hiddens.html.erb (24.3ms) I, [2021-06-15T13:28:26.812185 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_request_page_action.html.erb (25.6ms) I, [2021-06-15T13:28:26.812858 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_staff_link_action.html.erb (0.2ms) I, [2021-06-15T13:28:26.813104 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_page_actions.html.erb (28.9ms) I, [2021-06-15T13:28:26.813776 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_breadcrumbs.html.erb (0.3ms) I, [2021-06-15T13:28:26.814377 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_digital.html.erb (0.3ms) I, [2021-06-15T13:28:26.815070 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_dates.html.erb (0.1ms) I, [2021-06-15T13:28:26.816935 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_multi_notes.html.erb (0.0ms) I, [2021-06-15T13:28:26.831346 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered digital_objects/_linked_instances.html.erb (14.0ms) I, [2021-06-15T13:28:26.832042 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.832604 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_present_list_external_docs.html.erb (0.1ms) I, [2021-06-15T13:28:26.833089 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.834073 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered repositories/_full_repo.html.erb (0.4ms) I, [2021-06-15T13:28:26.834370 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered repositories/_repository_details.html.erb (0.9ms) I, [2021-06-15T13:28:26.834845 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.836665 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_record_innards.html.erb (21.9ms) I, [2021-06-15T13:28:26.850905 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered objects/show.html.erb within layouts/application (67.7ms) I, [2021-06-15T13:28:26.852604 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Completed 500 Internal Server Error in 115ms F, [2021-06-15T13:28:26.854132 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] F, [2021-06-15T13:28:26.854269 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] ActionView::Template::Error (undefined method `resource_uri' for #): F, [2021-06-15T13:28:26.854696 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] 31: end [2d67df51-6e7d-4007-b293-a38c457127ed] 32: %> [2d67df51-6e7d-4007-b293-a38c457127ed] 33: <% if AppConfig[:pui_search_collection_from_archival_objects] %> [2d67df51-6e7d-4007-b293-a38c457127ed] 34: <%= render partial: 'shared/search_collection_form', :locals => {:resource_uri => @result.resource_uri, :action_text => "#{t('actions.search_in', :type => t('resource._singular'))}"} %> [2d67df51-6e7d-4007-b293-a38c457127ed] 35: <% end %> [2d67df51-6e7d-4007-b293-a38c457127ed] 36: <%= render partial: 'shared/children_tree', :locals => {:heading_text => heading_text, :root_node_uri => @result.root_node_uri, :current_node_uri => @result.uri} %> [2d67df51-6e7d-4007-b293-a38c457127ed] 37: F, [2021-06-15T13:28:26.854867 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] F, [2021-06-15T13:28:26.855039 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] app/views/objects/show.html.erb:34:in `_app_views_objects_show_html_erb___1370737355_3282' [2d67df51-6e7d-4007-b293-a38c457127ed] app/controllers/objects_controller.rb:116:in `show' And here is the database record: MariaDB [archivesspace]> select * from digital_object where id = 3342\G *************************** 1. row *************************** id: 3342 lock_version: 13 json_schema_version: 1 repo_id: 2 digital_object_id: 483a5879-ffeb-4418-80ba-a96bf3dfd133 title: Lacrosse Photographs 2013 level_id: 271 digital_object_type_id: NULL publish: 1 restrictions: 0 system_generated: 0 created_by: [user] last_modified_by: [user] create_time: 2020-12-21 20:35:35 system_mtime: 2021-06-15 13:20:52 user_mtime: 2021-06-15 13:20:52 suppressed: 0 slug: NULL is_slug_auto: 0 Thank you! - Megan _____________________________________ Megan Schanz Application Developer & Systems Administrator Michigan State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Jun 15 11:00:38 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 15 Jun 2021 16:00:38 +0100 Subject: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site In-Reply-To: References: Message-ID: <596f861a-1847-90b4-8c5d-950cecc1cb98@bodleian.ox.ac.uk> I'm afraid this appears to be a bug in a contribution I made . It occurs when both of the following conditions are met: 1. AppConfig[:pui_search_collection_from_archival_objects] is set to true in config.rb (by default it is false) 2. The digital object has one or more child digital object components Is the case, and which version of ArchivesSpace are you running? Andrew. On 15/06/2021 15:01, Schanz, Megan wrote: > Hi everyone, > > We are running across an error loading a digital object on the public > front end site (but does load and function fine on the backend staff > side). Nothing immediately looks out of place with that digital object > record as compared to others. I tried re-saving the record to force a > reindex of that object, which didn't change the error. Any help or > suggestions would helpful! > > The error users see is the typical "something went wrong" message. > This is the error we are seeing in our logs when attempting to load > that page: > > I, [2021-06-15T13:28:26.735417 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] Started GET > "/repositories/2/digital_objects/3342" for [IP] at 2021-06-15 13:28:26 > +0000 > I, [2021-06-15T13:28:26.737099 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] Processing by > ObjectsController#show as HTML > I, [2021-06-15T13:28:26.737218 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Parameters: > {"repo_slug"=>"2", "obj_type"=>"digital_objects", "slug_or_id"=>"3342"} > I, [2021-06-15T13:28:26.782973 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendering > objects/show.html.erb within layouts/application > I, [2021-06-15T13:28:26.783870 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_idbadge.html.erb (0.3ms) > I, [2021-06-15T13:28:26.786098 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_cite_page_action.html.erb (1.8ms) > I, [2021-06-15T13:28:26.811105 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_request_hiddens.html.erb (24.3ms) > I, [2021-06-15T13:28:26.812185 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_request_page_action.html.erb (25.6ms) > I, [2021-06-15T13:28:26.812858 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_staff_link_action.html.erb (0.2ms) > I, [2021-06-15T13:28:26.813104 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_page_actions.html.erb (28.9ms) > I, [2021-06-15T13:28:26.813776 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_breadcrumbs.html.erb (0.3ms) > I, [2021-06-15T13:28:26.814377 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_digital.html.erb (0.3ms) > I, [2021-06-15T13:28:26.815070 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_dates.html.erb (0.1ms) > I, [2021-06-15T13:28:26.816935 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_multi_notes.html.erb (0.0ms) > I, [2021-06-15T13:28:26.831346 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > digital_objects/_linked_instances.html.erb (14.0ms) > I, [2021-06-15T13:28:26.832042 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_accordion_panel.html.erb (0.1ms) > I, [2021-06-15T13:28:26.832604 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_present_list_external_docs.html.erb (0.1ms) > I, [2021-06-15T13:28:26.833089 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_accordion_panel.html.erb (0.1ms) > I, [2021-06-15T13:28:26.834073 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > repositories/_full_repo.html.erb (0.4ms) > I, [2021-06-15T13:28:26.834370 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > repositories/_repository_details.html.erb (0.9ms) > I, [2021-06-15T13:28:26.834845 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_accordion_panel.html.erb (0.1ms) > I, [2021-06-15T13:28:26.836665 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > shared/_record_innards.html.erb (21.9ms) > I, [2021-06-15T13:28:26.850905 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered > objects/show.html.erb within layouts/application (67.7ms) > I, [2021-06-15T13:28:26.852604 #57] ?INFO -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] Completed 500 Internal Server > Error in 115ms > F, [2021-06-15T13:28:26.854132 #57] FATAL -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] > F, [2021-06-15T13:28:26.854269 #57] FATAL -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ActionView::Template::Error > (undefined method `resource_uri' for #): > F, [2021-06-15T13:28:26.854696 #57] FATAL -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 31: ? ? ? ? end > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 32: ? ? ? %> > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 33: ? ? ? <% if > AppConfig[:pui_search_collection_from_archival_objects] %> > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 34: <%= render partial: > 'shared/search_collection_form', :locals => {:resource_uri => > @result.resource_uri, :action_text => "#{t('actions.search_in', :type > => t('resource._singular'))}"} %> > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 35: ? ? ? <% end %> > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 36: ? ? ? <%= render > partial: 'shared/children_tree', :locals => {:heading_text => > heading_text, :root_node_uri => @result.root_node_uri, > :current_node_uri => @result.uri} %> > [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 37: > F, [2021-06-15T13:28:26.854867 #57] FATAL -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] > F, [2021-06-15T13:28:26.855039 #57] FATAL -- : > [2d67df51-6e7d-4007-b293-a38c457127ed] > app/views/objects/show.html.erb:34:in > `_app_views_objects_show_html_erb___1370737355_3282' > [2d67df51-6e7d-4007-b293-a38c457127ed] > app/controllers/objects_controller.rb:116:in `show' > > And here is the database record: > > MariaDB [archivesspace]> select * from digital_object where id = 3342\G > *************************** 1. row *************************** > id: 3342 > lock_version: 13 > json_schema_version: 1 > repo_id: 2 > digital_object_id: 483a5879-ffeb-4418-80ba-a96bf3dfd133 > title: Lacrosse Photographs 2013 > level_id: 271 > digital_object_type_id: NULL > publish: 1 > restrictions: 0 > system_generated: 0 > created_by: [user] > last_modified_by: [user] > create_time: 2020-12-21 20:35:35 > system_mtime: 2021-06-15 13:20:52 > user_mtime: 2021-06-15 13:20:52 > suppressed: 0 > slug: NULL > is_slug_auto: 0 > > > Thank you! > > - Megan > > > _____________________________________ > > Megan Schanz > Application Developer & Systems Administrator > Michigan State University Libraries > > _______________________________________________ > 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 schanzme at msu.edu Tue Jun 15 11:18:13 2021 From: schanzme at msu.edu (Schanz, Megan) Date: Tue, 15 Jun 2021 15:18:13 +0000 Subject: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site In-Reply-To: <596f861a-1847-90b4-8c5d-950cecc1cb98@bodleian.ox.ac.uk> References: , <596f861a-1847-90b4-8c5d-950cecc1cb98@bodleian.ox.ac.uk> Message-ID: Oh interesting; both of those conditions exist for that digital object. We are running v2.8.1 right now. We do plan on upgrading in the near future if it is already fixed in newer versions. - Megan ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Tuesday, June 15, 2021 11:00 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site I'm afraid this appears to be a bug in a contribution I made. It occurs when both of the following conditions are met: 1. AppConfig[:pui_search_collection_from_archival_objects] is set to true in config.rb (by default it is false) 2. The digital object has one or more child digital object components Is the case, and which version of ArchivesSpace are you running? Andrew. On 15/06/2021 15:01, Schanz, Megan wrote: Hi everyone, We are running across an error loading a digital object on the public front end site (but does load and function fine on the backend staff side). Nothing immediately looks out of place with that digital object record as compared to others. I tried re-saving the record to force a reindex of that object, which didn't change the error. Any help or suggestions would helpful! The error users see is the typical "something went wrong" message. This is the error we are seeing in our logs when attempting to load that page: I, [2021-06-15T13:28:26.735417 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Started GET "/repositories/2/digital_objects/3342" for [IP] at 2021-06-15 13:28:26 +0000 I, [2021-06-15T13:28:26.737099 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Processing by ObjectsController#show as HTML I, [2021-06-15T13:28:26.737218 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Parameters: {"repo_slug"=>"2", "obj_type"=>"digital_objects", "slug_or_id"=>"3342"} I, [2021-06-15T13:28:26.782973 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendering objects/show.html.erb within layouts/application I, [2021-06-15T13:28:26.783870 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_idbadge.html.erb (0.3ms) I, [2021-06-15T13:28:26.786098 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_cite_page_action.html.erb (1.8ms) I, [2021-06-15T13:28:26.811105 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_request_hiddens.html.erb (24.3ms) I, [2021-06-15T13:28:26.812185 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_request_page_action.html.erb (25.6ms) I, [2021-06-15T13:28:26.812858 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_staff_link_action.html.erb (0.2ms) I, [2021-06-15T13:28:26.813104 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_page_actions.html.erb (28.9ms) I, [2021-06-15T13:28:26.813776 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_breadcrumbs.html.erb (0.3ms) I, [2021-06-15T13:28:26.814377 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_digital.html.erb (0.3ms) I, [2021-06-15T13:28:26.815070 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_dates.html.erb (0.1ms) I, [2021-06-15T13:28:26.816935 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_multi_notes.html.erb (0.0ms) I, [2021-06-15T13:28:26.831346 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered digital_objects/_linked_instances.html.erb (14.0ms) I, [2021-06-15T13:28:26.832042 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.832604 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_present_list_external_docs.html.erb (0.1ms) I, [2021-06-15T13:28:26.833089 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.834073 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered repositories/_full_repo.html.erb (0.4ms) I, [2021-06-15T13:28:26.834370 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered repositories/_repository_details.html.erb (0.9ms) I, [2021-06-15T13:28:26.834845 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.836665 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_record_innards.html.erb (21.9ms) I, [2021-06-15T13:28:26.850905 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered objects/show.html.erb within layouts/application (67.7ms) I, [2021-06-15T13:28:26.852604 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Completed 500 Internal Server Error in 115ms F, [2021-06-15T13:28:26.854132 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] F, [2021-06-15T13:28:26.854269 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] ActionView::Template::Error (undefined method `resource_uri' for #): F, [2021-06-15T13:28:26.854696 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] 31: end [2d67df51-6e7d-4007-b293-a38c457127ed] 32: %> [2d67df51-6e7d-4007-b293-a38c457127ed] 33: <% if AppConfig[:pui_search_collection_from_archival_objects] %> [2d67df51-6e7d-4007-b293-a38c457127ed] 34: <%= render partial: 'shared/search_collection_form', :locals => {:resource_uri => @result.resource_uri, :action_text => "#{t('actions.search_in', :type => t('resource._singular'))}"} %> [2d67df51-6e7d-4007-b293-a38c457127ed] 35: <% end %> [2d67df51-6e7d-4007-b293-a38c457127ed] 36: <%= render partial: 'shared/children_tree', :locals => {:heading_text => heading_text, :root_node_uri => @result.root_node_uri, :current_node_uri => @result.uri} %> [2d67df51-6e7d-4007-b293-a38c457127ed] 37: F, [2021-06-15T13:28:26.854867 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] F, [2021-06-15T13:28:26.855039 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] app/views/objects/show.html.erb:34:in `_app_views_objects_show_html_erb___1370737355_3282' [2d67df51-6e7d-4007-b293-a38c457127ed] app/controllers/objects_controller.rb:116:in `show' And here is the database record: MariaDB [archivesspace]> select * from digital_object where id = 3342\G *************************** 1. row *************************** id: 3342 lock_version: 13 json_schema_version: 1 repo_id: 2 digital_object_id: 483a5879-ffeb-4418-80ba-a96bf3dfd133 title: Lacrosse Photographs 2013 level_id: 271 digital_object_type_id: NULL publish: 1 restrictions: 0 system_generated: 0 created_by: [user] last_modified_by: [user] create_time: 2020-12-21 20:35:35 system_mtime: 2021-06-15 13:20:52 user_mtime: 2021-06-15 13:20:52 suppressed: 0 slug: NULL is_slug_auto: 0 Thank you! - Megan _____________________________________ Megan Schanz Application Developer & Systems Administrator Michigan State University Libraries _______________________________________________ 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 andrew.morrison at bodleian.ox.ac.uk Tue Jun 15 12:22:03 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 15 Jun 2021 17:22:03 +0100 Subject: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site In-Reply-To: References: <596f861a-1847-90b4-8c5d-950cecc1cb98@bodleian.ox.ac.uk> Message-ID: I'm sorry to have caused this problem. I have just submitted a fix but it is up to the ArchivesSpace Program Team to decide whether and how to release it. The fix is in a single template. You could download it from here... https://raw.githubusercontent.com/bodleian/archivesspace/fix-pui-digital-object-bug/public/app/views/objects/show.html.erb ...and put it in a local plug-in in your system (in public/views/objects). That template hasn't been changed since I introduced the bug in 2.8.0 so, for any release since, it will override the core template and fix the bug. Let me know if you need any help with that. Andrew. On 15/06/2021 16:18, Schanz, Megan wrote: > Oh interesting; both of those conditions exist for that digital > object. We are running v2.8.1 right now. We do plan on upgrading in > the near future if it is already fixed in newer versions. > > - Megan > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Andrew Morrison > *Sent:* Tuesday, June 15, 2021 11:00 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > > *Subject:* Re: [Archivesspace_Users_Group] Error viewing a digital > object from the frontend site > > I'm afraid this appears to be a bug in a contribution I made > . > It occurs when both of the following conditions are met: > > > 1. AppConfig[:pui_search_collection_from_archival_objects] is set to > true in config.rb (by default it is false) > > 2. The digital object has one or more child digital object components > > > Is the case, and which version of ArchivesSpace are you running? > > > Andrew. > > > > On 15/06/2021 15:01, Schanz, Megan wrote: >> Hi everyone, >> >> We are running across an error loading a digital object on the public >> front end site (but does load and function fine on the backend staff >> side). Nothing immediately looks out of place with that digital >> object record as compared to others. I tried re-saving the record to >> force a reindex of that object, which didn't change the error. Any >> help or suggestions would helpful! >> >> The error users see is the typical "something went wrong" message. >> This is the error we are seeing in our logs when attempting to load >> that page: >> >> I, [2021-06-15T13:28:26.735417 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] Started GET >> "/repositories/2/digital_objects/3342" for [IP] at 2021-06-15 >> 13:28:26 +0000 >> I, [2021-06-15T13:28:26.737099 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] Processing by >> ObjectsController#show as HTML >> I, [2021-06-15T13:28:26.737218 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Parameters: >> {"repo_slug"=>"2", "obj_type"=>"digital_objects", "slug_or_id"=>"3342"} >> I, [2021-06-15T13:28:26.782973 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendering >> objects/show.html.erb within layouts/application >> I, [2021-06-15T13:28:26.783870 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_idbadge.html.erb (0.3ms) >> I, [2021-06-15T13:28:26.786098 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_cite_page_action.html.erb (1.8ms) >> I, [2021-06-15T13:28:26.811105 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_request_hiddens.html.erb (24.3ms) >> I, [2021-06-15T13:28:26.812185 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_request_page_action.html.erb (25.6ms) >> I, [2021-06-15T13:28:26.812858 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_staff_link_action.html.erb (0.2ms) >> I, [2021-06-15T13:28:26.813104 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_page_actions.html.erb (28.9ms) >> I, [2021-06-15T13:28:26.813776 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_breadcrumbs.html.erb (0.3ms) >> I, [2021-06-15T13:28:26.814377 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_digital.html.erb (0.3ms) >> I, [2021-06-15T13:28:26.815070 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_dates.html.erb (0.1ms) >> I, [2021-06-15T13:28:26.816935 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_multi_notes.html.erb (0.0ms) >> I, [2021-06-15T13:28:26.831346 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> digital_objects/_linked_instances.html.erb (14.0ms) >> I, [2021-06-15T13:28:26.832042 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_accordion_panel.html.erb (0.1ms) >> I, [2021-06-15T13:28:26.832604 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_present_list_external_docs.html.erb (0.1ms) >> I, [2021-06-15T13:28:26.833089 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_accordion_panel.html.erb (0.1ms) >> I, [2021-06-15T13:28:26.834073 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> repositories/_full_repo.html.erb (0.4ms) >> I, [2021-06-15T13:28:26.834370 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> repositories/_repository_details.html.erb (0.9ms) >> I, [2021-06-15T13:28:26.834845 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_accordion_panel.html.erb (0.1ms) >> I, [2021-06-15T13:28:26.836665 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> shared/_record_innards.html.erb (21.9ms) >> I, [2021-06-15T13:28:26.850905 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? Rendered >> objects/show.html.erb within layouts/application (67.7ms) >> I, [2021-06-15T13:28:26.852604 #57] ?INFO -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] Completed 500 Internal Server >> Error in 115ms >> F, [2021-06-15T13:28:26.854132 #57] FATAL -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] >> F, [2021-06-15T13:28:26.854269 #57] FATAL -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ActionView::Template::Error >> (undefined method `resource_uri' for #): >> F, [2021-06-15T13:28:26.854696 #57] FATAL -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 31: ? ? ? ? end >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 32: %> >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 33: <% if >> AppConfig[:pui_search_collection_from_archival_objects] %> >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 34: <%= render partial: >> 'shared/search_collection_form', :locals => {:resource_uri => >> @result.resource_uri, :action_text => "#{t('actions.search_in', :type >> => t('resource._singular'))}"} %> >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 35: <% end %> >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 36: <%= render partial: >> 'shared/children_tree', :locals => {:heading_text => heading_text, >> :root_node_uri => @result.root_node_uri, :current_node_uri => >> @result.uri} %> >> [2d67df51-6e7d-4007-b293-a38c457127ed] ? ? 37: >> F, [2021-06-15T13:28:26.854867 #57] FATAL -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] >> F, [2021-06-15T13:28:26.855039 #57] FATAL -- : >> [2d67df51-6e7d-4007-b293-a38c457127ed] >> app/views/objects/show.html.erb:34:in >> `_app_views_objects_show_html_erb___1370737355_3282' >> [2d67df51-6e7d-4007-b293-a38c457127ed] >> app/controllers/objects_controller.rb:116:in `show' >> >> And here is the database record: >> >> MariaDB [archivesspace]> select * from digital_object where id = 3342\G >> *************************** 1. row *************************** >> id: 3342 >> lock_version: 13 >> json_schema_version: 1 >> repo_id: 2 >> digital_object_id: 483a5879-ffeb-4418-80ba-a96bf3dfd133 >> title: Lacrosse Photographs 2013 >> level_id: 271 >> digital_object_type_id: NULL >> publish: 1 >> restrictions: 0 >> system_generated: 0 >> created_by: [user] >> last_modified_by: [user] >> create_time: 2020-12-21 20:35:35 >> system_mtime: 2021-06-15 13:20:52 >> user_mtime: 2021-06-15 13:20:52 >> suppressed: 0 >> slug: NULL >> is_slug_auto: 0 >> >> >> Thank you! >> >> - Megan >> >> >> _____________________________________ >> >> Megan Schanz >> Application Developer & Systems Administrator >> Michigan State University Libraries >> >> _______________________________________________ >> 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 schanzme at msu.edu Tue Jun 15 13:55:18 2021 From: schanzme at msu.edu (Schanz, Megan) Date: Tue, 15 Jun 2021 17:55:18 +0000 Subject: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site In-Reply-To: References: <596f861a-1847-90b4-8c5d-950cecc1cb98@bodleian.ox.ac.uk> , Message-ID: Thank you for your prompt help; that did indeed resolve our issue! - Megan ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Tuesday, June 15, 2021 12:22 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site I'm sorry to have caused this problem. I have just submitted a fix but it is up to the ArchivesSpace Program Team to decide whether and how to release it. The fix is in a single template. You could download it from here... https://raw.githubusercontent.com/bodleian/archivesspace/fix-pui-digital-object-bug/public/app/views/objects/show.html.erb ...and put it in a local plug-in in your system (in public/views/objects). That template hasn't been changed since I introduced the bug in 2.8.0 so, for any release since, it will override the core template and fix the bug. Let me know if you need any help with that. Andrew. On 15/06/2021 16:18, Schanz, Megan wrote: Oh interesting; both of those conditions exist for that digital object. We are running v2.8.1 right now. We do plan on upgrading in the near future if it is already fixed in newer versions. - Megan ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Tuesday, June 15, 2021 11:00 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Error viewing a digital object from the frontend site I'm afraid this appears to be a bug in a contribution I made. It occurs when both of the following conditions are met: 1. AppConfig[:pui_search_collection_from_archival_objects] is set to true in config.rb (by default it is false) 2. The digital object has one or more child digital object components Is the case, and which version of ArchivesSpace are you running? Andrew. On 15/06/2021 15:01, Schanz, Megan wrote: Hi everyone, We are running across an error loading a digital object on the public front end site (but does load and function fine on the backend staff side). Nothing immediately looks out of place with that digital object record as compared to others. I tried re-saving the record to force a reindex of that object, which didn't change the error. Any help or suggestions would helpful! The error users see is the typical "something went wrong" message. This is the error we are seeing in our logs when attempting to load that page: I, [2021-06-15T13:28:26.735417 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Started GET "/repositories/2/digital_objects/3342" for [IP] at 2021-06-15 13:28:26 +0000 I, [2021-06-15T13:28:26.737099 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Processing by ObjectsController#show as HTML I, [2021-06-15T13:28:26.737218 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Parameters: {"repo_slug"=>"2", "obj_type"=>"digital_objects", "slug_or_id"=>"3342"} I, [2021-06-15T13:28:26.782973 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendering objects/show.html.erb within layouts/application I, [2021-06-15T13:28:26.783870 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_idbadge.html.erb (0.3ms) I, [2021-06-15T13:28:26.786098 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_cite_page_action.html.erb (1.8ms) I, [2021-06-15T13:28:26.811105 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_request_hiddens.html.erb (24.3ms) I, [2021-06-15T13:28:26.812185 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_request_page_action.html.erb (25.6ms) I, [2021-06-15T13:28:26.812858 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_staff_link_action.html.erb (0.2ms) I, [2021-06-15T13:28:26.813104 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_page_actions.html.erb (28.9ms) I, [2021-06-15T13:28:26.813776 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_breadcrumbs.html.erb (0.3ms) I, [2021-06-15T13:28:26.814377 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_digital.html.erb (0.3ms) I, [2021-06-15T13:28:26.815070 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_dates.html.erb (0.1ms) I, [2021-06-15T13:28:26.816935 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_multi_notes.html.erb (0.0ms) I, [2021-06-15T13:28:26.831346 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered digital_objects/_linked_instances.html.erb (14.0ms) I, [2021-06-15T13:28:26.832042 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.832604 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_present_list_external_docs.html.erb (0.1ms) I, [2021-06-15T13:28:26.833089 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.834073 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered repositories/_full_repo.html.erb (0.4ms) I, [2021-06-15T13:28:26.834370 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered repositories/_repository_details.html.erb (0.9ms) I, [2021-06-15T13:28:26.834845 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_accordion_panel.html.erb (0.1ms) I, [2021-06-15T13:28:26.836665 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered shared/_record_innards.html.erb (21.9ms) I, [2021-06-15T13:28:26.850905 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Rendered objects/show.html.erb within layouts/application (67.7ms) I, [2021-06-15T13:28:26.852604 #57] INFO -- : [2d67df51-6e7d-4007-b293-a38c457127ed] Completed 500 Internal Server Error in 115ms F, [2021-06-15T13:28:26.854132 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] F, [2021-06-15T13:28:26.854269 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] ActionView::Template::Error (undefined method `resource_uri' for #): F, [2021-06-15T13:28:26.854696 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] 31: end [2d67df51-6e7d-4007-b293-a38c457127ed] 32: %> [2d67df51-6e7d-4007-b293-a38c457127ed] 33: <% if AppConfig[:pui_search_collection_from_archival_objects] %> [2d67df51-6e7d-4007-b293-a38c457127ed] 34: <%= render partial: 'shared/search_collection_form', :locals => {:resource_uri => @result.resource_uri, :action_text => "#{t('actions.search_in', :type => t('resource._singular'))}"} %> [2d67df51-6e7d-4007-b293-a38c457127ed] 35: <% end %> [2d67df51-6e7d-4007-b293-a38c457127ed] 36: <%= render partial: 'shared/children_tree', :locals => {:heading_text => heading_text, :root_node_uri => @result.root_node_uri, :current_node_uri => @result.uri} %> [2d67df51-6e7d-4007-b293-a38c457127ed] 37: F, [2021-06-15T13:28:26.854867 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] F, [2021-06-15T13:28:26.855039 #57] FATAL -- : [2d67df51-6e7d-4007-b293-a38c457127ed] app/views/objects/show.html.erb:34:in `_app_views_objects_show_html_erb___1370737355_3282' [2d67df51-6e7d-4007-b293-a38c457127ed] app/controllers/objects_controller.rb:116:in `show' And here is the database record: MariaDB [archivesspace]> select * from digital_object where id = 3342\G *************************** 1. row *************************** id: 3342 lock_version: 13 json_schema_version: 1 repo_id: 2 digital_object_id: 483a5879-ffeb-4418-80ba-a96bf3dfd133 title: Lacrosse Photographs 2013 level_id: 271 digital_object_type_id: NULL publish: 1 restrictions: 0 system_generated: 0 created_by: [user] last_modified_by: [user] create_time: 2020-12-21 20:35:35 system_mtime: 2021-06-15 13:20:52 user_mtime: 2021-06-15 13:20:52 suppressed: 0 slug: NULL is_slug_auto: 0 Thank you! - Megan _____________________________________ Megan Schanz Application Developer & Systems Administrator Michigan State University Libraries _______________________________________________ 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 nfitzgerald at slv.vic.gov.au Tue Jun 15 21:02:57 2021 From: nfitzgerald at slv.vic.gov.au (Neal Fitzgerald) Date: Wed, 16 Jun 2021 01:02:57 +0000 Subject: [Archivesspace_Users_Group] 2 Bug fixes for as-ead-pdf.xsl - Staff interface PDF generation Message-ID: One of our large collections has an archival object with an Index and items in the note section. This was causing the PDF generation to fail with a fatal error in the log: ValidationException: Missing attribute on fo:basic-link: Either external-destination or internal-destination must be specified. as the EAD XML contains elements which do not have an @target attribute I changed line 1106 in the linking section: to to match only those ref tags with and @target attribute and this solved the problem. This same collection had a number of digital objects with unpublished File URIs that had whitespace before and after the URI, probably from a copy and paste error or perhaps as an artifact of an import process. When the staff PDF generation was run with the 'include unpublished' box ticked the process failed with an "illegal character" message listing the first offending URI I solved this by adding a normalize-space function to the XSLT wherever I found: [slv] [https://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?9] [follow us] [SLV facebook] [SLV twitter] [SLV youtube] [SLV instagram] [Gold Winner 2018 RACV Victorian Tourism Awards] [MEA Awards 2018 National Winner] 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 Scott.Renton at ed.ac.uk Wed Jun 16 11:15:09 2021 From: Scott.Renton at ed.ac.uk (RENTON Scott) Date: Wed, 16 Jun 2021 15:15:09 +0000 Subject: [Archivesspace_Users_Group] Search API- detailed documentation? Message-ID: Hi again folks I'm wondering if anyone has any detailed documentation for the search API, with some examples. The git resource is really good, but it doesn't go that deeply into search, and I'm trying to write something for internal users interfacing with the API. Issues I'm trying to resolve most directly- chaining terms with agents, and working with dates (I can do some of this with the SOLR admin panel, but there are some differences between the syntax, and I'm falling down there). Chaining terms: Running something like this: search?type[]=archival_object&page= 1&q=language_enum_s:gla AND title:Loch AND certainty_enum_s:approximate AND agents[]:Collinson It all looks good till I get to the agents- where I get some records back which don't have that agent. Is there an easy fix there? Dates: I'd like to be able to search where a Date of Creation is greater than X but less than Y. However, as that field is in the json object returned by Search, I don't think I can logically perform that search (as I'd basically be wildcard matching a string)- unless there's a way to drill into the json? Any advice gratefully received! Thanks Scott ========== Scott Renton Digital Library Development & Systems Floor F East Argyle House 515219 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th' ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidtriebwasser at berkeley.edu Wed Jun 16 11:27:30 2021 From: davidtriebwasser at berkeley.edu (David Triebwasser) Date: Wed, 16 Jun 2021 08:27:30 -0700 Subject: [Archivesspace_Users_Group] Batch modifications of Controlled Value Lists Message-ID: We have a controlled value list (extent_extent_type) which has accumulated thousands of unused values over time. The list is now unusable in UI due to load times. We would like to remove all the values that are "Not Used." Doing this through UI is not practical, does anyone know how this would be done in batch? Or do we have to modify DB directly? Is that possible? best David -- David Triebwasser Library IT, lib.berkeley.edu 289 Doe Annex University of California, Berkeley 94720 510.982.1640 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdysonsm at utk.edu Wed Jun 16 12:19:10 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Wed, 16 Jun 2021 16:19:10 +0000 Subject: [Archivesspace_Users_Group] logrotate and "binary" logs In-Reply-To: References: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> Message-ID: <8434dc89267640d509248975e09232b28d9aada2.camel@utk.edu> Hi Peter, On Tue, 2021-06-15 at 08:42 +0000, Peter Heiner wrote: > > $ file as-log.out > > as-log.out: data > This looks like the file utility was unable to determine the type of > as-log.out. As it should normally be able to identify all types emitted > by logrotate, this suggests to me that the actual file it was ran on is > corrupt. I'm not sure about corrupt, but I won't rule it out. I'm not sure because `cat`, `tail`, and some other utilities seem to work correctly (but maybe they're more forgiving?). Thanks for the suggestion! > > archivesspace/logs/archivesspace.out { > This may be a result of pasting, but AFAIK logrotate requires an > absolute path. You're absolutely right - bad copy'pasta on my part; that should read: `/vhosts/archivesspace/logs/archivesspace.out {` > > ? ? ? ?compress > This will default to gzip compression, with an extension '..gz' > added to the filename. Normally, you would use the z* utilities (zcat, > zless, zmore, zgrep, zdiff) to handle rotated logs as these will also > handle uncompressed streams. I note that the filename above does not > have the usual extension, but this may also be a result of > pasting/obfuscation. > > /vhosts/archivesspace/logs% ls archivesspace.out archivesspace.out-20210611.gz archivesspace.out-20210613.gz archivesspace.out-20210615.gz archivesspace.out-20210610.gz archivesspace.out-20210612.gz archivesspace.out-20210614.gz archivesspace.out-20210616.gz We're good here (we use the datext in our logrotate.conf), and zgrep (thank you for the reminder!) works fine on the *.gz files. The `aspace-log.out` is a copy of log from pre-logrotate, with a different name (i.e. `cp archivesspace.out ~/aspace-out.log`). > You should be?able?to run logrotate -d and see all actions > that would be performed according to configfile. > > Sadly this doesn't seem to provide any new information: % logrotate -dv /etc/logrotate.d/archivesspace reading config file /etc/logrotate.d/archivesspace Allocating hash table for state file, size 15360 B Handling 1 logs rotating pattern: /vhosts/archivesspace/logs/archivesspace.out after 1 days (7 rotations) empty log files are not rotated, old logs are removed considering log /vhosts/archivesspace/logs/archivesspace.out log does not need rotating (log has been rotated at 2021-6-16 3:45, that is not day ago yet) > p > > Thanks again for your time, Peter - I really appreciate the help! Best, Bridger > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From ph448 at cam.ac.uk Wed Jun 16 12:44:00 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Wed, 16 Jun 2021 16:44:00 +0000 Subject: [Archivesspace_Users_Group] logrotate and "binary" logs In-Reply-To: <8434dc89267640d509248975e09232b28d9aada2.camel@utk.edu> References: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> , <8434dc89267640d509248975e09232b28d9aada2.camel@utk.edu> Message-ID: > On Tue, 2021-06-15 at 08:42 +0000, Peter Heiner wrote: > > > $ file as-log.out > > > as-log.out: data > > This looks like the file utility was unable to determine the type of > > as-log.out. As it should normally be able to identify all types emitted > > by logrotate, this suggests to me that the actual file it was ran on is > > corrupt. > I'm not sure about corrupt, but I won't rule it out. I'm not sure > because `cat`, `tail`, and some other utilities seem to work correctly > (but maybe they're more forgiving?). Thanks for the suggestion! If other utilities work well with the file, meaning for example that less or tail do not complain that the file may be binary, then I wouldn't worry too much about it. It's also possible for different contents?in the file to yield different results. Identifying log files certainly seems capricious on my laptop: [ph448 at sparkly log]$ file pacman.log pacman.log: Unicode text, UTF-8 text [ph448 at sparkly log]$ file xdm.log xdm.log: ASCII text [ph448 at sparkly log]$ file Xorg.0.log Xorg.0.log: JSON data All 3 files are plaintext logs. p From bdysonsm at utk.edu Wed Jun 16 12:47:45 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Wed, 16 Jun 2021 16:47:45 +0000 Subject: [Archivesspace_Users_Group] logrotate and "binary" logs In-Reply-To: References: <7d7a701f9d74818e85fdb5338dde34ec79e0621e.camel@utk.edu> , <8434dc89267640d509248975e09232b28d9aada2.camel@utk.edu> Message-ID: <1a8dbfd9910fc1718e2508434a79bc15a3575373.camel@utk.edu> On Wed, 2021-06-16 at 16:44 +0000, Peter Heiner wrote: > > > On Tue, 2021-06-15 at 08:42 +0000, Peter Heiner wrote: > > > > $ file as-log.out > > > > as-log.out: data > > > This looks like the file utility was unable to determine the type > > > of > > > as-log.out. As it should normally be able to identify all types > > > emitted > > > by logrotate, this suggests to me that the actual file it was ran > > > on is > > > corrupt. > > I'm not sure about corrupt, but I won't rule it out. I'm not sure > > because `cat`, `tail`, and some other utilities seem to work > > correctly > > (but maybe they're more forgiving?). Thanks for the suggestion! > > If other utilities work well with the file, meaning for example that > less > or tail do not complain that the file may be binary, then I wouldn't > worry > too much about it. > It's also possible for different contents?in the file to yield > different results. > Identifying log files certainly seems capricious on my laptop: > > [ph448 at sparkly log]$ file pacman.log > pacman.log: Unicode text, UTF-8 text > [ph448 at sparkly log]$ file xdm.log > xdm.log: ASCII text > [ph448 at sparkly log]$ file Xorg.0.log > Xorg.0.log: JSON data > > All 3 files are plaintext logs. > > Aren't computers fun? > p After some fiddling with the logrotate configuration, it looks like the default gzip compression is introducing the (apparent) binary file metadata. I've removed it for now. Thanks! Best, Bridger > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From yatsonskyn at uncw.edu Wed Jun 16 13:20:21 2021 From: yatsonskyn at uncw.edu (Yatsonsky, Nicole) Date: Wed, 16 Jun 2021 17:20:21 +0000 Subject: [Archivesspace_Users_Group] Bulk updating instances with new Top Containers linked to multiple resources Message-ID: Hi all, We are condensing several boxes from collections into multiple-collection boxes. For example, Collection# 1 Box 1, Collection #2 Box 5, and Collection# 3, Box 10 will now all be in Box A. Is there a way to simply replace all instances of Box 1 in Collection 1's resource record with Box A, maintaining any child information like folder numbers in the Instances, without having to individually click on each archival object and update the instance? There aren't enough archival objects to warrant exporting as a CSV, editing the file, and then importing it back, but just enough to sometimes make it a hassle in certain resource records. Since these new top containers are linked to multiple resource records, I'm also wary of it creating duplicates that way. Essentially it would be helpful if there was basically a way in the Top Containers page to "replace" a box with another, though I don't see anything like that, and merge isn't exactly what we're looking for. Thanks! Nicole Yatsonsky, CA Special Collections Library Specialist Randall Library UNC Wilmington 910.962.3412 "The great use of a life is to spend it for something that outlasts it." ~ William James -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Wed Jun 16 15:00:38 2021 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Wed, 16 Jun 2021 19:00:38 +0000 Subject: [Archivesspace_Users_Group] Question re: Accessions Module Data Message-ID: Good afternoon all, I had previously posted the request below and never received any answers, so I thought I'd try again. Earlier this year, I was doing some test imports into v2.8.1, specifically the accessions module. The raw data is coming in from a CSV file and the two parts of the accession #/identifier are in two separate fields. During the import, it put a " - " rather than a period between the numbers. Is there any way to change that? I detest using dashes in accession numbers and so would REALLY like to put a period in there so that the electronic record matches the labelling on my file folders. Any thoughts about how to change this? Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mary.weppler at deltacollege.edu Wed Jun 16 15:03:17 2021 From: mary.weppler at deltacollege.edu (Mary Weppler) Date: Wed, 16 Jun 2021 19:03:17 +0000 Subject: [Archivesspace_Users_Group] Question re: Accessions Module Data In-Reply-To: References: Message-ID: Hi VivianLea, I can't say why that is happening, but from a migration and digital naming convention perspective, the periods are problematic, and can cause file corruption to digital files. Mary ?Mary Weppler-Van Diver Professor, Librarian 209-954-5147 library.deltacollege.edu libguides.deltacollege.edu [cid:59449b60-7abc-4b3c-8897-8143bec4ffae][cid:e5f452e2-bd33-4fbf-8fcc-4cebadaa7982][cid:474c1f46-607a-46ab-bcc6-03fdcf6be409] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Solek, VivianLea Sent: Wednesday, June 16, 2021 12:00 PM To: ASpace Users Group (archivesspace_users_group at lyralists.lyrasis.org) ; ASpace - Small Archives List (archivesspace_small_archives_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Question re: Accessions Module Data CAUTION: This email originated from outside of Delta College. Do not click links, open attachments, or reply to emails unless you recognize the sender and know the content is safe. Good afternoon all, I had previously posted the request below and never received any answers, so I thought I?d try again. Earlier this year, I was doing some test imports into v2.8.1, specifically the accessions module. The raw data is coming in from a CSV file and the two parts of the accession #/identifier are in two separate fields. During the import, it put a ? ? ? rather than a period between the numbers. Is there any way to change that? I detest using dashes in accession numbers and so would REALLY like to put a period in there so that the electronic record matches the labelling on my file folders. Any thoughts about how to change this? Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-ba2euh2x.png Type: image/png Size: 665 bytes Desc: Outlook-ba2euh2x.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-k4aciiah.png Type: image/png Size: 708 bytes Desc: Outlook-k4aciiah.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-ygawl2sy.jpg Type: image/jpeg Size: 1472 bytes Desc: Outlook-ygawl2sy.jpg URL: From VivianLea.Solek at Kofc.Org Wed Jun 16 15:09:03 2021 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Wed, 16 Jun 2021 19:09:03 +0000 Subject: [Archivesspace_Users_Group] Question re: Accessions Module Data In-Reply-To: References: Message-ID: Hi Mary, That is true, but that shouldn?t affect data held within ASpace. The use of a period is common in museums and I know many archives that use it as well. It will be interesting to see what others can suggest. Thanks for the speedy reply! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Mary Weppler Sent: Wednesday, June 16, 2021 3:03 PM To: ASpace Users Group (archivesspace_users_group at lyralists.lyrasis.org) ; ASpace - Small Archives List (archivesspace_small_archives_users_group at lyralists.lyrasis.org) Subject: Re: [Archivesspace_Users_Group] Question re: Accessions Module Data Hi VivianLea, I can't say why that is happening, but from a migration and digital naming convention perspective, the periods are problematic, and can cause file corruption to digital files. Mary ?Mary Weppler-Van Diver Professor, Librarian 209-954-5147 library.deltacollege.edu libguides.deltacollege.edu [cid:image001.png at 01D762C1.8637E820][cid:image002.png at 01D762C1.8637E820][cid:image003.jpg at 01D762C1.8637E820] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Solek, VivianLea > Sent: Wednesday, June 16, 2021 12:00 PM To: ASpace Users Group (archivesspace_users_group at lyralists.lyrasis.org) >; ASpace - Small Archives List (archivesspace_small_archives_users_group at lyralists.lyrasis.org) > Subject: [Archivesspace_Users_Group] Question re: Accessions Module Data CAUTION: This email originated from outside of Delta College. Do not click links, open attachments, or reply to emails unless you recognize the sender and know the content is safe. Good afternoon all, I had previously posted the request below and never received any answers, so I thought I?d try again. Earlier this year, I was doing some test imports into v2.8.1, specifically the accessions module. The raw data is coming in from a CSV file and the two parts of the accession #/identifier are in two separate fields. During the import, it put a ? ? ? rather than a period between the numbers. Is there any way to change that? I detest using dashes in accession numbers and so would REALLY like to put a period in there so that the electronic record matches the labelling on my file folders. Any thoughts about how to change this? Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 665 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 708 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1472 bytes Desc: image003.jpg URL: From dmichelson at smith.edu Wed Jun 16 16:32:20 2021 From: dmichelson at smith.edu (Dan Michelson) Date: Wed, 16 Jun 2021 16:32:20 -0400 Subject: [Archivesspace_Users_Group] Bulk updating instances with new Top Containers linked to multiple resources In-Reply-To: References: Message-ID: Hi Nicole, What aspect of the merge function wouldn't meet your requirements? I haven't used it for dealing with this specific situation, but it seems like it would work perfectly. Either create a new box A to merge into or update one of the existing top container records with the appropriate data and merge the others into that one. Dan On Wed, Jun 16, 2021 at 1:20 PM Yatsonsky, Nicole wrote: > Hi all, > > > > We are condensing several boxes from collections into multiple-collection > boxes. For example, Collection# 1 Box 1, Collection #2 Box 5, and > Collection# 3, Box 10 will now all be in Box A. > > > > Is there a way to simply replace all instances of Box 1 in Collection 1?s > resource record with Box A, maintaining any child information like folder > numbers in the Instances, without having to individually click on each > archival object and update the instance? > > > > There aren?t enough archival objects to warrant exporting as a CSV, > editing the file, and then importing it back, but just enough to sometimes > make it a hassle in certain resource records. Since these new top > containers are linked to multiple resource records, I?m also wary of it > creating duplicates that way. > > > > Essentially it would be helpful if there was basically a way in the Top > Containers page to ?replace? a box with another, though I don?t see > anything like that, and merge isn?t exactly what we?re looking for. > > > > Thanks! > > > > Nicole Yatsonsky, CA > > *Special Collections Library Specialist* > > *Randall Library* > > UNC Wilmington > > 910.962.3412 > > > > *"The great use of a life is to spend it for* > > *something that outlasts it." ~ William James* > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Dan Michelson Project Manager Archivist Smith College Special Collections Special Collections is moving into the new Neilson Library and will be closed from May 31st until August 30th. All services will be temporarily unavailable. We look forward to reopening in the fall, 2021. Additional information can be found on our website . -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Jun 17 05:56:02 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 17 Jun 2021 10:56:02 +0100 Subject: [Archivesspace_Users_Group] Search API- detailed documentation? In-Reply-To: References: Message-ID: <2f12f4c0-c0a0-546e-db03-76f3ae6c45eb@bodleian.ox.ac.uk> I think the idea is that there is a lot of documentation and many examples of Solr queries available online, and that's what most people use to when searching via the API. You can build AdvancedSearch objects, which the backend will convert to Solr queries, but it is more difficult and less powerful. I'm not entirely clear what you are trying to achieve with your chained-terms query, but one thing I can suggest is that the square brackets aren't needed between agents and :Collinson. That is inside the q parameter, hence part of the the Solr query you are telling ArchivesSpace to pass on to Solr, and multi-valued fields aren't searched any differently than single-value ones in Solr queries. Dates applicable to the item (rather than the record) are indexed in a "dates" multi-valued field in Solr, but without anything to indicate which dates have the label "Creation". If, by policy, you only ever catalogue creation dates, you could do a Solr range search on that, but that would be quite restrictive on cataloguers. Searching the "json" field isn't an option (it isn't indexed for starters) but your client script could parse it and discard records that don't match your date criteria (it depends what you are doing whether that it practical.) Probably what I'd do is customize the indexer so that it populates a new, dedicated Solr index field just with creation dates. That way, after a re-index, you'd be able to do Solr range queries on that. That isn't too difficult to set up, in a plug-in, but it has an ongoing maintenance cost of having to test it still works every time you upgrade ArchivesSpace. Also, when experimenting with queries in the Solr admin interface, remember to select "edismax" because that is the query parser which ArchivesSpace uses by default. It doesn't just give more options, but also changes the way "q" and "fq" are interpreted (although not radically, in most cases.) Andrew. On 16/06/2021 16:15, RENTON Scott wrote: > Hi again folks > > > I'm wondering if anyone has any detailed documentation for the search > API, with some examples. The git resource is really good, but it > doesn't go that deeply into search, and I'm trying to write something > for internal users interfacing with the API. > > Issues I'm trying to resolve most directly- chaining terms with > agents, and working with dates (I can do some of this with the SOLR > admin panel, but there are some differences between the syntax, and > I'm falling down there). > > Chaining terms: > Running something like this: > search?type[]=archival_object&page= 1&q=language_enum_s:gla AND > title:Loch AND certainty_enum_s:approximate AND agents[]:Collinson > > It all looks good till I get to the agents- where I get some records > back which don't have that agent. Is there an easy fix there? > > Dates: > I'd like to be able to search where a Date of Creation is greater than > X but less than Y. However, as that field is in the json object > returned by Search, I don't think I can logically perform that search > (as I'd basically be wildcard matching a string)- unless there's a way > to drill into the json? > > Any advice gratefully received! > > Thanks > Scott > > ========== > > Scott Renton > > Digital Library Development & Systems > > Floor F East > > Argyle House > > 515219 > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. Is e buidheann > carthannais a th? ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, > ?ireamh cl?raidh SC005336. > > _______________________________________________ > 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 yatsonskyn at uncw.edu Thu Jun 17 10:25:49 2021 From: yatsonskyn at uncw.edu (Yatsonsky, Nicole) Date: Thu, 17 Jun 2021 14:25:49 +0000 Subject: [Archivesspace_Users_Group] Bulk updating instances with new Top Containers linked to multiple resources In-Reply-To: References: Message-ID: Hi Dan, I think I must have misplaced my brain yesterday and it took your email for me to rethink how I was looking at the merge feature. Yes, you're so right-all I have to do is add the new Top Container to one instance in each of the subsequent records after it's initially created and then can do a merge feature within the Top Containers of that collection now instead of individually. The top containers being linked to multiple resources through me for a loop at first, but it's of course that simple. Really can't thank you enough! -Nicole From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Dan Michelson Sent: Wednesday, June 16, 2021 4:32 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Bulk updating instances with new Top Containers linked to multiple resources [This email originated from outside of UNCW] Hi Nicole, What aspect of the merge function wouldn't meet your requirements? I haven't used it for dealing with this specific situation, but it seems like it would work perfectly. Either create a new box A to merge into or update one of the existing top container records with the appropriate data and merge the others into that one. Dan On Wed, Jun 16, 2021 at 1:20 PM Yatsonsky, Nicole > wrote: Hi all, We are condensing several boxes from collections into multiple-collection boxes. For example, Collection# 1 Box 1, Collection #2 Box 5, and Collection# 3, Box 10 will now all be in Box A. Is there a way to simply replace all instances of Box 1 in Collection 1's resource record with Box A, maintaining any child information like folder numbers in the Instances, without having to individually click on each archival object and update the instance? There aren't enough archival objects to warrant exporting as a CSV, editing the file, and then importing it back, but just enough to sometimes make it a hassle in certain resource records. Since these new top containers are linked to multiple resource records, I'm also wary of it creating duplicates that way. Essentially it would be helpful if there was basically a way in the Top Containers page to "replace" a box with another, though I don't see anything like that, and merge isn't exactly what we're looking for. Thanks! Nicole Yatsonsky, CA Special Collections Library Specialist Randall Library UNC Wilmington 910.962.3412 "The great use of a life is to spend it for something that outlasts it." ~ William James _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dan Michelson Project Manager Archivist Smith College Special Collections Special Collections is moving into the new Neilson Library and will be closed from May 31st until August 30th. All services will be temporarily unavailable. We look forward to reopening in the fall, 2021. Additional information can be found on our website. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brijmcla at iu.edu Thu Jun 17 16:41:10 2021 From: brijmcla at iu.edu (McLaughlin, Brianna Jean) Date: Thu, 17 Jun 2021 20:41:10 +0000 Subject: [Archivesspace_Users_Group] Using diacritics in ArchivesSpace Message-ID: Hi everyone, I'm probably missing a simple solution, but is there another way to use diacritics in ArchivesSpace without copy and pasting from another source? I saw some conversation about this in the listserv archives ~6 years ago, but most of the links are broken. Thanks! Bri McLaughlin, she/her/hers Visiting Metadata Services Librarian Indiana University 812-856-3321 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Thu Jun 17 16:45:31 2021 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Thu, 17 Jun 2021 20:45:31 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Background job error Message-ID: Hello all, We encountered the error below when running the "Generate PDF" job on a particular resource. Short of looking through every single record in the resource for the missing ", is there a way to quickly track down the error? Generating PDF for xxxxxxxxxxxxxxxxxxxxx -------------------------------------------------- Warning: this resource has not been published -------------------------------------------------- org.xml.sax.SAXParseException; lineNumber: 189; columnNumber: 110330; Open quote is expected for attribute "href" associated with an element type "a". net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:360) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317) RUBY.build(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/document_builder.rb:225) RUBY.to_fo(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:42) RUBY.to_pdf(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) var.local.archivesspace.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.lib.request_context.open(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) var.local.archivesspace.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.lib.background_job_queue.invokeOther31:run(var/local/archivesspace/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/lib//var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.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.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.start_background_thread(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:318) java.lang.Thread.run(java/lang/Thread.java:748) Regards, Zach Pelli Seton Hall University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Thu Jun 17 16:50:23 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 17 Jun 2021 20:50:23 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Background job error In-Reply-To: References: Message-ID: "Open quote is expected for attribute "href" associated with an element type "a"." There's some bad HTML in there. I usually export it to EAD and then just search for "href" and look for the bad tags, hopefully it's not a record with 1000 hrefs in there ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Zachary L Pelli Sent: Thursday, June 17, 2021 4:45 PM To: ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Generate PDF Background job error Hello all, We encountered the error below when running the "Generate PDF" job on a particular resource. Short of looking through every single record in the resource for the missing ", is there a way to quickly track down the error? Generating PDF for xxxxxxxxxxxxxxxxxxxxx -------------------------------------------------- Warning: this resource has not been published -------------------------------------------------- org.xml.sax.SAXParseException; lineNumber: 189; columnNumber: 110330; Open quote is expected for attribute "href" associated with an element type "a". net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:360) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317) RUBY.build(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/document_builder.rb:225) RUBY.to_fo(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:42) RUBY.to_pdf(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) var.local.archivesspace.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.lib.request_context.open(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) var.local.archivesspace.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.lib.background_job_queue.invokeOther31:run(var/local/archivesspace/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/lib//var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.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.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.start_background_thread(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:318) java.lang.Thread.run(java/lang/Thread.java:748) Regards, Zach Pelli Seton Hall University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddonizio at atlas-sys.com Thu Jun 17 16:51:58 2021 From: vaddonizio at atlas-sys.com (Valerie Addonizio) Date: Thu, 17 Jun 2021 20:51:58 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Background job error In-Reply-To: References: Message-ID: I second the tip about exporting to EAD as a inroad to the PDF failure. The EAD export itself may fail, but the logging may be more specific. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Thursday, June 17, 2021 4:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Generate PDF Background job error "Open quote is expected for attribute "href" associated with an element type "a"." There's some bad HTML in there. I usually export it to EAD and then just search for "href" and look for the bad tags, hopefully it's not a record with 1000 hrefs in there ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Zachary L Pelli > Sent: Thursday, June 17, 2021 4:45 PM To: ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org) > Subject: [Archivesspace_Users_Group] Generate PDF Background job error Hello all, We encountered the error below when running the "Generate PDF" job on a particular resource. Short of looking through every single record in the resource for the missing ", is there a way to quickly track down the error? Generating PDF for xxxxxxxxxxxxxxxxxxxxx -------------------------------------------------- Warning: this resource has not been published -------------------------------------------------- org.xml.sax.SAXParseException; lineNumber: 189; columnNumber: 110330; Open quote is expected for attribute "href" associated with an element type "a". net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:360) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317) RUBY.build(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/document_builder.rb:225) RUBY.to_fo(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:42) RUBY.to_pdf(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) var.local.archivesspace.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.lib.request_context.open(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) var.local.archivesspace.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.lib.background_job_queue.invokeOther31:run(var/local/archivesspace/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/lib//var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.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.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.start_background_thread(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:318) java.lang.Thread.run(java/lang/Thread.java:748) Regards, Zach Pelli Seton Hall University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Thu Jun 17 16:53:48 2021 From: seth.shaw at unlv.edu (Seth Shaw) Date: Thu, 17 Jun 2021 13:53:48 -0700 Subject: [Archivesspace_Users_Group] Generate PDF Background job error In-Reply-To: References: Message-ID: Also, once you download the EAD, the parse error tells you on what line the error occurred; "189" in this case. The problem may not be *right there* but that will give you a starting point for your search. On Thu, Jun 17, 2021 at 1:52 PM Valerie Addonizio wrote: > I second the tip about exporting to EAD as a inroad to the PDF failure. > The EAD export itself *may* fail, but the logging may be more specific. > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Blake > Carver > *Sent:* Thursday, June 17, 2021 4:50 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Generate PDF Background job > error > > > > "Open quote is expected for attribute "href" associated with an element > type "a"." > > > > There's some bad HTML in there. I usually export it to EAD and then just > search for "href" and look for the bad tags, hopefully it's not a record > with 1000 hrefs in there > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Zachary L Pelli > *Sent:* Thursday, June 17, 2021 4:45 PM > *To:* ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org) > > *Subject:* [Archivesspace_Users_Group] Generate PDF Background job error > > > > Hello all, > > > > We encountered the error below when running the "Generate PDF" job on a > particular resource. Short of looking through every single record in the > resource for the missing ", is there a way to quickly track down the error? > > > > Generating PDF for xxxxxxxxxxxxxxxxxxxxx > > -------------------------------------------------- > > Warning: this resource has not been published > > -------------------------------------------------- > > org.xml.sax.SAXParseException; lineNumber: 189; columnNumber: 110330; Open > quote is expected for attribute "href" associated with an element type > "a". > > > net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:360) > > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) > > > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456) > > > org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317) > > > RUBY.build(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/document_builder.rb:225) > > > RUBY.to_fo(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:42) > > > RUBY.to_pdf(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) > > > RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) > > > var.local.archivesspace.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.lib.request_context.open(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) > > > RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) > > > var.local.archivesspace.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.lib.background_job_queue.invokeOther31:run(var/local/archivesspace/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/lib//var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > > > var.local.archivesspace.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.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > > > RUBY.start_background_thread(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) > > org.jruby.RubyProc.call(org/jruby/RubyProc.java:318) > > java.lang.Thread.run(java/lang/Thread.java:748) > > > > > > Regards, > > > > Zach Pelli > > Seton Hall University Libraries > _______________________________________________ > 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 Mon Jun 21 14:05:10 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 21 Jun 2021 18:05:10 +0000 Subject: [Archivesspace_Users_Group] Call for speakers - ArchivesSpace 7th Annual Member Forum Message-ID: Dear ArchivesSpace Members, ArchivesSpace is seeking proposals for presentations and moderated discussions to be offered as part of our 7th Annual Member Forum, which will be offered virtually on August 2-4, 2021. Presentations will be delivered on Monday, August 2, from 12pm-3pm ET, and moderated discussions will be held on Tuesday, August 3, from 12pm-3pm ET. The event wiki and registrations will be made available soon, but for now we are looking for presenters and discussion leaders for August 2-3, 2021. Anything related to ArchivesSpace is fair game. Presentations and discussions can be on anything related to your work using, developing, or actively contributing to the ArchivesSpace application and community. Topics of particular interest include managing others working in ArchivesSpace (including interns, volunteers and students), large scale implementation or cleanup projects you or your organization have undertaken in either a remote or in-person environment, and presentations related to plugins or tools you have developed to work with ArchivesSpace. There is a short Google form for proposals available at https://forms.gle/7ru7pemTkshL2HDB9. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted is July 16, 2021, and all notifications will be made by July 20, 2021. If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org. We look forward to ?seeing? you soon! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29063 bytes Desc: image001.jpg URL: From PGalligan at rockarch.org Mon Jun 21 14:10:06 2021 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 21 Jun 2021 18:10:06 +0000 Subject: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1 Message-ID: Hi all, We?ve noticed that in our test migration from ArchivesSpace version 2.8.0 to 3.0.1 that the agent migration was sometimes creating two separate structured dates based on whether there was an existing date expression or not in the dates of existence section. Here is the JSON before migration: "dates_of_existence": [ { "lock_version": 0, "expression": "1915-2017", "begin": "1915", "end": "2017", "created_by": "pgalligan", "last_modified_by": "pgalligan", "create_time": "2019-12-04T14:24:11Z", "system_mtime": "2019-12-04T14:24:11Z", "user_mtime": "2019-12-04T14:24:11Z", "date_type": "range", "label": "existence", "jsonmodel_type": "date" } ], Here is the JSON post-migration: "dates_of_existence": [ { "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_label": "existence", "date_type_structured": "single", "jsonmodel_type": "structured_date_label", "structured_date_single": { "date_expression": "1915-2017", "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_role": "begin", "date_standardized_type": "standard", "jsonmodel_type": "structured_date_single" } }, { "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_label": "existence", "date_type_structured": "range", "jsonmodel_type": "structured_date_label", "structured_date_range": { "begin_date_standardized": "1915", "end_date_standardized": "2017", "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "begin_date_standardized_type": "standard", "end_date_standardized_type": "standard", "jsonmodel_type": "structured_date_range" } } ], It also seems to be creating a structured singular date instead of a date range. It?s parsing the expression correctly into separate dates, but it?s entirely unnecessary and creates and incorrect duplication. This seems like a bug and would stop us from updating because it?d be a hassle to go in and remove these. Is this intended behavior for this migration? There may be something I?m not understanding about MARC or EAC-CPF that makes this desirable, but it seems like a bug to me. Thanks, Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Jun 22 10:05:53 2021 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 22 Jun 2021 14:05:53 +0000 Subject: [Archivesspace_Users_Group] Add Subrecord for only one Agent type via Plugin? Message-ID: Just wondering if anyone knows if it's possible to add a subrecord via a plugin to *only one* agent type? From what I can tell, the current releases do not support this and the sidebar link mechanism appears to be broken as well. It looks like you need to add an entry for both agent and agent_{type} to the plugin config.yml file. Like agent: name: subrecord_name cardinality: zero_to_many agent_corporate_entity: name: subrecord_name cardinality: zero_to_many to get both a sidebar entry and the actual subrecord to appear. The generic agent entry is necessary for the subrecord to appear and is why you can't add to just one agent type. And the specific type entry controls the sidebar link. However, due to the mismatch between config keys, the sidebar link does not match the subrecord anchor. Am I missing something? The changes coming in the main branch, look like they *might* support this (or at least something close), but I haven't tested those changes yet. Thanks! Joshua ___________________ Joshua Shaw (he, him) Technology Coordinator Rauner Special Collections Library & Digital Library Technologies Group Dartmouth College 603.646.0405 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Tue Jun 22 10:29:42 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Tue, 22 Jun 2021 14:29:42 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace election results and new appointments Message-ID: Dear ArchivesSpace members, On behalf of the Governance Board I am pleased to announce the following new members for our ArchivesSpace governance groups. Governance Board (elected to three-year terms running July 1, 2021-June 30, 2024) * Natalie Adams, Cambridge University - Very Large level representative * Julia Novakovic, The Strong National Museum of Play- Small level representative Technical Advisory Council (appointed to terms running from July 1, 2021-June 30, 2024) * Tom Steele, University of Oklahoma * Elizabeth Dunham, Arizona State University * Austin Munsell, University of Oregon * Jenna Silver-Baustian, University of Iowa User Advisory Council (appointed to terms running from July 1, 2021-June 30, 2024) * Sarah Ponichtera, Seton Hall University * Kellen Carpenter, Western Carolina University * Suzanne Reller, University of Cincinnati * Patrick Milhoan, University of Notre Dame Please join me in welcoming these members to our governance groups and thanking them for their willingness to serve the ArchivesSpace community in this way. I want to personally thank the members of this year's Nominating Committee for their work in putting together a slate of excellent candidates for the openings on our groups and to all who participated in the process. Our community is enriched by the many different ways people contribute their talents. Yours sincerely, J. Gordon Daines III Chair, 2021 ArchivesSpace Nominating Committee Past-chair, ArchivesSpace Governance Board Brigham Young University _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Margaret.Peachy at tufts.edu Tue Jun 22 10:43:53 2021 From: Margaret.Peachy at tufts.edu (Peachy, Margaret) Date: Tue, 22 Jun 2021 14:43:53 +0000 Subject: [Archivesspace_Users_Group] Replacing text in the PUI Message-ID: Hi, everyone - I have a question regarding customizing how certain bits of text display in the PUI. In our current EAD delivery system we use CSS to essentially find and replace particular text strings to convey a clearer message to end users. For instance, we use a consistent placeholder URL in the File Version section of digital objects that are not yet processed. Currently, we use CSS to replace that URL (that goes nowhere) with a note that indicates the item is in digital storage. We have a similar solution for restricted digital objects. Has anyone done similar customization in the PUI? Thanks in advance for any assistance! Margaret Margaret Peachy, Digital Archivist Digital Collections & Archives, Tufts University Margaret.peachy at tufts.edu | 617.627.6855 she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Tue Jun 22 10:58:41 2021 From: cory_nimer at byu.edu (Cory Nimer) Date: Tue, 22 Jun 2021 14:58:41 +0000 Subject: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1 In-Reply-To: References: Message-ID: Patrick, We found the same thing in our test migration to 3.0.1. In cases where an Agent date entry included both a date expression and normalized dates, the application had split up the 2.8 date entry into two separate entries--one for the date expression (without normalized dates) and one for the normalized dates (without date expressions). Our impression was that the application was not parsing the date expression at all. This is a significant issue for us moving forward, and we would be interested in learning more about what approaches other institutions have been considering to address this issue. Best, Cory Nimer University Archivist Brigham Young University From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Galligan, Patrick Sent: Monday, June 21, 2021 12:10 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1 Hi all, We've noticed that in our test migration from ArchivesSpace version 2.8.0 to 3.0.1 that the agent migration was sometimes creating two separate structured dates based on whether there was an existing date expression or not in the dates of existence section. Here is the JSON before migration: "dates_of_existence": [ { "lock_version": 0, "expression": "1915-2017", "begin": "1915", "end": "2017", "created_by": "pgalligan", "last_modified_by": "pgalligan", "create_time": "2019-12-04T14:24:11Z", "system_mtime": "2019-12-04T14:24:11Z", "user_mtime": "2019-12-04T14:24:11Z", "date_type": "range", "label": "existence", "jsonmodel_type": "date" } ], Here is the JSON post-migration: "dates_of_existence": [ { "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_label": "existence", "date_type_structured": "single", "jsonmodel_type": "structured_date_label", "structured_date_single": { "date_expression": "1915-2017", "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_role": "begin", "date_standardized_type": "standard", "jsonmodel_type": "structured_date_single" } }, { "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_label": "existence", "date_type_structured": "range", "jsonmodel_type": "structured_date_label", "structured_date_range": { "begin_date_standardized": "1915", "end_date_standardized": "2017", "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "begin_date_standardized_type": "standard", "end_date_standardized_type": "standard", "jsonmodel_type": "structured_date_range" } } ], It also seems to be creating a structured singular date instead of a date range. It's parsing the expression correctly into separate dates, but it's entirely unnecessary and creates and incorrect duplication. This seems like a bug and would stop us from updating because it'd be a hassle to go in and remove these. Is this intended behavior for this migration? There may be something I'm not understanding about MARC or EAC-CPF that makes this desirable, but it seems like a bug to me. Thanks, Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Jun 22 13:37:13 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 22 Jun 2021 17:37:13 +0000 Subject: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1 In-Reply-To: References: Message-ID: Patrick and Cory, Thank you for surfacing this issue. We've looked into this more and I'd like to work with you to determine the desired outcome for migration of these dates. I'll reach out to you directly. If anyone else reading these messages has a strong interest in or suggestions for the migration of this information, would you please comment here or reach out to me to participate in these discussions? In the meantime, I would suggest that people who have both structured dates and date expressions on Agents in their pre-3.0 ArchivesSpace hold off on migrating for now. These kinds of dates would typically be in your Dates of Existence sub-records. If pre-3.0 you have been using only the Dates field in a Name Form, or if you only use structured dates, the issue mentioned here is less likely to be pertinent to you. Thanks for your help, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Cory Nimer Sent: Tuesday, June 22, 2021 10:59 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1 Patrick, We found the same thing in our test migration to 3.0.1. In cases where an Agent date entry included both a date expression and normalized dates, the application had split up the 2.8 date entry into two separate entries--one for the date expression (without normalized dates) and one for the normalized dates (without date expressions). Our impression was that the application was not parsing the date expression at all. This is a significant issue for us moving forward, and we would be interested in learning more about what approaches other institutions have been considering to address this issue. Best, Cory Nimer University Archivist Brigham Young University From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Galligan, Patrick Sent: Monday, June 21, 2021 12:10 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1 Hi all, We've noticed that in our test migration from ArchivesSpace version 2.8.0 to 3.0.1 that the agent migration was sometimes creating two separate structured dates based on whether there was an existing date expression or not in the dates of existence section. Here is the JSON before migration: "dates_of_existence": [ { "lock_version": 0, "expression": "1915-2017", "begin": "1915", "end": "2017", "created_by": "pgalligan", "last_modified_by": "pgalligan", "create_time": "2019-12-04T14:24:11Z", "system_mtime": "2019-12-04T14:24:11Z", "user_mtime": "2019-12-04T14:24:11Z", "date_type": "range", "label": "existence", "jsonmodel_type": "date" } ], Here is the JSON post-migration: "dates_of_existence": [ { "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_label": "existence", "date_type_structured": "single", "jsonmodel_type": "structured_date_label", "structured_date_single": { "date_expression": "1915-2017", "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_role": "begin", "date_standardized_type": "standard", "jsonmodel_type": "structured_date_single" } }, { "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "date_label": "existence", "date_type_structured": "range", "jsonmodel_type": "structured_date_label", "structured_date_range": { "begin_date_standardized": "1915", "end_date_standardized": "2017", "create_time": "2021-06-16T19:12:16Z", "system_mtime": "2021-06-16T19:12:16Z", "user_mtime": "2021-06-16T19:12:16Z", "lock_version": 0, "begin_date_standardized_type": "standard", "end_date_standardized_type": "standard", "jsonmodel_type": "structured_date_range" } } ], It also seems to be creating a structured singular date instead of a date range. It's parsing the expression correctly into separate dates, but it's entirely unnecessary and creates and incorrect duplication. This seems like a bug and would stop us from updating because it'd be a hassle to go in and remove these. Is this intended behavior for this migration? There may be something I'm not understanding about MARC or EAC-CPF that makes this desirable, but it seems like a bug to me. Thanks, Patrick Galligan Rockefeller Archive Center -------------- 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 Corinne.Chatnik at nysed.gov Tue Jun 22 13:44:12 2021 From: Corinne.Chatnik at nysed.gov (Corinne Chatnik) Date: Tue, 22 Jun 2021 17:44:12 +0000 Subject: [Archivesspace_Users_Group] Auto Generate Unique Barcodes for Top Containers Message-ID: Hi everyone, I know this is a long shot but has anyone had any luck developing something that would generate unique barcodes for new top containers? Thanks! Corinne Chatnik Digital Strategies New York State Archives 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 Jessica.Crouch at lyrasis.org Wed Jun 23 09:43:06 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 23 Jun 2021 13:43:06 +0000 Subject: [Archivesspace_Users_Group] Webinar Reminder: Making the most of the ArchivesSpace Classifications Module and Library of Congress Subject Headings at the University of Oregon Message-ID: <46826DF7-D045-4F82-9C11-5AEC9C6BAF37@lyrasis.org> Dear ArchivesSpace users, There?s still time to register for next week?s webinar on making the most of the ArchivesSpace classifications module and Library of Congress Subject Headings at the University of Oregon. In this webinar, Liliya Benz and Alex Bisio of University of Oregon will discuss their initiative to create interactive, browsable subject guides for new reference staff and patrons by making use of the classifications module in ArchivesSpace. When: June 30, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00 p.m. PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_9vyoqxiySM-UnKuHCnfexA This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: In March 2020, processing archivists in Special Collections and University Archives (SCUA) at the University of Oregon Libraries began experimenting with the Classifications module in ArchivesSpace, seeking a way to create interactive, browsable subject guides for new reference staff and patrons. Using existing controlled vocabulary in SCUA?s MARC records, processing archivists employed data exploration tools in OpenRefine (formerly GoogleRefine) to collate collections into subject areas based on Library of Congress Classifications. Using OpenRefine and additional subject analysis of the collections, processing archivists were able to create comprehensive lists of SCUA?s collections by subjects represented. These lists could then be uploaded into ArchivesSpace Classifications, giving staff and patrons a tool to browse archival collections as they would books on a shelf in the general stacks of the university library. This webinar will explore the MARC-to-Classifications workflow in OpenRefine, as well as subject analysis methods used to assign both classifications and subclassifications based on numerical collection data. Classification Web, the primary tool used for subject analysis and classification, will be juxtaposed with other open-access tools in the hope that institutions may replicate aspects of the project regardless of subscription-based resources. Highlighted resources used for subject analysis will include Library of Congress Classification Web (subscription-based), Library of Congress Authorities (open access), and the Library of Congress Classification Outline (open access). A Q&A will follow. Presenter Information: Liliya Benz is the Special Projects Processing Archivist for Special Collections and University Archives at the University of Oregon. She received her Bachelor of Arts in applied mathematics from the University of Oregon and her Master of Library Science with a concentration in archives studies from Emporia State University. Alex Bisio (she/her/hers) is the Lead Processing Archivist in Special Collections and University Archives at the University of Oregon Libraries. She earned her MSLIS in Archives Management and MA in American History from Simmons College, and her BA in American History from Santa Clara University. Before joining SCUA at the University of Oregon, she served as the Associate Archivist of the Jesuit Archives: Central United States in Saint Louis, Missouri, and the Archivist for the Critical Theory Archive at the University of California, Irvine. Who should attend: Anyone using or interested in using the ArchivesSpace Classifications module. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29066 bytes Desc: image001.jpg URL: From vaddonizio at atlas-sys.com Thu Jun 24 08:43:20 2021 From: vaddonizio at atlas-sys.com (Valerie Addonizio) Date: Thu, 24 Jun 2021 12:43:20 +0000 Subject: [Archivesspace_Users_Group] Seeking pro-tips for AS Member Forum! Message-ID: Greetings everyone, I am seeking "pro-tips" from the community for a 90 minute presentation for the AS Member Forum. These can be tips of any flavor! Every day tips! Super advanced tips! I hate that I know this tips! Please do it this way instead tips! I'm gathering these tips together here, so please click and submit your idea, whether it's version specific/dependent, and whether you'd like credit. Once your tip is submitted, I might reach out to you if I need clarification. I am not automatically collecting email addresses nor do you have to sign in to Google to submit this form. I have no hidden agendas or nefarious info-collection motivations. Just pro-tips. No tip too small! Well, maybe, but please submit it anyway. That link again is: https://forms.gle/ELoxgzmbRysfA9Zu9 Thanks so much! -Valerie _______________________ Valerie Addonizio, MLIS Special Collections and Archives Technical Consultant Atlas Systems - You have a job to do. We help you do it. (757) 317-2592 vaddonizio at atlas-sys.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Jun 28 10:02:04 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 28 Jun 2021 14:02:04 +0000 Subject: [Archivesspace_Users_Group] Announcing the next ArchivesSpace Trainers Corps Office Monday, July 19th at 2pm ET/11am PT Message-ID: <5C3777E1-D49E-43CD-A834-7A539F93A663@lyrasis.org> Dear ArchivesSpace Users, The second ArchivesSpace Trainers Corps ?Office Hour? will be Monday, July 19th 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 members and take questions related to a pre-determined topic. For this open call, the Trainers Corps will briefly explain the difference between full mode and light mode in the ArchivesSpace Agents module and how to enable and toggle between the two. This feature is new to ArchivesSpace v3.0/3.0.1. Following the presentation, you will have the opportunity to ask questions about the topic, followed by a general Q&A about all things agents. If you would like to suggest a topic for a future ?Office Hour,? you can do so at https://forms.gle/unz3GmAbWwvpHjSr7. ArchivesSpace Trainers Corps ?Office Hour? Date: July 19, 2021 Time: 2:00pm ET / 11:00am PT Topic: Full mode vs. light mode in the ArchivesSpace Agents module Registration: https://lyrasis.zoom.us/meeting/register/tJckce-trjwtH9SW4q2BywTYU1YkkJo-5Sr6 Over the next year, the Trainers Corps will offer regularly scheduled trainings and office hours covering a variety of topics on all things ArchivesSpace. Registration for each training will be separate and registration will open 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 [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29062 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Mon Jun 28 13:06:29 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 28 Jun 2021 17:06:29 +0000 Subject: [Archivesspace_Users_Group] Webinar Reminder - Virtual Every Step of the Way: Migrating to ArchivesSpace during Remote Work Message-ID: <17A924AB-84A5-43FF-8430-056709F812B9@lyrasis.org> Dear ArchivesSpace users, There?s still time to register for next week?s webinar on implementing ArchivesSpace in a remote work environment. In this webinar, Tomaro Taylor, Amanda Boczar, and Anastasia Temkina of USF Libraries - Tampa Special Collections will illustrate how they structured their complete migration to ArchivesSpace in a remote environment, including the active incorporation of student workers with various levels of archival experience. When: July 7, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00 pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_p_-DXUf8S1KlEYmsheGujw This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: In February 2020, USF Libraries ? Tampa Special Collections formally began the process to migrate to ArchivesSpace. Those discussions quickly stalled, however, when the University asked that they begin to formulate continuity of operations plans for remote work in preparations for what was then a hypothetical shutdown. Early into lockdown, USF determined that it would actually be the perfect time to migrate to ArchivesSpace. The campus was closed, no Reading Room services could be provided, and staff wanted to engage in meaningful projects. Guiding a team consisting of librarians, staff, and student employees, Special Collections organized a multi-phase plan for preparing data for migration, undergoing migration, and cleaning records in ArchivesSpace. As staff begin to gain more physical access in 2021, they are finalizing the clean up and ready to engage with patrons using ArchivesSpace. In this webinar, Tomaro Taylor, Amanda Boczar, and Anastasia Temkina of USF Libraries - Tampa Special Collections will illustrate how they structured their complete migration to ArchivesSpace in a remote environment, including the active incorporation of student workers with various levels of archival experience. No one on staff had prior experience with ArchivesSpace and all members of the team were trained in stages. They will also address how this project encouraged a more holistic reassessment, including systematically evaluating finding aids for missing information, conscious editing of descriptive content and subject headings, and the addition of classification headers. A Q&A will follow. Presenter Information: Tomaro Taylor is the Head of Special Collections at the University of South Florida Libraries Tampa campus. A Certified Archivist, Tomaro has nearly 20 years of experience implementing policies, procedures, guidelines, and best practices in the archival field. She currently serves as President of the Academy of Certified Archivists and Co-Manager of the Society of American Archivists' Digital Archives Specialist (DAS) Exam. Amanda Boczar is Special Collections Operations Manager at the University of South Florida Libraries Tampa campus. Amanda holds a Ph.D. in History with over 12 years of experience in higher education, and joined the library in 2019. She was responsible for the migration to ArchivesSpace, and supervised student and employee training through the process. Ana Temkina is a student assistant at USF Libraries Tampa campus, Special Collections. She received her bachelor's degree in Library and Information Science, Children?s Literature track, from St. Petersburg State University of Culture and Arts, Russia. At USF she is doing her MA in Applied Anthropology and will soon graduate to continue her academic path at the University of Kentucky. Library work remains one of her great passions. Who should attend: Anyone interested in implementing ArchivesSpace, developing a migration plan or using ArchivesSpace remotely. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29067 bytes Desc: image001.jpg URL: From ndroark at anderson.edu Tue Jun 29 11:54:10 2021 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Tue, 29 Jun 2021 11:54:10 -0400 Subject: [Archivesspace_Users_Group] LCNAF in 2.8.1 Message-ID: Hi all, I'm testing a fresh install of 2.8.1 and getting an error message on the LCNAF and LCSH plugin. This should be working in 2.8.1, right? [image: image.png] *Nicholas Stanton-Roark* | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 <%28765%29%20641%204285> | ndroark at anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 91371 bytes Desc: not available URL: From blake.carver at lyrasis.org Tue Jun 29 17:50:16 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 29 Jun 2021 21:50:16 +0000 Subject: [Archivesspace_Users_Group] LCNAF in 2.8.1 In-Reply-To: References: Message-ID: There should be an error in the logs, that should help explain what's happening. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Nic Stanton-Roark Sent: Tuesday, June 29, 2021 11:54 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] LCNAF in 2.8.1 Hi all, I'm testing a fresh install of 2.8.1 and getting an error message on the LCNAF and LCSH plugin. This should be working in 2.8.1, right? [image.png] [https://anderson.edu/uploads/au-email-logo.gif] Nicholas Stanton-Roark | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 | ndroark at anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 91371 bytes Desc: image.png URL: From Jessica.Crouch at lyrasis.org Wed Jun 30 09:11:54 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 30 Jun 2021 13:11:54 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - June 2021 Message-ID: <35575CA2-A573-4D3B-AA8F-C89692E0AE4A@lyrasis.org> [cid:image001.jpg at 01D76D8F.F81D9C40] ArchivesSpace Update ? June 2021 Development ArchivesSpace released v3.0.1 earlier this month. It contains all the code from 3.0.0, along with a fix to the migration for agent contact notes. More details are available from the releases page at https://github.com/archivesspace/archivesspace/releases. Please note that we are working with community members on an issue related to how Dates of Existence migrate when there are both standardized dates and date expressions in the same date record. If you use Dates of Existence this way, you may want to hold off on upgrading until a new release is available later in the summer. Please contact us if you would like more details. Governance Board Election Results and New Council Members From Gordon Daines, Chair of the Nominating Committee and Past Chair of the Governance Board On behalf of the Governance Board I am pleased to announce the following new members for our ArchivesSpace governance groups. Governance Board (elected to three-year terms running July 1, 2021-June 30, 2024) * Natalie Adams, Cambridge University ? Very Large level representative * Julia Novakovic, The Strong National Museum of Play ? Small level representative Technical Advisory Council (appointed to terms running from July 1, 2021-June 30, 2024) * Tom Steele, University of Oklahoma * Elizabeth Dunham, Arizona State University * Austin Munsell, University of Oregon * Jenna Silver-Baustian, University of Iowa User Advisory Council (appointed to terms running from July 1, 2021-June 30, 2024) * Sarah Ponichtera, Seton Hall University * Kellen Carpenter, Western Carolina University * Suzanne Reller, University of Cincinnati * Patrick Milhoan, University of Notre Dame Please join me in welcoming these members to our governance groups and thanking them for their willingness to serve the ArchivesSpace community in this way. I want to personally thank the members of this year?s Nominating Committee for their work in putting together a slate of excellent candidates for the openings on our groups and to all who participated in the process. Our community is enriched by the many different ways people contribute their talents. Membership Renewals ArchivesSpace is developed by and for the community that uses it, and strengthened by services and activities that support our community and connect us to one another. As we close another membership year, we want to give a special thanks to all of the institutions that have joined us as members. ArchivesSpace membership is our primary source of revenue and informs and sustains every aspect of the program, including software development, support and engagement. Thanks for all that your support makes possible. ArchivesSpace membership renewals for 2021-2022 have been sent to all current members. If you have any questions, or if you would like to join as a new member for the 2021-2022 membership year, please let us know at ArchivesSpaceHome at lyrasis.org. We look forward to another year working together. Webinar Announcement: Virtual Every Step of the Way: Migrating to ArchivesSpace during Remote Work When: July 7, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00 pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_p_-DXUf8S1KlEYmsheGujw This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: In February 2020, USF Libraries ? Tampa Special Collections formally began the process to migrate to ArchivesSpace. Those discussions quickly stalled, however, when the University asked that they begin to formulate continuity of operations plans for remote work in preparations for what was then a hypothetical shutdown. Early into lockdown, USF determined that it would actually be the perfect time to migrate to ArchivesSpace. The campus was closed, no Reading Room services could be provided, and staff wanted to engage in meaningful projects. Guiding a team consisting of librarians, staff, and student employees, Special Collections organized a multi-phase plan for preparing data for migration, undergoing migration, and cleaning records in ArchivesSpace. As staff begin to gain more physical access in 2021, they are finalizing the clean up and ready to engage with patrons using ArchivesSpace. In this webinar, Tomaro Taylor, Amanda Boczar, and Anastasia Temkina of USF Libraries ? Tampa Special Collections will illustrate how they structured their complete migration to ArchivesSpace in a remote environment, including the active incorporation of student workers with various levels of archival experience. No one on staff had prior experience with ArchivesSpace and all members of the team were trained in stages. They will also address how this project encouraged a more holistic reassessment, including systematically evaluating finding aids for missing information, conscious editing of descriptive content and subject headings, and the addition of classification headers. A Q&A will follow. Presenter Information: Tomaro Taylor is the Head of Special Collections at the University of South Florida Libraries Tampa campus. A Certified Archivist, Tomaro has nearly 20 years of experience implementing policies, procedures, guidelines, and best practices in the archival field. She currently serves as President of the Academy of Certified Archivists and Co-Manager of the Society of American Archivists? Digital Archives Specialist (DAS) Exam. Amanda Boczar is Special Collections Operations Manager at the University of South Florida Libraries Tampa campus. Amanda holds a Ph.D. in History with over 12 years of experience in higher education, and joined the library in 2019. She was responsible for the migration to ArchivesSpace, and supervised student and employee training through the process. Ana Temkina is a student assistant at USF Libraries Tampa campus, Special Collections. She received her bachelor?s degree in Library and Information Science, Children?s Literature track, from St. Petersburg State University of Culture and Arts, Russia. At USF she is doing her MA in Applied Anthropology and will soon graduate to continue her academic path at the University of Kentucky. Library work remains one of her great passions. Announcing the next ArchivesSpace Trainers Corps Office Monday, July 19th at 2pm ET/11am PT The second ArchivesSpace Trainers Corps ?Office Hour? will be Monday, July 19th 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 members and take questions related to a pre-determined topic. For this open call, the Trainers Corps will briefly explain the difference between full mode and light mode in the ArchivesSpace Agents module and how to enable and toggle between the two. This feature is new to ArchivesSpace v3.0/3.0.1. Following the presentation, you will have the opportunity to ask questions about the topic, followed by a general Q&A about all things agents. If you would like to suggest a topic for a future ?Office Hour,? you can do so at https://forms.gle/unz3GmAbWwvpHjSr7. ArchivesSpace Trainers Corps ?Office Hour? Date: July 19, 2021 Time: 2:00pm ET / 11:00am PT Topic: Full mode vs. light mode in the ArchivesSpace Agents module Registration: https://lyrasis.zoom.us/meeting/register/tJckce-trjwtH9SW4q2BywTYU1YkkJo-5Sr6 Over the next year, the Trainers Corps will offer regularly scheduled trainings and office hours covering a variety of topics on all things ArchivesSpace. Registration for each training will be separate and registration will open 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. Call for speakers - ArchivesSpace 7th Annual Member Forum ArchivesSpace is seeking proposals for presentations and moderated discussions to be offered as part of our 7th Annual Member Forum, which will be offered virtually on August 2-4, 2021. Presentations will be delivered on Monday, August 2, from 12pm-3pm ET, and moderated discussions will be held on Tuesday, August 3, from 12pm-3pm ET. The event wiki and registrations will be made available soon, but for now we are looking for presenters and discussion leaders for August 2-3, 2021. Anything related to ArchivesSpace is fair game. Presentations and discussions can be on anything related to your work using, developing, or actively contributing to the ArchivesSpace application and community. Topics of particular interest include managing others working in ArchivesSpace (including interns, volunteers and students), large scale implementation or cleanup projects you or your organization have undertaken in either a remote or in-person environment, and presentations related to plugins or tools you have developed to work with ArchivesSpace. There is a short Google form for proposals available at https://forms.gle/7ru7pemTkshL2HDB9. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted is July 16, 2021, and all notifications will be made by July 20, 2021. Recording Announcement: ArchivesSpace Digital Objects Module Training Thank you to everyone who attended the community-wide training on the ArchivesSpace Digital Objects Module. A recording of this training is now available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2331148319/ArchivesSpace+Community-Wide+Virtual+Training. Membership Update We are excited to welcome our newest members to our community! Our new members since May 31 include: * Black Cultural Archives (London, England) * Elmhurst University (Elmhurst, IL) * Letterenhuis (Antwerp, Belgium) * Spelman College (Atlanta, GA) As of June 30, we have 437 General members, 21 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22471 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29063 bytes Desc: image002.jpg URL: From mladair at umich.edu Wed Jun 30 09:15:48 2021 From: mladair at umich.edu (Matthew Adair) Date: Wed, 30 Jun 2021 09:15:48 -0400 Subject: [Archivesspace_Users_Group] jetty* directories in /tmp Message-ID: Hi folks, I've been tinkering with setting up a new ArchiveSpace instance. I've run into an issue that is causing me problems. I suspect it is something that I've done configuration wise that I just don't fully understand. I have a bunch of jetty* directories that have piled up in /tmp, for example: jetty-0.0.0.0-30023-backend.war-_-any-_8588578728394279934/ Some many, in fact, they used up our space allocation for /tmp and I wasn't not able to SSH into our server. Is there a way to direct these to a different location? Even better would be an understanding of what these are if somebody wants to dive that deep with an explanation Thanks! Matt ---- *Matthew Adair* Lead Archivist for Digital Imaging and Infrastructure *[Due to working remotely, email is the best method to reach me.]* Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734-647-3537 http://bentley.umich.edu @UmichBentley *The Bentley Historical Library acknowledges that coerced cessions of land by the Anishnaabeg and Wyandot made the University of Michigan possible, and we seek to reaffirm the ancestral and contemporary ties of these peoples to the lands where the University now stands.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdysonsm at utk.edu Wed Jun 30 11:04:44 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Wed, 30 Jun 2021 15:04:44 +0000 Subject: [Archivesspace_Users_Group] JMX monitoring (or similar) Message-ID: <90e0f7c73858d093e89be2d20bb776c178ba2463.camel@utk.edu> Hi all - We're looking to incorporate a monitoring solution for ArchivesSpace, and AS is a slightly different beastie: most of our of Java applications run in Tomcat and the Jetty runtime is a bit unfamiliar. Is anyone using monitoring to keep an eye on AS? I can modify the archivesspace.sh to enable JMX, but I was curious if anyone was doing anything specific in terms of Solr monitoring, log tracking, or some other configuration change in one of the Jetty containers. Thanks in advance for reading and any insights or suggestions you're willing to share. Best, Bridger -- Bridger Dyson-Smith University of Tennessee Libraries Digital Initiatives