From k-miller3 at northwestern.edu Thu Nov 1 10:46:44 2018 From: k-miller3 at northwestern.edu (Karen Miller) Date: Thu, 1 Nov 2018 14:46:44 +0000 Subject: [Archivesspace_Users_Group] ASpace testing protocol In-Reply-To: References: Message-ID: <544d409081664b448852177e9c39595b@evcspmbx05.ads.northwestern.edu> Julie, I?ve attached our test plan from NUL after removing some URLs for finding aids in the staff interface. We?ve found it useful to use specific records to test display and editing functionality, and providing the URLs makes it easier to test. Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 On Wed, Oct 31, 2018 at 9:55 AM Wetherill, Julie M. > wrote: Hello ASpacers, I?m developing an ASpace testing protocol for evaluating new releases in our environment. I?ve seen references to a testing protocol in Google sheets used by core ASpace staff. Anyone have a link to that sheet/sheets? Or has your institution developed a test plan that you can share? I?d love not to create ours from scratch! Thanks in advance. ?julie Julie Wetherill Library Technology Services Harvard University _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=tnO8MQ5NNSOuAgXM8qZ2gIM4LOLxIrSIo5m7wzN-wUw&s=J44TVyRWnEVWKIlm_xnKp-mMJSgc7LHwKXtY0dRcutM&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ArchivesSpace Test Plan.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 181989 bytes Desc: ArchivesSpace Test Plan.xlsx URL: From adrien_hilton at harvard.edu Thu Nov 1 11:06:38 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 1 Nov 2018 15:06:38 +0000 Subject: [Archivesspace_Users_Group] Alma Integration In-Reply-To: References: <382DA976-600C-4F7C-9BBF-49C02143E82D@iup.edu> Message-ID: Hi All, Looks like enough interest. Please fill out this Doodle poll with your availability following Thanksgiving for a conference call. https://doodle.com/poll/rdarq6tyapi8i73k If you have thoughts on how to structure the meeting and/or agenda items feel free to send them my way. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Lacher-Feldman, Jessica Sent: Wednesday, October 31, 2018 6:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Alma Integration And the University of Rochester! From: > on behalf of Tara Laver > Reply-To: Archivesspace Users Group > Date: Wednesday, October 31, 2018 at 6:00 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Nelson-Atkins, too. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Wednesday, October 31, 2018 4:52 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration As is USC. Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Beth Kilmarx Sent: Wednesday, October 31, 2018 2:47 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration IUP is definitely interested in the Alma/Aspace intergration Sent from my iPhone On Oct 31, 2018, at 5:40 PM, Zhang, Bin > wrote: We at Sacramento State (part of California State University system) are also interested in integration between ASpace and Alma/Primo. Like Northwestern and others we are considering harvesting EADs directly to Primo, but would like to export collection-level records to Alma? --- 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: > on behalf of "Custer, Mark" > Reply-To: Archivesspace Group > Date: Wednesday, October 31, 2018 at 1:51 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Adrien, Susan, Vernica, and all: Add me to the interested list! ? We are not using Alma right now, but since we will eventually migrate from our current ILS to another one that has a robust API, I?d love to keep up with what other institutions are doing. I?ll also say that my thoughts on the matter so far has been along the same lines of what Leilani and Benn mentioned ? namely, bypassing the ILS, but we still need to get those records to WorldCat, etc. That said, I?ve no clue yet whether we?ll be able to achieve that with our next ILS or not, or whether we?ll continue to try to keep records in synch between ArchivesSpace and an ILS. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ryan Edwards Sent: Wednesday, 31 October, 2018 3:54 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Hello, We, here at the Getty Research Institute are also interested in ArchivesSpace/Alma/Primo integration. We have experimented a bit with the Denver plugin in our Sandbox environment. Currently, we are indexing the full-text of our EADs in Primo. We may also be interested in exploring the interplay between Alma bibliographic/holdings/items records and resource records/instances in ArchivesSpace. Thanks, Ryan Ryan Edwards Digital Access and Systems Librarian Getty Digital ? Collection Management Systems Getty Research Institute 1200 Getty Center Drive, Suite 1100 Los Angeles, CA 90049-1688 reedwards at getty.edu 310.440.7398 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Wednesday, October 31, 2018 6:45 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Hi All, At Houghton Library, part of the Harvard Library, we too are interested in ArchivesSpace/Alma integration. In terms of functionality for resource description, we looked a bit at the Denver plug-in and like the type of data exchange it offers between the ArchivesSpace resource record and the Alma Bib and Holdings records using the MMS ID. We could also envision the exchange working the other way, starting from the Alma record and looking to ArchivesSpace for a resource record with that MMS ID (in a locally specified field), creating a resource if non-existent or updating if existent. We would also like to think through subject and agent access points and keeping those up-to-date in both systems (using URIs), and optimally, up-to-date with the authority file (functionality that Alma currently offers). Lastly, exchanging and maintaining container inventories and barcodes (instances in ArchivesSpace and item records in Alma) across the systems is another area of functionality we?d like to explore. We?d like to host a conference call for interested parties. Can folks respond if they are interested in taking part? If there?s enough momentum, I?ll send around a Doodle poll with some available times. Best wishes, Adrien, Susan, and Vernica Houghton Library From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Chad Mills Sent: Wednesday, October 24, 2018 2:30 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Hi all, Attached is the reference architecture and test/sample implementation architecture we developed at Rutgers. We have not implemented this yet. Best, Chad From: Chad Mills Sent: Friday, October 12, 2018 8:43 AM To: Archivesspace Users Group > Subject: RE: [Archivesspace_Users_Group] Alma Integration Hi, We are interested! At Rutgers earlier this year we developed a reference architecture for our Special Collections. We tested the reference architecture by creating an implementation architecture using Alma, Primo, ArchiveSpace and a generic repository framework. In June we migrated to Alma so we will be looking to integrate ArchiveSpace with Alma in the near future using our the reference architecture as a blue print. I?ll see if I can share that reference architecture with the group. Best, Chad ------------------------------------- Chad Mills Digital Library Architect Rutgers University Libraries Phone: 848.932.5924 Cell: 732.309.8538 ------------------------------------- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Megan Firestone Sent: Wednesday, October 10, 2018 1:34 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Alma Integration Hi, We us Alma as our library ILS here, so we have been looking at the possibility of integrating Alma and ArchivesSpace. I was curious if anyone else is interested in this type of integration and if there is any work being done? Thanks! Megan -- Megan M. Firestone Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu Nov 1 12:50:34 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 1 Nov 2018 16:50:34 +0000 Subject: [Archivesspace_Users_Group] REMINDER: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) In-Reply-To: References: Message-ID: Hi everyone, Just a friendly reminder that we?ll be holding our quarterly open call shortly. Here is a list of submitted topics, but we can of course chat about anything else that comes up! Let?s talk about: * Where are the "how to videos" that were previously available? Ex. How to create an instance. * How are people using reporting? Any tips or tricks? * What are some recommended practices for maintaining the security of your ArchivesSpace staff interface instance? Our institution's staff interface login page is behind a VPN, but I am not sure that everyone knows recommended approaches for maintaining a secure database, especially for small, low-tech shops. Can you help me with: * Synching with Preservica - managing what constitutes an archival object so the ingest process is less time-consuming * Showing an thumbnail image when linking to an external photo. * Advice on project planning, especially as it relates to dealing with legacy metadata or locations. I have an idea! * I would like a webinar on the different resources/documentation on ArchivesSpace. I see the GitHub pages and can be pretty overwhelmed on where to begin or how to utilize what others have created. * Let?s chat about the upcoming ASpace Online Forum coming this Winter 2019. Just want to get a general sense of interest, ideas, comments, feedback. Here are the call in details: * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 * Or iPhone one-tap : * US: +16468769923,,804518729# or +16699006833,,804518729# * Or Telephone? * Dial(for higher quality, dial a number based on your current location)? * US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 * Meeting ID: 804 518 729 * International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC Thanks so much, and look forward to seeing you all soon! Best wishes, Christine Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org On Behalf Of Christine Kim Sent: Tuesday, October 30, 2018 10:41 AM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: Re: [Archivesspace_tac] REMINDER: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) Friendly reminder about our open community call this Thursday, November 1st at 2pm ET (11am PT). Here is a pre-survey to help generate discussion topics prior to the call. Please submit your suggestions by Wednesday, October 31. https://goo.gl/forms/sBnZLgpZJv95LEcx1 Thanks so much, and we?ll see you on Thursday! 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 From: archivesspace_tac-bounces at lyralists.lyrasis.org > On Behalf Of Christine Kim Sent: Wednesday, October 24, 2018 3:08 PM Subject: [Archivesspace_tac] RESCHEDULED: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) Dear ArchivesSpace members, We are rescheduling our Open Community Call due to a scheduling conflict on our end. We apologize for any confusion this causes, but hope you will be able to join us next week on November 1st instead. Please join us for our next community Zoom call on November 1 at 2-3pm ET (11-noon PT). This is an opportunity to hear updates from each other and encourage group discussion. The community call is a space to surface news, ideas, and challenges. This may also be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. You will be able to join by either computer or phone. In an effort to be more organized, here is a pre-survey to help generate discussion topics prior to the call. Please submit your suggestions by Wednesday, October 31. https://goo.gl/forms/sBnZLgpZJv95LEcx1 Here are the details of joining the call: * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 * Or iPhone one-tap : * US: +16468769923,,804518729# or +16699006833,,804518729# * Or Telephone? * Dial(for higher quality, dial a number based on your current location)? * US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 * Meeting ID: 804 518 729 * International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC Please email me at christine.kim at lyrasis.org if you have any questions about the call. Thanks so much, and we look forward to seeing you there! Best wishes, Christine 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 Terry.Brady at georgetown.edu Thu Nov 1 12:52:29 2018 From: Terry.Brady at georgetown.edu (Terry Brady) Date: Thu, 1 Nov 2018 09:52:29 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace Search Result Ordering Message-ID: We are currently running AS 2.2.1. We merged the following change into our instance. This change prioritized search results so that collection objects appeared before other object types. - https://github.com/archivesspace/archivesspace/pull/1002 This change is now a part of the code base. We are in the process of upgrading to AS 2.5.1. I see that this override to solrconfig.xml is present in that release. But, when I run a search in our test 2.5.1 instance, I do not see the expected search result ordering. Can you think of some other change that needs to be made to activate this default sort? Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu Nov 1 15:00:23 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 1 Nov 2018 19:00:23 +0000 Subject: [Archivesspace_Users_Group] REMINDER: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) In-Reply-To: References: Message-ID: Thanks to everyone who participated in today?s open call! The call notes are posted here: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/781385729/2018-11-01+Meeting+notes Best wishes, Christine Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: Christine Kim Sent: Thursday, November 1, 2018 9:51 AM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: RE: REMINDER: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) Hi everyone, Just a friendly reminder that we?ll be holding our quarterly open call shortly. Here is a list of submitted topics, but we can of course chat about anything else that comes up! Let?s talk about: * Where are the "how to videos" that were previously available? Ex. How to create an instance. * How are people using reporting? Any tips or tricks? * What are some recommended practices for maintaining the security of your ArchivesSpace staff interface instance? Our institution's staff interface login page is behind a VPN, but I am not sure that everyone knows recommended approaches for maintaining a secure database, especially for small, low-tech shops. Can you help me with: * Synching with Preservica - managing what constitutes an archival object so the ingest process is less time-consuming * Showing an thumbnail image when linking to an external photo. * Advice on project planning, especially as it relates to dealing with legacy metadata or locations. I have an idea! * I would like a webinar on the different resources/documentation on ArchivesSpace. I see the GitHub pages and can be pretty overwhelmed on where to begin or how to utilize what others have created. * Let?s chat about the upcoming ASpace Online Forum coming this Winter 2019. Just want to get a general sense of interest, ideas, comments, feedback. Here are the call in details: * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 * Or iPhone one-tap : * US: +16468769923,,804518729# or +16699006833,,804518729# * Or Telephone? * Dial(for higher quality, dial a number based on your current location)? * US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 * Meeting ID: 804 518 729 * International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC Thanks so much, and look forward to seeing you all soon! Best wishes, Christine Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org > On Behalf Of Christine Kim Sent: Tuesday, October 30, 2018 10:41 AM To: Archivesspace Users Group >; Archivesspace Member Reps >; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: Re: [Archivesspace_tac] REMINDER: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) Friendly reminder about our open community call this Thursday, November 1st at 2pm ET (11am PT). Here is a pre-survey to help generate discussion topics prior to the call. Please submit your suggestions by Wednesday, October 31. https://goo.gl/forms/sBnZLgpZJv95LEcx1 Thanks so much, and we?ll see you on Thursday! 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 From: archivesspace_tac-bounces at lyralists.lyrasis.org > On Behalf Of Christine Kim Sent: Wednesday, October 24, 2018 3:08 PM Subject: [Archivesspace_tac] RESCHEDULED: ArchivesSpace Open Community Call -- Nov 1st at 2pm ET (11am PT) Dear ArchivesSpace members, We are rescheduling our Open Community Call due to a scheduling conflict on our end. We apologize for any confusion this causes, but hope you will be able to join us next week on November 1st instead. Please join us for our next community Zoom call on November 1 at 2-3pm ET (11-noon PT). This is an opportunity to hear updates from each other and encourage group discussion. The community call is a space to surface news, ideas, and challenges. This may also be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. You will be able to join by either computer or phone. In an effort to be more organized, here is a pre-survey to help generate discussion topics prior to the call. Please submit your suggestions by Wednesday, October 31. https://goo.gl/forms/sBnZLgpZJv95LEcx1 Here are the details of joining the call: * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 * Or iPhone one-tap : * US: +16468769923,,804518729# or +16699006833,,804518729# * Or Telephone? * Dial(for higher quality, dial a number based on your current location)? * US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 * Meeting ID: 804 518 729 * International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC Please email me at christine.kim at lyrasis.org if you have any questions about the call. Thanks so much, and we look forward to seeing you there! Best wishes, Christine 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 koenigs at newmanu.edu Thu Nov 1 15:52:01 2018 From: koenigs at newmanu.edu (Sue Koenig) Date: Thu, 1 Nov 2018 19:52:01 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 In-Reply-To: References: Message-ID: <4d43ccf1b29b4d24bd2742c68995162e@newmanu.edu> Christine, Am I understanding this correctly? Do both parties fill out the attached form no matter which side you are on? I am on the side of need a buddy to mentor me. Do I say yes or no on the below question? I need someone to help me? [cid:image004.png at 01D471F2.71EFEB00] [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 Normal office hours 12:50 ? 4:50, subject to change From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, October 02, 2018 5:37 PM To: Emily Pyers Cc: Archivesspace Member Reps; Archivesspace Users Group; archivesspace_bot_members at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; Archivesspace_uac at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 The webinar has been recorded and is now available! The webinar includes a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form (sent to member reps) and the Implementation Buddy sign-up sheet. Resources from the webinar are now available: http://archivesspace.org/archives/3183. You are welcome to submit your individual interest to be an ?implementation buddy? through this Implementation Buddy sign-up sheet. A digital listing of all interested implementation buddies will be regularly circulated through email to individuals who have submitted their interest through this buddy sign-up sheet. If you have any questions, please contact Christine Kim at christine.kim at lyrasis.org. Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: Emily Pyers > Sent: Tuesday, September 25, 2018 8:18 PM To: Christine Kim > Cc: Archivesspace Member Reps >; Archivesspace Users Group >; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: RE: Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 Hi Kim, I was just wondering if there was any chance the webinar might be recorded and distributed so international users who aren?t able to attend can get some further information on the program? I?m in Melbourne (AEST), and I know there are a couple of other Australian institutions using Aspace who might also be interested. Cheers, Emily Emily Pyers | Metadata & Archival Systems Specialist | Collection Resources In the office Monday, Wednesday - Friday 9.30am-3pm State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 T +61 3 8664 7368 | epyers at slv.vic.gov.au slv.vic.gov.au [Image removed by sender.] [Image removed by sender. follow us] [Image removed by sender. SLV facebook] [Image removed by sender. SLV twitter] [Image removed by sender. SLV youtube] [Image removed by sender. SLV instagram] [Image removed by sender. RACV logo] From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, 25 September 2018 4:50 AM To: Archivesspace Users Group; Archivesspace Member Reps; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: Re: [Archivesspace_member_reps] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 Reminder ? Join us for the ArchivesSpace Implementation Buddies info webinar on Wednesday, September 26! Details: http://archivesspace.org/archives/3175 Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_uac-bounces at lyralists.lyrasis.org > On Behalf Of Christine Kim Sent: Wednesday, September 12, 2018 2:15 PM Subject: [Archivesspace_uac] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 ArchivesSpace Implementation Buddies When: Wednesday, September 26, 2018 Time: 1:00 p.m. ? 1:30 p.m. EST (10:00 a.m. ? 10:30 a.m. PST) Where: Webinar at https://zoom.us/j/834400938 Dial-in only option: 669-900-6833 or 646-876-9923 ? Meeting ID is 834-400-938 International numbers available: https://zoom.us/u/iZNgWlhI No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Please note: We are using Zoom Video Communications to host this webinar, taking a break from Adobe Connect temporarily. If this is your first time using Zoom, please join this Test meeting to make sure you are all set up: https://zoom.us/test Webinar description: 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. We are 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. Please feel free to bring any questions you have. Presenters: Christine Kim (Community Engagement Coordinator, ArchivesSpace) is responsible for facilitating community activities, and is inspired by the incredible projects, initiatives, and accomplishments of the ASpace community. Who should attend: Everyone interested in learning about the ArchivesSpace implementation buddy program, as well as anyone who wants a deeper look at the member directory submission form. Questions? Please contact Kim at christine.kim at lyrasis.org This message and any attachment is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please delete all copies of the message and its attachments and notify the sender immediately. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 823 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 10127 bytes Desc: image004.png URL: From koenigs at newmanu.edu Thu Nov 1 16:03:57 2018 From: koenigs at newmanu.edu (Sue Koenig) Date: Thu, 1 Nov 2018 20:03:57 +0000 Subject: [Archivesspace_Users_Group] Recall: Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 Message-ID: <42e04aae73334b5da57ad49dc9726d64@newmanu.edu> Sue Koenig would like to recall the message, "Webinar Announcement: ArchivesSpace Implementation Buddies - September 26". From Terry.Brady at georgetown.edu Thu Nov 1 16:34:47 2018 From: Terry.Brady at georgetown.edu (Terry Brady) Date: Thu, 1 Nov 2018 13:34:47 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace Search Result Ordering In-Reply-To: References: Message-ID: I believe that we found a fix for this issue. We needed to move the SOLR boost parameters into our config file. https://github.com/Georgetown-University-Libraries/GUArchivesspace/commit/a9143d2d0e21acf95101b39219f879f58e500616 On Thu, Nov 1, 2018 at 9:52 AM Terry Brady wrote: > We are currently running AS 2.2.1. We merged the following change into > our instance. This change prioritized search results so that collection > objects appeared before other object types. > > - https://github.com/archivesspace/archivesspace/pull/1002 > > This change is now a part of the code base. > > We are in the process of upgrading to AS 2.5.1. I see that this override > to solrconfig.xml is present in that release. But, when I run a search in > our test 2.5.1 instance, I do not see the expected search result ordering. > > Can you think of some other change that needs to be made to activate this > default sort? > > Thanks, Terry > > -- > Terry Brady > Applications Programmer Analyst > Georgetown University Library Information Technology > https://github.com/terrywbrady/info > 425-298-5498 (Seattle, WA) > -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Fri Nov 2 15:32:25 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Fri, 2 Nov 2018 19:32:25 +0000 Subject: [Archivesspace_Users_Group] Alma Integration In-Reply-To: References: <382DA976-600C-4F7C-9BBF-49C02143E82D@iup.edu> Message-ID: Hi Everyone, It looks like the day and time that is most convenience for everyone is Wednesday, November 28th at 1pm Eastern. Mark your calendars. We?ll send out the call logistics closer to the meeting. Have a nice weekend. Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Hilton, Adrien Sent: Thursday, November 1, 2018 11:07 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Alma Integration Hi All, Looks like enough interest. Please fill out this Doodle poll with your availability following Thanksgiving for a conference call. https://doodle.com/poll/rdarq6tyapi8i73k If you have thoughts on how to structure the meeting and/or agenda items feel free to send them my way. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Lacher-Feldman, Jessica Sent: Wednesday, October 31, 2018 6:04 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration And the University of Rochester! From: > on behalf of Tara Laver > Reply-To: Archivesspace Users Group > Date: Wednesday, October 31, 2018 at 6:00 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Nelson-Atkins, too. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Wednesday, October 31, 2018 4:52 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration As is USC. Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Beth Kilmarx Sent: Wednesday, October 31, 2018 2:47 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration IUP is definitely interested in the Alma/Aspace intergration Sent from my iPhone On Oct 31, 2018, at 5:40 PM, Zhang, Bin > wrote: We at Sacramento State (part of California State University system) are also interested in integration between ASpace and Alma/Primo. Like Northwestern and others we are considering harvesting EADs directly to Primo, but would like to export collection-level records to Alma? --- 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: > on behalf of "Custer, Mark" > Reply-To: Archivesspace Group > Date: Wednesday, October 31, 2018 at 1:51 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Adrien, Susan, Vernica, and all: Add me to the interested list! ? We are not using Alma right now, but since we will eventually migrate from our current ILS to another one that has a robust API, I?d love to keep up with what other institutions are doing. I?ll also say that my thoughts on the matter so far has been along the same lines of what Leilani and Benn mentioned ? namely, bypassing the ILS, but we still need to get those records to WorldCat, etc. That said, I?ve no clue yet whether we?ll be able to achieve that with our next ILS or not, or whether we?ll continue to try to keep records in synch between ArchivesSpace and an ILS. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ryan Edwards Sent: Wednesday, 31 October, 2018 3:54 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Hello, We, here at the Getty Research Institute are also interested in ArchivesSpace/Alma/Primo integration. We have experimented a bit with the Denver plugin in our Sandbox environment. Currently, we are indexing the full-text of our EADs in Primo. We may also be interested in exploring the interplay between Alma bibliographic/holdings/items records and resource records/instances in ArchivesSpace. Thanks, Ryan Ryan Edwards Digital Access and Systems Librarian Getty Digital ? Collection Management Systems Getty Research Institute 1200 Getty Center Drive, Suite 1100 Los Angeles, CA 90049-1688 reedwards at getty.edu 310.440.7398 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Wednesday, October 31, 2018 6:45 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Hi All, At Houghton Library, part of the Harvard Library, we too are interested in ArchivesSpace/Alma integration. In terms of functionality for resource description, we looked a bit at the Denver plug-in and like the type of data exchange it offers between the ArchivesSpace resource record and the Alma Bib and Holdings records using the MMS ID. We could also envision the exchange working the other way, starting from the Alma record and looking to ArchivesSpace for a resource record with that MMS ID (in a locally specified field), creating a resource if non-existent or updating if existent. We would also like to think through subject and agent access points and keeping those up-to-date in both systems (using URIs), and optimally, up-to-date with the authority file (functionality that Alma currently offers). Lastly, exchanging and maintaining container inventories and barcodes (instances in ArchivesSpace and item records in Alma) across the systems is another area of functionality we?d like to explore. We?d like to host a conference call for interested parties. Can folks respond if they are interested in taking part? If there?s enough momentum, I?ll send around a Doodle poll with some available times. Best wishes, Adrien, Susan, and Vernica Houghton Library From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Chad Mills Sent: Wednesday, October 24, 2018 2:30 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Alma Integration Hi all, Attached is the reference architecture and test/sample implementation architecture we developed at Rutgers. We have not implemented this yet. Best, Chad From: Chad Mills Sent: Friday, October 12, 2018 8:43 AM To: Archivesspace Users Group > Subject: RE: [Archivesspace_Users_Group] Alma Integration Hi, We are interested! At Rutgers earlier this year we developed a reference architecture for our Special Collections. We tested the reference architecture by creating an implementation architecture using Alma, Primo, ArchiveSpace and a generic repository framework. In June we migrated to Alma so we will be looking to integrate ArchiveSpace with Alma in the near future using our the reference architecture as a blue print. I?ll see if I can share that reference architecture with the group. Best, Chad ------------------------------------- Chad Mills Digital Library Architect Rutgers University Libraries Phone: 848.932.5924 Cell: 732.309.8538 ------------------------------------- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Megan Firestone Sent: Wednesday, October 10, 2018 1:34 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Alma Integration Hi, We us Alma as our library ILS here, so we have been looking at the possibility of integrating Alma and ArchivesSpace. I was curious if anyone else is interested in this type of integration and if there is any work being done? Thanks! Megan -- Megan M. Firestone Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 _______________________________________________ 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 belaira at union.edu Fri Nov 2 15:35:11 2018 From: belaira at union.edu (Belair, Andrea) Date: Fri, 2 Nov 2018 15:35:11 -0400 Subject: [Archivesspace_Users_Group] editing/adding series Message-ID: Hello, I created a record and inputted via rapidentry at file level, and I'd like to go back and add a column or hierarchical level to indicate series. Is there a way to do this? I am not able to find it in my manual. Thank you so much, Andrea -- Andrea Belair Archives and Special Collections Librarian Union College 807 Union Street Schenectady, NY 12308 518-388-6871 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Adrienne.Pruitt at tufts.edu Mon Nov 5 11:00:46 2018 From: Adrienne.Pruitt at tufts.edu (Pruitt, Adrienne) Date: Mon, 5 Nov 2018 16:00:46 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers Message-ID: Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Mon Nov 5 14:17:04 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Mon, 5 Nov 2018 14:17:04 -0500 Subject: [Archivesspace_Users_Group] editing/adding series In-Reply-To: References: Message-ID: Andrea, If you're looking to declare the level of hierarchy in the RDE, you can do so via the Level of Description column, which has a drop-down for Series, Subseries, File, etc. If you're looking to add hierarchy to the RDE (e.g. a row for a series, then rows for subseries/files under it), that's unfortunately impossible via the RDE. The RDE can only create components at one level at a time, so there's no way to create a series-level component and its children within a single RDE session. There are methods to create many components within a series via RDE (such as starting the RDE session from the series-level component), but there's no way to do so all within one single session. Hope this helps, --Alex On Fri, Nov 2, 2018 at 3:35 PM, Belair, Andrea wrote: > Hello, > I created a record and inputted via rapidentry at file level, and I'd like > to go back and add a column or hierarchical level to indicate series. Is > there a way to do this? I am not able to find it in my manual. > Thank you so much, > Andrea > > -- > Andrea Belair > Archives and Special Collections Librarian > Union College > 807 Union Street > Schenectady, NY 12308 > 518-388-6871 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From belaira at union.edu Mon Nov 5 14:38:24 2018 From: belaira at union.edu (Belair, Andrea) Date: Mon, 5 Nov 2018 14:38:24 -0500 Subject: [Archivesspace_Users_Group] editing/adding series In-Reply-To: References: Message-ID: Thank you so much, Alex. This is extremely helpful! Best, Andrea On Mon, Nov 5, 2018 at 2:17 PM Alexander Duryee wrote: > Andrea, > > If you're looking to declare the level of hierarchy in the RDE, you can do > so via the Level of Description column, which has a drop-down for Series, > Subseries, File, etc. > > If you're looking to add hierarchy to the RDE (e.g. a row for a series, > then rows for subseries/files under it), that's unfortunately impossible > via the RDE. The RDE can only create components at one level at a time, so > there's no way to create a series-level component and its children within a > single RDE session. There are methods to create many components within a > series via RDE (such as starting the RDE session from the series-level > component), but there's no way to do so all within one single session. > > Hope this helps, > --Alex > > > On Fri, Nov 2, 2018 at 3:35 PM, Belair, Andrea wrote: > >> Hello, >> I created a record and inputted via rapidentry at file level, and I'd >> like to go back and add a column or hierarchical level to indicate series. >> Is there a way to do this? I am not able to find it in my manual. >> Thank you so much, >> Andrea >> >> -- >> Andrea Belair >> Archives and Special Collections Librarian >> Union College >> 807 Union Street >> Schenectady, NY 12308 >> 518-388-6871 >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderduryee at nypl.org > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Andrea Belair Archives and Special Collections Librarian Union College 807 Union Street Schenectady, NY 12308 518-388-6871 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Mon Nov 5 14:48:21 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 5 Nov 2018 19:48:21 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers Message-ID: <1061D033-9B9E-4F39-9497-6946BB6E63D6@lib.msu.edu> Thanks for bringing this up, Adrienne! Would you (and others) be willing to share your perspective on the following tickets? https://archivesspace.atlassian.net/browse/ANW-770 https://archivesspace.atlassian.net/browse/ANW-780 I think it would be helpful to hear about the diverse approaches to how CUIs are being used. Ideally, it may also be helpful to upload a sample EAD file to the sandbox (http://test.archivesspace.org/staff/) for developers to ?play? with - it would be great to have at least one representative from an institution that has the specific series and box numbering issue, as well as yours. Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Pruitt, Adrienne" Reply-To: Archivesspace Users Group Date: Monday, November 5, 2018 at 11:01 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Component unique identifiers Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 From mayoc at bc.edu Mon Nov 5 14:53:46 2018 From: mayoc at bc.edu (Chris Mayo) Date: Mon, 5 Nov 2018 14:53:46 -0500 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: Hi Adrienne, We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs in Aspace were much too long for our needs. What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now. Hope that helps! Best, Chris On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne wrote: > Hello, all, > > We?re hoping to move away from semantically meaningful component unique > identifiers, but need some way to be able to easily auto-generate a unique > identifier that could be used for file-naming purposes in digitization > projects. Working with legacy data, we have seen that there can be value in > being able to easily associate a binary file floating around on a server > somewhere with a relatively easily parsed identifier that links it to its > related metadata. However, semantically meaningful identifiers based on > collection structure are a rather brittle system prone to breaking when > collections are rearranged or reprocessed and easy to mis-enter when > working with so many digits. We?re interested to hear how others are > handling their identifiers (particularly in regards to digitization > workflows.) > > Thank you! > > *Adrienne Pruitt *| Collections Management Archivist > Digital Collections and Archives > Tufts University > adrienne.pruitt at tufts.edu |617-627-0957 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Chris Mayo Digital Production Librarian Thomas P. O'Neill, Jr. Library Boston College chris.mayo at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.searcy at nyu.edu Tue Nov 6 09:37:30 2018 From: rachel.searcy at nyu.edu (Rachel Aileen Searcy) Date: Tue, 6 Nov 2018 09:37:30 -0500 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: Hi Adrienne, We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (here on github ). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides here , as well as instructions in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions. Best, Rachel On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo wrote: > Hi Adrienne, > > We ran into a similar issue at Boston College when we migrated from to > ASpace from Toolkit. Our practice had been to combine the collection ID > with an auto-generated refID to create component unique identifiers, but > the auto-generated refIDs in Aspace were much too long for our needs. > > What we eventually wound up doing is using the database primary key for a > given archival object as the unique part of its component unique ID, so > that any given for an archival object we're planning to digitize gets a CUI > with the format of 'mmsID_NNNNN" where the numerical portion is pulled from > the 'archival_object_NNNNN' at the end of the archival object's URL. The > really handy part of this is that it lets us parse our CUIs to make API > calls. It's also robust to rearrangement, if you are only moving the > archival object around within the collection hierarchy - the database key > remains the same. It doesn't survive reprocessing, however, if you are > deleting/rebuilding/combining archival objects, so we always make sure to > begin the process of digitization after a collection has been processed or > reprocessed. It makes the CUIs somewhat semantically meaningful - but only > if you know what you are looking at. We're still not sure how we feel about > that, but it's what works for us for now. > > Hope that helps! > Best, > Chris > > On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne < > Adrienne.Pruitt at tufts.edu> wrote: > >> Hello, all, >> >> We?re hoping to move away from semantically meaningful component unique >> identifiers, but need some way to be able to easily auto-generate a unique >> identifier that could be used for file-naming purposes in digitization >> projects. Working with legacy data, we have seen that there can be value in >> being able to easily associate a binary file floating around on a server >> somewhere with a relatively easily parsed identifier that links it to its >> related metadata. However, semantically meaningful identifiers based on >> collection structure are a rather brittle system prone to breaking when >> collections are rearranged or reprocessed and easy to mis-enter when >> working with so many digits. We?re interested to hear how others are >> handling their identifiers (particularly in regards to digitization >> workflows.) >> >> Thank you! >> >> *Adrienne Pruitt *| Collections Management Archivist >> Digital Collections and Archives >> Tufts University >> adrienne.pruitt at tufts.edu |617-627-0957 >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Chris Mayo > Digital Production Librarian > Thomas P. O'Neill, Jr. Library > Boston College > chris.mayo at bc.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e= > -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahueb2 at uis.edu Tue Nov 6 09:38:47 2018 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Tue, 6 Nov 2018 14:38:47 +0000 Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute Message-ID: Good morning everyone, In my attempts to secure our installation of ArchivesSpace, I've run into an issue setting the "Set-Cookie" attribute through Apache. I'm currently routing ArchiveSpace through Apache for SSL as dictated in the HTTPS readme file, but it appears that ArchivesSpace only sees the http connection and does not set the Secure attribute. I've attempted to force the attribute to set with Apache but none of the settings changes seem to work when it comes to set-cookie (other attributes do change when set in Apache). Is there a way to force this attribute to be set properly? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Tue Nov 6 10:53:04 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Tue, 6 Nov 2018 15:53:04 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: Hi all, Just a +1 for the NYU Digitization Work Order plugin. We make use of that plugin at Duke in our digitization workflow, although instead of adding component unique identifiers we just use the Ref ID field as the key that unites our digital object metadata (stored in Fedora) with ASpace. For the most part, we have abandoned semantic filenames so that we can accommodate existing filenames for born-digital materials and filenames that may have been generated by other units on campus that we might not control. We created a service in our repository that can post (in batch) very basic digital object records to ArchivesSpace and then link those digital objects to existing archival objects using the ASpace ref_ID values stored in our repository. Then, we can publish finding aids that include links to digital objects in our repository and well as embedded image, audio, and video files. Happy to explain more if folks are interested, -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 Rachel Aileen Searcy Sent: Tuesday, November 6, 2018 9:38 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Hi Adrienne, We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (here on github). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides here, as well as instructions in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions. Best, Rachel On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo > wrote: Hi Adrienne, We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs in Aspace were much too long for our needs. What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now. Hope that helps! Best, Chris On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne > wrote: Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Thomas P. O'Neill, Jr. Library Boston College chris.mayo at bc.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Tue Nov 6 10:59:28 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Tue, 6 Nov 2018 15:59:28 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: Wow, this is super helpful. We?ve been noodling on a similar use case. All our existing repository projects leverage our MARC 035 field ids (Voyager ILS-supplied) to mint ids/Fedora PIDs, but now we?re embarking on ASpace projects that don?t always have a Voyager record, or have ID minting practices from other external systems that we can?t replicate in ASpace - or maybe don?t want to. We?re still struggling with what the ID should actually be ? we?re wary of using internally-generated IDs. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: Rachel Aileen Searcy Sent: Tuesday, November 06, 2018 9:38 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Hi Adrienne, We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (here on github). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides here, as well as instructions in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions. Best, Rachel On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo > wrote: Hi Adrienne, We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs in Aspace were much too long for our needs. What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now. Hope that helps! Best, Chris On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne > wrote: Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Thomas P. O'Neill, Jr. Library Boston College chris.mayo at bc.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Tue Nov 6 11:09:31 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Tue, 6 Nov 2018 16:09:31 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: John?s message reminded me that at Duke, our repository items have externally-minted and persistent ARKs. When we created digital object records in ASpace based on our repository objects using the service I described previously, we store those ARKs in the digital object identifier field in ArchivesSpace. So, basically we have two identifiers that connect records in ArchivesSpace with records in our repository (the refID and the ARK). In our shop, the refID is really useful for starting and facilitating the digitization workflow, but the ARK is more stable. I?m still not sure we have the most elegant setup and there are a lot of identifiers floating around, but it seems to be working for us so far? -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Rees, John (NIH/NLM) [E] Sent: Tuesday, November 6, 2018 10:59 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Wow, this is super helpful. We?ve been noodling on a similar use case. All our existing repository projects leverage our MARC 035 field ids (Voyager ILS-supplied) to mint ids/Fedora PIDs, but now we?re embarking on ASpace projects that don?t always have a Voyager record, or have ID minting practices from other external systems that we can?t replicate in ASpace - or maybe don?t want to. We?re still struggling with what the ID should actually be ? we?re wary of using internally-generated IDs. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: Rachel Aileen Searcy > Sent: Tuesday, November 06, 2018 9:38 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Hi Adrienne, We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (here on github). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides here, as well as instructions in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions. Best, Rachel On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo > wrote: Hi Adrienne, We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs in Aspace were much too long for our needs. What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now. Hope that helps! Best, Chris On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne > wrote: Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Thomas P. O'Neill, Jr. Library Boston College chris.mayo at bc.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Adrienne.Pruitt at tufts.edu Tue Nov 6 11:22:03 2018 From: Adrienne.Pruitt at tufts.edu (Pruitt, Adrienne) Date: Tue, 6 Nov 2018 16:22:03 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: Thanks for all of your very helpful responses, everybody! We have been investigating use of the digitization plug-in, which looks great. However, our digitization workflow (especially digitization on demand) usually involves items that don?t have pre-existing metadata, which makes it less suitable at the moment, since our display system requires item-level metadata. As we move into a system that can handle complex objects, and also try out the PUI, it sounds like there are a couple of solutions here that might work for us. We will probably be contacting some of you with further questions ? thanks again! -Adrienne From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman Sent: 6 November 2018 11:10 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component unique identifiers John?s message reminded me that at Duke, our repository items have externally-minted and persistent ARKs. When we created digital object records in ASpace based on our repository objects using the service I described previously, we store those ARKs in the digital object identifier field in ArchivesSpace. So, basically we have two identifiers that connect records in ArchivesSpace with records in our repository (the refID and the ARK). In our shop, the refID is really useful for starting and facilitating the digitization workflow, but the ARK is more stable. I?m still not sure we have the most elegant setup and there are a lot of identifiers floating around, but it seems to be working for us so far? -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Rees, John (NIH/NLM) [E] Sent: Tuesday, November 6, 2018 10:59 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Wow, this is super helpful. We?ve been noodling on a similar use case. All our existing repository projects leverage our MARC 035 field ids (Voyager ILS-supplied) to mint ids/Fedora PIDs, but now we?re embarking on ASpace projects that don?t always have a Voyager record, or have ID minting practices from other external systems that we can?t replicate in ASpace - or maybe don?t want to. We?re still struggling with what the ID should actually be ? we?re wary of using internally-generated IDs. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: Rachel Aileen Searcy > Sent: Tuesday, November 06, 2018 9:38 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Hi Adrienne, We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (here on github). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides here, as well as instructions in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions. Best, Rachel On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo > wrote: Hi Adrienne, We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs in Aspace were much too long for our needs. What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now. Hope that helps! Best, Chris On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne > wrote: Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Thomas P. O'Neill, Jr. Library Boston College chris.mayo at bc.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From harnold at rockarch.org Tue Nov 6 13:02:13 2018 From: harnold at rockarch.org (Arnold, Hillel) Date: Tue, 6 Nov 2018 18:02:13 +0000 Subject: [Archivesspace_Users_Group] Component unique identifiers In-Reply-To: References: Message-ID: <20F89298-A087-4582-9BE2-3AC6FAF8528E@rockarch.org> We also tend to use refIDs for digitization. We?ve tried to look at their length and semantic meaninglessness as an advantage, and an opportunity to examine our workflows for places where colleagues are doing a lot of manual data entry, and to replace those points with API calls or some other form of automation that doesn?t force folks to do a lot of copying and pasting. The `find_by_id` endpoint is super useful for this. Another option are ArchivesSpace?s external IDs. You can save as many as you want and, more importantly, you can specify where the identifier comes from, which can be super useful if you have an environment where there are multiple identifier sets which get used for specific things. Although these aren?t visible in the UI by default, it looks like you can turn them on in the config.rb file: https://archivesspace.github.io/archivesspace/user/configuring-archivesspace/ I?m not sure if these get exported in EAD or anything, but thought I?d throw that out there as an option. Hillel From: on behalf of "Pruitt, Adrienne" Reply-To: Archivesspace Users Group Date: Tuesday, November 6, 2018 at 11:22 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Thanks for all of your very helpful responses, everybody! We have been investigating use of the digitization plug-in, which looks great. However, our digitization workflow (especially digitization on demand) usually involves items that don?t have pre-existing metadata, which makes it less suitable at the moment, since our display system requires item-level metadata. As we move into a system that can handle complex objects, and also try out the PUI, it sounds like there are a couple of solutions here that might work for us. We will probably be contacting some of you with further questions ? thanks again! -Adrienne From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman Sent: 6 November 2018 11:10 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component unique identifiers John?s message reminded me that at Duke, our repository items have externally-minted and persistent ARKs. When we created digital object records in ASpace based on our repository objects using the service I described previously, we store those ARKs in the digital object identifier field in ArchivesSpace. So, basically we have two identifiers that connect records in ArchivesSpace with records in our repository (the refID and the ARK). In our shop, the refID is really useful for starting and facilitating the digitization workflow, but the ARK is more stable. I?m still not sure we have the most elegant setup and there are a lot of identifiers floating around, but it seems to be working for us so far? -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Rees, John (NIH/NLM) [E] Sent: Tuesday, November 6, 2018 10:59 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Wow, this is super helpful. We?ve been noodling on a similar use case. All our existing repository projects leverage our MARC 035 field ids (Voyager ILS-supplied) to mint ids/Fedora PIDs, but now we?re embarking on ASpace projects that don?t always have a Voyager record, or have ID minting practices from other external systems that we can?t replicate in ASpace - or maybe don?t want to. We?re still struggling with what the ID should actually be ? we?re wary of using internally-generated IDs. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: Rachel Aileen Searcy > Sent: Tuesday, November 06, 2018 9:38 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component unique identifiers Hi Adrienne, We had a similar issue here at NYU. Previous digitization projects relied on the shorter Archivist's Toolkit refids for file naming, but this became untenable with those created by ArchivesSpace. We didn't want to change our inter-departmental workflows too radically, so we contracted with HM to develop a plugin called the Digitization Work Order plugin (here on github). This plugin allows the user to select individual components from a resource record (including all if desired), which are then assigned sequential component unique identifiers that can be used for file naming or other purposes. The plugin also produces a csv of descriptive information of those components, and automatically inserts this newly created identifier into the components Component Unique Identifier field. We have some demo slides here, as well as instructions in our local ArchivesSpace manual. I'd also be happy to talk further to answer any questions. Best, Rachel On Mon, Nov 5, 2018 at 2:54 PM Chris Mayo > wrote: Hi Adrienne, We ran into a similar issue at Boston College when we migrated from to ASpace from Toolkit. Our practice had been to combine the collection ID with an auto-generated refID to create component unique identifiers, but the auto-generated refIDs in Aspace were much too long for our needs. What we eventually wound up doing is using the database primary key for a given archival object as the unique part of its component unique ID, so that any given for an archival object we're planning to digitize gets a CUI with the format of 'mmsID_NNNNN" where the numerical portion is pulled from the 'archival_object_NNNNN' at the end of the archival object's URL. The really handy part of this is that it lets us parse our CUIs to make API calls. It's also robust to rearrangement, if you are only moving the archival object around within the collection hierarchy - the database key remains the same. It doesn't survive reprocessing, however, if you are deleting/rebuilding/combining archival objects, so we always make sure to begin the process of digitization after a collection has been processed or reprocessed. It makes the CUIs somewhat semantically meaningful - but only if you know what you are looking at. We're still not sure how we feel about that, but it's what works for us for now. Hope that helps! Best, Chris On Mon, Nov 5, 2018 at 11:00 AM Pruitt, Adrienne > wrote: Hello, all, We?re hoping to move away from semantically meaningful component unique identifiers, but need some way to be able to easily auto-generate a unique identifier that could be used for file-naming purposes in digitization projects. Working with legacy data, we have seen that there can be value in being able to easily associate a binary file floating around on a server somewhere with a relatively easily parsed identifier that links it to its related metadata. However, semantically meaningful identifiers based on collection structure are a rather brittle system prone to breaking when collections are rearranged or reprocessed and easy to mis-enter when working with so many digits. We?re interested to hear how others are handling their identifiers (particularly in regards to digitization workflows.) Thank you! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Thomas P. O'Neill, Jr. Library Boston College chris.mayo at bc.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=S8ME4Fo5XAeEtz-SEJljWkmvBYIPb_6ILuGWdUkOXtE&s=fTvu_1amNaLXp4WRGkvgY0OdpV3LaA82ly7l70dQZjc&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpeterson at smith.edu Tue Nov 6 13:27:50 2018 From: cpeterson at smith.edu (Christie Peterson) Date: Tue, 6 Nov 2018 13:27:50 -0500 Subject: [Archivesspace_Users_Group] Tracking media for preservation and access Message-ID: Hello everyone, We're actively looking for a new system for managing information about our A/V media, not just the content and where it lives intellectually within archival collections, but also the format, the age and condition of the media, and whether and when it has been migrated to other media, at a minimum. For example, I'd like to be able to run a report that would tell me what we have on film that has never been forward-migrated, then another that would tell me what has been forward-migrated, but over 10 years ago. Maybe what was digitized to or received on DVD but never saved on networked storage. We're talking on a scale of tens of thousands, very likely more, individual items. We've been asking around on specialized listservs and elsewhere, but I thought I'd ask here as well, since we're in ArchivesSpace and would like to implement something that works with and builds on the ASpace data we're already spending so much time on. It doesn't seem like there's anything out-of-the-box that will do what we need, and a veritable garden of home-grown solutions out there. I'd love to hear from you if you're using a system (whether home grown or not) that you think works well. Many thanks for your thoughts and responses, 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 mblair1 at stedwards.edu Tue Nov 6 13:56:28 2018 From: mblair1 at stedwards.edu (Megan Firestone) Date: Tue, 6 Nov 2018 12:56:28 -0600 Subject: [Archivesspace_Users_Group] Alma Integration In-Reply-To: References: <382DA976-600C-4F7C-9BBF-49C02143E82D@iup.edu> Message-ID: Hi all, It's great to see all this interest in an Alma/AS integration. I created a Google sheets with everyone who expressed interest and if there are more who want to put their names done feel free. Here is the link: https://docs.google.com/spreadsheets/d/1dw7ViWhhNfy0Q_33fIqIEhzxe4p35Qj1YGF1_3hm4jg/edit?usp=sharing Best, Megan On Fri, Nov 2, 2018 at 2:32 PM Hilton, Adrien wrote: > Hi Everyone, > > > > It looks like the day and time that is most convenience for everyone is > Wednesday, November 28th at 1pm Eastern. Mark your calendars. We?ll send > out the call logistics closer to the meeting. > > > > Have a nice weekend. > > Adrien > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Hilton, > Adrien > *Sent:* Thursday, November 1, 2018 11:07 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > Hi All, > > > > Looks like enough interest. > > > > Please fill out this Doodle poll with your availability following > Thanksgiving for a conference call. > > > > https://doodle.com/poll/rdarq6tyapi8i73k > > > > > If you have thoughts on how to structure the meeting and/or agenda items > feel free to send them my way. > > > > Best wishes, > > Adrien > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Lacher-Feldman, > Jessica > *Sent:* Wednesday, October 31, 2018 6:04 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > And the University of Rochester! > > > > *From: * on > behalf of Tara Laver > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Wednesday, October 31, 2018 at 6:00 PM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Alma Integration > > > > Nelson-Atkins, too. > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Susan > Luftschein > *Sent:* Wednesday, October 31, 2018 4:52 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > As is USC. > > > > *Sue Luftschein, Ph.D.* > > *Head of Special Collections/Archival & Metadata Librarian* > > *USC Libraries Special Collections* > > *University of Southern California* > > *Doheny Memorial Library* > > *3550 Trousdale Parkway, Room 207* > > *Los Angeles, CA 90089-0189* > > *tel:213-740-4046* <213-740-4046> > > *fax:213-740-2343* > > *luftsche at usc.edu* > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Beth > Kilmarx > *Sent:* Wednesday, October 31, 2018 2:47 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > IUP is definitely interested in the Alma/Aspace intergration > > Sent from my iPhone > > > On Oct 31, 2018, at 5:40 PM, Zhang, Bin wrote: > > We at Sacramento State (part of California State University system) are > also interested in integration between ASpace and Alma/Primo. Like > Northwestern and others we are considering harvesting EADs directly to > Primo, but would like to export collection-level records to Alma? > > > > --- > > 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: * on > behalf of "Custer, Mark" > *Reply-To: *Archivesspace Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Wednesday, October 31, 2018 at 1:51 PM > *To: *Archivesspace Group > > *Subject: *Re: [Archivesspace_Users_Group] Alma Integration > > > > Adrien, Susan, Vernica, and all: > > > > Add me to the interested list! ? We are not using Alma right now, but > since we will eventually migrate from our current ILS to another one that > has a robust API, I?d love to keep up with what other institutions are > doing. > > > > I?ll also say that my thoughts on the matter so far has been along the > same lines of what Leilani and Benn mentioned ? namely, bypassing the ILS, > but we still need to get those records to WorldCat, etc. That said, I?ve > no clue yet whether we?ll be able to achieve that with our next ILS or not, > or whether we?ll continue to try to keep records in synch between > ArchivesSpace and an ILS. > > > > Mark > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Ryan > Edwards > *Sent:* Wednesday, 31 October, 2018 3:54 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > Hello, > > > > We, here at the Getty Research Institute are also interested in > ArchivesSpace/Alma/Primo integration. We have experimented a bit with the > Denver plugin in our Sandbox environment. Currently, we are indexing the > full-text of our EADs in Primo. We may also be interested in exploring the > interplay between Alma bibliographic/holdings/items records and resource > records/instances in ArchivesSpace. > > > > > > Thanks, > > > > Ryan > > > > Ryan Edwards > > Digital Access and Systems Librarian > > Getty Digital ? Collection Management Systems > > Getty Research Institute > 1200 Getty Center Drive, Suite 1100 > Los Angeles, CA 90049-1688 > reedwards at getty.edu > 310.440.7398 > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Hilton, > Adrien > *Sent:* Wednesday, October 31, 2018 6:45 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > Hi All, > > > > At Houghton Library, part of the Harvard Library, we too are interested in > ArchivesSpace/Alma integration. > > > > In terms of functionality for resource description, we looked a bit at the > Denver plug-in and like the type of data exchange it offers between the > ArchivesSpace resource record and the Alma Bib and Holdings records using > the MMS ID. We could also envision the exchange working the other way, > starting from the Alma record and looking to ArchivesSpace for a resource > record with that MMS ID (in a locally specified field), creating a resource > if non-existent or updating if existent. > > > > We would also like to think through subject and agent access points and > keeping those up-to-date in both systems (using URIs), and optimally, > up-to-date with the authority file (functionality that Alma currently > offers). > > > > Lastly, exchanging and maintaining container inventories and barcodes > (instances in ArchivesSpace and item records in Alma) across the systems is > another area of functionality we?d like to explore. > > > > We?d like to host a conference call for interested parties. Can folks > respond if they are interested in taking part? If there?s enough momentum, > I?ll send around a Doodle poll with some available times. > > > > Best wishes, > > Adrien, Susan, and Vernica > > Houghton Library > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Chad > Mills > *Sent:* Wednesday, October 24, 2018 2:30 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > Hi all, > > > > Attached is the reference architecture and test/sample implementation > architecture we developed at Rutgers. We have not implemented this yet. > > > > Best, > > Chad > > > > *From:* Chad Mills > *Sent:* Friday, October 12, 2018 8:43 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* RE: [Archivesspace_Users_Group] Alma Integration > > > > Hi, > > > > We are interested! At Rutgers earlier this year we developed a reference > architecture for our Special Collections. We tested the reference > architecture by creating an implementation architecture using Alma, Primo, > ArchiveSpace and a generic repository framework. In June we migrated to > Alma so we will be looking to integrate ArchiveSpace with Alma in the near > future using our the reference architecture as a blue print. I?ll see if I > can share that reference architecture with the group. > > > > Best, > > Chad > > > > ------------------------------------- > Chad Mills > Digital Library Architect > Rutgers University Libraries > Phone: 848.932.5924 > Cell: 732.309.8538 > ------------------------------------- > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Megan > Firestone > *Sent:* Wednesday, October 10, 2018 1:34 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Alma Integration > > > > Hi, > > > > We us Alma as our library ILS here, so we have been looking at the > possibility of integrating Alma and ArchivesSpace. I was curious if anyone > else is interested in this type of integration and if there is any work > being done? > > > > Thanks! > > Megan > > > -- > > Megan M. Firestone > Archivist and Public Services Librarian > Munday Library > St. Edward's University > 3001 S. Congress Ave. > Austin, TX 78704 > 512.428.1047 > > _______________________________________________ > 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 > -- Megan M. Firestone Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Nov 7 12:25:33 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 7 Nov 2018 17:25:33 +0000 Subject: [Archivesspace_Users_Group] new ArchivesSpace role for Lora Woodford Message-ID: Dear ArchivesSpace members, We are very excited to announce that Lora Woodford will now be the Junior Developer for ArchivesSpace. Most recently Lora served as DevOps Specialist based in LYRASIS' Digital Technology Services department. In that role, she participated in a range of technical support activities including responding to ArchivesSpace support tickets, contributing code, and supporting DTS hosting services for ArchivesSpace, Islandora and CollectionSpace. In addition to her work directly with the ArchivesSpace team since the start of 2018, Lora has been involved with ArchivesSpace for many years, having helped lead ArchivesSpace implementations at Johns Hopkins University and Colgate University. She is also an inaugural member of our Core Committers group. Before joining LYRASIS, Lora was the Digital Archivist in the Sheridan Libraries at Johns Hopkins University where she created, documented, and managed workflows for acquiring, describing, processing, preserving, and providing access to born-digital materials. At Colgate, she was an early adopter of ArchivesSpace, having co-written a successful proposal to fund their ArchivesSpace implementation in 2013. We are very pleased to have Lora focus on ArchivesSpace development full time in her new role. LYRASIS continues to build up its technical knowledge and show increased commitment to the technical side of ArchivesSpace based on the growth of the ArchivesSpace community. LYRASIS serves as the organizational home for ArchivesSpace, providing resources and services to help grow, support and amplify the community contributions. Welcome Lora to her new role! 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 christine.dibella at lyrasis.org Thu Nov 8 13:23:03 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 8 Nov 2018 18:23:03 +0000 Subject: [Archivesspace_Users_Group] news re: Christine Kim Message-ID: Dear ArchivesSpace members, It is with regret that we announce that Christine Kim will be leaving her position as ArchivesSpace Community Engagement Coordinator at the end of the year to take a position with the California Digital Library. She will be sorely missed by her fellow team members and the ArchivesSpace community. As the inaugural person in this position, Christine has created a strong infrastructure for community engagement. She has worked tirelessly to develop innovative opportunities for community members to engage with us and each other such as our blog, webinar and open call series. She has been instrumental in implementing the regional forums and in expanding and refining the annual member forum. She has also reinvigorated the training program along with our many dedicated community trainers. All of us have greatly benefitted from the creativity and optimism that she brings to every activity in which she is involved. Fortunately, Christine will remain in her position for the next eight weeks to help us with programs already scheduled and develop solid plans for those that will continue in 2019 and beyond. LYRASIS, the Organizational Home for ArchivesSpace, will be posting a position description for her successor soon and we encourage all interested community members to apply. Feel free to get in touch with me if you have any questions. We wish Christine Kim well in her future endeavors and look forward to continuing to work with her in the future as a much cherished member of the ArchivesSpace community. 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 jmargalo at udel.edu Thu Nov 8 15:59:33 2018 From: jmargalo at udel.edu (Jaime Margalotti) Date: Thu, 8 Nov 2018 15:59:33 -0500 Subject: [Archivesspace_Users_Group] Imported Index - Fix or Toss? Message-ID: Hi All, We have a (thankfully small) number of finding aids with indexes that were imported into ArchivesSpace and I'm now trying to decide if they're worth salvaging. For example, the George S. Messersmith papers finding aid has this index: http://www.lib.udel.edu/ud/spec/findaids/html/mss0109.html#FAIndexhead (The EAD is visible here: http://www.lib.udel.edu/ud/spec/findaids/xml/mss0109.xml) The import populated only "Name" and "Type", striping out the and the it contained. I assume I could go in and add back the information from the , but it doesn't look like there's a way to group multiple for a single Name/Type; I'd just have to repeat it (over 30 times, for some of them!). My gut feeling is that this is a lot of work for something that is going to look terrible and, as such, be minimally useful. I could just make a PDF of the old index and link to it to preserve the information. We've had some uniquely formed appendices that I've already had to address that way. Has anybody tried to fix an imported index? If so, how and was it worth your time? Thanks for your help! Jaime -- Jaime L. Margalotti Associate Librarian / *Coordinator, Manuscript and Archival Description* Special Collections and Museums University of Delaware Library, Museums and Press 181 South College Ave. Newark, DE 19717 302-831-0554 https://library.udel.edu/special/ jmargalo at udel.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Thu Nov 8 16:12:02 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Thu, 8 Nov 2018 21:12:02 +0000 Subject: [Archivesspace_Users_Group] Imported Index - Fix or Toss? In-Reply-To: References: Message-ID: Hi Jaime, I vaguely remember dealing with this same issue when preparing a bunch of EADs for import into Archivists Toolkit. Here a chunk of XSL template I wrote to deal with the problem in a fairly hacky way: https://github.com/noahgh221/ead-test/blob/develop/xsl/AT-import-fixer.xsl#L607 Basically, just consolidate all of the refs into a single and separate them with semicolons. We only had 3-4 old EADs with this problem, so this seemed like a workable compromise at the time--to lose some structure but retain the data. -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Jaime Margalotti Sent: Thursday, November 8, 2018 4:00 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Imported Index - Fix or Toss? Hi All, We have a (thankfully small) number of finding aids with indexes that were imported into ArchivesSpace and I'm now trying to decide if they're worth salvaging. For example, the George S. Messersmith papers finding aid has this index: http://www.lib.udel.edu/ud/spec/findaids/html/mss0109.html#FAIndexhead (The EAD is visible here: http://www.lib.udel.edu/ud/spec/findaids/xml/mss0109.xml) The import populated only "Name" and "Type", striping out the and the it contained. I assume I could go in and add back the information from the , but it doesn't look like there's a way to group multiple for a single Name/Type; I'd just have to repeat it (over 30 times, for some of them!). My gut feeling is that this is a lot of work for something that is going to look terrible and, as such, be minimally useful. I could just make a PDF of the old index and link to it to preserve the information. We've had some uniquely formed appendices that I've already had to address that way. Has anybody tried to fix an imported index? If so, how and was it worth your time? Thanks for your help! Jaime -- Jaime L. Margalotti Associate Librarian / Coordinator, Manuscript and Archival Description Special Collections and Museums University of Delaware Library, Museums and Press 181 South College Ave. Newark, DE 19717 302-831-0554 https://library.udel.edu/special/ jmargalo at udel.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpeterson at smith.edu Thu Nov 8 17:37:20 2018 From: cpeterson at smith.edu (Christie Peterson) Date: Thu, 8 Nov 2018 17:37:20 -0500 Subject: [Archivesspace_Users_Group] Imported Index - Fix or Toss? In-Reply-To: References: Message-ID: If the indexed terms are all included in the free-text areas of description that the links point to, the search functionalities of ASpace or another public user interface will largely make the index not worth the bother of saving. If you feel there is real value added to having these terms called out beyond their inclusion in searchable text, you could turn them into controlled access terms (either subjects or agents, as appopriate) and link them to the relevant Archival Objects. That's probably not an insignificant amount of work, though, so you'd want to be sure you have a reality-based scenario where you think your users would want that. Cheers, Christie Christie S. Peterson Manager of Technical Services for Special Collections Smith College cpeterson at smith.edu she/her/hers On Thu, Nov 8, 2018 at 4:12 PM Noah Huffman wrote: > Hi Jaime, > > > > I vaguely remember dealing with this same issue when preparing a bunch of > EADs for import into Archivists Toolkit. > > > > Here a chunk of XSL template I wrote to deal with the problem in a fairly > hacky way: > https://github.com/noahgh221/ead-test/blob/develop/xsl/AT-import-fixer.xsl#L607 > > > > Basically, just consolidate all of the refs into a single and > separate them with semicolons. > > > > We only had 3-4 old EADs with this problem, so this seemed like a workable > compromise at the time--to lose some structure but retain the data. > > > > -Noah > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Jaime > Margalotti > *Sent:* Thursday, November 8, 2018 4:00 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Imported Index - Fix or Toss? > > > > Hi All, > > > > We have a (thankfully small) number of finding aids with indexes that were > imported into ArchivesSpace and I'm now trying to decide if they're worth > salvaging. > > > > For example, the George S. Messersmith papers finding aid has this index: > http://www.lib.udel.edu/ud/spec/findaids/html/mss0109.html#FAIndexhead > > (The EAD is visible here: > http://www.lib.udel.edu/ud/spec/findaids/xml/mss0109.xml > > ) > > > > The import populated only "Name" and "Type", striping out the and > the it contained. I assume I could go in and add back the > information from the , but it doesn't look like there's a way to group > multiple for a single Name/Type; I'd just have to repeat it (over 30 > times, for some of them!). > > > > My gut feeling is that this is a lot of work for something that is going > to look terrible and, as such, be minimally useful. I could just make a > PDF of the old index and link to it to preserve the information. We've had > some uniquely formed appendices that I've already had to address that way. > > > > Has anybody tried to fix an imported index? If so, how and was it worth > your time? > > > > Thanks for your help! > > Jaime > > > > -- > > > > *Jaime L. Margalotti* > > *Associate Librarian / **Coordinator, Manuscript and Archival Description* > > Special Collections and Museums > > University of Delaware Library, Museums and Press > > 181 South College Ave. > > Newark, DE 19717 > > 302-831-0554 > > https://library.udel.edu/special/ > > > jmargalo at udel.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 Christine.Kim at lyrasis.org Fri Nov 9 17:09:19 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 9 Nov 2018 22:09:19 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_tac] ASpace Kansas City Regional Forum - Registration is now open! In-Reply-To: References: Message-ID: Dear ArchivesSpace Community, The ASpace Kansas City Regional Forum is just 3 weeks away! Registration is currently open! We are thrilled to share that during this forum, we plan to offer a session in the afternoon that highlights the diverse phases of ArchivesSpace implementation. During this session, we invite organizations to provide a quick 5 minute overview on where their institution is currently at with implementation, as well as any challenges they're facing as they move forward into the next phase. Following the overview, we will open up for a 10-15 minute group conversation sharing any insights, ideas, or lessons learned to help you navigate into your next stage. We are looking to represent a diverse spectrum of community organizations, including public libraries, academic institutions, museums, religious organizations, and historical societies. We encourage smaller institutions as well as lone arrangers to consider participating in this session. Please let me know if you are attending the forum and would be interested in participating in this session. Program specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Thanks! Best wishes, Christine Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org On Behalf Of Christine Kim Sent: Friday, October 26, 2018 8:21 AM Subject: [Archivesspace_tac] ASpace Kansas City Regional Forum - Registration is now open! Join us for the ArchivesSpace Regional Forum in Kansas City! 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. Registration is now open! [https://archivesspace.atlassian.net/wiki/download/attachments/728662017/KC-Banner02.jpg?version=1&modificationDate=1539367905411&cacheVersion=1&api=v2&effects=border-simple,blur-border,tape] DETAILS * Location: Midwest Genealogy Center * Date: November 30, 2018 (Friday) * Time: 9am - 5pm * Parking: Parking & Transportation PROGRAM The specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Morning Workshops: The morning will feature two hands-on, engaging workshops. Please register for the workshop you are interested in attending. Each workshop is limited to 15 participants. * Workshop A: Choose Your ASpace Adventure * Instructor: Miloche Kottman, University of Kansas Libraries * The content of this workshop will be determined by a poll presented during registration check-out. Options include: * Option 1: Deep dive of Accession & Reource records: How to create an accession record, all about notes and spawning; How to create a resource record, all about notes, creating multi-level description, adding instance(s) * Option 2: Built-in ArchivesSpace efficiencies: Learn how to use Rapid Data Entry; set up default values for new accession, resource or digital object records; import EAD record with archival objects and merge with brief top-level resource record; controlled value list; default note order; LCNAF Import plugin; Container and Location management * Option 3: Controlling Data in ArchivesSpace: Data cleanup in ArchivesSpace; Cleaning up controlled values list; adding values to controlled values list; creating agent/subject records; merging duplicate agent/subject records * Workshop B: Introduction to Git and GitHub: A hands-on workshop * Instructor: Jamene Brooks-Kieffer, University of Kansas Libraries * Workshop Description: Git is a powerful open source version control tool that was originally designed for software development projects. GitHub is a web-based service that offers the functionality of Git plus additional features that enhance collaboration and project management. The combination of Git and GitHub creates a redundant, transparent, and reproducible work environment. However, accessing items available on GitHub (such as ArchivesSpace source code, documentation, and migration scripts) can be confusing and frustrating without training and practice. This workshop will introduce you to the basics of using Git on the command line, setting up your own GitHub repository, and contributing to projects hosted on GitHub. This workshop will also introduce you to using Markdown for formatting plain text files. You do not need to have any prior knowledge of Git, GitHub, Markdown, or the Unix-style command line to attend. Afternoon program: The afternoon session will highlight stories and experiences through presentations and group discussions. A catered lunch will be provided. * Speaker submissions: Currently accepting submissions! More info here: http://archivesspace.org/archives/3210 REGISTRATION Registration, including the "Workshop A: Choose Your ASpace Adventure" poll, is now open: https://www.eventbrite.com/e/archivesspace-regional-forum-kansas-city-2018-tickets-50618209427 HAPPY HOUR We will kick off the forum on November 29th (the night before) with an optional happy hour at Smokehouse Barbecue. Join us for a casual get together so we can get to know each other over delicious Kansas City barbecue! We'll provide a selection of appetizers to share. You are welcome to purchase your own drinks or additional food. This social activity is open to everyone. QUESTIONS? If you have any questions (or ideas!) related to the regional forums, feel free to email Christine Kim at christine.kim at lyrasis.org. Sincerely, Kansas City Regional Forum Working Group Danielle Butler (Central Arkansas Library System) Marcella Huggard (University of Kansas) Miloche Kottman (University of Kansas) Patrice-Andre Prud'homme (Oklahoma State University) Christine Kim (ArchivesSpace) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 58033 bytes Desc: image001.jpg URL: From larry.weimer at nyhistory.org Sat Nov 10 17:39:38 2018 From: larry.weimer at nyhistory.org (Larry Weimer) Date: Sat, 10 Nov 2018 17:39:38 -0500 Subject: [Archivesspace_Users_Group] Question re: Including Unpublished in EAD/PDF Message-ID: Hi all, I had occasion recently to run a "Print to PDF" of one of our resources that includes several series that are "unpublished." I wanted the unpublished this time so I checked the "include unpublished" box. But the PDF did not include them. I found this was not unique to the particular resource I first ran. I also found that the unpublished was not included in the EADXML even when checked to include. I'm running version 2.3.2. These records had been migrated from Archivists Toolkit (where the series had been checked as "internal only.") Has anyone else experienced this? Any thoughts or guidance on this? Thanks! Larry Weimer Head of Archival Processing New-York Historical Society -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneal at richmond.edu Mon Nov 12 11:30:07 2018 From: rneal at richmond.edu (Neal, Rick) Date: Mon, 12 Nov 2018 16:30:07 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue Message-ID: Good morning, I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. I am now trying to replicate it on my production server. After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt That file mentions that an address is already in use. (I append it to the bottom). I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. I appreciate whatever advice you have. Rick ~~~~~~~~~~~~~~~~~~~~~~~ I see this in the archivesspace.out file Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use This is the complete aspace_diagnostic_1542032577.txt file "cpu_count": 2, "exception": { "msg": "Address already in use", "backtrace": [ "sun.nio.ch.Net.bind0(Native Method)", "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", "launcher.launcher.start_server(launcher/launcher.rb:92)", "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", "launcher.launcher.main(launcher/launcher.rb:179)", "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", "launcher.launcher.
(launcher/launcher.rb:261)", "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", "org.jruby.Main.internalRun(org/jruby/Main.java:305)", "org.jruby.Main.run(org/jruby/Main.java:232)", "org.jruby.Main.main(org/jruby/Main.java:204)" ] } } -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Nov 12 11:38:56 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 12 Nov 2018 16:38:56 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue In-Reply-To: References: Message-ID: >>WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Neal, Rick Sent: Monday, November 12, 2018 11:30:07 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] 2.5 install issue Good morning, I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. I am now trying to replicate it on my production server. After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt That file mentions that an address is already in use. (I append it to the bottom). I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. I appreciate whatever advice you have. Rick ~~~~~~~~~~~~~~~~~~~~~~~ I see this in the archivesspace.out file Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use This is the complete aspace_diagnostic_1542032577.txt file "cpu_count": 2, "exception": { "msg": "Address already in use", "backtrace": [ "sun.nio.ch.Net.bind0(Native Method)", "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", "launcher.launcher.start_server(launcher/launcher.rb:92)", "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", "launcher.launcher.main(launcher/launcher.rb:179)", "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", "launcher.launcher.
(launcher/launcher.rb:261)", "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", "org.jruby.Main.internalRun(org/jruby/Main.java:305)", "org.jruby.Main.run(org/jruby/Main.java:232)", "org.jruby.Main.main(org/jruby/Main.java:204)" ] } } From alison.clemens at yale.edu Mon Nov 12 13:38:43 2018 From: alison.clemens at yale.edu (Clemens, Alison) Date: Mon, 12 Nov 2018 18:38:43 +0000 Subject: [Archivesspace_Users_Group] Using ASpace event records to track digitization work? Message-ID: Dear colleagues, I'm writing to ask if anyone is using ArchivesSpace event records to track digitization work performed on collection materials. For example, I could see indicating digitization status by attaching event records to particular archival components and/or resources. If you're doing something like this, would you mind please sharing the details of how you've set this up? Additionally, I'd love to hear if folks using other ArchivesSpace data elements to indicate specific details of digitization efforts (e.g., if digitization was unsuccessful due to fragility, etc.). I've looked through past listserv digests and haven't found anything quite along these lines, but I'd be grateful to hear of any experiences you might have with this or similar efforts! With thanks, Alison Alison Clemens Assistant Head of Arrangement and Description Manuscripts & Archives, Yale University Library P.O. Box 208240 New Haven, CT 06520-8240 203-432-9029 alison.clemens at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneal at richmond.edu Mon Nov 12 13:53:28 2018 From: rneal at richmond.edu (Neal, Rick) Date: Mon, 12 Nov 2018 18:53:28 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue In-Reply-To: References: , Message-ID: Blake, What port did it run on before 2.5? Rick Sent from my iPhone On Nov 12, 2018, at 11:39 AM, Blake Carver wrote: >>> WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use > > Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. > > > > ________________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Neal, Rick > Sent: Monday, November 12, 2018 11:30:07 AM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] 2.5 install issue > > Good morning, > > I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. > > I am now trying to replicate it on my production server. > > After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: > > { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } > > > The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt > > That file mentions that an address is already in use. (I append it to the bottom). > > I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. > > I appreciate whatever advice you have. > > Rick > > ~~~~~~~~~~~~~~~~~~~~~~~ > > I see this in the archivesspace.out file > > Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized > INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war > Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed > WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use > > This is the complete aspace_diagnostic_1542032577.txt file > > "cpu_count": 2, > "exception": { > "msg": "Address already in use", > "backtrace": [ > "sun.nio.ch.Net.bind0(Native Method)", > "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", > "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", > "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", > "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", > "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", > "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", > "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", > "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", > "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", > "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", > "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", > "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", > "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", > "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", > "launcher.launcher.start_server(launcher/launcher.rb:92)", > "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", > "launcher.launcher.main(launcher/launcher.rb:179)", > "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", > "launcher.launcher.
(launcher/launcher.rb:261)", > "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", > "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", > "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", > "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", > "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", > "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", > "org.jruby.Main.internalRun(org/jruby/Main.java:305)", > "org.jruby.Main.run(org/jruby/Main.java:232)", > "org.jruby.Main.main(org/jruby/Main.java:204)" > ] > } > } > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From sdm7g at virginia.edu Mon Nov 12 14:02:28 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 12 Nov 2018 19:02:28 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue In-Reply-To: References: Message-ID: <200589CE-F587-4006-AE58-B49244231581@virginia.edu> The default ports haven?t changed. Blake transposed digits in his email to 8028, but the error message says 8082, which is the default port for public webapp. Default port numbers are in common/config/config-defaults.rb: https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L22-L48 AppConfig[:backend_url] = "http://localhost:8089" AppConfig[:frontend_url] = "http://localhost:8080" AppConfig[:public_url] = "http://localhost:8081" AppConfig[:oai_url] = "http://localhost:8082" AppConfig[:solr_url] = "http://localhost:8090" AppConfig[:indexer_url] = "http://localhost:8091" AppConfig[:docs_url] = "http://localhost:8888" > On Nov 12, 2018, at 1:53 PM, Neal, Rick wrote: > > Blake, > > What port did it run on before 2.5? > > Rick > > Sent from my iPhone > > On Nov 12, 2018, at 11:39 AM, Blake Carver wrote: > >>>> WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use >> >> Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. >> >> >> >> ________________________________________ >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Neal, Rick >> Sent: Monday, November 12, 2018 11:30:07 AM >> To: Archivesspace Users Group >> Subject: [Archivesspace_Users_Group] 2.5 install issue >> >> Good morning, >> >> I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. >> >> I am now trying to replicate it on my production server. >> >> After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: >> >> { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } >> >> >> The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt >> >> That file mentions that an address is already in use. (I append it to the bottom). >> >> I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. >> >> I appreciate whatever advice you have. >> >> Rick >> >> ~~~~~~~~~~~~~~~~~~~~~~~ >> >> I see this in the archivesspace.out file >> >> Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized >> INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war >> Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed >> WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use >> >> This is the complete aspace_diagnostic_1542032577.txt file >> >> "cpu_count": 2, >> "exception": { >> "msg": "Address already in use", >> "backtrace": [ >> "sun.nio.ch.Net.bind0(Native Method)", >> "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", >> "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", >> "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", >> "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", >> "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", >> "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", >> "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", >> "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", >> "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", >> "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", >> "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", >> "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", >> "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", >> "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", >> "launcher.launcher.start_server(launcher/launcher.rb:92)", >> "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", >> "launcher.launcher.main(launcher/launcher.rb:179)", >> "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", >> "launcher.launcher.
(launcher/launcher.rb:261)", >> "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", >> "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", >> "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", >> "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", >> "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", >> "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", >> "org.jruby.Main.internalRun(org/jruby/Main.java:305)", >> "org.jruby.Main.run(org/jruby/Main.java:232)", >> "org.jruby.Main.main(org/jruby/Main.java:204)" >> ] >> } >> } >> _______________________________________________ >> 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: 6102 bytes Desc: not available URL: From sdm7g at virginia.edu Mon Nov 12 15:01:28 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 12 Nov 2018 20:01:28 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue In-Reply-To: <200589CE-F587-4006-AE58-B49244231581@virginia.edu> References: <200589CE-F587-4006-AE58-B49244231581@virginia.edu> Message-ID: <1F81B46B-36F3-4835-B0AE-F53927B3712D@virginia.edu> Oops. My error. 8082 is OAI port, not PUI. Not sure how far back OAI support was initially added. > On Nov 12, 2018, at 2:02 PM, Majewski, Steven Dennis (sdm7g) wrote: > > > The default ports haven?t changed. > Blake transposed digits in his email to 8028, but the error message says 8082, which is the default port for public webapp. > Default port numbers are in common/config/config-defaults.rb: > > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L22-L48 > > > AppConfig[:backend_url] = "http://localhost:8089 " > AppConfig[:frontend_url] = "http://localhost:8080 " > AppConfig[:public_url] = "http://localhost:8081 " > AppConfig[:oai_url] = "http://localhost:8082 " > AppConfig[:solr_url] = "http://localhost:8090 " > AppConfig[:indexer_url] = "http://localhost:8091 " > AppConfig[:docs_url] = "http://localhost:8888 " > > > > >> On Nov 12, 2018, at 1:53 PM, Neal, Rick > wrote: >> >> Blake, >> >> What port did it run on before 2.5? >> >> Rick >> >> Sent from my iPhone >> >> On Nov 12, 2018, at 11:39 AM, Blake Carver > wrote: >> >>>>> WARNING: FAILED SelectChannelConnector at 0.0.0.0 :8082: java.net.BindException: Address already in use >>> >>> Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. >>> >>> >>> >>> ________________________________________ >>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Neal, Rick > >>> Sent: Monday, November 12, 2018 11:30:07 AM >>> To: Archivesspace Users Group >>> Subject: [Archivesspace_Users_Group] 2.5 install issue >>> >>> Good morning, >>> >>> I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. >>> >>> I am now trying to replicate it on my production server. >>> >>> After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: >>> >>> { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } >>> >>> >>> The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt >>> >>> That file mentions that an address is already in use. (I append it to the bottom). >>> >>> I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. >>> >>> I appreciate whatever advice you have. >>> >>> Rick >>> >>> ~~~~~~~~~~~~~~~~~~~~~~~ >>> >>> I see this in the archivesspace.out file >>> >>> Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized >>> INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war >>> Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed >>> WARNING: FAILED SelectChannelConnector at 0.0.0.0 :8082: java.net.BindException: Address already in use >>> >>> This is the complete aspace_diagnostic_1542032577.txt file >>> >>> "cpu_count": 2, >>> "exception": { >>> "msg": "Address already in use", >>> "backtrace": [ >>> "sun.nio.ch.Net.bind0(Native Method)", >>> "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", >>> "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", >>> "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", >>> "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", >>> "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", >>> "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", >>> "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", >>> "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", >>> "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", >>> "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", >>> "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", >>> "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", >>> "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", >>> "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", >>> "launcher.launcher.start_server(launcher/launcher.rb:92)", >>> "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", >>> "launcher.launcher.main(launcher/launcher.rb:179)", >>> "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", >>> "launcher.launcher.
(launcher/launcher.rb:261)", >>> "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", >>> "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", >>> "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", >>> "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", >>> "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", >>> "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", >>> "org.jruby.Main.internalRun(org/jruby/Main.java:305)", >>> "org.jruby.Main.run(org/jruby/Main.java:232)", >>> "org.jruby.Main.main(org/jruby/Main.java:204)" >>> ] >>> } >>> } >>> _______________________________________________ >>> 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: 6102 bytes Desc: not available URL: From rneal at richmond.edu Tue Nov 13 13:49:57 2018 From: rneal at richmond.edu (Neal, Rick) Date: Tue, 13 Nov 2018 18:49:57 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue In-Reply-To: <1F81B46B-36F3-4835-B0AE-F53927B3712D@virginia.edu> References: <200589CE-F587-4006-AE58-B49244231581@virginia.edu> <1F81B46B-36F3-4835-B0AE-F53927B3712D@virginia.edu> Message-ID: Thanks to everyone. It is up and working. The oai/sample is working, at least on campus. We have 2 repositories. One for our Special Collections and one for the Law School. https://archives.richmond.edu/repositories/4 https://archives.richmond.edu/repositories/5 I have never worked with setting up oai before and I am wondering how the ?scraper? determines which repository to scrape? Do I need to set up 2 sets (1 for each repository)? Would setting up 2 sets look something like this?: AppConfig[:oai_sets] = { 'repository_set' => { :repo_codes => ['4'], :description => "Special Collections Repository", }, 'repository_set' => { :repo_codes => ['5'], :description => "Law School Repository", }, } Thanks! Rick Neal ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # OAI configuration options AppConfig[:oai_repository_name] = 'ArchivesSpace OAI Provider' AppConfig[:oai_proxy_url] = 'http://aspace.richmond.edu:8082/' AppConfig[:oai_record_prefix] = 'oai:archivesspace' AppConfig[:oai_admin_email] = 'admin at example.com' # In addition to the sets based on level of description, you can define OAI Sets # based on repository codes and/or sponsors as follows # # AppConfig[:oai_sets] = { # 'repository_set' => { # :repo_codes => ['hello626'], # :description => "A set of one or more repositories", # }, # # 'sponsor_set' => { # :sponsors => ['The_Sponsor'], # :description => "A set of one or more sponsors", # }, # } AppConfig[:oai_ead_options] = {} # alternate example: AppConfig[:oai_ead_options] = { :include_daos => true, :use_numbered_c_tags => true } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rick Neal Library Applications and Systems Administrator Boatwright Memorial Library University of Richmond, VA 23173 rneal at richmond.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Monday, November 12, 2018 3:01 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.5 install issue Oops. My error. 8082 is OAI port, not PUI. Not sure how far back OAI support was initially added. On Nov 12, 2018, at 2:02 PM, Majewski, Steven Dennis (sdm7g) > wrote: The default ports haven?t changed. Blake transposed digits in his email to 8028, but the error message says 8082, which is the default port for public webapp. Default port numbers are in common/config/config-defaults.rb: https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L22-L48 AppConfig[:backend_url] = "http://localhost:8089" AppConfig[:frontend_url] = "http://localhost:8080" AppConfig[:public_url] = "http://localhost:8081" AppConfig[:oai_url] = "http://localhost:8082" AppConfig[:solr_url] = "http://localhost:8090" AppConfig[:indexer_url] = "http://localhost:8091" AppConfig[:docs_url] = "http://localhost:8888" On Nov 12, 2018, at 1:53 PM, Neal, Rick > wrote: Blake, What port did it run on before 2.5? Rick Sent from my iPhone On Nov 12, 2018, at 11:39 AM, Blake Carver > wrote: WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Neal, Rick > Sent: Monday, November 12, 2018 11:30:07 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] 2.5 install issue Good morning, I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. I am now trying to replicate it on my production server. After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt That file mentions that an address is already in use. (I append it to the bottom). I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. I appreciate whatever advice you have. Rick ~~~~~~~~~~~~~~~~~~~~~~~ I see this in the archivesspace.out file Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed WARNING: FAILED SelectChannelConnector at 0.0.0.0:8082: java.net.BindException: Address already in use This is the complete aspace_diagnostic_1542032577.txt file "cpu_count": 2, "exception": { "msg": "Address already in use", "backtrace": [ "sun.nio.ch.Net.bind0(Native Method)", "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", "launcher.launcher.start_server(launcher/launcher.rb:92)", "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", "launcher.launcher.main(launcher/launcher.rb:179)", "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", "launcher.launcher.
(launcher/launcher.rb:261)", "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", "org.jruby.Main.internalRun(org/jruby/Main.java:305)", "org.jruby.Main.run(org/jruby/Main.java:232)", "org.jruby.Main.main(org/jruby/Main.java:204)" ] } } _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From ldfs at umn.edu Tue Nov 13 14:06:28 2018 From: ldfs at umn.edu (Lara Friedman-Shedlov) Date: Tue, 13 Nov 2018 13:06:28 -0600 Subject: [Archivesspace_Users_Group] Using ASpace event records to track digitization work? In-Reply-To: References: Message-ID: I have been using events in ASpace to record work done on born digital collection materials. So far I've just been creating events to indicate completion of ingest and processing. However, so far we haven't really figured out whether it is actually useful or what exactly we can do with this info, so I'd be interested in hearing from others. / Lara Friedman-Shedlov On Mon, Nov 12, 2018 at 12:38 PM Clemens, Alison wrote: > Dear colleagues, > > > > I?m writing to ask if anyone is using ArchivesSpace event records to track > digitization work performed on collection materials. For example, I could > see indicating digitization status by attaching event records to particular > archival components and/or resources. If you?re doing something like this, > would you mind please sharing the details of how you?ve set this up? > > > > Additionally, I?d love to hear if folks using other ArchivesSpace data > elements to indicate specific details of digitization efforts (e.g., if > digitization was unsuccessful due to fragility, etc.). > > > > I?ve looked through past listserv digests and haven?t found anything quite > along these lines, but I?d be grateful to hear of any experiences you might > have with this or similar efforts! > > > > With thanks, > > Alison > > > > Alison Clemens > > Assistant Head of Arrangement and Description > > Manuscripts & Archives, Yale University Library > > P.O. Box 208240 > > New Haven, CT 06520-8240 > > 203-432-9029 > > alison.clemens at yale.edu > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- _________________________________ Lara D. Friedman-Shedlov (She/Her/Hers) Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [image: www.facebook.com/IHRCA] [image: https://twitter.com/yarchives] -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue Nov 13 14:14:00 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 13 Nov 2018 19:14:00 +0000 Subject: [Archivesspace_Users_Group] 2.5 install issue In-Reply-To: References: <200589CE-F587-4006-AE58-B49244231581@virginia.edu> <1F81B46B-36F3-4835-B0AE-F53927B3712D@virginia.edu> Message-ID: This is what we did, and it?s useful if you want to harvest only one particular repository. But if you?re going to harvest from both, then it?s not necessary. We are using: https://github.com/bloomonkey/oai-harvest to harvest, with the ??create-subdirs? option which will create subdirectories based on the URIs and so will sort the repositories separately. So for example: $ oai-harvest -p oai_ead -s collection --create-subdirs https://archives-oai.lib.virginia.edu will export all of the published repository collections as EAD in this directory structure: oai:lib.virginia.edu ??? repositories ??? 3 ? ??? resources ? ??? 1.oai_ead.xml ? ??? 10.oai_ead.xml ? ??? 11.oai_ead.xml ? ??? 12.oai_ead.xml ? ??? 13.oai_ead.xml ? ??? 14.oai_ead.xml ? ??? 15.oai_ead.xml ? ??? 16.oai_ead.xml ? ??? 17.oai_ead.xml ? ??? 177.oai_ead.xml ? ??? 18.oai_ead.xml ? ??? 19.oai_ead.xml ? ??? 2.oai_ead.xml ? ??? 20.oai_ead.xml ? ??? 206.oai_ead.xml ? ??? 207.oai_ead.xml ? ??? 209.oai_ead.xml ? ??? 21.oai_ead.xml ? ??? 22.oai_ead.xml ? ??? 222.oai_ead.xml ? ??? 223.oai_ead.xml ? ??? 225.oai_ead.xml ? ??? 226.oai_ead.xml ? ??? 227.oai_ead.xml ? ??? 228.oai_ead.xml ? ??? 23.oai_ead.xml ? ??? 230.oai_ead.xml ? ??? 231.oai_ead.xml ? ??? 232.oai_ead.xml ? ??? 234.oai_ead.xml ? ??? 235.oai_ead.xml ? ??? 236.oai_ead.xml ? ??? 237.oai_ead.xml ? ??? 238.oai_ead.xml ? ??? 239.oai_ead.xml ? ??? 24.oai_ead.xml ? ??? 240.oai_ead.xml ? ??? 241.oai_ead.xml ? ??? 242.oai_ead.xml ? ??? 243.oai_ead.xml ? ??? 244.oai_ead.xml ? ??? 245.oai_ead.xml ? ??? 246.oai_ead.xml ? ??? 247.oai_ead.xml ? ??? 248.oai_ead.xml ? ??? 249.oai_ead.xml ? ??? 25.oai_ead.xml ? ??? 250.oai_ead.xml ? ??? 251.oai_ead.xml ? ??? 252.oai_ead.xml ? ??? 253.oai_ead.xml ? ??? 254.oai_ead.xml ? ??? 255.oai_ead.xml ? ??? 256.oai_ead.xml ? ??? 257.oai_ead.xml ? ??? 258.oai_ead.xml ? ??? 259.oai_ead.xml ? ??? 26.oai_ead.xml ? ??? 260.oai_ead.xml ? ??? 261.oai_ead.xml ? ??? 263.oai_ead.xml ? ??? 264.oai_ead.xml ? ??? 265.oai_ead.xml ? ??? 266.oai_ead.xml ? ??? 267.oai_ead.xml ? ??? 268.oai_ead.xml ? ??? 269.oai_ead.xml ? ??? 27.oai_ead.xml ? ??? 270.oai_ead.xml ? ??? 271.oai_ead.xml ? ??? 272.oai_ead.xml ? ??? 28.oai_ead.xml ? ??? 29.oai_ead.xml ? ??? 294.oai_ead.xml ? ??? 298.oai_ead.xml ? ??? 299.oai_ead.xml ? ??? 3.oai_ead.xml ? ??? 30.oai_ead.xml ? ??? 300.oai_ead.xml ? ??? 301.oai_ead.xml ? ??? 302.oai_ead.xml ? ??? 303.oai_ead.xml ? ??? 304.oai_ead.xml ? ??? 305.oai_ead.xml ? ??? 306.oai_ead.xml ? ??? 307.oai_ead.xml ? ??? 308.oai_ead.xml ? ??? 309.oai_ead.xml ? ??? 31.oai_ead.xml ? ??? 310.oai_ead.xml ? ??? 311.oai_ead.xml ? ??? 312.oai_ead.xml ? ??? 313.oai_ead.xml ? ??? 314.oai_ead.xml ? ??? 315.oai_ead.xml ? ??? 316.oai_ead.xml ? ??? 317.oai_ead.xml ? ??? 319.oai_ead.xml ? ??? 32.oai_ead.xml ? ??? 320.oai_ead.xml ? ??? 321.oai_ead.xml ? ??? 322.oai_ead.xml ? ??? 323.oai_ead.xml ? ??? 324.oai_ead.xml ? ??? 325.oai_ead.xml ? ??? 326.oai_ead.xml ? ??? 327.oai_ead.xml ? ??? 328.oai_ead.xml ? ??? 329.oai_ead.xml ? ??? 33.oai_ead.xml ? ??? 330.oai_ead.xml ? ??? 331.oai_ead.xml ? ??? 332.oai_ead.xml ? ??? 333.oai_ead.xml ? ??? 334.oai_ead.xml ? ??? 335.oai_ead.xml ? ??? 336.oai_ead.xml ? ??? 337.oai_ead.xml ? ??? 338.oai_ead.xml ? ??? 339.oai_ead.xml ? ??? 34.oai_ead.xml ? ??? 340.oai_ead.xml ? ??? 341.oai_ead.xml ? ??? 342.oai_ead.xml ? ??? 343.oai_ead.xml ? ??? 344.oai_ead.xml ? ??? 345.oai_ead.xml ? ??? 346.oai_ead.xml ? ??? 347.oai_ead.xml ? ??? 348.oai_ead.xml ? ??? 349.oai_ead.xml ? ??? 35.oai_ead.xml ? ??? 350.oai_ead.xml ? ??? 351.oai_ead.xml ? ??? 352.oai_ead.xml ? ??? 353.oai_ead.xml ? ??? 355.oai_ead.xml ? ??? 356.oai_ead.xml ? ??? 357.oai_ead.xml ? ??? 358.oai_ead.xml ? ??? 359.oai_ead.xml ? ??? 36.oai_ead.xml ? ??? 360.oai_ead.xml ? ??? 361.oai_ead.xml ? ??? 362.oai_ead.xml ? ??? 363.oai_ead.xml ? ??? 364.oai_ead.xml ? ??? 365.oai_ead.xml ? ??? 366.oai_ead.xml ? ??? 367.oai_ead.xml ? ??? 368.oai_ead.xml ? ??? 369.oai_ead.xml ? ??? 37.oai_ead.xml ? ??? 370.oai_ead.xml ? ??? 371.oai_ead.xml ? ??? 372.oai_ead.xml ? ??? 373.oai_ead.xml ? ??? 374.oai_ead.xml ? ??? 375.oai_ead.xml ? ??? 376.oai_ead.xml ? ??? 378.oai_ead.xml ? ??? 38.oai_ead.xml ? ??? 380.oai_ead.xml ? ??? 381.oai_ead.xml ? ??? 382.oai_ead.xml ? ??? 383.oai_ead.xml ? ??? 384.oai_ead.xml ? ??? 385.oai_ead.xml ? ??? 386.oai_ead.xml ? ??? 387.oai_ead.xml ? ??? 388.oai_ead.xml ? ??? 39.oai_ead.xml ? ??? 390.oai_ead.xml ? ??? 391.oai_ead.xml [ ? ] ??? 4 ? ??? resources ? ??? 100.oai_ead.xml ? ??? 101.oai_ead.xml ? ??? 102.oai_ead.xml ? ??? 289.oai_ead.xml ? ??? 292.oai_ead.xml ? ??? 481.oai_ead.xml ? ??? 492.oai_ead.xml ? ??? 493.oai_ead.xml ? ??? 494.oai_ead.xml ? ??? 495.oai_ead.xml ? ??? 496.oai_ead.xml ? ??? 497.oai_ead.xml ? ??? 506.oai_ead.xml ? ??? 507.oai_ead.xml ? ??? 508.oai_ead.xml ? ??? 520.oai_ead.xml ? ??? 521.oai_ead.xml ? ??? 522.oai_ead.xml ? ??? 523.oai_ead.xml ? ??? 525.oai_ead.xml ? ??? 555.oai_ead.xml ? ??? 562.oai_ead.xml ? ??? 563.oai_ead.xml ? ??? 573.oai_ead.xml ? ??? 574.oai_ead.xml ? ??? 575.oai_ead.xml ? ??? 576.oai_ead.xml ? ??? 577.oai_ead.xml ? ??? 579.oai_ead.xml ? ??? 58.oai_ead.xml ? ??? 580.oai_ead.xml ? ??? 583.oai_ead.xml ? ??? 585.oai_ead.xml ? ??? 59.oai_ead.xml ? ??? 610.oai_ead.xml ? ??? 611.oai_ead.xml ? ??? 612.oai_ead.xml ? ??? 62.oai_ead.xml ? ??? 632.oai_ead.xml ? ??? 634.oai_ead.xml ? ??? 635.oai_ead.xml ? ??? 636.oai_ead.xml ? ??? 637.oai_ead.xml ? ??? 638.oai_ead.xml ? ??? 64.oai_ead.xml ? ??? 640.oai_ead.xml ? ??? 641.oai_ead.xml ? ??? 643.oai_ead.xml ? ??? 644.oai_ead.xml ? ??? 645.oai_ead.xml ? ??? 646.oai_ead.xml ? ??? 647.oai_ead.xml ? ??? 649.oai_ead.xml ? ??? 650.oai_ead.xml ? ??? 651.oai_ead.xml ? ??? 652.oai_ead.xml ? ??? 653.oai_ead.xml ? ??? 654.oai_ead.xml ? ??? 655.oai_ead.xml ? ??? 656.oai_ead.xml ? ??? 657.oai_ead.xml ? ??? 659.oai_ead.xml ? ??? 66.oai_ead.xml ? ??? 660.oai_ead.xml ? ??? 661.oai_ead.xml ? ??? 662.oai_ead.xml ? ??? 663.oai_ead.xml ? ??? 664.oai_ead.xml ? ??? 665.oai_ead.xml ? ??? 666.oai_ead.xml ? ??? 667.oai_ead.xml ? ??? 668.oai_ead.xml ? ??? 669.oai_ead.xml ? ??? 67.oai_ead.xml ? ??? 670.oai_ead.xml ? ??? 671.oai_ead.xml ? ??? 672.oai_ead.xml ? ??? 673.oai_ead.xml ? ??? 674.oai_ead.xml ? ??? 675.oai_ead.xml ? ??? 676.oai_ead.xml ? ??? 677.oai_ead.xml ? ??? 678.oai_ead.xml ? ??? 679.oai_ead.xml ? ??? 68.oai_ead.xml ? ??? 680.oai_ead.xml ? ??? 681.oai_ead.xml ? ??? 682.oai_ead.xml ? ??? 683.oai_ead.xml ? ??? 684.oai_ead.xml ? ??? 685.oai_ead.xml ? ??? 686.oai_ead.xml ? ??? 687.oai_ead.xml ? ??? 688.oai_ead.xml ? ??? 689.oai_ead.xml ? ??? 69.oai_ead.xml ? ??? 690.oai_ead.xml ? ??? 691.oai_ead.xml ? ??? 692.oai_ead.xml ? ??? 693.oai_ead.xml ? ??? 694.oai_ead.xml ? ??? 695.oai_ead.xml ? ??? 696.oai_ead.xml ? ??? 697.oai_ead.xml ? ??? 698.oai_ead.xml ? ??? 699.oai_ead.xml ? ??? 70.oai_ead.xml ? ??? 700.oai_ead.xml ? ??? 701.oai_ead.xml ? ??? 702.oai_ead.xml ? ??? 703.oai_ead.xml ? ??? 704.oai_ead.xml ? ??? 705.oai_ead.xml ? ??? 707.oai_ead.xml ? ??? 708.oai_ead.xml ? ??? 709.oai_ead.xml ? ??? 71.oai_ead.xml ? ??? 710.oai_ead.xml ? ??? 711.oai_ead.xml ? ??? 712.oai_ead.xml ? ??? 713.oai_ead.xml ? ??? 714.oai_ead.xml ? ??? 716.oai_ead.xml ? ??? 717.oai_ead.xml ? ??? 718.oai_ead.xml ? ??? 719.oai_ead.xml ? ??? 72.oai_ead.xml ? ??? 720.oai_ead.xml ? ??? 721.oai_ead.xml ? ??? 722.oai_ead.xml ? ??? 723.oai_ead.xml ? ??? 725.oai_ead.xml ? ??? 726.oai_ead.xml ? ??? 727.oai_ead.xml ? ??? 728.oai_ead.xml ? ??? 730.oai_ead.xml ? ??? 731.oai_ead.xml ? ??? 732.oai_ead.xml ? ??? 733.oai_ead.xml ? ??? 734.oai_ead.xml ? ??? 74.oai_ead.xml ? ??? 75.oai_ead.xml ? ??? 76.oai_ead.xml ? ??? 77.oai_ead.xml ? ??? 78.oai_ead.xml ? ??? 79.oai_ead.xml ? ??? 80.oai_ead.xml ? ??? 81.oai_ead.xml ? ??? 86.oai_ead.xml ? ??? 87.oai_ead.xml ? ??? 88.oai_ead.xml ? ??? 89.oai_ead.xml ? ??? 90.oai_ead.xml ? ??? 91.oai_ead.xml ? ??? 93.oai_ead.xml ? ??? 94.oai_ead.xml ? ??? 95.oai_ead.xml ? ??? 96.oai_ead.xml ? ??? 97.oai_ead.xml ? ??? 98.oai_ead.xml ? ??? 99.oai_ead.xml ??? 7 ? ??? resources ? ??? 109.oai_ead.xml ? ??? 110.oai_ead.xml ? ??? 111.oai_ead.xml ? ??? 112.oai_ead.xml ? ??? 113.oai_ead.xml ? ??? 114.oai_ead.xml ? ??? 115.oai_ead.xml ? ??? 116.oai_ead.xml ? ??? 117.oai_ead.xml ? ??? 119.oai_ead.xml ? ??? 120.oai_ead.xml ? ??? 121.oai_ead.xml ? ??? 122.oai_ead.xml ? ??? 123.oai_ead.xml ? ??? 124.oai_ead.xml ? ??? 125.oai_ead.xml ? ??? 126.oai_ead.xml ? ??? 127.oai_ead.xml ? ??? 128.oai_ead.xml ? ??? 129.oai_ead.xml ? ??? 130.oai_ead.xml ? ??? 131.oai_ead.xml ? ??? 132.oai_ead.xml ? ??? 133.oai_ead.xml ? ??? 134.oai_ead.xml ? ??? 135.oai_ead.xml ? ??? 137.oai_ead.xml ? ??? 138.oai_ead.xml ? ??? 139.oai_ead.xml ? ??? 140.oai_ead.xml ? ??? 141.oai_ead.xml ? ??? 142.oai_ead.xml ? ??? 143.oai_ead.xml ? ??? 144.oai_ead.xml ? ??? 145.oai_ead.xml ? ??? 146.oai_ead.xml ? ??? 147.oai_ead.xml ? ??? 148.oai_ead.xml ? ??? 149.oai_ead.xml ? ??? 150.oai_ead.xml ? ??? 151.oai_ead.xml ? ??? 152.oai_ead.xml ? ??? 153.oai_ead.xml ? ??? 154.oai_ead.xml ? ??? 155.oai_ead.xml ? ??? 156.oai_ead.xml ? ??? 157.oai_ead.xml ? ??? 158.oai_ead.xml ? ??? 159.oai_ead.xml ? ??? 160.oai_ead.xml ? ??? 161.oai_ead.xml ? ??? 163.oai_ead.xml ? ??? 164.oai_ead.xml ? ??? 165.oai_ead.xml ? ??? 166.oai_ead.xml ? ??? 167.oai_ead.xml ? ??? 168.oai_ead.xml ? ??? 169.oai_ead.xml ? ??? 170.oai_ead.xml ? ??? 171.oai_ead.xml ? ??? 172.oai_ead.xml ? ??? 173.oai_ead.xml ? ??? 174.oai_ead.xml ? ??? 210.oai_ead.xml ??? 8 ??? resources ??? 182.oai_ead.xml ??? 183.oai_ead.xml ??? 186.oai_ead.xml ??? 188.oai_ead.xml ??? 189.oai_ead.xml ??? 190.oai_ead.xml ??? 192.oai_ead.xml ??? 193.oai_ead.xml ??? 194.oai_ead.xml ??? 195.oai_ead.xml ??? 196.oai_ead.xml ??? 198.oai_ead.xml ??? 199.oai_ead.xml ??? 200.oai_ead.xml ??? 201.oai_ead.xml ??? 203.oai_ead.xml ??? 208.oai_ead.xml ??? 216.oai_ead.xml ??? 218.oai_ead.xml ??? 377.oai_ead.xml ??? 379.oai_ead.xml ??? 406.oai_ead.xml ??? 412.oai_ead.xml ??? 505.oai_ead.xml > On Nov 13, 2018, at 1:49 PM, Neal, Rick wrote: > > Thanks to everyone. It is up and working. The oai/sample is working, at least on campus. > > We have 2 repositories. One for our Special Collections and one for the Law School. > > https://archives.richmond.edu/repositories/4 > https://archives.richmond.edu/repositories/5 > > I have never worked with setting up oai before and I am wondering how the ?scraper? determines which repository to scrape? Do I need to set up 2 sets (1 for each repository)? > > Would setting up 2 sets look something like this?: > > AppConfig[:oai_sets] = { > 'repository_set' => { > :repo_codes => ['4'], > :description => "Special Collections Repository", > }, > 'repository_set' => { > :repo_codes => ['5'], > :description => "Law School Repository", > }, > } > > Thanks! > > Rick Neal > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > # OAI configuration options > AppConfig[:oai_repository_name] = 'ArchivesSpace OAI Provider' > AppConfig[:oai_proxy_url] = 'http://aspace.richmond.edu:8082/ ' > AppConfig[:oai_record_prefix] = 'oai:archivesspace' > AppConfig[:oai_admin_email] = 'admin at example.com ' > # In addition to the sets based on level of description, you can define OAI Sets > # based on repository codes and/or sponsors as follows > # > # AppConfig[:oai_sets] = { > # 'repository_set' => { > # :repo_codes => ['hello626'], > # :description => "A set of one or more repositories", > # }, > # > # 'sponsor_set' => { > # :sponsors => ['The_Sponsor'], > # :description => "A set of one or more sponsors", > # }, > # } > AppConfig[:oai_ead_options] = {} > # alternate example: AppConfig[:oai_ead_options] = { :include_daos => true, :use_numbered_c_tags => true } > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Rick Neal > Library Applications and Systems Administrator > Boatwright Memorial Library > University of Richmond, VA 23173 > > rneal at richmond.edu > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) > Sent: Monday, November 12, 2018 3:01 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] 2.5 install issue > > > Oops. My error. 8082 is OAI port, not PUI. > Not sure how far back OAI support was initially added. > > > On Nov 12, 2018, at 2:02 PM, Majewski, Steven Dennis (sdm7g) > wrote: > > > The default ports haven?t changed. > Blake transposed digits in his email to 8028, but the error message says 8082, which is the default port for public webapp. > Default port numbers are in common/config/config-defaults.rb: > > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L22-L48 > > > AppConfig[:backend_url] = "http://localhost:8089 " > AppConfig[:frontend_url] = "http://localhost:8080 " > AppConfig[:public_url] = "http://localhost:8081 " > AppConfig[:oai_url] = "http://localhost:8082 " > AppConfig[:solr_url] = "http://localhost:8090 " > AppConfig[:indexer_url] = "http://localhost:8091 " > AppConfig[:docs_url] = "http://localhost:8888 " > > > > > > On Nov 12, 2018, at 1:53 PM, Neal, Rick > wrote: > > Blake, > > What port did it run on before 2.5? > > Rick > > Sent from my iPhone > > On Nov 12, 2018, at 11:39 AM, Blake Carver > wrote: > > > WARNING: FAILED SelectChannelConnector at 0.0.0.0 :8082: java.net.BindException: Address already in use > > Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. > > > > ________________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Neal, Rick > > Sent: Monday, November 12, 2018 11:30:07 AM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] 2.5 install issue > > Good morning, > > I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. > > I am now trying to replicate it on my production server. > > After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: > > { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } > > > The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt > > That file mentions that an address is already in use. (I append it to the bottom). > > I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. > > I appreciate whatever advice you have. > > Rick > > ~~~~~~~~~~~~~~~~~~~~~~~ > > I see this in the archivesspace.out file > > Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized > INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war > Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed > WARNING: FAILED SelectChannelConnector at 0.0.0.0 :8082: java.net.BindException: Address already in use > > This is the complete aspace_diagnostic_1542032577.txt file > > "cpu_count": 2, > "exception": { > "msg": "Address already in use", > "backtrace": [ > "sun.nio.ch.Net.bind0(Native Method)", > "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", > "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", > "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", > "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", > "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", > "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", > "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", > "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", > "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", > "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", > "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", > "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", > "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", > "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", > "launcher.launcher.start_server(launcher/launcher.rb:92)", > "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", > "launcher.launcher.main(launcher/launcher.rb:179)", > "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", > "launcher.launcher.
(launcher/launcher.rb:261)", > "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", > "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", > "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", > "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", > "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", > "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", > "org.jruby.Main.internalRun(org/jruby/Main.java:305)", > "org.jruby.Main.run(org/jruby/Main.java:232)", > "org.jruby.Main.main(org/jruby/Main.java:204)" > ] > } > } > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6102 bytes Desc: not available URL: From sdm7g at virginia.edu Tue Nov 13 14:22:58 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 13 Nov 2018 19:22:58 +0000 Subject: [Archivesspace_Users_Group] OAI [ was: 2.5 install issue ] In-Reply-To: References: <200589CE-F587-4006-AE58-B49244231581@virginia.edu> <1F81B46B-36F3-4835-B0AE-F53927B3712D@virginia.edu> Message-ID: :repo_codes are the repo_codes from the repository schema which is labeled ?Repository short name? in the staff webapp. Not the number of the repository. So, for example, we have this config for OAI sets: AppConfig[:oai_sets] = { 'uva-sc' => { :repo_codes => [ 'uva-sc' ], :description => 'Albert and Shirley Small Special Collections Library' }, 'uva-hs' => { :repo_codes => [ 'uva-hs' ], :description => 'Claude Moore Health Sciences Library' }, 'uva-law' => { :repo_codes => [ 'uva-law' ], :description => 'Arthur J. Morris Law Library Special Collections' }, 'uva-cnhi' => { :repo_codes => [ 'uva-cnhi' ], :description => 'The Eleanor Crowder Bjoring Center for Nursing Historical Inquiry' } } > On Nov 13, 2018, at 1:49 PM, Neal, Rick wrote: > > Thanks to everyone. It is up and working. The oai/sample is working, at least on campus. > > We have 2 repositories. One for our Special Collections and one for the Law School. > > https://archives.richmond.edu/repositories/4 > https://archives.richmond.edu/repositories/5 > > I have never worked with setting up oai before and I am wondering how the ?scraper? determines which repository to scrape? Do I need to set up 2 sets (1 for each repository)? > > Would setting up 2 sets look something like this?: > > AppConfig[:oai_sets] = { > 'repository_set' => { > :repo_codes => ['4'], > :description => "Special Collections Repository", > }, > 'repository_set' => { > :repo_codes => ['5'], > :description => "Law School Repository", > }, > } > > Thanks! > > Rick Neal > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > # OAI configuration options > AppConfig[:oai_repository_name] = 'ArchivesSpace OAI Provider' > AppConfig[:oai_proxy_url] = 'http://aspace.richmond.edu:8082/ ' > AppConfig[:oai_record_prefix] = 'oai:archivesspace' > AppConfig[:oai_admin_email] = 'admin at example.com ' > # In addition to the sets based on level of description, you can define OAI Sets > # based on repository codes and/or sponsors as follows > # > # AppConfig[:oai_sets] = { > # 'repository_set' => { > # :repo_codes => ['hello626'], > # :description => "A set of one or more repositories", > # }, > # > # 'sponsor_set' => { > # :sponsors => ['The_Sponsor'], > # :description => "A set of one or more sponsors", > # }, > # } > AppConfig[:oai_ead_options] = {} > # alternate example: AppConfig[:oai_ead_options] = { :include_daos => true, :use_numbered_c_tags => true } > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Rick Neal > Library Applications and Systems Administrator > Boatwright Memorial Library > University of Richmond, VA 23173 > > rneal at richmond.edu > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) > Sent: Monday, November 12, 2018 3:01 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] 2.5 install issue > > > Oops. My error. 8082 is OAI port, not PUI. > Not sure how far back OAI support was initially added. > > > On Nov 12, 2018, at 2:02 PM, Majewski, Steven Dennis (sdm7g) > wrote: > > > The default ports haven?t changed. > Blake transposed digits in his email to 8028, but the error message says 8082, which is the default port for public webapp. > Default port numbers are in common/config/config-defaults.rb: > > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L22-L48 > > > AppConfig[:backend_url] = "http://localhost:8089 " > AppConfig[:frontend_url] = "http://localhost:8080 " > AppConfig[:public_url] = "http://localhost:8081 " > AppConfig[:oai_url] = "http://localhost:8082 " > AppConfig[:solr_url] = "http://localhost:8090 " > AppConfig[:indexer_url] = "http://localhost:8091 " > AppConfig[:docs_url] = "http://localhost:8888 " > > > > > > On Nov 12, 2018, at 1:53 PM, Neal, Rick > wrote: > > Blake, > > What port did it run on before 2.5? > > Rick > > Sent from my iPhone > > On Nov 12, 2018, at 11:39 AM, Blake Carver > wrote: > > > WARNING: FAILED SelectChannelConnector at 0.0.0.0 :8082: java.net.BindException: Address already in use > > Something is running on port 8028 already so ArchivesSpace can't start up since that's being used now. > > > > ________________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Neal, Rick > > Sent: Monday, November 12, 2018 11:30:07 AM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] 2.5 install issue > > Good morning, > > I successfully upgraded our version of ArchiveSpace on my test server to version 2.5 with no issues. > > I am now trying to replicate it on my production server. > > After my upgrade I restarted the service and the staff and public interfaces won?t display in a browser although the backend does: > > { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.5.0" } > > > The archivesspace.out log had this in it: A trace file has been written to the following location: /tmp/aspace_diagnostic_1542039282.txt > > That file mentions that an address is already in use. (I append it to the bottom). > > I did not use the new config.rb file because I use virtualhosts to give unique urls for ArchivesSpace to use. The only thing in my config.rb file that is uncommented is the line for database access. I have been using it this way for years now and there was no issue with the recent test server upgrade. > > I appreciate whatever advice you have. > > Rick > > ~~~~~~~~~~~~~~~~~~~~~~~ > > I see this in the archivesspace.out file > > Nov 12, 2018 11:14:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized > INFO: started o.e.j.w.WebAppContext{/,file:/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war > Nov 12, 2018 11:14:42 AM org.eclipse.jetty.util.component.AbstractLifeCycle setFailed > WARNING: FAILED SelectChannelConnector at 0.0.0.0 :8082: java.net.BindException: Address already in use > > This is the complete aspace_diagnostic_1542032577.txt file > > "cpu_count": 2, > "exception": { > "msg": "Address already in use", > "backtrace": [ > "sun.nio.ch.Net.bind0(Native Method)", > "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:463)", > "sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)", > "sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:223)", > "sun.nio.ch.ServerSocketAdaptor.bind(sun/nio/ch/ServerSocketAdaptor.java:74)", > "org.eclipse.jetty.server.nio.SelectChannelConnector.open(org/eclipse/jetty/server/nio/SelectChannelConnector.java:182)", > "org.eclipse.jetty.server.AbstractConnector.doStart(org/eclipse/jetty/server/AbstractConnector.java:311)", > "org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(org/eclipse/jetty/server/nio/SelectChannelConnector.java:260)", > "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", > "org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:283)", > "org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)", > "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)", > "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)", > "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)", > "launcher.launcher.invokeOther148:start(launcher/launcher.rb:92)", > "launcher.launcher.start_server(launcher/launcher.rb:92)", > "launcher.launcher.invokeOther341:start_server(launcher/launcher.rb:179)", > "launcher.launcher.main(launcher/launcher.rb:179)", > "launcher.launcher.invokeOther454:main(launcher/launcher.rb:261)", > "launcher.launcher.
(launcher/launcher.rb:261)", > "java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle.java:599)", > "org.jruby.Ruby.runScript(org/jruby/Ruby.java:827)", > "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:746)", > "org.jruby.Ruby.runNormally(org/jruby/Ruby.java:764)", > "org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:577)", > "org.jruby.Main.doRunFromMain(org/jruby/Main.java:417)", > "org.jruby.Main.internalRun(org/jruby/Main.java:305)", > "org.jruby.Main.run(org/jruby/Main.java:232)", > "org.jruby.Main.main(org/jruby/Main.java:204)" > ] > } > } > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6102 bytes Desc: not available URL: From mpaquette at smith.edu Tue Nov 13 14:40:14 2018 From: mpaquette at smith.edu (Michelle Paquette) Date: Tue, 13 Nov 2018 14:40:14 -0500 Subject: [Archivesspace_Users_Group] Using ASpace event records to track digitization work? In-Reply-To: References: Message-ID: At my former institution we used the "Capture" event to track capture of born digital, using the Outcome field to specify whether the capture was successful, partially successful, or unsuccessful and detailing where the captured material was now stored and any associated files related to the capture report. But we weren't using events to note digitization of analog material. I'd be happy to connect anyone to the Digital Archivist there if they want to know more. Michelle On Tue, Nov 13, 2018 at 2:06 PM Lara Friedman-Shedlov wrote: > I have been using events in ASpace to record work done on born digital > collection materials. So far I've just been creating events to indicate > completion of ingest and processing. However, so far we haven't really > figured out whether it is actually useful or what exactly we can do with > this info, so I'd be interested in hearing from others. > > / Lara Friedman-Shedlov > > On Mon, Nov 12, 2018 at 12:38 PM Clemens, Alison > wrote: > >> Dear colleagues, >> >> >> >> I?m writing to ask if anyone is using ArchivesSpace event records to >> track digitization work performed on collection materials. For example, I >> could see indicating digitization status by attaching event records to >> particular archival components and/or resources. If you?re doing something >> like this, would you mind please sharing the details of how you?ve set this >> up? >> >> >> >> Additionally, I?d love to hear if folks using other ArchivesSpace data >> elements to indicate specific details of digitization efforts (e.g., if >> digitization was unsuccessful due to fragility, etc.). >> >> >> >> I?ve looked through past listserv digests and haven?t found anything >> quite along these lines, but I?d be grateful to hear of any experiences you >> might have with this or similar efforts! >> >> >> >> With thanks, >> >> Alison >> >> >> >> Alison Clemens >> >> Assistant Head of Arrangement and Description >> >> Manuscripts & Archives, Yale University Library >> >> P.O. Box 208240 >> >> New Haven, CT 06520-8240 >> >> 203-432-9029 >> >> alison.clemens at yale.edu >> >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > _________________________________ > > Lara D. Friedman-Shedlov (She/Her/Hers) > Kautz Family YMCA Archives | University of > Minnesota Libraries > ldfs at umn.edu | 612.626.7972 | > > [image: www.facebook.com/IHRCA] [image: > https://twitter.com/yarchives] > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Michelle Paquette Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Nov 14 08:50:29 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 14 Nov 2018 13:50:29 +0000 Subject: [Archivesspace_Users_Group] Question re: Including Unpublished in EAD/PDF In-Reply-To: References: Message-ID: Hi Larry, We tried to reproduce your issue on the current version of ArchivesSpace and on version 2.3.2 since you indicated that?s what you?re using. What we expected to be included in the PDF based on published status and whether or not we checked the option to include unpublished content matched up in all cases. Are you still experiencing this issue? If you are, there may be something specific to your data going on. (You mention having brought the EAD in via AT, which is definitely common, but perhaps there?s something more unusual going on.) In that case, please email us at ArchivesSpaceHome at lyrasis.org and we can determine if a tech support ticket can help ferret out what?s going on. 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 Larry Weimer Sent: Saturday, November 10, 2018 5:40 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Question re: Including Unpublished in EAD/PDF Hi all, I had occasion recently to run a "Print to PDF" of one of our resources that includes several series that are "unpublished." I wanted the unpublished this time so I checked the "include unpublished" box. But the PDF did not include them. I found this was not unique to the particular resource I first ran. I also found that the unpublished was not included in the EADXML even when checked to include. I'm running version 2.3.2. These records had been migrated from Archivists Toolkit (where the series had been checked as "internal only.") Has anyone else experienced this? Any thoughts or guidance on this? Thanks! Larry Weimer Head of Archival Processing New-York Historical Society [http://email.nyhscommunications.org/email/2019/Footer_HarryPotter2_396x150.jpg] -------------- 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 blake.carver at lyrasis.org Wed Nov 14 09:06:39 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 14 Nov 2018 14:06:39 +0000 Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute In-Reply-To: References: Message-ID: Hi Alan, Did you ever get this one figured out? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Huebschen, Alan M Sent: Tuesday, November 6, 2018 9:38:47 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute Good morning everyone, In my attempts to secure our installation of ArchivesSpace, I?ve run into an issue setting the ?Set-Cookie? attribute through Apache. I?m currently routing ArchiveSpace through Apache for SSL as dictated in the HTTPS readme file, but it appears that ArchivesSpace only sees the http connection and does not set the Secure attribute. I?ve attempted to force the attribute to set with Apache but none of the settings changes seem to work when it comes to set-cookie (other attributes do change when set in Apache). Is there a way to force this attribute to be set properly? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 From ahueb2 at uis.edu Wed Nov 14 10:17:42 2018 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Wed, 14 Nov 2018 15:17:42 +0000 Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute In-Reply-To: References: Message-ID: <9152d5fa64434db99b2d616afa7e8c65@uismbx02.uisad.uis.edu> I was unable to figure out how to get Set-Cookie to display the secure attribute. I also examined other ArchivesSpace installations using HTTPS listed at http://archivesspace.org/community/whos-using-archivesspace and I was unable to find any that had the attribute set. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Wednesday, November 14, 2018 8:07 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Set-Cookie: Secure attribute Hi Alan, Did you ever get this one figured out? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Huebschen, Alan M Sent: Tuesday, November 6, 2018 9:38:47 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute Good morning everyone, In my attempts to secure our installation of ArchivesSpace, I've run into an issue setting the "Set-Cookie" attribute through Apache. I'm currently routing ArchiveSpace through Apache for SSL as dictated in the HTTPS readme file, but it appears that ArchivesSpace only sees the http connection and does not set the Secure attribute. I've attempted to force the attribute to set with Apache but none of the settings changes seem to work when it comes to set-cookie (other attributes do change when set in Apache). Is there a way to force this attribute to be set properly? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From Joshua.D.Shaw at dartmouth.edu Wed Nov 14 12:11:35 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 14 Nov 2018 17:11:35 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI In-Reply-To: References: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu>, Message-ID: Digging up an old thread. Has anyone successfully overridden/extended any of the methods in the public models via a plugin? I'm trying to change a few things in /public/app/models/resource.rb, but have had zero luck. I don't really want to do a custom build at this point, though I suppose I could venture down that road. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Thursday, May 17, 2018 9:10 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hopefully someone else can chime in with an actual answer about how to do this via a plugin, but outside of the views, I've had more success overriding things in the PUI with a custom build. And with the citation feature, you might also need to check out this bit, which is where the URL + timestamp text is added: https://github.com/archivesspace/archivesspace/blob/33a433f4df55c5ee4a21128825529bb9a1a4c023/public/app/models/record.rb#L331-L333 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin Clair Sent: Thursday, May 17, 2018 7:33:57 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven?t been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Wed Nov 14 12:19:18 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Wed, 14 Nov 2018 17:19:18 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI In-Reply-To: References: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu>, Message-ID: Hi, I did overrides and extensions of models, controllers, and concerns for Harvard, mostly in the plugin_init.rb (https://github.com/harvard-library/aspace-hvd-pui/blob/master/public/plugin_init.rb) I don't know if I did them the "best" way, but they work ! >smile< hth, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Wednesday, November 14, 2018 12:12 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Digging up an old thread. Has anyone successfully overridden/extended any of the methods in the public models via a plugin? I'm trying to change a few things in /public/app/models/resource.rb, but have had zero luck. I don't really want to do a custom build at this point, though I suppose I could venture down that road. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Thursday, May 17, 2018 9:10 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hopefully someone else can chime in with an actual answer about how to do this via a plugin, but outside of the views, I've had more success overriding things in the PUI with a custom build. And with the citation feature, you might also need to check out this bit, which is where the URL + timestamp text is added: https://github.com/archivesspace/archivesspace/blob/33a433f4df55c5ee4a21128825529bb9a1a4c023/public/app/models/record.rb#L331-L333 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kevin Clair > Sent: Thursday, May 17, 2018 7:33:57 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven't been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Nov 14 12:22:40 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 14 Nov 2018 17:22:40 +0000 Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute In-Reply-To: <9152d5fa64434db99b2d616afa7e8c65@uismbx02.uisad.uis.edu> References: <9152d5fa64434db99b2d616afa7e8c65@uismbx02.uisad.uis.edu> Message-ID: Hi Alan, We're going to put a tech support ticket on this for you. You'll see another message about that directly to you in a minute. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Huebschen, Alan M Sent: Wednesday, November 14, 2018 10:18 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Set-Cookie: Secure attribute I was unable to figure out how to get Set-Cookie to display the secure attribute. I also examined other ArchivesSpace installations using HTTPS listed at http://archivesspace.org/community/whos-using-archivesspace and I was unable to find any that had the attribute set. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Wednesday, November 14, 2018 8:07 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Set-Cookie: Secure attribute Hi Alan, Did you ever get this one figured out? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Huebschen, Alan M Sent: Tuesday, November 6, 2018 9:38:47 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Set-Cookie: Secure attribute Good morning everyone, In my attempts to secure our installation of ArchivesSpace, I've run into an issue setting the "Set-Cookie" attribute through Apache. I'm currently routing ArchiveSpace through Apache for SSL as dictated in the HTTPS readme file, but it appears that ArchivesSpace only sees the http connection and does not set the Secure attribute. I've attempted to force the attribute to set with Apache but none of the settings changes seem to work when it comes to set-cookie (other attributes do change when set in Apache). Is there a way to force this attribute to be set properly? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 _______________________________________________ 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 Joshua.D.Shaw at dartmouth.edu Wed Nov 14 12:22:44 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 14 Nov 2018 17:22:44 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI In-Reply-To: References: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu>, , Message-ID: I'll give it a shot this way. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Fox, Bobbi Sent: Wednesday, November 14, 2018 12:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hi, I did overrides and extensions of models, controllers, and concerns for Harvard, mostly in the plugin_init.rb (https://github.com/harvard-library/aspace-hvd-pui/blob/master/public/plugin_init.rb) I don?t know if I did them the ?best? way, but they work ! >smile< hth, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Wednesday, November 14, 2018 12:12 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Digging up an old thread. Has anyone successfully overridden/extended any of the methods in the public models via a plugin? I'm trying to change a few things in /public/app/models/resource.rb, but have had zero luck. I don't really want to do a custom build at this point, though I suppose I could venture down that road. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Thursday, May 17, 2018 9:10 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hopefully someone else can chime in with an actual answer about how to do this via a plugin, but outside of the views, I've had more success overriding things in the PUI with a custom build. And with the citation feature, you might also need to check out this bit, which is where the URL + timestamp text is added: https://github.com/archivesspace/archivesspace/blob/33a433f4df55c5ee4a21128825529bb9a1a4c023/public/app/models/record.rb#L331-L333 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kevin Clair > Sent: Thursday, May 17, 2018 7:33:57 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven?t been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Wed Nov 14 12:24:12 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Wed, 14 Nov 2018 17:24:12 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI In-Reply-To: References: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu>, , Message-ID: Feel free to ask me questions off-list. (That goes for anyone else who's interested; I just don't want to add to list clutter). Cheers, Bobbi bobbi_fox at harvard.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Wednesday, November 14, 2018 12:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI I'll give it a shot this way. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Fox, Bobbi > Sent: Wednesday, November 14, 2018 12:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hi, I did overrides and extensions of models, controllers, and concerns for Harvard, mostly in the plugin_init.rb (https://github.com/harvard-library/aspace-hvd-pui/blob/master/public/plugin_init.rb) I don't know if I did them the "best" way, but they work ! >smile< hth, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Joshua D. Shaw Sent: Wednesday, November 14, 2018 12:12 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Digging up an old thread. Has anyone successfully overridden/extended any of the methods in the public models via a plugin? I'm trying to change a few things in /public/app/models/resource.rb, but have had zero luck. I don't really want to do a custom build at this point, though I suppose I could venture down that road. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Thursday, May 17, 2018 9:10 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hopefully someone else can chime in with an actual answer about how to do this via a plugin, but outside of the views, I've had more success overriding things in the PUI with a custom build. And with the citation feature, you might also need to check out this bit, which is where the URL + timestamp text is added: https://github.com/archivesspace/archivesspace/blob/33a433f4df55c5ee4a21128825529bb9a1a4c023/public/app/models/record.rb#L331-L333 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kevin Clair > Sent: Thursday, May 17, 2018 7:33:57 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven't been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Nov 14 12:34:41 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 14 Nov 2018 17:34:41 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI In-Reply-To: References: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu>, , , Message-ID: For the record, Bobbi's method works! I think it might be that you need to nest the overrides for the models in Rails.application.config.after_initialize jds ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Fox, Bobbi Sent: Wednesday, November 14, 2018 12:24 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Feel free to ask me questions off-list. (That goes for anyone else who?s interested; I just don?t want to add to list clutter). Cheers, Bobbi bobbi_fox at harvard.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Wednesday, November 14, 2018 12:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI I'll give it a shot this way. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Fox, Bobbi > Sent: Wednesday, November 14, 2018 12:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hi, I did overrides and extensions of models, controllers, and concerns for Harvard, mostly in the plugin_init.rb (https://github.com/harvard-library/aspace-hvd-pui/blob/master/public/plugin_init.rb) I don?t know if I did them the ?best? way, but they work ! >smile< hth, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Joshua D. Shaw Sent: Wednesday, November 14, 2018 12:12 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Digging up an old thread. Has anyone successfully overridden/extended any of the methods in the public models via a plugin? I'm trying to change a few things in /public/app/models/resource.rb, but have had zero luck. I don't really want to do a custom build at this point, though I suppose I could venture down that road. Thanks! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Thursday, May 17, 2018 9:10 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] overriding default citation text in the PUI Hopefully someone else can chime in with an actual answer about how to do this via a plugin, but outside of the views, I've had more success overriding things in the PUI with a custom build. And with the citation feature, you might also need to check out this bit, which is where the URL + timestamp text is added: https://github.com/archivesspace/archivesspace/blob/33a433f4df55c5ee4a21128825529bb9a1a4c023/public/app/models/record.rb#L331-L333 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kevin Clair > Sent: Thursday, May 17, 2018 7:33:57 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven?t been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Wed Nov 14 15:15:31 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Wed, 14 Nov 2018 20:15:31 +0000 Subject: [Archivesspace_Users_Group] Using ASpace event records to track digitization work? In-Reply-To: References: Message-ID: We?ve been toying with the idea of using Events to record digitization and metadata review/approval status information for a large data migration/re-architecture project as well as record these elements going forward. The customer?s old system tracked project and item status information, metadata management, QA, repository functions, and public interface deployment in a single system and wants to retain as much of that functionality in as few new systems as possible ? the old system/workflows performed lots of assurance checks before content was deemed ready to be released for exhibit building. I?ve added ?digitized? and ?metadata validated? to the event_event_type controlled vocabulary list as an experiment, combined with the label ?Digitized? within the Date subrecord. The desire is to have ASpace be the authoritative store for these trigger events so the customer knows when content is ready for release, or to blacklist objects that are not yet ready or otherwise quarantined. We?re getting close to re-purposing ASpace as a DAMS, but trying hard to record only essential/enduring archival metadata in ASpace, not project management/QA information that likely has a limited retention value. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: Michelle Paquette Sent: Tuesday, November 13, 2018 2:40 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Using ASpace event records to track digitization work? At my former institution we used the "Capture" event to track capture of born digital, using the Outcome field to specify whether the capture was successful, partially successful, or unsuccessful and detailing where the captured material was now stored and any associated files related to the capture report. But we weren't using events to note digitization of analog material. I'd be happy to connect anyone to the Digital Archivist there if they want to know more. Michelle On Tue, Nov 13, 2018 at 2:06 PM Lara Friedman-Shedlov > wrote: I have been using events in ASpace to record work done on born digital collection materials. So far I've just been creating events to indicate completion of ingest and processing. However, so far we haven't really figured out whether it is actually useful or what exactly we can do with this info, so I'd be interested in hearing from others. / Lara Friedman-Shedlov On Mon, Nov 12, 2018 at 12:38 PM Clemens, Alison > wrote: Dear colleagues, I?m writing to ask if anyone is using ArchivesSpace event records to track digitization work performed on collection materials. For example, I could see indicating digitization status by attaching event records to particular archival components and/or resources. If you?re doing something like this, would you mind please sharing the details of how you?ve set this up? Additionally, I?d love to hear if folks using other ArchivesSpace data elements to indicate specific details of digitization efforts (e.g., if digitization was unsuccessful due to fragility, etc.). I?ve looked through past listserv digests and haven?t found anything quite along these lines, but I?d be grateful to hear of any experiences you might have with this or similar efforts! With thanks, Alison Alison Clemens Assistant Head of Arrangement and Description Manuscripts & Archives, Yale University Library P.O. Box 208240 New Haven, CT 06520-8240 203-432-9029 alison.clemens at yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- _________________________________ Lara D. Friedman-Shedlov (She/Her/Hers) Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [www.facebook.com/IHRCA] [https://twitter.com/yarchives] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Michelle Paquette Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpeterson at smith.edu Wed Nov 14 15:20:10 2018 From: cpeterson at smith.edu (Christie Peterson) Date: Wed, 14 Nov 2018 15:20:10 -0500 Subject: [Archivesspace_Users_Group] Implementing PUI Message-ID: Hi, We're looking at implementing the PUI much sooner than we had previously anticipated. I'm aware of this pre-launch checklist , but I'm wondering if others who have tread this ground before us have other resources (project charters/plans, checklists, etc.) that you could share with us. Many thanks in advance, Christie -- Christie S. Peterson Head of Technical Services for Special Collections Smith College cpeterson at smith.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Nov 14 16:21:34 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 14 Nov 2018 21:21:34 +0000 Subject: [Archivesspace_Users_Group] position announcement: ArchivesSpace Community Engagement Coordinator Message-ID: We're seeking the next Community Engagement Coordinator for ArchivesSpace. This position is on the frontlines of the program, working directly with individual users and groups of users. Some of the key responsibilities include organizing online and in person events, managing our communications program, and working with community groups responsible for testing, user documentation and training activities. The person in this position plays a tremendous part in helping connect users to each other and works closely with our community to make ArchivesSpace better for everyone. The full job posting is attached. All applications must include a cover letter and resume and be submitted through the new LYRASIS online hiring portal; the online listing for this position is at https://lyrasis.isolvedhire.com/jobs/43961.html. (Applicants can upload separate files for a cover letter and resume to the portal, or one file containing everything.) Applications received by December 7 will receive priority consideration. I look forward to filling this important position on the ArchivesSpace team. Please feel free to contact me if you have any questions about the position. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ASpaceComm Eng Coord JobDesc-201811.pdf Type: application/pdf Size: 690760 bytes Desc: ASpaceComm Eng Coord JobDesc-201811.pdf URL: From Christine.Kim at lyrasis.org Wed Nov 14 16:54:57 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 14 Nov 2018 21:54:57 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_tac] ASpace Kansas City Regional Forum - Registration is now open! In-Reply-To: References: Message-ID: Dear ArchivesSpace community, We're thrilled to share our finalized program for the upcoming Kansas City Regional Forum on November 30th! Register for the ArchivesSpace Regional Forum in Kansas City! We do still have an open poll for the Choose Your ASpace Adventure Workshop, which is available for selection during registration check-out. The poll for this workshop closes on Friday (November 16) but we will continue to accept registrations beyond that date. Please let me know if you have any questions. Thanks! Best wishes, Christine Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org On Behalf Of Christine Kim Sent: Friday, November 9, 2018 2:09 PM Subject: Re: [Archivesspace_tac] ASpace Kansas City Regional Forum - Registration is now open! Dear ArchivesSpace Community, The ASpace Kansas City Regional Forum is just 3 weeks away! Registration is currently open! We are thrilled to share that during this forum, we plan to offer a session in the afternoon that highlights the diverse phases of ArchivesSpace implementation. During this session, we invite organizations to provide a quick 5 minute overview on where their institution is currently at with implementation, as well as any challenges they're facing as they move forward into the next phase. Following the overview, we will open up for a 10-15 minute group conversation sharing any insights, ideas, or lessons learned to help you navigate into your next stage. We are looking to represent a diverse spectrum of community organizations, including public libraries, academic institutions, museums, religious organizations, and historical societies. We encourage smaller institutions as well as lone arrangers to consider participating in this session. Please let me know if you are attending the forum and would be interested in participating in this session. Program specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Thanks! Best wishes, Christine Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org > On Behalf Of Christine Kim Sent: Friday, October 26, 2018 8:21 AM Subject: [Archivesspace_tac] ASpace Kansas City Regional Forum - Registration is now open! Join us for the ArchivesSpace Regional Forum in Kansas City! 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. Registration is now open! [https://archivesspace.atlassian.net/wiki/download/attachments/728662017/KC-Banner02.jpg?version=1&modificationDate=1539367905411&cacheVersion=1&api=v2&effects=border-simple,blur-border,tape] DETAILS * Location: Midwest Genealogy Center * Date: November 30, 2018 (Friday) * Time: 9am - 5pm * Parking: Parking & Transportation PROGRAM The specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Morning Workshops: The morning will feature two hands-on, engaging workshops. Please register for the workshop you are interested in attending. Each workshop is limited to 15 participants. * Workshop A: Choose Your ASpace Adventure * Instructor: Miloche Kottman, University of Kansas Libraries * The content of this workshop will be determined by a poll presented during registration check-out. Options include: * Option 1: Deep dive of Accession & Reource records: How to create an accession record, all about notes and spawning; How to create a resource record, all about notes, creating multi-level description, adding instance(s) * Option 2: Built-in ArchivesSpace efficiencies: Learn how to use Rapid Data Entry; set up default values for new accession, resource or digital object records; import EAD record with archival objects and merge with brief top-level resource record; controlled value list; default note order; LCNAF Import plugin; Container and Location management * Option 3: Controlling Data in ArchivesSpace: Data cleanup in ArchivesSpace; Cleaning up controlled values list; adding values to controlled values list; creating agent/subject records; merging duplicate agent/subject records * Workshop B: Introduction to Git and GitHub: A hands-on workshop * Instructor: Jamene Brooks-Kieffer, University of Kansas Libraries * Workshop Description: Git is a powerful open source version control tool that was originally designed for software development projects. GitHub is a web-based service that offers the functionality of Git plus additional features that enhance collaboration and project management. The combination of Git and GitHub creates a redundant, transparent, and reproducible work environment. However, accessing items available on GitHub (such as ArchivesSpace source code, documentation, and migration scripts) can be confusing and frustrating without training and practice. This workshop will introduce you to the basics of using Git on the command line, setting up your own GitHub repository, and contributing to projects hosted on GitHub. This workshop will also introduce you to using Markdown for formatting plain text files. You do not need to have any prior knowledge of Git, GitHub, Markdown, or the Unix-style command line to attend. Afternoon program: The afternoon session will highlight stories and experiences through presentations and group discussions. A catered lunch will be provided. * Speaker submissions: Currently accepting submissions! More info here: http://archivesspace.org/archives/3210 REGISTRATION Registration, including the "Workshop A: Choose Your ASpace Adventure" poll, is now open: https://www.eventbrite.com/e/archivesspace-regional-forum-kansas-city-2018-tickets-50618209427 HAPPY HOUR We will kick off the forum on November 29th (the night before) with an optional happy hour at Smokehouse Barbecue. Join us for a casual get together so we can get to know each other over delicious Kansas City barbecue! We'll provide a selection of appetizers to share. You are welcome to purchase your own drinks or additional food. This social activity is open to everyone. QUESTIONS? If you have any questions (or ideas!) related to the regional forums, feel free to email Christine Kim at christine.kim at lyrasis.org. Sincerely, Kansas City Regional Forum Working Group Danielle Butler (Central Arkansas Library System) Marcella Huggard (University of Kansas) Miloche Kottman (University of Kansas) Patrice-Andre Prud'homme (Oklahoma State University) Christine Kim (ArchivesSpace) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 57211 bytes Desc: image002.jpg URL: From racheltrent at gwu.edu Thu Nov 15 14:30:06 2018 From: racheltrent at gwu.edu (Rachel Trent) Date: Thu, 15 Nov 2018 14:30:06 -0500 Subject: [Archivesspace_Users_Group] Implementing PUI In-Reply-To: References: Message-ID: Hi Christie, We just did this here at GW: https://searcharchives.library.gwu.edu. It was a really good experience! We aimed for a minimal process, maximizing as little staff time as possible. For context and for those who aren't Christie (Christie is already very familiar with our context!): We previously published EAD XML files by putting them on our web server. They were linked to style sheets which also sat alongside the XML files on the server. So, it was just files on a server. Our catalog linked to those finding aids, as did our institutional website. And we relied on web search engines to index and search the finding aids. Two weeks ago, we replaced those finding aids with the PUI. *Github public documentation* As part of our PUI project, we documented our local configurations to the ASpace app here: https://github.com/gwu-libraries/aspace-pui/. That repo shows everything we customized in relation to the PUI. *Here are some of our fondest memories and lessons:* 1. A big +1 to Mark's pre-launch checklist recommendation to "Review the use of the 'publish' checkbox in your staff site". This was big work, for which we relied heavily on the API. We made lists of all our resources, compared that to our list of published finding aids, and manually reviewed everything that didn't match. This was great. We found resource records that had never been published, but which we wanted published. We did a light review of everything that would be newly visible to the public, including a double check that there wasn't anything embarrassingly "drafty" or marked as restricted on these finding aids. We tried not to be perfectionists, and that worked really well. We probably spent about three days reconciling the lists of ASpace resource records and published finding aid files. We found that it was best managed with one person coordinating and sending out lists to others to approve what should be published and what shouldn't. We also unpublished large swaths of material, although our choices here were particular to our institution. We unpublished digital objects, accession records, and all unused repositories. We did this using the API, but database changes may have been easier. 2. Agents - People worried that our Agent records might cause private information to get published, like donor contact info. They don't. We also chose to unpublish our staff agent records (aka, our own names). 3. You will absolutely want to search for weird stuff like "test" and "demo". If you're like us, you'll find stuff. So much stuff. Sometimes hard to find. Often with the "published" checkbox checked. Our favorite: [image: blahdeeblah.JPG] 4. We came to terms with the fact that our subject headings need a lot of work. We weighed wether to fix them before going live or after, and decided to do it after. Since we had flat XML finding aids before, our subject headings didn't really matter that much; they weren't surfaced as facets. We decided that we can live with less-than-ideal subject headings for now. I expect many other institutions would make the choice to fix up their subject headings before launching. If so, the API would come in very handy here, too. 5. For now, we've done redirects from the old finding aids to the new ones in ArchivesSpace. We did a lot of internal outreach to make sure that people understood that the PUI still creates "finding aids"/"collection guides", and that the old finding aid URLs have a corresponding new URL. 6. If your finding aids are being harvested into ArchiveGrid, check that everything will transition smoothly. It may be an opportunity to change your method of harvest. We left ours in place as-is, because it was pulling from the MARC records that we send to WorldCat, and the ArchivesSpace PUI doesn't impact that process at all. 7. One last warning: we had to do some clean up that involved moving resource records between repositories. That went poorly, and broke stuff. Things were very weird for a while, because our index broke and then we couldn't determine if it was fixed or not for a while. Lyrasis was very helpful during this period. 8. Because part of our backend system would now be public, we realized that we needed to improve security on our accounts. 9. We archived the old finding aids in Archive-It, and are keeping a (non-public) copy of the XML finding aids for one year. 10. We couldn't have done any of this without the leadership and vision of our public services librarian (Leah Richardson!), who was in full support of embracing change. *Project progression:* 1. June: Two 2-week sprints to configure the PUI and do most of the cleaning of our data, at the end of which we launched what we branded as the "beta" PUI. 2. June - October: The "beta" PUI existed alongside our XML finding aids for several months (the "summer", which ended up extending into October). During that time, we got a feel for how much it would "cost" to maintain an application that not only contains our staff system, but also now our front-facing system (esp from a sys admin perspective). We weighed that against the improvements that ASpace would bring us. This wasn't too formal. Lots of talking and checking in. No metrics or charts. We decided in the end to move forward. We also used this time to ask staff to use the PUI instead of the XML finding aids, with two purposes in mind: (1) get staff trained, and (2) locate and fix messy data (e.g., if they saw any more "Mr. Blah Dee Blahs", everyone was supposed to fix it on the spot). 3. October: A 1-week sprint to finalize the implementation of the PUI, replacing the XML finding aids. We finished in our Halloween costumes. (Special thanks to one colleague in particular who stayed late, in head-to-toe costume!) Best, Rachel and Leah Rachel Trent Digital Services Manager Special Collections Research Center Gelman Library, George Washington University 2130 H Street NW Washington DC 20052 202.994.4824 racheltrent at gwu.edu On Wed, Nov 14, 2018 at 3:20 PM Christie Peterson wrote: > Hi, > > We're looking at implementing the PUI much sooner than we had previously > anticipated. I'm aware of this pre-launch checklist > , > but I'm wondering if others who have tread this ground before us have other > resources (project charters/plans, checklists, etc.) that you could share > with us. > > Many thanks in advance, > > Christie > > -- > Christie S. Peterson > Head 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: blahdeeblah.JPG Type: image/jpeg Size: 29119 bytes Desc: not available URL: From matt.lawson at uni.edu Fri Nov 16 09:29:59 2018 From: matt.lawson at uni.edu (Matthew Lawson) Date: Fri, 16 Nov 2018 08:29:59 -0600 Subject: [Archivesspace_Users_Group] Alma Integration In-Reply-To: References: <5BD9BBB2.1030103@rice.edu> Message-ID: Benn- At UNI we use Primo (newUI, back office), Alma and AS 2.3.2 I would like to evaluate our options for getting AS data displayed to the public. I would like to hear about how you do it. OAI pipe? -Matt University of Northern Iowa On Wed, Oct 31, 2018 at 9:51 AM Benn Joseph wrote: > We?d be interested at Northwestern as well, but I should mention also that > we are an Alma/Primo institution and have actually avoided any kind of > ASpace/Alma integration, preferring to send finding aid records from ASpace > directly to Primo. I can share more about this if anyone is interested! > > > > --Benn > > > > *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 < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Harmeyer, > Neal A > *Sent:* Wednesday, October 31, 2018 9:43 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > We are very interested at Purdue University. > > > > Thank you! > > Neal > > -- > > Neal Harmeyer > > Digital Archivist > > Purdue University Archives and Special Collections > > harmeyna at purdue.edu > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Joshua > D. Shaw > *Sent:* Wednesday, October 31, 2018 10:31 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > And at Dartmouth - though we are in the early stages of switching to Alma, > with an initial rollout June 2019. > > > > Joshua > > > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Amanda Focke > *Sent:* Wednesday, October 31, 2018 10:26 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > Interested here at Rice University! > > Thanks! > Amanda Focke > afocke at rice.edu > > On 10/31/2018 8:45 AM, Hilton, Adrien wrote: > > Hi All, > > > > At Houghton Library, part of the Harvard Library, we too are interested in > ArchivesSpace/Alma integration. > > > > In terms of functionality for resource description, we looked a bit at the > Denver plug-in and like the type of data exchange it offers between the > ArchivesSpace resource record and the Alma Bib and Holdings records using > the MMS ID. We could also envision the exchange working the other way, > starting from the Alma record and looking to ArchivesSpace for a resource > record with that MMS ID (in a locally specified field), creating a resource > if non-existent or updating if existent. > > > > We would also like to think through subject and agent access points and > keeping those up-to-date in both systems (using URIs), and optimally, > up-to-date with the authority file (functionality that Alma currently > offers). > > > > Lastly, exchanging and maintaining container inventories and barcodes > (instances in ArchivesSpace and item records in Alma) across the systems is > another area of functionality we?d like to explore. > > > > We?d like to host a conference call for interested parties. Can folks > respond if they are interested in taking part? If there?s enough momentum, > I?ll send around a Doodle poll with some available times. > > > > Best wishes, > > Adrien, Susan, and Vernica > > Houghton Library > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > > *On Behalf Of * > Chad Mills > *Sent:* Wednesday, October 24, 2018 2:30 PM > *To:* Archivesspace Users Group > > > *Subject:* Re: [Archivesspace_Users_Group] Alma Integration > > > > Hi all, > > > > Attached is the reference architecture and test/sample implementation > architecture we developed at Rutgers. We have not implemented this yet. > > > > Best, > > Chad > > > > *From:* Chad Mills > *Sent:* Friday, October 12, 2018 8:43 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* RE: [Archivesspace_Users_Group] Alma Integration > > > > Hi, > > > > We are interested! At Rutgers earlier this year we developed a reference > architecture for our Special Collections. We tested the reference > architecture by creating an implementation architecture using Alma, Primo, > ArchiveSpace and a generic repository framework. In June we migrated to > Alma so we will be looking to integrate ArchiveSpace with Alma in the near > future using our the reference architecture as a blue print. I?ll see if I > can share that reference architecture with the group. > > > > Best, > > Chad > > > > ------------------------------------- > Chad Mills > Digital Library Architect > Rutgers University Libraries > Phone: 848.932.5924 > Cell: 732.309.8538 > ------------------------------------- > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Megan > Firestone > *Sent:* Wednesday, October 10, 2018 1:34 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Alma Integration > > > > Hi, > > > > We us Alma as our library ILS here, so we have been looking at the > possibility of integrating Alma and ArchivesSpace. I was curious if anyone > else is interested in this type of integration and if there is any work > being done? > > > > Thanks! > > Megan > > > -- > > Megan M. Firestone > Archivist and Public Services Librarian > Munday Library > St. Edward's University > 3001 S. Congress Ave. > Austin, TX 78704 > 512.428.1047 > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > -- > Amanda Focke, CA, DAS > Asst. Head of Woodson Research Center > Fondren Library > Rice University > 6100 Main St. MS-44 > Houston, TX 77005 > afocke at rice.edu | 713-348-2124 > http://library.rice.edu/woodson > > _______________________________________________ > 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 Terry.Brady at georgetown.edu Fri Nov 16 13:53:42 2018 From: Terry.Brady at georgetown.edu (Terry Brady) Date: Fri, 16 Nov 2018 10:53:42 -0800 Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes Message-ID: The Georgetown University Library uses DSpace to publish digital objects for our archival collections. In ArchivesSpace, we will be constructing DAO objects that link to specific DSpace items. At the ArchivesSpace resource/collection level, we would like to display a note that indicates that digital objects exist within the resource. We would like that note to link to a DSpace collection. We are able to create a scope and content note that contains a hyperlink to a DSpace collection. Additionally, we would like to display an inline image along with that hyperlink. If we attempt to add html img tags into our scope and content note, we see that ArchivesSpace sanitizes the html and removes the img tags. Is there a way to include inline images within a note (or another object) in ArchivesSpace? So far, we have kept the code changes in our AS instance to a minimum. I suppose that we could create a custom note type and then render that note type on the front end with an inline image. If possible, we would prefer to avoid that level of customization. Do you have any suggestions for how we could solve this problem? Alternatively, we think it could be useful to be able to display DAO thumbnails inline for collection/resource objects. See the following enhancement request: https://archivesspace.atlassian.net/browse/ANW-810 Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From tadams at cshl.edu Fri Nov 16 14:18:20 2018 From: tadams at cshl.edu (Adams, Thomas) Date: Fri, 16 Nov 2018 19:18:20 +0000 Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes In-Reply-To: References: Message-ID: <9924A3758AEDEC48B06A918F5A0175FE9CB200AA@EX-HS-MBX01.cshl.edu> Jerry, You are able to include an image within the resource/collection description. Simply added within the Notes - Scope and Content section, the following tag: For including a link, we use the following construct: http://library.cshl.edu/personal-collections/amos-g-avery/collection-inventory> These two constructs do not get sanitized, like the html construct would. No AS customization is required. I do not see why both would not work together. An example of both is displayed here: http://archivesspace.cshl.edu/repositories/2/resources/8 Hope that helps. -Tom From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Terry Brady Sent: Friday, November 16, 2018 1:54 PM To: archivesspace at googlegroups.com; Archivesspace Users Group Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes The Georgetown University Library uses DSpace to publish digital objects for our archival collections. In ArchivesSpace, we will be constructing DAO objects that link to specific DSpace items. At the ArchivesSpace resource/collection level, we would like to display a note that indicates that digital objects exist within the resource. We would like that note to link to a DSpace collection. We are able to create a scope and content note that contains a hyperlink to a DSpace collection. Additionally, we would like to display an inline image along with that hyperlink. If we attempt to add html img tags into our scope and content note, we see that ArchivesSpace sanitizes the html and removes the img tags. Is there a way to include inline images within a note (or another object) in ArchivesSpace? So far, we have kept the code changes in our AS instance to a minimum. I suppose that we could create a custom note type and then render that note type on the front end with an inline image. If possible, we would prefer to avoid that level of customization. Do you have any suggestions for how we could solve this problem? Alternatively, we think it could be useful to be able to display DAO thumbnails inline for collection/resource objects. See the following enhancement request: https://archivesspace.atlassian.net/browse/ANW-810 Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Terry.Brady at georgetown.edu Fri Nov 16 14:52:29 2018 From: Terry.Brady at georgetown.edu (Terry Brady) Date: Fri, 16 Nov 2018 11:52:29 -0800 Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes In-Reply-To: <9924A3758AEDEC48B06A918F5A0175FE9CB200AA@EX-HS-MBX01.cshl.edu> References: <9924A3758AEDEC48B06A918F5A0175FE9CB200AA@EX-HS-MBX01.cshl.edu> Message-ID: Tom, That is very helpful to know. Thank you! On Fri, Nov 16, 2018 at 11:18 AM Adams, Thomas wrote: > Jerry, > > > > You are able to include an image within the resource/collection > description. Simply added within the Notes - Scope and Content section, the > following tag: > > actuate="onload" show="embed"> > > > > For including a link, we use the following construct: > > > http://library.cshl.edu/personal-collections/amos-g-avery/collection-inventory > > > > > These two constructs do not get sanitized, like the html construct would. > No AS customization is required. I do not see why both would not work > together. > > > > An example of both is displayed here: > > http://archivesspace.cshl.edu/repositories/2/resources/8 > > > > Hope that helps. > > > > -Tom > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Terry > Brady > *Sent:* Friday, November 16, 2018 1:54 PM > *To:* archivesspace at googlegroups.com; Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Styling links in ArchviesSpace > notes > > > > The Georgetown University Library uses DSpace to publish digital objects > for our archival collections. > > > > In ArchivesSpace, we will be constructing DAO objects that link to > specific DSpace items. > > > > At the ArchivesSpace resource/collection level, we would like to display a > note that indicates that digital objects exist within the resource. We > would like that note to link to a DSpace collection. > > > > We are able to create a scope and content note that contains a hyperlink > to a DSpace collection. > > > > Additionally, we would like to display an inline image along with that > hyperlink. > > > > If we attempt to add html img tags into our scope and content note, we see > that ArchivesSpace sanitizes the html and removes the img tags. > > > > Is there a way to include inline images within a note (or another object) > in ArchivesSpace? > > > > So far, we have kept the code changes in our AS instance to a minimum. I > suppose that we could create a custom note type and then render that note > type on the front end with an inline image. If possible, we would prefer > to avoid that level of customization. > > > > Do you have any suggestions for how we could solve this problem? > > > > Alternatively, we think it could be useful to be able to display DAO > thumbnails inline for collection/resource objects. See the following > enhancement request: https://archivesspace.atlassian.net/browse/ANW-810 > > > > > Thanks, Terry > > > > -- > > Terry Brady > > Applications Programmer Analyst > > Georgetown University Library Information Technology > > https://github.com/terrywbrady/info > > > 425-298-5498 (Seattle, WA) > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcaffrey at towson.edu Fri Nov 16 16:03:04 2018 From: jcaffrey at towson.edu (Caffrey, Julia) Date: Fri, 16 Nov 2018 21:03:04 +0000 Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes In-Reply-To: References: <9924A3758AEDEC48B06A918F5A0175FE9CB200AA@EX-HS-MBX01.cshl.edu> Message-ID: Hi All, To add on to the previously suggested solution: Using < extptr> embeds it as an HTML5 , rather than an image (). HTML5 introduced the embed so that a variety of formats can be included. I?m not familiar with AS enough to know why you can?t encode as an image, but I recommend including the following attributes for greater accessibility and to make your code more semantic. Use an aria-label and alt to define the media type and alternative text: If the image is decorative or redundant with text, use alt="" Thanks, Julia Caffrey Web Services Librarian Towson University From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Terry Brady Sent: Friday, November 16, 2018 2:52 PM To: Archivesspace Users Group Cc: archivesspace at googlegroups.com Subject: Re: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes Tom, That is very helpful to know. Thank you! On Fri, Nov 16, 2018 at 11:18 AM Adams, Thomas > wrote: Jerry, You are able to include an image within the resource/collection description. Simply added within the Notes - Scope and Content section, the following tag: For including a link, we use the following construct: http://library.cshl.edu/personal-collections/amos-g-avery/collection-inventory> These two constructs do not get sanitized, like the html construct would. No AS customization is required. I do not see why both would not work together. An example of both is displayed here: http://archivesspace.cshl.edu/repositories/2/resources/8 Hope that helps. -Tom From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Terry Brady Sent: Friday, November 16, 2018 1:54 PM To: archivesspace at googlegroups.com; Archivesspace Users Group Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes The Georgetown University Library uses DSpace to publish digital objects for our archival collections. In ArchivesSpace, we will be constructing DAO objects that link to specific DSpace items. At the ArchivesSpace resource/collection level, we would like to display a note that indicates that digital objects exist within the resource. We would like that note to link to a DSpace collection. We are able to create a scope and content note that contains a hyperlink to a DSpace collection. Additionally, we would like to display an inline image along with that hyperlink. If we attempt to add html img tags into our scope and content note, we see that ArchivesSpace sanitizes the html and removes the img tags. Is there a way to include inline images within a note (or another object) in ArchivesSpace? So far, we have kept the code changes in our AS instance to a minimum. I suppose that we could create a custom note type and then render that note type on the front end with an inline image. If possible, we would prefer to avoid that level of customization. Do you have any suggestions for how we could solve this problem? Alternatively, we think it could be useful to be able to display DAO thumbnails inline for collection/resource objects. See the following enhancement request: https://archivesspace.atlassian.net/browse/ANW-810 Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcaffrey at towson.edu Fri Nov 16 16:05:49 2018 From: jcaffrey at towson.edu (Caffrey, Julia) Date: Fri, 16 Nov 2018 21:05:49 +0000 Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes In-Reply-To: References: <9924A3758AEDEC48B06A918F5A0175FE9CB200AA@EX-HS-MBX01.cshl.edu> Message-ID: Additionally, note that this response did not post to the Google group. I received a failure notification when replying. J From: Caffrey, Julia Sent: Friday, November 16, 2018 4:03 PM To: Archivesspace Users Group Cc: archivesspace at googlegroups.com Subject: RE: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes Hi All, To add on to the previously suggested solution: Using < extptr> embeds it as an HTML5 , rather than an image (). HTML5 introduced the embed so that a variety of formats can be included. I?m not familiar with AS enough to know why you can?t encode as an image, but I recommend including the following attributes for greater accessibility and to make your code more semantic. Use an aria-label and alt to define the media type and alternative text: If the image is decorative or redundant with text, use alt="" Thanks, Julia Caffrey Web Services Librarian Towson University From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Terry Brady Sent: Friday, November 16, 2018 2:52 PM To: Archivesspace Users Group > Cc: archivesspace at googlegroups.com Subject: Re: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes Tom, That is very helpful to know. Thank you! On Fri, Nov 16, 2018 at 11:18 AM Adams, Thomas > wrote: Jerry, You are able to include an image within the resource/collection description. Simply added within the Notes - Scope and Content section, the following tag: For including a link, we use the following construct: http://library.cshl.edu/personal-collections/amos-g-avery/collection-inventory> These two constructs do not get sanitized, like the html construct would. No AS customization is required. I do not see why both would not work together. An example of both is displayed here: http://archivesspace.cshl.edu/repositories/2/resources/8 Hope that helps. -Tom From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Terry Brady Sent: Friday, November 16, 2018 1:54 PM To: archivesspace at googlegroups.com; Archivesspace Users Group Subject: [Archivesspace_Users_Group] Styling links in ArchviesSpace notes The Georgetown University Library uses DSpace to publish digital objects for our archival collections. In ArchivesSpace, we will be constructing DAO objects that link to specific DSpace items. At the ArchivesSpace resource/collection level, we would like to display a note that indicates that digital objects exist within the resource. We would like that note to link to a DSpace collection. We are able to create a scope and content note that contains a hyperlink to a DSpace collection. Additionally, we would like to display an inline image along with that hyperlink. If we attempt to add html img tags into our scope and content note, we see that ArchivesSpace sanitizes the html and removes the img tags. Is there a way to include inline images within a note (or another object) in ArchivesSpace? So far, we have kept the code changes in our AS instance to a minimum. I suppose that we could create a custom note type and then render that note type on the front end with an inline image. If possible, we would prefer to avoid that level of customization. Do you have any suggestions for how we could solve this problem? Alternatively, we think it could be useful to be able to display DAO thumbnails inline for collection/resource objects. See the following enhancement request: https://archivesspace.atlassian.net/browse/ANW-810 Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From CBogen at records.nyc.gov Sat Nov 17 12:12:31 2018 From: CBogen at records.nyc.gov (Bogen, Carly (Records)) Date: Sat, 17 Nov 2018 17:12:31 +0000 Subject: [Archivesspace_Users_Group] Importing Accessions CSVs - linking agents and resources Message-ID: <3B5F069130854D49B95CC2D8921E980C45580D83@MSPWPA-CTWDG1E.cs.nycnet> Hi all, Is there a way to use the accessions CSV import to link the new accession being created to agents, resources and classifications that already exist in the repository? We'd like to be able to add an existing agent uid to a field in the spreadsheet, include a role, and have that automatically link. Same for resources and classifications, only without the role. I can't seem to figure out how to make this work. Thanks for your help! And sorry for the cross-post - this list seems a bit more active than the Google group. -Carly ____________________________________________________________________ Carly Bogen | Manager, Digital Programs Department of Records and Information Services (DORIS) 31 Chambers Street, New York, NY 10007 P: 212-341-6029 | E-mail: cbogen at records.nyc.gov [mailBanner] Follow us on: [acebook] [witter] [umblr] [outube] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1071 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 659 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 353 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 660 bytes Desc: image004.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 672 bytes Desc: image005.jpg URL: From Christine.Kim at lyrasis.org Mon Nov 19 12:39:26 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Mon, 19 Nov 2018 17:39:26 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - November 2018 Message-ID: [ASpaceOrgHome.jpg] November 2018 Update We have some staffing updates, and an opportunity for a new person to join the ArchivesSpace team! An updated digital copy of our ArchivesSpace Member Directory was distributed last week, and we are looking forward to the upcoming Kansas City Regional Forum next week! Read on for more news! Development We expect to release one more update to the ArchivesSpace application before 2018 ends. All community pull requests should be submitted by December 7 to be considered for this release. ArchivesSpace is always interested in more development help. Depending on your interest and availability, we have lots of suggestions for projects small and big that developers and tech-savvy archivists of all experience levels could help with to make ArchivesSpace better for everyone. If you?re interested in writing code and helping with ArchivesSpace development, or if you know someone who might be, please contact Program Manager Christine Di Bella (christine.dibella at lyrasis.org) or Tech Lead Laney McGlohon (laney.mcglohon at lyrasis.org) for more details. Staffing News We have two staffing updates to share with you -- one we share with great pleasure, and the other with sadness. We are very excited to announce that Lora Woodford will now be the Junior Developer for ArchivesSpace. Most recently Lora served as DevOps Specialist based in LYRASIS? Digital Technology Services department. In that role, she participated in a range of technical support activities including responding to ArchivesSpace support tickets, contributing code, and supporting DTS hosting services for ArchivesSpace, Islandora and CollectionSpace. We are very pleased to have Lora now focus on ArchivesSpace development full time in her new role and look forward to the increase in development activity that this change will make possible. It is with regret, however, that we announce that Christine Kim will be leaving her position as ArchivesSpace Community Engagement Coordinator at the end of the year to take a position with the California Digital Library. She will be sorely missed by her fellow team members and the ArchivesSpace community. Christine has created a strong infrastructure for community engagement. She has worked tirelessly to develop innovative opportunities for community members to engage with us and each other such as our blog, webinar, open call series, and regional forums. All of us have greatly benefited from the creativity and optimism that she brings to every activity in which she is involved. Fortunately, Christine will remain in her position through the end of December to help us with programs already scheduled and develop solid plans for those that will continue in 2019 and beyond. We wish Christine Kim well in her future endeavors and look forward to continuing to work with her in the future as a much cherished member of the ArchivesSpace community. We?re Hiring! As a result of the previous news item, we're seeking the next Community Engagement Coordinator for ArchivesSpace. This position is on the frontlines of the program, working directly with individual users and groups of users. Some of the key responsibilities include organizing online and in person events, managing our communications program, and working with community groups responsible for testing, user documentation and training activities. The person in this position plays a tremendous part in helping connect users to each other and works closely with our community to make ArchivesSpace better for everyone. All applications have to include a cover letter and resume and must be submitted through the LYRASIS online hiring portal; the online listing for this position is at https://lyrasis.isolvedhire.com/jobs/43961.html. Applications received by December 7 will receive priority consideration. Please feel free to contact Christine Di Bella (christine.dibella at lyrasis.org) with questions. Regional Forum Updates Our Fall Regional Forum is coming up next week, and we are also exploring an online forum for the Winter season. Here are some of the most relevant news, dates, and links to keep you up to date on all the activity! [https://lh4.googleusercontent.com/zcIOErEnM08cHKRH5w6FByocnsUNVspIhrt49G2mUdsHHcFUCjK039qtZ8GZmlYB6fVMNoyXs43-VyqnZe681TWJgEQuWClFNC69t0KMi2vRV1PW7baTv5S5BoN51OmYZ1Jgi-so] Upcoming: Kansas City Regional Forum: November 30, 2018 Join us at the Kansas City Regional Forum! We?ll be meeting at the Midwest Genealogy Center in Independence, MO on Friday, November 30, 2018. * Registration is open! * Check out our program agenda, including information on workshops, presenters, and discussions! Upcoming: ArchivesSpace Online Forum: Winter (Feb/March) 2019 We are thrilled to share we have formed a Working Group to shape the program content for our upcoming online forum. The group is represented by community members across all membership sizes, as well as international (non-US) members. Our working group members are: Jessica Crouch, University of South Carolina Leilani Dawson, University of Hawai?i at M?noa Madeline Sheldon, LYRASIS Maggie Schreiner, Brooklyn Historical Society Mariella Soprano, California Institute of Technology Megan Firestone, St. Edward?s University Patrick Milhoan, University of Notre Dame Stephen Innes, University of Auckland Venkat Srinivasan, Archives, National Centre for Biological Sciences Christine Kim, ArchivesSpace Our first planning team meeting will be scheduled for early December. We are excited for this opportunity to explore new ways for our community can collaborate, communicate, and engage with each other through an online forum! If you have any questions (or ideas) related to the regional forums, feel free to email Christine 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. Community Member Resources ArchivesSpace Member Directory - Updated digital copy distributed to member reps We have distributed an updated digital copy of our Member Directory! The information was collected through submissions from members and compiled to share information about how you are using ArchivesSpace, and any implementation or integration projects you are planning for the future. This directory was sent out to all ArchivesSpace Member Representatives. Would you like to add or update information about your organization to the directory? The submission form is available here: https://tinyurl.com/aspace-directory. Most questions are optional. 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. Please email us at ArchivesSpaceHome at lyrasis.org if you have any questions. ArchivesSpace Implementation Buddies - Updated digital copy distributed to buddy participants The ASpace Implementation Buddy program is in full swing! A digital listing of all interested implementation buddies has been distributed through email to all individuals who have submitted their interest through the Implementation Buddy sign-up sheet. Interested in learning more about the buddy program before you sign up? Visit our ASpace Buddies info page to get started. If you have any questions, please contact Christine Kim at christine.kim at lyrasis.org. Association of Moving Image Archivists Hack Day: ArchivesSpace PBCore plugin At the Association of Moving Image Archivists 2018 conference in Portland, Oregon, specifically at the AMIA/Digital Library Federation Hack Day on November 28, a group from the WGBH public radio/television plans to propose a continuation of development of the preliminary ArchivesSpace PBCore plugin that was begun at a previous AMIA Hack Day in 2014: https://github.com/amiaopensource/avspace/wiki. AMIA/DLF Hack Day is now in its 5th year and is a unique opportunity for practitioners and managers of moving image collections to join with developers and engineers for an intense day of collaboration to develop solutions for digital audiovisual preservation and access. Within digital preservation and curation communities, hack days provide an opportunity for archivists, collection managers, technologists, and others to work together develop software solutions, documentation or training materials, and more for digital collections management needs. More information about Hack Day is available here: http://www.amiaconference.net/amia-dlf-hack-day/ Membership Update We are excited to welcome our newest members to our community! Our new members since October 31 include: * National Centre for Biological Sciences, Tata Institute of Fundamental Research (Bangalore, India) * Episcopal Church in Connecticut (Meriden, CT) * Worcester Polytechnic Institute (Worcester, MA) As of November 19, we have 365 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: image001.jpg Type: image/jpeg Size: 20006 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 36390 bytes Desc: image002.jpg URL: From VivianLea.Solek at Kofc.Org Tue Nov 20 14:16:11 2018 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Tue, 20 Nov 2018 19:16:11 +0000 Subject: [Archivesspace_Users_Group] Help with "Lost" Series Message-ID: Good afternoon, I am working on moving legacy data into proper series within a collection. I created several series and started moving objects into them using the Reorder Mode. I have moved 9 items into Series I. Now, when I select an object to move into that series, Series I no longer appears in my list of places to move it. Help!?! Am I doing something wrong or is my system having a pre-Thanksgiving mental fit? MANY thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Tue Nov 20 14:26:53 2018 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Tue, 20 Nov 2018 19:26:53 +0000 Subject: [Archivesspace_Users_Group] Another Reordering Question Message-ID: I believe the answer to my last post was "it was a pre-Thanksgiving mental fit." After posting I went back in and it had reappeared. So the next question is, when reading the manual, it says that you can select multiple items by using the ctrl+click. However, when I use that combination (or shift+click or alt+click, it justs open another browser tab with the same page. Is this a bug that has been identified? I'm in version 2.4.1 and we are self-hosting. Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Tue Nov 20 14:52:01 2018 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Tue, 20 Nov 2018 19:52:01 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing Message-ID: Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Tue Nov 20 14:58:44 2018 From: buschedw at msu.edu (Busch, Ed) Date: Tue, 20 Nov 2018 19:58:44 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Tue Nov 20 15:25:59 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Tue, 20 Nov 2018 20:25:59 +0000 Subject: [Archivesspace_Users_Group] Another Reordering Question In-Reply-To: References: Message-ID: VivianLea - Try clicking on the far left rather than on the archival object title. There is a small lightly shaded square, with a dotted 'drag-handle' icon. As you click, the square will turn blue. You can select one at a time (CTRL + click) , or many (SHIFT + click). When selecting, the squares will show an order number - you can select 'out of order' if you like (1-3-2 vs 1-2-3) [cid:image001.png at 01D480E5.52909460] Nancy From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Solek, VivianLea Sent: Tuesday, November 20, 2018 2:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Another Reordering Question I believe the answer to my last post was "it was a pre-Thanksgiving mental fit." After posting I went back in and it had reappeared. So the next question is, when reading the manual, it says that you can select multiple items by using the ctrl+click. However, when I use that combination (or shift+click or alt+click, it justs open another browser tab with the same page. Is this a bug that has been identified? I'm in version 2.4.1 and we are self-hosting. Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1782 bytes Desc: image001.png URL: From sdm7g at virginia.edu Tue Nov 20 15:41:53 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 20 Nov 2018 20:41:53 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> Message-ID: <0D67DB68-6346-4420-8403-9194A2CECA8B@virginia.edu> > On Nov 20, 2018, at 2:58 PM, Busch, Ed wrote: > > The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. > > So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. > I good first step in debugging print-to-PDF issues in the staff interface is to try to export and validate EAD. The path to generate PDF is: ArchivesSpace resource => EAD => FOP => PDF , and invalid EAD will often cause errors in later steps. If that is the case, then validation will also pinpoint where exactly the problem is. > Good luck! > > Ed Busch, MLIS > Electronic Records Archivist > Michigan State University Archives > Conrad Hall > 943 Conrad Road, Room 101 > East Lansing, MI 48824 > 517-884-6438 > buschedw at msu.edu > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Zachary L Pelli > Sent: Tuesday, November 20, 2018 2:52 PM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Print to PDF job failing > > Hey all, > > One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). > > In the log within AS Background Jobs section, it gives this: > > Generating PDF for John M. Oesterreicher papers > org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. > net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) > org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) > RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) > RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) > RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) > RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) > RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) > RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) > var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) > RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) > var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) > org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) > org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) > java.lang.Thread.run(java/lang/Thread.java:748) > > Has anyone encountered this problem before? > > Regards, > > Zach Pelli > Digital Collections Infrastructure Developer > Seton Hall University Libraries > 973.275.2046 > > _______________________________________________ > 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: 6102 bytes Desc: not available URL: From mark.custer at yale.edu Tue Nov 20 15:42:33 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 20 Nov 2018 20:42:33 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> Message-ID: Zach, I'd suggest exporting the EAD file and taking a look at the file that way (and I'd be happy to take a look if you can send it to me). Those "ns2" namespace prefixes are likely from Archivist's Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I'm honestly not sure why you'd be getting that error without seeing the entire EAD file since you shouldn't even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can't think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that's being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink="http://www.w3.org/1999/xlink" Whereas what you have further down in your file on that ref tag is "ns2:", and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you'd see this at the top of the file: xmlns:ns2:"http://www.w3.org/1999/xlink" And "xlink" does not equal "ns2", even though they're both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 -------------- next part -------------- An HTML attachment was scrubbed... URL: From eef46 at cornell.edu Tue Nov 20 16:46:56 2018 From: eef46 at cornell.edu (Erin Faulder) Date: Tue, 20 Nov 2018 21:46:56 +0000 Subject: [Archivesspace_Users_Group] read-only subrecords Message-ID: Cornell is creating a plugin to store a small custom subrecord (so far so good) with the additional requirement that it be read-only from the UI (the data will be imported via other means), so the fields should not be editable from the edit page. Is there a supported way to do this? We?ve tried using the ?label_and_readonly? form helper method in my template, and while this does result in the fields being output as read-only labels, they aren?t passed back to the server when one attempts to save the object. We end up getting a database error saying that one of the fields does not have a default value, and inspecting the params object in the log file reveals that my subrecord data is not present at all. Marking the properties as ?readonly? in the schema results in the same problem. Using a standard ?label_and_textfield? works ok so I don?t know if this is a bug or I?m missing something. This is all on version 2.5.0 at the moment. Any help/direction is greatly appreciated! Erin Faulder -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.innes at auckland.ac.nz Tue Nov 20 20:48:20 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Wed, 21 Nov 2018 01:48:20 +0000 Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI Message-ID: <693b33c48d5f407c8aea2dbf0e882d24@uxcn13-ogg-c.UoA.auckland.ac.nz> I note that this issue appears to have been partially resolved with AR-1803. However, our Bibliography notes are not currently displaying in the PUI, eg in this record: https://archives.library.auckland.ac.nz/repositories/2/resources/668 Attached is a screenshot of the Bibliography note for this resource: Cuthbert family papers. MSS & Archives 2003/6. Also, the AS staff interface does not seem to be exporting this note either, as can be seen in the attached EAD record for the resource. Can someone update us on the status of this bug or suggest a solution? Regards, Stephen Innes Team Leader, Cultural Collections (Special Collections) 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 | Fax (649) 373-7565 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cuthbert-2003-6.xml Type: text/xml Size: 6432 bytes Desc: cuthbert-2003-6.xml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bibliography-note.png Type: image/png Size: 39773 bytes Desc: bibliography-note.png URL: From blake.carver at lyrasis.org Wed Nov 21 07:57:53 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 21 Nov 2018 12:57:53 +0000 Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI In-Reply-To: <693b33c48d5f407c8aea2dbf0e882d24@uxcn13-ogg-c.UoA.auckland.ac.nz> References: <693b33c48d5f407c8aea2dbf0e882d24@uxcn13-ogg-c.UoA.auckland.ac.nz> Message-ID: Have a look in your logs, what's the error reported there? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Tuesday, November 20, 2018 8:48:20 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI I note that this issue appears to have been partially resolved with AR-1803. However, our Bibliography notes are not currently displaying in the PUI, eg in this record: https://archives.library.auckland.ac.nz/repositories/2/resources/668 Attached is a screenshot of the Bibliography note for this resource: Cuthbert family papers. MSS & Archives 2003/6. Also, the AS staff interface does not seem to be exporting this note either, as can be seen in the attached EAD record for the resource. Can someone update us on the status of this bug or suggest a solution? Regards, Stephen Innes Team Leader, Cultural Collections (Special Collections) 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 | Fax (649) 373-7565 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Nov 21 09:57:15 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 21 Nov 2018 14:57:15 +0000 Subject: [Archivesspace_Users_Group] read-only subrecords In-Reply-To: References: Message-ID: Try wrapping the form fields in a user_can? statement. Something like <% if user_can?('administer_system') %> <%= form.label_and_textfield "{FIELD_NAME}" %> <% else %> <%= form.label_and_readonly "{FIELD_NAME}" %> <%= form.hidden_input("{FIELD_NAME}") %> <% end %> Hope that helps! Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Erin Faulder Sent: Tuesday, November 20, 2018 4:46 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Don Smith Subject: [Archivesspace_Users_Group] read-only subrecords Cornell is creating a plugin to store a small custom subrecord (so far so good) with the additional requirement that it be read-only from the UI (the data will be imported via other means), so the fields should not be editable from the edit page. Is there a supported way to do this? We?ve tried using the ?label_and_readonly? form helper method in my template, and while this does result in the fields being output as read-only labels, they aren?t passed back to the server when one attempts to save the object. We end up getting a database error saying that one of the fields does not have a default value, and inspecting the params object in the log file reveals that my subrecord data is not present at all. Marking the properties as ?readonly? in the schema results in the same problem. Using a standard ?label_and_textfield? works ok so I don?t know if this is a bug or I?m missing something. This is all on version 2.5.0 at the moment. Any help/direction is greatly appreciated! Erin Faulder -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Mon Nov 26 11:51:18 2018 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Mon, 26 Nov 2018 16:51:18 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> Message-ID: Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I'd suggest exporting the EAD file and taking a look at the file that way (and I'd be happy to take a look if you can send it to me). Those "ns2" namespace prefixes are likely from Archivist's Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I'm honestly not sure why you'd be getting that error without seeing the entire EAD file since you shouldn't even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can't think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that's being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink="http://www.w3.org/1999/xlink" Whereas what you have further down in your file on that ref tag is "ns2:", and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you'd see this at the top of the file: xmlns:ns2:"http://www.w3.org/1999/xlink" And "xlink" does not equal "ns2", even though they're both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mss_0053_20181120_212323_UTC__ead.xml Type: application/xml Size: 1734424 bytes Desc: Mss_0053_20181120_212323_UTC__ead.xml URL: From buschedw at msu.edu Mon Nov 26 11:58:14 2018 From: buschedw at msu.edu (Busch, Ed) Date: Mon, 26 Nov 2018 16:58:14 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164B034CC@CAD-EX01.campusad.msu.edu> I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I'd suggest exporting the EAD file and taking a look at the file that way (and I'd be happy to take a look if you can send it to me). Those "ns2" namespace prefixes are likely from Archivist's Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I'm honestly not sure why you'd be getting that error without seeing the entire EAD file since you shouldn't even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can't think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that's being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink="http://www.w3.org/1999/xlink" Whereas what you have further down in your file on that ref tag is "ns2:", and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you'd see this at the top of the file: xmlns:ns2:"http://www.w3.org/1999/xlink" And "xlink" does not equal "ns2", even though they're both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Nov 26 12:35:52 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 26 Nov 2018 17:35:52 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164B034CC@CAD-EX01.campusad.msu.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164B019EF@CAD-EX01.campusad.msu.edu> <35E2A8E8997F6C48A5D5FC21602BDEB60164B034CC@CAD-EX01.campusad.msu.edu> Message-ID: Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it's not good to have that in the text in the first place, so I wouldn't advise that). I'm not sure why ASpace's normal EAD cleaning process isn't changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don't match any @id attributes (e.g. "ref16" does not equal "aspace_ref16_p33"). This won't cause the file from converting to a PDF, but it's still a broken link. All that said, if there's no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends "aspace_" during its EAD export process), I'd say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I'd suggest exporting the EAD file and taking a look at the file that way (and I'd be happy to take a look if you can send it to me). Those "ns2" namespace prefixes are likely from Archivist's Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I'm honestly not sure why you'd be getting that error without seeing the entire EAD file since you shouldn't even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can't think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that's being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink="http://www.w3.org/1999/xlink" Whereas what you have further down in your file on that ref tag is "ns2:", and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you'd see this at the top of the file: xmlns:ns2:"http://www.w3.org/1999/xlink" And "xlink" does not equal "ns2", even though they're both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Mon Nov 26 13:22:40 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 26 Nov 2018 18:22:40 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing Message-ID: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> Hi Zach, Ed, and Mark, It sounds like this is a bug with the AT Migrator. Would you be willing to create a bug report for this in JIRA? On a quick search, it didn?t seem like this issue has been logged yet. https://archivesspace.atlassian.net/secure/Dashboard.jspa It would be great if you could include in the tags ?ATMigrator.? Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Monday, November 26, 2018 at 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it?s not good to have that in the text in the first place, so I wouldn?t advise that). I?m not sure why ASpace?s normal EAD cleaning process isn?t changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don?t match any @id attributes (e.g. ?ref16? does not equal ?aspace_ref16_p33?). This won?t cause the file from converting to a PDF, but it?s still a broken link. All that said, if there?s no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends ?aspace_? during its EAD export process), I?d say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I?d suggest exporting the EAD file and taking a look at the file that way (and I?d be happy to take a look if you can send it to me). Those ?ns2? namespace prefixes are likely from Archivist?s Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I?m honestly not sure why you?d be getting that error without seeing the entire EAD file since you shouldn?t even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can?t think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that?s being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink=?http://www.w3.org/1999/xlink? Whereas what you have further down in your file on that ref tag is ?ns2:?, and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you?d see this at the top of the file: xmlns:ns2:?http://www.w3.org/1999/xlink? And ?xlink? does not equal ?ns2?, even though they?re both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 From mark.custer at yale.edu Mon Nov 26 14:59:26 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 26 Nov 2018 19:59:26 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> References: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> Message-ID: Lydia, all: I don't know if it's a bug with the AT migrator, but I have raised this issue in 2014 when providing (a lot!) of feedback about the AT migration process. There are a couple of complicated issues, namely: All of those xlink namespace prefixes are treated and stored as text, not as XML (in both the AT and ASpace). So, it can be a bit dangerous and inefficient to change them in bulk. I had hoped that the migration tool would address that issue, but the decision at the time was not to have the migration tool do this. Because of that, we decided to address this prior to our migration with the following (albeit inelegant) SQL update: https://github.com/YaleArchivesSpace/migrationSQL/blob/master/AllDatabasesPreMigration.sql#L1-L26 (that largely did the trick, if I recall correctly). All of those @target attributes are also stored as text. That was a lot messier, so the AT migration tool eventually added the ability to keep the ID values as is (e.g. "ref33" ==> "ref33") during the migration process, but you had to pass that argument (with the "-refid_original" flag) to the migration tool to keep those values as is. Anyhow, given the complexities of the migrations, it's hard to say what's a bug and what's behaving as expected (at least it's hard for me to remember everything involved). That said, Maureen did an AMAZING job of writing up our steps: https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/ . If anything in there is something that can be fixed with the AT migration tool, I'd be happy to provide more feedback on those tickets. That said, I'm honestly not sure how best to capture those there at this point (and I think / assumed that all of those issues were recorded in a previous bug/feature tracking system used by ASpace). Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, 26 November, 2018 1:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Hi Zach, Ed, and Mark, It sounds like this is a bug with the AT Migrator. Would you be willing to create a bug report for this in JIRA? On a quick search, it didn?t seem like this issue has been logged yet. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fsecure%2FDashboard.jspa&data=02%7C01%7Cmark.custer%40yale.edu%7C773babf6349f4b3622dc08d653cc2c5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788533731893576&sdata=mbYCBrPIttccGrW%2FfPF6mUx5uFHy8TEQDHXMsIicCSA%3D&reserved=0 It would be great if you could include in the tags ?ATMigrator.? Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Monday, November 26, 2018 at 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it?s not good to have that in the text in the first place, so I wouldn?t advise that). I?m not sure why ASpace?s normal EAD cleaning process isn?t changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don?t match any @id attributes (e.g. ?ref16? does not equal ?aspace_ref16_p33?). This won?t cause the file from converting to a PDF, but it?s still a broken link. All that said, if there?s no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends ?aspace_? during its EAD export process), I?d say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I?d suggest exporting the EAD file and taking a look at the file that way (and I?d be happy to take a look if you can send it to me). Those ?ns2? namespace prefixes are likely from Archivist?s Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I?m honestly not sure why you?d be getting that error without seeing the entire EAD file since you shouldn?t even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can?t think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that?s being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink=?http://www.w3.org/1999/xlink? Whereas what you have further down in your file on that ref tag is ?ns2:?, and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you?d see this at the top of the file: xmlns:ns2:?http://www.w3.org/1999/xlink? And ?xlink? does not equal ?ns2?, even though they?re both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7C773babf6349f4b3622dc08d653cc2c5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788533731903580&sdata=3icOI8ehXBWQbc9fLUi5fur33u1%2B1JMtW8OOmWCHJP4%3D&reserved=0 From NDavis at museumofflight.org Mon Nov 26 15:18:50 2018 From: NDavis at museumofflight.org (Nicole Davis) Date: Mon, 26 Nov 2018 20:18:50 +0000 Subject: [Archivesspace_Users_Group] Subject listings Message-ID: <32c641d5ab37403196837c80088f188c@ExchSRV3.nmof.org> Hello all, We're just finishing up our migration to ASpace so I'm a new user. I'm looking ahead to customizing the PUI and getting that launched. I'm wondering about subject listings in resource records: it looks like names, places, genres and topics all get listed in one long list rather than listed separately by type (a list of names, a list of genres, etc.). How can we go about changing the display of subjects so they are grouped by type? Thanks, Nicole [cid:TMOF_2017EmailSig_4bbd8aad-f325-493b-948f-69f2acb54085.jpg] Nicole Davis | Supervisory Archivist The Museum of Flight 9404 East Marginal Way S Seattle, WA 98108 Work: +1 (206) 768-7215 www.museumofflight.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TMOF_2017EmailSig_4bbd8aad-f325-493b-948f-69f2acb54085.jpg Type: image/jpeg Size: 24027 bytes Desc: TMOF_2017EmailSig_4bbd8aad-f325-493b-948f-69f2acb54085.jpg URL: From zachary.pelli at shu.edu Mon Nov 26 15:26:15 2018 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Mon, 26 Nov 2018 20:26:15 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> Message-ID: Mark, Regarding my instance in particular, would you recommend running that SQL block? I do not see a way to edit the XML from within AS itself, so I'm thinking that leaves the mysql DB or through the API. Regards, Zach -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, November 26, 2018 2:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Lydia, all: I don't know if it's a bug with the AT migrator, but I have raised this issue in 2014 when providing (a lot!) of feedback about the AT migration process. There are a couple of complicated issues, namely: All of those xlink namespace prefixes are treated and stored as text, not as XML (in both the AT and ASpace). So, it can be a bit dangerous and inefficient to change them in bulk. I had hoped that the migration tool would address that issue, but the decision at the time was not to have the migration tool do this. Because of that, we decided to address this prior to our migration with the following (albeit inelegant) SQL update: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FYaleArchivesSpace%2FmigrationSQL%2Fblob%2Fmaster%2FAllDatabasesPreMigration.sql%23L1-L26&data=01%7C01%7CZachary.pelli%40shu.edu%7C51655a3db3c24d40642a08d653d9af16%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=6E9RbWLc%2BM%2FTxJGJ9X%2FgviFCRFlCzYhBlxAPhPVcIRs%3D&reserved=0 (that largely did the trick, if I recall correctly). All of those @target attributes are also stored as text. That was a lot messier, so the AT migration tool eventually added the ability to keep the ID values as is (e.g. "ref33" ==> "ref33") during the migration process, but you had to pass that argument (with the "-refid_original" flag) to the migration tool to keep those values as is. Anyhow, given the complexities of the migrations, it's hard to say what's a bug and what's behaving as expected (at least it's hard for me to remember everything involved). That said, Maureen did an AMAZING job of writing up our steps: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcampuspress.yale.edu%2Fyalearchivesspace%2F2015%2F06%2F14%2Fmigration-step-by-step%2F&data=01%7C01%7CZachary.pelli%40shu.edu%7C51655a3db3c24d40642a08d653d9af16%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=VHF7%2BFRIYh0VQQh%2Bui2YndcnqwGVn%2FJQBgC3g7D4Npc%3D&reserved=0 . If anything in there is something that can be fixed with the AT migration tool, I'd be happy to provide more feedback on those tickets. That said, I'm honestly not sure how best to capture those there at this point (and I think / assumed that all of those issues were recorded in a previous bug/feature tracking system used by ASpace). Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, 26 November, 2018 1:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Hi Zach, Ed, and Mark, It sounds like this is a bug with the AT Migrator. Would you be willing to create a bug report for this in JIRA? On a quick search, it didn?t seem like this issue has been logged yet. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fsecure%2FDashboard.jspa&data=01%7C01%7CZachary.pelli%40shu.edu%7C51655a3db3c24d40642a08d653d9af16%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=CtyHiDP11seG18JK%2FhkmdsW8P%2Fgz7bJeJZ6FRGbYs5Y%3D&reserved=0 It would be great if you could include in the tags ?ATMigrator.? Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Monday, November 26, 2018 at 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it?s not good to have that in the text in the first place, so I wouldn?t advise that). I?m not sure why ASpace?s normal EAD cleaning process isn?t changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don?t match any @id attributes (e.g. ?ref16? does not equal ?aspace_ref16_p33?). This won?t cause the file from converting to a PDF, but it?s still a broken link. All that said, if there?s no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends ?aspace_? during its EAD export process), I?d say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I?d suggest exporting the EAD file and taking a look at the file that way (and I?d be happy to take a look if you can send it to me). Those ?ns2? namespace prefixes are likely from Archivist?s Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I?m honestly not sure why you?d be getting that error without seeing the entire EAD file since you shouldn?t even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can?t think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that?s being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink=?http://www.w3.org/1999/xlink? Whereas what you have further down in your file on that ref tag is ?ns2:?, and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you?d see this at the top of the file: xmlns:ns2:?http://www.w3.org/1999/xlink? And ?xlink? does not equal ?ns2?, even though they?re both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=01%7C01%7CZachary.pelli%40shu.edu%7C51655a3db3c24d40642a08d653d9af16%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=%2FQRtZ%2B4vignqblnGJvP4u2h%2FJproCgBipkpGiSZ9bl0%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=01%7C01%7CZachary.pelli%40shu.edu%7C51655a3db3c24d40642a08d653d9af16%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=%2FQRtZ%2B4vignqblnGJvP4u2h%2FJproCgBipkpGiSZ9bl0%3D&reserved=0 From mark.custer at yale.edu Mon Nov 26 15:41:49 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 26 Nov 2018 20:41:49 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> Message-ID: Zach, No, sorry. That bit of SQL was run against the Archivists' Toolkit database, not ASpace. In ASpace, the SQL update would look quite a bit different, and given how the notes are stored in ASpace, it might be a bit tricky. I'm not sure what the best way would be to address that in ArchivesSpace. Has anyone else handled it there? Two of my colleagues, Alicia and Christy, have run a few different API updates on notes in ASpace, so they'd have more experience about that than I do at this point. In general, though, our usual approach would be to write an SQL query in ASpace to figure out where all of the issues are, and then turning to the API to try and fix those issues as safely as possible (but even that requires a lot of testing, since it's easy to mess things up when working in bulk, so we always test any new updates a few times before running it in our production system). If I recall correctly, someone added a nice fix for this at some point directly in ArchivesSpace that helps clean things up during the export process. I don't recall what/where that file is at the moment, though. I think it would probably be best to try to figure out why that process is not cleaning things up as expected in this particular case and then adding a fix for it there. Zach, is this happening in a lot of your files, or just this one (or some subset)? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Zachary L Pelli Sent: Monday, 26 November, 2018 3:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Mark, Regarding my instance in particular, would you recommend running that SQL block? I do not see a way to edit the XML from within AS itself, so I'm thinking that leaves the mysql DB or through the API. Regards, Zach -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, November 26, 2018 2:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Lydia, all: I don't know if it's a bug with the AT migrator, but I have raised this issue in 2014 when providing (a lot!) of feedback about the AT migration process. There are a couple of complicated issues, namely: All of those xlink namespace prefixes are treated and stored as text, not as XML (in both the AT and ASpace). So, it can be a bit dangerous and inefficient to change them in bulk. I had hoped that the migration tool would address that issue, but the decision at the time was not to have the migration tool do this. Because of that, we decided to address this prior to our migration with the following (albeit inelegant) SQL update: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FYaleArchivesSpace%2FmigrationSQL%2Fblob%2Fmaster%2FAllDatabasesPreMigration.sql%23L1-L26&data=02%7C01%7Cmark.custer%40yale.edu%7Cb18d86b62ff4402c74c708d653dd6ef7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788607928715851&sdata=zitl0BNm4TsJbInSEH2Lpsq4B2b7o9BS%2F8ZqGi8YNLU%3D&reserved=0 (that largely did the trick, if I recall correctly). All of those @target attributes are also stored as text. That was a lot messier, so the AT migration tool eventually added the ability to keep the ID values as is (e.g. "ref33" ==> "ref33") during the migration process, but you had to pass that argument (with the "-refid_original" flag) to the migration tool to keep those values as is. Anyhow, given the complexities of the migrations, it's hard to say what's a bug and what's behaving as expected (at least it's hard for me to remember everything involved). That said, Maureen did an AMAZING job of writing up our steps: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcampuspress.yale.edu%2Fyalearchivesspace%2F2015%2F06%2F14%2Fmigration-step-by-step%2F&data=02%7C01%7Cmark.custer%40yale.edu%7Cb18d86b62ff4402c74c708d653dd6ef7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788607928715851&sdata=wrC%2BCtod5QST%2F4dVjM6g6g9PGt3iBS932frIgp45hik%3D&reserved=0 . If anything in there is something that can be fixed with the AT migration tool, I'd be happy to provide more feedback on those tickets. That said, I'm honestly not sure how best to capture those there at this point (and I think / assumed that all of those issues were recorded in a previous bug/feature tracking system used by ASpace). Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, 26 November, 2018 1:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Hi Zach, Ed, and Mark, It sounds like this is a bug with the AT Migrator. Would you be willing to create a bug report for this in JIRA? On a quick search, it didn?t seem like this issue has been logged yet. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fsecure%2FDashboard.jspa&data=02%7C01%7Cmark.custer%40yale.edu%7Cb18d86b62ff4402c74c708d653dd6ef7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788607928715851&sdata=ugGDJurhTNn0ACJT0c7%2Bcho72xpmJWK1ekCgE1u6VUo%3D&reserved=0 It would be great if you could include in the tags ?ATMigrator.? Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Monday, November 26, 2018 at 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it?s not good to have that in the text in the first place, so I wouldn?t advise that). I?m not sure why ASpace?s normal EAD cleaning process isn?t changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don?t match any @id attributes (e.g. ?ref16? does not equal ?aspace_ref16_p33?). This won?t cause the file from converting to a PDF, but it?s still a broken link. All that said, if there?s no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends ?aspace_? during its EAD export process), I?d say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I?d suggest exporting the EAD file and taking a look at the file that way (and I?d be happy to take a look if you can send it to me). Those ?ns2? namespace prefixes are likely from Archivist?s Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I?m honestly not sure why you?d be getting that error without seeing the entire EAD file since you shouldn?t even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can?t think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that?s being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink=?http://www.w3.org/1999/xlink? Whereas what you have further down in your file on that ref tag is ?ns2:?, and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you?d see this at the top of the file: xmlns:ns2:?http://www.w3.org/1999/xlink? And ?xlink? does not equal ?ns2?, even though they?re both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cb18d86b62ff4402c74c708d653dd6ef7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788607928715851&sdata=7dLCKkaHhPG8GQcQz%2B6nnkim8nPhcqUW%2BHn0o69jJw4%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cb18d86b62ff4402c74c708d653dd6ef7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788607928715851&sdata=7dLCKkaHhPG8GQcQz%2B6nnkim8nPhcqUW%2BHn0o69jJw4%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cb18d86b62ff4402c74c708d653dd6ef7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788607928715851&sdata=7dLCKkaHhPG8GQcQz%2B6nnkim8nPhcqUW%2BHn0o69jJw4%3D&reserved=0 From zachary.pelli at shu.edu Mon Nov 26 16:07:50 2018 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Mon, 26 Nov 2018 21:07:50 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> Message-ID: Mark, Thanks for all the help. The archivist who raised the issue said she was able to run the "Print to PDF" job on multiple other collections successfully. I am unsure whether or not other collections are affected by this, but my guess is there are others. I'll try running some queries tomorrow and see what I find. Regards, Zach -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, November 26, 2018 3:42 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, No, sorry. That bit of SQL was run against the Archivists' Toolkit database, not ASpace. In ASpace, the SQL update would look quite a bit different, and given how the notes are stored in ASpace, it might be a bit tricky. I'm not sure what the best way would be to address that in ArchivesSpace. Has anyone else handled it there? Two of my colleagues, Alicia and Christy, have run a few different API updates on notes in ASpace, so they'd have more experience about that than I do at this point. In general, though, our usual approach would be to write an SQL query in ASpace to figure out where all of the issues are, and then turning to the API to try and fix those issues as safely as possible (but even that requires a lot of testing, since it's easy to mess things up when working in bulk, so we always test any new updates a few times before running it in our production system). If I recall correctly, someone added a nice fix for this at some point directly in ArchivesSpace that helps clean things up during the export process. I don't recall what/where that file is at the moment, though. I think it would probably be best to try to figure out why that process is not cleaning things up as expected in this particular case and then adding a fix for it there. Zach, is this happening in a lot of your files, or just this one (or some subset)? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Zachary L Pelli Sent: Monday, 26 November, 2018 3:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Mark, Regarding my instance in particular, would you recommend running that SQL block? I do not see a way to edit the XML from within AS itself, so I'm thinking that leaves the mysql DB or through the API. Regards, Zach -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, November 26, 2018 2:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Lydia, all: I don't know if it's a bug with the AT migrator, but I have raised this issue in 2014 when providing (a lot!) of feedback about the AT migration process. There are a couple of complicated issues, namely: All of those xlink namespace prefixes are treated and stored as text, not as XML (in both the AT and ASpace). So, it can be a bit dangerous and inefficient to change them in bulk. I had hoped that the migration tool would address that issue, but the decision at the time was not to have the migration tool do this. Because of that, we decided to address this prior to our migration with the following (albeit inelegant) SQL update: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FYaleArchivesSpace%2FmigrationSQL%2Fblob%2Fmaster%2FAllDatabasesPreMigration.sql%23L1-L26&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=PMiw7s15WKAgZBtzeOdtuKzOoj%2Biw0nMKZenqCYARmw%3D&reserved=0 (that largely did the trick, if I recall correctly). All of those @target attributes are also stored as text. That was a lot messier, so the AT migration tool eventually added the ability to keep the ID values as is (e.g. "ref33" ==> "ref33") during the migration process, but you had to pass that argument (with the "-refid_original" flag) to the migration tool to keep those values as is. Anyhow, given the complexities of the migrations, it's hard to say what's a bug and what's behaving as expected (at least it's hard for me to remember everything involved). That said, Maureen did an AMAZING job of writing up our steps: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcampuspress.yale.edu%2Fyalearchivesspace%2F2015%2F06%2F14%2Fmigration-step-by-step%2F&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=TgiyMCs8LhLJvyoh%2FI0Caz9%2BtNh%2FsPotWw1DvPwBf3U%3D&reserved=0 . If anything in there is something that can be fixed with the AT migration tool, I'd be happy to provide more feedback on those tickets. That said, I'm honestly not sure how best to capture those there at this point (and I think / assumed that all of those issues were recorded in a previous bug/feature tracking system used by ASpace). Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, 26 November, 2018 1:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Hi Zach, Ed, and Mark, It sounds like this is a bug with the AT Migrator. Would you be willing to create a bug report for this in JIRA? On a quick search, it didn?t seem like this issue has been logged yet. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fsecure%2FDashboard.jspa&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=ZIchj%2BwRid6GPJGfAYJ6O83vXYjxLz%2B8lqEQ39tgUXA%3D&reserved=0 It would be great if you could include in the tags ?ATMigrator.? Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Monday, November 26, 2018 at 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it?s not good to have that in the text in the first place, so I wouldn?t advise that). I?m not sure why ASpace?s normal EAD cleaning process isn?t changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don?t match any @id attributes (e.g. ?ref16? does not equal ?aspace_ref16_p33?). This won?t cause the file from converting to a PDF, but it?s still a broken link. All that said, if there?s no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends ?aspace_? during its EAD export process), I?d say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I?d suggest exporting the EAD file and taking a look at the file that way (and I?d be happy to take a look if you can send it to me). Those ?ns2? namespace prefixes are likely from Archivist?s Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I?m honestly not sure why you?d be getting that error without seeing the entire EAD file since you shouldn?t even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can?t think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that?s being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink=?http://www.w3.org/1999/xlink? Whereas what you have further down in your file on that ref tag is ?ns2:?, and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you?d see this at the top of the file: xmlns:ns2:?http://www.w3.org/1999/xlink? And ?xlink? does not equal ?ns2?, even though they?re both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=64AP%2FUL7OVOPsSVBCEilfWxCGM8%2Fb4Tt3u9vWIKjD%2B8%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=64AP%2FUL7OVOPsSVBCEilfWxCGM8%2Fb4Tt3u9vWIKjD%2B8%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=64AP%2FUL7OVOPsSVBCEilfWxCGM8%2Fb4Tt3u9vWIKjD%2B8%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=01%7C01%7CZachary.pelli%40shu.edu%7C0a2c51afba654c142a9d08d653df9ae7%7C51f07c2253b744dfb97ca13261d71075%7C1&sdata=64AP%2FUL7OVOPsSVBCEilfWxCGM8%2Fb4Tt3u9vWIKjD%2B8%3D&reserved=0 From mark.custer at yale.edu Mon Nov 26 17:50:50 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 26 Nov 2018 22:50:50 +0000 Subject: [Archivesspace_Users_Group] Print to PDF job failing In-Reply-To: References: <4755310E-CD21-45B8-8238-4F532581CAE3@lib.msu.edu> Message-ID: Zach, In case it helps, I dug up an old ASpace SQL query to look for those namespace prefixes (turns out that we still have 3 of those lurking around that I need to fix later this week!). Anyhow, here it is: select resource.id as resourceid, resource.ead_id, archival_object.id as aoid, archival_object.root_record_id, convert(notes using utf8) as jsonnote from note left join resource on resource.id = note.resource_id left join archival_object on archival_object.id = note.archival_object_id where notes like '%ns2:%'; Maybe you'll see some patterns there with the files that do work vs. those that don't work. If so, let us know, since that might provide some clues on if there's more work that can be done on the XML cleaning process during the ASpace export process. All my best, Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Zachary L Pelli Sent: Monday, 26 November, 2018 4:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Mark, Thanks for all the help. The archivist who raised the issue said she was able to run the "Print to PDF" job on multiple other collections successfully. I am unsure whether or not other collections are affected by this, but my guess is there are others. I'll try running some queries tomorrow and see what I find. Regards, Zach -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, November 26, 2018 3:42 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, No, sorry. That bit of SQL was run against the Archivists' Toolkit database, not ASpace. In ASpace, the SQL update would look quite a bit different, and given how the notes are stored in ASpace, it might be a bit tricky. I'm not sure what the best way would be to address that in ArchivesSpace. Has anyone else handled it there? Two of my colleagues, Alicia and Christy, have run a few different API updates on notes in ASpace, so they'd have more experience about that than I do at this point. In general, though, our usual approach would be to write an SQL query in ASpace to figure out where all of the issues are, and then turning to the API to try and fix those issues as safely as possible (but even that requires a lot of testing, since it's easy to mess things up when working in bulk, so we always test any new updates a few times before running it in our production system). If I recall correctly, someone added a nice fix for this at some point directly in ArchivesSpace that helps clean things up during the export process. I don't recall what/where that file is at the moment, though. I think it would probably be best to try to figure out why that process is not cleaning things up as expected in this particular case and then adding a fix for it there. Zach, is this happening in a lot of your files, or just this one (or some subset)? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Zachary L Pelli Sent: Monday, 26 November, 2018 3:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Mark, Regarding my instance in particular, would you recommend running that SQL block? I do not see a way to edit the XML from within AS itself, so I'm thinking that leaves the mysql DB or through the API. Regards, Zach -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, November 26, 2018 2:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Lydia, all: I don't know if it's a bug with the AT migrator, but I have raised this issue in 2014 when providing (a lot!) of feedback about the AT migration process. There are a couple of complicated issues, namely: All of those xlink namespace prefixes are treated and stored as text, not as XML (in both the AT and ASpace). So, it can be a bit dangerous and inefficient to change them in bulk. I had hoped that the migration tool would address that issue, but the decision at the time was not to have the migration tool do this. Because of that, we decided to address this prior to our migration with the following (albeit inelegant) SQL update: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FYaleArchivesSpace%2FmigrationSQL%2Fblob%2Fmaster%2FAllDatabasesPreMigration.sql%23L1-L26&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868575733&sdata=NSLLhJrJzC5gj2ImscUr0H5dz6Tq92DbXd%2BNt2pIvIM%3D&reserved=0 (that largely did the trick, if I recall correctly). All of those @target attributes are also stored as text. That was a lot messier, so the AT migration tool eventually added the ability to keep the ID values as is (e.g. "ref33" ==> "ref33") during the migration process, but you had to pass that argument (with the "-refid_original" flag) to the migration tool to keep those values as is. Anyhow, given the complexities of the migrations, it's hard to say what's a bug and what's behaving as expected (at least it's hard for me to remember everything involved). That said, Maureen did an AMAZING job of writing up our steps: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcampuspress.yale.edu%2Fyalearchivesspace%2F2015%2F06%2F14%2Fmigration-step-by-step%2F&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868575733&sdata=XI6wbhXAvK%2BU3uBEBDENjlU7vWdreaKSbTCtya58bl4%3D&reserved=0 . If anything in there is something that can be fixed with the AT migration tool, I'd be happy to provide more feedback on those tickets. That said, I'm honestly not sure how best to capture those there at this point (and I think / assumed that all of those issues were recorded in a previous bug/feature tracking system used by ASpace). Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, 26 November, 2018 1:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Hi Zach, Ed, and Mark, It sounds like this is a bug with the AT Migrator. Would you be willing to create a bug report for this in JIRA? On a quick search, it didn?t seem like this issue has been logged yet. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fsecure%2FDashboard.jspa&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868575733&sdata=4fDbmpMxzatNGU0WnM6LPpmj6%2BgedKS04lJw6Cb0y8I%3D&reserved=0 It would be great if you could include in the tags ?ATMigrator.? Thanks! Lydia -on behalf of Dev. Pri. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Monday, November 26, 2018 at 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Removing the ns2: prefix altogether should work, as should updating those ns2: prefixes to be xlink: prefixes (but it?s not good to have that in the text in the first place, so I wouldn?t advise that). I?m not sure why ASpace?s normal EAD cleaning process isn?t changing those prefixes to xlink prefixes during the export, though. Another issue (seeing that this came from the AT) is that the @target attributes in the EAD file don?t match any @id attributes (e.g. ?ref16? does not equal ?aspace_ref16_p33?). This won?t cause the file from converting to a PDF, but it?s still a broken link. All that said, if there?s no need to have a valid EAD file, then probably the easiest way to fix the PDF conversion issue (and something that ASpace could handle easily) would be to add a second namespace prefix for the xlink attributes. So, just changing this: To this: Given the broken links, though, which were also caused by the AT to ASpace migration (and the fact that ASpace prepends ?aspace_? during its EAD export process), I?d say that some data updates would have to happen at some point, though. But the above trick should allow you to create the PDF for this file with the least amount of editing. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Monday, 26 November, 2018 11:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing I just remove ns2: from ns2:actuate. Ed From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Monday, November 26, 2018 11:51 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Thanks for the reply, guys. I have attached the EAD file. This is indeed likely a carry-over from AT. I do not see a namespace declaration in the file, but I do see the ns2 prefixes. So would the solution be to eliminate the ns2 prefixes? Regards, Zach From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Custer, Mark Sent: Tuesday, November 20, 2018 3:43 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing Zach, I?d suggest exporting the EAD file and taking a look at the file that way (and I?d be happy to take a look if you can send it to me). Those ?ns2? namespace prefixes are likely from Archivist?s Toolkit, which at some point started appending that prefix for the xlink namespace (which is fine, but everything that looks like XML in the AT and ASpace is treated as text, and things can get messy when namespace prefixed are hardcoded in that text!). ArchivesSpace has a process to clean the XML upon export, which generally fixes a lot of those hard-coded namespace prefixes, but I?m honestly not sure why you?d be getting that error without seeing the entire EAD file since you shouldn?t even need a valid EAD file for the PDF process to potentially still work. There are other reasons why the PDF file not be created, but I can?t think of why that type of invalidity would cause it to fail on its own. Anyhow, the issue that?s being reported is that the EAD file that ASpace will produce for this record will have the following at the top of the file: xmlns:xlink=?http://www.w3.org/1999/xlink? Whereas what you have further down in your file on that ref tag is ?ns2:?, and if you export that same file from the AT (or whatever else caused the ns2 prefix to get in there), you?d see this at the top of the file: xmlns:ns2:?http://www.w3.org/1999/xlink? And ?xlink? does not equal ?ns2?, even though they?re both trying to stand in for the same namespace. All that said, the only way that I can think to troubleshoot the issue is investigating the EAD file itself, since the process for creating a PDF from the staff interface is 1) export the EAD, then 2) convert that EAD into a PDF file. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Tuesday, 20 November, 2018 2:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Print to PDF job failing The collection probably has a component title of the form The Alert--. These will generate an error when creating a finding aid in PDF format. The ns2 text around the title should be removed. For example, The Alert from the example above. So, you get to figure out which one it is. If you have access to the backend DB, you can probably come up with a query to find it. Or you can go through your Resource component lines looking for it. Good luck! Ed Busch, MLIS Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Tuesday, November 20, 2018 2:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Print to PDF job failing Hey all, One of our archivists is having an issue with a Print to PDF job with a particular collection (other large collections work fine). In the log within AS Background Jobs section, it gives this: Generating PDF for John M. Oesterreicher papers org.xml.sax.SAXParseException; lineNumber: 28; columnNumber: 76; The prefix "ns2" for attribute "ns2:actuate" associated with an element type "ref" is not bound. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/var/local/archivesspace/archivesspace250/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:39) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(var/local/archivesspace/archivesspace250/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) var.local.archivesspace.archivesspace250.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/var/local/archivesspace/archivesspace250/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Has anyone encountered this problem before? Regards, Zach Pelli Digital Collections Infrastructure Developer Seton Hall University Libraries 973.275.2046 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868585734&sdata=h6orhgOgR%2FsUZvEm1t9FNqoFdgYO8Hxgyb%2F273lxzg0%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868585734&sdata=h6orhgOgR%2FsUZvEm1t9FNqoFdgYO8Hxgyb%2F273lxzg0%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868585734&sdata=h6orhgOgR%2FsUZvEm1t9FNqoFdgYO8Hxgyb%2F273lxzg0%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868585734&sdata=h6orhgOgR%2FsUZvEm1t9FNqoFdgYO8Hxgyb%2F273lxzg0%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Cd6c8ba8235814427e9a708d653e33f5a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636788632868595738&sdata=jlKEcv%2FaWEmd1oYXEhNPvy42YEBrBj3lIPkq8zyN4go%3D&reserved=0 From mark.custer at yale.edu Tue Nov 27 09:23:13 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 27 Nov 2018 14:23:13 +0000 Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI In-Reply-To: References: <693b33c48d5f407c8aea2dbf0e882d24@uxcn13-ogg-c.UoA.auckland.ac.nz>, Message-ID: Stephen, This looks like a bug to me. I haven't had much time to look into it, but I have managed to replicate the issue and it appears to affect both the PUI *and* the EAD exports, as you note. The second part is very strange, since I know that I've tested those notes via EAD exports a few years ago. So, not sure if this is something new that's cropped up (which it seems to be, since I also thought that the PUI part worked in a previous version, though I've yet to verify that so I could be mistaken), or if it's a bug that's gone unnoticed for a long time. Anyhow, I'd suggest creating a JIRA report specifically for the issue about the bibliography notes (or I can do that by the end of the week, once I have a bit more time to dig into this). I'm going to try to test a few more things this week to see if I can't figure out what's going on. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver Sent: Wednesday, November 21, 2018 7:57:53 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Bibliography note not displaying in PUI Have a look in your logs, what's the error reported there? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Tuesday, November 20, 2018 8:48:20 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI I note that this issue appears to have been partially resolved with AR-1803. However, our Bibliography notes are not currently displaying in the PUI, eg in this record: https://archives.library.auckland.ac.nz/repositories/2/resources/668 Attached is a screenshot of the Bibliography note for this resource: Cuthbert family papers. MSS & Archives 2003/6. Also, the AS staff interface does not seem to be exporting this note either, as can be seen in the attached EAD record for the resource. Can someone update us on the status of this bug or suggest a solution? Regards, Stephen Innes Team Leader, Cultural Collections (Special Collections) 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 | Fax (649) 373-7565 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Nov 27 09:35:44 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 27 Nov 2018 14:35:44 +0000 Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI In-Reply-To: References: <693b33c48d5f407c8aea2dbf0e882d24@uxcn13-ogg-c.UoA.auckland.ac.nz>, , Message-ID: Stephen, all: Of course, right after I send the previous message, I tried to replicate the issue in yet another instance of ASpace, and everything works as expected there (well, aside from the fact that the index notes don't display very nicely in the PUI). See http://sandbox.archivesspace.org/public/repositories/2/resources/4 I did run into the same issue that you did when trying to replicate the issue in Yale's instance of ASpace (version 2.4.1, so a little bit behind the version where I know for sure that it works, but I'm also pretty sure that it worked in version 2.1, as well). I'm not sure if that's because the bibliography note isn't getting index in the first place or what, but I think we'll need to check the logs as Blake suggested. Anyhow, hopefully we can figure things out soon. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Tuesday, November 27, 2018 9:23:13 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Bibliography note not displaying in PUI Stephen, This looks like a bug to me. I haven't had much time to look into it, but I have managed to replicate the issue and it appears to affect both the PUI *and* the EAD exports, as you note. The second part is very strange, since I know that I've tested those notes via EAD exports a few years ago. So, not sure if this is something new that's cropped up (which it seems to be, since I also thought that the PUI part worked in a previous version, though I've yet to verify that so I could be mistaken), or if it's a bug that's gone unnoticed for a long time. Anyhow, I'd suggest creating a JIRA report specifically for the issue about the bibliography notes (or I can do that by the end of the week, once I have a bit more time to dig into this). I'm going to try to test a few more things this week to see if I can't figure out what's going on. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver Sent: Wednesday, November 21, 2018 7:57:53 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Bibliography note not displaying in PUI Have a look in your logs, what's the error reported there? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stephen Innes Sent: Tuesday, November 20, 2018 8:48:20 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Bibliography note not displaying in PUI I note that this issue appears to have been partially resolved with AR-1803. However, our Bibliography notes are not currently displaying in the PUI, eg in this record: https://archives.library.auckland.ac.nz/repositories/2/resources/668 Attached is a screenshot of the Bibliography note for this resource: Cuthbert family papers. MSS & Archives 2003/6. Also, the AS staff interface does not seem to be exporting this note either, as can be seen in the attached EAD record for the resource. Can someone update us on the status of this bug or suggest a solution? Regards, Stephen Innes Team Leader, Cultural Collections (Special Collections) 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 | Fax (649) 373-7565 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Tue Nov 27 10:52:45 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Tue, 27 Nov 2018 15:52:45 +0000 Subject: [Archivesspace_Users_Group] Alma/ArchivesSpace conference call information Message-ID: Hi All, For those interested in discussing Alma and ArchivesSpace integration, there is a conference call scheduled for tomorrow, Wed. November 28 at 1pm eastern. Below you will find the call information. I started a Google Drive that contains a loose agenda for the meeting and a copy of the Google Sheet that Megan started with interested parties. We were thinking it would be useful and efficient if folks wanted to fill out the spreadsheet with their goals for the call so that we could save time with introductions. https://drive.google.com/open?id=1QpnEj_CsTOzpgEz8FHpUAFB7cz8PVa3d Thanks! Adrien ----------------------------------------------------------------------------------------------- To join the audio portion of the Personal Conference meeting ----------------------------------------------------------------------------------------------- Call-in toll number (US/Canada): 1-650-479-3207 Global call-in numbers: https://harvard.webex.com/harvard/globalcallin.php?serviceType=MC&ED=694955102&tollFree=0 Attendee access code: 126 436 04 ----------------------------------------------------------------------------------------------- To join the online portion of the Personal Conference meeting ----------------------------------------------------------------------------------------------- 1. Go to https://harvard.webex.com/harvard/j.php?MTID=mcac5e3f140a792bedd2a5f20b30e8aa2 2. If a password is required, enter the Meeting Password: 12643604 https://www.webex.com IMPORTANT NOTICE: This Webex service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. IMPORTANT NOTICE: This Webex service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Tue Nov 27 16:59:41 2018 From: mkottman at ku.edu (Kottman, Miloche) Date: Tue, 27 Nov 2018 21:59:41 +0000 Subject: [Archivesspace_Users_Group] Another Reordering Question In-Reply-To: References: Message-ID: VivianLea, If you are using a version of ArchivesSpace that has the "Enable Reorder Mode" button, the ctrl+shift+click doesn't work like it does in other windows programs. Instead do the following to select multiple records: Multiple records NOT adjacent: 1. In reorder mode, hold down key and click on the two columns of dots at the far left of the first record you want to move. This should highlight your selected title 2. Hold down the key and click on the two columns of dots at the far left of the second record you want to move. This should highlight your second selected title and provide a numeric designation of the order that the titles will be moved [cid:image003.jpg at 01D4866A.346DE660] 3. Continue until you've selected all the title you want to move then drag them to the appropriate location Multiple records that are adjacent: 1. In reorder mode, hold down key and click on the two columns of dots at the far left of the first record you want to move. This should highlight your selected title 2. Let go of the key 3. Hold down the key and click on the last record in the list you want to move. This will highlight and enumerate all the records between the first and last record you selected [cid:image004.jpg at 01D4866A.346DE660] 4. Drag the records to the appropriate location as usual --Miloche ****************************** Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Solek, VivianLea Sent: Tuesday, November 20, 2018 1:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Another Reordering Question I believe the answer to my last post was "it was a pre-Thanksgiving mental fit." After posting I went back in and it had reappeared. So the next question is, when reading the manual, it says that you can select multiple items by using the ctrl+click. However, when I use that combination (or shift+click or alt+click, it justs open another browser tab with the same page. Is this a bug that has been identified? I'm in version 2.4.1 and we are self-hosting. Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 7117 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 8648 bytes Desc: image004.jpg URL: From mark.custer at yale.edu Tue Nov 27 17:24:54 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 27 Nov 2018 22:24:54 +0000 Subject: [Archivesspace_Users_Group] Another Reordering Question In-Reply-To: References: Message-ID: Miloche, That is some first-rate documentation! Thank you. I almost always forget how to select multiple adjacent records since I so rarely do that (and switching between CTRL and Shift is not so intuitive, and I always try to start with the Shift key). I?m going to print out your email and post it near my computer right now. I?ll probably print out a few for colleagues, too ? Thanks again, 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: Tuesday, 27 November, 2018 5:00 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Another Reordering Question VivianLea, If you are using a version of ArchivesSpace that has the ?Enable Reorder Mode? button, the ctrl+shift+click doesn?t work like it does in other windows programs. Instead do the following to select multiple records: Multiple records NOT adjacent: 1. In reorder mode, hold down key and click on the two columns of dots at the far left of the first record you want to move. This should highlight your selected title 2. Hold down the key and click on the two columns of dots at the far left of the second record you want to move. This should highlight your second selected title and provide a numeric designation of the order that the titles will be moved [cid:image001.jpg at 01D48676.1B69F9E0] 1. Continue until you?ve selected all the title you want to move then drag them to the appropriate location Multiple records that are adjacent: 1. In reorder mode, hold down key and click on the two columns of dots at the far left of the first record you want to move. This should highlight your selected title 2. Let go of the key 3. Hold down the key and click on the last record in the list you want to move. This will highlight and enumerate all the records between the first and last record you selected [cid:image002.jpg at 01D48676.1B69F9E0] 1. Drag the records to the appropriate location as usual --Miloche ?????????????????????????????? Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Solek, VivianLea Sent: Tuesday, November 20, 2018 1:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Another Reordering Question I believe the answer to my last post was ?it was a pre-Thanksgiving mental fit.? After posting I went back in and it had reappeared. So the next question is, when reading the manual, it says that you can select multiple items by using the ctrl+click. However, when I use that combination (or shift+click or alt+click, it justs open another browser tab with the same page. Is this a bug that has been identified? I?m in version 2.4.1 and we are self-hosting. Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 7117 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8648 bytes Desc: image002.jpg URL: From VivianLea.Solek at Kofc.Org Wed Nov 28 07:56:48 2018 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Wed, 28 Nov 2018 12:56:48 +0000 Subject: [Archivesspace_Users_Group] Another Reordering Question In-Reply-To: References: Message-ID: Good morning Miloche, Thank you VERY much for these great instructions. I'm off to give it a try now. Happy Wednesday! Best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kottman, Miloche Sent: Tuesday, November 27, 2018 5:00 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Another Reordering Question VivianLea, If you are using a version of ArchivesSpace that has the "Enable Reorder Mode" button, the ctrl+shift+click doesn't work like it does in other windows programs. Instead do the following to select multiple records: Multiple records NOT adjacent: 1. In reorder mode, hold down key and click on the two columns of dots at the far left of the first record you want to move. This should highlight your selected title 2. Hold down the key and click on the two columns of dots at the far left of the second record you want to move. This should highlight your second selected title and provide a numeric designation of the order that the titles will be moved [cid:image001.jpg at 01D486EF.CE193050] 3. Continue until you've selected all the title you want to move then drag them to the appropriate location Multiple records that are adjacent: 1. In reorder mode, hold down key and click on the two columns of dots at the far left of the first record you want to move. This should highlight your selected title 2. Let go of the key 3. Hold down the key and click on the last record in the list you want to move. This will highlight and enumerate all the records between the first and last record you selected [cid:image002.jpg at 01D486EF.CE193050] 4. Drag the records to the appropriate location as usual --Miloche ****************************** Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Solek, VivianLea Sent: Tuesday, November 20, 2018 1:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Another Reordering Question I believe the answer to my last post was "it was a pre-Thanksgiving mental fit." After posting I went back in and it had reappeared. So the next question is, when reading the manual, it says that you can select multiple items by using the ctrl+click. However, when I use that combination (or shift+click or alt+click, it justs open another browser tab with the same page. Is this a bug that has been identified? I'm in version 2.4.1 and we are self-hosting. Many thanks! VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 7117 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8648 bytes Desc: image002.jpg URL: From kws2126 at columbia.edu Wed Nov 28 12:42:31 2018 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Wed, 28 Nov 2018 12:42:31 -0500 Subject: [Archivesspace_Users_Group] Collection-level EAD records in OAI feed based on child record updates Message-ID: Hi all, We are investigating a few different ways to use the OAI feed for our nightly EAD publication. We've noticed in testing that when a child component is updated, the collection-level parent does not appear in the OAI feed. Does anyone know if it is possible to have parent timestamps update based on child timestamps in the OAI feed itself? I'm pretty sure we could do this with the API, but we are hoping the leverage the OAI feed since we already use that for our library catalog updates. Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 From sdm7g at virginia.edu Wed Nov 28 12:56:09 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 28 Nov 2018 17:56:09 +0000 Subject: [Archivesspace_Users_Group] Collection-level EAD records in OAI feed based on child record updates In-Reply-To: References: Message-ID: <73895025-323B-4EBD-849E-D1F0E58FA3AB@virginia.edu> This feature should be in the next release (thanks to Mark Cooper! ): https://github.com/archivesspace/archivesspace/pull/1374 > On Nov 28, 2018, at 12:42 PM, Kevin W. Schlottmann wrote: > > Hi all, > > We are investigating a few different ways to use the OAI feed for our > nightly EAD publication. We've noticed in testing that when a child > component is updated, the collection-level parent does not appear in > the OAI feed. Does anyone know if it is possible to have parent > timestamps update based on child timestamps in the OAI feed itself? > > I'm pretty sure we could do this with the API, but we are hoping the > leverage the OAI feed since we already use that for our library > catalog updates. > > Kevin > > -- > Kevin Schlottmann > Head of Archives Processing > Rare Book & Manuscript Library > Butler Library, Room 801 > Columbia University > 535 W. 114th St., New York, NY 10027 > (212) 854-8483 > > _______________________________________________ > 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: 6102 bytes Desc: not available URL: From kws2126 at columbia.edu Wed Nov 28 12:58:28 2018 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Wed, 28 Nov 2018 12:58:28 -0500 Subject: [Archivesspace_Users_Group] Collection-level EAD records in OAI feed based on child record updates In-Reply-To: <73895025-323B-4EBD-849E-D1F0E58FA3AB@virginia.edu> References: <73895025-323B-4EBD-849E-D1F0E58FA3AB@virginia.edu> Message-ID: Awesome! Thanks, Steve and Mark. On Wed, Nov 28, 2018 at 12:56 PM Majewski, Steven Dennis (sdm7g) wrote: > > > This feature should be in the next release (thanks to Mark Cooper! ): > > https://github.com/archivesspace/archivesspace/pull/1374 > > > > > On Nov 28, 2018, at 12:42 PM, Kevin W. Schlottmann wrote: > > Hi all, > > We are investigating a few different ways to use the OAI feed for our > nightly EAD publication. We've noticed in testing that when a child > component is updated, the collection-level parent does not appear in > the OAI feed. Does anyone know if it is possible to have parent > timestamps update based on child timestamps in the OAI feed itself? > > I'm pretty sure we could do this with the API, but we are hoping the > leverage the OAI feed since we already use that for our library > catalog updates. > > Kevin > > -- > Kevin Schlottmann > Head of Archives Processing > Rare Book & Manuscript Library > Butler Library, Room 801 > Columbia University > 535 W. 114th St., New York, NY 10027 > (212) 854-8483 > > _______________________________________________ > 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 -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 From ltang5 at lib.msu.edu Thu Nov 29 10:13:10 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 29 Nov 2018 15:13:10 +0000 Subject: [Archivesspace_Users_Group] ArcLight or other aggregation tools for discovery Message-ID: <473518DB-DDFF-49BF-8169-FF1CACDFFFB2@lib.msu.edu> Hi all, At Michigan State, we currently have two distinct instances of ArchivesSpace and have been interested in the possibility of merging instances (but keeping our unique repositories). So far, it seems like there are challenges relating to reconciling overlapping agents and subjects and possibly some challenges with migrating our locations, events, and other meta-records in our individual databases. With this in mind, I am curious to hear if some institutions keep their separate instances but successfully are able to combine their discovery experience using the API or OAI-PMH (sorry, I?m no techie and this may be basically the same approach). I?m curious about the status of ArcLight. http://archival-integration.blogspot.com/2015/07/archivesspace-blacklight-arclight.html Any news there? Any other ideas are very welcome! 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 reesj at mail.nlm.nih.gov Fri Nov 30 15:42:04 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Fri, 30 Nov 2018 20:42:04 +0000 Subject: [Archivesspace_Users_Group] ArcLight or other aggregation tools for discovery In-Reply-To: <473518DB-DDFF-49BF-8169-FF1CACDFFFB2@lib.msu.edu> References: <473518DB-DDFF-49BF-8169-FF1CACDFFFB2@lib.msu.edu> Message-ID: Lydia, ArcLight completed a MVP work cycle last summer and a few institutions have done some local work since then, notably the Bentley and U. Albany. Mark Matienzo is the Stanford POC. You can take a look at the ArcLight Community Google Group, or request to join the Slack channel. G Group: https://groups.google.com/forum/#!forum/arclight-community Working channel for the ArcLight project: http://bit.ly/arclight-project Git repo: https://github.com/sul-dlss/arclight MVP demo instance: https://arclight-demo.projectblacklight.org/ John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -----Original Message----- From: Tang, Lydia Sent: Thursday, November 29, 2018 10:13 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ArcLight or other aggregation tools for discovery Hi all, At Michigan State, we currently have two distinct instances of ArchivesSpace and have been interested in the possibility of merging instances (but keeping our unique repositories). So far, it seems like there are challenges relating to reconciling overlapping agents and subjects and possibly some challenges with migrating our locations, events, and other meta-records in our individual databases. With this in mind, I am curious to hear if some institutions keep their separate instances but successfully are able to combine their discovery experience using the API or OAI-PMH (sorry, I?m no techie and this may be basically the same approach). I?m curious about the status of ArcLight. http://archival-integration.blogspot.com/2015/07/archivesspace-blacklight-arclight.html Any news there? Any other ideas are very welcome! 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 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group