From Christine.Kim at lyrasis.org Wed Aug 1 01:19:07 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 1 Aug 2018 05:19:07 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - July 2018 Message-ID: [ASpaceOrgHome.jpg] July 2018 Update Please join us at the upcoming 4th annual Member Forum! We'll be at the Society of American Archivists annual conference, and would love the opportunity to meet you and hear updates on your projects. We just had a great webinar featuring work the Reports sub-team has recently accomplished, which will be included in the next release. Read on for more news! Development Our next release is imminent. We expect to put out a release candidate this week, and then, barring major issues, aim to put out the release itself no later than August 10. The centerpiece of this next release will be the refactored reports worked on by our own Sarah Morrissey. Another area that will be less immediately visible but bound to be appreciated by many is code to enhance staff interface performance that has been contributed by Mark Triggs. The release will also include a number of other fixes and improvements from community members, the program team and those working with us. Look for an announcement later this week of the release candidate and a call for wider community testing. Webinars Past Webinar: Reports Refactored Thanks to all who joined us for the Reports Refactored webinar on July 31. Special thanks to our presenter Sarah Morrissey (ArchivesSpace). Resources from the webinar are now available: http://archivesspace.org/archives/3098 Feedback on Webinars & Ideas for the Future We are interested in hearing your feedback on ArchivesSpace webinars -- What do you enjoy about the webinars? How can we improve them? How does the schedule work for you? These are some of the questions we ask, as well as an opportunity to provide insight into potential themes and topics we should explore in the future. This will be an ongoing survey. Please share your thoughts with us when you have a chance. https://tinyurl.com/aspace-webinarsurvey Call for Comments: ArchivesSpace Documentation - Twitter Chat on August 8 The ArchivesSpace Users Advisory Council's Documentation sub-team is seeking input from the community in an effort to improve the application's documentation, which currently consists of the User Manual, screencasts, and video tutorials. * Are there any sections of the manual that you would like to see improved? * Are there features of the application you find difficult to implement? * Is there a new type of screencast you'd like to see? * Do you have an idea for a completely new way of documenting ArchivesSpace? Please let the team know! Use this form to submit your comments and idea. (https://goo.gl/forms/7MFLUqIzeKY6iPeq1) The User Documentation sub-team will also be hosting a Twitter chat on August 8th from 11am-12pm PDT (2pm-3pm EDT) and 6pm-7pm PDT (9pm-10pm EDT). The chat will be hosted by @ArchivesSpace. Please use the hashtag #aspacedoc to tag your questions/comments. This Twitter chat will be hosted by the ArchivesSpace Users Advisory Council's Documentation sub-team. Annual Member Forum: August 14, 2018, in Washington D.C. Registration is now open! We kindly ask you to register by August 7th so we can finalize our lunch orders. We will continue to take registrations until August 14th. Plan your visit: * Program: The program is available on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. * Open Discussion on the Future of ArchivesSpace: Do you have a topic you would like to suggest for this discussion? More information is available here. * Registration: Registration is open! * Location: ArchivesSpace will be holding its fourth annual Member Forum on August 14, 2018 at the Josephine Butler Parks Center in Washington, DC. * Parking & Transportation: Information about transportation is available here. * Reception: This year we're excited to join forces with our friends at Archive-It to co-host a reception that will bring our partner communities together. Join us at the Conservation Pavilion at the National Zoo from 5-7 PM for drinks, hors d'oeuvres, and good times! More information is available here: http://archivesspace.org/archives/3025 Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. If you have any questions or other suggestions, please feel free to email Kim at christine.kim at lyrasis.org. [https://lh5.googleusercontent.com/X4ROgS58DM0xS83GmQdBtG6KfLNnaC3nnuQdffR7I0bT50-rLMETMhPmhFaqd-gKthW9A_b6VPaKiYQkwozjpM4kNAPy-PvJN25fRrIQkgScqjk-sX5gVqmDpUUpqpOKne1ocCzd] ArchivesSpace at SAA! The program team will also be at the Society of American Archivists annual conference! Find us in the Expo Hall at booth #613 during these hours: * Thursday, August 16 * Expo Hall Grand Opening /Happy Hour: 5:30 pm - 7:00 pm * Friday, August 17 * Expo Hall is open: 8:00 am - 4:30 pm * Expo Hall Coffee Break: 8:00 am - 8:30 am * Expo Hall Lunch: 12:00 - 1:30 pm * Expo Hall Closing Break: 4:15 - 5:00 pm ArchivesSpace Sessions at SAA Congratulations to our community members who are presenting on their incredible work using ArchivesSpace. * 408 - Pop Up: The Messy Work of Database Migrations (Friday, August 17 - 9:45am - 10:45am) Moving from one database to another is anything but a smooth transition. A panel of archivists will share their experience of cleaning data, organizing and "packing" finding aids, and migrating them from one database to another. As with a household move, we encountered cluttered closets, broken items, and long lost treasures we forgot we owned. In our commitment to transparency, we will discuss the real and arduous challenges we encountered in our database migrations and will share our programming fixes, plans for standardizing our data, and lessons we learned along the way. No archives have completely perfect finding aids which can cause database migration to be a seemingly impossible task. This panel's goal is to candidly share the hurdles we encountered and solutions we implemented in our own database migrations in order to make yours less challenging. This panel format pop-up will present on a number of databases from which we migrated from including Archivists' Toolkit, Archon, ReDiscovery, and Homegrown Databases into Archives Space. We will offer our solutions to commonly encountered challenges and pitfalls and show helpful tips and tools. We will share lessons learned and solicit a robust question and answer period in order to best address unique audience inquiries. We encourage anyone who is thinking about a database migration, completed one and may have insight to share during our Q & A, or anywhere in between to attend our session. In addition to our panel presentations, we will highlight a newly created Awesome ArchivesSpace List that can serve as a wonderful resource tool for those in the database migration market. * 510 - Challenge Accepted: Building Access Infrastructure for 400+ Years and 1000+ Creators at NYC Municipal Archives (Friday, August 17 - 2:00pm - 3:00pm) For the first time in decades, NYC Municipal Archives is newly addressing legacy issues to provide access to more than 400 years of records. Challenged with the complexities of government, we've struggled to maintain the balance between function and provenance. To provide access and context, we've established a historical ontology within ArchivesSpace of NYC government creators and traced them to their modern-day Record Group equivalents. Join us for a special session sharing our process. * 709 - Beyond the Reference Interview: Assessing the Reading Room Experience (Saturday, August 18 -10:30am - 11:30am) Join us to explore and discuss strategies deployed by public services archivists to gauge levels of patron satisfaction in physical and virtual reading room spaces. Contributors share assessment efforts designed to create more inclusive and efficient research experiences. These include techniques for creating and delivering surveys, data collected from usability studies on several different interfaces (ArchivesSpace PUI, Aeon, and web-based digital collections), and tools for training and assessing students who are responsible for providing research services. New Stories on the Blog In All About Community (http://archivesspace.org/category/all-about-community/), John Zarrillo (Senior Archivist, New York University) introduces the User Documentation sub-team and the work they do to maintain the user manual. This is a continuation of a series looking into the various sub-teams of the Technical Advisory Council and User Advisory Council to provide insight into the variety of activities and initiatives undertaken by these groups. We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Kim at christine.kim at lyrasis.org. Membership Update We are excited to welcome our newest members to our community! Our new members since June 30 include: * Diocese of Olympia (Seattle, WA) * Dominican University of California (San Rafael, CA) * East Carolina University (Greenville, NC) * Kingston Public Library (Kingston, MA) * Providence City Archives (Providence, RI) * Tennessee State Library & Archives (Nashville, TN) As of July 31, we have 359 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 20006 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 337888 bytes Desc: image006.png URL: From cpeterson at smith.edu Wed Aug 1 10:46:50 2018 From: cpeterson at smith.edu (Christie Peterson) Date: Wed, 1 Aug 2018 10:46:50 -0400 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions Message-ID: Hello, Is there more detailed documentation somewhere about managing user accounts and permissions? (beyond what is in the user manual) Specifically, I need to know: - What happens when a user account is deleted? Does it delete all references to them in the database (that is, every action they've taken)? If so, what is a better alternative to deletion to use when a staff member leaves an organization? - Is there an easy way through the interface to see who currently has system administrator priviledges? Thanks, CP Christie S. Peterson Manager of Technical Services for Special Collections Smith College cpeterson at smith.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry.weimer at nyhistory.org Wed Aug 1 10:55:14 2018 From: larry.weimer at nyhistory.org (Larry Weimer) Date: Wed, 1 Aug 2018 10:55:14 -0400 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: References: Message-ID: Christie, When users no longer need access, I've taken two steps: 1) delete their ID from the user group they're in and 2) change the password. That would seem to eliminate their ability to access and act in the system, while retaining a record of them. Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Aug 1, 2018 at 10:46 AM, Christie Peterson wrote: > Hello, > > Is there more detailed documentation somewhere about managing user > accounts and permissions? (beyond what is in the user manual) > > Specifically, I need to know: > > - What happens when a user account is deleted? Does it delete all > references to them in the database (that is, every action they've taken)? > If so, what is a better alternative to deletion to use when a staff member > leaves an organization? > - Is there an easy way through the interface to see who currently has > system administrator priviledges? > > Thanks, > > CP > Christie S. Peterson > Manager of Technical Services for Special Collections > Smith College > cpeterson at smith.edu > she/her/hers > > > > _______________________________________________ > 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 michelsd at union.edu Wed Aug 1 11:13:38 2018 From: michelsd at union.edu (Michelson, Daniel) Date: Wed, 1 Aug 2018 11:13:38 -0400 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: References: Message-ID: Hi Christie, To answer your second question, any system administrators should have the "Edit Groups" button grayed out in the Manage User Access list. Dan Michelson On Wed, Aug 1, 2018 at 10:55 AM, Larry Weimer wrote: > Christie, > > When users no longer need access, I've taken two steps: 1) delete their ID > from the user group they're in and 2) change the password. That would seem > to eliminate their ability to access and act in the system, while retaining > a record of them. > > Larry > > Larry Weimer > Head of Archival Processing > New-York Historical Society > > On Wed, Aug 1, 2018 at 10:46 AM, Christie Peterson > wrote: > >> Hello, >> >> Is there more detailed documentation somewhere about managing user >> accounts and permissions? (beyond what is in the user manual) >> >> Specifically, I need to know: >> >> - What happens when a user account is deleted? Does it delete all >> references to them in the database (that is, every action they've taken)? >> If so, what is a better alternative to deletion to use when a staff member >> leaves an organization? >> - Is there an easy way through the interface to see who currently has >> system administrator priviledges? >> >> Thanks, >> >> CP >> Christie S. Peterson >> Manager of Technical Services for Special Collections >> Smith College >> cpeterson at smith.edu >> she/her/hers >> >> >> >> _______________________________________________ >> 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.huffman at duke.edu Wed Aug 1 11:29:08 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Wed, 1 Aug 2018 15:29:08 +0000 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: References: Message-ID: Hi Christie, I created a new permissions group called ?Expired Users? (morbid, I know). That group has no permissions in the system. When students/interns/staff leave our employ, I assign their user account to that group. This way I can keep a record of their username and other user details. To answer your first question, I believe the ?created_by? and ?last_modified_by? fields will still retain usernames even if those users are deleted from the system. -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 Michelson, Daniel Sent: Wednesday, August 1, 2018 11:14 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions Hi Christie, To answer your second question, any system administrators should have the "Edit Groups" button grayed out in the Manage User Access list. Dan Michelson On Wed, Aug 1, 2018 at 10:55 AM, Larry Weimer > wrote: Christie, When users no longer need access, I've taken two steps: 1) delete their ID from the user group they're in and 2) change the password. That would seem to eliminate their ability to access and act in the system, while retaining a record of them. Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Aug 1, 2018 at 10:46 AM, Christie Peterson > wrote: Hello, Is there more detailed documentation somewhere about managing user accounts and permissions? (beyond what is in the user manual) Specifically, I need to know: * What happens when a user account is deleted? Does it delete all references to them in the database (that is, every action they've taken)? If so, what is a better alternative to deletion to use when a staff member leaves an organization? * Is there an easy way through the interface to see who currently has system administrator priviledges? Thanks, CP Christie S. Peterson Manager of Technical Services for Special Collections Smith College cpeterson at smith.edu she/her/hers _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [http://email.nyhscommunications.org/email/Footer_Shoes3.jpg] _______________________________________________ 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 mkottman at ku.edu Wed Aug 1 12:33:32 2018 From: mkottman at ku.edu (Kottman, Miloche) Date: Wed, 1 Aug 2018 16:33:32 +0000 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: References: Message-ID: <9c18ff036f8b4f31b4d29d0ca0e55b82@ex13-ell-cr-15.home.ku.edu> Christie, This behavior may have changed in subsequent releases so you may want to experiment ? Ages ago (somewhere in the version 1.2 ? 1.3 range) we switched to a Shibboleth sign in system which caused pseudo duplicate users when the Shib username was not the same as the one manually created in ASpace. So to fix this I naively deleted the username that was created manually in ASpace. Everything worked fine and dandy until we upgraded to a newer version of ASpace. My IT folks said that this generated a lot of errors and prevented the upgrade until they went in and cleaned up the affected records. ASpace was trying to link information in fields to users who no longer existed, my guess would be the create/modify information. Fortunately for us it was early days of our installation so it was only a handful of records. So my advice, don?t delete your user records. --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Noah Huffman Sent: Wednesday, August 1, 2018 10:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions Hi Christie, I created a new permissions group called ?Expired Users? (morbid, I know). That group has no permissions in the system. When students/interns/staff leave our employ, I assign their user account to that group. This way I can keep a record of their username and other user details. To answer your first question, I believe the ?created_by? and ?last_modified_by? fields will still retain usernames even if those users are deleted from the system. -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 Michelson, Daniel Sent: Wednesday, August 1, 2018 11:14 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions Hi Christie, To answer your second question, any system administrators should have the "Edit Groups" button grayed out in the Manage User Access list. Dan Michelson On Wed, Aug 1, 2018 at 10:55 AM, Larry Weimer > wrote: Christie, When users no longer need access, I've taken two steps: 1) delete their ID from the user group they're in and 2) change the password. That would seem to eliminate their ability to access and act in the system, while retaining a record of them. Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Aug 1, 2018 at 10:46 AM, Christie Peterson > wrote: Hello, Is there more detailed documentation somewhere about managing user accounts and permissions? (beyond what is in the user manual) Specifically, I need to know: * What happens when a user account is deleted? Does it delete all references to them in the database (that is, every action they've taken)? If so, what is a better alternative to deletion to use when a staff member leaves an organization? * Is there an easy way through the interface to see who currently has system administrator priviledges? Thanks, CP Christie S. Peterson Manager of Technical Services for Special Collections Smith College cpeterson at smith.edu she/her/hers _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender. http://email.nyhscommunications.org/email/Footer_Shoes3.jpg] _______________________________________________ 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: 1004 bytes Desc: image001.jpg URL: From ltang5 at lib.msu.edu Wed Aug 1 12:50:38 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Wed, 1 Aug 2018 16:50:38 +0000 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions Message-ID: <7531452a1849403e9595da687a131559@lib.msu.edu> Although I don't know the timeline for the implementation, the Staff Interface Enhancement Working Group (which both Christie and Miloche were magnificent participants in :) ) proposed easier ways to identify inactive users. I know that this improvement is in the pipeline for sometime down the road! Lydia Sent from my Verizon, Samsung Galaxy smartphone From eve.neiger at yale.edu Wed Aug 1 16:04:49 2018 From: eve.neiger at yale.edu (Neiger, Eve) Date: Wed, 1 Aug 2018 20:04:49 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Message-ID: Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 - eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Aug 1 18:39:05 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 1 Aug 2018 22:39:05 +0000 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: <9c18ff036f8b4f31b4d29d0ca0e55b82@ex13-ell-cr-15.home.ku.edu> References: <9c18ff036f8b4f31b4d29d0ca0e55b82@ex13-ell-cr-15.home.ku.edu> Message-ID: All, It sounds like Noah?s suggestion is a really great one! I?d also heed Miloche?s advice about not deleting user records!!! Another wrinkle is that whenever you create a user record in ArchivesSpace, a corresponding agent record is created at the same time (those records are also linked, but invisibly essentially, since they?re only linked in the database, and editing one doesn?t change the contents of the other record, of course). Here?s the kicker: let?s say you later update that agent record with an LCCN authority ID, link it up to some descriptive records, etc., then if you delete that user record in the staff interface, then the agent record is also deleted silently, which includes all links to any other records! That?s definitely not what someone would expected (and I just tested to confirm that it?s still true in version 2.4.1). The reverse, thankfully, is not true. If you try to link an agent record that was created because it?s linked to a user record, then you will get an error in the staff interface telling you that you cannot delete that agent record. Although if the interface allowed you to do that, it would be potentially less disastrous than losing an agent record and all of its links. Anyhow, the takeaway, in my opinion, is to never stray from Miloche?s advice ? Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kottman, Miloche Sent: Wednesday, 01 August, 2018 12:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions Christie, This behavior may have changed in subsequent releases so you may want to experiment ? Ages ago (somewhere in the version 1.2 ? 1.3 range) we switched to a Shibboleth sign in system which caused pseudo duplicate users when the Shib username was not the same as the one manually created in ASpace. So to fix this I naively deleted the username that was created manually in ASpace. Everything worked fine and dandy until we upgraded to a newer version of ASpace. My IT folks said that this generated a lot of errors and prevented the upgrade until they went in and cleaned up the affected records. ASpace was trying to link information in fields to users who no longer existed, my guess would be the create/modify information. Fortunately for us it was early days of our installation so it was only a handful of records. So my advice, don?t delete your user records. --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Noah Huffman Sent: Wednesday, August 1, 2018 10:29 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions Hi Christie, I created a new permissions group called ?Expired Users? (morbid, I know). That group has no permissions in the system. When students/interns/staff leave our employ, I assign their user account to that group. This way I can keep a record of their username and other user details. To answer your first question, I believe the ?created_by? and ?last_modified_by? fields will still retain usernames even if those users are deleted from the system. -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 Michelson, Daniel Sent: Wednesday, August 1, 2018 11:14 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions Hi Christie, To answer your second question, any system administrators should have the "Edit Groups" button grayed out in the Manage User Access list. Dan Michelson On Wed, Aug 1, 2018 at 10:55 AM, Larry Weimer > wrote: Christie, When users no longer need access, I've taken two steps: 1) delete their ID from the user group they're in and 2) change the password. That would seem to eliminate their ability to access and act in the system, while retaining a record of them. Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Aug 1, 2018 at 10:46 AM, Christie Peterson > wrote: Hello, Is there more detailed documentation somewhere about managing user accounts and permissions? (beyond what is in the user manual) Specifically, I need to know: * What happens when a user account is deleted? Does it delete all references to them in the database (that is, every action they've taken)? If so, what is a better alternative to deletion to use when a staff member leaves an organization? * Is there an easy way through the interface to see who currently has system administrator priviledges? Thanks, CP Christie S. Peterson Manager of Technical Services for Special Collections Smith College cpeterson at smith.edu she/her/hers _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender. http://email.nyhscommunications.org/email/Footer_Shoes3.jpg] _______________________________________________ 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: 1004 bytes Desc: image001.jpg URL: From adrien_hilton at harvard.edu Thu Aug 2 10:28:43 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 2 Aug 2018 14:28:43 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results In-Reply-To: References: Message-ID: Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that's listed, creator last name, for instance. What field are you sorting this from? At Harvard, we're currently browsing collections using the first word of the collection title, which is not ideal. We'd prefer to sort by finding aid title, but I've been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 - eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Thu Aug 2 11:00:29 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 2 Aug 2018 15:00:29 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results In-Reply-To: References: Message-ID: Hi Adrien, Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what's used for sorting. If there's no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like "Guide to the..." or "Inventory of" etc. at the very beginning). Here's where that logic happens in the indexer: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 I hope that helps (and I hope the bit about the indexer above is correct, but I'm pretty sure that it is). But if you put the title as you want it to be sorted in the "finding aid filing title" in the staff interface, then you should be all set. For instance, the "Bradford Edward Ableson Papers" sorts before "Accelerator Laboratories, Yale University, photographs" in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: "Ableson (Bradford Edward) Papers" Also, I agree that the report that Eve shared looks great!!! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 10:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that's listed, creator last name, for instance. What field are you sorting this from? At Harvard, we're currently browsing collections using the first word of the collection title, which is not ideal. We'd prefer to sort by finding aid title, but I've been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 - eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Thu Aug 2 11:41:45 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 2 Aug 2018 15:41:45 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results In-Reply-To: References: Message-ID: Hi Mark, Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, "Last Name, First Name. First Name Last Name papers: Guide." But thanks for the link, that might help us develop a solution. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 11:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Adrien, Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what's used for sorting. If there's no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like "Guide to the..." or "Inventory of" etc. at the very beginning). Here's where that logic happens in the indexer: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 I hope that helps (and I hope the bit about the indexer above is correct, but I'm pretty sure that it is). But if you put the title as you want it to be sorted in the "finding aid filing title" in the staff interface, then you should be all set. For instance, the "Bradford Edward Ableson Papers" sorts before "Accelerator Laboratories, Yale University, photographs" in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: "Ableson (Bradford Edward) Papers" Also, I agree that the report that Eve shared looks great!!! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 10:29 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that's listed, creator last name, for instance. What field are you sorting this from? At Harvard, we're currently browsing collections using the first word of the collection title, which is not ideal. We'd prefer to sort by finding aid title, but I've been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 - eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Aug 2 12:41:06 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 2 Aug 2018 16:41:06 +0000 Subject: [Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.5.0-RC1 Message-ID: The ArchivesSpace team is pleased to announce a release candidate, v2.5.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.5.0-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This release candidate contains many program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. The centerpiece of this release candidate is the refactored reports worked on by our co-op student from Georgia Tech, Sarah Morrissey. Another improvement that is sure to be greatly appreciated by many is code that has been contributed by Mark Triggs that reduces loading times for records in the staff interface. Other items of note include small updates to the OAI-PMH functionality, the MARCXML exporter, the EAD exporter, and the PDF produced from the public interface, and the option to use Japanese translations for the interface labels. There are also some bug fixes for the public and staff interfaces and some additional automated tests and infrastructure upgrades. This release also adds a linked top containers endpoint for the API, which will facilitate bulk data operations related to containers. Thanks to the many community members who made contributions to this release, including both individual developers and our Development Prioritization sub-team, Reports sub-team, and Core Committers Group. In putting release notes together we're always heartened by the reminder of just how many people work with us to make ArchivesSpace better for everyone. Thank you all. Please try this release candidate out over the next few days and let us know by August 8 at ArchivesSpaceHome at lyrasis.org if you notice any problems with the specific areas that are addressed in this release, or if anything that was working before no longer is. Barring major issues, we expect to release 2.5.0 by the end of next week. 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: image005.jpg Type: image/jpeg Size: 6608 bytes Desc: image005.jpg URL: From mark.custer at yale.edu Thu Aug 2 14:56:25 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 2 Aug 2018 18:56:25 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results In-Reply-To: References: Message-ID: That's actually a really good use case for using the ASpace API. The Finding Aid Title field could be moved (or duplicated) in the Filing Title field with a sleek script! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 11:42 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Mark, Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, "Last Name, First Name. First Name Last Name papers: Guide." But thanks for the link, that might help us develop a solution. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 11:00 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Adrien, Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what's used for sorting. If there's no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like "Guide to the..." or "Inventory of" etc. at the very beginning). Here's where that logic happens in the indexer: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 I hope that helps (and I hope the bit about the indexer above is correct, but I'm pretty sure that it is). But if you put the title as you want it to be sorted in the "finding aid filing title" in the staff interface, then you should be all set. For instance, the "Bradford Edward Ableson Papers" sorts before "Accelerator Laboratories, Yale University, photographs" in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: "Ableson (Bradford Edward) Papers" Also, I agree that the report that Eve shared looks great!!! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 10:29 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that's listed, creator last name, for instance. What field are you sorting this from? At Harvard, we're currently browsing collections using the first word of the collection title, which is not ideal. We'd prefer to sort by finding aid title, but I've been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 - eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Aug 2 15:57:39 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 2 Aug 2018 19:57:39 +0000 Subject: [Archivesspace_Users_Group] Finding Air Filing Title sort [was: Yale Library ASpace PUI Usability Testing Final Report + Results] In-Reply-To: References: Message-ID: <873DFFA3-CBDD-4DCA-B477-B2A6BE325861@virginia.edu> I usually agree with the notion that you shouldn?t try modifying resources directly in MySQL unless you know what you?re doing. That?s because, when you?re dealing with linked resources, you need to define some complicated views using multiple JOINs in MySQL to follow those linkages so that parents and children all get updated properly. The backend API resolves these links for you in most cases, so it?s simpler to use the API. However, this is one of those cases where you would just be modifying one MySQL resource field based on another in the same record, so no extra link resolution required. Simpler to update in MySQL and then trigger a Solr reindex. ( Because making changed directly in MySQL bypasses the indexer notifications. ) Also a lot more efficient if you?ve got a lot of resources. ? Steve. > On Aug 2, 2018, at 2:56 PM, Custer, Mark wrote: > > That?s actually a really good use case for using the ASpace API. The Finding Aid Title field could be moved (or duplicated) in the Filing Title field with a sleek script! > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien > Sent: Thursday, 02 August, 2018 11:42 AM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results > > Hi Mark, > > Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, ?Last Name, First Name. First Name Last Name papers: Guide.? > > But thanks for the link, that might help us develop a solution. > > Best wishes, > Adrien > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark > Sent: Thursday, August 02, 2018 11:00 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results > > Hi Adrien, > > Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what?s used for sorting. If there?s no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like ?Guide to the?? or ?Inventory of? etc. at the very beginning). > > Here?s where that logic happens in the indexer: > > https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 > > I hope that helps (and I hope the bit about the indexer above is correct, but I?m pretty sure that it is). But if you put the title as you want it to be sorted in the ?finding aid filing title? in the staff interface, then you should be all set. For instance, the ?Bradford Edward Ableson Papers? sorts before ?Accelerator Laboratories, Yale University, photographs? in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: ?Ableson (Bradford Edward) Papers? > > Also, I agree that the report that Eve shared looks great!!! > > Mark > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org ] On Behalf Of Hilton, Adrien > Sent: Thursday, 02 August, 2018 10:29 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results > > Hi Eve, > > Congratulations, this looks great! > > A question: your collections browse list is alphabetical by something other than the first word of the title that?s listed, creator last name, for instance. What field are you sorting this from? > > At Harvard, we?re currently browsing collections using the first word of the collection title, which is not ideal. We?d prefer to sort by finding aid title, but I?ve been told this field is not sortable in the core code. > > Thanks, > Adrien > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve > Sent: Wednesday, August 01, 2018 4:05 PM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results > > Dear ArchivesSpace User Group Members: > > The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. > > The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users? mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. > > We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. > > You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing > We?ve also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH > > And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here:https://puitestarchivesspace.library.yale.edu/ > *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. > > We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me ateve.neiger at yale.edu . > > Best, > > Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup > > Eve Neiger > Archivist > Beinecke Rare Book and Manuscript Library > Yale University > 203.432.9027 ? eve.neiger at yale.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: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From mark.custer at yale.edu Thu Aug 2 17:31:49 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 2 Aug 2018 21:31:49 +0000 Subject: [Archivesspace_Users_Group] Finding Air Filing Title sort [was: Yale Library ASpace PUI Usability Testing Final Report + Results] In-Reply-To: <873DFFA3-CBDD-4DCA-B477-B2A6BE325861@virginia.edu> References: <873DFFA3-CBDD-4DCA-B477-B2A6BE325861@virginia.edu> Message-ID: Good point, Steve. Also, I *think* (not 100% sure about this now that I?m typing this) that you can coax a re-index by updating the modification time when running an SQL update if you?re updating the timestamp on a major record type. At least, we?ve usually included a new ?modified time? and ?username? whenever we opted to update the database directly. And yes, it?s a heck of a lot quicker, as my colleague Alicia Detelich can attest! A couple of months ago she updated about 1 million date records with normalized begin/end date values, and she did that with an SQL update script since it only took a few seconds that way, whereas using the API to update ~1 million archival object records would?ve taken? well? I forget how long it would?ve taken in our setup, but it was a long time ?. All that said, often folks might have access to the API but that doesn?t mean that they also have access to the underlying database. I have read-only access to our database but not write access, for example. And some folks might not even have database access at all (but hopefully they?re very friendly with their IT department/person in that case). I know that?s definitely come up before when discussing workarounds for reports. Mark p.s. thank you for changing the subject line, as I almost always forgot to do that! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Thursday, 02 August, 2018 3:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding Air Filing Title sort [was: Yale Library ASpace PUI Usability Testing Final Report + Results] I usually agree with the notion that you shouldn?t try modifying resources directly in MySQL unless you know what you?re doing. That?s because, when you?re dealing with linked resources, you need to define some complicated views using multiple JOINs in MySQL to follow those linkages so that parents and children all get updated properly. The backend API resolves these links for you in most cases, so it?s simpler to use the API. However, this is one of those cases where you would just be modifying one MySQL resource field based on another in the same record, so no extra link resolution required. Simpler to update in MySQL and then trigger a Solr reindex. ( Because making changed directly in MySQL bypasses the indexer notifications. ) Also a lot more efficient if you?ve got a lot of resources. ? Steve. On Aug 2, 2018, at 2:56 PM, Custer, Mark > wrote: That?s actually a really good use case for using the ASpace API. The Finding Aid Title field could be moved (or duplicated) in the Filing Title field with a sleek script! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 11:42 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Mark, Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, ?Last Name, First Name. First Name Last Name papers: Guide.? But thanks for the link, that might help us develop a solution. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 11:00 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Adrien, Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what?s used for sorting. If there?s no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like ?Guide to the?? or ?Inventory of? etc. at the very beginning). Here?s where that logic happens in the indexer: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 I hope that helps (and I hope the bit about the indexer above is correct, but I?m pretty sure that it is). But if you put the title as you want it to be sorted in the ?finding aid filing title? in the staff interface, then you should be all set. For instance, the ?Bradford Edward Ableson Papers? sorts before ?Accelerator Laboratories, Yale University, photographs? in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: ?Ableson (Bradford Edward) Papers? Also, I agree that the report that Eve shared looks great!!! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 10:29 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that?s listed, creator last name, for instance. What field are you sorting this from? At Harvard, we?re currently browsing collections using the first word of the collection title, which is not ideal. We?d prefer to sort by finding aid title, but I?ve been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users? mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We?ve also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here:https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me ateve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 ? eve.neiger at yale.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 bobbi_fox at harvard.edu Fri Aug 3 08:12:28 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Fri, 3 Aug 2018 12:12:28 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results In-Reply-To: References: Message-ID: That thought had occurred to me, since I'm already knee deep in ArchiveSnake. :-) From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 2:56 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results That's actually a really good use case for using the ASpace API. The Finding Aid Title field could be moved (or duplicated) in the Filing Title field with a sleek script! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 11:42 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Mark, Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, "Last Name, First Name. First Name Last Name papers: Guide." But thanks for the link, that might help us develop a solution. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 11:00 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Adrien, Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what's used for sorting. If there's no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like "Guide to the..." or "Inventory of" etc. at the very beginning). Here's where that logic happens in the indexer: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 I hope that helps (and I hope the bit about the indexer above is correct, but I'm pretty sure that it is). But if you put the title as you want it to be sorted in the "finding aid filing title" in the staff interface, then you should be all set. For instance, the "Bradford Edward Ableson Papers" sorts before "Accelerator Laboratories, Yale University, photographs" in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: "Ableson (Bradford Edward) Papers" Also, I agree that the report that Eve shared looks great!!! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 10:29 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that's listed, creator last name, for instance. What field are you sorting this from? At Harvard, we're currently browsing collections using the first word of the collection title, which is not ideal. We'd prefer to sort by finding aid title, but I've been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users' mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We've also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 - eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From maura.carbone at yale.edu Fri Aug 3 09:05:59 2018 From: maura.carbone at yale.edu (Carbone, Maura) Date: Fri, 3 Aug 2018 13:05:59 +0000 Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results In-Reply-To: References: Message-ID: <02F0F03E-1F2F-4367-A8A5-A205B0D7267E@yale.edu> Just here to say +1 for ASnake From: on behalf of "Fox, Bobbi" Reply-To: Archivesspace Users Group Date: Friday, August 3, 2018 at 8:12 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results That thought had occurred to me, since I?m already knee deep in ArchiveSnake. :-) From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 2:56 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results That?s actually a really good use case for using the ASpace API. The Finding Aid Title field could be moved (or duplicated) in the Filing Title field with a sleek script! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 11:42 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Mark, Yeah, legacy practice across Harvard was not to use Finding Aid Filing Title, just Finding Aid Title, which was formatted like, ?Last Name, First Name. First Name Last Name papers: Guide.? But thanks for the link, that might help us develop a solution. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Thursday, August 02, 2018 11:00 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Adrien, Right now, the logic for this is the same in the staff interface as it is in the public interface. If the record is a resource, and if that resource record has a Finding Aid Filing Fitle, then the filing title is what?s used for sorting. If there?s no filing title, then the resource title is used (not the finding aid title; and I assume that decision was made when ASpace was created since often the finding aid title proper will have things like ?Guide to the?? or ?Inventory of? etc. at the very beginning). Here?s where that logic happens in the indexer: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L888-L890 I hope that helps (and I hope the bit about the indexer above is correct, but I?m pretty sure that it is). But if you put the title as you want it to be sorted in the ?finding aid filing title? in the staff interface, then you should be all set. For instance, the ?Bradford Edward Ableson Papers? sorts before ?Accelerator Laboratories, Yale University, photographs? in our instance because we have the following recorded in the Finding Aid Filling Title in the staff interface: ?Ableson (Bradford Edward) Papers? Also, I agree that the report that Eve shared looks great!!! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Thursday, 02 August, 2018 10:29 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Hi Eve, Congratulations, this looks great! A question: your collections browse list is alphabetical by something other than the first word of the title that?s listed, creator last name, for instance. What field are you sorting this from? At Harvard, we?re currently browsing collections using the first word of the collection title, which is not ideal. We?d prefer to sort by finding aid title, but I?ve been told this field is not sortable in the core code. Thanks, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Neiger, Eve Sent: Wednesday, August 01, 2018 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Yale Library ASpace PUI Usability Testing Final Report + Results Dear ArchivesSpace User Group Members: The Yale University Library ASpace Public User Interface (PUI) Implementation Team has completed pre-launch usability testing work on our customized PUI, now called Archives at Yale. Over the last year, our team has been preparing for the launch of our ASpace PUI and a move from the Yale Finding Aid Database (YFAD). In order to identify and prioritize needed changes and customizations to the out-of-the-box PUI, we ran two rounds of usability testing. The first round of testing took place in February 2018, followed by an analysis and report. Based on this analysis, we customized our PUI to better match users? mental models, eliminate usability and accessibility issues, and facilitate more accurate searching. During our first round of testing, our Aeon integration for material requesting was not ready so we could not asses usability for requesting at that time. By the time we finished major customizations, the Aeon integration was ready and we ran a second round of testing in June 2018 focused on requesting and the new changes. We compiled the results from both rounds of usability testing in a report (with an addendum for the second round of testing) and are proud to share it with you now. You view a copy of our report here: https://drive.google.com/file/d/1yB8ejKvfSokOMZnWn6k8MjL0CYA6WKkq/view?usp=sharing We?ve also compiled screenshots of our PUI pre-customization for reference: https://drive.google.com/open?id=1lDMTrXSKp4qzujdCzwhu-PzomyL0KAlH And finally, you can see the results of our customizations and the most current version of Archives at Yale (our PUI) here: https://puitestarchivesspace.library.yale.edu/ *Please note, this is a TEST version or our PUI and may not include up-to-date collection information. We are happy to answer any questions you have about our usability testing process, analysis, and results. Feel free to reach out to me at eve.neiger at yale.edu. Best, Eve Neiger, on behalf of the Yale University Library ArchivesSpace Public User Interface Implementation Team, Usability and Accessibility Workgroup Eve Neiger Archivist Beinecke Rare Book and Manuscript Library Yale University 203.432.9027 ? eve.neiger at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Fri Aug 3 09:51:30 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 3 Aug 2018 13:51:30 +0000 Subject: [Archivesspace_Users_Group] Local Access Restrictions - ColdStorageBrbl vs Other Message-ID: Morning, Has anyone customized their list of Local Access Restrictions? Any gotchas? I'm especially curious about anyone using the "Other" category. In the controlled vocab list, I see that the value "ColdStorageBrbl" is translating to "5 - Other". I'd like to avoid confusion down the line - especially since our users do want to have a cold storage specific option. Has anyone addressed this at your repository? Are there any details to watch out for, perhaps for upgrades or current/planned reports? I think we're OK to create new options, and suppress/merge/delete the out-of-box options. We'd need to reassign any current records using 'other', of course, since most are not cold storage. Before we begin, I would love to know how anyone else has addressed this. E.g. Is suppress a better choice than deleting? Or can I safely delete ColdStorageBrbl once and for all (once records are reassigned)? Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Aug 3 11:41:27 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 3 Aug 2018 15:41:27 +0000 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: References: <9c18ff036f8b4f31b4d29d0ca0e55b82@ex13-ell-cr-15.home.ku.edu> Message-ID: <27821EF9-6C03-4CEB-8377-BB0C5F4A6E95@virginia.edu> I agree: the best thing in to change password and remove permissions. Although, I think it would be safe to delete a user who was not an editor/creator of any resources. The last time I tested it, deleting the user unlinked the agent records that would identify who made edits or changes. ( And if that person left UVA, they would also be removed from our LDAP/whois database, which would make connecting a userid to an actual name impossible outside of ArchivesSpace. ) I don?t know if this is already on the list of Staff interface enhancements, but perhaps an active/inactive flag that disabled that users login and access, but kept the entry for tracking would be a good addition. ? Steve. > On Aug 1, 2018, at 6:39 PM, Custer, Mark wrote: > > All, > > It sounds like Noah?s suggestion is a really great one! > > I?d also heed Miloche?s advice about not deleting user records!!! > > Another wrinkle is that whenever you create a user record in ArchivesSpace, a corresponding agent record is created at the same time (those records are also linked, but invisibly essentially, since they?re only linked in the database, and editing one doesn?t change the contents of the other record, of course). Here?s the kicker: let?s say you later update that agent record with an LCCN authority ID, link it up to some descriptive records, etc., then if you delete that user record in the staff interface, then the agent record is also deleted silently, which includes all links to any other records! That?s definitely not what someone would expected (and I just tested to confirm that it?s still true in version 2.4.1). The reverse, thankfully, is not true. If you try to link an agent record that was created because it?s linked to a user record, then you will get an error in the staff interface telling you that you cannot delete that agent record. Although if the interface allowed you to do that, it would be potentially less disastrous than losing an agent record and all of its links. > > Anyhow, the takeaway, in my opinion, is to never stray from Miloche?s advice ? > > Mark > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kottman, Miloche > Sent: Wednesday, 01 August, 2018 12:34 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions > > Christie, > > This behavior may have changed in subsequent releases so you may want to experiment ? Ages ago (somewhere in the version 1.2 ? 1.3 range) we switched to a Shibboleth sign in system which caused pseudo duplicate users when the Shib username was not the same as the one manually created in ASpace. So to fix this I naively deleted the username that was created manually in ASpace. Everything worked fine and dandy until we upgraded to a newer version of ASpace. My IT folks said that this generated a lot of errors and prevented the upgrade until they went in and cleaned up the affected records. ASpace was trying to link information in fields to users who no longer existed, my guess would be the create/modify information. Fortunately for us it was early days of our installation so it was only a handful of records. > > So my advice, don?t delete your user records. > > --Miloche > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Noah Huffman > Sent: Wednesday, August 1, 2018 10:29 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions > > Hi Christie, > > I created a new permissions group called ?Expired Users? (morbid, I know). That group has no permissions in the system. > > When students/interns/staff leave our employ, I assign their user account to that group. This way I can keep a record of their username and other user details. > > To answer your first question, I believe the ?created_by? and ?last_modified_by? fields will still retain usernames even if those users are deleted from the system. > > -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 Michelson, Daniel > Sent: Wednesday, August 1, 2018 11:14 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Questions about user accounts & permissions > > Hi Christie, > > To answer your second question, any system administrators should have the "Edit Groups" button grayed out in the Manage User Access list. > > Dan Michelson > > On Wed, Aug 1, 2018 at 10:55 AM, Larry Weimer > wrote: > Christie, > > When users no longer need access, I've taken two steps: 1) delete their ID from the user group they're in and 2) change the password. That would seem to eliminate their ability to access and act in the system, while retaining a record of them. > > Larry > > Larry Weimer > Head of Archival Processing > New-York Historical Society > > On Wed, Aug 1, 2018 at 10:46 AM, Christie Peterson > wrote: > Hello, > > Is there more detailed documentation somewhere about managing user accounts and permissions? (beyond what is in the user manual) > > Specifically, I need to know: > What happens when a user account is deleted? Does it delete all references to them in the database (that is, every action they've taken)? If so, what is a better alternative to deletion to use when a staff member leaves an organization? > Is there an easy way through the interface to see who currently has system administrator priviledges? > Thanks, > > CP > Christie S. Peterson > Manager of Technical Services for Special Collections > Smith College > cpeterson at smith.edu > she/her/hers > > > > _______________________________________________ > 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: 6091 bytes Desc: not available URL: From sdm7g at virginia.edu Fri Aug 3 12:23:43 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 3 Aug 2018 16:23:43 +0000 Subject: [Archivesspace_Users_Group] Customizing generated citations for archival components In-Reply-To: <3443649aa61f4cfeb73a545d9ff709ec@lib.msu.edu> References: <3443649aa61f4cfeb73a545d9ff709ec@lib.msu.edu> Message-ID: <6E042CC7-865F-43A8-AFCA-B783831569EE@virginia.edu> Just to note that if you don?t want to deal with modifying the default behavior with a plugin, you could also use the API to generate prefercite notes with your desired format, as those have priority over constructing one from the display string. ( url and timestamp are always added to the end of the citation. ) Changing the code is probably the simpler solution, but in some cases it may be more manageable to change the data. ? Steve. > On Jul 30, 2018, at 12:58 PM, Tang, Lydia wrote: > > Hi all, > My repository would like to tweak the data fields and the formatting of the fully generated citations. Does anyone know how to do that? I assume it would be in an en.yml file, but apparently there are three en.yml files and my IT person is not sure where to look. Any help would be greatly appreciated! Full description of our issue below: > > Current behavior on a sample citation: > Brooks, Marshall. Harry Smith, An Appreciation, 1936-2012. The Smith collection, . Michigan State University Libraries Special Collections. http://as.lib.msu.edu/repositories/2/archival_objects/24677 Accessed July 11, 2018. > > A translation of the data fields: > [File title]. [Collection Title], . [Repository]. [Archival Object URI] [Date accessed] > > What we?d like instead is added and bolded: > [Archival Object title], [Instance Information (Box/Folder number)], [Collection title], [Collection identifier (such as MSS 212)], [Repository]. [Archival Object URI] [Date accessed] > Ideally, we'd also like the citation to be formatted with commas instead of periods as well. > Also, what are other ways repositories have editing their en.yml files? We're just getting started in customizing and I wanted to get some ideas. > Thanks all! > Lydia > > Sent from my Verizon, Samsung Galaxy smartphone > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From cpeterson at smith.edu Fri Aug 3 13:00:33 2018 From: cpeterson at smith.edu (Christie Peterson) Date: Fri, 3 Aug 2018 13:00:33 -0400 Subject: [Archivesspace_Users_Group] Questions about user accounts & permissions In-Reply-To: <27821EF9-6C03-4CEB-8377-BB0C5F4A6E95@virginia.edu> References: <9c18ff036f8b4f31b4d29d0ca0e55b82@ex13-ell-cr-15.home.ku.edu> <27821EF9-6C03-4CEB-8377-BB0C5F4A6E95@virginia.edu> Message-ID: Thank you to everyone who responded to my question. This was exactly the information and informed discussion I needed -- as always, it's so great to have colleagues like y'all in the ArchivesSpace community. CP -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Fri Aug 3 15:19:02 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 3 Aug 2018 19:19:02 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Annual Member Forum (Aug 14) - Livestreaming announcement! Message-ID: Dear ArchivesSpace Community, We are looking forward to our annual Member Forum coming up on August 14th! We know travel can be challenging for many of you, so we have set up an option to participate remotely via livestreaming. Please register for access to the livestream at: https://attendee.gototraining.com/r/8278258622427027714 Upon registration, you will receive a confirmation email containing information about how to join the forum remotely. Please note: We will be streaming two rooms simultaneously. * The Ballroom sessions will be livestreamed using GoTo Training -- Registration is required * The South Gallery sessions will be livestreamed using Zoom -- Registration is not required to access the Zoom livestream. Please check the program to help direct you to the appropriate access links. The program also includes the most up to date information. We continue to gather suggestions for the community-wide discussion on the future of ArchivesSpace. Do you have a topic you would like to suggest for this discussion? This can address any interest, concern, feedback, or idea you have with the perspective of the application's future in mind. We would like for this conversation to represent the variety of topics, interests, and concerns that come from all of our users, institutions, and stakeholders. * Please use this form to suggest a discussion topic here. * Facilitators will continue to take suggestions for discussion topics at the forum. Registration for in-person attendance is also currently open! Register at: https://www.eventbrite.com/e/archivesspace-4th-annual-member-forum-tickets-46537118775 We look forward to seeing you at the Member Forum, whether in-person or remotely! Please let me know if you have any questions. Thanks! Best wishes, Christine Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Daniel.Thacker at tamuk.edu Fri Aug 3 17:45:15 2018 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Fri, 3 Aug 2018 21:45:15 +0000 Subject: [Archivesspace_Users_Group] Timeout on merge Message-ID: I am merging a rather large accession into an university group and I am unable to complete my task because of a timeout. I am getting this error message: {"db_error"=>["Database integrity constraint conflict: Java::ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction"]} Is there a way to adjust the timeout limit on MySQL? Thank you Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbutler at cals.org Mon Aug 6 11:44:22 2018 From: dbutler at cals.org (Danielle Butler) Date: Mon, 6 Aug 2018 15:44:22 +0000 Subject: [Archivesspace_Users_Group] Agent Link Date EAD Export Message-ID: Hello all, I have discovered why agent link existence dates don't export when exporting EAD, but I was wondering if anyone has sorted out a workaround for this issue? We are using the EAD 2002 export with container indicators and no DAO tags. The only thing I can think of to do is to add the date to the end of the authority text, either instead of in the existence date fields, or in addition. That doesn't seem ideal, and will probably be time consuming to do, so I thought I'd reach out and see if anyone had found a workaround for the issue before I proceeded with that plan. Thanks, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org 100 Rock Street Little Rock, AR 72201 501-320-5724 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Mon Aug 6 12:06:24 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Mon, 6 Aug 2018 16:06:24 +0000 Subject: [Archivesspace_Users_Group] Agent Link Date EAD Export In-Reply-To: References: Message-ID: Hi Danielle, If you include exist dates in the Dates field of the Name Forms subrecord, those dates should appear in your EAD exports. I believe you can also provide whatever name string you'd like to export in EAD in the Sort Name field. By default the Sort Name value is auto-generated, but you can override the default and type in whatever string you want in Sort Name. Even so, it would be nice if the Dates of Existence were used in auto-generating the Sort Name value... I'm not sure if there is a feature request for this, but I can't find one at first glance. -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Danielle Butler Sent: Monday, August 6, 2018 11:44 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Agent Link Date EAD Export Hello all, I have discovered why agent link existence dates don't export when exporting EAD, but I was wondering if anyone has sorted out a workaround for this issue? We are using the EAD 2002 export with container indicators and no DAO tags. The only thing I can think of to do is to add the date to the end of the authority text, either instead of in the existence date fields, or in addition. That doesn't seem ideal, and will probably be time consuming to do, so I thought I'd reach out and see if anyone had found a workaround for the issue before I proceeded with that plan. Thanks, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org 100 Rock Street Little Rock, AR 72201 501-320-5724 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbutler at cals.org Mon Aug 6 12:52:19 2018 From: dbutler at cals.org (Danielle Butler) Date: Mon, 6 Aug 2018 16:52:19 +0000 Subject: [Archivesspace_Users_Group] Agent Link Date EAD Export In-Reply-To: References: Message-ID: Thank you for the tip to include the date in the Name Form sub-record. That seems to have solved my issue, though that does mean I will still have to do the legwork to move all of that data. But it's a better alternative! Thanks again, Danielle From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman Sent: Monday, August 06, 2018 11:06 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agent Link Date EAD Export Hi Danielle, If you include exist dates in the Dates field of the Name Forms subrecord, those dates should appear in your EAD exports. I believe you can also provide whatever name string you'd like to export in EAD in the Sort Name field. By default the Sort Name value is auto-generated, but you can override the default and type in whatever string you want in Sort Name. Even so, it would be nice if the Dates of Existence were used in auto-generating the Sort Name value... I'm not sure if there is a feature request for this, but I can't find one at first glance. -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Danielle Butler Sent: Monday, August 6, 2018 11:44 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Agent Link Date EAD Export Hello all, I have discovered why agent link existence dates don't export when exporting EAD, but I was wondering if anyone has sorted out a workaround for this issue? We are using the EAD 2002 export with container indicators and no DAO tags. The only thing I can think of to do is to add the date to the end of the authority text, either instead of in the existence date fields, or in addition. That doesn't seem ideal, and will probably be time consuming to do, so I thought I'd reach out and see if anyone had found a workaround for the issue before I proceeded with that plan. Thanks, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org 100 Rock Street Little Rock, AR 72201 501-320-5724 -------------- next part -------------- An HTML attachment was scrubbed... URL: From julie_wetherill at harvard.edu Mon Aug 6 14:45:17 2018 From: julie_wetherill at harvard.edu (Wetherill, Julie M.) Date: Mon, 6 Aug 2018 18:45:17 +0000 Subject: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete Message-ID: Hi Christine, Harvard has experienced the same problem re: unable to re-import after deleting a record. In our case, a resource was deleted and any attempt to re-import produces the error "ref_id : An Archival Object Ref ID must be unique to its resource". The deleted resource is not findable thru search or browse, but we suspect some fragments of it were left behind in the index and preventing the re-import. Has there been any progress on identifying the problem? Thanks. -julie Julie Wetherill Library Technology Services Harvard University -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Aug 8 09:08:45 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 8 Aug 2018 13:08:45 +0000 Subject: [Archivesspace_Users_Group] announcing the ArchivesSpace annual report for 2017/2018 Message-ID: Dear ArchivesSpace members, The ArchivesSpace team is pleased to share this annual report covering the 2017/2018 membership term. This digital document celebrates our community's many activities and accomplishments during the past year and provides some information on what's planned for the future. Thanks to all of our members for all you've done and do to sustain and move the application and the program forward! We encourage you to share the ArchivesSpace annual report with others at your institutions, and anyone else with an interest in ArchivesSpace. We hope that it may be especially helpful in conveying the value of ArchivesSpace, and the value of ArchivesSpace membership, to resource allocators at your institutions. In addition to the attachment to this email, you can find it online at http://archivesspace.org/archives/3127. Thanks to all who contributed ideas, images, and text for the report, and to all of you for the community-centered work that this report represents. We welcome feedback and ideas for future annual reports. Please feel free to email us at ArchivesSpaceHome at lyrasis.org at any point. All best, 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ArchivesSpace-20172018final.pdf Type: application/pdf Size: 7033938 bytes Desc: ArchivesSpace-20172018final.pdf URL: From christine.dibella at lyrasis.org Wed Aug 8 10:15:29 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 8 Aug 2018 14:15:29 +0000 Subject: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete In-Reply-To: References: Message-ID: Hi Julie, Typically this error comes up because something remained in your database after a delete, merge, or transfer - possibly because something happened while one of those was occurring that made the operation not fully complete. In most cases those records become "orphans" since they're no longer attached to anything. To resolve the problem, look in your MySQL database for something with this ref_id - you will have to look directly in the database since it's not coming up via search or browse. - and then do a MySQL update to get rid of that particular problem record from the database. There's some information on queries for locating and getting rid of orphan records in the ticket at https://archivesspace.atlassian.net/browse/ANW-220. Remember that backing up and testing first are really important before doing anything with the database. A plugin is in the works that will make that process a little easier, but especially if it's only a small amount of problem data, there's no need to wait for that to resolve your issue. If you need help with any of this, feel free to contact us directly at ArchivesSpaceHome at lyrasis.org and we'll be glad to put a tech support ticket in for you. 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 Wetherill, Julie M. Sent: Monday, August 6, 2018 2:45 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete Hi Christine, Harvard has experienced the same problem re: unable to re-import after deleting a record. In our case, a resource was deleted and any attempt to re-import produces the error "ref_id : An Archival Object Ref ID must be unique to its resource". The deleted resource is not findable thru search or browse, but we suspect some fragments of it were left behind in the index and preventing the re-import. Has there been any progress on identifying the problem? Thanks. -julie Julie Wetherill Library Technology Services Harvard University -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From john.zarrillo at nyu.edu Wed Aug 8 10:35:14 2018 From: john.zarrillo at nyu.edu (John M Zarrillo) Date: Wed, 8 Aug 2018 10:35:14 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace Documentation Twitter Chat today Message-ID: *Hi all,We are hosting Twitter chat today to discuss issues with ArchiveSpace's documentation today, August 8th from 11am-12pm PDT (2pm-3pm EDT) and 6pm-7pm PDT (9pm-10pm EDT). * *The chat will be hosted by @ArchivesSpace . Please use the hashtag #aspacedoc to tag your questions/comments.* *We look forward to hearing from you!Sincerely,ArchivesSpace Users Advisory Council?s Documentation sub-team* -- John Zarrillo Senior Archivist New York University Archives P: 212-998-2646 https://library.nyu.edu/locations/new-york-university-archives/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From thutchi1 at swarthmore.edu Thu Aug 9 11:34:12 2018 From: thutchi1 at swarthmore.edu (Tom Hutchinson) Date: Thu, 9 Aug 2018 11:34:12 -0400 Subject: [Archivesspace_Users_Group] Java Process High CPU In-Reply-To: <683310B0-68D4-41C1-A762-08478E4DB7DC@library.rochester.edu> References: <683310B0-68D4-41C1-A762-08478E4DB7DC@library.rochester.edu> Message-ID: Hi, Ralph ? We've experienced this issue in the past. Also other issues with related to indices after upgrades. Because of this we don't migrate the old indices when we upgrade. Currently we delete the whole [archivesspace]/data folder and wait for a re-index to finish. Does anyone know if only deleting [archivesspace]/data/indexer_state would have the same effect? It would be nice to use the old indices until the reindex is complete to minimize downtime. Another issue we had causing high resource use had to do with this bug: https://archivesspace.atlassian.net/browse/ANW-137 The band-aid we put on it is to use this plugin weekly: https://github.com/lyrasis/events-deduper Since you turned off indexing (which means changes to the data won't be reflected in search results), maybe it's this. Cheers, Tom On Mon, Jul 23, 2018 at 4:03 PM, Arbelo, Ralph wrote: > Hello, > > > > We recently migrated ArchivesSpace (2.2.2) from SUSE Linux (11 SP4) to > Ubuntu 16.04 for our development server. It has a high CPU usage for Java > all the time, averaging (according to top) over 100% (across two CPUs), > which triggers alerts in VMware. Here?s some of the relevant specs: > > Ubuntu 16.04 64 bit running on VMware > 2 x CPU > 4 GB of RAM > 80 GB disk > > > > It?s running Java 8: > > java version "1.8.0_181" > > Java(TM) SE Runtime Environment (build 1.8.0_181-b13) > > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) > > > > It seems to be constantly indexing, so I temporarily disabled indexing in > config.rb. It didn?t seem to make much of a difference ? Java was still > using over 100% CPU. I used the same config.rb file as the old SUSE dev > server. These are the settings we have enabled in config.rb: > > AppConfig[:db_url] = > "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password= > &useUnicode=true&characterEncoding=UTF-8&serverTimezone=EST" > > AppConfig[:db_max_connections] = 10 > > AppConfig[:backend_url] = "http://localhost:8089" > > AppConfig[:frontend_url] = "http://localhost:8080" > > AppConfig[:public_url] = "http://localhost:8081" > > AppConfig[:backend_log_level] = "warn" > > AppConfig[:plugins] = ['local', 'lcnaf'] > > AppConfig[:mysql_binlog] = false > > AppConfig[:frontend_proxy_url] = proc { AppConfig[:frontend_url] } > > AppConfig[:public_proxy_url] = proc { AppConfig[:public_url] } > > AppConfig[:enable_backend] = true > > AppConfig[:enable_frontend] = true > > AppConfig[:enable_public] = true > > AppConfig[:enable_solr] = true > > AppConfig[:enable_indexer] = true > > AppConfig[:enable_docs] = true > > AppConfig[:report_page_layout] = "letter landscape" > > AppConfig[:report_pdf_font_family] = "\"DejaVu Sans\", sans-serif" > > > > Finally, here are our Java settings in archivesspace.sh: > > ASPACE_JAVA_XMX="-Xmx2048m" > > ASPACE_JAVA_XSS="-Xss2m" > > ASPACE_JAVA_MAXPERMSIZE="-XX:MaxPermSize=256m" > > > > If there?s some settings/troubleshooting I should try, please let me know. I > can also provide some log output. Note there are no errors in the > archviesspace.out log. I do see this warning: > > DEPRECATION WARNING: Sprockets method `register_engine` is deprecated. > > > > Thank you! > > Ralph > > > > Ralph Arbelo - Library IT Services > > River Campus Libraries - University of Rochester > > 121 Rush Rhees Library, Rochester, NY 14627 > > o: 585.275.3449 - m: 585.721.0129 - f: 585.275.1032 > > > > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > From julie_wetherill at harvard.edu Thu Aug 9 12:51:59 2018 From: julie_wetherill at harvard.edu (Wetherill, Julie M.) Date: Thu, 9 Aug 2018 16:51:59 +0000 Subject: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete In-Reply-To: References: Message-ID: Thanks for the info Christine. We'll pursue the database update approach. Regards. --julie -------------- next part -------------- An HTML attachment was scrubbed... URL: From bzhang at csus.edu Thu Aug 9 15:04:30 2018 From: bzhang at csus.edu (Zhang, Bin) Date: Thu, 9 Aug 2018 19:04:30 +0000 Subject: [Archivesspace_Users_Group] Job Posting: Head of Library Information Systems @ Sacramento State Message-ID: Apologize for the cross-posting. --- Bin Zhang Digital Information Services Librarian Library Systems & IT Services, University Library California State University, Sacramento +1 (916) 278-5664 | bzhang at csus.edu From: Conrad, Suzanna Sent: Thursday, August 09, 2018 11:44 AM Subject: Job Posting: Head of Library Information Systems @ Sacramento State The University Library at California State University, Sacramento is hiring for the Head of Library Information Systems As the center of campus intellectual discovery, the Sacramento State University Library promotes teaching, learning, research, and scholarly communication at the University by integrating the Library with campus student success programs and instruction. One of twenty-three libraries in the California State University System, the Library holds over 1.4 million volumes, comprised of print and electronic monographs and serials, and is a Federal Document Depository. The Library's mission is to inspire excellence in teaching, learning, and scholarly activities. The University Library is undergoing rapid transformation with a forward-thinking mission and vision and a deep commitment to improving the campus learning environment. We welcome individuals with diverse backgrounds to join our growing organization of 26 library faculty, 34 staff and approximately 40 FTE student assistants. Duties Responsibilities The Head of Library Information Systems reports to the Associate Dean for Digital Technologies and Resource Management, and serves to provide leadership and direction for innovative services and technologies. The position will define and articulate the vision, strategic directions, and priorities for information technology in a dynamic environment that values creativity, teamwork and innovation. * The Head of Library Information Systems is responsible for the management of the Library Information Systems Department, which includes planning, budgeting, and setting policy for information resources in the University Library. * The Head of Library Information Systems directly supervises staff responsible for desktop support, application development, the Library web sites, supporting digital services, infrastructure architecture and administration, and supports staff in the performance of their duties. * The individual will lead a service-oriented program that researches, develops, and supports advanced information systems for the Library, and ensures excellent operational management of information systems and support of end users. * The Head of Library Information Systems provides leadership in coordinating and defining system requirements and tasks for library-wide projects and initiatives. * The Head of Library Information Systems will work closely with Library Administration, University IT, and other stakeholders to take advantage of technological developments that enhance teaching, learning, research, and scholarship. More information here: https://csus.peopleadmin.com/postings/3321 I'm happy to answer any questions you may have about the position. Suzanna Conrad Associate Dean for Digital Technologies & Resource Management University Library California State University, Sacramento T: (916) 278-5659 | suzanna.conrad at csus.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Aug 10 09:09:02 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 10 Aug 2018 13:09:02 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.5.0 released Message-ID: Hello ArchivesSpace members, The ArchivesSpace team is pleased to announce the availability of v2.5.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.5.0. This release contains many program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. The centerpiece of this release is the refactored reports worked on by our co-op student from Georgia Tech, Sarah Morrissey. Another especially noteworthy improvement is code that has been contributed by Mark Triggs that reduces loading times for records in the staff interface. Our contractor Manny Rodriguez from LibraryHost continues to provide invaluable work to improve our OAI-PMH and export functionality. Other items of note include small updates to the PDF produced from the public interface and the option to use Japanese translations for the interface labels. There are also some bug fixes for the public and staff interfaces and some additional automated tests and infrastructure upgrades. The full list of bug fixes and improvements is included in the release notes. Thanks to community members Mark Triggs, Chris Fitzpatrick, Lora Woodford, Mark Cooper, Dave Mayo, Steve Majewski, knjko, Jacob Brown, and Brian Harrington for their code contributions. We are also very appreciative of all the work our Development Prioritization sub-team, Testing sub-team, and Core Committers Group do in helping prioritize, test, and do code review for issues for this and all of our releases. A special note of gratitude goes to the Reports sub-team for all their long-standing and indefatigable work in helping us improve reports. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to a 2.4.x version, we recommend going directly to 2.5.0, though, depending on the version you are coming from, you should read the special considerations for upgrading from/to different versions that are linked to from the upgrading document first. If you have any questions or need help upgrading, please let us know. 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: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From dbutler at cals.org Fri Aug 10 12:21:22 2018 From: dbutler at cals.org (Danielle Butler) Date: Fri, 10 Aug 2018 16:21:22 +0000 Subject: [Archivesspace_Users_Group] Duplicate Commas Following Description Message-ID: In Archivists' Toolkit before migrating to ASpace, we manually added commas to the end of each description element, so that there would be commas between the description and date elements in our XSL style sheet. When we migrated to ASpace all of the commas are duplicated in display, because ASpace automatically inserts a comma (so nice!). To have cleaner data going forward I would like to remove that comma and just add something to the style sheet to insert the comma at the end of each description element (which is what we likely should have been doing all along anyway). I have never run a script on a dataset, but I imagine that it should be fairly uncomplicated to remove the last character from a particular table using some sort of a script. We are running 2.3.2 on a Windows Server using a MySQL database. Does anyone have any experience doing such a thing and could perhaps provide some guidance? Thank you, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org 100 Rock Street Little Rock, AR 72201 501-320-5724 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Fri Aug 10 15:36:45 2018 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Fri, 10 Aug 2018 19:36:45 +0000 Subject: [Archivesspace_Users_Group] Duplicate Commas Following Description Message-ID: <6BABB58B-78EA-41CF-9045-290105DDECED@harvard.edu> Hi, That?s definitely possible. There are definitely multiple ways to do that, with different risks and benefits. The ones I can think of offhand are: 1. Do that in the MySQL database, then clear out and rebuild ArchivesSpace?s Solr indexes. This would probably be overall fastest, but would mean some downtime, and Solr index rebuilds can take a fair amount of time if your collection is large. 2. Do it via a scripting language and the ArchivesSpace API. In this case, you?d basically write a loop over all your records, download the object, alter the description, and save the object. If you wouldn?t mind talking a little about what your available resources, access (can you directly access MySQL? Can you run Python scripts against the backend? What version of Python can you use? That sort of thing), and available expertise, I might be able to provide more help/advice? -- Dave Mayo ASpace Core Committers Group From: on behalf of Danielle Butler Reply-To: Archivesspace Users Group Date: Friday, August 10, 2018 at 12:21 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Duplicate Commas Following Description In Archivists? Toolkit before migrating to ASpace, we manually added commas to the end of each description element, so that there would be commas between the description and date elements in our XSL style sheet. When we migrated to ASpace all of the commas are duplicated in display, because ASpace automatically inserts a comma (so nice!). To have cleaner data going forward I would like to remove that comma and just add something to the style sheet to insert the comma at the end of each description element (which is what we likely should have been doing all along anyway). I have never run a script on a dataset, but I imagine that it should be fairly uncomplicated to remove the last character from a particular table using some sort of a script. We are running 2.3.2 on a Windows Server using a MySQL database. Does anyone have any experience doing such a thing and could perhaps provide some guidance? Thank you, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org 100 Rock Street Little Rock, AR 72201 501-320-5724 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Aug 10 15:52:41 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 10 Aug 2018 19:52:41 +0000 Subject: [Archivesspace_Users_Group] Duplicate Commas Following Description In-Reply-To: References: Message-ID: We've run into those a few times and found an update to the tables was the way to go. Depending on where those pesky commas are showing up it would be something like this: mysql> UPDATE archival_object -> SET display_string = replace(display_string, ',,', ','), system_mtime = now() where display_string like '%,,%'; mysql> UPDATE archival_object -> SET title = TRIM(TRAILING ',' FROM title), system_mtime = now() where title like '%,'; mysql> UPDATE date -> SET expression = TRIM(TRAILING ',' FROM expression), system_mtime = now() where expression like '%,'; Using either TRIM or REPLACE should do the trick. Dave's idea of using the API is also another option. -Blake ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danielle Butler Sent: Friday, August 10, 2018 12:21:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Duplicate Commas Following Description In Archivists? Toolkit before migrating to ASpace, we manually added commas to the end of each description element, so that there would be commas between the description and date elements in our XSL style sheet. When we migrated to ASpace all of the commas are duplicated in display, because ASpace automatically inserts a comma (so nice!). To have cleaner data going forward I would like to remove that comma and just add something to the style sheet to insert the comma at the end of each description element (which is what we likely should have been doing all along anyway). I have never run a script on a dataset, but I imagine that it should be fairly uncomplicated to remove the last character from a particular table using some sort of a script. We are running 2.3.2 on a Windows Server using a MySQL database. Does anyone have any experience doing such a thing and could perhaps provide some guidance? Thank you, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org 100 Rock Street Little Rock, AR 72201 501-320-5724 From livsolis at utexas.edu Thu Aug 16 10:47:37 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Thu, 16 Aug 2018 09:47:37 -0500 Subject: [Archivesspace_Users_Group] Different subjects with identical labels In-Reply-To: <52F71939-7829-49F7-95B4-F43C2813941C@eservices.virginia.edu> References: <52F71939-7829-49F7-95B4-F43C2813941C@eservices.virginia.edu> Message-ID: Hello all, I wrote to the group a year ago about my ASpace issues using GeoNames as controlled our vocabulary source as we would like to for a number of reasons. The crux of the issue spelled out more verbosely in my original email below is that ASpace will not let me use an identical subject term in the same subject type, as is GeoNames' practice. (e.g. There are 7 towns/cities of Salem in Texas !) Steve Majewski kindly suggested using subdivisions to differentiate the terms, which does allow for me to enter the subjects in ASpace. This is what I was doing but, I am dissatisfied with this solution for a number of reasons. 1. I feel like I can't claim to be using GeoNames in good faith if I change GeoNames' lexical label. 2. It requires more maintenance (deciding and implementing which broader terms to use based on individual geographic location feature types, differentiation needs and updating them as appropriate). One advantage of the URI should be that you can just make an API call to grab a term's current label. Fun fact... Macedonia just changed its name last month! If I had to change "Macedonia" to "North Macedonia" in all terms it appeared in, it adds a lot more work. 3. Sharing Geographic terms between ASpace and our digital repository (separate from ASpace) because a bigger challenge. After talking with our Digital Collections Services team, we've decided to go with taking an approach similar to IMDB: [image: Screen Shot 2018-08-16 at 9.25.00 AM.png] [image: Screen Shot 2018-08-16 at 9.27.02 AM.png] and add a roman numeral suffix surrounded by parens to the end of the geographic term if it repeats. We're still deviating from the GeoNames terms slightly. But "Salem (V)" much less of a deviation from the GeoNames term of "Salem" than "Salem -- Bastrop County -- Texas" plus it communicates to the researcher that they may want to check out all the other Salems in our ASpace instance since there are at least 5. We plan to customize the PUI to display a clickable URI with the term for context. I was wondering if anyone else is using GeoNames or has a similar situation... a controlled vocabulary category you want to use allows for identical terms within a subject type, but ASpace does not. If so, what have some of your solutions been if so? Thanks, Olivia On Wed, Jul 5, 2017 at 8:48 PM Majewski, Steven Dennis (sdm7g) < sdm7g at eservices.virginia.edu> wrote: > I think you need to use Texas or France as subdivisions of the subject. > The scope note is just a note/comment for documentation, and doesn?t > distinguish the two subjects as being different. If you encode it like > this, it will allow both ?Paris ? France? and ?Paris ? Texas? . Will this > work for you ? ? Steve Majewski / UVA > > > > > > > > > > On Jul 5, 2017, at 1:32 PM, Olivia S Solis wrote: > > Hello all, > > I am not sure how many ASpace users out there share the most recent issue > I have encountered migrating data to ArchivesSpace. For a number of > reasons, the Briscoe Center has decided to go with GeoNames as our > canonical controlled vocabulary for subject/geographical terms. This is a > recent adoption and much of the legacy EAD we use goes with Library of > Congress Geographic terms, which we are mapping to GeoNames. We are using > Islandora for our digital repository for item-level description. i.e. We're > using the MODS hierarchicalGeographic > element, > which works well with GeoNames because GeoNames also uses a hierarchical > system to classify its terms. So for individual MODS records for digital > objects you can do something like city: "Paris", country: "France" for one > record vs city: "Paris", state: "Texas" in another. There would be two > instances of "Paris" in our cities taxonomies, distinguished from each > other by their broader terms and associated URIs. There is no > disambiguating information in the labels themselves. The difference between > the cities in records is given by the broader state or country elements > plus URIs. > > That works great for item-level description, but causes a number of > problems for collection level description in ArchivesSpace. > > 1. It appears that ArchivesSpace won't let me create a subject of the > same type (e.g. Geographic) from the same source (e.g. GeoNames) that has a > label identical to another term classified with the same type/source. > 2. Just for the sake of experimentation in our ASpace sandbox, I > identified one of my "Paris" records as a cultural context term. It was > difficult to know the difference between the two when I tried to apply the > subject to a resource record. The autocomplete feature did not include any > disambiguating information (e.g. from the Scope field or the identifier > field in the subject records). The browser headers in the "Browse" subjects > link don't include the Scope note either. > 3. Even if I could create two GeoNames geographical subjects with the > label "Paris", I'm not sure how to communicate to the ASpace end user the > difference between the cities when they are applied to records. I can add > notes in the "Scope" field for each subject record -- "France" and "Texas" > -- to communicate the info, but the scope field for the terms doesn't > appear in e.g. a resource record's linked subject. > 4. Even if we apply the correct label, the human-readable > disambiguating information ("Texas" vs. "France") won't export to our EAD > and our end users might get confused about which Paris we mean, especially > if there happens to be a collection with both the Paris in Texas and the > Paris in France. In such a case would we include the two different "Paris" > subjects plus "France" and "Texas"? Again, this illustrates a difference in > item vs. collection-level description. We publish our EAD via a consortial > regional portal hosted by the University of Texas, TARO, which is how > researchers view our finding aids online. It's possible we'll open up the > public interface, but we're not there yet. > > Has anyone else encountered these problems? I'm sure there is a > solution/numerous possible solutions to the problems above, though it might > mean altering the GeoNames label in ArchivesSpace to include the > disambiguating information. Not exactly kosher if we say we're using > GeoNames terms, but we might have to. We want to use the same controlled > vocabulary terms regardless of system for global consistency, ease of > maintenance etc. I can imagine a kind of customization where our EAD > exporter could grab, e.g. the "Scope" field with the broader term's label > and append it to the label for, in this example "Paris", surrounded by > parentheses. But that presumes we can enter two different > GeoNames/geographical terms "Paris". > > See screen shots with fake data. FYI, we are on ASpace version 1.5.3. > > Thanks, and hopefully I'm not the only one with this problem! > > -Olivia > > -- > Olivia Solis, MSIS > Metadata Coordinator > Dolph Briscoe Center for American History > The University of Texas at Austin > 2300 Red River St. Stop D1100 > Austin TX, 78712-1426 > (512) 232-8013 > 11.32.47 AM.png> 2017-07-05 at 11.42.37 AM.png> > _______________________________________________ > 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 > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-16 at 9.25.00 AM.png Type: image/png Size: 20241 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-16 at 9.27.02 AM.png Type: image/png Size: 73889 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paris.edit.png Type: image/png Size: 328325 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2paris.png Type: image/png Size: 540583 bytes Desc: not available URL: From s.innes at auckland.ac.nz Thu Aug 16 17:08:04 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Thu, 16 Aug 2018 21:08:04 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Message-ID: Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: print-function.png Type: image/png Size: 19748 bytes Desc: print-function.png URL: From blake.carver at lyrasis.org Thu Aug 16 17:59:53 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 16 Aug 2018 21:59:53 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF In-Reply-To: References: Message-ID: Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 From s.innes at auckland.ac.nz Thu Aug 16 19:58:09 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Thu, 16 Aug 2018 23:58:09 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF In-Reply-To: References: Message-ID: <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> Blake, No other errors other than the 422 error returned by the server. General Request URL:https://archives.library.test.auckland.ac.nz/repositories/2/resources/270/pdf Request Method:POST Status Code:422 Unprocessable Entity Remote Address:130.216.14.106:443 Referrer Policy:origin-when-cross-origin We do, however, have a Varnish caching server also running as well. But not sure if this has anything to do with the printing problem. Response Headers Accept-Ranges:bytes Age:0 Connection:keep-alive Content-Length:386 Content-Type:text/html; charset=iso-8859-1 Date:Thu, 16 Aug 2018 23:33:14 GMT Server:Apache/2.4.29 (Unix) Strict-Transport-Security:max-age=31536000 Via:1.1 varnish X-Varnish:542914328 X-Webroute-Cache:MISS X-Webroute-Cache-Reason:Cookie Regards, Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 10:00 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From blake.carver at lyrasis.org Thu Aug 16 20:19:46 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 17 Aug 2018 00:19:46 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF In-Reply-To: <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> References: , <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> Message-ID: "Referrer Policy:origin-when-cross-origin" I think that's it right there. I wish I could remember the details, but I've seen this before, there's something in one of the URLs being served that's breaking the cross origin rules. If I remember right, the counsel did show some errors and one of them had a localhost or something in a URL being served. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 7:58:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, No other errors other than the 422 error returned by the server. General Request URL:https://archives.library.test.auckland.ac.nz/repositories/2/resources/270/pdf Request Method:POST Status Code:422 Unprocessable Entity Remote Address:130.216.14.106:443 Referrer Policy:origin-when-cross-origin We do, however, have a Varnish caching server also running as well. But not sure if this has anything to do with the printing problem. Response Headers Accept-Ranges:bytes Age:0 Connection:keep-alive Content-Length:386 Content-Type:text/html; charset=iso-8859-1 Date:Thu, 16 Aug 2018 23:33:14 GMT Server:Apache/2.4.29 (Unix) Strict-Transport-Security:max-age=31536000 Via:1.1 varnish X-Varnish:542914328 X-Webroute-Cache:MISS X-Webroute-Cache-Reason:Cookie Regards, Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 10:00 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ 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 From s.innes at auckland.ac.nz Thu Aug 16 21:30:31 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Fri, 17 Aug 2018 01:30:31 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF In-Reply-To: References: , <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> Message-ID: Blake, thank you. We tried adding into the NGIX config the following add_header 'Referrer-Policy' 'origin-when-cross-origin'; But this hasn't solved the problem. Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 12:20 PM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF "Referrer Policy:origin-when-cross-origin" I think that's it right there. I wish I could remember the details, but I've seen this before, there's something in one of the URLs being served that's breaking the cross origin rules. If I remember right, the counsel did show some errors and one of them had a localhost or something in a URL being served. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 7:58:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, No other errors other than the 422 error returned by the server. General Request URL:https://archives.library.test.auckland.ac.nz/repositories/2/resources/270/pdf Request Method:POST Status Code:422 Unprocessable Entity Remote Address:130.216.14.106:443 Referrer Policy:origin-when-cross-origin We do, however, have a Varnish caching server also running as well. But not sure if this has anything to do with the printing problem. Response Headers Accept-Ranges:bytes Age:0 Connection:keep-alive Content-Length:386 Content-Type:text/html; charset=iso-8859-1 Date:Thu, 16 Aug 2018 23:33:14 GMT Server:Apache/2.4.29 (Unix) Strict-Transport-Security:max-age=31536000 Via:1.1 varnish X-Varnish:542914328 X-Webroute-Cache:MISS X-Webroute-Cache-Reason:Cookie Regards, Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 10:00 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ 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 From blake.carver at lyrasis.org Thu Aug 16 21:44:42 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 17 Aug 2018 01:44:42 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF In-Reply-To: References: , <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> , Message-ID: Ah, ok, I think I was wrong on that, I just read your error again, and I don't think that was it. Have you tried disabling Varnish? Did you just upgrade to 2.5 and this starting happening? It wasn't happening on 2.4? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 9:30:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, thank you. We tried adding into the NGIX config the following add_header 'Referrer-Policy' 'origin-when-cross-origin'; But this hasn't solved the problem. Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 12:20 PM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF "Referrer Policy:origin-when-cross-origin" I think that's it right there. I wish I could remember the details, but I've seen this before, there's something in one of the URLs being served that's breaking the cross origin rules. If I remember right, the counsel did show some errors and one of them had a localhost or something in a URL being served. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 7:58:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, No other errors other than the 422 error returned by the server. General Request URL:https://archives.library.test.auckland.ac.nz/repositories/2/resources/270/pdf Request Method:POST Status Code:422 Unprocessable Entity Remote Address:130.216.14.106:443 Referrer Policy:origin-when-cross-origin We do, however, have a Varnish caching server also running as well. But not sure if this has anything to do with the printing problem. Response Headers Accept-Ranges:bytes Age:0 Connection:keep-alive Content-Length:386 Content-Type:text/html; charset=iso-8859-1 Date:Thu, 16 Aug 2018 23:33:14 GMT Server:Apache/2.4.29 (Unix) Strict-Transport-Security:max-age=31536000 Via:1.1 varnish X-Varnish:542914328 X-Webroute-Cache:MISS X-Webroute-Cache-Reason:Cookie Regards, Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 10:00 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ 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 From s.innes at auckland.ac.nz Thu Aug 16 22:10:18 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Fri, 17 Aug 2018 02:10:18 +0000 Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF In-Reply-To: References: , <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> , Message-ID: No we haven't tried disabling Varnish - the PDF was printing fine on 2.4.1. -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 1:45 PM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Ah, ok, I think I was wrong on that, I just read your error again, and I don't think that was it. Have you tried disabling Varnish? Did you just upgrade to 2.5 and this starting happening? It wasn't happening on 2.4? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 9:30:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, thank you. We tried adding into the NGIX config the following add_header 'Referrer-Policy' 'origin-when-cross-origin'; But this hasn't solved the problem. Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 12:20 PM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF "Referrer Policy:origin-when-cross-origin" I think that's it right there. I wish I could remember the details, but I've seen this before, there's something in one of the URLs being served that's breaking the cross origin rules. If I remember right, the counsel did show some errors and one of them had a localhost or something in a URL being served. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 7:58:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, No other errors other than the 422 error returned by the server. General Request URL:https://archives.library.test.auckland.ac.nz/repositories/2/resources/270/pdf Request Method:POST Status Code:422 Unprocessable Entity Remote Address:130.216.14.106:443 Referrer Policy:origin-when-cross-origin We do, however, have a Varnish caching server also running as well. But not sure if this has anything to do with the printing problem. Response Headers Accept-Ranges:bytes Age:0 Connection:keep-alive Content-Length:386 Content-Type:text/html; charset=iso-8859-1 Date:Thu, 16 Aug 2018 23:33:14 GMT Server:Apache/2.4.29 (Unix) Strict-Transport-Security:max-age=31536000 Via:1.1 varnish X-Varnish:542914328 X-Webroute-Cache:MISS X-Webroute-Cache-Reason:Cookie Regards, Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 10:00 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ 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 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From s.innes at auckland.ac.nz Thu Aug 16 23:32:23 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Fri, 17 Aug 2018 03:32:23 +0000 Subject: [Archivesspace_Users_Group] FW: Error on v2.5.0 PUI print PDF In-Reply-To: <967B5C35-0CF0-48DC-80FF-E288A91E4632@auckland.ac.nz> References: <9ca93008bf18408ca1ae261d8913f887@uxcn13-tdc-c.UoA.auckland.ac.nz> <967B5C35-0CF0-48DC-80FF-E288A91E4632@auckland.ac.nz> Message-ID: <965314e4ed854b5fab2d3a2769325fdc@uxcn13-tdc-c.UoA.auckland.ac.nz> Dear Colleagues, Our developer has now resolved this issue - thanks Blake for your assistance. "I have found what the issue was and printing is now working. NGINX config for port 8081 required proxy_set_header X-Forwarded-Port $server_port; proxy_set_header X-Forwarded-Ssl on;" Stephen Innes ?On 17/08/18, 2:10 PM, "Stephen Innes" wrote: No we haven't tried disabling Varnish - the PDF was printing fine on 2.4.1. -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 1:45 PM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Ah, ok, I think I was wrong on that, I just read your error again, and I don't think that was it. Have you tried disabling Varnish? Did you just upgrade to 2.5 and this starting happening? It wasn't happening on 2.4? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 9:30:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, thank you. We tried adding into the NGIX config the following add_header 'Referrer-Policy' 'origin-when-cross-origin'; But this hasn't solved the problem. Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 12:20 PM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF "Referrer Policy:origin-when-cross-origin" I think that's it right there. I wish I could remember the details, but I've seen this before, there's something in one of the URLs being served that's breaking the cross origin rules. If I remember right, the counsel did show some errors and one of them had a localhost or something in a URL being served. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 7:58:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Blake, No other errors other than the 422 error returned by the server. General Request URL:https://archives.library.test.auckland.ac.nz/repositories/2/resources/270/pdf Request Method:POST Status Code:422 Unprocessable Entity Remote Address:130.216.14.106:443 Referrer Policy:origin-when-cross-origin We do, however, have a Varnish caching server also running as well. But not sure if this has anything to do with the printing problem. Response Headers Accept-Ranges:bytes Age:0 Connection:keep-alive Content-Length:386 Content-Type:text/html; charset=iso-8859-1 Date:Thu, 16 Aug 2018 23:33:14 GMT Server:Apache/2.4.29 (Unix) Strict-Transport-Security:max-age=31536000 Via:1.1 varnish X-Varnish:542914328 X-Webroute-Cache:MISS X-Webroute-Cache-Reason:Cookie Regards, Stephen Innes -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, 17 August 2018 10:00 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [FORGED] Re: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Do you see any errors in the Chrome Dev Tools Counsel when you hit that page? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Thursday, August 16, 2018 5:08:04 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Error on v2.5.0 PUI print PDF Dear Colleagues, Does anyone have a solution to the problem we have encountered when implementing the AS PUI on a NGINX web server? In the test environment, we receive the attached error message when attempting to print any finding aid in Chrome or Safari browsers, although it works OK in Firefox. Our technical staff have identified the probable cause as our use of NGINX, as opposed to the Apache webserver. In the AS notes https://github.com/archivesspace/tech-docs/blob/master/provisioning/https.md#nginx, there are examples configuring Apache, but there is a ?FIXME Need nginx documentation? note where the Nginx documentation should be. Can someone provide us with the NGINX documentation and especially configurations to fix the printing issue? I am including below an earlier thread related to the issue. Thanks, Stephen Innes (ALIANZA) Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, 17 March 2018 3:29 AM To: Archivesspace Users Group Subject: [FORGED] Re: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) > wrote: Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? and seeing title of this Rails issue: CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. https://github.com/rails/rails/issues/22965 ? Steve M. On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: Thanks. Yes: I?m still seeing the problem. No: no solution so far. The fact that I was only seeing it on production limited my ability to debug. Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. ? Steve. On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: Hi Aspace! I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ 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 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From Matthew.Tallant at tamuk.edu Fri Aug 17 12:17:59 2018 From: Matthew.Tallant at tamuk.edu (Matthew H Tallant) Date: Fri, 17 Aug 2018 16:17:59 +0000 Subject: [Archivesspace_Users_Group] Bulk Changing Top Container Indicator Message-ID: Hello All, We are attempting to change the indicator for top containers by doing a bulk edit. We have several collections that run in excess of a thousand photos and do not want to do it individually. Since there is an operation to bulk update storage location is there a way to do this same procedure for the indicator? Thanks, Matt Tallant Matthew Tallant Processing Archivist South Texas Archives 361-593-3251 matthew.tallant at tamuk.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Mon Aug 20 14:18:21 2018 From: buschedw at msu.edu (Busch, Ed) Date: Mon, 20 Aug 2018 18:18:21 +0000 Subject: [Archivesspace_Users_Group] Manage Repositories: No records found Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB7518@CAD-EX01.campusad.msu.edu> We migrated to ASpace v.2.5.0 (from AT) and Manage Repositories is reporting no records found but I can Select between our two Repositories. I assume both work with the repository table. Anyone seen this before? Everything else seems correct. Thanks! Ed Busch MSU Archives -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Tue Aug 21 11:48:30 2018 From: smithkr at mit.edu (Kari R Smith) Date: Tue, 21 Aug 2018 15:48:30 +0000 Subject: [Archivesspace_Users_Group] ? on how to add Restrictions to archival objects that display at the Container record Message-ID: <29F559819ACA9A4FBF208407D4B63ABB017917F9B2@W92EXPO28.exchange.mit.edu> Hello, I have done this in the past but cannot find information about it in the ArchivesSpace Docs. I want to add a restriction note (with year range) for archival objects (in this case Folders within a Resource record.) My goal is to have this information display when I look up the Container that the items are in. Would someone point me to documentation on this or write out the steps involved? Thanks very much! Kari -------------------------------------------------------------------------- Kari R. Smith Institute Archivist and Program Head, Digital Archives Institute Archives & Special Collections, MIT Libraries Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 IASC office: 617.258.5568 http://libraries.mit.edu/archives/ she | her | hers @karirene69 [smithkr at mit.edu] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcallahan at smith.edu Tue Aug 21 12:02:58 2018 From: mcallahan at smith.edu (Maureen Callahan) Date: Tue, 21 Aug 2018 12:02:58 -0400 Subject: [Archivesspace_Users_Group] ? on how to add Restrictions to archival objects that display at the Container record In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB017917F9B2@W92EXPO28.exchange.mit.edu> References: <29F559819ACA9A4FBF208407D4B63ABB017917F9B2@W92EXPO28.exchange.mit.edu> Message-ID: Hi Kari, A video about how to do exactly what you describe is available here: https://www.youtube.com/watch?v=biCDhkbBSng MC On Tue, Aug 21, 2018 at 11:49 AM Kari R Smith wrote: > Hello, I have done this in the past but cannot find information about it > in the ArchivesSpace Docs. > > > > I want to add a restriction note (with year range) for archival objects > (in this case Folders within a Resource record.) My goal is to have this > information display when I look up the Container that the items are in. > > > > Would someone point me to documentation on this or write out the steps > involved? Thanks very much! > > > > Kari > > > > -------------------------------------------------------------------------- > > Kari R. Smith > > Institute Archivist and Program Head, Digital Archives > > Institute Archives & Special Collections, MIT Libraries > > Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 > > IASC office: 617.258.5568 http://libraries.mit.edu/archives/ > > she | her | hers @karirene69 [smithkr at mit.edu] > > > _______________________________________________ > 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 T. 413 585 2981 C. 215.863.1860 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 . -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Tue Aug 21 12:15:39 2018 From: smithkr at mit.edu (Kari R Smith) Date: Tue, 21 Aug 2018 16:15:39 +0000 Subject: [Archivesspace_Users_Group] ? on how to add Restrictions to archival objects that display at the Container record In-Reply-To: References: <29F559819ACA9A4FBF208407D4B63ABB017917F9B2@W92EXPO28.exchange.mit.edu> Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01791800C7@W92EXPO28.exchange.mit.edu> Maureen, Thank you!! From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Maureen Callahan Sent: Tuesday, August 21, 2018 12:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ? on how to add Restrictions to archival objects that display at the Container record Hi Kari, A video about how to do exactly what you describe is available here: https://www.youtube.com/watch?v=biCDhkbBSng MC On Tue, Aug 21, 2018 at 11:49 AM Kari R Smith > wrote: Hello, I have done this in the past but cannot find information about it in the ArchivesSpace Docs. I want to add a restriction note (with year range) for archival objects (in this case Folders within a Resource record.) My goal is to have this information display when I look up the Container that the items are in. Would someone point me to documentation on this or write out the steps involved? Thanks very much! Kari -------------------------------------------------------------------------- Kari R. Smith Institute Archivist and Program Head, Digital Archives Institute Archives & Special Collections, MIT Libraries Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 IASC office: 617.258.5568 http://libraries.mit.edu/archives/ she | her | hers @karirene69 [smithkr at mit.edu] _______________________________________________ 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 T. 413 585 2981 C. 215.863.1860 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Wed Aug 22 08:50:49 2018 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 22 Aug 2018 12:50:49 +0000 Subject: [Archivesspace_Users_Group] Manage Repositories: No records found Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB8848@CAD-EX01.campusad.msu.edu> I still can't figure this out. I can switch between repositories fine. I created a new test repository and that comes up in the Manage Repositories window but the two real ones do not. We queried the repository table and everything looks fine. I've attached the contents of the repository table. Anyone have an explanation why the two repositories don't show up in the Manage Repositories window? Ed Busch MSU Archives -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: repository_uas_test.txt URL: From djpillen at umich.edu Wed Aug 22 09:05:42 2018 From: djpillen at umich.edu (Dallas Pillen) Date: Wed, 22 Aug 2018 09:05:42 -0400 Subject: [Archivesspace_Users_Group] Manage Repositories: No records found In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB8848@CAD-EX01.campusad.msu.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB8848@CAD-EX01.campusad.msu.edu> Message-ID: Hi Ed, My guess is that the "Manage Repositories" page uses the Solr index for displaying available repositories, not the database, and that there may have been some issue with the repository records indexing during migration. If you haven't yet, I would try triggering a reindex of your UAHC and Gone repos by navigating directly to each of them, http://your-archivesspace-url.edu/repositories/2 and http://your-archivesspace-url.edu/repositories/3, respectively, and editing and saving each repository record. That should cause both repo records to reindex and they should display on the "Manage Repositories" page. Dallas On Wed, Aug 22, 2018 at 8:50 AM, Busch, Ed wrote: > I still can?t figure this out. I can switch between repositories fine. I > created a new test repository and that comes up in the Manage Repositories > window but the two real ones do not. We queried the repository table and > everything looks fine. > > > > I?ve attached the contents of the repository table. Anyone have an > explanation why the two repositories don?t show up in the Manage > Repositories window? > > > > Ed Busch > > MSU Archives > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Dallas Pillen*Archivist for Metadata and Digital Projects Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Aug 22 09:11:16 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 22 Aug 2018 13:11:16 +0000 Subject: [Archivesspace_Users_Group] Manage Repositories: No records found In-Reply-To: References: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB8848@CAD-EX01.campusad.msu.edu>, Message-ID: I think Dallas is probably right, it's most likely that solr has become unhappy. I think it would be best to just force it to recreate everything and see if that fixes things. Stop ArchivesSpace. Empty out EVERYTHING in the /data/ directory. Start ArchivesSpace. Wait for it to reindex. If that doesn't fix it, have a look at your logs, there will likely be some ugly errors there than might help explain what's happening. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Wednesday, August 22, 2018 9:05:42 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Manage Repositories: No records found Hi Ed, My guess is that the "Manage Repositories" page uses the Solr index for displaying available repositories, not the database, and that there may have been some issue with the repository records indexing during migration. If you haven't yet, I would try triggering a reindex of your UAHC and Gone repos by navigating directly to each of them, http://your-archivesspace-url.edu/repositories/2 and http://your-archivesspace-url.edu/repositories/3, respectively, and editing and saving each repository record. That should cause both repo records to reindex and they should display on the "Manage Repositories" page. Dallas On Wed, Aug 22, 2018 at 8:50 AM, Busch, Ed > wrote: I still can?t figure this out. I can switch between repositories fine. I created a new test repository and that comes up in the Manage Repositories window but the two real ones do not. We queried the repository table and everything looks fine. I?ve attached the contents of the repository table. Anyone have an explanation why the two repositories don?t show up in the Manage Repositories window? Ed Busch MSU Archives _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook From christine.dibella at lyrasis.org Wed Aug 22 10:14:23 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 22 Aug 2018 14:14:23 +0000 Subject: [Archivesspace_Users_Group] PUI request button - are you using it? if so, how? Message-ID: Hi all, I've been getting questions here and there about how people are setting up and using the Request functionality in the ArchivesSpace public interface. Since this is more on the individual institution implementation side of things, I'd like to put the question out to the group. Are you using it? Have you customized it at all? Do you link out to a shared organizational email smtp or sendmail server from your ArchivesSpace server or install that functionality on the ArchivesSpace server itself? (And if you're not using the ArchivesSpace request functionality itself, but linking/integrating to something else that performs that function, I'm sure that would be of interest too.) Thanks in advance, 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 buschedw at msu.edu Wed Aug 22 11:47:57 2018 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 22 Aug 2018 15:47:57 +0000 Subject: [Archivesspace_Users_Group] Manage Repositories: No records found In-Reply-To: References: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB8848@CAD-EX01.campusad.msu.edu>, Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164AB89A7@CAD-EX01.campusad.msu.edu> Thanks Dallas and Blake for the suggestion! -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Wednesday, August 22, 2018 9:11 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Manage Repositories: No records found I think Dallas is probably right, it's most likely that solr has become unhappy. I think it would be best to just force it to recreate everything and see if that fixes things. Stop ArchivesSpace. Empty out EVERYTHING in the /data/ directory. Start ArchivesSpace. Wait for it to reindex. If that doesn't fix it, have a look at your logs, there will likely be some ugly errors there than might help explain what's happening. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Wednesday, August 22, 2018 9:05:42 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Manage Repositories: No records found Hi Ed, My guess is that the "Manage Repositories" page uses the Solr index for displaying available repositories, not the database, and that there may have been some issue with the repository records indexing during migration. If you haven't yet, I would try triggering a reindex of your UAHC and Gone repos by navigating directly to each of them, https://urldefense.proofpoint.com/v2/url?u=http-3A__your-2Darchivesspace-2Durl.edu_repositories_2&d=DwIF-g&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=lCOMbrI3q1T4OSR2eOlAqowZQ1eHuGUyGUg5f179X2k&s=UyArI_vHwB6tcAtLhzXaeaEpf53H9H95ThRuebdjTq8&e= and https://urldefense.proofpoint.com/v2/url?u=http-3A__your-2Darchivesspace-2Durl.edu_repositories_3&d=DwIF-g&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=lCOMbrI3q1T4OSR2eOlAqowZQ1eHuGUyGUg5f179X2k&s=00GjnOOXEkp1MqTZeyL_uJiWYythj22Aq-mG0cqRXAg&e=, respectively, and editing and saving each repository record. That should cause both repo records to reindex and they should display on the "Manage Repositories" page. Dallas On Wed, Aug 22, 2018 at 8:50 AM, Busch, Ed > wrote: I still can't figure this out. I can switch between repositories fine. I created a new test repository and that comes up in the Manage Repositories window but the two real ones do not. We queried the repository table and everything looks fine. I've attached the contents of the repository table. Anyone have an explanation why the two repositories don't show up in the Manage Repositories window? Ed Busch MSU Archives _______________________________________________ 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=DwIF-g&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=lCOMbrI3q1T4OSR2eOlAqowZQ1eHuGUyGUg5f179X2k&s=uHzYz_dT34268laUpPUsVnm7NUa6q5uCDHGDdY_voQ4&e= -- Dallas Pillen Archivist for Metadata and Digital Projects [https://urldefense.proofpoint.com/v2/url?u=https-3A__webapps.lsa.umich.edu_dean_lsa-5Femails_bentley-2Dsig-2Dem.png&d=DwIF-g&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=lCOMbrI3q1T4OSR2eOlAqowZQ1eHuGUyGUg5f179X2k&s=F4GjXemfZEBmEUF-3_8ovt-R8naM6eFO60Y3YQg_k9E&e=] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook _______________________________________________ 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=DwIF-g&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=lCOMbrI3q1T4OSR2eOlAqowZQ1eHuGUyGUg5f179X2k&s=uHzYz_dT34268laUpPUsVnm7NUa6q5uCDHGDdY_voQ4&e= From koenigs at newmanu.edu Wed Aug 22 12:15:37 2018 From: koenigs at newmanu.edu (Sue Koenig) Date: Wed, 22 Aug 2018 16:15:37 +0000 Subject: [Archivesspace_Users_Group] transfer data Message-ID: <5098289851544b22bc36a55d727c47b6@newmanu.edu> Hello all, I am a newbie to Archivesspace. Can anyone give me some guidance on how to transfer data from an old 2003 SQL to Archivesspace? Is it possible? If anyone has found some good videos on how to begin using Archivesspace please share with me. I found videos on the archivesspace.org website and am in the process of watching them. Thanks in advance! [Newman University] Sue Koenig Director of Archives Library Office: SH Old Bookstore 316-942-4291, ext. 2467 Connect to Dugan Library [A Degree of Difference] newmanu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22234 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 56721 bytes Desc: image002.png URL: From benn.joseph at northwestern.edu Wed Aug 22 13:51:22 2018 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Wed, 22 Aug 2018 17:51:22 +0000 Subject: [Archivesspace_Users_Group] PUI request button - are you using it? if so, how? Message-ID: We have request functionality turned off in our instance, so the button doesn't show up. But we are planning to somehow integrate that button with Aeon in the future. https://findingaids.library.northwestern.edu/ Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: Wednesday, August 22, 2018 9:14 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] PUI request button - are you using it? if so, how? Hi all, I've been getting questions here and there about how people are setting up and using the Request functionality in the ArchivesSpace public interface. Since this is more on the individual institution implementation side of things, I'd like to put the question out to the group. Are you using it? Have you customized it at all? Do you link out to a shared organizational email smtp or sendmail server from your ArchivesSpace server or install that functionality on the ArchivesSpace server itself? (And if you're not using the ArchivesSpace request functionality itself, but linking/integrating to something else that performs that function, I'm sure that would be of interest too.) Thanks in advance, 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: image001.jpg Type: image/jpeg Size: 4014 bytes Desc: image001.jpg URL: From Kevin.Clair at du.edu Thu Aug 23 13:20:53 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 23 Aug 2018 17:20:53 +0000 Subject: [Archivesspace_Users_Group] PUI request button - are you using it? if so, how? References: Message-ID: Hello, We have our request button configured to send an e-mail to our Special Collections reference desk, from which it?s easier to pipe the requests into our reference tracking system (we use LibAnswers). I?d say for every actual reference question we get through that link, we get another four or five spam e-mails. That may be because we haven?t been actively marketing the PUI to students and researchers yet, so more robots know about the PUI than people. -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Wednesday, August 22, 2018 8:14:23 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] PUI request button - are you using it? if so, how? Hi all, I?ve been getting questions here and there about how people are setting up and using the Request functionality in the ArchivesSpace public interface. Since this is more on the individual institution implementation side of things, I?d like to put the question out to the group. Are you using it? Have you customized it at all? Do you link out to a shared organizational email smtp or sendmail server from your ArchivesSpace server or install that functionality on the ArchivesSpace server itself? (And if you?re not using the ArchivesSpace request functionality itself, but linking/integrating to something else that performs that function, I?m sure that would be of interest too.) Thanks in advance, 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: image001.jpg Type: image/jpeg Size: 6609 bytes Desc: image001.jpg URL: From Henry.Steele at tufts.edu Fri Aug 24 12:49:20 2018 From: Henry.Steele at tufts.edu (Steele, Henry) Date: Fri, 24 Aug 2018 16:49:20 +0000 Subject: [Archivesspace_Users_Group] question about external documents stored locally Message-ID: Digital Archives & Collections at Tufts has a number of external documents that are stored in an institutional network drive. ArchivesSpace has a way to link to documents, and we see this works for documents that are web-accessible through a URL. But for documents in DCA's departmental drive, we don't know how create a file path for these. Obvisouly we would add the file:/// prefix, but I don't see anywhere in ArchivesSpace where you would define the network path for a such a drive. The documentation at https://archivesspace.org/wp-content/uploads/2016/05/ExtDocument-Specification-ReviewedVersion-20111114.pdf indicates that you could use a file path or URI , but I haven't found anything on how. Any help would be much appreciated. Thanks! Henry Steele Systems Librarian Tufts Univerity Library Technology Services (617)627-5239 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Fri Aug 24 14:17:52 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Fri, 24 Aug 2018 18:17:52 +0000 Subject: [Archivesspace_Users_Group] New version of aspace-import-excel Message-ID: This will be of interest to those using the aspace-import-excel plugin, available on GitHub at https://github.com/harvard-library/aspace-import-excel , or those who up to this point have not been able to do so because they were using Excel 2016. V 2.1.11 (https://github.com/harvard-library/aspace-import-excel/releases/tag/v2.1.11 ) no longer errors out with a "[Unknown child node [xr:revisionPtr] for element [workbook]]" error. In addition, thanks to Mark Cooper, the plugin handles proxy-ing correctly. As always, Issues and/or Pull Requests via GitHub are welcome. Have a great weekend! Cheers, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: From smallen at email.gwu.edu Mon Aug 27 16:40:00 2018 From: smallen at email.gwu.edu (Smallen, Vakil) Date: Mon, 27 Aug 2018 16:40:00 -0400 Subject: [Archivesspace_Users_Group] Any Advice for Posting Barcodes to the API? Message-ID: Here at GW we are undertaking a project to add barcodes to top level containers that do not have them or replacing an Aspace generated faux code with a barcode. We plan to use the API for much of this work. Batch editing records through the API is a new project for us, though our department had some limited experience with it. We've pulled reports from ArchivesSpace using the API, and done some very limited posting of content. We have library staff to assists with the Python scripting we plan to use. We're working with Archivesspace version 2.3.2. I would love to hear from folks that have done this already. I've looked at Johns Hopkins script to post barcodes in Github. https://github.com/jhu-archives-and-manuscripts/MARAC_API_Workshop/blob/master/postBarcodes.py I wasn't able to make that one work for me, but I hope with assistance with editing the script I can make it work. Are there other suggestions for places to look for guidance or any advice people can provide from their experiences? -- Vakil Smallen NEA Project Archivist Special Collections Research Center The George Washington University Smallen at email.gwu.edu 202-994-1371 -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Tue Aug 28 18:56:32 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Tue, 28 Aug 2018 17:56:32 -0500 Subject: [Archivesspace_Users_Group] Processing Status vs. Finding Aid Status Message-ID: Hello all, We have just recently gone live with accessions and soon will start creating new resource records in ArchivesSpace. Yay for progress! We're fine-tuning some of our resource records workflows and are realizing we may not have given enough thought to the difference between "Finding Aid Status" and the "Processing Status" field in ArchivesSpace. We've got both in our workflows, but this may be redundant. I can see some immediate distinctions between the two: 1) Processing status is a field shared among resources and accessions in Collections Management; Finding Aid Status is just for resources. Nonetheless, the Collections Management fields cannot be shared between a resource record and accession record. 2) You can create a default report for unprocessed accessions, presumedly dedicated by the processing status field (we've not thoroughly tested reports). 3) A resource record may be undergoing major revisions so the finding aid is under revision, but you may consider the collection already processed. 4) Maybe you've processed a collection but don't have a good publicly accessible finding aid and there for consider it's finding aid to be unprocessed? (This seems dubious to me). We've got a lot of "paper" finding aids accessible in the reading room only. But the collection would still seem processed to me. And this also seems like something you could track with the Assessments module. 5) Conveniently, "Finding Aid Status" is immediately available as a search results column for resources. It's be nice to sort results by that column. Anyway, I was wondering if any of you have decided to use one or the other field to describe the processing state of collections. Do you use those two fields in distinct ways, and if so how? How do you define each for your processors and / or accessioners. FYI, we are using processing status for accessions going forward. We've customized it a bit (for instance including a "Pending" status for accessions not yet arrived so we can document associated events like deed sent.) Thank you! -Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Tue Aug 28 19:36:47 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Tue, 28 Aug 2018 18:36:47 -0500 Subject: [Archivesspace_Users_Group] Processing Status vs. Finding Aid Status In-Reply-To: References: Message-ID: Sorry, left out another point of distinction. 6) An individual accession to a resource record may remain unprocessed, so that accession record's processing status would be "unprocessed", but you would consider the processing status of the resource record as a whole to be perhaps "under revision" if that accession (an accrual to that resource record) were being processed and any resulting revisions to the resource were happening. Anyway, I can see that many of these variables need to be spelled out. Wondering about others' decisions/definitions here. Thanks again... On Tue, Aug 28, 2018 at 5:56 PM Olivia S Solis wrote: > Hello all, > > We have just recently gone live with accessions and soon will start > creating new resource records in ArchivesSpace. Yay for progress! We're > fine-tuning some of our resource records workflows and are realizing we may > not have given enough thought to the difference between "Finding Aid > Status" and the "Processing Status" field in ArchivesSpace. We've got both > in our workflows, but this may be redundant. > > I can see some immediate distinctions between the two: > 1) Processing status is a field shared among resources and accessions in > Collections Management; Finding Aid Status is just for resources. > Nonetheless, the Collections Management fields cannot be shared between a > resource record and accession record. > 2) You can create a default report for unprocessed accessions, presumedly > dedicated by the processing status field (we've not thoroughly tested > reports). > 3) A resource record may be undergoing major revisions so the finding aid > is under revision, but you may consider the collection already processed. > 4) Maybe you've processed a collection but don't have a good publicly > accessible finding aid and there for consider it's finding aid to be > unprocessed? (This seems dubious to me). We've got a lot of "paper" finding > aids accessible in the reading room only. But the collection would still > seem processed to me. And this also seems like something you could track > with the Assessments module. > 5) Conveniently, "Finding Aid Status" is immediately available as a search > results column for resources. It's be nice to sort results by that column. > > Anyway, I was wondering if any of you have decided to use one or the other > field to describe the processing state of collections. Do you use those two > fields in distinct ways, and if so how? How do you define each for your > processors and / or accessioners. > > FYI, we are using processing status for accessions going forward. We've > customized it a bit (for instance including a "Pending" status for > accessions not yet arrived so we can document associated events like deed > sent.) > > Thank you! > > -Olivia > -- > Olivia Solis, MSIS > Metadata Coordinator > Dolph Briscoe Center for American History > The University of Texas at Austin > 2300 Red River St. Stop D1100 > Austin TX, 78712-1426 > (512) 232-8013 > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Wed Aug 29 13:05:23 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 29 Aug 2018 17:05:23 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Implementation Buddies! Message-ID: Dear ArchivesSpace community, At our Annual Member Forum, we announced our idea to facilitate an "implementation buddy" program to help connect our ArchivesSpace community members so we can work through challenges together. We shared our thoughts on how stepping up as a mentor comes with the expectations that may exceed the bandwidth that most of our extremely busy community currently may have. Our vision for "implementation buddies" aims to lift that burden of mentorship while connecting members who can help each other out in balanced harmony. You are welcome to begin submitting your individual interest to be an "implementation buddy" through this Implementation Buddy sign-up sheet. We will regularly circulate this list to individuals who have submitted their interest through this sign-up sheet. We are also offering a webinar on September 26 at 1-1:30pm ET (10-10:30am PT) to provide a background on the ASpace Implementation Buddy program as well as a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form (link to announcement) and the Implementation Buddy sign-up sheet. A formal announcement for the webinar, including webinar viewing link, to follow. If you have any questions, please contact Kim at christine.kim at lyrasis.org. Best wishes, Christine Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Aug 31 10:39:45 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 31 Aug 2018 14:39:45 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - August 2018 Message-ID: [ASpaceOrgHome.jpg] August 2018 Update Thanks to all who participated at the ArchivesSpace Annual Member Forum! We really enjoyed catching up with you and getting some real facetime with our incredible community. In an effort to get to know our community better, we are launching full speed in the effort to compile an ArchivesSpace Member Directory! Read on for more news! Development ArchivesSpace released v2.5.0 on August 10. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.5.0. This release contains many program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. The centerpiece of this release is the refactored reports worked on by our co-op student from Georgia Tech, Sarah Morrissey. Another especially noteworthy improvement is code contributed by Mark Triggs that reduces loading times for records in the staff interface. Our contractor Manny Rodriguez from LibraryHost continues to provide invaluable work to improve our OAI-PMH and export functionality. Other items of note include small updates to the PDF produced from the public interface and the option to use Japanese translations for the interface labels. There are also some bug fixes for the public and staff interfaces and some additional automated tests and infrastructure upgrades. The full list of bug fixes and improvements is included in the release notes. Thanks to community members Mark Triggs, Chris Fitzpatrick, Lora Woodford, Mark Cooper, Dave Mayo, Steve Majewski, knjko, Jacob Brown, and Brian Harrington for their code contributions. We are also very appreciative of all the work our Development Prioritization sub-team, Testing sub-team, and Core Committers Group do in helping prioritize, test, and do code review for issues for this and all of our releases. A special note of gratitude goes to the Reports sub-team for all their long-standing and indefatigable work in helping us improve reports. Our roadmap is in the process of being updated, but we expect to put out our next release in late September. The deadline for community pull requests for that release will be September 21. ArchivesSpace Member Directory We are thrilled to announce our latest effort to provide information on how our community is using ArchivesSpace! We are compiling an ArchivesSpace Member Directory to bring together information about our diverse ArchivesSpace member community and use of the ArchivesSpace application. We hope the compiled directory will help you identify others in similar situations or facing similar challenges to your own as well as provide a way for all of us to better engage each other for questions, ideas, and insights. The information collected will be shared only with ArchivesSpace members. Aside from publicly available information about institutions like names and locations, information about the use of ArchivesSpace will be shared only for those who consent to have it included. The submission form has been sent to each organization's member rep. We will circulate the directory to member organizations as soon as it is available. Please email us at ArchivesSpaceHome at lyrasis.org if you have any questions or if your institution did not receive a link to the submission form. Our hope is to have all of our 350+ member institutions represented in the directory. Webinars Upcoming Webinar: ArchivesSpace Implementation Buddies, September 26, 1-1:30pm ET (10-10:30am PT) At our Annual Member Forum, we announced our idea to facilitate an "implementation buddy" program to help connect our ArchivesSpace community members so we can work through challenges together. We shared our thoughts on how stepping up as a mentor comes with the expectations that may exceed the bandwidth that most of our extremely busy community currently may have. Our vision for "implementation buddies" aims to lift that burden of mentorship while connecting members who can help each other out in balanced harmony. This webinar will provide a background on the ASpace Implementation Buddy program as well as a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form and the Implementation Buddy sign-up sheet. Formal announcement, including webinar viewing link, to follow. If you have any questions, please contact Kim at christine.kim at lyrasis.org. We look forward to seeing you at the webinar! Feedback on Webinars & Ideas for the Future We are interested in hearing your feedback on ArchivesSpace webinars -- What do you enjoy about the webinars? How can we improve them? How does the schedule work for you? These are some of the questions we ask, as well as an opportunity to provide insight into potential themes and topics we should explore in the future. This will be an ongoing survey. Please share your thoughts with us when you have a chance. https://tinyurl.com/aspace-webinarsurvey Annual Member Forum in Washington D.C. Thank you all for joining us for the Annual Member Forum in Washington DC! * Presentation slides and notes: All presentation slides are up on the wiki! https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. * Recordings: Links to the recordings will be announced as soon as they are available. Special thanks to Atlas Systems for providing this service! * Share your notes and photos: Did you take notes or photos during the forum? Please post them in this shared google drive folder: https://goo.gl/8UYh2N * Evaluation: Whether you attended or not, please take a moment to provide your feedback and help us improve our future programs by submitting this survey: https://www.surveymonkey.com/r/K8R7BYS [https://lh6.googleusercontent.com/TbwuS6wNBLYd8rPGkjn0jiDanBrrgmp_oGgga0n1NiNvc6gpZk9HUxRoqYWp9e0BzZr0ssNGEfur3HKadJJmC0lHMnz9fSTDfz4u36E-JWYdrgPrp4Ft0GZew9jjnMAryRT02weX] Regional Forum updates Planning for our next regional forum is underway. Here are some of the most relevant news, dates, and links to keep you up to date on all the activity! Kansas City Regional Forum: Early November in Kansas City, MO * We are looking for volunteers to join a working group to shape the program content for a Kansas City Regional Forum to be tentatively held in early November. Response requested by September 14. Email Kim at christine.kim at lyrasis.org. * Exact date and location will be determined shortly. We plan to hold the regional forum in near vicinity (date and location) of the Kansas City Area Archivists Fall Symposium, which is also to be determined at the moment. If you have any questions (or ideas) related to the regional forums, feel free to email Kim at christine.kim at lyrasis.org. The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. We look forward to having the content shaped by our community. New Stories on the Blog In All About Community (http://archivesspace.org/category/all-about-community), Brittany Newberry (Processing Archivist, Archives Research Center at Atlanta University Center Robert W. Woodruff Library) introduces the Testing sub-team and the work they do before an updated version release can be made available for public use. This is a continuation of a series looking into the various sub-teams of the Technical Advisory Council and User Advisory Council to provide insight into the variety of activities and initiatives undertaken by these groups. In User Insights (http://archivesspace.org/archives/category/user-insights), Kelly Spring (Access Archivist, East Carolina University) launches a series of posts that will provide insight into the migration process at ECU. Follow along throughout their two-year journey! We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Kim at christine.kim at lyrasis.org. Membership Update We are excited to welcome our newest members to our community! Our new members since July 31 include: * Illinois Wesleyan University (Bloomington, IN) * International Institute of Social History (Amsterdam, Netherlands) * National Agricultural Library (Beltsville, MD) * North Dakota State University (Fargo, ND) * San Francisco Museum of Modern Art (San Francisco, CA) * University of Illinois Springfield (Springfield, IL) * Wilkes University (Wilkes-Barre, PA) As of August 31, we have 359 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 20006 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 337888 bytes Desc: image006.png URL: From ltang5 at lib.msu.edu Fri Aug 31 12:12:42 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 31 Aug 2018 16:12:42 +0000 Subject: [Archivesspace_Users_Group] barcodes saga continues... Message-ID: Hi all, I have a wishful dream about barcoded top containers importing and exporting out of our catalog system. Does anyone know of a plugin or tool for enable this to happen? Example scenario: I have a collection with 60+ barcoded containers nicely described in ArchivesSpace. I can easily export the MARC record for the collection, but I just wish that it would also export the item records for the barcoded top containers as well. This way, when I import the MARCXML into my ILS, it also imports the barcoded and attached item records. Ideally in the other direction, if a collection is only described in MARC with attached barcoded item records for each box, that could be imported into ArchivesSpace to create a stub resource record with already created top containers. Is it possible? Has it been built? Thanks, all! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 From abersch at calhist.org Fri Aug 31 20:00:13 2018 From: abersch at calhist.org (Al Bersch) Date: Sat, 1 Sep 2018 00:00:13 +0000 Subject: [Archivesspace_Users_Group] server error when adding sibling Message-ID: Hello, We're having an issue/bug when attempting to add a sibling to a series. Clicking on the "add sibling" button results in the message "An error occurred loading this form. Server error", and a New Archival Object entry that appears to duplicate the files of the above sub-series. When the record is closed, I am unable to open the series, sub-series, or files in that record, getting an error message that says "an error occurred loading this form. Server error." Screenshots are attached. If anyone has any ideas about this, it'd be great to hear! Many thanks, Al Al Bersch, Metadata and Systems Librarian California Historical Society 678 Mission Street, San Francisco, CA 94105 415.357.1848 http://www.californiahistoricalsociety.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sibling_server_error.png Type: image/png Size: 156186 bytes Desc: sibling_server_error.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NewArchivalObject_duplicatefiles.png Type: image/png Size: 162548 bytes Desc: NewArchivalObject_duplicatefiles.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error_loading_this_form.png Type: image/png Size: 160525 bytes Desc: error_loading_this_form.png URL: From blake.carver at lyrasis.org Fri Aug 31 21:04:13 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Sat, 1 Sep 2018 01:04:13 +0000 Subject: [Archivesspace_Users_Group] server error when adding sibling In-Reply-To: References: Message-ID: What version are you running? Can you find that error in the logs? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Al Bersch Sent: Friday, August 31, 2018 8:00:13 PM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] server error when adding sibling Hello, We?re having an issue/bug when attempting to add a sibling to a series. Clicking on the ?add sibling? button results in the message ?An error occurred loading this form. Server error?, and a New Archival Object entry that appears to duplicate the files of the above sub-series. When the record is closed, I am unable to open the series, sub-series, or files in that record, getting an error message that says ?an error occurred loading this form. Server error.? Screenshots are attached. If anyone has any ideas about this, it?d be great to hear! Many thanks, Al Al Bersch, Metadata and Systems Librarian California Historical Society 678 Mission Street, San Francisco, CA 94105 415.357.1848 http://www.californiahistoricalsociety.org/