From Jessica.Crouch at lyrasis.org Mon Dec 2 09:45:27 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 2 Dec 2019 14:45:27 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - November 2019 Message-ID: <28114A50-9B47-4DA3-94A9-F97DFD8F5E0F@lyrasis.org> [cid:image001.jpg at 01D5A8F5.39D39880] November 2019 Update Development As mentioned in the release announcement for ArchivesSpace v2.7.0, the changes in the languages area will require data cleanup to existing records for some people. Upon upgrade, existing language information is migrated to the new or newly structured fields. While some ways of recording information could be easily accommodated in this migration, because there are so many different ways language information could have been recorded previously, some situations will require data cleanup. We?ve put together three plugins that you can use, or use as examples, to handle some common situations. These only run on resource records. They are: * Batch update language and script of description in resource records to one language and/or script of description value: https://github.com/archivesspace-plugins/batch_update_lang_and_script - for cases where all or most of your description is done in one language and script, this will help you do a global or repository-specific update. * Batch update language of materials in resource records currently lacking a controlled value language: https://github.com/archivesspace-plugins/batch_update_langmaterials - for situations where all or most of your materials that do not currently have a language value are in one language, this will help you do a global or repository-specific update. * Batch update language of materials records for resource records currently lacking a controlled value language by matching a text string in a note: https://github.com/archivesspace-plugins/batch_update_langmaterials_from_note - for situations where specific note text can be easily parsed into a controlled value language, this will help you do a targeted update. You will be able to choose whether to keep or delete the notes after running this job. (credit for these plugins goes to Lora Woodford) As with any plugins that change information in records, we strongly recommend you backup your data before running them and review the results in records afterwards before moving on to do more work in your ArchivesSpace. These plugins make changes to your records that cannot be undone, though you can edit individual records or run the plugins again at any point. Once you?ve run the plugin(s) and are satisfied with the results, you can disable the plugins at any time. In addition, we have been alerted to an issue where previously created RDE templates do not display correctly in v2.7.0 due to the language changes. This will be corrected in the next release, but there is now a plugin available that can provide a fix for people who need it quicker than that: RDE template fix: https://github.com/archivesspace-plugins/rde_template_fix (credit for this plugin goes to Mark Cooper) We anticipate the next release of ArchivesSpace will come out early in 2020. Program team and contracted developers are primarily working on the re-envisioned agents module, some container improvements, and additional infrastructure improvements. Community developers have already submitted pull requests for some notable bug fixes and feature enhancements. If you are currently working on development that you'd like to share with the community we'd love to hear from you. New ArchivesSpace Help Center We?re pleased to announce that a new ArchivesSpace Help Center, with an improved user manual and new training videos, is on its way. We expect to be launching the site in mid-December. The Help Center will be part of our larger Confluence site, which includes information about many of our community and development activities. The current Help Center site (http://docs.archivesspace.org) will be up through early 2020, but it will be closed to new user signups and no content will be updated once the new site is up. Access to the Help Center is a member benefit. The new and improved content is thanks to the efforts of our User Documentation sub-team and our training corps, and the amazing organizational skills of our Community Engagement Coordinator, Jessica Crouch. We?ll be migrating member user accounts to the new site beginning the week of December 9. We ask that you do not update, create or sign up for new accounts on the current site after December 6 as these changes may not carry over to the new site. We hope you enjoy the new content and look forward to the enhanced opportunities for community participation that the new site will allow. Thanks for your patience as we make this transition and please let us know if you have any questions. Volunteer for the next ArchivesSpace online forum The deadline to volunteer for the working group for our next online forum has been extended to December 9th! Planned for early spring 2020, this event will build on the success of the 2019 Online Forum, which had over 400 registrants, participating from 7 different countries. We would love this event to highlight the work institutions near and far are doing to adapt and integrate ArchivesSpace into their systems and workflows. We expect to offer a variety of activities aimed at building community connections and contacts among our users. All ideas are welcome! All community members are welcome to volunteer for this working group. We especially encourage our Small and Very Small members as well as non-U.S. members to join in envisioning the next iteration of this event. We will schedule meetings and the forum itself in ways that allow for participation across time zones. If you would like to volunteer, please respond by December 9, 2019. And if you have any questions, contact Jessica at jessica.crouch at lyrasis.org. Upcoming Webinar: Integrating ArchivesSpace with Archive-It December 4, 2019, 2-3pm ET (11-noon PT; 7-8pm BST) Visit the ArchivesSpace blog for details. ArchivesSpace is pleased to announce the third webinar in our new series focused on Integrations with ArchivesSpace. Each webinar in this series will highlight an integration with another application used in archives that ArchivesSpace members have worked on or requested. The webinar series will feature both open source and proprietary systems. Our third webinar in this series will feature an open discussion on ArchivesSpace integration with Archive-It, a subscription web archiving service from the Internet Archive that helps organizations to harvest, build, and preserve collections of digital content Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. In this webinar, Lori Donovan (Archive-It) will discuss the Archive-It/ArchivesSpace integration that was developed as part of the Archiving the Websites of Contemporary Composers Mellon grant, which the Internet Archive collaborated on with New York University. Lori will also share information about the APIs that underlie the Archive-It service and ways that these might be leveraged to integrate metadata from Archive-It into ArchivesSpace repositories. Dallas Pillen (University of Michigan) will present on the Bentley Historical Library's use of ArchivesSpace to manage descriptive metadata about websites captured with Archive-It. The presentation will discuss why and how the Bentley decided to manage its descriptive metadata about archived websites in ArchivesSpace and will provide an overview of a locally developed ArchivesSpace plugin that integrates the two systems to facilitate this work. A discussion will follow. ArchivesSpace users who have integrated with Archive-It or are considering integrating with Archive-It are encouraged to participate in this discussion in an effort to identify and highlight current community efforts or the potential for community collaboration to encourage integration between the two systems. Presenters: Lori Donovan is the Senior Program Manager for Web Archiving at the Internet Archive. Lori manages Archive-It service growth, which includes leading a team of Web Archivists and Technical Support staff who provide instruction, guidance and support for Archive-It users, and interfacing with the engineering team to develop new features and functionality for the Archive-It service. Lori has a Master of Information degree from University of Michigan, and a Bachelor?s degree from Boise State University, where she majored in history and political science. Dallas Pillen is the Archivist for Metadata and Digital Curation at the University of Michigan?s Bentley Historical Library, where he oversees the library's use of ArchivesSpace, Archive-It, Archivematica, and DSpace. He is also a member of the ArchivesSpace Technical Advisory Council and co-chair of the Society of American Archivists' Encoded Archival Standards Section. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. The next Integrations with ArchivesSpace webinar will be: Integrating ArchivesSpace with Aviary, January 15, 2020, at 2pm ET (11am PT) Membership Update We are excited to welcome our newest members to our community! Our new members since October 31 include: * George Mason University (Fairfax VA) * Hartford Public Library (Hartford CT) * New York State Archives (Albany NY) * Virginia Museum of Fine Arts (Richmond VA) As of November 30, we have 409 General members, 19 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 Tools 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 Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 19859 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29060 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Mon Dec 2 13:50:22 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 2 Dec 2019 18:50:22 +0000 Subject: [Archivesspace_Users_Group] new ArchivesSpace Help Center coming soon Message-ID: Dear ArchivesSpace members, We're pleased that a new ArchivesSpace Help Center, with an improved user manual and new training videos, is on its way. We expect to be launching the site by mid-December. The Help Center will be a private area within our larger Confluence site, which includes information about many of our community and development activities. The current Help Center site (http://docs.archivesspace.org) will be up through early 2020, but it will be closed to new user signups and no content will be updated once the new site is up. The new and improved content is thanks to the efforts of our User Documentation sub-team and our training corps, and the amazing organizational skills of our Community Engagement Coordinator, Jessica Crouch. We'll be migrating user accounts to the new site beginning the week of December 9. Please do not update, create or sign up for new accounts on the current site after December 6. After that, * If you already have an account for our Confluence site, you will not need to do anything. Privileges to access the Help Center area will be added to your account. * If you have an active* account on the current Help Center site but do not already have an account for our Confluence site, you will receive an email invitation from Atlassian to set up your account and get access to the new area. The subject line will be "ArchivesSpace has invited you to Confluence." This account will also give you enhanced access to our other Confluence and JIRA areas. Passwords from the old site will not carry over, so you will need to create a password as part of setting up your Confluence account. * If you do not have an account on the current Help Center site and do not already have a Confluence account, I suggest waiting until the new site launches and then signing up yourself. If you need help with that, please let us know at ArchivesSpaceHome at lyrasis.org. * We've asked Help Center institutional administrators to clean up user accounts for their institutions over the last few weeks. Thank you for all your help with this! Prior to the move, we will also be clearing out accounts from the current site for people who have not logged in for more than 18 months. This will help us ensure that only currently active users are moved over to the new site. We hope you enjoy the new content and look forward to the enhanced opportunities for community participation that the new site will allow. Thanks for your patience as we make this transition and please do let us know if you have any questions. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From gboggio at mitre.org Mon Dec 2 16:13:45 2019 From: gboggio at mitre.org (Boggio, Jerry) Date: Mon, 2 Dec 2019 21:13:45 +0000 Subject: [Archivesspace_Users_Group] Accessions Query In-Reply-To: References: Message-ID: Hi ArchivesSpace Users; It appears we have found the answer to our question on https://archivesspace.github.io/archivesspace/user/re-creating-indexes/. By rebuilding the index files all records are now found from the MySQL database. The issues seems to be related to refreshing the database in a test environment from production, but the index files not picking up the new records. Rebuilding the index files also appears to address the issue we outlined in our eMail "Error browsing Resources in version 2.6". One other observation we made when refreshing the database is that the script archivesspace/scripts/setup-database.sh does not appear to work on later refreshes. The firs time we ran the script, the beginning of the output was as follows: [scripts]$ ./setup-database.sh Loading ArchivesSpace configuration file from path: /apps/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /apps/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /apps/archivesspace/config/config.rb Running migrations against jdbc:mysql://mysqldev-a.mitre.org:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true I, [2019-10-18T13:24:53.944292 #48098] INFO -- : Begin applying migration version 98, direction: up I, [2019-10-18T13:24:54.123838 #48098] INFO -- : Finished applying migration version 98, direction: up, took 0.179616 seconds I, [2019-10-18T13:24:54.124897 #48098] INFO -- : Begin applying migration version 99, direction: up I, [2019-10-18T13:24:54.290539 #48098] INFO -- : Finished applying migration version 99, direction: up, took 0.165550 seconds I, [2019-10-18T13:24:54.291407 #48098] INFO -- : Begin applying migration version 100, direction: up I, [2019-10-18T13:25:01.935442 #48098] INFO -- : Finished applying migration version 100, direction: up, took 7.643832 seconds I, [2019-10-18T13:25:01.936657 #48098] INFO -- : Begin applying migration version 101, direction: up I, [2019-10-18T13:25:02.357509 #48098] INFO -- : Finished applying migration version 101, direction: up, took 0.420813 seconds I, [2019-10-18T13:25:02.358205 #48098] INFO -- : Begin applying migration version 102, direction: up I, [2019-10-18T13:25:02.706000 #48098] INFO -- : Finished applying migration version 102, direction: up, took 0.347575 seconds I, [2019-10-18T13:25:02.707015 #48098] INFO -- : Begin applying migration version 103, direction: up Updating qaa-qtz to und Deleting enumeration_id for qaa-qtz I, [2019-10-18T13:25:03.059206 #48098] INFO -- : Finished applying migration version 103, direction: up, took 0.352167 seconds : : After later refreshes, the output contained only these messages: [logs]$ more setup-database.log_20191202_1504 Loading ArchivesSpace configuration file from path: /apps/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /apps/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /apps/archivesspace/config/config.rb Running migrations against jdbc:mysql://mysqldev-a.mitre.org:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true All done. [m91981 at archspcdev1 logs]$ Does something need to be "reset" in a file or someplace else to allow the database conversion to happen again? We would also still be interested in seeing document that identifies the relationships between tables, if available. Please advise. Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 From: Boggio, Jerry Sent: Wednesday, November 27, 2019 12:01 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Accessions Query Hi ArchivesSpace Users; We are seeing an issue in our Linux based installation of version 2.6 where we are not seeing all of my Accession records when selecting Browse > Accessions. Could you please provide the SQL query used to populate that page so that we may see if there is selection criteria being applied? With that information we can compare to our SQL query going directly against the database to identify differences. Is there also a document that identifies the relationships between tables in ArchivesSpace? Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.donahue at lac-group.com Tue Dec 3 09:20:50 2019 From: rachel.donahue at lac-group.com (Rachel Donahue) Date: Tue, 3 Dec 2019 09:20:50 -0500 Subject: [Archivesspace_Users_Group] Accessions Query In-Reply-To: References: Message-ID: Hi Jerry, I haven't seen an up-to-date ER diagram for ArchivesSpace (there were some early architecture documents), but you can reverse engineer one using MySQL workbench. Workbench: https://www.mysql.com/products/workbench/ Directions: https://medium.com/@tushar0618/how-to-create-er-diagram-of-a-database-in-mysql-workbench-209fbf63fd03 I'd recommend doing it on a fresh database rather than your production database. --Rachel -- The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. On Mon, Dec 2, 2019 at 4:14 PM Boggio, Jerry wrote: > Hi ArchivesSpace Users; > > > > It appears we have found the answer to our question on > https://archivesspace.github.io/archivesspace/user/re-creating-indexes/. > By rebuilding the index files all records are now found from the MySQL > database. The issues seems to be related to refreshing the database in a > test environment from production, but the index files not picking up the > new records. Rebuilding the index files also appears to address the issue > we outlined in our eMail ?Error browsing Resources in version 2.6?. > > > > One other observation we made when refreshing the database is that the > script archivesspace/scripts/setup-database.sh does not appear to work on > later refreshes. The firs time we ran the script, the beginning of the > output was as follows: > > > > [scripts]$ ./setup-database.sh > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Running migrations against jdbc:mysql:// > mysqldev-a.mitre.org:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true > > I, [2019-10-18T13:24:53.944292 #48098] INFO -- : Begin applying migration > version 98, direction: up > > I, [2019-10-18T13:24:54.123838 #48098] INFO -- : Finished applying > migration version 98, direction: up, took 0.179616 seconds > > I, [2019-10-18T13:24:54.124897 #48098] INFO -- : Begin applying migration > version 99, direction: up > > I, [2019-10-18T13:24:54.290539 #48098] INFO -- : Finished applying > migration version 99, direction: up, took 0.165550 seconds > > I, [2019-10-18T13:24:54.291407 #48098] INFO -- : Begin applying migration > version 100, direction: up > > I, [2019-10-18T13:25:01.935442 #48098] INFO -- : Finished applying > migration version 100, direction: up, took 7.643832 seconds > > I, [2019-10-18T13:25:01.936657 #48098] INFO -- : Begin applying migration > version 101, direction: up > > I, [2019-10-18T13:25:02.357509 #48098] INFO -- : Finished applying > migration version 101, direction: up, took 0.420813 seconds > > I, [2019-10-18T13:25:02.358205 #48098] INFO -- : Begin applying migration > version 102, direction: up > > I, [2019-10-18T13:25:02.706000 #48098] INFO -- : Finished applying > migration version 102, direction: up, took 0.347575 seconds > > I, [2019-10-18T13:25:02.707015 #48098] INFO -- : Begin applying migration > version 103, direction: up > > Updating qaa-qtz to und > > Deleting enumeration_id for qaa-qtz > > I, [2019-10-18T13:25:03.059206 #48098] INFO -- : Finished applying > migration version 103, direction: up, took 0.352167 seconds > > : > > : > > > > After later refreshes, the output contained only these messages: > > > > [logs]$ more setup-database.log_20191202_1504 > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Running migrations against jdbc:mysql:// > mysqldev-a.mitre.org:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true > > All done. > > [m91981 at archspcdev1 logs]$ > > > > Does something need to be ?reset? in a file or someplace else to allow the > database conversion to happen again? > > > > We would also still be interested in seeing document that identifies the > relationships between tables, if available. > > > > Please advise. > > > > Thank you! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R504 - Collaboration & > Info Management | 781-271-2719 | Bedford, MA | 2K132 > > > > *From:* Boggio, Jerry > *Sent:* Wednesday, November 27, 2019 12:01 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* Accessions Query > > > > Hi ArchivesSpace Users; > > > > We are seeing an issue in our Linux based installation of version 2.6 > where we are not seeing all of my Accession records when selecting Browse > > Accessions. Could you please provide the SQL query used to populate that > page so that we may see if there is selection criteria being applied? With > that information we can compare to our SQL query going directly against the > database to identify differences. > > > > Is there also a document that identifies the relationships between tables > in ArchivesSpace? > > > > Thank you! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R504 - Collaboration & > Info Management | 781-271-2719 | Bedford, MA | 2K132 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Dec 3 10:22:25 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 3 Dec 2019 15:22:25 +0000 Subject: [Archivesspace_Users_Group] Reminder - Webinar Tomorrow: Integrating ArchivesSpace and Archive-It Message-ID: Webinar Announcement: Integrating ArchivesSpace and Archive-It ArchivesSpace is pleased to announce the third webinar in our new series focused on Integrations with ArchivesSpace. Each webinar in this series will highlight an integration with another application used in archives that ArchivesSpace members have worked on or requested. The webinar series will feature both open source and proprietary systems. Our third webinar in this series will feature an open discussion on ArchivesSpace integration with Archive-It, a subscription web archiving service from the Internet Archive that helps organizations to harvest, build, and preserve collections of digital content. When: December 4, 2019 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT; 7 p.m. ? 8 p.m. BST) Where: Zoom https://lyrasis.zoom.us/j/901271657 One tap mobile +19292056099,,901271657# US (New York) +16699006833,,901271657# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 901 271 657 Find your local number: https://zoom.us/u/awkFNWPxh Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. In this webinar, Lori Donovan (Archive-It) will discuss the Archive-It/ArchivesSpace integration that was developed as part of the Archiving the Websites of Contemporary Composers Mellon grant, which the Internet Archive collaborated on with New York University. Lori will also share information about the APIs that underly the Archive-It service and ways that these might be leveraged to integrate metadata from Archive-It into ArchivesSpace repositories. Dallas Pillen (University of Michigan) will present on the Bentley Historical Library's use of ArchivesSpace to manage descriptive metadata about websites captured with Archive-It. The presentation will discuss why and how the Bentley decided to manage its descriptive metadata about archived websites in ArchivesSpace and will provide an overview of a locally developed ArchivesSpace plugin that integrates the two systems to facilitate this work. A discussion will follow. ArchivesSpace users who have integrated with Archive-It or are considering integrating with Archive-It are encouraged to participate in this discussion in an effort to identify and highlight current community efforts or the potential for community collaboration to encourage integration between the two systems. Presenters: Lori Donovan is the Senior Program Manager for Web Archiving at the Internet Archive. Lori manages Archive-It service growth, which includes leading a team of Web Archivists and Technical Support staff who provide instruction, guidance and support for Archive-It users, and interfacing with the engineering team to develop new features and functionality for the Archive-It service. Lori has a Master of Information degree from University of Michigan, and a Bachelor?s degree from Boise State University, where she majored in history and political science. Dallas Pillen is the Archivist for Metadata and Digital Curation at the University of Michigan?s Bentley Historical Library, where he oversees the library's use of ArchivesSpace, Archive-It, Archivematica, and DSpace. He is also a member of the ArchivesSpace Technical Advisory Council and co-chair of the Society of American Archivists' Encoded Archival Standards Section. Who should attend: Anyone interested in possibilities for integrating ArchivesSpace with Archive-It, those who have integrated ArchivesSpace and Archive-It and would like to offer insight to others, and those who are interested in working with fellow community members to make integration with Archive-It easier. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. The next Integrations with ArchivesSpace webinar will be: Integrating ArchivesSpace with Aviary, January 15, 2020 at 2pm ET (11am PT) Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8535 bytes Desc: image001.jpg URL: From sanfilippo_thomas at wheatoncollege.edu Tue Dec 3 13:42:33 2019 From: sanfilippo_thomas at wheatoncollege.edu (Thomas San Filippo) Date: Tue, 3 Dec 2019 13:42:33 -0500 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway Message-ID: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> Hi folks, Has anyone successfully run an OAI-PMH harvest of their ArchivesSpace via OCLC's Digital Collection Gateway? Everything *seems* to be set up correctly in our config file, but we fail the third test in the DCG interface: * SUCCESS: Testing URL Uniqueness * SUCCESS: Testing URL Validity * FAILED: Testing Availability * SKIPPED: Testing OAI Support * SKIPPED: Testing DC Format Support * SKIPPED: Testing OCLC DC Format Support * SKIPPED: Testing List Sets * SKIPPED: Testing Set Uniqueness * SKIPPED: Testing List Records * SKIPPED: Testing Actionable URL Identifier I think we may have a problem with our base URL. I'm using http://archives.wheatoncollege.edu:8082 , but pretty much anything I try passes the first two tests and fails the third. The troubleshooting information given for that test is: Testing Availability: The OAI-??PMH Base URL is currently inaccessible. It is possible that the repository is currently down or that it is simply not reachable by the Gateway. Double-??check the spelling of the URL and make sure it has not been mistyped or pasted incorrectly. -- *Thomas San Filippo* /Systems and Educational Technology Liaison/ Pronouns: he/him/his; they/them/their(s) Madeleine Clark Wallace Library , G34 Wheaton College 26 E. Main Street, Norton, MA 02766 (508) 286-5601 Twitter: @WallaceLibrary | Instagram: /wallacelibrary | Facebook: wheatoncollege -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue Dec 3 13:56:46 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 3 Dec 2019 18:56:46 +0000 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway In-Reply-To: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> References: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> Message-ID: <50E5D5CA-59F6-44B4-AA2E-3BAA9999AD51@virginia.edu> I can?t access that URL, although if I change it to port 8081, I can see the PUI welcome page. Is port 8082 behind a firewall ? I thing the error message is to be taken literally: URL is inaccessible. ? Steve M. > On Dec 3, 2019, at 1:42 PM, Thomas San Filippo wrote: > > Hi folks, > > Has anyone successfully run an OAI-PMH harvest of their ArchivesSpace via OCLC's Digital Collection Gateway? Everything *seems* to be set up correctly in our config file, but we fail the third test in the DCG interface: > > SUCCESS: Testing URL Uniqueness > SUCCESS: Testing URL Validity > FAILED: Testing Availability > SKIPPED: Testing OAI Support > SKIPPED: Testing DC Format Support > SKIPPED: Testing OCLC DC Format Support > SKIPPED: Testing List Sets > SKIPPED: Testing Set Uniqueness > SKIPPED: Testing List Records > SKIPPED: Testing Actionable URL Identifier > I think we may have a problem with our base URL. I'm using http://archives.wheatoncollege.edu:8082 , but pretty much anything I try passes the first two tests and fails the third. The troubleshooting information given for that test is: > > Testing Availability: The OAI-??PMH Base URL is currently inaccessible. It is possible that the repository is currently down or that it is simply not reachable by the Gateway. Double-??check the spelling of the URL and make sure it has not been mistyped or pasted incorrectly. > > > > -- > Thomas San Filippo > Systems and Educational Technology Liaison > > Pronouns: he/him/his; they/them/their(s) > > Madeleine Clark Wallace Library , G34 > Wheaton College > 26 E. Main Street, Norton, MA 02766 > (508) 286-5601 > Twitter: @WallaceLibrary | Instagram: /wallacelibrary | Facebook: wheatoncollege > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4974 bytes Desc: not available URL: From seth.shaw at unlv.edu Tue Dec 3 13:57:25 2019 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 3 Dec 2019 10:57:25 -0800 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway In-Reply-To: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> References: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> Message-ID: Presuming the OCLC Digital Collections Gateway is running from an OCLC IP address, I would check with your systems folks to make sure that host and port are available outside of your library/campus. I can't reach the archives.wheatoncollege.edu host address from here. On Tue, Dec 3, 2019 at 10:42 AM Thomas San Filippo < sanfilippo_thomas at wheatoncollege.edu> wrote: > Hi folks, > > Has anyone successfully run an OAI-PMH harvest of their ArchivesSpace via > OCLC's Digital Collection Gateway? Everything *seems* to be set up > correctly in our config file, but we fail the third test in the DCG > interface: > > - SUCCESS: Testing URL Uniqueness > - SUCCESS: Testing URL Validity > - FAILED: Testing Availability > - SKIPPED: Testing OAI Support > - SKIPPED: Testing DC Format Support > - SKIPPED: Testing OCLC DC Format Support > - SKIPPED: Testing List Sets > - SKIPPED: Testing Set Uniqueness > - SKIPPED: Testing List Records > - SKIPPED: Testing Actionable URL Identifier > > I think we may have a problem with our base URL. I'm using > http://archives.wheatoncollege.edu:8082 , but pretty much anything I try > passes the first two tests and fails the third. The troubleshooting > information given for that test is: > > Testing Availability: The OAI-??PMH Base URL is currently inaccessible. It > is possible that the repository is currently down or that it is simply not > reachable by the Gateway. Double-??check the spelling of the URL and make > sure it has not been mistyped or pasted incorrectly. > > > -- > *Thomas San Filippo* > *Systems and Educational Technology Liaison* > > Pronouns: he/him/his; they/them/their(s) > > Madeleine Clark Wallace Library > , G34 > Wheaton College > 26 E. Main Street, Norton, MA 02766 > (508) 286-5601 <+15082865601> > Twitter: @WallaceLibrary | > Instagram: /wallacelibrary | > Facebook: wheatoncollege > _______________________________________________ > 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 seth.shaw at unlv.edu Tue Dec 3 14:02:57 2019 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 3 Dec 2019 11:02:57 -0800 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway In-Reply-To: References: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> Message-ID: Side note now that Steve pointed out that port 8081 does work, I recommend changing the PUI port to "80", the default web port, so users don't need to add the 8081 port to access your site. On Tue, Dec 3, 2019 at 10:57 AM Seth Shaw wrote: > Presuming the OCLC Digital Collections Gateway is running from an OCLC IP > address, I would check with your systems folks to make sure that host and > port are available outside of your library/campus. I can't reach the > archives.wheatoncollege.edu host address from here. > > On Tue, Dec 3, 2019 at 10:42 AM Thomas San Filippo < > sanfilippo_thomas at wheatoncollege.edu> wrote: > >> Hi folks, >> >> Has anyone successfully run an OAI-PMH harvest of their ArchivesSpace via >> OCLC's Digital Collection Gateway? Everything *seems* to be set up >> correctly in our config file, but we fail the third test in the DCG >> interface: >> >> - SUCCESS: Testing URL Uniqueness >> - SUCCESS: Testing URL Validity >> - FAILED: Testing Availability >> - SKIPPED: Testing OAI Support >> - SKIPPED: Testing DC Format Support >> - SKIPPED: Testing OCLC DC Format Support >> - SKIPPED: Testing List Sets >> - SKIPPED: Testing Set Uniqueness >> - SKIPPED: Testing List Records >> - SKIPPED: Testing Actionable URL Identifier >> >> I think we may have a problem with our base URL. I'm using >> http://archives.wheatoncollege.edu:8082 , but pretty much anything I try >> passes the first two tests and fails the third. The troubleshooting >> information given for that test is: >> >> Testing Availability: The OAI-??PMH Base URL is currently inaccessible. >> It is possible that the repository is currently down or that it is simply >> not reachable by the Gateway. Double-??check the spelling of the URL and >> make sure it has not been mistyped or pasted incorrectly. >> >> >> -- >> *Thomas San Filippo* >> *Systems and Educational Technology Liaison* >> >> Pronouns: he/him/his; they/them/their(s) >> >> Madeleine Clark Wallace Library >> , G34 >> Wheaton College >> 26 E. Main Street, Norton, MA 02766 >> (508) 286-5601 <+15082865601> >> Twitter: @WallaceLibrary | >> Instagram: /wallacelibrary | >> Facebook: wheatoncollege >> _______________________________________________ >> 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 bzhang at csus.edu Tue Dec 3 14:13:28 2019 From: bzhang at csus.edu (Zhang, Bin) Date: Tue, 3 Dec 2019 19:13:28 +0000 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway In-Reply-To: References: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> Message-ID: <8EACFBE3-3F75-43A0-8E09-E83BDACAFE4D@csus.edu> I can only reach ports 443 and 8081 on your server, both of which serve your PUI. Looks like you need to ask campus to open up the port 8082 on the firewall. --- Bin Zhang Digital Information Services Librarian Library Systems & IT Services, University Library California State University, Sacramento +1 (916) 278-5664 | bzhang at csus.edu Zoom: https://csus.zoom.us/my/bzhang From: on behalf of Seth Shaw Reply-To: Archivesspace Group Date: Tuesday, December 3, 2019 at 11:03 AM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] OCLC Digital Collection Gateway Side note now that Steve pointed out that port 8081 does work, I recommend changing the PUI port to "80", the default web port, so users don't need to add the 8081 port to access your site. On Tue, Dec 3, 2019 at 10:57 AM Seth Shaw > wrote: Presuming the OCLC Digital Collections Gateway is running from an OCLC IP address, I would check with your systems folks to make sure that host and port are available outside of your library/campus. I can't reach the archives.wheatoncollege.edu host address from here. On Tue, Dec 3, 2019 at 10:42 AM Thomas San Filippo > wrote: Hi folks, Has anyone successfully run an OAI-PMH harvest of their ArchivesSpace via OCLC's Digital Collection Gateway? Everything *seems* to be set up correctly in our config file, but we fail the third test in the DCG interface: * SUCCESS: Testing URL Uniqueness * SUCCESS: Testing URL Validity * FAILED: Testing Availability * SKIPPED: Testing OAI Support * SKIPPED: Testing DC Format Support * SKIPPED: Testing OCLC DC Format Support * SKIPPED: Testing List Sets * SKIPPED: Testing Set Uniqueness * SKIPPED: Testing List Records * SKIPPED: Testing Actionable URL Identifier I think we may have a problem with our base URL. I'm using http://archives.wheatoncollege.edu:8082 , but pretty much anything I try passes the first two tests and fails the third. The troubleshooting information given for that test is: Testing Availability: The OAI-??PMH Base URL is currently inaccessible. It is possible that the repository is currently down or that it is simply not reachable by the Gateway. Double-??check the spelling of the URL and make sure it has not been mistyped or pasted incorrectly. -- Thomas San Filippo Systems and Educational Technology Liaison Pronouns: he/him/his; they/them/their(s) Madeleine Clark Wallace Library, G34 Wheaton College 26 E. Main Street, Norton, MA 02766 (508) 286-5601 Twitter: @WallaceLibrary | Instagram: /wallacelibrary | Facebook: wheatoncollege _______________________________________________ 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 sdm7g at virginia.edu Tue Dec 3 14:20:16 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 3 Dec 2019 19:20:16 +0000 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway In-Reply-To: References: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> Message-ID: <8F7D50E3-9A53-44C3-B81B-968E904FB997@virginia.edu> Not at all a solution to the original posters problem, but I was thinking of proposing that in a future release, we just get rid of the separate OAI server, and server OAI from public-url/oai . Some sites are already doing that ? I assume thru apache or other proxy server. ( I think that?s what Lyrasis is doing for the sites they manage. I wish I had thought of that obvious option before setting up a separate VHOST for OAI. ) The existing OAI server is only proxying data from the backend server anyway. Proxying to the PUI would make configuration simpler, and would have the side benefit of a consistent OAI endpoint for all public sites. ? Steve M. > On Dec 3, 2019, at 2:02 PM, Seth Shaw wrote: > > Side note now that Steve pointed out that port 8081 does work, I recommend changing the PUI port to "80", the default web port, so users don't need to add the 8081 port to access your site. > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4974 bytes Desc: not available URL: From sanfilippo_thomas at wheatoncollege.edu Tue Dec 3 18:19:16 2019 From: sanfilippo_thomas at wheatoncollege.edu (Thomas San Filippo) Date: Tue, 3 Dec 2019 18:19:16 -0500 Subject: [Archivesspace_Users_Group] OCLC Digital Collection Gateway In-Reply-To: <8F7D50E3-9A53-44C3-B81B-968E904FB997@virginia.edu> References: <5742bbf1-ec45-983d-322d-d395d2a9c3a1@wheatoncollege.edu> <8F7D50E3-9A53-44C3-B81B-968E904FB997@virginia.edu> Message-ID: Thank you! This never even occurred to me, but I just tried from home and I'm firewalled, too. Kind of defeats the purpose of a public interface, huh? I'll talk to IT and try to reverse the damage from 3 hours of banging my head against my laptop. Thanks again, *Thomas San Filippo* *Systems and Educational Technology Liaison* Pronouns: he/him/his; they/them/their(s) Madeleine Clark Wallace Library , G34 Wheaton College 26 E. Main Street, Norton, MA 02766 (508) 286-5601 <+15082865601> Twitter: @WallaceLibrary | Instagram: /wallacelibrary | Facebook: wheatoncollege On Tue, Dec 3, 2019 at 2:20 PM Majewski, Steven Dennis (sdm7g) < sdm7g at virginia.edu> wrote: > > Not at all a solution to the original posters problem, but I was thinking > of proposing that in a future release, we just get rid of the separate OAI > server, and server OAI from public-url/oai . > > Some sites are already doing that ? I assume thru apache or other proxy > server. > ( I think that?s what Lyrasis is doing for the sites they manage. I wish I > had thought of that obvious option before setting up a separate VHOST for > OAI. ) > > The existing OAI server is only proxying data from the backend server > anyway. > > Proxying to the PUI would make configuration simpler, and would have the > side benefit of a consistent OAI endpoint for all public sites. > > ? Steve M. > > > > On Dec 3, 2019, at 2:02 PM, Seth Shaw wrote: > > > > Side note now that Steve pointed out that port 8081 does work, I > recommend changing the PUI port to "80", the default web port, so users > don't need to add the 8081 port to access your site. > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Fri Dec 6 09:13:13 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 6 Dec 2019 14:13:13 +0000 Subject: [Archivesspace_Users_Group] Deadline December 9 - Volunteer for the next ArchivesSpace online forum Message-ID: Dear ArchivesSpace community, The final date to volunteer for the working group to plan for our second ArchivesSpace online forum is Monday, December 9th! Planned for early spring 2020, this event will build on the success of the 2019 Online Forum, which had over 400 registrants, participating from 7 different countries. We would love this event to highlight the work institutions near and far are doing to adapt and integrate ArchivesSpace into their systems and workflows. We expect to offer a variety of activities aimed at building community connections and contacts among our users. All ideas are welcome! All community members are welcome to volunteer for this working group. We especially encourage our Small and Very Small members as well as non-U.S. members to join in envisioning the next iteration of this event. We will schedule meetings and the forum itself in ways that allow for participation across time zones. If you would like to volunteer, please respond on or before December 9, 2019. And if you have any questions, contact Jessica at jessica.crouch at lyrasis.org. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From dundon at ucsc.edu Fri Dec 6 13:07:07 2019 From: dundon at ucsc.edu (Kate Dundon) Date: Fri, 6 Dec 2019 10:07:07 -0800 Subject: [Archivesspace_Users_Group] Language notes added randomly V2.7.0 Message-ID: Hi there, We've noticed an issue after our recent upgrade to V2.7.0. New language information has been added to over 100 archival objects throughout an existing resource record at seemingly random places (irregularly at item, sub-series, and series levels). There was no existing language information present in these objects prior to the upgrade. Has anyone else run into this issue? Is this something the batch_update_langmaterials_from_note plugin would address? The EAD export is attached. Thank you, Kate Dundon Supervisory Archivist Special Collections & Archives University of California, Santa Cruz 831-502-7587 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: UA.041_20191206_173145_UTC__ead.xml Type: text/xml Size: 951654 bytes Desc: not available URL: From scheirw at newschool.edu Sat Dec 7 16:54:49 2019 From: scheirw at newschool.edu (Wendy Scheir) Date: Sat, 7 Dec 2019 16:54:49 -0500 Subject: [Archivesspace_Users_Group] bulk shift to top container Message-ID: Hi, We're new explorers in ArchivesSpace, working in a test instance of version 2.1. I've encountered 2 top container questions that I can't find or figure out the answer to, and hope you seasoned experts will be able to help. 1. If one wants to move multiple instances associated with a particular top container to instead be associated with a different, existing top container, how does one do that in a batch, without needing to click into each instance to make the change? In other words, if we're physically shifting the contents of Box 1 into Box 3, and Box 3 already exists and has other materials in it, can we perform something like a transfer or merge of Box 1 into Box 3 in ASpace? 2. Similarly, if we have a Box 1 within a resource that has a barcode, and a Box 1 that does not have a barcode, can we batch reassign instances associated with Box 1 without bcs to the Box 1 with bcs? With thanks, Wendy ________________________________ Wendy Scheir Director THE NEW SCHOOL ARCHIVES and SPECIAL COLLECTIONS 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 library.newschool.edu/archives https://digitalarchives.library.newschool.edu @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhack at mcdaniel.edu Mon Dec 9 13:34:07 2019 From: jhack at mcdaniel.edu (Janet Hack) Date: Mon, 9 Dec 2019 18:34:07 +0000 Subject: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace In-Reply-To: <1C67B489-1856-4D5D-B36E-F3B76A475BBA@virginia.edu> References: <56DB844F-459E-4734-96C3-B45156DDF88D@virginia.edu> , <1C67B489-1856-4D5D-B36E-F3B76A475BBA@virginia.edu> Message-ID: So, I finally got some time to get back to this and still can't get it to work. After updating the en.yml file located at plugins/local/public/locales/ to the following: en: brand: McDaniel Archives title: McDaniel College Archives Catalog home: Home welcome_message: HEY HEY HEY! ! and restarting the server, I get the following fatal error message in the log: I18n::InvalidLocaleData (can not load translations from /opt/archivesspace/archivesspace-2.7.0/plugins/local/public/locales/en.yml: # ?Any suggestions would be greatly appreciated. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Friday, November 22, 2019 3:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace On Nov 22, 2019, at 2:49 PM, Blake Carver > wrote: I think that doc is out of date, this might be more update: https://github.com/archivesspace/tech-docs/blob/master/customization/locales.md Although, that doc has an error in the whitespace/indentation of the example. ?brand:? should be less indented. ? Steve. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, November 22, 2019 2:24 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace One thing to check: the spaces and indentation in .yml files are significant, and you can?t mix tabs(*) with spaces, so you should make sure that you haven?t accidentally inserted a tab when editing. You can edit the file in place for testing, but for normal production, I advise copying the values you want to change into plugins/local/public/locales/en.yml and editing them there. But again, you have to be careful to preserve .yml hierarchy. You may also eventually want to try copying some of the shared view templates into plugins/local/public/views/shared/ and editing those. It?s easier to manage upgrades if you keep your changes in plugins directories. (*) In fact, googling this, I see it doesn?t like tabs at all. Must be only spaces. ? Steve M. On Nov 22, 2019, at 1:50 PM, Janet Hack > wrote: Greetings, we are new to ArchivesSpace and are trying to change the wording on our public-facing pages https://archivesspace.mcdaniel.edu/. We want to change the header title from the standard "ArchivesSpace Public Interface" and we would like to put in a custom welcome message. I have tried editing the en.yml file following the instructions at https://archivesspace.github.io/archivesspace/user/customizing-text-in-archivesspace/ with no success. Any assistance would be greatly appreciated. Please feel free to contact me off-list. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Dec 9 14:06:12 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 9 Dec 2019 19:06:12 +0000 Subject: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace In-Reply-To: References: <56DB844F-459E-4734-96C3-B45156DDF88D@virginia.edu> <1C67B489-1856-4D5D-B36E-F3B76A475BBA@virginia.edu> Message-ID: There shouldn?t be a text value after ?brand:? The value of en.brand is the hash of the following values, so that en.brand.title, for example, maps to a value. If you take out that text it should work: en: brand: title: McDaniel College Archives Catalog home: Home welcome_message: HEY HEY HEY! ! Error message is a bit confusing, but it?s trying to say it can?t assign mappings of title, home, welcome_message, to en.brand because it already has a string value of ?McDaniel Archives? . > On Dec 9, 2019, at 1:34 PM, Janet Hack wrote: > > So, I finally got some time to get back to this and still can't get it to work. > > After updating the en.yml file located at plugins/local/public/locales/ to the following: > > en: > brand: McDaniel Archives > title: McDaniel College Archives Catalog > home: Home > welcome_message: HEY HEY HEY! ! > and restarting the server, I get the following fatal error message in the log: > I18n::InvalidLocaleData (can not load translations from /opt/archivesspace/archivesspace-2.7.0/plugins/local/public/locales/en.yml: # > ?Any suggestions would be greatly appreciated. > > - Janet > > ----------------- > Janet Hack > Science and Online Technologies Librarian > Hoover Library | McDaniel College > 2 College Hill | Westminster, MD 21157-4390 > 410-857-2283 | jhack at mcdaniel.edu > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, November 22, 2019 3:02 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace > > > >> On Nov 22, 2019, at 2:49 PM, Blake Carver > wrote: >> >> I think that doc is out of date, this might be more update: >> https://github.com/archivesspace/tech-docs/blob/master/customization/locales.md >> >> > > > Although, that doc has an error in the whitespace/indentation of the example. ?brand:? should be less indented. ? Steve. > > >> >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > >> Sent: Friday, November 22, 2019 2:24 PM >> To: Archivesspace Users Group > >> Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace >> >> One thing to check: the spaces and indentation in .yml files are significant, and you can?t mix tabs(*) with spaces, so you should make sure that you haven?t accidentally inserted a tab when editing. You can edit the file in place for testing, but for normal production, I advise copying the values you want to change into plugins/local/public/locales/en.yml and editing them there. But again, you have to be careful to preserve .yml hierarchy. >> >> You may also eventually want to try copying some of the shared view templates into plugins/local/public/views/shared/ and editing those. >> It?s easier to manage upgrades if you keep your changes in plugins directories. >> >> (*) In fact, googling this, I see it doesn?t like tabs at all. Must be only spaces. >> >> >> ? Steve M. >> >> >> >>> On Nov 22, 2019, at 1:50 PM, Janet Hack > wrote: >>> >>> Greetings, >>> >>> we are new to ArchivesSpace and are trying to change the wording on our public-facing pages https://archivesspace.mcdaniel.edu/ . We want to change the header title from the standard "ArchivesSpace Public Interface" and we would like to put in a custom welcome message. I have tried editing the en.yml file following the instructions at https://archivesspace.github.io/archivesspace/user/customizing-text-in-archivesspace/ with no success. >>> >>> Any assistance would be greatly appreciated. Please feel free to contact me off-list. >>> >>> - Janet >>> >>> ----------------- >>> Janet Hack >>> Science and Online Technologies Librarian >>> Hoover Library | McDaniel College >>> 2 College Hill | Westminster, MD 21157-4390 >>> 410-857-2283 | jhack at mcdaniel.edu _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4974 bytes Desc: not available URL: From jhack at mcdaniel.edu Mon Dec 9 14:31:12 2019 From: jhack at mcdaniel.edu (Janet Hack) Date: Mon, 9 Dec 2019 19:31:12 +0000 Subject: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace In-Reply-To: References: <56DB844F-459E-4734-96C3-B45156DDF88D@virginia.edu> <1C67B489-1856-4D5D-B36E-F3B76A475BBA@virginia.edu> , Message-ID: That looks like it worked - thanks for your help. A few more questions: * Is it possible to change the wording of the heading "Welcome to ArchivesSpace"? * How can we add line breaks to the Welcome message? Thanks. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Monday, December 9, 2019 2:06 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace There shouldn?t be a text value after ?brand:? The value of en.brand is the hash of the following values, so that en.brand.title, for example, maps to a value. If you take out that text it should work: en: brand: title: McDaniel College Archives Catalog home: Home welcome_message: HEY HEY HEY! ! Error message is a bit confusing, but it?s trying to say it can?t assign mappings of title, home, welcome_message, to en.brand because it already has a string value of ?McDaniel Archives? . On Dec 9, 2019, at 1:34 PM, Janet Hack > wrote: So, I finally got some time to get back to this and still can't get it to work. After updating the en.yml file located at plugins/local/public/locales/ to the following: en: brand: McDaniel Archives title: McDaniel College Archives Catalog home: Home welcome_message: HEY HEY HEY! ! and restarting the server, I get the following fatal error message in the log: I18n::InvalidLocaleData (can not load translations from /opt/archivesspace/archivesspace-2.7.0/plugins/local/public/locales/en.yml: # ?Any suggestions would be greatly appreciated. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, November 22, 2019 3:02 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace On Nov 22, 2019, at 2:49 PM, Blake Carver > wrote: I think that doc is out of date, this might be more update: https://github.com/archivesspace/tech-docs/blob/master/customization/locales.md Although, that doc has an error in the whitespace/indentation of the example. ?brand:? should be less indented. ? Steve. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, November 22, 2019 2:24 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace One thing to check: the spaces and indentation in .yml files are significant, and you can?t mix tabs(*) with spaces, so you should make sure that you haven?t accidentally inserted a tab when editing. You can edit the file in place for testing, but for normal production, I advise copying the values you want to change into plugins/local/public/locales/en.yml and editing them there. But again, you have to be careful to preserve .yml hierarchy. You may also eventually want to try copying some of the shared view templates into plugins/local/public/views/shared/ and editing those. It?s easier to manage upgrades if you keep your changes in plugins directories. (*) In fact, googling this, I see it doesn?t like tabs at all. Must be only spaces. ? Steve M. On Nov 22, 2019, at 1:50 PM, Janet Hack > wrote: Greetings, we are new to ArchivesSpace and are trying to change the wording on our public-facing pages https://archivesspace.mcdaniel.edu/. We want to change the header title from the standard "ArchivesSpace Public Interface" and we would like to put in a custom welcome message. I have tried editing the en.yml file following the instructions at https://archivesspace.github.io/archivesspace/user/customizing-text-in-archivesspace/ with no success. Any assistance would be greatly appreciated. Please feel free to contact me off-list. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdtillman at sdsu.edu Mon Dec 9 14:39:55 2019 From: jdtillman at sdsu.edu (Josh Tillman) Date: Mon, 9 Dec 2019 11:39:55 -0800 Subject: [Archivesspace_Users_Group] Archon to AS migration data issue In-Reply-To: References: <03DE74AE-1BA2-45EA-AA60-7DD3A163369C@lyrasis.org> Message-ID: Hello, I'm still having an issue with the Archon to AS migration. After the migration tool runs, there are empty duplicate boxes showing up at the collection-level. Is there a way to remove them all at once or prevent them from duplicating in the first place? Or does each one have to be deleted manually? Has anyone else had this problem or know where I can find some documentation to fix this issue? Thank you, Josh Tillman PHP Programmer and Database Administrator Library Information Technologies & Digital Initiatives San Diego State University 5500 Campanile Drive San Diego, CA 92182-8050 619.594.1811 jdtillman at sdsu.edu On Tue, Nov 26, 2019 at 3:22 PM Josh Tillman wrote: > Hi Brian, > > Following up. > > I re-migrated with all Archon containers set to Intellectual and it did > the same thing as with all containers set to Physical. > > Is there something else I can do to solve this issue? > > Thank you, > > Josh Tillman > PHP Programmer and Database Administrator > > Library Information Technologies & Digital Initiatives > San Diego State University > 5500 Campanile Drive > San Diego, CA 92182-8050 > 619.594.1811 > jdtillman at sdsu.edu > > > On Mon, Nov 18, 2019 at 9:17 AM Josh Tillman wrote: > >> Hi Brian, >> >> Thanks for your help. >> >> I re-migrated after changing all containers to both Intellectual and >> Physical. That made the problem worse. Each folder also duplicated for each >> item in the folder (i.e. I have 30-40 instances of each folder). >> >> I re-migrated again after changing all containers to just Physical. That >> created all the empty boxes from before but with none of the actual content. >> >> I have not rerun the migration with all containers set to just >> Intellectual yet. >> >> Is there something I'm missing? >> >> Thank you, >> >> Josh Tillman >> PHP Programmer and Database Administrator >> >> Library Information Technologies & Digital Initiatives >> San Diego State University >> 5500 Campanile Drive >> San Diego, CA 92182-8050 >> 619.594.1811 >> jdtillman at sdsu.edu >> >> >> On Wed, Nov 6, 2019 at 10:47 AM Brian Harrington < >> brian.harrington at lyrasis.org> wrote: >> >>> Hi Josh, >>> >>> I?m wondering if there might be a problem with Intellectual vs. Physical >>> containers. Take a look at the Level/Container Manager section in this >>> document >>> https://github.com/archivesspace/tech-docs/blob/master/migrations/migrate_from_archon.md >>> and see if that helps. If that doesn?t fix things, let us know. >>> >>> Thanks, >>> >>> Brian >>> >>> > On Oct 31, 2019, at 3:26 PM, Josh Tillman wrote: >>> > >>> > Hello, >>> > >>> > I'm having an issue with the Archon to AS migration. After the >>> migration tool runs, there are empty duplicate boxes showing up at the >>> collection-level. Is there a way to remove them all at once or prevent them >>> from duplicating in the first place? Or does each one have to be deleted >>> manually? >>> > >>> > Thank you, >>> > >>> > Josh Tillman >>> > PHP Programmer and Database Administrator >>> > >>> > Library Information Technologies & Digital Initiatives >>> > San Diego State University >>> > 5500 Campanile Drive >>> > San Diego, CA 92182-8050 >>> > 619.594.1811 >>> > jdtillman at sdsu.edu >>> > _______________________________________________ >>> > Archivesspace_Users_Group mailing list >>> > Archivesspace_Users_Group at lyralists.lyrasis.org >>> > >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Dec 9 15:24:34 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 9 Dec 2019 20:24:34 +0000 Subject: [Archivesspace_Users_Group] Archon to AS migration data issue In-Reply-To: References: <03DE74AE-1BA2-45EA-AA60-7DD3A163369C@lyrasis.org> Message-ID: <9219364F-8FF7-4146-A53D-ABE0FB8E9706@lyrasis.org> Hi Josh, You are able to bulk delete top containers from the Manage Top Containers area of ArchivesSpace. The Manage Top Containers menu item should be listed in the menu under the gear close to the top right of your ArchivesSpace installation. If you?re not able to access it, you may need to ask your system administrator to adjust your permissions. The search form for Manage Top Containers gives you a number of options, including searching across a resource for the boxes you would like to delete. From the results, pick all of the containers you want to remove, then select Delete Top Containers from the Bulk Operations drop down menu. You?ll get a page that allows you to confirm that you want to delete them. If you confirm deletion, they are gone for good. There?s more documentation about bulk operations for containers in the user manual here. I hope this helps. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] From: on behalf of Josh Tillman Reply-To: Archivesspace Users Group Date: Monday, December 9, 2019 at 2:40 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archon to AS migration data issue Hello, I'm still having an issue with the Archon to AS migration. After the migration tool runs, there are empty duplicate boxes showing up at the collection-level. Is there a way to remove them all at once or prevent them from duplicating in the first place? Or does each one have to be deleted manually? Has anyone else had this problem or know where I can find some documentation to fix this issue? Thank you, Josh Tillman PHP Programmer and Database Administrator Library Information Technologies & Digital Initiatives San Diego State University 5500 Campanile Drive San Diego, CA 92182-8050 619.594.1811 jdtillman at sdsu.edu On Tue, Nov 26, 2019 at 3:22 PM Josh Tillman > wrote: Hi Brian, Following up. I re-migrated with all Archon containers set to Intellectual and it did the same thing as with all containers set to Physical. Is there something else I can do to solve this issue? Thank you, Josh Tillman PHP Programmer and Database Administrator Library Information Technologies & Digital Initiatives San Diego State University 5500 Campanile Drive San Diego, CA 92182-8050 619.594.1811 jdtillman at sdsu.edu On Mon, Nov 18, 2019 at 9:17 AM Josh Tillman > wrote: Hi Brian, Thanks for your help. I re-migrated after changing all containers to both Intellectual and Physical. That made the problem worse. Each folder also duplicated for each item in the folder (i.e. I have 30-40 instances of each folder). I re-migrated again after changing all containers to just Physical. That created all the empty boxes from before but with none of the actual content. I have not rerun the migration with all containers set to just Intellectual yet. Is there something I'm missing? Thank you, Josh Tillman PHP Programmer and Database Administrator Library Information Technologies & Digital Initiatives San Diego State University 5500 Campanile Drive San Diego, CA 92182-8050 619.594.1811 jdtillman at sdsu.edu On Wed, Nov 6, 2019 at 10:47 AM Brian Harrington > wrote: Hi Josh, I?m wondering if there might be a problem with Intellectual vs. Physical containers. Take a look at the Level/Container Manager section in this document https://github.com/archivesspace/tech-docs/blob/master/migrations/migrate_from_archon.md and see if that helps. If that doesn?t fix things, let us know. Thanks, Brian > On Oct 31, 2019, at 3:26 PM, Josh Tillman > wrote: > > Hello, > > I'm having an issue with the Archon to AS migration. After the migration tool runs, there are empty duplicate boxes showing up at the collection-level. Is there a way to remove them all at once or prevent them from duplicating in the first place? Or does each one have to be deleted manually? > > Thank you, > > Josh Tillman > PHP Programmer and Database Administrator > > Library Information Technologies & Digital Initiatives > San Diego State University > 5500 Campanile Drive > San Diego, CA 92182-8050 > 619.594.1811 > jdtillman at sdsu.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29060 bytes Desc: image001.jpg URL: From sdm7g at virginia.edu Mon Dec 9 15:40:52 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 9 Dec 2019 20:40:52 +0000 Subject: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace In-Reply-To: References: <56DB844F-459E-4734-96C3-B45156DDF88D@virginia.edu> <1C67B489-1856-4D5D-B36E-F3B76A475BBA@virginia.edu> Message-ID: <302E907D-4B76-42B8-A7D8-10189AAB8B17@virginia.edu> "Welcome to ArchivesSpace? is en.brand.welcome_message : en: brand: title: ArchivesSpace Public Interface title_link_text: Return to the ArchivesSpace homepage home: Home welcome_head: Welcome to ArchivesSpace welcome_message: |

Search across our collections, digital materials, and more.

welcome_search_label: "Find what you're looking for:" welcome_page_title: ArchivesSpace Public Interface And the default welcome_message above is html with paragraph tags. So you should be able to include multiple paragraphs or other markup or styling. If you want to make deeper changes, you want to edit the view templates and add them to the local plugin as well. Read the Rails Guide for Layout and Rendering: https://guides.rubyonrails.org/layouts_and_rendering.html along with the ArchivesSpace docs on customization. If you view the log file when you are accessing a page, you will see which controller is called as well as all of the views that are rendered for the page requested: [java] I, [2019-12-09T14:42:51.500361 #52422] INFO -- : Started GET "/" for 0:0:0:0:0:0:0:1 at 2019-12-09 14:42:51 -0500 [java] I, [2019-12-09T14:42:51.626236 #52422] INFO -- : Processing by WelcomeController#show as HTMLI, [2019-12-09T14:42:51.626918 #52422] INFO -- : Processing by WelcomeController#show as HTML [java] [java] I, [2019-12-09T14:42:52.917277 #52422] INFO -- : Rendering welcome/show.html.erb within layouts/application [java] I, [2019-12-09T14:42:52.961968 #52422] INFO -- : Rendered shared/_search.html.erb (25.9ms) [java] I, [2019-12-09T14:42:52.963225 #52422] INFO -- : Rendered welcome/show.html.erb within layouts/application (45.1ms) [java] I, [2019-12-09T14:42:52.917654 #52422] INFO -- : Rendering welcome/show.html.erb within layouts/application [java] I, [2019-12-09T14:42:52.962609 #52422] INFO -- : Rendered shared/_search.html.erb (25.9ms) [java] I, [2019-12-09T14:42:52.963542 #52422] INFO -- : Rendered welcome/show.html.erb within layouts/application (45.1ms) [java] I, [2019-12-09T14:43:05.707996 #52422] INFO -- : Rendered shared/_metadata.html.erb (5.5ms) [java] I, [2019-12-09T14:43:05.708551 #52422] INFO -- : Rendered shared/_metadata.html.erb (5.5ms) [java] I, [2019-12-09T14:43:05.719336 #52422] INFO -- : Rendered shared/_skipnav.html.erb (4.8ms) [java] I, [2019-12-09T14:43:05.731258 #52422] INFO -- : Rendered shared/_header.html.erb (8.2ms) [java] I, [2019-12-09T14:43:05.749501 #52422] INFO -- : Rendered shared/_navigation.html.erb (12.5ms) [java] I, [2019-12-09T14:43:05.718912 #52422] INFO -- : Rendered shared/_skipnav.html.erb (4.8ms) [java] I, [2019-12-09T14:43:05.730940 #52422] INFO -- : Rendered shared/_header.html.erb (8.2ms) [java] I, [2019-12-09T14:43:05.749000 #52422] INFO -- : Rendered shared/_navigation.html.erb (12.5ms) [java] I, [2019-12-09T14:43:05.758603 #52422] INFO -- : Rendered shared/_footer.html.erb (4.1ms) [java] I, [2019-12-09T14:43:05.760572 #52422] INFO -- : Completed 200 OK in 14131ms (Views: 12860.0ms) [java] The likeliest templates to modify for branding are probably welcome/show, shared/_header, shared/_footer, and maybe shared/_search . If you look at public/app/views/welcome/show.html.erb, all of those t() function calls are getting locale translations, so if your locale is English, t( ?brand.welcome_message? ) is replaced by the value of en.brand.welcome_message. So you need to look at the page templates if you want to know where some particular text comes from. ( Sometimes, easier to go the other direction: search for a particular text like ?Welcome to ArchivesSpace? in .yml files, then ack thru the view templates for ?brand.welcome_head? to see where it?s used. ) If you want to make changes to that page, copy it into plugins/local/public/views/welcome/show.html.erb ( after creating needed directories ) Any other views you change should be similarly be copied into the corresponding position in plugin directory.

<%= t('brand.welcome_head') %>

<%= t('brand.welcome_message').html_safe %>
<%= render partial: 'shared/search', locals: { :search_url => "/search", :title => t('archive._plural'), :limit_options => [ ["#{t('actions.search')} #{t('search-limits.all')}",''], [t('search-limit', :limit => t('search-limits.resources')),'resource'], [t('search-limit', :limit => t('search-limits.digital')),'digital_object'] ], :field_options => [ ["#{t('search_results.filter.fullrecord')}",''], ["#{t('search_results.filter.title')}",'title'], ["#{t('search_results.filter.creators')}",'creators_text'], ["#{t('search_results.filter.subjects')}",'subjects_text'], ["#{t('search_results.filter.notes')}", 'notes'], ["#{t('search_results.filter.identifier')}", 'four_part_id'] ] } %> One template that you don?t change is public/app/views/layouts/application.html.erb, which is the top level layout that handles the HTML header and shared markup for all of the pages ( i.e. header, footer, navigation, etc. ) . Instead, each plugin can include a views/layout_head.html.erb file, which are included in the HTML header by that application.html.erb template. This is where you can stick custom javascript or css links. > On Dec 9, 2019, at 2:31 PM, Janet Hack wrote: > > That looks like it worked - thanks for your help. > > A few more questions: > Is it possible to change the wording of the heading "Welcome to ArchivesSpace"? > How can we add line breaks to the Welcome message? > Thanks. > > - Janet > > ----------------- > Janet Hack > Science and Online Technologies Librarian > Hoover Library | McDaniel College > 2 College Hill | Westminster, MD 21157-4390 > 410-857-2283 | jhack at mcdaniel.edu > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Monday, December 9, 2019 2:06 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace > > There shouldn?t be a text value after ?brand:? > The value of en.brand is the hash of the following values, so that en.brand.title, for example, maps to a value. > If you take out that text it should work: > > en: > brand: > title: McDaniel College Archives Catalog > home: Home > welcome_message: HEY HEY HEY! ! > > > Error message is a bit confusing, but it?s trying to say it can?t assign mappings of title, home, welcome_message, to en.brand because it already has a string value of ?McDaniel Archives? . > > >> On Dec 9, 2019, at 1:34 PM, Janet Hack > wrote: >> >> So, I finally got some time to get back to this and still can't get it to work. >> >> After updating the en.yml file located at plugins/local/public/locales/ to the following: >> >> en: >> brand: McDaniel Archives >> title: McDaniel College Archives Catalog >> home: Home >> welcome_message: HEY HEY HEY! ! >> and restarting the server, I get the following fatal error message in the log: >> I18n::InvalidLocaleData (can not load translations from /opt/archivesspace/archivesspace-2.7.0/plugins/local/public/locales/en.yml: # >> ?Any suggestions would be greatly appreciated. >> >> - Janet >> >> ----------------- >> Janet Hack >> Science and Online Technologies Librarian >> Hoover Library | McDaniel College >> 2 College Hill | Westminster, MD 21157-4390 >> 410-857-2283 | jhack at mcdaniel.edu >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > >> Sent: Friday, November 22, 2019 3:02 PM >> To: Archivesspace Users Group > >> Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace >> >> >> >>> On Nov 22, 2019, at 2:49 PM, Blake Carver > wrote: >>> >>> I think that doc is out of date, this might be more update: >>> https://github.com/archivesspace/tech-docs/blob/master/customization/locales.md >>> >>> >> >> >> Although, that doc has an error in the whitespace/indentation of the example. ?brand:? should be less indented. ? Steve. >> >> >>> >>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > >>> Sent: Friday, November 22, 2019 2:24 PM >>> To: Archivesspace Users Group > >>> Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace >>> >>> One thing to check: the spaces and indentation in .yml files are significant, and you can?t mix tabs(*) with spaces, so you should make sure that you haven?t accidentally inserted a tab when editing. You can edit the file in place for testing, but for normal production, I advise copying the values you want to change into plugins/local/public/locales/en.yml and editing them there. But again, you have to be careful to preserve .yml hierarchy. >>> >>> You may also eventually want to try copying some of the shared view templates into plugins/local/public/views/shared/ and editing those. >>> It?s easier to manage upgrades if you keep your changes in plugins directories. >>> >>> (*) In fact, googling this, I see it doesn?t like tabs at all. Must be only spaces. >>> >>> >>> ? Steve M. >>> >>> >>> >>>> On Nov 22, 2019, at 1:50 PM, Janet Hack > wrote: >>>> >>>> Greetings, >>>> >>>> we are new to ArchivesSpace and are trying to change the wording on our public-facing pages https://archivesspace.mcdaniel.edu/ . We want to change the header title from the standard "ArchivesSpace Public Interface" and we would like to put in a custom welcome message. I have tried editing the en.yml file following the instructions at https://archivesspace.github.io/archivesspace/user/customizing-text-in-archivesspace/ with no success. >>>> >>>> Any assistance would be greatly appreciated. Please feel free to contact me off-list. >>>> >>>> - Janet >>>> >>>> ----------------- >>>> Janet Hack >>>> Science and Online Technologies Librarian >>>> Hoover Library | McDaniel College >>>> 2 College Hill | Westminster, MD 21157-4390 >>>> 410-857-2283 | jhack at mcdaniel.edu _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4974 bytes Desc: not available URL: From jhack at mcdaniel.edu Mon Dec 9 16:26:52 2019 From: jhack at mcdaniel.edu (Janet Hack) Date: Mon, 9 Dec 2019 21:26:52 +0000 Subject: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace In-Reply-To: <302E907D-4B76-42B8-A7D8-10189AAB8B17@virginia.edu> References: <56DB844F-459E-4734-96C3-B45156DDF88D@virginia.edu> <1C67B489-1856-4D5D-B36E-F3B76A475BBA@virginia.edu> , <302E907D-4B76-42B8-A7D8-10189AAB8B17@virginia.edu> Message-ID: That answered all my questions. Thanks much. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Monday, December 9, 2019 3:40 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace "Welcome to ArchivesSpace? is en.brand.welcome_message : en: brand: title: ArchivesSpace Public Interface title_link_text: Return to the ArchivesSpace homepage home: Home welcome_head: Welcome to ArchivesSpace welcome_message: |

Search across our collections, digital materials, and more.

welcome_search_label: "Find what you're looking for:" welcome_page_title: ArchivesSpace Public Interface And the default welcome_message above is html with paragraph tags. So you should be able to include multiple paragraphs or other markup or styling. If you want to make deeper changes, you want to edit the view templates and add them to the local plugin as well. Read the Rails Guide for Layout and Rendering: https://guides.rubyonrails.org/layouts_and_rendering.html along with the ArchivesSpace docs on customization. If you view the log file when you are accessing a page, you will see which controller is called as well as all of the views that are rendered for the page requested: [java] I, [2019-12-09T14:42:51.500361 #52422] INFO -- : Started GET "/" for 0:0:0:0:0:0:0:1 at 2019-12-09 14:42:51 -0500 [java] I, [2019-12-09T14:42:51.626236 #52422] INFO -- : Processing by WelcomeController#show as HTMLI, [2019-12-09T14:42:51.626918 #52422] INFO -- : Processing by WelcomeController#show as HTML [java] [java] I, [2019-12-09T14:42:52.917277 #52422] INFO -- : Rendering welcome/show.html.erb within layouts/application [java] I, [2019-12-09T14:42:52.961968 #52422] INFO -- : Rendered shared/_search.html.erb (25.9ms) [java] I, [2019-12-09T14:42:52.963225 #52422] INFO -- : Rendered welcome/show.html.erb within layouts/application (45.1ms) [java] I, [2019-12-09T14:42:52.917654 #52422] INFO -- : Rendering welcome/show.html.erb within layouts/application [java] I, [2019-12-09T14:42:52.962609 #52422] INFO -- : Rendered shared/_search.html.erb (25.9ms) [java] I, [2019-12-09T14:42:52.963542 #52422] INFO -- : Rendered welcome/show.html.erb within layouts/application (45.1ms) [java] I, [2019-12-09T14:43:05.707996 #52422] INFO -- : Rendered shared/_metadata.html.erb (5.5ms) [java] I, [2019-12-09T14:43:05.708551 #52422] INFO -- : Rendered shared/_metadata.html.erb (5.5ms) [java] I, [2019-12-09T14:43:05.719336 #52422] INFO -- : Rendered shared/_skipnav.html.erb (4.8ms) [java] I, [2019-12-09T14:43:05.731258 #52422] INFO -- : Rendered shared/_header.html.erb (8.2ms) [java] I, [2019-12-09T14:43:05.749501 #52422] INFO -- : Rendered shared/_navigation.html.erb (12.5ms) [java] I, [2019-12-09T14:43:05.718912 #52422] INFO -- : Rendered shared/_skipnav.html.erb (4.8ms) [java] I, [2019-12-09T14:43:05.730940 #52422] INFO -- : Rendered shared/_header.html.erb (8.2ms) [java] I, [2019-12-09T14:43:05.749000 #52422] INFO -- : Rendered shared/_navigation.html.erb (12.5ms) [java] I, [2019-12-09T14:43:05.758603 #52422] INFO -- : Rendered shared/_footer.html.erb (4.1ms) [java] I, [2019-12-09T14:43:05.760572 #52422] INFO -- : Completed 200 OK in 14131ms (Views: 12860.0ms) [java] The likeliest templates to modify for branding are probably welcome/show, shared/_header, shared/_footer, and maybe shared/_search . If you look at public/app/views/welcome/show.html.erb, all of those t() function calls are getting locale translations, so if your locale is English, t( ?brand.welcome_message? ) is replaced by the value of en.brand.welcome_message. So you need to look at the page templates if you want to know where some particular text comes from. ( Sometimes, easier to go the other direction: search for a particular text like ?Welcome to ArchivesSpace? in .yml files, then ack thru the view templates for ?brand.welcome_head? to see where it?s used. ) If you want to make changes to that page, copy it into plugins/local/public/views/welcome/show.html.erb ( after creating needed directories ) Any other views you change should be similarly be copied into the corresponding position in plugin directory.

<%= t('brand.welcome_head') %>

<%= t('brand.welcome_message').html_safe %>
<%= render partial: 'shared/search', locals: { :search_url => "/search", :title => t('archive._plural'), :limit_options => [ ["#{t('actions.search')} #{t('search-limits.all')}",''], [t('search-limit', :limit => t('search-limits.resources')),'resource'], [t('search-limit', :limit => t('search-limits.digital')),'digital_object'] ], :field_options => [ ["#{t('search_results.filter.fullrecord')}",''], ["#{t('search_results.filter.title')}",'title'], ["#{t('search_results.filter.creators')}",'creators_text'], ["#{t('search_results.filter.subjects')}",'subjects_text'], ["#{t('search_results.filter.notes')}", 'notes'], ["#{t('search_results.filter.identifier')}", 'four_part_id'] ] } %> One template that you don?t change is public/app/views/layouts/application.html.erb, which is the top level layout that handles the HTML header and shared markup for all of the pages ( i.e. header, footer, navigation, etc. ) . Instead, each plugin can include a views/layout_head.html.erb file, which are included in the HTML header by that application.html.erb template. This is where you can stick custom javascript or css links. On Dec 9, 2019, at 2:31 PM, Janet Hack > wrote: That looks like it worked - thanks for your help. A few more questions: * Is it possible to change the wording of the heading "Welcome to ArchivesSpace"? * How can we add line breaks to the Welcome message? Thanks. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Monday, December 9, 2019 2:06 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace There shouldn?t be a text value after ?brand:? The value of en.brand is the hash of the following values, so that en.brand.title, for example, maps to a value. If you take out that text it should work: en: brand: title: McDaniel College Archives Catalog home: Home welcome_message: HEY HEY HEY! ! Error message is a bit confusing, but it?s trying to say it can?t assign mappings of title, home, welcome_message, to en.brand because it already has a string value of ?McDaniel Archives? . On Dec 9, 2019, at 1:34 PM, Janet Hack > wrote: So, I finally got some time to get back to this and still can't get it to work. After updating the en.yml file located at plugins/local/public/locales/ to the following: en: brand: McDaniel Archives title: McDaniel College Archives Catalog home: Home welcome_message: HEY HEY HEY! ! and restarting the server, I get the following fatal error message in the log: I18n::InvalidLocaleData (can not load translations from /opt/archivesspace/archivesspace-2.7.0/plugins/local/public/locales/en.yml: # ?Any suggestions would be greatly appreciated. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, November 22, 2019 3:02 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace On Nov 22, 2019, at 2:49 PM, Blake Carver > wrote: I think that doc is out of date, this might be more update: https://github.com/archivesspace/tech-docs/blob/master/customization/locales.md Although, that doc has an error in the whitespace/indentation of the example. ?brand:? should be less indented. ? Steve. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, November 22, 2019 2:24 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] need help customizing text in ArchivesSpace One thing to check: the spaces and indentation in .yml files are significant, and you can?t mix tabs(*) with spaces, so you should make sure that you haven?t accidentally inserted a tab when editing. You can edit the file in place for testing, but for normal production, I advise copying the values you want to change into plugins/local/public/locales/en.yml and editing them there. But again, you have to be careful to preserve .yml hierarchy. You may also eventually want to try copying some of the shared view templates into plugins/local/public/views/shared/ and editing those. It?s easier to manage upgrades if you keep your changes in plugins directories. (*) In fact, googling this, I see it doesn?t like tabs at all. Must be only spaces. ? Steve M. On Nov 22, 2019, at 1:50 PM, Janet Hack > wrote: Greetings, we are new to ArchivesSpace and are trying to change the wording on our public-facing pages https://archivesspace.mcdaniel.edu/. We want to change the header title from the standard "ArchivesSpace Public Interface" and we would like to put in a custom welcome message. I have tried editing the en.yml file following the instructions at https://archivesspace.github.io/archivesspace/user/customizing-text-in-archivesspace/ with no success. Any assistance would be greatly appreciated. Please feel free to contact me off-list. - Janet ----------------- Janet Hack Science and Online Technologies Librarian Hoover Library | McDaniel College 2 College Hill | Westminster, MD 21157-4390 410-857-2283 | jhack at mcdaniel.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ 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 noah.geraci at ucr.edu Tue Dec 10 12:18:37 2019 From: noah.geraci at ucr.edu (Noah Geraci) Date: Tue, 10 Dec 2019 17:18:37 +0000 Subject: [Archivesspace_Users_Group] harvesting project planning Message-ID: Hi all, My library is looking at setting up OAI-PMH harvesting from ArchivesSpace to Primo and WorldCat. Currently, a cataloger uses the ArchivesSpace MARCXML export as a starting point to manually create and maintain a MARC record for each collection in WorldCat and Alma. We'd like to move away from this for greater efficiency and data consistency. Previous conversations on this list about harvesting logistics have been really helpful, but if you've undertaken similar projects, I'd be curious to talk a bit about the bigger picture. Were there any unexpected or particularly tricky challenges/side effects in moving from a cataloging approach to a harvesting approach? Also curious about experiences with WorldCat Digital Collection Gateway beyond the initial setup. Since it looks like its main scope is harvesting open access digital content, are there any issues with using it to harvest resource records for non-digital archival collections? Thank you! Noah -- Noah Geraci Digital Assets Metadata Librarian UCR | Library P.O. Box 5900 Orbach Library, Room G46 Riverside, CA 92517-5900 (951) 827-2814 | noah.geraci at ucr.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From belaira at union.edu Tue Dec 10 12:46:05 2019 From: belaira at union.edu (Belair, Andrea) Date: Tue, 10 Dec 2019 12:46:05 -0500 Subject: [Archivesspace_Users_Group] harvesting project planning In-Reply-To: References: Message-ID: I would love information on this as well. Thanks, Andrea On Tue, Dec 10, 2019, 12:18 PM Noah Geraci wrote: > Hi all, > > > > My library is looking at setting up OAI-PMH harvesting from ArchivesSpace > to Primo and WorldCat. Currently, a cataloger uses the ArchivesSpace > MARCXML export as a starting point to manually create and maintain a MARC > record for each collection in WorldCat and Alma. We'd like to move away > from this for greater efficiency and data consistency. > > > > Previous conversations on this list about harvesting logistics have been > really helpful, but if you've undertaken similar projects, I'd be curious > to talk a bit about the bigger picture. Were there any unexpected or > particularly tricky challenges/side effects in moving from a cataloging > approach to a harvesting approach? Also curious about experiences with > WorldCat Digital Collection Gateway beyond the initial setup. Since it > looks like its main scope is harvesting open access digital content, are > there any issues with using it to harvest resource records for non-digital > archival collections? > > > > Thank you! > > Noah > > > > -- > > Noah Geraci > > Digital Assets Metadata Librarian > > > > *UC**R *| Library > > P.O. Box 5900 > > Orbach Library, Room G46 > > Riverside, CA 92517-5900 > > > > (951) 827-2814 | noah.geraci at ucr.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanfilippo_thomas at wheatoncollege.edu Tue Dec 10 12:54:59 2019 From: sanfilippo_thomas at wheatoncollege.edu (Thomas San Filippo) Date: Tue, 10 Dec 2019 12:54:59 -0500 Subject: [Archivesspace_Users_Group] harvesting project planning In-Reply-To: References: Message-ID: As would we! *Thomas San Filippo* /Systems and Educational Technology Liaison/ Pronouns: he/him/his; they/them/their(s) Madeleine Clark Wallace Library , G34 Wheaton College 26 E. Main Street, Norton, MA 02766 (508) 286-5601 Twitter: @WallaceLibrary | Instagram: /wallacelibrary | Facebook: wheatoncollege On 12/10/19 12:46 PM, Belair, Andrea wrote: > I would love information on this as well. > Thanks, > Andrea > > On Tue, Dec 10, 2019, 12:18 PM Noah Geraci > wrote: > > Hi all, > > My library is looking at setting up OAI-PMH harvesting from > ArchivesSpace to Primo and WorldCat. Currently, a cataloger uses > the ArchivesSpace MARCXML export as a starting point to manually > create ?and maintain a MARC record for each collection in WorldCat > and Alma. We'd like to move away from this for greater efficiency > and data consistency. > > Previous conversations on this list about harvesting logistics > have been really helpful, but if you've undertaken similar > projects, I'd be curious to talk a bit about the bigger picture. > Were there any unexpected or particularly tricky challenges/side > effects in moving from a cataloging approach to a harvesting > approach? Also curious about experiences with WorldCat Digital > Collection Gateway beyond the initial setup. Since it looks like > its main scope is harvesting open access digital content, are > there any issues with using it to harvest resource records for > non-digital archival collections? > > Thank you! > > Noah > > -- > > Noah Geraci > > Digital Assets Metadata Librarian > > *UC**R *|**Library > > P.O. Box 5900 > > Orbach Library, Room G46 > > Riverside, CA 92517-5900 > > (951) 827-2814 | noah.geraci at ucr.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin_wendler at harvard.edu Tue Dec 10 13:19:07 2019 From: robin_wendler at harvard.edu (Wendler, Robin King) Date: Tue, 10 Dec 2019 18:19:07 +0000 Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input Message-ID: Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. Some of you may remember a proposal we distributed this time last year. A variety of factors delayed the work, so we have significantly revised the proposal based on the valuable feedback provided by the ArchivesSpace community and informed by Harvard archivists' increasing experience with container management in ArchivesSpace. Some proposals have been removed, while others have been added or altered. Additions include * Return to Top Container search results from viewing an individual Top Container record * Bulk or batch function to create new Top Containers, associate existing Locations with them, and link them to multiple existing archival objects. * Bulk operation to delete barcodes from Top Containers * File-upload function to add Locations to Top Containers * Ability to merge Location records The most significant changes to previous proposals include the following: * The proposed additional indicator fields and ILS Bibliographic Record ID field in Top Containers have been removed. * The proposed Note field and Inactive checkbox for Locations, along with all functionality associated with inactive status, have been removed. * Automatic scoping of Container Profiles, Locations, and Location Profiles by repository appears to be too complex, given the community request to make repositories repeatable and the desire for it to be an installation configuration option. In lieu of that, the revised proposal adds a repeatable, optional repository field to container profiles and adds a facet for filtering by repository to browse results for Container Profiles and Locations. * Proposed functionality around Location status has been removed The revised draft proposal is attached to this email and we are asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that the proposal represents a superset of the work we may be able to complete in the next couple of months, and that not all the proposed changes will be addressed at this time. Another caveat: some of the desiderata require further technical design that will determine what approach will be taken. These will be investigated in consultation with Lyrasis ArchivesSpace staff. If you have questions or feedback, please email me at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 18, 2019. We look forward to receiving community input. Best, Robin Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Harvard Library ArchivesSpace Container Management Enhancement Proposal_v2_20191210.pdf Type: application/pdf Size: 407756 bytes Desc: Harvard Library ArchivesSpace Container Management Enhancement Proposal_v2_20191210.pdf URL: From Corey.Schmidt at uga.edu Tue Dec 10 14:09:00 2019 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Tue, 10 Dec 2019 19:09:00 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Message-ID: Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists' Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people's feedback on it. Specifically, I'm looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: UGA_AT-AS_Workflow.pdf Type: application/pdf Size: 160973 bytes Desc: UGA_AT-AS_Workflow.pdf URL: From gboggio at mitre.org Tue Dec 10 16:42:44 2019 From: gboggio at mitre.org (Boggio, Jerry) Date: Tue, 10 Dec 2019 21:42:44 +0000 Subject: [Archivesspace_Users_Group] RuntimeError: Schema Info Mismatch Message-ID: Hello ArchivesSpace Users! Could someone please provide more information on the meaning of this message? In particular, what is represented by the "Expected" and "received" values? RuntimeError: Schema Info Mismatch. Expected 97, received 120 for ASPACE version v2.3.0. If this is an issue with the MySQL database's schema being changed, is there a command/process to roll it back? Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Tue Dec 10 17:21:58 2019 From: ph448 at cam.ac.uk (Peter Heiner) Date: Tue, 10 Dec 2019 22:21:58 +0000 Subject: [Archivesspace_Users_Group] RuntimeError: Schema Info Mismatch In-Reply-To: Message-ID: <4fdc18d4-95a0-44d9-a992-5eefdb1220ac@email.android.com> An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Tue Dec 10 17:22:23 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 10 Dec 2019 22:22:23 +0000 Subject: [Archivesspace_Users_Group] RuntimeError: Schema Info Mismatch In-Reply-To: References: Message-ID: "Expected 97, received 120" So your version of ArchivesSpace wants an older DB version, I don't even know that version of ArchivesSpace that is off the top O' my head, maybe 2.4ish? Somehow your DB is on 120, which is the schema version for 2.6. Someone must've run setup-database.sh on that DB. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Boggio, Jerry Sent: Tuesday, December 10, 2019 4:42 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Versteeg, Steve ; Brotherston, Rob Subject: [Archivesspace_Users_Group] RuntimeError: Schema Info Mismatch Hello ArchivesSpace Users! Could someone please provide more information on the meaning of this message? In particular, what is represented by the ?Expected? and ?received? values? RuntimeError: Schema Info Mismatch. Expected 97, received 120 for ASPACE version v2.3.0. If this is an issue with the MySQL database?s schema being changed, is there a command/process to roll it back? Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Dec 10 18:33:10 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 10 Dec 2019 23:33:10 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow In-Reply-To: References: Message-ID: Corey, First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time. Glancing at your workflow document, it looks like you?ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It?s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn?t be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *should* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend. Regarding the AT to ASpace migration tool, just off the top of my head, I?d also add: 1. if you have linked cross references in your current EAD files, you?ll either want to make sure to run the migration with the ?-refid_original? parameter, or set aside some time after the migration to go back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot of cross references in our source files in the AT, so we opted with that first option, as you can see here: https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/) 2. unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it?s not required to do so). E.g. for our lists in the AT that did not have a title, after the migration we wound up with lists in ASpace that had a title of ?Missing Title?. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the AT someone selected a container type of ?Box? but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of ?Box? around without dropping it during the migration. We had quite a few instances in the AT where someone would add ?Box X, Folder?. That behaved fine in the AT, but once we migrated, that would turn into something like ?Box X, Folder someweirdnumber? (ideally it would?ve just come over as ?Box X?). And unless you have EAD files that aren?t in the AT already, I don?t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the more import options you allow during the migration, the more variety you?ll have in the results. That?s not to say that EAD imports are bad ASpace, since they?ve actually improved on the AT?s EAD import process. Also, long after our migration, we still import EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they?d be hard to create directly in ASpace. However, you?ll have to be mindful of all of the ways that those EAD imports can muddy up your database (the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data?. See the comment here https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16? In other words, free text like ?2.5 Linear feet (4 boxes)? would result in a new extent type with a value of ?Linear Feet (4 boxes)?, which is not a controlled extent type that anyone wants to have around. Okay, that?s probably more info than you wanted, but hopefully some of it?s helpful ? There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal, https://journal.code4lib.org/articles/14871, which describes the migration to ASpace at Columbia University. Keep us posted with how everything goes, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Corey Schmidt Sent: Tuesday, 10 December, 2019 2:09 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists? Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people?s feedback on it. Specifically, I?m looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Wed Dec 11 06:33:10 2019 From: ph448 at cam.ac.uk (Peter Heiner) Date: Wed, 11 Dec 2019 11:33:10 +0000 Subject: [Archivesspace_Users_Group] RuntimeError: Schema Info Mismatch In-Reply-To: <4fdc18d4-95a0-44d9-a992-5eefdb1220ac@email.android.com> References: <4fdc18d4-95a0-44d9-a992-5eefdb1220ac@email.android.com> Message-ID: <20191211113310.dm74dyglwzn43msn@axolotl> Apologies for sending HTML mail to the list, I have failed to set my GMail up correctly. Reproducing in plain text for convenience. On 10 Dec 2019 21:42, "Boggio, Jerry" wrote: > Could someone please provide more information on the meaning of this > message? In particular, what is represented by the ?Expected? and > ?received? values? > > RuntimeError: Schema Info Mismatch. Expected 97, received 120 for > ASPACE version v2.3.0 This means that the database has at some point been updated using ArchivesSpace 2.6.0 (you can find the corresponding schema version number in the release notes), but a version 2.3.0 instance has now been started over it. This happened to me some time ago when I updated a symlink pointing to my current installation to point to the new version but configuration management has reset it to point to the old one. Generally, I would recommend moving forward with the application version and not back with the database version, even if there are facilities to do the latter. p From Corey.Schmidt at uga.edu Wed Dec 11 10:19:30 2019 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 11 Dec 2019 15:19:30 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow In-Reply-To: References: Message-ID: Mark, Thank you so much for the wonderful info! I am just beginning to dive into the data, but I will look out for linked cross references and the creation of new data in ArchivesSpace. We don?t have any EADs that exist outside of AT so far as I?m aware, so the process of exporting from AT, cleaning up, then reimporting might be unnecessary as you pointed out. If it?s possible to update the AT database directly, that would save so much time and effort. The articles you linked were very helpful and should give me a basis for how to approach this and other potential problems. Thanks again! Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Tuesday, December 10, 2019 6:33 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Corey, First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time. Glancing at your workflow document, it looks like you?ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It?s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn?t be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *should* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend. Regarding the AT to ASpace migration tool, just off the top of my head, I?d also add: 1. if you have linked cross references in your current EAD files, you?ll either want to make sure to run the migration with the ?-refid_original? parameter, or set aside some time after the migration to go back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot of cross references in our source files in the AT, so we opted with that first option, as you can see here: https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/) 2. unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it?s not required to do so). E.g. for our lists in the AT that did not have a title, after the migration we wound up with lists in ASpace that had a title of ?Missing Title?. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the AT someone selected a container type of ?Box? but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of ?Box? around without dropping it during the migration. We had quite a few instances in the AT where someone would add ?Box X, Folder?. That behaved fine in the AT, but once we migrated, that would turn into something like ?Box X, Folder someweirdnumber? (ideally it would?ve just come over as ?Box X?). And unless you have EAD files that aren?t in the AT already, I don?t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the more import options you allow during the migration, the more variety you?ll have in the results. That?s not to say that EAD imports are bad ASpace, since they?ve actually improved on the AT?s EAD import process. Also, long after our migration, we still import EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they?d be hard to create directly in ASpace. However, you?ll have to be mindful of all of the ways that those EAD imports can muddy up your database (the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data?. See the comment here https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16? In other words, free text like ?2.5 Linear feet (4 boxes)? would result in a new extent type with a value of ?Linear Feet (4 boxes)?, which is not a controlled extent type that anyone wants to have around. Okay, that?s probably more info than you wanted, but hopefully some of it?s helpful ? There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal, https://journal.code4lib.org/articles/14871, which describes the migration to ASpace at Columbia University. Keep us posted with how everything goes, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Corey Schmidt Sent: Tuesday, 10 December, 2019 2:09 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists? Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people?s feedback on it. Specifically, I?m looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Wed Dec 11 12:12:36 2019 From: noah.huffman at duke.edu (Noah Huffman) Date: Wed, 11 Dec 2019 17:12:36 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow In-Reply-To: References: Message-ID: Hi Corey, I?d highly recommend doing as much data cleanup as possible directly in your AT database, particularly extent type values, container type values, etc. Of course, be sure to back up your database? If you?re comfortable writing/running SQL queries, you can connect a free database management tool like MySQL Workbench to your AT backend database to review/clean your data in bulk. Alternatively, there are other database management tools like Navicat that let you review and edit the backend database tables in a graphical spreadsheet-like editor (without having to write SQL). I used Navicat to clean up a lot of AT data prior to migrating to ASpace. If you can do all your cleanup in the 14-day trial period, then you don?t have to buy the software! Best of luck, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Corey Schmidt Sent: Wednesday, December 11, 2019 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Mark, Thank you so much for the wonderful info! I am just beginning to dive into the data, but I will look out for linked cross references and the creation of new data in ArchivesSpace. We don?t have any EADs that exist outside of AT so far as I?m aware, so the process of exporting from AT, cleaning up, then reimporting might be unnecessary as you pointed out. If it?s possible to update the AT database directly, that would save so much time and effort. The articles you linked were very helpful and should give me a basis for how to approach this and other potential problems. Thanks again! Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, December 10, 2019 6:33 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Corey, First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time. Glancing at your workflow document, it looks like you?ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It?s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn?t be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *should* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend. Regarding the AT to ASpace migration tool, just off the top of my head, I?d also add: 1. if you have linked cross references in your current EAD files, you?ll either want to make sure to run the migration with the ?-refid_original? parameter, or set aside some time after the migration to go back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot of cross references in our source files in the AT, so we opted with that first option, as you can see here: https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/) 2. unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it?s not required to do so). E.g. for our lists in the AT that did not have a title, after the migration we wound up with lists in ASpace that had a title of ?Missing Title?. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the AT someone selected a container type of ?Box? but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of ?Box? around without dropping it during the migration. We had quite a few instances in the AT where someone would add ?Box X, Folder?. That behaved fine in the AT, but once we migrated, that would turn into something like ?Box X, Folder someweirdnumber? (ideally it would?ve just come over as ?Box X?). And unless you have EAD files that aren?t in the AT already, I don?t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the more import options you allow during the migration, the more variety you?ll have in the results. That?s not to say that EAD imports are bad ASpace, since they?ve actually improved on the AT?s EAD import process. Also, long after our migration, we still import EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they?d be hard to create directly in ASpace. However, you?ll have to be mindful of all of the ways that those EAD imports can muddy up your database (the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data?. See the comment here https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16? In other words, free text like ?2.5 Linear feet (4 boxes)? would result in a new extent type with a value of ?Linear Feet (4 boxes)?, which is not a controlled extent type that anyone wants to have around. Okay, that?s probably more info than you wanted, but hopefully some of it?s helpful ? There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal, https://journal.code4lib.org/articles/14871, which describes the migration to ASpace at Columbia University. Keep us posted with how everything goes, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Corey Schmidt Sent: Tuesday, 10 December, 2019 2:09 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists? Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people?s feedback on it. Specifically, I?m looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Dec 11 15:50:54 2019 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 11 Dec 2019 20:50:54 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow In-Reply-To: References: Message-ID: Noah, Thank you for the advice! I have copies of databases made, but I do not have access to the MySQL databases directly, as that is being hosted by a third-party. If I can get access to them, I should be able to experiment with cleaning them up directly with SQL. I have some experience working with SQLite, so it shouldn?t be too hard to learn. I?ll look into using Navicat too, as it seems like a pretty handy tool. Thanks, Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Noah Huffman Sent: Wednesday, December 11, 2019 12:13 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Hi Corey, I?d highly recommend doing as much data cleanup as possible directly in your AT database, particularly extent type values, container type values, etc. Of course, be sure to back up your database? If you?re comfortable writing/running SQL queries, you can connect a free database management tool like MySQL Workbench to your AT backend database to review/clean your data in bulk. Alternatively, there are other database management tools like Navicat that let you review and edit the backend database tables in a graphical spreadsheet-like editor (without having to write SQL). I used Navicat to clean up a lot of AT data prior to migrating to ASpace. If you can do all your cleanup in the 14-day trial period, then you don?t have to buy the software! Best of luck, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Corey Schmidt Sent: Wednesday, December 11, 2019 10:20 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Mark, Thank you so much for the wonderful info! I am just beginning to dive into the data, but I will look out for linked cross references and the creation of new data in ArchivesSpace. We don?t have any EADs that exist outside of AT so far as I?m aware, so the process of exporting from AT, cleaning up, then reimporting might be unnecessary as you pointed out. If it?s possible to update the AT database directly, that would save so much time and effort. The articles you linked were very helpful and should give me a basis for how to approach this and other potential problems. Thanks again! Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, December 10, 2019 6:33 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Corey, First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time. Glancing at your workflow document, it looks like you?ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It?s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn?t be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *should* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend. Regarding the AT to ASpace migration tool, just off the top of my head, I?d also add: 1. if you have linked cross references in your current EAD files, you?ll either want to make sure to run the migration with the ?-refid_original? parameter, or set aside some time after the migration to go back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot of cross references in our source files in the AT, so we opted with that first option, as you can see here: https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/) 2. unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it?s not required to do so). E.g. for our lists in the AT that did not have a title, after the migration we wound up with lists in ASpace that had a title of ?Missing Title?. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the AT someone selected a container type of ?Box? but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of ?Box? around without dropping it during the migration. We had quite a few instances in the AT where someone would add ?Box X, Folder?. That behaved fine in the AT, but once we migrated, that would turn into something like ?Box X, Folder someweirdnumber? (ideally it would?ve just come over as ?Box X?). And unless you have EAD files that aren?t in the AT already, I don?t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the more import options you allow during the migration, the more variety you?ll have in the results. That?s not to say that EAD imports are bad ASpace, since they?ve actually improved on the AT?s EAD import process. Also, long after our migration, we still import EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they?d be hard to create directly in ASpace. However, you?ll have to be mindful of all of the ways that those EAD imports can muddy up your database (the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data?. See the comment here https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16? In other words, free text like ?2.5 Linear feet (4 boxes)? would result in a new extent type with a value of ?Linear Feet (4 boxes)?, which is not a controlled extent type that anyone wants to have around. Okay, that?s probably more info than you wanted, but hopefully some of it?s helpful ? There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal, https://journal.code4lib.org/articles/14871, which describes the migration to ASpace at Columbia University. Keep us posted with how everything goes, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Corey Schmidt Sent: Tuesday, 10 December, 2019 2:09 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists? Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people?s feedback on it. Specifically, I?m looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laney.mcglohon at lyrasis.org Thu Dec 12 13:07:56 2019 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Thu, 12 Dec 2019 18:07:56 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Message-ID: <8D37CE5B-13C6-4BCC-A778-82B7EB09EA26@lyrasis.org> Hi Corey, I wanted to make sure that you knew that the current version of the AT Migration Tool will only work up to ArchivesSpace version 2.6.0 so, when testing and for production, make sure you migrate into ArchivesSpace version 2.6.0 and then upgrade into 2.7.0 or higher from there. Best, Laney From: on behalf of Corey Schmidt Reply-To: Archivesspace Users Group Date: Wednesday, December 11, 2019 at 12:51 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Noah, Thank you for the advice! I have copies of databases made, but I do not have access to the MySQL databases directly, as that is being hosted by a third-party. If I can get access to them, I should be able to experiment with cleaning them up directly with SQL. I have some experience working with SQLite, so it shouldn?t be too hard to learn. I?ll look into using Navicat too, as it seems like a pretty handy tool. Thanks, Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Noah Huffman Sent: Wednesday, December 11, 2019 12:13 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Hi Corey, I?d highly recommend doing as much data cleanup as possible directly in your AT database, particularly extent type values, container type values, etc. Of course, be sure to back up your database? If you?re comfortable writing/running SQL queries, you can connect a free database management tool like MySQL Workbench to your AT backend database to review/clean your data in bulk. Alternatively, there are other database management tools like Navicat that let you review and edit the backend database tables in a graphical spreadsheet-like editor (without having to write SQL). I used Navicat to clean up a lot of AT data prior to migrating to ASpace. If you can do all your cleanup in the 14-day trial period, then you don?t have to buy the software! Best of luck, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Corey Schmidt Sent: Wednesday, December 11, 2019 10:20 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Mark, Thank you so much for the wonderful info! I am just beginning to dive into the data, but I will look out for linked cross references and the creation of new data in ArchivesSpace. We don?t have any EADs that exist outside of AT so far as I?m aware, so the process of exporting from AT, cleaning up, then reimporting might be unnecessary as you pointed out. If it?s possible to update the AT database directly, that would save so much time and effort. The articles you linked were very helpful and should give me a basis for how to approach this and other potential problems. Thanks again! Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, December 10, 2019 6:33 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Corey, First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time. Glancing at your workflow document, it looks like you?ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It?s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn?t be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *should* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend. Regarding the AT to ASpace migration tool, just off the top of my head, I?d also add: 1. if you have linked cross references in your current EAD files, you?ll either want to make sure to run the migration with the ?-refid_original? parameter, or set aside some time after the migration to go back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot of cross references in our source files in the AT, so we opted with that first option, as you can see here: https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/) 2. unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it?s not required to do so). E.g. for our lists in the AT that did not have a title, after the migration we wound up with lists in ASpace that had a title of ?Missing Title?. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the AT someone selected a container type of ?Box? but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of ?Box? around without dropping it during the migration. We had quite a few instances in the AT where someone would add ?Box X, Folder?. That behaved fine in the AT, but once we migrated, that would turn into something like ?Box X, Folder someweirdnumber? (ideally it would?ve just come over as ?Box X?). And unless you have EAD files that aren?t in the AT already, I don?t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the more import options you allow during the migration, the more variety you?ll have in the results. That?s not to say that EAD imports are bad ASpace, since they?ve actually improved on the AT?s EAD import process. Also, long after our migration, we still import EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they?d be hard to create directly in ASpace. However, you?ll have to be mindful of all of the ways that those EAD imports can muddy up your database (the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data?. See the comment here https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16? In other words, free text like ?2.5 Linear feet (4 boxes)? would result in a new extent type with a value of ?Linear Feet (4 boxes)?, which is not a controlled extent type that anyone wants to have around. Okay, that?s probably more info than you wanted, but hopefully some of it?s helpful ? There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal, https://journal.code4lib.org/articles/14871, which describes the migration to ASpace at Columbia University. Keep us posted with how everything goes, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Corey Schmidt Sent: Tuesday, 10 December, 2019 2:09 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists? Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people?s feedback on it. Specifically, I?m looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Thu Dec 12 15:05:36 2019 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Thu, 12 Dec 2019 20:05:36 +0000 Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow In-Reply-To: <8D37CE5B-13C6-4BCC-A778-82B7EB09EA26@lyrasis.org> References: <8D37CE5B-13C6-4BCC-A778-82B7EB09EA26@lyrasis.org> Message-ID: Laney, Thank you for the heads up! Fortunately, we are running ArchivesSpace version 2.6.0 and my first test migration has been running smoothly (55 hours later). I?ll follow up if I have any issues. Thanks, Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Laney McGlohon Sent: Thursday, December 12, 2019 1:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Hi Corey, I wanted to make sure that you knew that the current version of the AT Migration Tool will only work up to ArchivesSpace version 2.6.0 so, when testing and for production, make sure you migrate into ArchivesSpace version 2.6.0 and then upgrade into 2.7.0 or higher from there. Best, Laney From: > on behalf of Corey Schmidt > Reply-To: Archivesspace Users Group > Date: Wednesday, December 11, 2019 at 12:51 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Noah, Thank you for the advice! I have copies of databases made, but I do not have access to the MySQL databases directly, as that is being hosted by a third-party. If I can get access to them, I should be able to experiment with cleaning them up directly with SQL. I have some experience working with SQLite, so it shouldn?t be too hard to learn. I?ll look into using Navicat too, as it seems like a pretty handy tool. Thanks, Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Noah Huffman Sent: Wednesday, December 11, 2019 12:13 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Hi Corey, I?d highly recommend doing as much data cleanup as possible directly in your AT database, particularly extent type values, container type values, etc. Of course, be sure to back up your database? If you?re comfortable writing/running SQL queries, you can connect a free database management tool like MySQL Workbench to your AT backend database to review/clean your data in bulk. Alternatively, there are other database management tools like Navicat that let you review and edit the backend database tables in a graphical spreadsheet-like editor (without having to write SQL). I used Navicat to clean up a lot of AT data prior to migrating to ASpace. If you can do all your cleanup in the 14-day trial period, then you don?t have to buy the software! Best of luck, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Corey Schmidt Sent: Wednesday, December 11, 2019 10:20 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Mark, Thank you so much for the wonderful info! I am just beginning to dive into the data, but I will look out for linked cross references and the creation of new data in ArchivesSpace. We don?t have any EADs that exist outside of AT so far as I?m aware, so the process of exporting from AT, cleaning up, then reimporting might be unnecessary as you pointed out. If it?s possible to update the AT database directly, that would save so much time and effort. The articles you linked were very helpful and should give me a basis for how to approach this and other potential problems. Thanks again! Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, December 10, 2019 6:33 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow [External Sender] Corey, First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time. Glancing at your workflow document, it looks like you?ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It?s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn?t be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *should* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend. Regarding the AT to ASpace migration tool, just off the top of my head, I?d also add: 1. if you have linked cross references in your current EAD files, you?ll either want to make sure to run the migration with the ?-refid_original? parameter, or set aside some time after the migration to go back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot of cross references in our source files in the AT, so we opted with that first option, as you can see here: https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/) 2. unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it?s not required to do so). E.g. for our lists in the AT that did not have a title, after the migration we wound up with lists in ASpace that had a title of ?Missing Title?. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the AT someone selected a container type of ?Box? but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of ?Box? around without dropping it during the migration. We had quite a few instances in the AT where someone would add ?Box X, Folder?. That behaved fine in the AT, but once we migrated, that would turn into something like ?Box X, Folder someweirdnumber? (ideally it would?ve just come over as ?Box X?). And unless you have EAD files that aren?t in the AT already, I don?t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the more import options you allow during the migration, the more variety you?ll have in the results. That?s not to say that EAD imports are bad ASpace, since they?ve actually improved on the AT?s EAD import process. Also, long after our migration, we still import EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they?d be hard to create directly in ASpace. However, you?ll have to be mindful of all of the ways that those EAD imports can muddy up your database (the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data?. See the comment here https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16? In other words, free text like ?2.5 Linear feet (4 boxes)? would result in a new extent type with a value of ?Linear Feet (4 boxes)?, which is not a controlled extent type that anyone wants to have around. Okay, that?s probably more info than you wanted, but hopefully some of it?s helpful ? There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal, https://journal.code4lib.org/articles/14871, which describes the migration to ASpace at Columbia University. Keep us posted with how everything goes, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Corey Schmidt Sent: Tuesday, 10 December, 2019 2:09 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow Dear ArchivesSpace Community, Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists? Toolkit to ArchivesSpace and revamping our public interface to include resources from both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies. I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people?s feedback on it. Specifically, I?m looking for help identifying any missing processes, changing the order of the steps involved, or anything else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan. Thank you for your time and assistance! I have attached the workflow to this email. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager | University of Georgia Libraries Email: Corey.Schmidt at uga.edu Phone: +1-706-542-8151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Thu Dec 12 15:44:52 2019 From: gordon_daines at byu.edu (Gordon Daines) Date: Thu, 12 Dec 2019 20:44:52 +0000 Subject: [Archivesspace_Users_Group] Report on the 2nd Quarter meeting of the ArchivesSpace Governance Board Message-ID: Dear ArchivesSpace members, The ArchivesSpace Governance Board held its 2nd Quarter meeting virtually on December 5th. Below is a brief report of the meeting. We reviewed the ongoing work of the Technical Advisory Council and the User Advisory Council. We would like to thank the members of these councils for their incredible contributions. It is good to see these councils continue to evolve and strengthen in terms of structure and interaction with each other. The operations update highlighted progress with the new Help Center due to launch in mid-December, along with continued work with member institutions to increase development activity and strengthen the ArchivesSpace software. The financial reports showed a strong budgetary position and increasing membership. Given the recent merger of LYRASIS with DuraSpace, the board has begun learning more about the former DuraSpace programs and began discussing potential opportunities for programs to work together. John Wilkin graciously agreed to chair the Nominating Committee this year. We appreciate him taking on this pivotal responsibility. He has already formed a strong group of committee members to start the process. If you are interested in a more active role in the ArchivesSpace Community, please let us know. The Board also discussed ways to strengthen the processes and procedures for naming the Board liaisons to the Advisory Councils and discussed interest in continuing our annual sessions to incorporate member feedback into strategic planning. In closing, I am very happy to report that the ArchivesSpace membership organization continues to be vital and growing, with members making contributions to all facets of the program. As always, the Board welcomes your feedback. Feel free to reach out directly to me or to your elected representative. Respectfully, Gordon Daines Chair, ArchivesSpace Governance Board _________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of Yellowstone National Park collection Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Fri Dec 13 15:03:31 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 13 Dec 2019 20:03:31 +0000 Subject: [Archivesspace_Users_Group] New ArchivesSpace Help Center now available Message-ID: <153E58FE-0D1C-4B32-AE93-5D5E6D3959E3@lyrasis.org> Dear ArchivesSpace members, We?re pleased to announce that the new ArchivesSpace Help Center, with an improved user manual and new training videos, is now available. Click here to learn more about accessing and navigating the Help Center. The new Help Center is part of our larger Confluence site, which includes information about many of our community and development activities. The current site (http://docs.archivesspace.org) will be up through early 2020, but it will be closed to new user signups and no content will be updated. The new and improved content is thanks to the efforts of our User Documentation sub-team and our training corps. We are in the process of migrating accounts from the previous Help Center this week ? we expect to conclude this process no later than Monday, December 16. Depending on whether you already had an account in Confluence or the previous Help Center, here is what to do: * If you already had an account for our Confluence site, you do not need to do anything. Privileges to access the Help Center area have been added to your account as long as your email address on Confluence and the email address used in the previous Help Center were the same. You will not receive a separate invitation for the Help Center; access will just appear in your account. If you are unsure whether you already had a Confluence account or haven?t used it in awhile, please contact us. * If you had an account on the previous Help Center site but did not already have an account for our Confluence site, you will receive an email invitation from Atlassian to set up your account and get access to the new area. The subject line will be ArchivesSpace has invited you to Confluence. This account will also give you enhanced access to our other Confluence areas. Passwords from the old site will not carry over, so you will need to create a password as part of setting up your Confluence account. If you do not see this invitation in your inbox, please check your spam area as it may have been delivered there. * If you did not have an account on the previous Help Center site and do not already have a Confluence account, follow these steps to sign up for an account. We hope you enjoy the new content and look forward to the enhanced opportunities for community participation that the new site will allow. Thanks for your patience as we make this transition and please do let us know if you have any questions. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29060 bytes Desc: image001.jpg URL: From gcoddington at mcdaniel.edu Mon Dec 16 10:30:06 2019 From: gcoddington at mcdaniel.edu (Gwenlyn Coddington) Date: Mon, 16 Dec 2019 15:30:06 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records Message-ID: Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message ("We're sorry, but something went wrong"). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maura.carbone at yale.edu Mon Dec 16 10:56:56 2019 From: maura.carbone at yale.edu (Carbone, Maura) Date: Mon, 16 Dec 2019 15:56:56 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records Message-ID: Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: on behalf of Gwenlyn Coddington Reply-To: Archivesspace Users Group Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gcoddington at mcdaniel.edu Mon Dec 16 11:23:57 2019 From: gcoddington at mcdaniel.edu (Gwenlyn Coddington) Date: Mon, 16 Dec 2019 16:23:57 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records In-Reply-To: References: Message-ID: Hi Maura, Thank you so much for responding to my question. Unfortunately, I do not know how to examine the logs for errors. Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 10:57 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Dec 16 14:30:48 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 16 Dec 2019 19:30:48 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records In-Reply-To: References: Message-ID: Gwen, Which version of ArchivesSpace are you on? Here?s an example of an agent record in the PUI that uses both the Dates of Existence subrecord (for specific birth and death dates) aas the date field in the Names subrecord: https://archives.yale.edu/agents/people/81438 Also, have you tried to just re-save the agent record and see if that clears things up? Usually when you get the ?We?re sorry, but something went wrong message?, the issues generally has to do with the index. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gwenlyn Coddington Sent: Monday, 16 December, 2019 11:24 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Maura, Thank you so much for responding to my question. Unfortunately, I do not know how to examine the logs for errors. Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 10:57 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gcoddington at mcdaniel.edu Mon Dec 16 14:40:54 2019 From: gcoddington at mcdaniel.edu (Gwenlyn Coddington) Date: Mon, 16 Dec 2019 19:40:54 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records In-Reply-To: References: Message-ID: Hi Mark, Thanks for your help! We recently upgraded to v 2.7.0. I tried resaving the record as you suggested and unfortunately that did not clear it up. I also found this problem in the Sandbox Demo as I was trying to recreate what was happening in our system: entering the date in the expression field rather than a normalized begin and end date gave the same error response in the PUI but it cleared up when I switched to the begin and end fields. So I guess I know how to fix it but I want to know why its rejecting dates in the Expression field. Thanks again, Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, December 16, 2019 2:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Gwen, Which version of ArchivesSpace are you on? Here?s an example of an agent record in the PUI that uses both the Dates of Existence subrecord (for specific birth and death dates) aas the date field in the Names subrecord: https://archives.yale.edu/agents/people/81438 Also, have you tried to just re-save the agent record and see if that clears things up? Usually when you get the ?We?re sorry, but something went wrong message?, the issues generally has to do with the index. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gwenlyn Coddington Sent: Monday, 16 December, 2019 11:24 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Maura, Thank you so much for responding to my question. Unfortunately, I do not know how to examine the logs for errors. Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 10:57 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maura.carbone at yale.edu Mon Dec 16 15:11:06 2019 From: maura.carbone at yale.edu (Carbone, Maura) Date: Mon, 16 Dec 2019 20:11:06 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records In-Reply-To: References: Message-ID: <4044A7E5-39A3-46E0-BDF3-24A39F0B4460@yale.edu> Hi, To look at the logs requires someone with server access ? not sure if you are hosted by Lyrasis or hosted by your IT department but if you can recreate the error and note the time you could send them a screen shot and an approximate time (?this happened to me at 2:30 pm today?) and they can access the logs and look for errors in there. I?m not familiar with 2.7.0 so I don?t know what date requirements there are. Best, Maura From: on behalf of Gwenlyn Coddington Reply-To: Archivesspace Users Group Date: Monday, December 16, 2019 at 2:41 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Mark, Thanks for your help! We recently upgraded to v 2.7.0. I tried resaving the record as you suggested and unfortunately that did not clear it up. I also found this problem in the Sandbox Demo as I was trying to recreate what was happening in our system: entering the date in the expression field rather than a normalized begin and end date gave the same error response in the PUI but it cleared up when I switched to the begin and end fields. So I guess I know how to fix it but I want to know why its rejecting dates in the Expression field. Thanks again, Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, December 16, 2019 2:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Gwen, Which version of ArchivesSpace are you on? Here?s an example of an agent record in the PUI that uses both the Dates of Existence subrecord (for specific birth and death dates) aas the date field in the Names subrecord: https://archives.yale.edu/agents/people/81438 Also, have you tried to just re-save the agent record and see if that clears things up? Usually when you get the ?We?re sorry, but something went wrong message?, the issues generally has to do with the index. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gwenlyn Coddington Sent: Monday, 16 December, 2019 11:24 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Maura, Thank you so much for responding to my question. Unfortunately, I do not know how to examine the logs for errors. Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 10:57 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gcoddington at mcdaniel.edu Mon Dec 16 15:25:48 2019 From: gcoddington at mcdaniel.edu (Gwenlyn Coddington) Date: Mon, 16 Dec 2019 20:25:48 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records In-Reply-To: <4044A7E5-39A3-46E0-BDF3-24A39F0B4460@yale.edu> References: <4044A7E5-39A3-46E0-BDF3-24A39F0B4460@yale.edu> Message-ID: Hi Maura, Thank you so much for the suggestion. I will coordinate with our I.T. Department to see if we can?t figure out exactly what the error is. Thanks again, Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 3:11 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, To look at the logs requires someone with server access ? not sure if you are hosted by Lyrasis or hosted by your IT department but if you can recreate the error and note the time you could send them a screen shot and an approximate time (?this happened to me at 2:30 pm today?) and they can access the logs and look for errors in there. I?m not familiar with 2.7.0 so I don?t know what date requirements there are. Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 2:41 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Mark, Thanks for your help! We recently upgraded to v 2.7.0. I tried resaving the record as you suggested and unfortunately that did not clear it up. I also found this problem in the Sandbox Demo as I was trying to recreate what was happening in our system: entering the date in the expression field rather than a normalized begin and end date gave the same error response in the PUI but it cleared up when I switched to the begin and end fields. So I guess I know how to fix it but I want to know why its rejecting dates in the Expression field. Thanks again, Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Monday, December 16, 2019 2:31 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Gwen, Which version of ArchivesSpace are you on? Here?s an example of an agent record in the PUI that uses both the Dates of Existence subrecord (for specific birth and death dates) aas the date field in the Names subrecord: https://archives.yale.edu/agents/people/81438 Also, have you tried to just re-save the agent record and see if that clears things up? Usually when you get the ?We?re sorry, but something went wrong message?, the issues generally has to do with the index. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gwenlyn Coddington Sent: Monday, 16 December, 2019 11:24 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Maura, Thank you so much for responding to my question. Unfortunately, I do not know how to examine the logs for errors. Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 10:57 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Dec 16 16:37:01 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 16 Dec 2019 21:37:01 +0000 Subject: [Archivesspace_Users_Group] Question about Agent Records In-Reply-To: References: <4044A7E5-39A3-46E0-BDF3-24A39F0B4460@yale.edu> Message-ID: Gwen, You?ve definitely found a bug! In the meantime, if you?re only using the date expression field within a Dates of Existence subrecord, I don?t think that I?d recommend using that record type to store that date. I believe that the Dates of Existence records are primarily there to map to the ?special coded dates? in a MARC authority record (see https://www.loc.gov/marc/authority/ad046.html). What type of date are you recording in this part of the agent record? Regardless, the current behavior in the application is a bug that needs to be fixed!!! I took a closer look, and it appears that this is due to an issue with the metadata mappings in the HTML head section of the PUI. There are a couple of ways to fix this bug: * Change this line, https://github.com/archivesspace/archivesspace/blob/master/public/app/models/agent_person.rb#L14, to md[?birthDate?] = dates[?begin?] if dates[?begin?]. I think I like this approach the most since it?s explicit that there?s no birth date when one isn?t set. * That line never would?ve been a problem, though, until I changed this line, https://github.com/archivesspace/archivesspace/blob/master/public/app/models/agent_person.rb#L78, from just ?md? to being md.delete_if { |key,value| value.empty?}. The problem there arises when the metadata record comes in with a value of md[?birthDate?] = nil. So, maybe the safest way to fix this, and still keep the resulting metadata clean, would be to change line 78 to md.compact.delete_if { |key,value| value.empty? } . In that case, the previous section that calls the compact method wouldn?t be needed. Thanks for pointing out this issue! It?s something that will need to be patched for each of the agent records. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gwenlyn Coddington Sent: Monday, 16 December, 2019 3:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Maura, Thank you so much for the suggestion. I will coordinate with our I.T. Department to see if we can?t figure out exactly what the error is. Thanks again, Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 3:11 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, To look at the logs requires someone with server access ? not sure if you are hosted by Lyrasis or hosted by your IT department but if you can recreate the error and note the time you could send them a screen shot and an approximate time (?this happened to me at 2:30 pm today?) and they can access the logs and look for errors in there. I?m not familiar with 2.7.0 so I don?t know what date requirements there are. Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 2:41 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Mark, Thanks for your help! We recently upgraded to v 2.7.0. I tried resaving the record as you suggested and unfortunately that did not clear it up. I also found this problem in the Sandbox Demo as I was trying to recreate what was happening in our system: entering the date in the expression field rather than a normalized begin and end date gave the same error response in the PUI but it cleared up when I switched to the begin and end fields. So I guess I know how to fix it but I want to know why its rejecting dates in the Expression field. Thanks again, Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Monday, December 16, 2019 2:31 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Gwen, Which version of ArchivesSpace are you on? Here?s an example of an agent record in the PUI that uses both the Dates of Existence subrecord (for specific birth and death dates) aas the date field in the Names subrecord: https://archives.yale.edu/agents/people/81438 Also, have you tried to just re-save the agent record and see if that clears things up? Usually when you get the ?We?re sorry, but something went wrong message?, the issues generally has to do with the index. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gwenlyn Coddington Sent: Monday, 16 December, 2019 11:24 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi Maura, Thank you so much for responding to my question. Unfortunately, I do not know how to examine the logs for errors. Gwen Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Carbone, Maura Sent: Monday, December 16, 2019 10:57 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Question about Agent Records Hi, Are you able to look at the logs and see what error is being returned there? Best, Maura From: > on behalf of Gwenlyn Coddington > Reply-To: Archivesspace Users Group > Date: Monday, December 16, 2019 at 10:30 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Question about Agent Records Hello, I am new to ArchivesSpace and was hoping some of the more experienced users might be able to shed some light on a problem we are having with our Agent Records. Many of our Agent Records with date expressions are not displaying properly in the Public Interface. When you go to click on the individual record, it returns an error message (?We?re sorry, but something went wrong?). All these records appear to use the Dates of Existence Expression field rather than the normalized Begin and End fields. Agent Records without dates appear to be displaying correctly. Has anyone else come across this problem? Thanks for your time, Gwen Coddington Gwenlyn Coddington College Archivist & Special Collections Librarian McDaniel Hoover Library gcoddington at mcdaniel.edu (410) 857-2793 -------------- next part -------------- An HTML attachment was scrubbed... URL: From na207 at cam.ac.uk Tue Dec 17 04:47:47 2019 From: na207 at cam.ac.uk (Natalie Adams) Date: Tue, 17 Dec 2019 09:47:47 +0000 Subject: [Archivesspace_Users_Group] Using ArchivesSpace for collection management: need trigger dates in the future Message-ID: Dear all, We are relatively new to ArchivesSpace and are currently exploring using the collection management functions in AS with a view to producing local guidelines for archivists working in the Cambridge University Library and partner organisations. Our ideal is that AS becomes the one (and only) place for notes and documentation about collection management. One of the issues we are seeking to accommodate is using AS to prompt us about dates for future action. Here are a couple of scenarios of the type of thing we would like to do:- 1) Produce reports of future dates when archival material is due to be opened or reviewed 2) Produce reports of future dates to prompt action by the repository eg get back in touch with a depositor to remind them to return deed of a gift For scenario 1, we've been exploring adding dates to resource/resource component descriptions in the 'conditions governing access' note field and linking the resource/resource component to an Assessment record. Our tech team wrote us a report which could pull together any resource/resource with a date in the 'conditions governing access' field. This looks like it will work well. For scenario 2, we're a little stuck. We think it would be helpful to be able to include a future date to an assessment record, but I wondered whether any other AS users out there have come up with different solutions to this. I am sorry if I have missed anything obvious but would be very grateful for any help or advice. It would also be interesting to know whether other repositories would be interested in amending the assessment record in this way. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday to Thursday. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at msu.edu Mon Dec 16 16:40:59 2019 From: ltang5 at msu.edu (Tang, Lydia) Date: Mon, 16 Dec 2019 21:40:59 +0000 Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 Message-ID: Hello all! The Development Prioritization and Usability sub-teams have prepared a brief list of tickets that we are seeking community feedback on! Please feel free to comment on these tickets and/or discuss them on the list. These tickets may be complex and/or have a high impact on the program, so we definitely would appreciate your thoughts on these! * Geolocation: https://archivesspace.atlassian.net/browse/ANW-357 * Moving sidebar tree to the left: https://archivesspace.atlassian.net/browse/ANW-769 * Downloading PDF from any view of the collection: https://archivesspace.atlassian.net/browse/ANW-773 Thank you for your feedback and consideration! We?ll send a reminder after the new year, with the hope of finalizing feedback by the beginning of February. Lydia Tang and Maggie Hughes ~ on behalf of the Development Prioritization and Usability subteams -------------- next part -------------- An HTML attachment was scrubbed... URL: From na207 at cam.ac.uk Tue Dec 17 09:17:00 2019 From: na207 at cam.ac.uk (Natalie Adams) Date: Tue, 17 Dec 2019 14:17:00 +0000 Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 In-Reply-To: References: Message-ID: Dear Lydia, I don?t seem to be able to add a comment directly on the ticket, but I would like to comment on: * Downloading PDF from any view of the collection: https://archivesspace.atlassian.net/browse/ANW-773 We are implementing one instance of AS for the University Library and 29 partner organisations in Cambridge. Some of the resources will be huge, multi-level descriptions (eg the University archives ? see skeleton record here https://arcspace-pub.lib.cam.ac.uk/repositories/2/resources/7) and what would be really helpful to us would be the ability to download a pdf of sections of the resource (ie at levels below the resource). I understand that the PDF generator works using EAD and this is why it is only possible to generate a PDF of a complete finding aid but thought it would be worth adding a note about this. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday to Thursday. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: 16 December 2019 21:41 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 Hello all! The Development Prioritization and Usability sub-teams have prepared a brief list of tickets that we are seeking community feedback on! Please feel free to comment on these tickets and/or discuss them on the list. These tickets may be complex and/or have a high impact on the program, so we definitely would appreciate your thoughts on these! * Geolocation: https://archivesspace.atlassian.net/browse/ANW-357 * Moving sidebar tree to the left: https://archivesspace.atlassian.net/browse/ANW-769 * Downloading PDF from any view of the collection: https://archivesspace.atlassian.net/browse/ANW-773 Thank you for your feedback and consideration! We?ll send a reminder after the new year, with the hope of finalizing feedback by the beginning of February. Lydia Tang and Maggie Hughes ~ on behalf of the Development Prioritization and Usability subteams -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.donahue at lac-group.com Tue Dec 17 09:19:35 2019 From: rachel.donahue at lac-group.com (Rachel Donahue) Date: Tue, 17 Dec 2019 09:19:35 -0500 Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 In-Reply-To: References: Message-ID: I'm having trouble logging in to comment (or even viewing issues, what's up, Atlassian??), so I'll respond here. *769: *Yes, please! *773: *I agree with Ed Busch that both options (this and 950) should be offered. 950 is about using CSS to print the current webpage rather than the full finding aid PDF. I would, however, make it clear on the button/with a text link that that is what's going to happen. *357:* This sounds like a great feature to have, but also like it could involve a fair amount of work. For us, it definitely isn't a high priority. Best, Rachel On Tue, Dec 17, 2019 at 8:01 AM Tang, Lydia wrote: > Hello all! > > > > The Development Prioritization and Usability sub-teams have prepared a > brief list of tickets that we are seeking community feedback on! > > > > Please feel free to comment on these tickets and/or discuss them on the > list. These tickets may be complex and/or have a high impact on the > program, so we definitely would appreciate your thoughts on these! > > > > - Geolocation: https://archivesspace.atlassian.net/browse/ANW-357 > - Moving sidebar tree to the left: > https://archivesspace.atlassian.net/browse/ANW-769 > - Downloading PDF from any view of the collection: > > https://archivesspace.atlassian.net/browse/ANW-773 > > > Thank you for your feedback and consideration! We?ll send a reminder > after the new year, with the hope of finalizing feedback by the beginning > of February. > > Lydia Tang and Maggie Hughes > > ~ on behalf of the Development Prioritization and Usability subteams > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Dec 17 09:54:56 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 17 Dec 2019 14:54:56 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Integrating ArchivesSpace and Aviary Message-ID: <5F4D5AC8-3625-44B7-83FA-4B29EDC33D76@lyrasis.org> Webinar Announcement: Integrating ArchivesSpace and Aviary ArchivesSpace is pleased to announce the fourth webinar in our series focused on Integrations with ArchivesSpace. Each webinar in this series will highlight an integration with another application used in archives that ArchivesSpace members have worked on or requested. The webinar series will feature both open source and proprietary systems. Our fourth webinar in this series will feature an integration with the audiovisual publishing platform, Aviary. When: January 15, 2020 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT; 7 p.m. ? 8 p.m. GMT) Where: Zoom https://lyrasis.zoom.us/j/108009089 One tap mobile +19292056099,,108009089# US (New York) +16699006833,,108009089# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 108 009 089 Find your local number: https://zoom.us/u/awkFNWPxh Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. In this webinar, Bertram Lyons (Aviary) will provide an overview of Aviary, highlighting access controls, accessibility and compliance. He will also demonstrate how Aviary integrates with ArchivesSpace and how this integration benefits archivists, specifically archivists from smaller organizations. Kevin Glick (Yale University Libraries) will present on Yale?s integration of ArchivesSpace and Aviary. The presentation will highlight how Yale recognized the need for this integration within the libraries and both their vision and their experience implementing this integration. Kevin will also offer recommendations to other users considering integration. Presenters: Bertram Lyons specializes in the acquisition, management, and preservation of documentary, research, and cultural heritage collections. He has developed tools, policies, and partnerships around the development and management of analog and digital archival collections. For fifteen years, Bert has worked as an archivist for extensive archives, first at the Alan Lomax Archive and most recently at the American Folklife Center (AFC) at the Library of Congress. Bert is active with professional archival organizations including the International Association of Sound and Audiovisual Archives, the Society of American Archivists, the Association of Recorded Sound Collections, and the Association of Moving Image Archivists. He has also received certification from the Academy of Certified Archivists and is a graduate of the Archives Leadership Institute. He holds an MA in museum studies with a focus in American studies and archival theory from the University of Kansas. Kevin Glick is Head of Digitization and Digital Preservation and Archivist in Yale University Library?s Manuscripts & Archives, where he currently focuses on digitization, digital libraries, and other technology issues in special collections and archives. In addition, Kevin manages the architecture of the Fortunoff Video Archive for Holocaust Testimony's digital preservation and access systems as well as digitization of all materials related to the collection. Who should attend: Anyone interested in possibilities for integrating ArchivesSpace with Aviary, those who have integrated ArchivesSpace and Aviary and would like to offer insight to others, and those who are interested in working with fellow community members to make integrations with ArchivesSpace easier. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. The next Integrations with ArchivesSpace webinar will be: Integrating ArchivesSpace with Archivematica, February 19, 2020 at 2pm ET (11am PT) Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29060 bytes Desc: image001.jpg URL: From mcallahan at smith.edu Tue Dec 17 10:21:37 2019 From: mcallahan at smith.edu (Maureen Callahan) Date: Tue, 17 Dec 2019 10:21:37 -0500 Subject: [Archivesspace_Users_Group] Using ArchivesSpace for collection management: need trigger dates in the future In-Reply-To: References: Message-ID: Dear Natalie, It's great to see repositories using ArchivesSpace to kick off automated actions! I was lucky enough to have worked on the team that had put together the specification for your scenario 1, and that was exactly the outcome we had in mind. (A video about that is here, although the version is very behind: https://www.youtube.com/watch?v=biCDhkbBSng ) For your scenario 2, I've been fantasizing about future ArchivesSpace functionality that would govern legal agreements -- a "legal agreement" record type that could track who signed onto the agreement, when, and what was agreed upon, and this information could be then linked to all of the materials that this agreement governs. This is to say that I don't think that this is the kind of thing that ASpace is currently designed to do and I tend to be nervous about bending enterprise systems to make them do hacks for us. But I would be very eager to talk more with you and others to come up with a specification for these kinds of collections management / collection development activities! Best wishes, Maureen On Tue, Dec 17, 2019 at 4:47 AM Natalie Adams wrote: > Dear all, > > > > We are relatively new to ArchivesSpace and are currently exploring using > the collection management functions in AS with a view to producing local > guidelines for archivists working in the Cambridge University Library and > partner organisations. Our ideal is that AS becomes the one (and only) > place for notes and documentation about collection management. > > > > One of the issues we are seeking to accommodate is using AS to prompt us > about dates for future action. Here are a couple of scenarios of the type > of thing we would like to do:- > > 1) Produce reports of future dates when archival material is due to > be opened or reviewed > > 2) Produce reports of future dates to prompt action by the > repository eg get back in touch with a depositor to remind them to return > deed of a gift > > > > For scenario 1, we?ve been exploring adding dates to resource/resource > component descriptions in the ?conditions governing access? note field and > linking the resource/resource component to an Assessment record. Our tech > team wrote us a report which could pull together any resource/resource with > a date in the ?conditions governing access? field. This looks like it will > work well. > > > > For scenario 2, we?re a little stuck. We think it would be helpful to be > able to include a future date to an assessment record, but I wondered > whether any other AS users out there have come up with different solutions > to this. I am sorry if I have missed anything obvious but would be very > grateful for any help or advice. It would also be interesting to know > whether other repositories would be interested in amending the assessment > record in this way. > > > > Best wishes, > > > > Natalie > > > > *Natalie Adams* > > Systems Archivist > > Cambridge University Library > > West Road > > Cambridge > > Cambridge, CB3 9DR > > Tel 01223 766377 > > www.lib.cam.ac.uk/ > > *Normal working days are Monday to Thursday.* > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 413 585 2981 mcallahan at smith.edu Pronouns: she/her/hers Smith College Special Collections is now housed at Young Library . Learn more about renovations to Neilson Library here . Visit us in our reading room in Young Library 202. Classes are taught in Young Library 201. More information about our current collecting goals is available in our collection development strategy . -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.searcy at nyu.edu Tue Dec 17 12:21:24 2019 From: rachel.searcy at nyu.edu (Rachel Aileen Searcy) Date: Tue, 17 Dec 2019 12:21:24 -0500 Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input In-Reply-To: References: Message-ID: Hi Robin, We wanted to provide some comments to this proposal for enhancements to ArchivesSpace?s container management functionality. We?d like to thank Harvard for their efforts to put this together to make ArchivesSpace a more useful system for the broader community. We are also a large, multi-repository institution with a single ArchivesSpace instance, and have encountered many of the challenges outlined in this document, although we do operate slightly differently (for example, our locations are shared across our repositories to make the best use of the space we have). We too have found it difficult to browse, filter, and sort through our large number of location records, especially when linking top containers to locations, and support the improvements specified in this document to more efficiently perform these tasks. We would appreciate the ability to return to an existing top container search, but would not want to sacrifice overall system performance for this feature. While the ability to merge locations would be useful in cleaning up obsolete or duplicate locations, we wonder if the logic required to create this functionality might be more complicated than other merging in the system, as there are currently measures in place to ensure that locations cannot be deleted while holdings are linked to them. We think this logic should remain in place to prevent deleting important data. We might not use many of the proposed enhancements (e.g., barcodes for container children, repositories for container profiles) but as long as they are optional and unobtrusive to users who do not employ them, we do not have strong feelings. We do have concerns about the proposal to add a Note field to the Top Container record, especially without a compelling use case to justify its inclusion, as there is such a high likelihood of this field being misused to record information about the contents of a box (as opposed to the container itself) more appropriate for specific EAD fields. It reminds us of boxes that have labels with crucial information about the materials inside that is not documented anywhere else, and we wouldn?t want to encourage that type of practice. If there are compelling use cases for this field, we?d prefer values to be controlled so that they can be structured, queried, and used somewhat consistently. Again, thank you for developing this proposal and continuing the conversation. We?re eager to see how this work continues. Best wishes, Rachel On Tue, Dec 10, 2019 at 1:19 PM Wendler, Robin King < robin_wendler at harvard.edu> wrote: > Dear ArchivesSpace Community, > > The Harvard Library has been reviewing container and location management > functionality in ArchivesSpace and we are proposing to make enhancements to > this functionality that we would like to contribute to the core code. With > these enhancements, we hope to make finding, viewing, and updating > information related to containers and locations in the staff interface more > efficient and effective. > > > > Some of you may remember a proposal we distributed this time last year. A > variety of factors delayed the work, so we have significantly revised the > proposal based on the valuable feedback provided by the ArchivesSpace > community and informed by Harvard archivists? increasing experience with > container management in ArchivesSpace. Some proposals have been removed, > while others have been added or altered. > > > > Additions include > > - Return to Top Container search results from viewing an individual > Top Container record > - Bulk or batch function to create new Top Containers, associate > existing Locations with them, and link them to multiple existing archival > objects. > - Bulk operation to delete barcodes from Top Containers > - File-upload function to add Locations to Top Containers > - Ability to merge Location records > > > > The most significant changes to previous proposals include the following: > > - The proposed additional indicator fields and ILS Bibliographic > Record ID field in Top Containers have been removed. > - The proposed Note field and Inactive checkbox for Locations, along > with all functionality associated with inactive status, have been removed. > - Automatic scoping of Container Profiles, Locations, and Location > Profiles by repository appears to be too complex, given the community > request to make repositories repeatable and the desire for it to be an > installation configuration option. In lieu of that, the revised proposal > adds a repeatable, optional repository field to container profiles and adds > a facet for filtering by repository to browse results for Container > Profiles and Locations. > - Proposed functionality around Location status has been removed > > > > The revised draft proposal is attached to this email and we are asking for > community review and feedback. The proposal includes the rationale for the > changes, a list of database fields to be added, user stories describing the > specific changes we are proposing, and mockups of the related updates to > the staff interface. Please note that the proposal represents a superset of > the work we may be able to complete in the next couple of months, and that > not all the proposed changes will be addressed at this time. Another > caveat: some of the desiderata require further technical design that will > determine what approach will be taken. These will be investigated in > consultation with Lyrasis ArchivesSpace staff. > > > > If you have questions or feedback, please email me at > robin_wendler at harvard.edu. *We will be accepting comments through > Wednesday, December 18, 2019.* > > > > We look forward to receiving community input. > > > > Best, > > Robin > > > > Robin Wendler > > Library Technology Services > > Harvard University > > 90 Mt. Auburn St. > > Cambridge, MA 02138 > > 617-998-5457 > > 617-495-3724 > > r_wendler at harvard.edu > > > > > > Robin Wendler > > Library Technology Services > > Harvard University > > 90 Mt. Auburn St. > > Cambridge, MA 02138 > > 617-998-5457 > > 617-495-3724 > > r_wendler at harvard.edu > > > _______________________________________________ > 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=xCPRgg7M_MSTK8m534QQeiXyHPD8UZ765hwtNHj9an0&s=Tqu4WUEA3bqTFcWqfAJWzW-Hd4lnvqlAZ8MT2TWeta4&e= > -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her -------------- next part -------------- An HTML attachment was scrubbed... URL: From ldfs at umn.edu Tue Dec 17 16:20:00 2019 From: ldfs at umn.edu (Lara Friedman-Shedlov) Date: Tue, 17 Dec 2019 15:20:00 -0600 Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 In-Reply-To: References: Message-ID: Re: 769: If this is going to happen, I hope at the same time the issue with scrolling of the main window (currently to the left of the navigation tree) when in "Finding Aid View" in Firefox, which I reported about two years ago and is still not fixed, can be resolved. Right now the scroll bar does not work. The only option is to scroll with a mouse or other pointing device, which is extremely slow. In addition, it is very hard to resize the navigation tree in Firefox. Clicking and dragging the left side of the window to make it bigger doesn't work correctly. / Lara Friedman-Shedlov _________________________________ Lara D. Friedman-Shedlov (She/Her/Hers) Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [image: www.facebook.com/IHRCA] [image: https://twitter.com/yarchives] > On Tue, Dec 17, 2019 at 8:01 AM Tang, Lydia wrote: > >> Hello all! >> >> >> >> The Development Prioritization and Usability sub-teams have prepared a >> brief list of tickets that we are seeking community feedback on! >> >> >> >> Please feel free to comment on these tickets and/or discuss them on the >> list. These tickets may be complex and/or have a high impact on the >> program, so we definitely would appreciate your thoughts on these! >> >> >> >> - Geolocation: https://archivesspace.atlassian.net/browse/ANW-357 >> - Moving sidebar tree to the left: >> https://archivesspace.atlassian.net/browse/ANW-769 >> - Downloading PDF from any view of the collection: >> >> https://archivesspace.atlassian.net/browse/ANW-773 >> >> >> Thank you for your feedback and consideration! We?ll send a reminder >> after the new year, with the hope of finalizing feedback by the beginning >> of February. >> >> Lydia Tang and Maggie Hughes >> >> ~ on behalf of the Development Prioritization and Usability subteams >> >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From amanifold at slv.vic.gov.au Tue Dec 17 16:53:11 2019 From: amanifold at slv.vic.gov.au (Alan Manifold) Date: Tue, 17 Dec 2019 21:53:11 +0000 Subject: [Archivesspace_Users_Group] Working with Ruby Message-ID: Hi all, I am new to Ruby, and have been adding some functionality to our PUI through a local plugin. I?m finding the testing a bit slow. Whenever I make a change to the code or configuration files, I have to restart the application before I see them in effect. This generally takes 4-5 minutes on our server. That?s not terrible, but I wondered if there?s a way to speed up the process. Is there any way to avoid restarting the application each time I make a change, such as just recompiling a single file or something like that? It would save me a lot of time in my testing. Thanks for any tips you can share. Regards, Alan Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 T +61 3 8664 7122 | amanifold at slv.vic.gov.au slv.vic.gov.au [https://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?9] [follow us] [SLV facebook] [SLV twitter] [SLV youtube] [SLV instagram] [Gold Winner 2018 RACV Victorian Tourism Awards] [MEA Awards 2018 National Winner] This message and any attachment is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please delete all copies of the message and its attachments and notify the sender immediately. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at msu.edu Tue Dec 17 16:56:30 2019 From: ltang5 at msu.edu (Tang, Lydia) Date: Tue, 17 Dec 2019 21:56:30 +0000 Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 In-Reply-To: References: Message-ID: <6E12D120-5C2D-4DC8-ADB3-DF2FB68D9487@msu.edu> Hi Natalie, Rachel, and Lara, Thanks for your feedback! I?ve copied your responses into Jira, so they can be reviewed there. Sorry you?ve been having issues with Jira. It sounds like perhaps we should create a tutorial or documentation to help people orient with the program. To comment on a ticket, you?d need to create an account and log into the system. I?m attaching a slide from a presentation Maggie and I did this summer. It?s a really teeny tiny ?door? in the bottom left corner of the screen. Thanks for your responses, all! Lydia From: on behalf of Natalie Adams Reply-To: Archivesspace Users Group Date: Tuesday, December 17, 2019 at 9:17 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 Dear Lydia, I don?t seem to be able to add a comment directly on the ticket, but I would like to comment on: * Downloading PDF from any view of the collection: https://archivesspace.atlassian.net/browse/ANW-773 We are implementing one instance of AS for the University Library and 29 partner organisations in Cambridge. Some of the resources will be huge, multi-level descriptions (eg the University archives ? see skeleton record here https://arcspace-pub.lib.cam.ac.uk/repositories/2/resources/7) and what would be really helpful to us would be the ability to download a pdf of sections of the resource (ie at levels below the resource). I understand that the PDF generator works using EAD and this is why it is only possible to generate a PDF of a complete finding aid but thought it would be worth adding a note about this. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday to Thursday. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: 16 December 2019 21:41 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 Hello all! The Development Prioritization and Usability sub-teams have prepared a brief list of tickets that we are seeking community feedback on! Please feel free to comment on these tickets and/or discuss them on the list. These tickets may be complex and/or have a high impact on the program, so we definitely would appreciate your thoughts on these! * Geolocation: https://archivesspace.atlassian.net/browse/ANW-357 * Moving sidebar tree to the left: https://archivesspace.atlassian.net/browse/ANW-769 * Downloading PDF from any view of the collection: https://archivesspace.atlassian.net/browse/ANW-773 Thank you for your feedback and consideration! We?ll send a reminder after the new year, with the hope of finalizing feedback by the beginning of February. Lydia Tang and Maggie Hughes ~ on behalf of the Development Prioritization and Usability subteams -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: log in.png Type: image/png Size: 404617 bytes Desc: log in.png URL: From na207 at cam.ac.uk Wed Dec 18 05:01:40 2019 From: na207 at cam.ac.uk (Natalie Adams) Date: Wed, 18 Dec 2019 10:01:40 +0000 Subject: [Archivesspace_Users_Group] Using ArchivesSpace for collection management: need trigger dates in the future In-Reply-To: References: Message-ID: Dear Maureen, Thanks so much for your response and the link the video- it is very helpful to see how you have used AS and also to have confirmation that there is no easy solution to our scenario 2. All the best, Natalie From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Maureen Callahan Sent: 17 December 2019 15:22 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Using ArchivesSpace for collection management: need trigger dates in the future Dear Natalie, It's great to see repositories using ArchivesSpace to kick off automated actions! I was lucky enough to have worked on the team that had put together the specification for your scenario 1, and that was exactly the outcome we had in mind. (A video about that is here, although the version is very behind: https://www.youtube.com/watch?v=biCDhkbBSng ) For your scenario 2, I've been fantasizing about future ArchivesSpace functionality that would govern legal agreements -- a "legal agreement" record type that could track who signed onto the agreement, when, and what was agreed upon, and this information could be then linked to all of the materials that this agreement governs. This is to say that I don't think that this is the kind of thing that ASpace is currently designed to do and I tend to be nervous about bending enterprise systems to make them do hacks for us. But I would be very eager to talk more with you and others to come up with a specification for these kinds of collections management / collection development activities! Best wishes, Maureen On Tue, Dec 17, 2019 at 4:47 AM Natalie Adams > wrote: Dear all, We are relatively new to ArchivesSpace and are currently exploring using the collection management functions in AS with a view to producing local guidelines for archivists working in the Cambridge University Library and partner organisations. Our ideal is that AS becomes the one (and only) place for notes and documentation about collection management. One of the issues we are seeking to accommodate is using AS to prompt us about dates for future action. Here are a couple of scenarios of the type of thing we would like to do:- 1) Produce reports of future dates when archival material is due to be opened or reviewed 2) Produce reports of future dates to prompt action by the repository eg get back in touch with a depositor to remind them to return deed of a gift For scenario 1, we?ve been exploring adding dates to resource/resource component descriptions in the ?conditions governing access? note field and linking the resource/resource component to an Assessment record. Our tech team wrote us a report which could pull together any resource/resource with a date in the ?conditions governing access? field. This looks like it will work well. For scenario 2, we?re a little stuck. We think it would be helpful to be able to include a future date to an assessment record, but I wondered whether any other AS users out there have come up with different solutions to this. I am sorry if I have missed anything obvious but would be very grateful for any help or advice. It would also be interesting to know whether other repositories would be interested in amending the assessment record in this way. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday to Thursday. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 413 585 2981 mcallahan at smith.edu Pronouns: she/her/hers Smith College Special Collections is now housed at Young Library. Learn more about renovations to Neilson Library here. Visit us in our reading room in Young Library 202. Classes are taught in Young Library 201. More information about our current collecting goals is available in our collection development strategy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.donahue at lac-group.com Wed Dec 18 09:09:21 2019 From: rachel.donahue at lac-group.com (Rachel Donahue) Date: Wed, 18 Dec 2019 09:09:21 -0500 Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1 In-Reply-To: <6E12D120-5C2D-4DC8-ADB3-DF2FB68D9487@msu.edu> References: <6E12D120-5C2D-4DC8-ADB3-DF2FB68D9487@msu.edu> Message-ID: Hi Lydia, I think Atlassian is just feeling buggy this week. Viewing issues, search, etc were all occasionally giving me something went wrong pages. When I tried to login, it would either give me that page or bring me back to the ArchivesSpace workspace without actually logging me in (or giving me an error about wrong password or no account). I've used Jira before and never experienced something like this! --Rachel -- The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. On Tue, Dec 17, 2019 at 4:56 PM Tang, Lydia wrote: > Hi Natalie, Rachel, and Lara, > > Thanks for your feedback! I?ve copied your responses into Jira, so they > can be reviewed there. Sorry you?ve been having issues with Jira. It > sounds like perhaps we should create a tutorial or documentation to help > people orient with the program. To comment on a ticket, you?d need to > create an account and log into the system. I?m attaching a slide from a > presentation Maggie and I did this summer. It?s a really teeny tiny ?door? > in the bottom left corner of the screen. > > Thanks for your responses, all! > > Lydia > > *From: * on > behalf of Natalie Adams > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Tuesday, December 17, 2019 at 9:17 AM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Seeking feedback on tickets by > Feb. 1 > > > > Dear Lydia, > > > > I don?t seem to be able to add a comment directly on the ticket, but I > would like to comment on: > > > > - Downloading PDF from any view of the collection: > > https://archivesspace.atlassian.net/browse/ANW-773 > > > > We are implementing one instance of AS for the University Library and 29 > partner organisations in Cambridge. Some of the resources will be huge, > multi-level descriptions (eg the University archives ? see skeleton record > here https://arcspace-pub.lib.cam.ac.uk/repositories/2/resources/7 > ) > and what would be really helpful to us would be the ability to download a > pdf of sections of the resource (ie at levels below the resource). I > understand that the PDF generator works using EAD and this is why it is > only possible to generate a PDF of a complete finding aid but thought it > would be worth adding a note about this. > > Best wishes, > > > > Natalie > > > > > > *Natalie Adams* > > Systems Archivist > > Cambridge University Library > > West Road > > Cambridge > > Cambridge, CB3 9DR > > Tel 01223 766377 > > www.lib.cam.ac.uk/ > > > *Normal working days are Monday to Thursday.* > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Tang, > Lydia > *Sent:* 16 December 2019 21:41 > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Seeking feedback on tickets by > Feb. 1 > > > > Hello all! > > > > The Development Prioritization and Usability sub-teams have prepared a > brief list of tickets that we are seeking community feedback on! > > > > Please feel free to comment on these tickets and/or discuss them on the > list. These tickets may be complex and/or have a high impact on the > program, so we definitely would appreciate your thoughts on these! > > > > - Geolocation: https://archivesspace.atlassian.net/browse/ANW-357 > > - Moving sidebar tree to the left: > https://archivesspace.atlassian.net/browse/ANW-769 > > - Downloading PDF from any view of the collection: > > https://archivesspace.atlassian.net/browse/ANW-773 > > > > Thank you for your feedback and consideration! We?ll send a reminder > after the new year, with the hope of finalizing feedback by the beginning > of February. > > Lydia Tang and Maggie Hughes > > ~ on behalf of the Development Prioritization and Usability subteams > > > > > _______________________________________________ > 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 christine.dibella at lyrasis.org Wed Dec 18 11:59:59 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 18 Dec 2019 16:59:59 +0000 Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input In-Reply-To: References: Message-ID: Hi Robin, Thanks so much to you and your colleagues at Harvard for distributing this specification for community comment. We really appreciate your interest in making this development work as relevant to the overall community as possible and contributing the results for consideration for the core code. To that end, I wanted to make a few comments based on past experience or current development that you or others may find helpful. On changing the columns that appear for browses or searches of Location records - we often have requests for columnar displays of browse or search results to be configurable, including in the Staff Interface Enhancement Working Group's recommendations. Our developers are currently working on more configuration options for Accession, Resource, and Digital Objects browse displays and the search results display in the staff interface, located in the preferences area of the application and summarized in this JIRA: https://archivesspace.atlassian.net/browse/ANW-929. A test server with this work is at http://wiprefds.lyrtech.org/staff/ (standard admin/admin login). We expect the final version of this work to be in the next release of ArchivesSpace. I'd encourage adding Locations to the type of record that can be configured in this area. With the established pattern I think this may be fairly easy to do. I have a similar comment about the proposed changes to the linked records displays, though I've heard this mentioned much less frequently. Given that different fields may be of interest to different people, I think it's likely to be desirable in many situations. I don't think this would fit the other pattern, though. It may be one of those things where if it's relatively simple to do, it would be worth it in extending the relevance across many different users/institutions. Lastly, you are able to delete barcodes in bulk at this time. When using the Rapid Barcode Entry feature in Manage Top Containers, leaving a barcode field blank removes the barcode without replacing it with a new barcode. This was actually always the case, but we fixed a bug with the indexing in this area (https://archivesspace.atlassian.net/browse/ANW-973) recently that didn't make it clear this was happening. This will be in the next release of ArchivesSpace. Those were the things that stood out to me. I look forward to talking more as your development work progresses. Thank you for getting the community involved proactively! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Wendler, Robin King Sent: Tuesday, December 10, 2019 1:19 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. Some of you may remember a proposal we distributed this time last year. A variety of factors delayed the work, so we have significantly revised the proposal based on the valuable feedback provided by the ArchivesSpace community and informed by Harvard archivists' increasing experience with container management in ArchivesSpace. Some proposals have been removed, while others have been added or altered. Additions include * Return to Top Container search results from viewing an individual Top Container record * Bulk or batch function to create new Top Containers, associate existing Locations with them, and link them to multiple existing archival objects. * Bulk operation to delete barcodes from Top Containers * File-upload function to add Locations to Top Containers * Ability to merge Location records The most significant changes to previous proposals include the following: * The proposed additional indicator fields and ILS Bibliographic Record ID field in Top Containers have been removed. * The proposed Note field and Inactive checkbox for Locations, along with all functionality associated with inactive status, have been removed. * Automatic scoping of Container Profiles, Locations, and Location Profiles by repository appears to be too complex, given the community request to make repositories repeatable and the desire for it to be an installation configuration option. In lieu of that, the revised proposal adds a repeatable, optional repository field to container profiles and adds a facet for filtering by repository to browse results for Container Profiles and Locations. * Proposed functionality around Location status has been removed The revised draft proposal is attached to this email and we are asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that the proposal represents a superset of the work we may be able to complete in the next couple of months, and that not all the proposed changes will be addressed at this time. Another caveat: some of the desiderata require further technical design that will determine what approach will be taken. These will be investigated in consultation with Lyrasis ArchivesSpace staff. If you have questions or feedback, please email me at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 18, 2019. We look forward to receiving community input. Best, Robin Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From robin_wendler at harvard.edu Wed Dec 18 12:16:59 2019 From: robin_wendler at harvard.edu (Wendler, Robin King) Date: Wed, 18 Dec 2019 17:16:59 +0000 Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input In-Reply-To: References: Message-ID: Hi, Rachel, Thank you very much for your feedback. I?ve added your comments to the tickets for these issues and we?ll be sure to account for them. One person expressed concern adding a Notes field to Top Container records when the proposal went out last year. The Notes field is a candidate for adding as a plug-in, so we?ll take a look at that. I?m curious whether there were others of these proposals that would particularly help you, or if there are minor changes to any that would make them more valuable. I?d welcome any further thoughts. Thanks again, Robin From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Rachel Aileen Searcy Sent: Tuesday, December 17, 2019 12:21 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input Hi Robin, We wanted to provide some comments to this proposal for enhancements to ArchivesSpace?s container management functionality. We?d like to thank Harvard for their efforts to put this together to make ArchivesSpace a more useful system for the broader community. We are also a large, multi-repository institution with a single ArchivesSpace instance, and have encountered many of the challenges outlined in this document, although we do operate slightly differently (for example, our locations are shared across our repositories to make the best use of the space we have). We too have found it difficult to browse, filter, and sort through our large number of location records, especially when linking top containers to locations, and support the improvements specified in this document to more efficiently perform these tasks. We would appreciate the ability to return to an existing top container search, but would not want to sacrifice overall system performance for this feature. While the ability to merge locations would be useful in cleaning up obsolete or duplicate locations, we wonder if the logic required to create this functionality might be more complicated than other merging in the system, as there are currently measures in place to ensure that locations cannot be deleted while holdings are linked to them. We think this logic should remain in place to prevent deleting important data. We might not use many of the proposed enhancements (e.g., barcodes for container children, repositories for container profiles) but as long as they are optional and unobtrusive to users who do not employ them, we do not have strong feelings. We do have concerns about the proposal to add a Note field to the Top Container record, especially without a compelling use case to justify its inclusion, as there is such a high likelihood of this field being misused to record information about the contents of a box (as opposed to the container itself) more appropriate for specific EAD fields. It reminds us of boxes that have labels with crucial information about the materials inside that is not documented anywhere else, and we wouldn?t want to encourage that type of practice. If there are compelling use cases for this field, we?d prefer values to be controlled so that they can be structured, queried, and used somewhat consistently. Again, thank you for developing this proposal and continuing the conversation. We?re eager to see how this work continues. Best wishes, Rachel On Tue, Dec 10, 2019 at 1:19 PM Wendler, Robin King > wrote: Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. Some of you may remember a proposal we distributed this time last year. A variety of factors delayed the work, so we have significantly revised the proposal based on the valuable feedback provided by the ArchivesSpace community and informed by Harvard archivists? increasing experience with container management in ArchivesSpace. Some proposals have been removed, while others have been added or altered. Additions include * Return to Top Container search results from viewing an individual Top Container record * Bulk or batch function to create new Top Containers, associate existing Locations with them, and link them to multiple existing archival objects. * Bulk operation to delete barcodes from Top Containers * File-upload function to add Locations to Top Containers * Ability to merge Location records The most significant changes to previous proposals include the following: * The proposed additional indicator fields and ILS Bibliographic Record ID field in Top Containers have been removed. * The proposed Note field and Inactive checkbox for Locations, along with all functionality associated with inactive status, have been removed. * Automatic scoping of Container Profiles, Locations, and Location Profiles by repository appears to be too complex, given the community request to make repositories repeatable and the desire for it to be an installation configuration option. In lieu of that, the revised proposal adds a repeatable, optional repository field to container profiles and adds a facet for filtering by repository to browse results for Container Profiles and Locations. * Proposed functionality around Location status has been removed The revised draft proposal is attached to this email and we are asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that the proposal represents a superset of the work we may be able to complete in the next couple of months, and that not all the proposed changes will be addressed at this time. Another caveat: some of the desiderata require further technical design that will determine what approach will be taken. These will be investigated in consultation with Lyrasis ArchivesSpace staff. If you have questions or feedback, please email me at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 18, 2019. We look forward to receiving community input. Best, Robin Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu _______________________________________________ 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=xCPRgg7M_MSTK8m534QQeiXyHPD8UZ765hwtNHj9an0&s=Tqu4WUEA3bqTFcWqfAJWzW-Hd4lnvqlAZ8MT2TWeta4&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Wed Dec 18 15:25:11 2019 From: james at hudmol.com (James Bullen) Date: Wed, 18 Dec 2019 15:25:11 -0500 Subject: [Archivesspace_Users_Group] Working with Ruby In-Reply-To: References: Message-ID: Hi Alan, If you run in development mode you don?t need to restart for most changes - they will hot reload. To do this, download the source and then from the archivesspace directory run the components separately like this: build/run backend:devserver build/run indexer build/run frontend:devserver build/run public:devserver You?ll need to put your config.rb in common/config/, and the mysql connector in common/lib/, and your plugins in plugins/. Hope that helps. Cheers, James > On Dec 17, 2019, at 4:53 PM, Alan Manifold wrote: > > Hi all, > I am new to Ruby, and have been adding some functionality to our PUI through a local plugin. I?m finding the testing a bit slow. > > Whenever I make a change to the code or configuration files, I have to restart the application before I see them in effect. This generally takes 4-5 minutes on our server. That?s not terrible, but I wondered if there?s a way to speed up the process. Is there any way to avoid restarting the application each time I make a change, such as just recompiling a single file or something like that? It would save me a lot of time in my testing. > > Thanks for any tips you can share. > > Regards, > Alan > > Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description > State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 > T +61 3 8664 7122 | amanifold at slv.vic.gov.au > slv.vic.gov.au > > > > > This message and any attachment is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please delete all copies of the message and its attachments and notify the sender immediately. Thank you. !DSPAM:5df95437243835172830492! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:5df95437243835172830492! -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahueb2 at uis.edu Fri Dec 20 09:43:58 2019 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Fri, 20 Dec 2019 14:43:58 +0000 Subject: [Archivesspace_Users_Group] ASpace database constraints Message-ID: <1576853038790.74554@uis.edu> Good morning all, I've been working with some test instances of our database and I need to remove some records in bulk. We are currently running ASpace against a MySQL instance and I am attempting to remove all traces of specific records from the tables. Easily enough I can delete the records from the resource table after disabling foreign key checks, however it appears that there is information left over in other tables making Solr an unhappy camper. I created an EER diagram in MySQL Workbench to try and figure out which records are tied together, but as someone who is fairly new to database work it's a bit of a headache to wrap my mind around. >From the research I've done, some records can be set as a parent and with a cascade setting the child records in other tables will be removed when the parent is removed. I've looked at some of the table settings but I haven't been able to figure out what needs to be removed to clean up the db or what the proper order of removal would be. Has anyone here removed resource table entries and their associated records with success? How can I go about figuring out what I need to remove and/or how to remove it? -Alan Huebschen University of Illinois at Springfield Brookens Library Information Systems -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Fri Dec 20 10:02:53 2019 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Fri, 20 Dec 2019 15:02:53 +0000 Subject: [Archivesspace_Users_Group] ASpace database constraints Message-ID: <6F9641DB-EBDD-4DD9-96BA-B8A9EE7C839D@harvard.edu> Hi Alan, So, it?s _possible_ to do a cascade delete of records in ASpace, but for a couple of reasons, I think it?s not necessarily a real good idea. Solr is unhappy not just because there?s leftover info in other tables, but also probably because it can?t inherently see the bulk deletions in MySQL. I think it?d probably be safer to delete things via the ArchivesSpace API; this way Solr will stay consistent throughout, and subsidiary records that depend on Resource _should_ all get deleted as well (I?m not quite comfortable saying ?will,? but if not, you can also clean those up via the API. There?s an actively maintained API client for ArchivesSpace, ArchivesSnake - https://github.com/archivesspace-labs/archivessnake; and a lot of example scripts are linked in the documentation. I think in principle, this would be fairly straightforward; you?d need to collect the ids of the resources you want to delete, and then delete them. So, just as a simplified example, if you wanted to delete all resources in repository 2: from asnake.client import ASnakeClient client = ASnakeClient(username=?admin?, password=?admin?, baseurl=?http://path.to.backend?) repos_response = client.get(?repositories/2/resources?, params={?all_ids?: True}) if (repos_response.status_code != 200): raise ?Something went wrong!? for res_id in repos_response.json(): delete_response = client.delete(?repositories/2/resources/{}?.format(res_id)) if (delete_response.status_code != 200): print(?Failed to delete {}?.format(res_id)) If you decide to try this and run into trouble, please feel free to email me, I?d be happy to help walk you through setup/troubleshooting. -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: on behalf of "Huebschen, Alan M" Reply-To: Archivesspace Users Group Date: Friday, December 20, 2019 at 9:44 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ASpace database constraints Good morning all, I've been working with some test instances of our database and I need to remove some records in bulk. We are currently running ASpace against a MySQL instance and I am attempting to remove all traces of specific records from the tables. Easily enough I can delete the records from the resource table after disabling foreign key checks, however it appears that there is information left over in other tables making Solr an unhappy camper. I created an EER diagram in MySQL Workbench to try and figure out which records are tied together, but as someone who is fairly new to database work it's a bit of a headache to wrap my mind around. From the research I've done, some records can be set as a parent and with a cascade setting the child records in other tables will be removed when the parent is removed. I've looked at some of the table settings but I haven't been able to figure out what needs to be removed to clean up the db or what the proper order of removal would be. Has anyone here removed resource table entries and their associated records with success? How can I go about figuring out what I need to remove and/or how to remove it? -Alan Huebschen University of Illinois at Springfield Brookens Library Information Systems -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin_wendler at harvard.edu Fri Dec 20 11:58:49 2019 From: robin_wendler at harvard.edu (Wendler, Robin King) Date: Fri, 20 Dec 2019 16:58:49 +0000 Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input In-Reply-To: References: Message-ID: Hi, Christine, Thank you very much for this information. As I told folks here, this is what happens while we plan: things move on without us! We're thrilled that we can drop the delete barcodes story. Dave is also thrilled about ANW-929. He'll be in touch with Laney to see how that can be leveraged and whether a similar model can be adopted for changes to linked record displays. Happy holidays to you and your team! Robin From: Christine Di Bella Sent: Wednesday, December 18, 2019 12:00 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Wendler, Robin King Subject: RE: Revised Proposal for Container Management Enhancements - Call for Community Input Hi Robin, Thanks so much to you and your colleagues at Harvard for distributing this specification for community comment. We really appreciate your interest in making this development work as relevant to the overall community as possible and contributing the results for consideration for the core code. To that end, I wanted to make a few comments based on past experience or current development that you or others may find helpful. On changing the columns that appear for browses or searches of Location records - we often have requests for columnar displays of browse or search results to be configurable, including in the Staff Interface Enhancement Working Group's recommendations. Our developers are currently working on more configuration options for Accession, Resource, and Digital Objects browse displays and the search results display in the staff interface, located in the preferences area of the application and summarized in this JIRA: https://archivesspace.atlassian.net/browse/ANW-929. A test server with this work is at http://wiprefds.lyrtech.org/staff/ (standard admin/admin login). We expect the final version of this work to be in the next release of ArchivesSpace. I'd encourage adding Locations to the type of record that can be configured in this area. With the established pattern I think this may be fairly easy to do. I have a similar comment about the proposed changes to the linked records displays, though I've heard this mentioned much less frequently. Given that different fields may be of interest to different people, I think it's likely to be desirable in many situations. I don't think this would fit the other pattern, though. It may be one of those things where if it's relatively simple to do, it would be worth it in extending the relevance across many different users/institutions. Lastly, you are able to delete barcodes in bulk at this time. When using the Rapid Barcode Entry feature in Manage Top Containers, leaving a barcode field blank removes the barcode without replacing it with a new barcode. This was actually always the case, but we fixed a bug with the indexing in this area (https://archivesspace.atlassian.net/browse/ANW-973) recently that didn't make it clear this was happening. This will be in the next release of ArchivesSpace. Those were the things that stood out to me. I look forward to talking more as your development work progresses. Thank you for getting the community involved proactively! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Wendler, Robin King Sent: Tuesday, December 10, 2019 1:19 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. Some of you may remember a proposal we distributed this time last year. A variety of factors delayed the work, so we have significantly revised the proposal based on the valuable feedback provided by the ArchivesSpace community and informed by Harvard archivists' increasing experience with container management in ArchivesSpace. Some proposals have been removed, while others have been added or altered. Additions include * Return to Top Container search results from viewing an individual Top Container record * Bulk or batch function to create new Top Containers, associate existing Locations with them, and link them to multiple existing archival objects. * Bulk operation to delete barcodes from Top Containers * File-upload function to add Locations to Top Containers * Ability to merge Location records The most significant changes to previous proposals include the following: * The proposed additional indicator fields and ILS Bibliographic Record ID field in Top Containers have been removed. * The proposed Note field and Inactive checkbox for Locations, along with all functionality associated with inactive status, have been removed. * Automatic scoping of Container Profiles, Locations, and Location Profiles by repository appears to be too complex, given the community request to make repositories repeatable and the desire for it to be an installation configuration option. In lieu of that, the revised proposal adds a repeatable, optional repository field to container profiles and adds a facet for filtering by repository to browse results for Container Profiles and Locations. * Proposed functionality around Location status has been removed The revised draft proposal is attached to this email and we are asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that the proposal represents a superset of the work we may be able to complete in the next couple of months, and that not all the proposed changes will be addressed at this time. Another caveat: some of the desiderata require further technical design that will determine what approach will be taken. These will be investigated in consultation with Lyrasis ArchivesSpace staff. If you have questions or feedback, please email me at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 18, 2019. We look forward to receiving community input. Best, Robin Robin Wendler Library Technology Services Harvard University 90 Mt. Auburn St. Cambridge, MA 02138 617-998-5457 617-495-3724 r_wendler at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4074 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Mon Dec 23 08:40:47 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 23 Dec 2019 13:40:47 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - December 2019 Message-ID: [cid:image003.jpg at 01D5B96C.AB465F20] December 2019 Update Development We are working on the next release of ArchivesSpace, projected for early 2020. Some of the new features that are likely to be included are merging top containers, merging container profiles, and additional options for viewing results in the browse and search areas in the staff interface. The release will also have some performance and accessibility improvements. We will have more details closer to the time of the release. One of the most popular plugins for ArchivesSpace is the aspace-import-excel (https://github.com/harvard-library/aspace-import-excel) plugin, originally developed at Harvard University by Bobbi Fox. This plugin enables users to create archival objects in a spreadsheet and import them into an ArchivesSpace resource record, greatly speeding up data entry. We are pleased to share that we have contracted with Bobbi to convert this plugin to the core code of ArchivesSpace, meaning that this functionality will soon be available in ArchivesSpace without downloading and installing a separate plugin. We expect this feature to be completed for a release of ArchivesSpace in late winter or early spring of 2020. New ArchivesSpace Help Center We're pleased to announce that the new ArchivesSpace Help Center, with an improved user manual and new training videos, is now available. Access to the ArchivesSpace Help Center is a benefit of ArchivesSpace membership. The new and improved content is thanks to the efforts of our User Documentation sub-team and our training corps. Click here to learn more about accessing and navigating the Help Center. The current site (http://docs.archivesspace.org) will be up through early 2020, but it is closed to new user signups and no content will be updated. Staff of member institutions are eligible for accounts in the new Help Center. How you access the new Help Center depends on a variety of factors, including whether or not you had access to the previous Help Center: * If you already had an account for our Confluence site, privileges to access the new Help Center area have been added to your account. * If you had an account on the previous Help Center site but did not already have an account for our Confluence site, you received an email invitation from Atlassian to set up your account and get access to the new area. The subject line is ArchivesSpace has invited you to Confluence. If you did not receive this message, please contact us. * If you did not have an account on the previous Help Center site and do not already have a Confluence account, follow these steps to sign up for an account. Upon account creation, please allow 2 business days for Help Center permissions to take effect. We hope you enjoy the new content and look forward to the enhanced opportunities for community participation that the new site will allow. Thanks for your patience as we make this transition and please do let us know if you have any questions. Volunteer for the next ArchivesSpace Regional Forum We are looking for volunteers from member institutions of all sizes to form a working group to plan the agenda and program for our next Regional Forum in San Francisco, California! ArchivesSpace will hold a Regional Forum at the San Francisco Public Library in conjunction with the Western Archivists Conference on April 22, 2020. As with previous Regional Forums, this will be a free opportunity for staff of ArchivesSpace member institutions to meet and share information with each other and the program team. Working group volunteers are essential to the success of Regional Forums as they work with me to create a program that reflects local users' interests and activities. Please contact Jessica at jessica.crouch at lyrasis.org to volunteer by January 24th. Registration for the Western Archivists Regional Forum will open closer to the time of the event. Upcoming Webinar: Integrating ArchivesSpace with Aviary January 15, 2020, 2-3pm ET (11-noon PT; 7-8pm GMT) Visit the ArchivesSpace blog for details. ArchivesSpace is pleased to announce the fourth webinar in our series focused on Integrations with ArchivesSpace. Each webinar in this series will highlight an integration with another application used in archives that ArchivesSpace members have worked on or requested. The webinar series will feature both open source and proprietary systems. Our fourth webinar in this series will feature an integration with the audiovisual publishing platform Aviary. Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. In this webinar, Bertram Lyons (Aviary) will provide an overview of Aviary, highlighting access controls, accessibility and compliance. He will also demonstrate how Aviary integrates with ArchivesSpace and how this integration benefits archivists, specifically archivists from smaller organizations. Kevin Glick (Yale University Libraries) will present on Yale's integration of ArchivesSpace and Aviary. The presentation will highlight how Yale recognized the need for this integration within the libraries and both their vision and their experience implementing this integration. Kevin will also offer recommendations to other users considering integration. Presenters: Bertram Lyons specializes in the acquisition, management, and preservation of documentary, research, and cultural heritage collections. He has developed tools, policies, and partnerships around the development and management of analog and digital archival collections. For fifteen years, Bert has worked as an archivist for extensive archives, first at the Alan Lomax Archive and most recently at the American Folklife Center (AFC) at the Library of Congress. Bert is active with professional archival organizations including the International Association of Sound and Audiovisual Archives, the Society of American Archivists, the Association of Recorded Sound Collections, and the Association of Moving Image Archivists. He has also received certification from the Academy of Certified Archivists and is a graduate of the Archives Leadership Institute. He holds an MA in museum studies with a focus in American studies and archival theory from the University of Kansas. Kevin Glick is Head of Digitization and Digital Preservation and Archivist in Yale University Library's Manuscripts & Archives, where he currently focuses on digitization, digital libraries, and other technology issues in special collections and archives. In addition, Kevin manages the architecture of the Fortunoff Video Archive for Holocaust Testimony's digital preservation and access systems as well as digitization of all materials related to the collection. Who should attend: Anyone interested in possibilities for integrating ArchivesSpace with Aviary, those who have integrated ArchivesSpace and Aviary and would like to offer insight to others, and those who are interested in working with fellow community members to make integrations with ArchivesSpace easier. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. The next Integrations with ArchivesSpace webinar will be: Integrating ArchivesSpace with Archivematica, February 19, 2020 at 2pm ET (11am PT) The recording for the previous webinar in this series, Integrating ArchivesSpace with Archive-It, is now available. Upcoming Open Community Call Please join us for our next community open call on Zoom on January 22 at 2-3pm ET (11-noon PT). This is an opportunity to talk informally about ideas you've had, challenges you've encountered, or news you'd like to share. During this call the Development Prioritization sub-team of our User Advisory Council will summarize the results of their recent community survey and the User Documentation sub-team will discuss plans for improvements to the User Manual on the new ArchivesSpace Help Center. If you would like to see a topic or discussion item addressed during the call, here is a pre-survey to help generate discussion topics. Please submit your suggestions by Tuesday, January 21st You will be able to join by either computer or phone. Here are the details for joining the call: Join Zoom Meeting https://lyrasis.zoom.us/j/214850306?pwd=aWp3VHZneE1XN2F5aThZMjE3bWhNdz09 Meeting ID: 214 850 306 Password: 093293 One tap mobile +19292056099,,214850306# US (New York) +16699006833,,214850306# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) 877 853 5257 US Toll-free 888 475 4499 US Toll-free Meeting ID: 214 850 306 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh ArchivesSpace Holiday Hours Our office will be closed from December 24 to January 1. Normal office hours will resume on January 2nd. We wish you all warm and happy holidays! Membership Update We are excited to welcome our newest members to our community! Our new members since November 30 include: * Honpa Hongwanji Mission of Hawaii * The New School (New York, New York) * University of Pittsburgh (Educational Program Member) As of December 23, we have 410 General members, 20 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 Tools 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 19935 bytes Desc: image003.jpg URL: From ahueb2 at uis.edu Mon Dec 23 10:42:25 2019 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Mon, 23 Dec 2019 15:42:25 +0000 Subject: [Archivesspace_Users_Group] [EXTERNAL] Re: ASpace database constraints In-Reply-To: <6F9641DB-EBDD-4DD9-96BA-B8A9EE7C839D@harvard.edu> References: <6F9641DB-EBDD-4DD9-96BA-B8A9EE7C839D@harvard.edu> Message-ID: <1577115745454.62047@uis.edu> Thanks Dave! ASnake is incredibly helpful, I've written scripts to automatically sort through our records to delete what needs to be removed for our database merge. It looks like it is possible to upload json records through the ASpace API, initially I was planning on uploading our modified records in EAD format but it would be nice if I can streamline the entire process through the API. Does anyone know if the json records obtained through the API differ from EAD records obtained using the ead_export script that comes with ASpace? At first glance it appears there might be some differences. Or might there be a way to incorporate EAD export/import using ASnake and the ASpace API? -Alan Huebschen University of Illinois at Springfield Brookens Library Information Systems ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mayo, Dave Sent: Friday, December 20, 2019 9:02 AM To: Archivesspace Users Group Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] ASpace database constraints Hi Alan, So, it?s _possible_ to do a cascade delete of records in ASpace, but for a couple of reasons, I think it?s not necessarily a real good idea. Solr is unhappy not just because there?s leftover info in other tables, but also probably because it can?t inherently see the bulk deletions in MySQL. I think it?d probably be safer to delete things via the ArchivesSpace API; this way Solr will stay consistent throughout, and subsidiary records that depend on Resource _should_ all get deleted as well (I?m not quite comfortable saying ?will,? but if not, you can also clean those up via the API. There?s an actively maintained API client for ArchivesSpace, ArchivesSnake - https://github.com/archivesspace-labs/archivessnake; and a lot of example scripts are linked in the documentation. I think in principle, this would be fairly straightforward; you?d need to collect the ids of the resources you want to delete, and then delete them. So, just as a simplified example, if you wanted to delete all resources in repository 2: from asnake.client import ASnakeClient client = ASnakeClient(username=?admin?, password=?admin?, baseurl=?http://path.to.backend?) repos_response = client.get(?repositories/2/resources?, params={?all_ids?: True}) if (repos_response.status_code != 200): raise ?Something went wrong!? for res_id in repos_response.json(): delete_response = client.delete(?repositories/2/resources/{}?.format(res_id)) if (delete_response.status_code != 200): print(?Failed to delete {}?.format(res_id)) If you decide to try this and run into trouble, please feel free to email me, I?d be happy to help walk you through setup/troubleshooting. -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: on behalf of "Huebschen, Alan M" Reply-To: Archivesspace Users Group Date: Friday, December 20, 2019 at 9:44 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ASpace database constraints Good morning all, I've been working with some test instances of our database and I need to remove some records in bulk. We are currently running ASpace against a MySQL instance and I am attempting to remove all traces of specific records from the tables. Easily enough I can delete the records from the resource table after disabling foreign key checks, however it appears that there is information left over in other tables making Solr an unhappy camper. I created an EER diagram in MySQL Workbench to try and figure out which records are tied together, but as someone who is fairly new to database work it's a bit of a headache to wrap my mind around. >From the research I've done, some records can be set as a parent and with a cascade setting the child records in other tables will be removed when the parent is removed. I've looked at some of the table settings but I haven't been able to figure out what needs to be removed to clean up the db or what the proper order of removal would be. Has anyone here removed resource table entries and their associated records with success? How can I go about figuring out what I need to remove and/or how to remove it? -Alan Huebschen University of Illinois at Springfield Brookens Library Information Systems -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Dec 23 13:55:16 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 23 Dec 2019 18:55:16 +0000 Subject: [Archivesspace_Users_Group] Happy holidays from ArchivesSpace Message-ID: [Happy Holidays from ArchivesSpace] Dear ArchivesSpace community, Thank you for your continued support! We really appreciate all you do to shape ArchivesSpace, both as an application and a community. This has been a wonderful year of progress and growth, and we look forward to accomplishing even more together in the next. Our office will be closed from December 24 to January 1. Normal office hours will resume on January 2nd. We wish you all warm and happy holidays! Sincerely, Your ArchivesSpace Program Team (Christine Di Bella, Jessica Crouch, Laney McGlohon, Lora Woodford, Alicia Johnson, and Laurie Gemmill Arp) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 40121 bytes Desc: image003.jpg URL: