From Jessica.Crouch at lyrasis.org Tue Feb 1 10:07:10 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 1 Feb 2022 15:07:10 +0000 Subject: [Archivesspace_Users_Group] Webinar Postponed: Using ArchivesSpace to create EAC-CPF records (90 minutes) Message-ID: <699EEA2C-4D25-4A19-8DB6-27C4BC2CD451@lyrasis.org> Dear ArchivesSpace users, Due to unforeseen circumstances, the 90-minute learning opportunity demonstrating how to create valid EAC-CPF scheduled for February 9 has been postponed to May 24, 2022, at 2:00pm ET/11:00am PT. If you?ve already registered for this webinar, your registration has been transferred to this new date. If you need to cancel your registration, you can do so using the connection information provided via Zoom. Led by Regine Heberlein, Library IT Data Analyst at Princeton University, and Christine Di Bella, ArchivesSpace Program Manager, this webinar will demonstrate how to create valid EAC-CPF records using ArchivesSpace and offer some tips and tricks for making the process easier within your repository. Date: May 24, 2022 Time: 2:00pm ? 3:30pm ET (11:00am ? 12:30pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_e777kyjtQ6qjBMWeiiTWmg This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: The recent expansion of the agents module in ArchivesSpace greatly expanded the application?s support for the metadata standard Encoded Archival Context ? Corporate Bodies, Persons, and Families (EAC-CPF) and the potential for exchanging these records with other systems, including Social Networks and Archival Context (SNAC). Taking full advantage of this potential requires some work on the record creator?s part as ArchivesSpace?s requirements for creating agent records remain minimal. This learning opportunity will demonstrate how to create valid EAC-CPF records using ArchivesSpace and offer some tips and tricks for making the process easier within your repository. An open discussion and Q&A will follow. This learning opportunity introduces EAC-CPF in the context of ArchivesSpace but is not intended to be a full overview of the standard. Resources for learning more about EAC-CPF include: * Encoded Archival Standards: A Primer: https://www.youtube.com/watch?v=WYWQeBRnhz0 * EAC-CPF Community and Support page: https://eac.staatsbibliothek-berlin.de/community-and-mailinglist/ * EAC-CPF Tag Library: https://eac.staatsbibliothek-berlin.de/schemata-and-tag-library/ NOTE: This learning opportunity assumes basic knowledge of ArchivesSpace, including an understanding of agent records. If you do not have this, we recommend watching the videos of the Basics workshop series, available on YouTube at https://www.youtube.com/playlist?list=PL3cxupmXL7WiHyMc0uFmsCEIVOQmrI7FL. We will not be able to answer general questions about ArchivesSpace or specific questions about individual ArchivesSpace implementations during this session. Who should attend: Anyone interested in using ArchivesSpace to create valid EAC-CPF records. Please email ArchivesSpaceHome at lyrasis.org if you have any questions. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Tue Feb 1 12:50:09 2022 From: npwb2 at cam.ac.uk (Nick Butler) Date: Tue, 1 Feb 2022 17:50:09 +0000 Subject: [Archivesspace_Users_Group] "Couldn't find enum" after v2.8.1 to v3.1.1 upgrade Message-ID: Hi there, I've been working on upgrading our test ArchivesSpace instance from v2.8.1 to v3.1.1. The database migrations all appear to have run correctly, and the site starts fine, but when I triggered a reindex the indexer logs are filled with stack traces of the following sort (abbreviated for brevity): E, [2022-02-01T17:25:28.067043 #9213] ERROR -- : Thread-2024: Failed fetching resource id=1: {"error":"Couldn't find enum in begin_date_standardized_type for StructuredDateRange with id 3194: /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/dynamic_enums.rb:51:in `block in uses_enums' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/dynamic_enums.rb:66:in `block in uses_enums' org/jruby/RubyArray.java:1809:in `each' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/dynamic_enums.rb:64:in `block in uses_enums' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/nested_record_resolver.rb:39:in `block in do_resolve' I've checked the enumeration_value table, and there are no values with id = 3194, if that's relevant. All of the entries in our structured_date_range table have this value (3194), for both begin_ and end_date_standardized_type_id: > select distinct begin_date_standardized_type_id, end_date_standardized_type_id from structured_date_range; +---------------------------------+-------------------------------+ | begin_date_standardized_type_id | end_date_standardized_type_id | +---------------------------------+-------------------------------+ | 3194 | 3194 | +---------------------------------+-------------------------------+ 1 row in set (0.043 sec) I'm not sure where to begin troubleshooting this - any advice is greatly appreciated! Many thanks, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From krwong at email.unc.edu Tue Feb 1 13:28:13 2022 From: krwong at email.unc.edu (Wong, Kara) Date: Tue, 1 Feb 2022 18:28:13 +0000 Subject: [Archivesspace_Users_Group] Participation in a Research Study on Open-Source Software Message-ID: Hello, Apologies for cross posting.? You are invited to participate in a research project studying?how?institutions choose to host open-source software designed for galleries, libraries, archives, and museums.?The study is open to all who have input in IT purchasing decisions, whether they are?members of IT units?or not.? Participation includes filling out a brief anonymous survey that will take approximately?15-20?minutes to complete. This survey will ask you about open-source software at your institution and how your institution chose to host said software. Participation is voluntary, and responses will be kept confidential.?You can choose to stop taking the survey at any time and withdraw from the study. Participation or?non-participation will not impact your relationship with the University of North Carolina?at?Chapel Hill. Study Information IRB Study #: 21-3376 Title of Study: Vendor-hosted versus Self-hosted Implementation of Open-Source Software at Academic Libraries Principal Investigator: Kara Wong Principal Investigator Department: UNC-CH School of Information and Library Science If you have any questions about the research, please contact the Principal Investigator,?Kara Wong, via email?at?krwong at email.unc.edu.?If you have questions or concerns about your rights as a research subject, you may contact the UNC-CH Institutional Review Board at 919-966-3113 or IRB_subjects at unc.edu. Thank you for your time and consideration. Follow this link to the survey: Take the Survey Or copy and paste the URL below into your browser:?https://unc.az1.qualtrics.com/jfe/form/SV_0PNYZWlaEbJNMuG Best, Kara Kara Wong (she/her) Carolina Academic Library Associate ? Software Development Master of Science in Information Science, 2020-2022 The University of North Carolina at Chapel Hill -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Wed Feb 2 06:14:17 2022 From: npwb2 at cam.ac.uk (Nick Butler) Date: Wed, 2 Feb 2022 11:14:17 +0000 Subject: [Archivesspace_Users_Group] "Couldn't find enum" after v2.8.1 to v3.1.1 upgrade In-Reply-To: References: Message-ID: Hi all, Turns out this was due to the database having been previously migrated and then not rolled back at all - recreating the database and remigrating solved this issue for us. Best wishes, Nick ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Nick Butler Sent: 01 February 2022 17:50 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] "Couldn't find enum" after v2.8.1 to v3.1.1 upgrade Hi there, I've been working on upgrading our test ArchivesSpace instance from v2.8.1 to v3.1.1. The database migrations all appear to have run correctly, and the site starts fine, but when I triggered a reindex the indexer logs are filled with stack traces of the following sort (abbreviated for brevity): E, [2022-02-01T17:25:28.067043 #9213] ERROR -- : Thread-2024: Failed fetching resource id=1: {"error":"Couldn't find enum in begin_date_standardized_type for StructuredDateRange with id 3194: /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/dynamic_enums.rb:51:in `block in uses_enums' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/dynamic_enums.rb:66:in `block in uses_enums' org/jruby/RubyArray.java:1809:in `each' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/dynamic_enums.rb:64:in `block in uses_enums' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/nested_record_resolver.rb:39:in `block in do_resolve' I've checked the enumeration_value table, and there are no values with id = 3194, if that's relevant. All of the entries in our structured_date_range table have this value (3194), for both begin_ and end_date_standardized_type_id: > select distinct begin_date_standardized_type_id, end_date_standardized_type_id from structured_date_range; +---------------------------------+-------------------------------+ | begin_date_standardized_type_id | end_date_standardized_type_id | +---------------------------------+-------------------------------+ | 3194 | 3194 | +---------------------------------+-------------------------------+ 1 row in set (0.043 sec) I'm not sure where to begin troubleshooting this - any advice is greatly appreciated! Many thanks, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahaywood at cca.qc.ca Wed Feb 2 17:03:52 2022 From: ahaywood at cca.qc.ca (Anna Haywood) Date: Wed, 2 Feb 2022 22:03:52 +0000 Subject: [Archivesspace_Users_Group] Generic top container note? In-Reply-To: References: Message-ID: Hello Olivia, This is a very late reply but I would like to second this idea. Our institution would be very interested in having a generic note field on top containers. When we create accession records, we attach container instances to the accession record to keep track of which unprocessed boxes came with which accession. Rather than link to an external inventory, or have to create component records for unprocessed materials, we would prefer to be able to give a brief note about the container?s contents in this field. Please let me know if you open a development ticket because I would strongly support it. Best, Anna --- Anna Haywood Archiviste Archivist Centre Canadien d'Architecture Canadian Centre for Architecture 1920, rue Baile, Montr?al, Qu?bec, Canada, H3H 2S6 +1 5149397001x1368 cca.qc.ca Twitter | Instagram | Facebook | YouTube Qu'est-ce qui vous pousse ? privil?gier une caract?ristique plut?t qu'une autre pour d?crire un objet? What makes you pick one characteristic over another to describe an object? Inscrivez-vous pour recevoir de nos nouvelles. Sign up to get news from us. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Olivia S Solis Sent: Monday, December 13, 2021 1:13 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Generic top container note? Hey all, I was wondering if any other institutions out there had an interest in a field that we have consistently found a need for: a generic note for staff attached to top container records. Reasons have included: * We renamed a box. Because boxes may be part of citations or referenced in numerous places in internal documentation, staff sometimes goes to absurd lengths to keep an old box number when it is no longer relevant or the box really should be renamed. Having the old box # in a note that is indexed gets rid of that problem as there is an immediately obvious place to document the change. Staff and researchers often look for a box number they've found in citations and notes. Keeping this information in a note on the container record would allow us to locate the correct container through a key-word search. * We merged two boxes into one. * We want to document the space left in a box and ASpace currently allows no way to do that. * The box has a nonstandard size (no container profile yet) * The box needs some upkeep (new label, new container, it's missing a lid) * We can't find a box. It's happened. We want to document all the places we've looked * Other internal notes about the box's status, condition, barcode or indicator or history, restriction status. It seems like ASpace wants us to document information about top containers in other places including Processing Notes attached to specific archival objects/resource records/accessions, assessments, location notes. Location notes sometimes could work, but we have limited staff time and can't update numerous records (all the archival objects/collections attached to a box or assessments attached to AOs/collections) to document a single change. A generic note attached to top containers would solve a lot of problems for us. If you have encountered any similar issue, how have you approached them in ASpace? Thanks, Olivia -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy.braitsch at bc.edu Thu Feb 3 10:20:29 2022 From: amy.braitsch at bc.edu (Amy Braitsch) Date: Thu, 3 Feb 2022 10:20:29 -0500 Subject: [Archivesspace_Users_Group] Approach to describing single items Message-ID: Hey there ASpace list, At BC we're working toward implementing the PUI. To get there we've remediated a lot of legacy data and data practice. An area we haven't handled yet is what to do with single item resources (e.g. a diary). We've been inconsistent and need to settle on one approach. I'd like to know what you've found to be the best approach and why. Here are the two approaches we?ve taken. I see pluses and minuses: Option 1: Resource without archival objects, with instances/digital objects associated at the collection level. This makes logical sense, but the PUI displays these containers/digital objects differently than on collections with instances on the archival objects. The biggest difference in the PUI is that thumbnails are omitted from the digital objects when they?re at this level. On the staff side, the collection-level resource lacks the ref ID and CUI field, which we use as part of our digital object file naming convention. Option 2: Resource with a child archival object (repeating the title of the parent), with instances/digital objects associated with the AO. This seems like redundant record-keeping. It requires more researcher clicks in the PUI, but the display of the instances are consistent with other collections. On the staff side, the ref ID and CUI are available for use in our digital object workflows. We rely on ASpace for collection management and description. As we move into using it for discovery as well, I want to be sure that we're following road-tested best practices. Thanks for your help! Amy -------------------- Amy Braitsch (pronouns: she/her/hers) Head of Archives, Burns Library, Boston College, amy.braitsch at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Thu Feb 3 15:35:57 2022 From: cory_nimer at byu.edu (Cory Nimer) Date: Thu, 3 Feb 2022 20:35:57 +0000 Subject: [Archivesspace_Users_Group] Approach to describing single items In-Reply-To: References: Message-ID: Amy, We use the Option 1 here, though we also have had some concerns with the PUI thumbnail display at this level. Looking ahead, we are hoping that the display issues will be fixed with the 3.2.0 release--the release candidate notes reference ANW-810 (https://archivesspace.atlassian.net/browse/ANW-810), which seems to cover this use case. There are also some proposed fixes for this issue in the draft specification for ANW-1209 (https://archivesspace.atlassian.net/browse/ANW-1209), which was under discussion by the Development Prioritization Subteam in their meeting on Tuesday (https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3022716936/2022-02-01+Meeting+notes). Best, Cory Nimer University Archivist Brigham Young University From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Amy Braitsch Sent: Thursday, February 3, 2022 8:20 AM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Approach to describing single items Hey there ASpace list, At BC we're working toward implementing the PUI. To get there we've remediated a lot of legacy data and data practice. An area we haven't handled yet is what to do with single item resources (e.g. a diary). We've been inconsistent and need to settle on one approach. I'd like to know what you've found to be the best approach and why. Here are the two approaches we?ve taken. I see pluses and minuses: Option 1: Resource without archival objects, with instances/digital objects associated at the collection level. This makes logical sense, but the PUI displays these containers/digital objects differently than on collections with instances on the archival objects. The biggest difference in the PUI is that thumbnails are omitted from the digital objects when they?re at this level. On the staff side, the collection-level resource lacks the ref ID and CUI field, which we use as part of our digital object file naming convention. [https://lh3.googleusercontent.com/h1gOnm4gLUMsOkM7ShuPikZJMpY8ZwsQAj-gVGJws5K6m75MIa8qjzUyHfMiGRvcAX4ELJg0GE2T5Zk1lPIUTrkuRkTkc96fU47C0ONY87t2XoRh3K48xQ1ieyjZ_jBOEf8TShj9] Option 2: Resource with a child archival object (repeating the title of the parent), with instances/digital objects associated with the AO. This seems like redundant record-keeping. It requires more researcher clicks in the PUI, but the display of the instances are consistent with other collections. On the staff side, the ref ID and CUI are available for use in our digital object workflows. [https://lh6.googleusercontent.com/4lxCTd6c0IIlfWYIXOjWgGv38DLlzakRsLwBQjjyso6KB6yTm3YaydBDG8Ask6SX1Zsu39SiVua3y0TTEce0zGURxlfT1hrJhKaYt8tAfjljaATqQR2BsgcgB7SEffpYIFIuGlBr] We rely on ASpace for collection management and description. As we move into using it for discovery as well, I want to be sure that we're following road-tested best practices. Thanks for your help! Amy -------------------- Amy Braitsch (pronouns: she/her/hers) Head of Archives, Burns Library, Boston College, amy.braitsch at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Fri Feb 4 09:39:46 2022 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Fri, 4 Feb 2022 14:39:46 +0000 Subject: [Archivesspace_Users_Group] Approach to describing single items In-Reply-To: References: Message-ID: Hi Amy, We use Option 2 and also rely on the CUI for Digital Object IDs and downstream digitization processes. We used this same pattern in our legacy EAD authoring/discovery system in a component description (?) and continued it into aspace. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 Teleworking M-F 8:00AM ? 4:30PM Eastern Time each day until further notice From: Cory Nimer Sent: Thursday, February 3, 2022 3:36 PM To: amy.braitsch at bc.edu; Archivesspace Users Group Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Approach to describing single items CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. Amy, We use the Option 1 here, though we also have had some concerns with the PUI thumbnail display at this level. Looking ahead, we are hoping that the display issues will be fixed with the 3.2.0 release--the release candidate notes reference ANW-810 (https://archivesspace.atlassian.net/browse/ANW-810), which seems to cover this use case. There are also some proposed fixes for this issue in the draft specification for ANW-1209 (https://archivesspace.atlassian.net/browse/ANW-1209), which was under discussion by the Development Prioritization Subteam in their meeting on Tuesday (https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3022716936/2022-02-01+Meeting+notes). Best, Cory Nimer University Archivist Brigham Young University From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Amy Braitsch Sent: Thursday, February 3, 2022 8:20 AM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Approach to describing single items Hey there ASpace list, At BC we're working toward implementing the PUI. To get there we've remediated a lot of legacy data and data practice. An area we haven't handled yet is what to do with single item resources (e.g. a diary). We've been inconsistent and need to settle on one approach. I'd like to know what you've found to be the best approach and why. Here are the two approaches we?ve taken. I see pluses and minuses: Option 1: Resource without archival objects, with instances/digital objects associated at the collection level. This makes logical sense, but the PUI displays these containers/digital objects differently than on collections with instances on the archival objects. The biggest difference in the PUI is that thumbnails are omitted from the digital objects when they?re at this level. On the staff side, the collection-level resource lacks the ref ID and CUI field, which we use as part of our digital object file naming convention. [https://lh3.googleusercontent.com/h1gOnm4gLUMsOkM7ShuPikZJMpY8ZwsQAj-gVGJws5K6m75MIa8qjzUyHfMiGRvcAX4ELJg0GE2T5Zk1lPIUTrkuRkTkc96fU47C0ONY87t2XoRh3K48xQ1ieyjZ_jBOEf8TShj9] Option 2: Resource with a child archival object (repeating the title of the parent), with instances/digital objects associated with the AO. This seems like redundant record-keeping. It requires more researcher clicks in the PUI, but the display of the instances are consistent with other collections. On the staff side, the ref ID and CUI are available for use in our digital object workflows. [https://lh6.googleusercontent.com/4lxCTd6c0IIlfWYIXOjWgGv38DLlzakRsLwBQjjyso6KB6yTm3YaydBDG8Ask6SX1Zsu39SiVua3y0TTEce0zGURxlfT1hrJhKaYt8tAfjljaATqQR2BsgcgB7SEffpYIFIuGlBr] We rely on ASpace for collection management and description. As we move into using it for discovery as well, I want to be sure that we're following road-tested best practices. Thanks for your help! Amy -------------------- Amy Braitsch (pronouns: she/her/hers) Head of Archives, Burns Library, Boston College, amy.braitsch at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Feb 4 11:56:23 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 4 Feb 2022 16:56:23 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 3.2.0 now available Message-ID: Hello ArchivesSpace members, ArchivesSpace is announcing the availability of v3.2.0. You can download it at https://github.com/archivesspace/archivesspace/releases/. This release marks the previously announced transition to external Solr. Links to documentation, a tutorial video, and other information are available at https://archivesspace.org/archives/7151. Beyond external Solr, there are several items to note in the release: * The Smithsonian worked with Hudson Molonglo to improve the ARKs feature. The scope of the work is described at https://github.com/archivesspace/archivesspace/pull/2437. * There is a new custom reports feature that was worked on by several developers, including former Tech Lead Laney McGlohon. * Other highlights include small improvements to the spreadsheet importers, a new page within the application for downloading templates, and various small bug fixes and features prioritized by the Development Prioritization sub-team. Thanks to all of the community members who contributed code for this release: Andrew Morrison, Blake Carver, Dean Farrell, Jacob Shelby, James Bullen, Laney McGlohon, Lora Woodford, Mario Terranova, Mark Triggs, Michael Glanznig, Payten Giles, and Saron Tran. As always, program team members Brian Hoffman and Mark Cooper, as well as contractors Manny Rodriguez and Brian Zelip, wrote and/or reviewed substantial code for the release. Thanks also to our community groups, especially the Testing sub-team, for their efforts. 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. This is the fall 2021 release from the roadmap that was originally projected for December. Items that were projected for this release that did not make it in have been shifted to future releases. If you have questions or need any assistance, please let us know. 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 PGalligan at rockarch.org Fri Feb 4 13:20:22 2022 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Fri, 4 Feb 2022 18:20:22 +0000 Subject: [Archivesspace_Users_Group] Performance hits with updated agents module? Message-ID: Hi all, Has anyone done any performance benchmarking between AS version 2.x and AS version 3.1.x? We?ve updated a few months ago and some of our GET requests are taking way longer than we?d expect. This request: GET /agents/people?all_ids=True&page_size=100&page=1 took about 2.5 minutes to complete. D, [2022-02-02T13:55:04.329994 #1804489] DEBUG -- : Thread-65736: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"321644"}, ["{\"first_page\":1,\"last_page\":12,\"this_page\":1,\"total\":1176,\"results\":[{\"lock_version\":0,\"publish\":false,\"create_time\":\"2014-12-05T20:32:16Z\",\"system_mtime\":\"2021-12-03T21:53:20Z\",\"user_mtime\":\"2014-12-05T20:32:16Z\",\"is_slug_auto\":false,\"jsonmodel_type\":\"agent_person\",\"agent_contacts\":[],\"agent_record_controls\":[],\"agent_alternate_sets\":[],\"age... in 154446ms Has anyone else experienced this? It seems to have started after we upgraded. -Patrick Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Fri Feb 4 13:29:17 2022 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Fri, 4 Feb 2022 13:29:17 -0500 Subject: [Archivesspace_Users_Group] Performance hits with updated agents module? In-Reply-To: References: Message-ID: Hey Patrick, I don't have a working 2.x install running, but this is what I got on 3.0.2 $ time curl -H "X-ArchivesSpace-Session: $SESSION" -X GET " https://my-archivesspace-server:8089/agents/people?all_ids=True&page_size=100&page=1 " {"first_page":1,"last_page":130,"this_page":1,"total":12971,"results":[snip]} real 0m12.801s user 0m0.018s sys 0m0.007s On Fri, Feb 4, 2022 at 1:20 PM Galligan, Patrick wrote: > Hi all, > > > > Has anyone done any performance benchmarking between AS version 2.x and AS > version 3.1.x? We?ve updated a few months ago and some of our GET requests > are taking way longer than we?d expect. > > > > This request: GET /agents/people?all_ids=True&page_size=100&page=1 took > about 2.5 minutes to complete. > > > > D, [2022-02-02T13:55:04.329994 #1804489] DEBUG -- : Thread-65736: > Responded with [200, {"Content-Type"=>"application/json", > "Cache-Control"=>"private, must-revalidate, max-age=0", > "Content-Length"=>"321644"}, > ["{\"first_page\":1,\"last_page\":12,\"this_page\":1,\"total\":1176,\"results\":[{\"lock_version\":0,\"publish\":false,\"create_time\":\"2014-12-05T20:32:16Z\",\"system_mtime\":\"2021-12-03T21:53:20Z\",\"user_mtime\":\"2014-12-05T20:32:16Z\",\"is_slug_auto\":false,\"jsonmodel_type\":\"agent_person\",\"agent_contacts\":[],\"agent_record_controls\":[],\"agent_alternate_sets\":[],\"age... > in 154446ms > > > > Has anyone else experienced this? It seems to have started after we > upgraded. > > > > -Patrick > > Rockefeller Archive Center > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=_DsNVvE0MidyDzdUOYchWsIErjGtgLba7OOoi6MzJhM&m=U7YhID3-trQ6xjjkkARr6YG0qrVlvMNeDbR1V6hzqclVIvUvemqXY-4PgyC4T9s1&s=SvrniU7gsnaDQJYASCA-Ard225aSpqzg5LCV5axoFDA&e= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Fri Feb 4 14:36:19 2022 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Fri, 4 Feb 2022 19:36:19 +0000 Subject: [Archivesspace_Users_Group] [EXTERNAL] Re: Performance hits with updated agents module? In-Reply-To: References: Message-ID: I haven?t noticed any meaningful increase in our jmeter tests for agents between 2.8.1 and 3.1.1. 8 seconds is the max for the 50 concurrent users test (over VPN), but 600ms is the average for 50. That?s on a QA string with only 2GB of heap. John From: Donald Mennerich Sent: Friday, February 4, 2022 1:29 PM To: Archivesspace Users Group Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Performance hits with updated agents module? CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. Hey Patrick, I don't have a working 2.x install running, but this is what I got on 3.0.2 $ time curl -H "X-ArchivesSpace-Session: $SESSION" -X GET "https://my-archivesspace-server:8089/agents/people?all_ids=True&page_size=100&page=1" {"first_page":1,"last_page":130,"this_page":1,"total":12971,"results":[snip]} real 0m12.801s user 0m0.018s sys 0m0.007s On Fri, Feb 4, 2022 at 1:20 PM Galligan, Patrick > wrote: Hi all, Has anyone done any performance benchmarking between AS version 2.x and AS version 3.1.x? We?ve updated a few months ago and some of our GET requests are taking way longer than we?d expect. This request: GET /agents/people?all_ids=True&page_size=100&page=1 took about 2.5 minutes to complete. D, [2022-02-02T13:55:04.329994 #1804489] DEBUG -- : Thread-65736: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"321644"}, ["{\"first_page\":1,\"last_page\":12,\"this_page\":1,\"total\":1176,\"results\":[{\"lock_version\":0,\"publish\":false,\"create_time\":\"2014-12-05T20:32:16Z\",\"system_mtime\":\"2021-12-03T21:53:20Z\",\"user_mtime\":\"2014-12-05T20:32:16Z\",\"is_slug_auto\":false,\"jsonmodel_type\":\"agent_person\",\"agent_contacts\":[],\"agent_record_controls\":[],\"agent_alternate_sets\":[],\"age... in 154446ms Has anyone else experienced this? It seems to have started after we upgraded. -Patrick Rockefeller Archive Center _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=_DsNVvE0MidyDzdUOYchWsIErjGtgLba7OOoi6MzJhM&m=U7YhID3-trQ6xjjkkARr6YG0qrVlvMNeDbR1V6hzqclVIvUvemqXY-4PgyC4T9s1&s=SvrniU7gsnaDQJYASCA-Ard225aSpqzg5LCV5axoFDA&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Feb 7 10:10:52 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 7 Feb 2022 15:10:52 +0000 Subject: [Archivesspace_Users_Group] SNAC Cooperative Presentation Announcement: ArchivesSpace SNAC Plugin Presentation Message-ID: [Posted on behalf of our colleagues at the SNAC Cooperative] The SNAC Cooperative is developing an ArchivesSpace plugin to facilitate efficient data exchange. An hour long presentation demonstrating the functional features of the plugin with following discussion is scheduled for March 8, 2022, 2:00pm ET/11:00am PT. The presenters will be Jason Jordan, software developer at the University of Virginia Library, and Daniel Pitti, director of the SNAC Cooperative. Date: March 8, 2022 Time: 2:00pm ? 3:00pm ET (11:00am ? 12:00pm PT) Where: zoom Registration: https://virginia.zoom.us/meeting/register/tJEqdeuvpz4vGtOv65JpTcaOjQUO9nEPWSrD From within ArchivesSpace, the demonstration will cover both pulling data from and pushing data to SNAC. Though pushing data to SNAC will require being a member of the SNAC Cooperative, any ArchivesSpace user will be able to pull data from SNAC. In particular the demonstration will cover: -SNAC environment management in ArchivesSpace preferences -Import of SNAC agents to new ArchivesSpace agents -Export of ArchivesSpace agents (optionally including linked resources) to SNAC -Export of ArchivesSpace record descriptions (optionally including linked agents) to SNAC -Linking ArchivesSpace agents/record descriptions to existing SNAC agents and resource descriptions -Unlinking ArchivesSpace agents/record descriptions from existing SNAC agents and resource descriptions The SNAC plugin ia available on Github: https://github.com/snac-cooperative/snac_aspace_plugin The session will be recorded and made available as soon as feasible after the presentation at https://portal.snaccooperative.org/node/501 If you have questions about the presentation or questions about the SNAC Cooperative, please feel free to contact the Cooperative at snac.cooperative at gmail.com 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: 1 bytes Desc: image001.jpg URL: From jwalske at minlib.net Mon Feb 7 10:45:59 2022 From: jwalske at minlib.net (Jared Walske) Date: Mon, 7 Feb 2022 10:45:59 -0500 Subject: [Archivesspace_Users_Group] Error when trying to import XML file Message-ID: Hi all, I was trying to import a bunch of collection data via an MarcXMLfile and got the following error message: -- The following errors were found: dates_of_existence/0/expression : is required unless a begin or end date is given dates_of_existence/0/begin : is required unless an expression or an end date is given dates_of_existence/0/end : is required unless an expression or a begin date is given For JSONModel(:agent_person): #"agent_person", "agent_contacts"=>[], "linked_agent_roles"=>[], "external_documents"=>[], "notes"=>[], "used_within_repositories"=>[], "used_within_published_repositories"=>[], "dates_of_existence"=>[{"jsonmodel_type"=>"date", "date_type"=>"single", "label"=>"existence"}], "is_slug_auto"=>true, "names"=>[{"jsonmodel_type"=>"name_person", "use_dates"=>[], "authorized"=>false, "is_display_name"=>false, "sort_name_auto_generate"=>true, "name_order"=>"inverted", "primary_name"=>"Magalha?es", "rest_of_name"=>"Ferna?o de", "dates"=>"-1521", "source"=>"lcsh"}], "related_agents"=>[], "uri"=>"/agents/people/import_16b1f035-4fb0-46f7-af70-989cadc56c27", "publish"=>true}> -- I had previously tested this with a cut down version of the same data that imported just fine, so I'm not sure what exactly the issue is or what I need to do to fix this so the file will import correctly. Any suggestions? Thanks, Jared -- Jared Walske (*he/him*) Reference Librarian The Public Library of Brookline jwalske at minlib.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jessica.wagnerwebster at baruch.cuny.edu Mon Feb 7 11:23:50 2022 From: jessica.wagnerwebster at baruch.cuny.edu (Jessica Wagner Webster) Date: Mon, 7 Feb 2022 16:23:50 +0000 Subject: [Archivesspace_Users_Group] digital object import troubleshooting Message-ID: <2d62d37d8ac1408191683cef9606ec19@mbx2v-b.BC.Baruch.Cuny.Edu> Hi all, I?m trying out the digital object import spreadsheet and while I had it work successfully before with one collection, I?m getting error messages now with a different collection and wondering if someone could help me troubleshoot. I?m trying to attach a digital object to folder-level record (is this possible with the spreadsheet import)? I?ve put in the record?s aspace ID as I see it in the resource record, but I keep getting this message: Cannot find archival object with Ref ID aspace_984xxxx etc etc I have tried using the EADID, the Collection-level ID, and the folder-level ID in the spreadsheet, but this keeps happening. What might I be doing wrong? Any suggestions? Thank you! Jessica Webster Digital Initiatives Librarian, Assistant Professor Baruch College, Newman Library Jessica.WagnerWebster at baruch.cuny.edu Note: I do not expect a response outside of standard business hours. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Jared Walske Sent: Monday, February 7, 2022 10:46 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Error when trying to import XML file Hi all, I was trying to import a bunch of collection data via an MarcXMLfile and got the following error message: -- The following errors were found: dates_of_existence/0/expression : is required unless a begin or end date is given dates_of_existence/0/begin : is required unless an expression or an end date is given dates_of_existence/0/end : is required unless an expression or a begin date is given For JSONModel(:agent_person): #"agent_person", "agent_contacts"=>[], "linked_agent_roles"=>[], "external_documents"=>[], "notes"=>[], "used_within_repositories"=>[], "used_within_published_repositories"=>[], "dates_of_existence"=>[{"jsonmodel_type"=>"date", "date_type"=>"single", "label"=>"existence"}], "is_slug_auto"=>true, "names"=>[{"jsonmodel_type"=>"name_person", "use_dates"=>[], "authorized"=>false, "is_display_name"=>false, "sort_name_auto_generate"=>true, "name_order"=>"inverted", "primary_name"=>"Magalha?es", "rest_of_name"=>"Ferna?o de", "dates"=>"-1521", "source"=>"lcsh"}], "related_agents"=>[], "uri"=>"/agents/people/import_16b1f035-4fb0-46f7-af70-989cadc56c27", "publish"=>true}> -- I had previously tested this with a cut down version of the same data that imported just fine, so I'm not sure what exactly the issue is or what I need to do to fix this so the file will import correctly. Any suggestions? Thanks, Jared -- Jared Walske (he/him) Reference Librarian The Public Library of Brookline jwalske at minlib.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Mon Feb 7 14:06:50 2022 From: livsolis at utexas.edu (Olivia S Solis) Date: Mon, 7 Feb 2022 13:06:50 -0600 Subject: [Archivesspace_Users_Group] Generic top container note? In-Reply-To: References: Message-ID: Hi Anna, There was not an issue filed, but you inspired me to file my first JIRA issue! Hopefully, I filled out everything correctly, but here is the ticket if you or anyone else wants to add any comments: https://archivesspace.atlassian.net/browse/ANW-1488 Thanks! Olivia On Wed, Feb 2, 2022 at 4:04 PM Anna Haywood wrote: > Hello Olivia, > > > > This is a very late reply but I would like to second this idea. Our > institution would be very interested in having a generic note field on top > containers. > > > > When we create accession records, we attach container instances to the > accession record to keep track of which unprocessed boxes came with which > accession. Rather than link to an external inventory, or have to create > component records for unprocessed materials, we would prefer to be able to > give a brief note about the container?s contents in this field. > > > > Please let me know if you open a development ticket because I would > strongly support it. > > > > Best, > > Anna > > > > --- > > > *Anna Haywood*Archiviste > Archivist > > > *Centre Canadien d'ArchitectureCanadian Centre for Architecture* > 1920, rue Baile, Montr?al, Qu?bec, Canada, H3H 2S6 > +1 5149397001x1368 > cca.qc.ca > > Twitter | Instagram > | Facebook > | YouTube > > > Qu'est-ce qui vous pousse ? privil?gier une caract?ristique plut?t qu'une > autre pour d?crire un objet? > What makes you pick one characteristic over another to describe an object? > > > Inscrivez-vous > > pour recevoir de nos nouvelles. > Sign up > > to get news from us. > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia > S Solis > *Sent:* Monday, December 13, 2021 1:13 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Generic top container note? > > > > Hey all, > > > > I was wondering if any other institutions out there had an interest in a > field that we have consistently found a need for: a generic note for staff > attached to top container records. Reasons have included: > > - We renamed a box. Because boxes may be part of citations or > referenced in numerous places in internal documentation, staff sometimes > goes to absurd lengths to keep an old box number when it is no longer > relevant or the box really should be renamed. Having the old box # in a > note that is indexed gets rid of that problem as there is an immediately > obvious place to document the change. Staff and researchers often look for > a box number they've found in citations and notes. Keeping this information > in a note on the container record would allow us to locate the correct > container through a key-word search. > - We merged two boxes into one. > - We want to document the space left in a box and ASpace currently > allows no way to do that. > - The box has a nonstandard size (no container profile yet) > - The box needs some upkeep (new label, new container, it's missing a > lid) > - We can't find a box. It's happened. We want to document all the > places we've looked > - Other internal notes about the box's status, condition, barcode or > indicator or history, restriction status. > > It seems like ASpace wants us to document information about top containers > in other places including Processing Notes attached to specific archival > objects/resource records/accessions, assessments, location notes. Location > notes sometimes could work, but we have limited staff time and can't update > numerous records (all the archival objects/collections attached to a box or > assessments attached to AOs/collections) to document a single change. > > > > A generic note attached to top containers would solve a lot of problems > for us. If you have encountered any similar issue, how have you approached > them in ASpace? > > > > Thanks, > > Olivia > > > > -- > > Olivia Solis, MSIS (she/her) > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahaywood at cca.qc.ca Mon Feb 7 14:12:22 2022 From: ahaywood at cca.qc.ca (Anna Haywood) Date: Mon, 7 Feb 2022 19:12:22 +0000 Subject: [Archivesspace_Users_Group] Generic top container note? In-Reply-To: References: Message-ID: Wonderful. Thanks Olivia, I appreciate it! I have added my comments to your development ticket. Best, Anna --- Anna Haywood Archiviste Archivist Centre Canadien d'Architecture Canadian Centre for Architecture 1920, rue Baile, Montr?al, Qu?bec, Canada, H3H 2S6 +1 5149397001x1368 cca.qc.ca Twitter | Instagram | Facebook | YouTube Qu'est-ce qui vous pousse ? privil?gier une caract?ristique plut?t qu'une autre pour d?crire un objet? What makes you pick one characteristic over another to describe an object? Inscrivez-vous pour recevoir de nos nouvelles. Sign up to get news from us. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Olivia S Solis Sent: Monday, February 7, 2022 2:07 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Generic top container note? Hi Anna, There was not an issue filed, but you inspired me to file my first JIRA issue! Hopefully, I filled out everything correctly, but here is the ticket if you or anyone else wants to add any comments: https://archivesspace.atlassian.net/browse/ANW-1488 Thanks! Olivia On Wed, Feb 2, 2022 at 4:04 PM Anna Haywood > wrote: Hello Olivia, This is a very late reply but I would like to second this idea. Our institution would be very interested in having a generic note field on top containers. When we create accession records, we attach container instances to the accession record to keep track of which unprocessed boxes came with which accession. Rather than link to an external inventory, or have to create component records for unprocessed materials, we would prefer to be able to give a brief note about the container's contents in this field. Please let me know if you open a development ticket because I would strongly support it. Best, Anna --- Anna Haywood Archiviste Archivist Centre Canadien d'Architecture Canadian Centre for Architecture 1920, rue Baile, Montr?al, Qu?bec, Canada, H3H 2S6 +1 5149397001x1368 cca.qc.ca Twitter | Instagram | Facebook | YouTube Qu'est-ce qui vous pousse ? privil?gier une caract?ristique plut?t qu'une autre pour d?crire un objet? What makes you pick one characteristic over another to describe an object? Inscrivez-vous pour recevoir de nos nouvelles. Sign up to get news from us. From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Olivia S Solis Sent: Monday, December 13, 2021 1:13 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Generic top container note? Hey all, I was wondering if any other institutions out there had an interest in a field that we have consistently found a need for: a generic note for staff attached to top container records. Reasons have included: * We renamed a box. Because boxes may be part of citations or referenced in numerous places in internal documentation, staff sometimes goes to absurd lengths to keep an old box number when it is no longer relevant or the box really should be renamed. Having the old box # in a note that is indexed gets rid of that problem as there is an immediately obvious place to document the change. Staff and researchers often look for a box number they've found in citations and notes. Keeping this information in a note on the container record would allow us to locate the correct container through a key-word search. * We merged two boxes into one. * We want to document the space left in a box and ASpace currently allows no way to do that. * The box has a nonstandard size (no container profile yet) * The box needs some upkeep (new label, new container, it's missing a lid) * We can't find a box. It's happened. We want to document all the places we've looked * Other internal notes about the box's status, condition, barcode or indicator or history, restriction status. It seems like ASpace wants us to document information about top containers in other places including Processing Notes attached to specific archival objects/resource records/accessions, assessments, location notes. Location notes sometimes could work, but we have limited staff time and can't update numerous records (all the archival objects/collections attached to a box or assessments attached to AOs/collections) to document a single change. A generic note attached to top containers would solve a lot of problems for us. If you have encountered any similar issue, how have you approached them in ASpace? Thanks, Olivia -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Wed Feb 9 11:06:17 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 9 Feb 2022 16:06:17 +0000 Subject: [Archivesspace_Users_Group] Registration still available: Virtual ArchivesSpace Assessments Module Training February 23, 2022, 12:00pm-3:00pm ET/9:00am-12:00pm PT In-Reply-To: <8170C463-65F5-4593-A477-659D48BE8A13@lyrasis.org> References: <56A2124E-DB2A-41C6-A363-483B5DAC742B@lyrasis.org> <8170C463-65F5-4593-A477-659D48BE8A13@lyrasis.org> Message-ID: Dear ArchivesSpace users, Registration is still open for the three-hour ArchivesSpace Assessments Module workshop on February 23, 2022, from 12:00pm-3:00pm ET/9:00am-12:00pm PT. During this workshop, ArchivesSpace trainer Brittany Newberry will cover using the assessments module in ArchivesSpace including completing assessments in ArchivesSpace, adding values to the assessments template and importing assessments using CSV. Attendees are expected to have experience with ArchivesSpace or to have completed the ArchivesSpace Basics training. A copy of the agenda is linked below. ArchivesSpace Assessments Module Training (Tentative Agenda) Date: February 23, 2022 Time: 12:00pm-3:00pm ET / 9:00am-12:00pm PT Trainer: Brittany Newberry Registration: https://lyrasis.zoom.us/webinar/register/WN_Yo9IfEoSRY-IePzdADgLzA Registration is now open to anyone using ArchivesSpace. In order to make training available to as many organizations and users as possible, registration will be limited to three (3) attendees per organization for virtual trainings. All community-wide virtual trainings will be recorded. These recordings will be made available via the ArchivesSpace website and YouTube channel. You do not need to register for the training to have access to the recordings. Over the past year, the Trainers Corps has offered regularly scheduled workshops and office hours covering a variety of topics on all things ArchivesSpace. These virtual, community-wide trainings are part of a 12-month pilot project by the Trainers Corps to assess community interest and training needs. 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, email ArchivesSpaceHome at lyrasis.org. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndroark at anderson.edu Fri Feb 11 10:03:12 2022 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Fri, 11 Feb 2022 10:03:12 -0500 Subject: [Archivesspace_Users_Group] Agent Records with missing information Message-ID: Hi all, I am curious how others treat entering agent records with only very partial information. We are currently doing item level processing on a significant collection where many of the subjects and even creators of the records are only described as "Bro. Smith" or "Sister Jones." Sometimes it is clear the same person is being referenced in multiple records, but without an identified first name. Do you place the humble honorific in the title field? Include a note on the agent record? Place [unknown] in the rest of name field? I paged through DACS but didn't find any references to unknown first names. Thanks for any advice. *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: From benn.joseph at northwestern.edu Fri Feb 11 15:01:01 2022 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Fri, 11 Feb 2022 20:01:01 +0000 Subject: [Archivesspace_Users_Group] Agent Records with missing information In-Reply-To: References: Message-ID: Hi Nic, This is a very timely question as we?ve been talking about the same thing here?basically we try not to create Agent records for names that cannot be established in the NAF. So for your examples below, we probably would not create an Agent record for those and would instead try to find another approach. If we did want to make an Agent record for creators like "Bro. Smith" or "Sister Jones?, we?d follow RDA rules where the honorific goes into the Title field (rather than DACS, which I?m not sure covers name construction). Here?s an example: [cid:image001.png at 01D81F4F.AC40B970] Cheers, --Benn Benn Joseph (he/him/his) Head, Collections Services McCormick Library of Special Collections & University Archives Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Nic Stanton-Roark Sent: Friday, February 11, 2022 9:03 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Agent Records with missing information Hi all, I am curious how others treat entering agent records with only very partial information. We are currently doing item level processing on a significant collection where many of the subjects and even creators of the records are only described as "Bro. Smith" or "Sister Jones." Sometimes it is clear the same person is being referenced in multiple records, but without an identified first name. Do you place the humble honorific in the title field? Include a note on the agent record? Place [unknown] in the rest of name field? I paged through DACS but didn't find any references to unknown first names. Thanks for any advice. [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: image001.png Type: image/png Size: 34342 bytes Desc: image001.png URL: From Jessica.Crouch at lyrasis.org Mon Feb 14 12:10:49 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 14 Feb 2022 17:10:49 +0000 Subject: [Archivesspace_Users_Group] Take a Break with ArchivesSpace returns March 4 Message-ID: <110A1ECB-C261-434E-B1DB-4C02E290AE96@lyrasis.org> Dear ArchivesSpace users, Whether you?ve continued to work from home, have returned to the office, or find yourself stuck somewhere in the middle, we could all use a break. In that spirit, ArchivesSpace will be reinstating our popular casual zoom open calls on Fridays. With a welcoming and robust member community all over the world, ArchivesSpace can offer camaraderie and relaxation, no matter the current state of the world. Beginning Friday, March 4th, we will have casual open calls via zoom at 12pm ET each Friday. We won?t be developing agendas or presentations for these calls. We just want to provide an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Whether you can attend once or plan to be there every Friday, these calls are open to everyone but registration is required to join. Register to join any open call at https://lyrasis.zoom.us/meeting/register/tZcldOGuqjotE9cNSaa6j45issVCKrEQKQYv We seek to provide a welcoming, fun, and safe community experience for everyone. The full text of the code of conduct is available at https://archivesspace.org/archivesspace-code-of-conduct. Please email ArchivesSpaceHome at lyrasis.org with any questions. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Feb 15 09:39:26 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 15 Feb 2022 14:39:26 +0000 Subject: [Archivesspace_Users_Group] Call for speakers for the ArchivesSpace 4th Annual Online Forum In-Reply-To: References: Message-ID: [Graphic with text announcing the ArchivesSpace online forum. a 2 day virtual event on March 21 and 22, 2022] Dear ArchivesSpace Users, Submissions remain open for both session proposals and ideas for topics for our 4th annual Online Forum. Taking place March 21-22, 2022, our Online Forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels. A schedule and information about how to register for the event will be released closer to March. Anyone who uses ArchivesSpace or is interested in ArchivesSpace is welcome to attend. We are now accepting both session proposals and ideas for topics via our online form at https://forms.gle/8QC48JmHeSmZYEZT8. We will be reviewing proposals on a rolling basis, so we encourage you to get your proposals in early. Submissions will be closed on February 28, 2022, with final notification by March 4, 2022. As in years past, our Online Forum will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace and all submissions are welcome. The ArchivesSpace program team is particularly interested in presentations or facilitated discussions related to the following topics: * Using ArchivesSpace in a work from home environment * Using ArchivesSpace as a long arranger or at a small archive * Managing paraprofessionals, students and volunteers using ArchivesSpace * Demonstrations of workflows using different modules or features of the application * Examples of anti-racism, anti-colonialism and redescription work being executed in ArchivesSpace * Demonstrations of plugins or tools you?ve developed to make your work in ArchivesSpace easier The length of the forum will be determined by what kind of program we can put together from submissions. We know that everyone is stretched thin right now and we appreciate any and all submissions. We anticipate recording many parts of the forum, but for it to be a success we will also need as many live participants as possible. We encourage you to dip in and out of the live program as much as you can. You will no doubt ?meet? a different set of colleagues each time. We?re looking forward to a great event, with your help! If you have questions, please email us at ArchivesSpaceHome at lyrasis.org. Best, Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 257205 bytes Desc: image001.jpg URL: From Joshua.D.Shaw at dartmouth.edu Tue Feb 15 20:26:58 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 16 Feb 2022 01:26:58 +0000 Subject: [Archivesspace_Users_Group] Translations/Localizations for Content & PUI Locales? Message-ID: Hey Everyone We're wondering how others handle translations for descriptive content. Example would be for a community with dual primary languages - eg English and French. How would you handle descriptive metadata (title, scope content, etc) in both languages? Followup Q. In the SUI, a specific user can select the locale best suited for them so that labels are translated correctly (assuming the localization is available) Is there a way to allow an anonymous/public user to change the locale in the PUI so that the labels are changed to the selected language? I know you can set this globally, but I'm interested in allowing the user to choose. Thanks Joshua ___________________ Joshua Shaw (he, him) Library Web & Application Developer Digital Library Technologies Group Dartmouth College 603.646.0405 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Feb 16 12:08:55 2022 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 16 Feb 2022 17:08:55 +0000 Subject: [Archivesspace_Users_Group] Agent Dates of Existence Lost to Update 2.8.1 to 3.1.1 Message-ID: Dear all, Hello, this is Corey from the University of Georgia. We are testing an update to ArchivesSpace, going from version 2.8.1 to 3.1.1. During testing, we discovered that over 660 agent records lost their dates of existence information. Not all agents lost their dates of existence, however, with the vast majority migrating properly into 3.1.1. We are unsure why these agents in particular lost this info, but we know that the 3.0.0 release came out with two patches because of issues related to the dates of existence field (listserv email, JIRA ticket). Agents with range and single types are both affected. Has anyone encountered this issue before? What might be the cause? For reference, I'm adding the JSON of an agent that lost their date of expression during the migration, as well as screenshots of what our agent records look like on 2.8.1 and 3.1.1: "dates_of_existence": [ { "lock_version": 0, "begin": "1905", "end": "1983", "created_by": "cschmidt", "last_modified_by": "cschmidt", "create_time": "2021-02-23T14:45:47Z", "system_mtime": "2021-02-23T14:45:47Z", "user_mtime": "2021-02-23T14:45:47Z", "date_type": "range", "label": "existence", "jsonmodel_type": "date" } ], Any help or info would be appreciated. Thanks. Sincerely, Corey Corey Schmidt Special Collections Libraries | ArchivesSpace Project Manager Athens, GA 30605 Corey.Schmidt at uga.edu [University of Georgia] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8920 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: No_DOE_281.png Type: image/png Size: 45878 bytes Desc: No_DOE_281.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: No_DOE_311.png Type: image/png Size: 44790 bytes Desc: No_DOE_311.png URL: From ccauste1 at swarthmore.edu Wed Feb 16 13:31:41 2022 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Wed, 16 Feb 2022 13:31:41 -0500 Subject: [Archivesspace_Users_Group] ODBC advice Message-ID: Hi folks, My colleague is trying to set up an ODBC connection between ArchivesSpace and MS Access (read-only) and has hit a dead end. I set it up for myself about 7 years ago and so my memory is foggy. Has anyone done it recently or can offer assistance? The step that is tripping her up is setting up the Data Source (on a Windows machine) Thanks! Celia -- Celia Caust-Ellenbogen (she/her/hers ) (pronounce my name ) Friends Historical Library of Swarthmore College ccauste1 at swarthmore.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Thu Feb 17 11:04:20 2022 From: k-miller3 at northwestern.edu (Karen Miller) Date: Thu, 17 Feb 2022 16:04:20 +0000 Subject: [Archivesspace_Users_Group] ODBC advice In-Reply-To: References: Message-ID: Hi Celia, I had to redo my ODBC setting recently, so it?s relatively fresh in my mind. Here?s what I think is the relevant issue from our documentation at NUL: Set up an ODBC connection with the following: * Data Source Name: ArchivesSpace Production * Description: can be left blank * TCP/IP Server: [your TCP/IP server here] * Port: 3306 [this is the default ? yours may differ] * User: [check with your DBA for this] * Password: [check with your DBA for this] * Database: can be left blank until the connection is first made, then should be archivesspace If you want to check out your own configuration in the ODBC Data Source Administrator (click Configure to see how it?s set up for you), that should give you the TCP/IP server and the Port number. If you need fuller instructions, I can edit our documentation to hide the local settings and send it along. Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Celia Caust-Ellenbogen Sent: Wednesday, February 16, 2022 12:32 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ODBC advice Hi folks, My colleague is trying to set up an ODBC connection between ArchivesSpace and MS Access (read-only) and has hit a dead end. I set it up for myself about 7 years ago and so my memory is foggy. Has anyone done it recently or can offer assistance? The step that is tripping her up is setting up the Data Source (on a Windows machine) Thanks! Celia -- Celia Caust-Ellenbogen (she/her/hers) (pronounce my name) Friends Historical Library of Swarthmore College ccauste1 at swarthmore.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Feb 21 13:29:49 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 21 Feb 2022 18:29:49 +0000 Subject: [Archivesspace_Users_Group] Registration now open for the 2022 ArchivesSpace Online Forum Message-ID: [A picture of a globe with connecting lines of light. Text reads ArchivesSpace Online Forum, Two Day Virtual Event, March 21-22, 2022] Registration is now open for the 4th annual ArchivesSpace Online Forum! Taking place March 21-22, 2022, our online forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels. Anyone who uses ArchivesSpace or is interested in ArchivesSpace is welcome to attend. As in years past, this free event will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace. When: Presentations will be held March 21 from 5pm-8pm UTC / 10am-1pm PT / 1-4pm ET / 5pm-8pm GMT / 6-9pm CET (find your local time). Discussion sessions will be held March 22 from 1pm-4pm UTC / 6am-9am PT / 9am-12pm ET / 1pm-4pm GMT / 2pm-5pm CET (find your local time). Where: All online via Zoom, with opportunities to join via computer or phone. Who Can Attend: Anyone using or interested in using ArchivesSpace is welcome to attend some or all of the sessions on these days. This is a free event but registration is required. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3036282881/ArchivesSpace+Online+Forum+2022 Registrations for each day of the Forum are separate. You will need to register for each day you are interested in attending to guarantee your spot. Registration is linked in the agenda at the top of each day. We anticipate recording many parts of the forum, but for it to be a success we will also need as many live participants as possible. We encourage you to dip in and out of the live program as much as you can. You will no doubt ?meet? a different set of colleagues each time. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch at ArchivesSpaceHome at lyrasis.org with questions. We look forward to seeing many of you there! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 257204 bytes Desc: image001.jpg URL: From Corey.Schmidt at uga.edu Tue Feb 22 09:08:26 2022 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Tue, 22 Feb 2022 14:08:26 +0000 Subject: [Archivesspace_Users_Group] Agent Dates of Existence Lost to Update 2.8.1 to 3.1.1 In-Reply-To: References: Message-ID: All, Just as a follow-up, we were unable to figure out the exact cause of the missing dates of existence, but we believe it was an indexing error. Since the timing for the update prohibited us from running a re-index, we weren't able to confirm this. However, since many of the issues we've had in the past were solved with a re-index and no one else reported losing their data on this kind of jump, we feel reasonably confident in our assumption. I apologize for causing a stir. It's a good reminder that running a re-index should be a part of our error checking process and we will update our upgrade and testing procedures to account for this in future upgrades. Sincerely, Corey From: Corey Schmidt Sent: Wednesday, February 16, 2022 12:09 PM To: Archivesspace Users Group Subject: Agent Dates of Existence Lost to Update 2.8.1 to 3.1.1 Dear all, Hello, this is Corey from the University of Georgia. We are testing an update to ArchivesSpace, going from version 2.8.1 to 3.1.1. During testing, we discovered that over 660 agent records lost their dates of existence information. Not all agents lost their dates of existence, however, with the vast majority migrating properly into 3.1.1. We are unsure why these agents in particular lost this info, but we know that the 3.0.0 release came out with two patches because of issues related to the dates of existence field (listserv email, JIRA ticket). Agents with range and single types are both affected. Has anyone encountered this issue before? What might be the cause? For reference, I'm adding the JSON of an agent that lost their date of expression during the migration, as well as screenshots of what our agent records look like on 2.8.1 and 3.1.1: "dates_of_existence": [ { "lock_version": 0, "begin": "1905", "end": "1983", "created_by": "cschmidt", "last_modified_by": "cschmidt", "create_time": "2021-02-23T14:45:47Z", "system_mtime": "2021-02-23T14:45:47Z", "user_mtime": "2021-02-23T14:45:47Z", "date_type": "range", "label": "existence", "jsonmodel_type": "date" } ], Any help or info would be appreciated. Thanks. Sincerely, Corey Corey Schmidt Special Collections Libraries | ArchivesSpace Project Manager Athens, GA 30605 Corey.Schmidt at uga.edu [University of Georgia] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8920 bytes Desc: image001.png URL: From kbreneman at ubalt.edu Tue Feb 22 10:54:38 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Tue, 22 Feb 2022 15:54:38 +0000 Subject: [Archivesspace_Users_Group] How to display location information under Top Container field? Message-ID: In the ArchivesSpace sandbox, on the staff side of the interface, you can see location information for top containers (attached). Is this simply a feature that was added in one of the more recent ArchivesSpace releases, or is it an option that we can configure or enable? We are running version 2.8.0. Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2022-02-22 at 9.33.30 AM.png Type: image/png Size: 393267 bytes Desc: Screen Shot 2022-02-22 at 9.33.30 AM.png URL: From lorawoodford at gmail.com Tue Feb 22 11:02:41 2022 From: lorawoodford at gmail.com (Lora Woodford) Date: Tue, 22 Feb 2022 11:02:41 -0500 Subject: [Archivesspace_Users_Group] How to display location information under Top Container field? In-Reply-To: References: Message-ID: Hi Kyle, That functionality was added in v2.8.1: https://github.com/archivesspace/archivesspace/releases/tag/v2.8.1. See the call out for PR #1891: https://github.com/archivesspace/archivesspace/pull/1891 Best, Lora *Lora Woodford (she/her)* *Software Engineer II * On Tue, Feb 22, 2022 at 10:54 AM Kyle Breneman wrote: > In the ArchivesSpace sandbox, on the staff side of the interface, you can > see location information for top containers (attached). Is this simply a > feature that was added in one of the more recent ArchivesSpace releases, or > is it an option that we can configure or enable? We are running version > 2.8.0. > > > > *Kyle Breneman* > > Integrated Digital Services Librarian > > The University of Baltimore > > kbreneman at ubalt.edu > > *I believe in freedom of thought and * > > *freedom of speech. Do you?* > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcross at clemson.edu Tue Feb 22 11:49:35 2022 From: jcross at clemson.edu (James E. Cross) Date: Tue, 22 Feb 2022 16:49:35 +0000 Subject: [Archivesspace_Users_Group] Spreadsheet error translation Message-ID: Can anyone tell me what {"error":"undefined method `pretty_inspect' for #"} is indicating when I try and load a spreadsheet? Because of size limitations I had to divide up a subseries; I get this error when I try to add the next segment. Thank you. James Edward Cross, C.A. CLEMSON UNIVERSITY Manuscripts Archivist Special Collections and Archives Clemson University Libraries Box 343001 Clemson, SC 29634-3001 Phone: (864) 656-5182 Website: http://library.clemson.edu/depts/specialcollections/ Pronouns: he/him/his Traditional Cherokee Lands | Site of Fort Hill Plantation Please do not feel obligated to respond to this message outside of your normal working hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Tue Feb 22 12:18:30 2022 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 22 Feb 2022 17:18:30 +0000 Subject: [Archivesspace_Users_Group] Spreadsheet error translation In-Reply-To: References: Message-ID: This was a bit of a error "Turducken"... it's an error bug hiding the error. It was in older versions (maybe < 2.8?) and was fixed in a newer version (2.8.1 maybe?). If I'm remembering correctly an error is raised and that 'pretty_inspect' barfs on it and rather than showing the error, it just shows the pretty_inspect error. If I'm remembering correctly, again, the real error shows up in the logs, so take a look there for the real problem. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James E. Cross Sent: Tuesday, February 22, 2022 11:49 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Spreadsheet error translation Can anyone tell me what {"error":"undefined method `pretty_inspect' for #"} is indicating when I try and load a spreadsheet? Because of size limitations I had to divide up a subseries; I get this error when I try to add the next segment. Thank you. James Edward Cross, C.A. CLEMSON UNIVERSITY Manuscripts Archivist Special Collections and Archives Clemson University Libraries Box 343001 Clemson, SC 29634-3001 Phone: (864) 656-5182 Website: http://library.clemson.edu/depts/specialcollections/ Pronouns: he/him/his Traditional Cherokee Lands | Site of Fort Hill Plantation Please do not feel obligated to respond to this message outside of your normal working hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Tue Feb 22 15:03:19 2022 From: hanstra at nd.edu (Tom Hanstra) Date: Tue, 22 Feb 2022 15:03:19 -0500 Subject: [Archivesspace_Users_Group] Java 11 and 3.2.0? Message-ID: The documentation for ArchviesSpace 3.2.0 indicates that Java 11 is supported but most information I see is for Java 1.8 (which I assume is "Java 8"). Are we OK to use Java 11 for 3.2.0 or should I stick with 1.8? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Wed Feb 23 16:04:29 2022 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Wed, 23 Feb 2022 16:04:29 -0500 Subject: [Archivesspace_Users_Group] Metadata Standards AS Online Forum presentation - call for feedback Message-ID: Dear ArchivesSpace community, The Metadata Standards subgroup of the Technical Advisory Committee will be presenting at the ArchivesSpace Online Forum on Tuesday, March 22 at 9am EST. During our discussion we will talk about how we prioritize support for various standards and share news about our ongoing work on the MARC importer and the current MARC import mappings . We are also looking for community feedback on a specific metadata question, below. Please consider providing feedback beforehand by email to kws2126 at columbia.edu. Sample MARC records would be welcome! You may also offer your thoughts during the session. Issue: Improving the MARC 300 field import behavior Do you have MARC records for your archival holdings? Then you probably have 300 fields. The MARC 300 ?Physical Description? field contains extent information critical for archival control of material, like 34 linear feet, or 12 boxes (10 cubic feet). The current AS MARC importer only parses the 300 field according to one very specific pattern, and otherwise defaults to ?1 linear feet.? This means that anyone doing bulk import of MARC records may be silently wiping out their archivist-supplied extents without realizing it. A recent ticket also noted that 300$f fields are ignored entirely. What we would like from the community is how your 300 fields are structured, and how you would want 300 fields parsed on import. Sample data will help us make recommendations on what should be happening. For example, this is a common construction (from LC) that is NOT handled by the MARC importer: 300 ?a 5 ?f boxes ?a (3 ?f linear ft.) A discussion based on that sample might be: Should this pattern be supported? How should this be parsed? How should all of that punctuation be handled? The Metadata Standards subgroup will take what it learns and develop a specification for the desired behavior, but we need to hear from you. Sent with apologies for cross-posting. Best, Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University Pronouns: he/him/his 535 W. 114th St., New York, NY 10027 (212) 854-8483 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Feb 24 14:50:38 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 24 Feb 2022 19:50:38 +0000 Subject: [Archivesspace_Users_Group] Community contribution requested in the ArchivesSpace Inclusive Examples Project Message-ID: <1326FC44-9595-456A-A668-3C4B285CF1EB@lyrasis.org> Dear ArchivesSpace Users, In the wake of the George Floyd and Breonna Taylor murders, and in the spirit of protest that followed, the ArchivesSpace community began a conversation about what it could do to promote diversity and inclusion while combating systemic racism in our field. That continuing conversation has led to a series of initiatives that we will undertake in the coming years, including an Inclusive Examples project. For this important project, ArchivesSpace is delighted to be working with Brittany Newberry of Georgia State University to update the examples provided in its workshop materials and test databases. We want the examples to be more representative of the diverse institutions that use ArchivesSpace. We are interested in adding examples from the ArchivesSpace user community. Below is a list of record types and collection types for which we are looking. In addition, we have created an agreement to provide information and expectations for how the data shared will be used. If you are interested in participating, please email a signed agreement and the records you'd like to share in one of the formats listed. Email ArchivesSpaceHome at lyrasis.org by Wednesday, March 23 and we will forward your submission to Brittany Newberry for review. Feel free to contact us with any questions you may have. Possible Examples: Types of Records: * Resource records (EAD, MarcXML, CSV, Excel spreadsheet) * Accessions (MarcXML, Excel spreadsheet, CSV) * Digital Objects (CSV, Excel Spreadsheet) * Subjects and Agents (MarcXML, Excel spreadsheet, CSV, EAC-CPF) Types of Institutions/Collections * Academic/University records * Corporate/Business archives * Government * Religious * Non-profit/community * Minority-serving * Museum * Public Library * Historical Society * BIPOC * LGBTQ+ * Music/arts Data should be in a format that can easily be ingested into ArchivesSpace. Templates are available for the record types where CSV or spreadsheet formats are indicated. Please contact ArchivesSpaceHome at lyrasis.org if you have questions about how to prepare your data. Thank you, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Fri Feb 25 09:43:36 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 25 Feb 2022 14:43:36 +0000 Subject: [Archivesspace_Users_Group] Take a Break with ArchivesSpace returns next Friday (March 4) Message-ID: <51F22031-BCF5-4F81-9E91-B2025697CEA9@lyrasis.org> Dear ArchivesSpace users, Whether you?ve continued to work from home, have returned to the office, or find yourself stuck somewhere in the middle, we could all use a break. In that spirit, ArchivesSpace will be reinstating our popular casual zoom open calls on Fridays. With a welcoming and robust member community all over the world, ArchivesSpace can offer camaraderie and relaxation, no matter the current state of the world. Beginning next Friday, March 4th, we will have casual open calls via zoom at 12pm ET each Friday. We won?t be developing agendas or presentations for these calls. We just want to provide an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Whether you can attend once or plan to be there every Friday, these calls are open to everyone but registration is required to join. Register to join any open call at https://lyrasis.zoom.us/meeting/register/tZcldOGuqjotE9cNSaa6j45issVCKrEQKQYv We seek to provide a welcoming, fun, and safe community experience for everyone. The full text of the code of conduct is available at https://archivesspace.org/archivesspace-code-of-conduct. Please email ArchivesSpaceHome at lyrasis.org with any questions. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corinne.Chatnik at nysed.gov Mon Feb 28 11:20:26 2022 From: Corinne.Chatnik at nysed.gov (Corinne Chatnik) Date: Mon, 28 Feb 2022 16:20:26 +0000 Subject: [Archivesspace_Users_Group] Date Facet/Filter for Resource Browse? Message-ID: Hi, Does anyone have an example of modifying search_result_data.rb in a plugin to include a date facet for Resource Facet /browse? Corinne Chatnik Archivist Digital Strategies New York State Archives www.archives.nysed.gov | Corinne.Chatnik at nysed.gov Facebook | Twitter | New York Archives Magazine | YouTube 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 Feb 28 11:52:56 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 28 Feb 2022 16:52:56 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - February 2022 Message-ID: [cid:image001.jpg at 01D7E600.7FF2B540] Upcoming Schedule at a Glance: March 4: Take a Break with ArchivesSpace returns March 8: SNAC Cooperative Presentation on the ArchivesSpace/SNAC plugin (co-sponsored event) March 21-22: ArchivesSpace 4th annual Online Forum March 23: Submissions due for the ArchivesSpace Inclusive Examples Project Development ArchivesSpace is announcing the availability of v3.2.0. You can download it at https://github.com/archivesspace/archivesspace/releases/. This release marks the previously announced transition to external Solr. Links to documentation, a tutorial video, and other information are available at https://archivesspace.org/archives/7151. Beyond external Solr, there are several items to note in the release: * The Smithsonian worked with Hudson Molonglo to improve the ARKs feature. The scope of the work is described at https://github.com/archivesspace/archivesspace/pull/2437. * There is a new custom reports feature that was worked on by several developers, including former Tech Lead Laney McGlohon. * Other highlights include small improvements to the spreadsheet importers, a new page within the application for downloading templates, and various small bug fixes and features prioritized by the Development Prioritization sub-team. Thanks to all of the community members who contributed code for this release: Andrew Morrison, Blake Carver, Dean Farrell, Jacob Shelby, James Bullen, Laney McGlohon, Lora Woodford, Mario Terranova, Mark Triggs, Michael Glanznig, Payten Giles, and Saron Tran. As always, program team members Brian Hoffman and Mark Cooper, as well as contractors Manny Rodriguez and Brian Zelip, wrote and/or reviewed substantial code for the release. Thanks also to our community groups, especially the Testing sub-team, for their efforts. 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. This is the fall 2021 release from the roadmap that was originally projected for December. Items that were projected for this release that did not make it in have been shifted to future releases. Take a Break with ArchivesSpace returns March 4 Whether you?ve continued to work from home, have returned to the office, or find yourself stuck somewhere in the middle, we could all use a break. In that spirit, ArchivesSpace will be reinstating our popular casual zoom open calls on Fridays. With a welcoming and robust member community all over the world, ArchivesSpace can offer camaraderie and relaxation, no matter the current state of the world. Beginning next Friday, March 4th, we will have casual open calls via zoom at 12pm ET each Friday. We won?t be developing agendas or presentations for these calls. We just want to provide an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Whether you can attend once or plan to be there every Friday, these calls are open to everyone but registration is required to join. Register to join any open call at https://lyrasis.zoom.us/meeting/register/tZcldOGuqjotE9cNSaa6j45issVCKrEQKQYv We seek to provide a welcoming, fun, and safe community experience for everyone. The full text of the code of conduct is available at https://archivesspace.org/archivesspace-code-of-conduct. Please email ArchivesSpaceHome at lyrasis.org with any questions. SNAC Cooperative Presentation Announcement: ArchivesSpace/SNAC plugin [Posted on behalf of our colleagues at the SNAC cooperative] The SNAC Cooperative is developing an ArchivesSpace plugin to facilitate efficient data exchange. An hour long presentation demonstrating the functional features of the plugin with following discussion is scheduled for March 8, 2022, 2:00pm ET/11:00am PT. The presenters will be Jason Jordan, software developer at the University of Virginia Library, and Daniel Pitti, director of the SNAC Cooperative. Date: March 8, 2022 Time: 2:00pm ? 3:00pm ET (11:00am ? 12:00pm PT) Where: zoom Registration: https://virginia.zoom.us/meeting/register/tJEqdeuvpz4vGtOv65JpTcaOjQUO9nEPWSrD From within ArchivesSpace, the demonstration will cover both pulling data from and pushing data to SNAC. Though pushing data to SNAC will require being a member of the SNAC Cooperative, any ArchivesSpace user will be able to pull data from SNAC. In particular the demonstration will cover: * SNAC environment management in ArchivesSpace preferences * Import of SNAC agents to new ArchivesSpace agents * Export of ArchivesSpace agents (optionally including linked resources) to SNAC * Export of ArchivesSpace record descriptions (optionally including linked agents) to SNAC * Linking ArchivesSpace agents/record descriptions to existing SNAC agents and resource descriptions * Unlinking ArchivesSpace agents/record descriptions from existing SNAC agents and resource descriptions The SNAC plugin ia available on Github: https://github.com/snac-cooperative/snac_aspace_plugin The session will be recorded and made available as soon as feasible after the presentation at https://portal.snaccooperative.org/node/501 If you have questions about the presentation or questions about the SNAC Cooperative, please feel free to contact the Cooperative at snac.cooperative at gmail.com Registration now open: 2022 ArchivesSpace Online Forum Registration is now open for the 4th annual ArchivesSpace Online Forum! Taking place March 21-22, 2022, our online forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels. Anyone who uses ArchivesSpace or is interested in ArchivesSpace is welcome to attend. As in years past, this free event will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace. When: Presentations will be held March 21 from 5pm-8pm UTC / 10am-1pm PT / 1-4pm ET / 5pm-8pm GMT / 6-9pm CET (find your local time). Discussion sessions will be held March 22 from 1pm-4pm UTC / 6am-9am PT / 9am-12pm ET / 1pm-4pm GMT / 2pm-5pm CET (find your local time). Where: All online via Zoom, with opportunities to join via computer or phone. Who Can Attend: Anyone using or interested in using ArchivesSpace is welcome to attend some or all of the sessions on these days. This is a free event but registration is required. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3036282881/ArchivesSpace+Online+Forum+2022 Registrations for each day of the Forum are separate. You will need to register for each day you are interested in attending to guarantee your spot. Registration is linked in the agenda at the top of each day. We anticipate recording many parts of the forum, but for it to be a success we will also need as many live participants as possible. We encourage you to dip in and out of the live program as much as you can. You will no doubt ?meet? a different set of colleagues each time. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch at ArchivesSpaceHome at lyrasis.org with questions. We look forward to seeing many of you there! Call for feedback: Metadata Standards Subteam Online Forum discussion Do you have MARC records for your archival holdings? Then you probably have 300 fields. The MARC 300 ?Physical Description? field contains extent information critical for archival control of material, like 34 linear feet, or 12 boxes (10 cubic feet). The current AS MARC importer only parses the 300 field according to one very specific pattern, and otherwise defaults to ?1 linear feet.? This means that anyone doing bulk import of MARC records may be silently wiping out their archivist-supplied extents without realizing it. A recent ticket also noted that 300$f fields are ignored entirely. What we would like to hear from the community is how your 300 fields are structured, and how you would want 300 fields parsed on import. Sample data will help us make recommendations on what should be happening. For example, this is a common construction (from LC) that is NOT handled by the MARC importer: 300 ?a 5 ?f boxes ?a (3 ?f linear ft.) A discussion based on that sample might be: Should this pattern be supported? How should this be parsed? How should all of that punctuation be handled? The Metadata Standards subgroup will take what it learns and develop a specification for the desired behavior, but we need to hear from you. Community contribution requested in the ArchivesSpace Inclusive Examples Project In the wake of the George Floyd and Breonna Taylor murders, and in the spirit of protest that followed, the ArchivesSpace community began a conversation about what it could do to promote diversity and inclusion while combating systemic racism in our field. That continuing conversation has led to a series of initiatives that we will undertake in the coming years, including an Inclusive Examples project. For this important project, ArchivesSpace is delighted to be working with Brittany Newberry of Georgia State University to update the examples provided in its workshop materials and test databases. We want the examples to be more representative of the diverse institutions that use ArchivesSpace. We are interested in adding examples from the ArchivesSpace user community. Below is a list of record types and collection types for which we are looking. In addition, we have created an agreement to provide information and expectations for how the data shared will be used. If you are interested in participating, please email a signed agreement and the records you'd like to share in one of the formats listed. Email ArchivesSpaceHome at lyrasis.org by Wednesday, March 23 and we will forward your submission to Brittany Newberry for review. Feel free to contact us with any questions you may have. Possible Examples: Types of Records: * Resource records (EAD, MarcXML, CSV, Excel spreadsheet) * Accessions (MarcXML, Excel spreadsheet, CSV) * Digital Objects (CSV, Excel Spreadsheet) * Subjects and Agents (MarcXML, Excel spreadsheet, CSV, EAC-CPF) Types of Institutions/Collections * Academic/University records * Corporate/Business archives * Government * Religious * Non-profit/community * Minority-serving * Museum * Public Library * Historical Society * BIPOC * LGBTQ+ * Music/arts Data should be in a format that can easily be ingested into ArchivesSpace. Templates are available for the record types where CSV or spreadsheet formats are indicated. Please contact ArchivesSpaceHome at lyrasis.org if you have questions about how to prepare your data. Program Announcement: ArchivesSpace Member Match program update The ArchivesSpace Member Engagement sub-team will soon begin accepting applications for the second cohort of the ArchivesSpace Member Match program. The Member Match program is an initiative to engage the ArchivesSpace membership community, created and organized by the Member Engagement sub-team of the ArchivesSpace User Advisory Council, with support from the ArchivesSpace Community Engagement Coordinator. The program is intended to be a resource and venue for peer-to-peer support between ArchivesSpace members. For one, year-long term, Member Match participants will be matched with a member with whom they can receive and offer professional insight, advice, and comradery. The program will also offer participants the opportunity to engage in exclusive events and enlightening discussions about ArchivesSpace and its active user community. Thanks to valuable feedback from the first cohort of Member Match Participants, we?ve implemented the following updates to the program: * Monthly Listserv Discussion Topics * Each month, a member of the Member Engagement sub-team will reach out to the Member Match listserv to spur discussion and encourage continued engagement between matches. * Quarterly Member Match Meet-Ups * These will be opportunities for large group socializing as well as the potential for dedicated time to spend with matches in breakout rooms. * Option to participate in small group matches of 3 people Eligibility Any individual affiliated with an ArchivesSpace member organization is eligible to participate in the ArchivesSpace Member Match program and there is no limit to the number of individuals from a member organization that may participate. If you are unsure of your organization?s ArchivesSpace membership status, visit https://archivesspace.org/community/whos-using-archivesspace or email ArchivesSpaceHome at lyrasis.org. To Learn More: Visit the Member Match wiki: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program Please feel free to direct any questions to ArchivesSpaceHome at lyrasis.org Recording available: Virtual ArchivesSpace Assessments Module Training February 23, 2022 Thank you to everyone who attended the ArchivesSpace Assessments Module Training on February 23. During this workshop, ArchivesSpace trainer Brittany Newberry will cover using the assessments module in ArchivesSpace including completing assessments in ArchivesSpace, adding values to the assessments template and importing assessments using CSV. A recording of this training is now available on the Community-Wide training page of the wiki. Membership Update We are excited to welcome our newest members to our community! Our new members since January 31 include: * Christchurch City Libraries, (Christchurch, New Zealand) * Presbyterian Church of Victoria Archives, (Victoria, Australia) * Township of Brick, New Jersey, (Brick, NJ) As of February 28, we have 464 General members, 22 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: 22473 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29071 bytes Desc: image002.jpg URL: From livsolis at utexas.edu Mon Feb 28 12:50:44 2022 From: livsolis at utexas.edu (Olivia S Solis) Date: Mon, 28 Feb 2022 11:50:44 -0600 Subject: [Archivesspace_Users_Group] Digital Objects and ASpace performance Message-ID: Hello all, Our team is beginning to consider how to use digital objects in conjunction with our Islandora repository/Archivematica. We manage our own ArchiveSpace instance so system maintenance is a big consideration. If you manage your own ASpace instance and implemented the digital object module, did you notice any impact it had on system performance? We have tens of thousands of objects in our repository and are concerned that adding that many digital objects might slow things down. If it does, we may need to create digital objects that link to the collection level in our repository ? which corresponds to an archival collection ? though it would be nice to integrate them at a more granular level. Did performance impact at what level you decided to implement the digital objects module? How have you noticed digital objects affecting any load testing you've done? Thanks! Olivia -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From elizabeth_coup at harvard.edu Mon Feb 28 16:34:31 2022 From: elizabeth_coup at harvard.edu (Coup, Betts) Date: Mon, 28 Feb 2022 21:34:31 +0000 Subject: [Archivesspace_Users_Group] Folder label creation from resource record Message-ID: Hi everyone, I'm wondering if anyone has any advice for creating folder labels from resource records in ArchivesSpace. We have been using a Windows PowerShell script that runs over the exported EAD XML file to pull out appropriately leveled container information but have run into problems with it off and on. I'd love to hear what others are doing to create folder labels in an automated way from a resource record if anyone has ideas or solutions to recommend. Thanks for your time! Best, Betts Coup Betts Coup (she/her) Lead Processing Archivist Houghton Library elizabeth_coup at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: