From livsolis at utexas.edu Fri Mar 1 10:24:30 2019 From: livsolis at utexas.edu (Olivia S Solis) Date: Fri, 1 Mar 2019 09:24:30 -0600 Subject: [Archivesspace_Users_Group] Empty space within a box In-Reply-To: References: Message-ID: Thank you Paul and Laurel for your responses! Paul, there doesn't appear to be any kind of note we can attach to the box itself as it relates to features of the box. We can attach a note about the box's location, as shown in the attachments to this email where "OD" represents "oversize drawer" ? we still need to go back and number the specific folders within the drawer, which we treat as a location. But remaining extent isn't related to location, so I'm loath to document this information in the location note. And again in some cases, as in the second screenshot attached, there can be dozens different archival objects in a container, documenting this kind of info in archival objects is not feasible. Incidentally, we'd love to have a note for boxes themselves for instances e.g. when a box's name has changed or the box is dedicated to separated born-digital materials. Laurel, that may be a solution. But as we already have 175 different container profiles, one that could be difficult to manage, particularly since our processors sometimes need to know that the box has 3 vs 1 inches remaining. Still, the primary candidates are bankers boxes and Hollingers, so it could be possible to restrict these kinds of container profiles to those container types. I will raise this option with my team. Again, thank you for your input!! On Thu, Feb 28, 2019 at 9:57 AM McPhee, Laurel wrote: > Hi Olivia, > > > > If I understand your problem correctly, it may be similar to something > we?ve addressed using the container profile feature. > > > > We recently completed a survey of our map case drawers, and wanted to > express each drawer as a shared top container (each drawer can contain many > oversize folders, of course, from different collections). The challenge was > we also wanted to find a way to communicate if a drawer was full, or had > space in it for more, so someone could be at their desk using ASpace and > figure out a likely location to put something new (as opposed to going on a > space-hunting expedition in the stacks). > > > > Our solution was to create our 200-or-so map case drawer top containers > (the unique indicator for each one is MC-XXX, X being the drawer number) , > but based on our survey, also assign a profile to each drawer that makes > the ?status? of the drawer explicit: the name of the profile assigned to > each drawer is either ?Map case drawer ? AVAILABLE? or ?Map case drawer ? > FULL?. Using the assigned profiles, we always know what has space in it, > and what is stuffed, because we can search on that profile name. And if a > processor fills up a drawer, they simply change the profile from AVAILABLE > to FULL. I?m not sure if this is a hacky work-around, or a brilliant > solution, but it works for us, and got us away from having a separate, > always out-of-date spreadsheet that told us the status of our drawers. It > does require a fresh survey, for which we used undergraduate workers, to > give you a snapshot of your container situation. > > > > May all your containers be half full J, > > Laurel > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia > S Solis > *Sent:* Wednesday, February 27, 2019 12:46 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Empty space within a box > > > > Hello all, > > > > We've been wondering if we are alone in this struggle. So we are a > space-deficient archives. Our stacks are boxed to the brim and processors > hunt for on-site space voraciously, particularly for collections that are > just a few inches in extent. For this reason, we have a column in our > spreadsheet shelf lists ? which we're trying to wean off of now that we are > increasingly utilizing the container management functionality of ASpace ? > that includes inches left in a box. There are some boxes that house 20 or > so different small collections, so documenting this information at the > archival object level seems, to put it mildly, inefficient. > > > > Does anyone else have this problem? If so, have you found a way to address > it in ASpace? > > > > Thanks, > > Olivia > > > > -- > > Olivia Solis, MSIS > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2019-03-01 at 8.59.23 AM.png Type: image/png Size: 123202 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2019-03-01 at 9.05.10 AM.png Type: image/png Size: 131372 bytes Desc: not available URL: From kate_bowers at harvard.edu Fri Mar 1 11:49:16 2019 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Fri, 1 Mar 2019 16:49:16 +0000 Subject: [Archivesspace_Users_Group] Empty space within a box In-Reply-To: References: Message-ID: What you are looking for is what we have in our local container management system, and that is a concept called ?group box?. Many repositories have these, some call them shared boxes, or small collection boxes, or have other terms for this common practice that doesn?t have a common name. A group box is a chimera that is not difficult to model in relational databse: * Administratively, it is a shelving convention, so it has relationships to the archival containers that it holds * Physically, it a box, so it also has characteristics of a box such as a container profile, and a relationship with a location. We are unfortunately unlikely to see this concept developed for ArchivesSpace any time soon. At the Harvard University Archives (HUA) we are planning to migrate our local container management system to ArchivesSpace, we are sad to say we have to choose only one of these types of records to try to hold this data. We are working on modeling these as locations. One reason is that we have about 9000 group boxes holding 85,000 containers. By sheer numbers, 85,000 is the worse impact. The greatest reason we will model these as shelves is that we have extensive container information and if we were to transform containers to ?subcontainers? in ArchivesSpace, we would lose all the container profile information on those 85,000 things. Modeling a ?location? with essentially a box profile means we can eventually upgrade these group box ?location? records to actual group boxes in some future system that accommodates group boxes or a future version of ArchivesSpace that has this concept. Here?s a few screenshots from our test system showing how HUA is planning to model a shelf/location as a group box (this is in the planning and testing stages, not implemented yet). The location profile for a document box size group box: [cid:image003.jpg at 01D4D024.CB501450] A group box expressed as a location [cid:image004.jpg at 01D4D024.CB501450] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Olivia S Solis Sent: Friday, March 01, 2019 10:25 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Empty space within a box Thank you Paul and Laurel for your responses! Paul, there doesn't appear to be any kind of note we can attach to the box itself as it relates to features of the box. We can attach a note about the box's location, as shown in the attachments to this email where "OD" represents "oversize drawer" ? we still need to go back and number the specific folders within the drawer, which we treat as a location. But remaining extent isn't related to location, so I'm loath to document this information in the location note. And again in some cases, as in the second screenshot attached, there can be dozens different archival objects in a container, documenting this kind of info in archival objects is not feasible. Incidentally, we'd love to have a note for boxes themselves for instances e.g. when a box's name has changed or the box is dedicated to separated born-digital materials. Laurel, that may be a solution. But as we already have 175 different container profiles, one that could be difficult to manage, particularly since our processors sometimes need to know that the box has 3 vs 1 inches remaining. Still, the primary candidates are bankers boxes and Hollingers, so it could be possible to restrict these kinds of container profiles to those container types. I will raise this option with my team. Again, thank you for your input!! On Thu, Feb 28, 2019 at 9:57 AM McPhee, Laurel > wrote: Hi Olivia, If I understand your problem correctly, it may be similar to something we?ve addressed using the container profile feature. We recently completed a survey of our map case drawers, and wanted to express each drawer as a shared top container (each drawer can contain many oversize folders, of course, from different collections). The challenge was we also wanted to find a way to communicate if a drawer was full, or had space in it for more, so someone could be at their desk using ASpace and figure out a likely location to put something new (as opposed to going on a space-hunting expedition in the stacks). Our solution was to create our 200-or-so map case drawer top containers (the unique indicator for each one is MC-XXX, X being the drawer number) , but based on our survey, also assign a profile to each drawer that makes the ?status? of the drawer explicit: the name of the profile assigned to each drawer is either ?Map case drawer ? AVAILABLE? or ?Map case drawer ? FULL?. Using the assigned profiles, we always know what has space in it, and what is stuffed, because we can search on that profile name. And if a processor fills up a drawer, they simply change the profile from AVAILABLE to FULL. I?m not sure if this is a hacky work-around, or a brilliant solution, but it works for us, and got us away from having a separate, always out-of-date spreadsheet that told us the status of our drawers. It does require a fresh survey, for which we used undergraduate workers, to give you a snapshot of your container situation. May all your containers be half full ?, Laurel From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Olivia S Solis Sent: Wednesday, February 27, 2019 12:46 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Empty space within a box Hello all, We've been wondering if we are alone in this struggle. So we are a space-deficient archives. Our stacks are boxed to the brim and processors hunt for on-site space voraciously, particularly for collections that are just a few inches in extent. For this reason, we have a column in our spreadsheet shelf lists ? which we're trying to wean off of now that we are increasingly utilizing the container management functionality of ASpace ? that includes inches left in a box. There are some boxes that house 20 or so different small collections, so documenting this information at the archival object level seems, to put it mildly, inefficient. Does anyone else have this problem? If so, have you found a way to address it in ASpace? Thanks, Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 15336 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 113335 bytes Desc: image004.jpg URL: From christine.dibella at lyrasis.org Fri Mar 1 16:19:13 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 1 Mar 2019 21:19:13 +0000 Subject: [Archivesspace_Users_Group] registration now open: ArchivesSpace Online Forum, March 18 Message-ID: (We'll have more publicity and additional details next week, but I wanted to make sure you all knew this news first!) Registration is now open for the first ever ArchivesSpace Online Forum. You can learn more about the event at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ArchivesSpace+Online+Forum+2019. Anyone interested in ArchivesSpace is welcome to attend, so please feel free to forward this message to anyone you think might be interested.. Divided into three blocks of 3 hours each, with a 1-hour break between each block, the developing program features sessions on navigating your ArchivesSpace implementation, working with IT, creating workflows and integrations for digital objects, regional discovery networks for archives, customizing the public interface, and making your case for ArchivesSpace, among other topics. As with our in-person forums, our Online Forum will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace. When: March 18 beginning at 5:00 p.m. UTC - see https://goo.gl/sCKvA9 to find your local time Online registration: https://www.eventbrite.com/e/archivesspace-online-forum-2019-registration-57088627622 Please register if you plan to attend any part of the Forum. We anticipate recording many parts of the event, but for it to be a success we will also need plenty of live participants. We encourage you to dip in and out of the live program as you much as you can. You will no doubt "meet" a different set of colleagues each time. Thanks so much to our international working group who have been working hard to bring you this new event, and please feel free to contact me with questions. We look forward to seeing many of you there! -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Mar 4 10:19:56 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 4 Mar 2019 15:19:56 +0000 Subject: [Archivesspace_Users_Group] FW: Accessibility Survey Deadline Extended In-Reply-To: References: Message-ID: Forwarded on behalf of our colleagues in LYRASIS. Please contact Jill (jill.grogg at lyrasis.org) or Hannah (hannah.rosen at lyrasis.org) with any questions. Thanks to all who have already participated! We would like to thank all those who have filled out the LYRASIS Accessibility Survey; we are very pleased with the survey response rate. Recently, several participants have asked for more time to fill out the survey, so we have decided to extend the deadline to March 22nd. Please see below for details. Reminder: Request for Participation in Accessibility Survey Please take approximately 10 minutes to fill out the following survey: https://www.surveymonkey.com/r/D2FX69V. The deadline for participation is March 22nd, 2019. Please feel free to share the survey with your colleagues for questions outside your job duties. We realize multiple responses from one institution may be necessary. This survey is intended to serve two general purposes. First, we would like to offer LYRASIS members and participants in the broader GLAM (galleries, libraries, archives and museums) community a new perspective on how accessibility is embedded in our work with collections and systems. Second, we would like to understand how we can better serve LYRASIS members/users in terms of the accessibility requirements of our products, services, and platforms. We appreciate your taking the time to answer this survey in order to achieve the broadest possible response from GLAM institutions of all shapes and sizes. The survey is divided into three sections concerning three different areas of responsibility: purchasing content, creating content, and purchasing systems. Most survey respondents will only be responsible for one or two of these areas within their institution. For any areas that you are not responsible for, please indicate "no" in the survey question, and you will be taken to the next section of the survey. At the beginning of the survey you will be asked for your name, institution and job title. All of this information will remain confidential, and will not be included in any external publications/reports or presentations. We are merely using this information to identify duplicate entries across our distribution channels. Please contact Jill Grogg, Scholarly Communication Strategist, at jill.grogg at lyrasis.org, or Hannah Rosen, Scholarly Communication Specialist, at hannah.rosen at lyrasis.org, with any questions. Thank you, LYRASIS Content and Scholarly Communication Initiatives Team [cid:D9C43C04-DF4E-467C-B0BC-358EF417F998] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 4483 bytes Desc: image002.png URL: From rex.hughes at ndsu.edu Wed Mar 6 10:20:05 2019 From: rex.hughes at ndsu.edu (Hughes ll, Rex) Date: Wed, 6 Mar 2019 15:20:05 +0000 Subject: [Archivesspace_Users_Group] Merging Extent Types Message-ID: Hello, I am attempting to work with our Controlled Value Lists in ArchivesSpace by merging extent types into default values. When we imported our MARC-XML files into ArchivesSpace, the system generated extent types based upon the description in the 300 field. While this does not inhibit description of the resources, since the extent description remains the same, I would still like to merge these added values into default/core values to make the search for extent type more cohesive. I was able to find the Controlled Value List, but every time I choose the option to merge an added value into a core value, the added value disappears and does not appear to merge with the default. For example, I attempted to merge "cassettes" (3 related resources) with "Cassettes" (no resources, not used), but after selecting Merge on the "cassettes" value and selecting "Cassettes" as the preferred value, the added value disappeared and I am still left with the default "Cassettes" value with no related resources (not used). Would anyone be able to provide advice on this matter? Thank you! [cid:image001.jpg at 01D4D3FD.C82D8500] Rex Hughes, II, M.L.I.S. Metadata and Cataloging Librarian Resource Acquisition, Management, and Discovery Subject Liaison to Apparel, Retail Merchandising & Design NDSU Libraries Dept. 2080, PO Box 6050 / Fargo ND 58108-6050 Phone:701.231.9677 (Main Library 120G) [ndsu_sig] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 69148 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 2861 bytes Desc: image002.jpg URL: From laurie.arp at lyrasis.org Wed Mar 6 12:34:34 2019 From: laurie.arp at lyrasis.org (Laurie Arp) Date: Wed, 6 Mar 2019 17:34:34 +0000 Subject: [Archivesspace_Users_Group] New ArchivesSpace Community Engagement Coordinator: Jessica Crouch Message-ID: LYRASIS, the organizational home for ArchivesSpace, is pleased to announce that Jessica Dowd Crouch will be joining us as our Community Engagement Coordinator. Jessica has been an archivist in the Irvin Department of Rare Books and Special Collections at the University of South Carolina (USC) since 2014, where she has been involved in all aspects of managing physical and digital collections and making them accessible, including providing outreach to donors and users. She has taken a leading role in the implementation of ArchivesSpace across the many varied repositories at the University, working closely with her colleagues to develop training, documentation, and opportunities for collaboration as well as working closely with the developers and system administrators who facilitate the technical side of their ArchivesSpace implementation. As a graduate student and early professional, she had previously been actively involved in USC's implementation of Archivists' Toolkit. Jessica has presented and provided archival instruction to a wide variety of groups. She is professionally active in the Society of American Archivists and the Rare Books and the Manuscripts Section of the Association of College and Research Libraries. She received an MLIS from the University of South Carolina and has an undergraduate degree in history from Wofford College. Already deeply involved in the ArchivesSpace community, Jessica served on our Public User Interface Enhancement group in its design phase and is currently involved in our Online Forum working group. As Community Engagement Coordinator, Jessica will be responsible for user support, training, outreach, and communications across the ArchivesSpace community and will work especially closely with the User Documentation and Testing sub-teams of our Advisory Councils. She will continue the great work already started in developing events and activities that further bring our community together, and also help us consider new areas for connection as our community continues to grow and mature. Jessica's first day will be April 1, though her involvement in the Online Forum working group has her working closely with our community even before that. Jessica will continue to be based in South Carolina, but is sure to become an even more familiar member of our community as she gets more active in our online activities and represents ArchivesSpace at face-to-face conferences. Please join us in welcoming Jessica to the ArchivesSpace team! Laurie Gemmill Arp Director, Collections Services & Community Supported Software laurie.arp at lyrasis.org 800.999.8558 x 2908 laurie.gemmill1 Skype [cid:D9C43C04-DF4E-467C-B0BC-358EF417F998] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4483 bytes Desc: image001.png URL: From akroeger at unomaha.edu Wed Mar 6 13:12:30 2019 From: akroeger at unomaha.edu (Angela Kroeger) Date: Wed, 6 Mar 2019 18:12:30 +0000 Subject: [Archivesspace_Users_Group] Merging Extent Types In-Reply-To: References: Message-ID: Rex Hughes said, "I was able to find the Controlled Value List, but every time I choose the option to merge an added value into a core value, the added value disappears and does not appear to merge with the default. For example, I attempted to merge 'cassettes' (3 related resources) with 'Cassettes' (no resources, not used), but after selecting Merge on the 'cassettes' value and selecting 'Cassettes' as the preferred value, the added value disappeared and I am still left with the default 'Cassettes' value with no related resources (not used)." Try reindexing your system. I recently merged many near-duplicate controlled values in our system (also the result of imported values). When I merged the first one, I picked something with only a few records attached to each value, made note of all affected resource records, and then checked every one of them after the merge. Although the displayed number of related records did not increment to the sum of the two merged values, all resources which had previously had the value that was merged out of existence (e.g.: "cassettes" in your case) correctly displayed the new value (e.g.: "Cassettes"). However, even after a couple of days, the number of related records for that value had not updated. We asked to have our system reindexed, and after that, the related resources number and link correctly included all of the records that had the merged value. So if you look at the three resource records that used to have "cassettes," you should find that they correctly have "Cassettes" now, even if the link to related resources doesn't include them. Once you reindex your system, the related resources value should be accurate. Hope that helps! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [Media:UniversityCommunications:Graphic Design:Brand tools:Logos- UNO:Vector files:Lock-up:Lockup-color on white backgrnd.eps] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5540 bytes Desc: image003.png URL: From rex.hughes at ndsu.edu Wed Mar 6 14:31:27 2019 From: rex.hughes at ndsu.edu (Hughes ll, Rex) Date: Wed, 6 Mar 2019 19:31:27 +0000 Subject: [Archivesspace_Users_Group] Merging Extent Types Message-ID: Dear Angela, Thank you so much for your response! I will ask our Systems Department if we can reindex and see if this updates the controlled value. Have a great day! Sincerely, Rex Hughes From: Kroeger, Angela Sent: Wednesday, March 6, 2019 12:12 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: Merging Extent Types Rex Hughes said, "I was able to find the Controlled Value List, but every time I choose the option to merge an added value into a core value, the added value disappears and does not appear to merge with the default. For example, I attempted to merge 'cassettes' (3 related resources) with 'Cassettes' (no resources, not used), but after selecting Merge on the 'cassettes' value and selecting 'Cassettes' as the preferred value, the added value disappeared and I am still left with the default 'Cassettes' value with no related resources (not used)." Try reindexing your system. I recently merged many near-duplicate controlled values in our system (also the result of imported values). When I merged the first one, I picked something with only a few records attached to each value, made note of all affected resource records, and then checked every one of them after the merge. Although the displayed number of related records did not increment to the sum of the two merged values, all resources which had previously had the value that was merged out of existence (e.g.: "cassettes" in your case) correctly displayed the new value (e.g.: "Cassettes"). However, even after a couple of days, the number of related records for that value had not updated. We asked to have our system reindexed, and after that, the related resources number and link correctly included all of the records that had the merged value. So if you look at the three resource records that used to have "cassettes," you should find that they correctly have "Cassettes" now, even if the link to related resources doesn't include them. Once you reindex your system, the related resources value should be accurate. Hope that helps! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu> From: Hughes ll, Rex Sent: Wednesday, March 6, 2019 9:20 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: Merging Extent Types Hello, I am attempting to work with our Controlled Value Lists in ArchivesSpace by merging extent types into default values. When we imported our MARC-XML files into ArchivesSpace, the system generated extent types based upon the description in the 300 field. While this does not inhibit description of the resources, since the extent description remains the same, I would still like to merge these added values into default/core values to make the search for extent type more cohesive. I was able to find the Controlled Value List, but every time I choose the option to merge an added value into a core value, the added value disappears and does not appear to merge with the default. For example, I attempted to merge "cassettes" (3 related resources) with "Cassettes" (no resources, not used), but after selecting Merge on the "cassettes" value and selecting "Cassettes" as the preferred value, the added value disappeared and I am still left with the default "Cassettes" value with no related resources (not used). Would anyone be able to provide advice on this matter? Thank you! [cid:image001.jpg at 01D4D420.E1484980] Rex Hughes, II, M.L.I.S. Metadata and Cataloging Librarian Resource Acquisition, Management, and Discovery Subject Liaison to Apparel, Retail Merchandising & Design NDSU Libraries Dept. 2080, PO Box 6050 / Fargo ND 58108-6050 Phone:701.231.9677 (Main Library 120G) [ndsu_sig] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 69148 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 2861 bytes Desc: image002.jpg URL: From s.innes at auckland.ac.nz Wed Mar 6 20:54:38 2019 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Thu, 7 Mar 2019 01:54:38 +0000 Subject: [Archivesspace_Users_Group] Media collections in ArchivesSpace? Message-ID: <4739a59d29c24ecf880981b5347e2c2f@uxcn13-ogg-c.UoA.auckland.ac.nz> Can anyone point us to AS sites which manage their audiovisual/media archives in AS? We are considering moving a large ethnographic audio and video archive collection to AS and wanted to demonstrate the capabilities of the system in successfully managing both analogue and digital objects. Thanks, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsteele at jhu.edu Fri Mar 8 14:29:19 2019 From: jsteele at jhu.edu (Jordon Steele) Date: Fri, 8 Mar 2019 19:29:19 +0000 Subject: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? Message-ID: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu> Hi all, This is more of an archival description question, but I'm not a member of that listserv, so I figured it would be easier to ping some of you about this for advice since I wager there's a lot of overlap. We have not-infrequent discussions around here about what "level of description" label to assign to an archival component at a given level, i.e. collection, series, file, item, etc. But because our data is already structured in hierarchical relationships via EAD/JSON, there's no real need to "tell the computer" what level this is since these labels aren't the way computers understand context and hierarchy, the nesting of data is. Once I realized this, I often made the case that these level-of-description labels are useful for stylesheets, i.e. tell a stylesheet with level=series to make it all caps and bold, level=file should be red, etc. But the ASpace PUI doesn't/doesn't need to style levels in this manner for the hierarchy to be easily understood. So we're considering discontinuing use of the "level of description" field in ASpace. But am I missing an important value of this field? Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu 410-516-5493 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Fri Mar 8 14:41:40 2019 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Fri, 8 Mar 2019 14:41:40 -0500 Subject: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? In-Reply-To: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu> References: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu> Message-ID: I believe the level of description field is required in ArchivesSpace, so it may be difficult for you to stop using it even if you want to. On Fri, Mar 8, 2019 at 2:29 PM Jordon Steele wrote: > Hi all, > > > > This is more of an archival description question, but I?m not a member of > that listserv, so I figured it would be easier to ping some of you about > this for advice since I wager there?s a lot of overlap. > > > > We have not-infrequent discussions around here about what ?level of > description? label to assign to an archival component at a given level, > i.e. collection, series, file, item, etc. But because our data is already > structured in hierarchical relationships via EAD/JSON, there?s no real need > to ?tell the computer? what level this is since these labels aren?t the way > computers understand context and hierarchy, the nesting of data is. > > > > Once I realized this, I often made the case that these > level-of-description labels are useful for stylesheets, i.e. tell a > stylesheet with level=series to make it all caps and bold, level=file > should be red, etc. But the ASpace PUI doesn?t/doesn?t need to style levels > in this manner for the hierarchy to be easily understood. > > > > So we?re considering discontinuing use of the ?level of description? field > in ASpace. But am I missing an important value of this field? Thanks! > > > > Best, > > > > Jordon > > > > Jordon Steele > > Hodson Curator of the University Archives > > Sheridan Libraries > > Johns Hopkins University > > 3400 N Charles St > > Baltimore, MD 21218 > > jsteele at jhu.edu > > 410-516-5493 > > he/him/his > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Mar 8 14:51:42 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 8 Mar 2019 19:51:42 +0000 Subject: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? In-Reply-To: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu> References: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu> Message-ID: In EAD, the hierarchy is fixed, but one of the advantages of linked data is that the elements are movable and reusable in other contexts. We?re not really taking advantage of that currently in ArchivesSpace, but for the future I think it makes sense to think about those use cases and whether level-of-description might be useful if the archival object is removed from its context. ( For example, organizing artificial or virtual collections from subsets or multiple archival collections for exhibits or other display purposes ? whether that?s done in ArchivesSpace or by another tool importing info from ArchivesSpace. ) I will also note that we are currently integrating Aeon with ArchivesSpace ? currently in testing and not yet in production here, so we don?t have a lot of experience yet, but I think it may be useful to have level-of-description included in those requests (another instance where you are seeing the info removed from it?s context) and we are considering filtering request so that only the lowest level items are units that can be requested ( although this can be perhaps better implemented just by looking at whether the item has children. ) ? Steve. > On Mar 8, 2019, at 2:29 PM, Jordon Steele wrote: > > Hi all, > > This is more of an archival description question, but I?m not a member of that listserv, so I figured it would be easier to ping some of you about this for advice since I wager there?s a lot of overlap. > > We have not-infrequent discussions around here about what ?level of description? label to assign to an archival component at a given level, i.e. collection, series, file, item, etc. But because our data is already structured in hierarchical relationships via EAD/JSON, there?s no real need to ?tell the computer? what level this is since these labels aren?t the way computers understand context and hierarchy, the nesting of data is. > > Once I realized this, I often made the case that these level-of-description labels are useful for stylesheets, i.e. tell a stylesheet with level=series to make it all caps and bold, level=file should be red, etc. But the ASpace PUI doesn?t/doesn?t need to style levels in this manner for the hierarchy to be easily understood. > > So we?re considering discontinuing use of the ?level of description? field in ASpace. But am I missing an important value of this field? Thanks! > > Best, > > Jordon > > Jordon Steele > Hodson Curator of the University Archives > Sheridan Libraries > Johns Hopkins University > 3400 N Charles St > Baltimore, MD 21218 > jsteele at jhu.edu > 410-516-5493 > he/him/his > > _______________________________________________ > 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: 3598 bytes Desc: not available URL: From cory_nimer at byu.edu Sun Mar 10 12:49:15 2019 From: cory_nimer at byu.edu (Cory Nimer) Date: Sun, 10 Mar 2019 16:49:15 +0000 Subject: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? In-Reply-To: References: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu>, Message-ID: <1552236554678.42561@byu.edu> Jordon, Another case similar to Steve's Aeon example is that the level value can be used in establishing inheritance rules for element display. If you are using the PUI, you can limit the inheritance of specific elements to prevent them from being included in archival object displays based on their level of description value. An example of this is provided at the end of the record inheritance section of the configuration documentation (http://archivesspace.github.io/archivesspace/user/configuring-archivesspace/?). Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Friday, March 8, 2019 12:51 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? In EAD, the hierarchy is fixed, but one of the advantages of linked data is that the elements are movable and reusable in other contexts. We're not really taking advantage of that currently in ArchivesSpace, but for the future I think it makes sense to think about those use cases and whether level-of-description might be useful if the archival object is removed from its context. ( For example, organizing artificial or virtual collections from subsets or multiple archival collections for exhibits or other display purposes - whether that's done in ArchivesSpace or by another tool importing info from ArchivesSpace. ) I will also note that we are currently integrating Aeon with ArchivesSpace - currently in testing and not yet in production here, so we don't have a lot of experience yet, but I think it may be useful to have level-of-description included in those requests (another instance where you are seeing the info removed from it's context) and we are considering filtering request so that only the lowest level items are units that can be requested ( although this can be perhaps better implemented just by looking at whether the item has children. ) - Steve. On Mar 8, 2019, at 2:29 PM, Jordon Steele > wrote: Hi all, This is more of an archival description question, but I'm not a member of that listserv, so I figured it would be easier to ping some of you about this for advice since I wager there's a lot of overlap. We have not-infrequent discussions around here about what "level of description" label to assign to an archival component at a given level, i.e. collection, series, file, item, etc. But because our data is already structured in hierarchical relationships via EAD/JSON, there's no real need to "tell the computer" what level this is since these labels aren't the way computers understand context and hierarchy, the nesting of data is. Once I realized this, I often made the case that these level-of-description labels are useful for stylesheets, i.e. tell a stylesheet with level=series to make it all caps and bold, level=file should be red, etc. But the ASpace PUI doesn't/doesn't need to style levels in this manner for the hierarchy to be easily understood. So we're considering discontinuing use of the "level of description" field in ASpace. But am I missing an important value of this field? Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu 410-516-5493 he/him/his _______________________________________________ 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 ndroark at anderson.edu Mon Mar 11 13:57:32 2019 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Mon, 11 Mar 2019 13:57:32 -0400 Subject: [Archivesspace_Users_Group] Calculate Dates functionality Message-ID: Hi all, Recently we have started using the Calculate Dates function. We sometimes run into situations where every subsidiarity element of a resource has dates, but Aspace will not calculate dates from that range. When the button is pressed nothing happens. Has anyone experienced this or seen documentation explaining the nuts and bolts of the Calculate functions? *Nicholas Stanton-Roark* | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 <%28765%29%20641%204285> | ndroark at anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Mar 11 14:03:25 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 11 Mar 2019 18:03:25 +0000 Subject: [Archivesspace_Users_Group] Calculate Dates functionality In-Reply-To: References: Message-ID: I saw that once, turned out to be an extra space in the date of a record. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Nic Stanton-Roark Sent: Monday, March 11, 2019 1:57 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Calculate Dates functionality Hi all, Recently we have started using the Calculate Dates function. We sometimes run into situations where every subsidiarity element of a resource has dates, but Aspace will not calculate dates from that range. When the button is pressed nothing happens. Has anyone experienced this or seen documentation explaining the nuts and bolts of the Calculate functions? [https://anderson.edu/uploads/au-email-logo.gif] Nicholas Stanton-Roark | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 | ndroark at anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmichelson at smith.edu Mon Mar 11 14:05:50 2019 From: dmichelson at smith.edu (Daniel Michelson) Date: Mon, 11 Mar 2019 14:05:50 -0400 Subject: [Archivesspace_Users_Group] Calculate Dates functionality In-Reply-To: References: Message-ID: Hi Nic, Have you checked that the dates have matching labels? When calculating the creation date, dates with other labels are not included. Sometimes creation dates are incorrectly imported (or incorrectly encoded) with the label "Other." Dan On Mon, Mar 11, 2019 at 1:58 PM Nic Stanton-Roark wrote: > Hi all, > > Recently we have started using the Calculate Dates function. We sometimes > run into situations where every subsidiarity element of a resource has > dates, but Aspace will not calculate dates from that range. When the button > is pressed nothing happens. > > Has anyone experienced this or seen documentation explaining the nuts and > bolts of the Calculate functions? > > > *Nicholas Stanton-Roark* | Archivist | Robert A. Nicholson University > Library > Anderson University | 1100 E. Fifth St, Anderson, IN 46012 > (765) 641-4285 <%28765%29%20641%204285> | ndroark at anderson.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Dan Michelson Project Manager Archivist Smith College Special Collections -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Mar 11 15:28:51 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 11 Mar 2019 19:28:51 +0000 Subject: [Archivesspace_Users_Group] reminder: register for the ArchivesSpace Online Forum, happening March 18 beginning at 5 p.m. UTC Message-ID: Our Online Forum is almost here! We have nearly 300 people registered, no doubt guaranteeing that this will be our largest ArchivesSpace event to date. You can learn more about the program at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ArchivesSpace+Online+Forum+2019. If you're planning to attend any portion of the Forum live, please register at https://www.eventbrite.com/e/archivesspace-online-forum-2019-registration-57088627622 as soon as you can. We'll be sending additional information, including the connection links, to registrants later this week. Thanks to all who will be attending live. For those who can't, we will be recording as much of the Forum as we can. Links to presentations, recordings, and notes will be added to the event page when they are available after the Forum. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From jsteele at jhu.edu Wed Mar 13 09:56:04 2019 From: jsteele at jhu.edu (Jordon Steele) Date: Wed, 13 Mar 2019 13:56:04 +0000 Subject: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? In-Reply-To: <1552236554678.42561@byu.edu> References: <9bda2bf03b0647879fd79ada8f8dc588@ESGMTWEX10.win.ad.jhu.edu>, <1552236554678.42561@byu.edu> Message-ID: <73be8d4decee4a2d9635bbdfb06f3f8e@ESGEBEX10.win.ad.jhu.edu> Thanks for everyone?s feedback. Sounds like it was a good idea to post this question to ASpace listserv, because I?m noticing that there are important style and formatting dependencies in the PUI that require levels of description labels. Based on this reality, we?ll let sleeping dogs lie for now and keep using these labels. Thanks, all! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu 410-516-5493 he/him/his From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Cory Nimer Sent: Sunday, March 10, 2019 12:49 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? Jordon, Another case similar to Steve's Aeon example is that the level value can be used in establishing inheritance rules for element display. If you are using the PUI, you can limit the inheritance of specific elements to prevent them from being included in archival object displays based on their level of description value. An example of this is provided at the end of the record inheritance section of the configuration documentation (http://archivesspace.github.io/archivesspace/user/configuring-archivesspace/?). Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, March 8, 2019 12:51 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Discontinuing use of "levels of description" labels? In EAD, the hierarchy is fixed, but one of the advantages of linked data is that the elements are movable and reusable in other contexts. We?re not really taking advantage of that currently in ArchivesSpace, but for the future I think it makes sense to think about those use cases and whether level-of-description might be useful if the archival object is removed from its context. ( For example, organizing artificial or virtual collections from subsets or multiple archival collections for exhibits or other display purposes ? whether that?s done in ArchivesSpace or by another tool importing info from ArchivesSpace. ) I will also note that we are currently integrating Aeon with ArchivesSpace ? currently in testing and not yet in production here, so we don?t have a lot of experience yet, but I think it may be useful to have level-of-description included in those requests (another instance where you are seeing the info removed from it?s context) and we are considering filtering request so that only the lowest level items are units that can be requested ( although this can be perhaps better implemented just by looking at whether the item has children. ) ? Steve. On Mar 8, 2019, at 2:29 PM, Jordon Steele > wrote: Hi all, This is more of an archival description question, but I?m not a member of that listserv, so I figured it would be easier to ping some of you about this for advice since I wager there?s a lot of overlap. We have not-infrequent discussions around here about what ?level of description? label to assign to an archival component at a given level, i.e. collection, series, file, item, etc. But because our data is already structured in hierarchical relationships via EAD/JSON, there?s no real need to ?tell the computer? what level this is since these labels aren?t the way computers understand context and hierarchy, the nesting of data is. Once I realized this, I often made the case that these level-of-description labels are useful for stylesheets, i.e. tell a stylesheet with level=series to make it all caps and bold, level=file should be red, etc. But the ASpace PUI doesn?t/doesn?t need to style levels in this manner for the hierarchy to be easily understood. So we?re considering discontinuing use of the ?level of description? field in ASpace. But am I missing an important value of this field? Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu 410-516-5493 he/him/his _______________________________________________ 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 ahueb2 at uis.edu Wed Mar 13 09:58:45 2019 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Wed, 13 Mar 2019 13:58:45 +0000 Subject: [Archivesspace_Users_Group] Possible issue with daylight savings time Message-ID: Good morning, I'm not entirely sure, but it appears that our ArchivesSpace instance has stopped working due to the recent DST change. I'm still getting the same error after updating all packages on the system as well. "NoMethodError: undefined method `getSQLState' for java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException Did you mean? getClass" Has anyone encountered this error before? How did you fix it? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Mar 13 16:21:40 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 13 Mar 2019 20:21:40 +0000 Subject: [Archivesspace_Users_Group] Possible issue with daylight savings time In-Reply-To: References: Message-ID: Hi Alan, (Since it sounds like a few people may be helped by this answer, I'm answering here instead of on the message you sent to ArchivesSpaceHome at lyrasis.org. If the explanation below doesn't resolve your issue, I'll put that tech support ticket through for you. Several users have reported this problem to us in various ways. This error isn't unique to ArchivesSpace, but ArchivesSpace can be affected by it if you have timestamps in the hour that never happened (between 2 and 3am) in the search_indexer row in the user table. We're not sure how this would happen, but maybe if your server got restarted around that time? If you get rid of those errant times that problem should go away. We have also heard of people having an issue with their MySQL connector when they upgrade. You'll want to be sure the MySQL connector you are using is for 7 and not 8. It doesn't sounds like that's your issue, but one more thing to check just in case. 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 Huebschen, Alan M Sent: Wednesday, March 13, 2019 9:59 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Possible issue with daylight savings time Good morning, I'm not entirely sure, but it appears that our ArchivesSpace instance has stopped working due to the recent DST change. I'm still getting the same error after updating all packages on the system as well. "NoMethodError: undefined method `getSQLState' for java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException Did you mean? getClass" Has anyone encountered this error before? How did you fix it? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -------------- 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 ahueb2 at uis.edu Thu Mar 14 09:23:44 2019 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Thu, 14 Mar 2019 13:23:44 +0000 Subject: [Archivesspace_Users_Group] Possible issue with daylight savings time In-Reply-To: References: Message-ID: <3833840e6d4544e498daf3a7c51d3ea4@UISMBX03.uisad.uis.edu> Christine, Changing the time entries for search_indexer appears to have fixed the issue. Thank you for the help! -Alan Huebschen Brookens Library Information Systems (217) 206-7115 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: Wednesday, March 13, 2019 3:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Possible issue with daylight savings time Hi Alan, (Since it sounds like a few people may be helped by this answer, I'm answering here instead of on the message you sent to ArchivesSpaceHome at lyrasis.org. If the explanation below doesn't resolve your issue, I'll put that tech support ticket through for you. Several users have reported this problem to us in various ways. This error isn't unique to ArchivesSpace, but ArchivesSpace can be affected by it if you have timestamps in the hour that never happened (between 2 and 3am) in the search_indexer row in the user table. We're not sure how this would happen, but maybe if your server got restarted around that time? If you get rid of those errant times that problem should go away. We have also heard of people having an issue with their MySQL connector when they upgrade. You'll want to be sure the MySQL connector you are using is for 7 and not 8. It doesn't sounds like that's your issue, but one more thing to check just in case. 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 Huebschen, Alan M Sent: Wednesday, March 13, 2019 9:59 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Possible issue with daylight savings time Good morning, I'm not entirely sure, but it appears that our ArchivesSpace instance has stopped working due to the recent DST change. I'm still getting the same error after updating all packages on the system as well. "NoMethodError: undefined method `getSQLState' for java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException Did you mean? getClass" Has anyone encountered this error before? How did you fix it? -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4014 bytes Desc: image001.jpg URL: From gordon_daines at byu.edu Mon Mar 18 10:28:51 2019 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 18 Mar 2019 14:28:51 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: <3603a148517743288b738113bab9c299@MB7.byu.local> Colleagues, This is a gentle reminder that we are seeking nominations for the Technical Advisory Council (TAC). We are in need of at least three (3) individuals willing to contribute their talents to this important group. If you have any questions about the TAC, please contact me at gordon_daines at byu.edu. We will be accepting nominations and self-nominations through April 19th, 2019. Gordon Daines Chair, ArchivesSpace Nominating Committee From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, January 24, 2019 8:36 AM To: archivesspace_users_group at lyralists.lyrasis.org; Archivesspace Member Reps Subject: [Archivesspace_member_reps] Nominations Requested for ArchivesSpace Technical Advisory Council Colleagues, The ArchivesSpace Governance Board is seeking nominations to fill three (3) vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution in any membership level (the vacancies being filled are from the very large and very small levels). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 19, 2019. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://www.archivesspace.org/technicaladvisory) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service for these appointments will be July 1, 2019-June 30, 2021. We expect making up to three (3) appointments, and each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2021-June 30, 2023. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine DiBella at christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 19, 2019. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Gordon Daines Brigham Young University Chair, Nominating Committee On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair, and Governance Board member Ashley Knox, University of North Carolina Wilmington,Chair of User Advisory Council Max Eckard, University of Michigan, Chair of Technical Advisory Council Caitlin Wells, University of Michigan, representing very large membership level Jay Trask, University of Northern Colorado, representing large membership level Carolyn Runyon, University of Tennessee Chattanooga, representing medium membership level Suzanne Stasiulitis, Pennsylvania State Archives, representing small membership level Jonathan Lawler, Southeastern Baptist Theological Seminary, representing very small membership level Christine DiBella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Bug fixes ___Technical documentation ___Program architecture and integrations with other software ___Migration issues, including import/exports and API design and implementation ___Application testing _________________________ J. Gordon Daines III Supervisor of Reference Services Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From gordon_daines at byu.edu Mon Mar 18 10:30:54 2019 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 18 Mar 2019 14:30:54 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council Message-ID: <39ae1d43f61c4612a5f0d1434eac5aca@MB7.byu.local> Colleagues, We are seeking nominations and self-nominations for the User Advisory Council. We have three (3) vacancies that we are seeking to fill. The deadline to be considered for membership on this important group is April 19th, 2019. Gordon Daines Chair, ArchivesSpace Nominating Committee From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, January 24, 2019 8:40 AM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' ; Archivesspace Member Reps Subject: [Archivesspace_member_reps] Nominations Requested for ArchivesSpace User Advisory Council Colleagues, The ArchivesSpace Governance Board is seeking nominations to fill three (3) vacancies on the ArchivesSpace User Advisory Council (UAC). Nominees should be presently employed at an ArchivesSpace member institution in any membership category (the vacancies being filled were represented by the very large and medium levels) (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities projected for UAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 19th, 2019. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. UAC (http://www.archivesspace.org/usersadvisory) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. It is also the group that implements and contributes to ArchivesSpace user services. Some of the activities UAC is currently engaged in are: * liaising with national and regional archives organizations; * soliciting, suggesting, gathering requirements for, and prioritizing enhancements to the ArchivesSpace application; * maintaining and updating user documentation, as needed, of the ArchivesSpace application; * developing and providing training to users; and * advising the Governance Board and LYRASIS on the design and delivery of user services, including but not limited to help desk support, training, and presentation of documentation. Sub-groups will be established within UAC to address the areas identified above, as well as other activities identified subsequently. Nominees will be appointed to UAC according to their ability to participate in and lead some of the activities mentioned above. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2019-June 30, 2021. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2021-June 30, 2023. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine DiBella at christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 19th, 2019. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Gordon Daines Brigham Young University Chair, Nominating Committee On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair, and Governance Board member Ashley Knox, University of North Carolina Wilmington,Chair of User Advisory Council Max Eckard, University of Michigan, Chair of Technical Advisory Council Caitlin Wells, University of Michigan, representing very large membership level Jay Trask, University of Northern Colorado, representing large membership level Carolyn Runyon, University of Tennessee Chattanooga, representing medium membership level Suzanne Stasiulitis, Pennsylvania State Archives, representing small membership level Jonathan Lawler, Southeastern Baptist Theological Seminary, representing very small membership level Christine DiBella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Documentation ___Liaising with archives organizations. Please indicate the organizations: _____________________ ___New features, functional or technical specifications ___Training, design ___Training, provision ___ Usability testing ___User/Help support _________________________ J. Gordon Daines III Supervisor of Reference Services Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From reesj at mail.nlm.nih.gov Fri Mar 15 15:56:38 2019 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Fri, 15 Mar 2019 19:56:38 +0000 Subject: [Archivesspace_Users_Group] Linking subjects to digital objects via the API Message-ID: We're trying to post-process digital objects and link existing subjects to them via the API, however there doesn't seem to be a call to do this. Are we missing something? It seems doable for linked_agents and linked_events. Or is the preferred approach to insert subjects? https://archivesspace.github.io/archivesspace/api/#update-a-digital-object Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Tue Mar 19 09:53:27 2019 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Tue, 19 Mar 2019 13:53:27 +0000 Subject: [Archivesspace_Users_Group] Container and Location management reports Message-ID: Dear Colleagues, I'm wondering if anyone at a repository that currently uses containers, container profiles, locations, and/or location profiles might offer me some advice regarding reporting. What kinds of data do you find yourself needing most regularly? How are you getting that data? Customized reporting, out of the box reports, database queries, API, others? Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Tue Mar 19 11:32:52 2019 From: livsolis at utexas.edu (Olivia S Solis) Date: Tue, 19 Mar 2019 10:32:52 -0500 Subject: [Archivesspace_Users_Group] Linking subjects to digital objects via the API In-Reply-To: References: Message-ID: Hi John, I am not sure if there is a way to do this directly through the API, but my team has come up with a way to do this through a Python script. We actually modified a script written by Duke (thank you Noah Huffman if you are out there!) to update major record types in ASpace. I use OpenRefine to structure the data/JSON then export via its Custom Tabular Export feature. I've tried to document my process in these two docs: Using the scripts: https://docs.google.com/document/d/12b9YN-_XFaFyEQivMm3g_9gMJ5tkm3JJMSg1fyLYUgA/edit?usp=sharing Using the templates: https://docs.google.com/document/d/1ulryK7V-_j-jQhIE_Dg3KqfCNexuUu8KHENLLz6njjs/edit?usp=sharing The "update" scripts/templates post a completely new array/set of, in your case e.g., linked subjects. The "append" ones tack on a subject to an existing array of subjects. I have actually only posted the update subject links (not append), and only to resource records, but it should work if you change the resource endpoint to a digital object endpoint (I would think... we don't use ASpace for digital objects). But there is no reason why adapted an append subject script wouldn't work. You will just need to know the digital object ASpace IDs and the subject IDs you want to use. Hopefully, my documentation is clearish, but it is drafty and not quite ready for prime time! I think it can be adapted for different uses. Thanks, Olivia On Mon, Mar 18, 2019 at 11:20 AM Rees, John (NIH/NLM) [E] < reesj at mail.nlm.nih.gov> wrote: > We?re trying to post-process digital objects and link existing subjects to > them via the API, however there doesn?t seem to be a call to do this. > > > > Are we missing something? It seems doable for linked_agents and > linked_events. > > > > Or is the preferred approach to insert subjects? > > > > https://archivesspace.github.io/archivesspace/api/#update-a-digital-object > > > > Thanks, > > John > > > > John P. Rees > > Archivist and Digital Resources Manager > > History of Medicine Division > > National Library of Medicine > > 301-827-4510 > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alicia.detelich at yale.edu Tue Mar 19 12:03:10 2019 From: alicia.detelich at yale.edu (Detelich, Alicia) Date: Tue, 19 Mar 2019 16:03:10 +0000 Subject: [Archivesspace_Users_Group] Container and Location management reports In-Reply-To: References: Message-ID: <7074D2C0-E1E9-4A13-ACE4-765D71898AD4@yale.edu> Hi Adrien, We use top containers, container profiles, and locations. Our reporting needs vary, but often they are related to answering questions like: ?What boxes/materials are in this location?? ?How much space do those boxes occupy?? ?What?s in the box(es)?? ?How many VHS boxes do we have?? ?How many linear feet is collection X?? ?Here?s a list of barcodes that should be in X location, are they actually there?? ?How many boxes are in ArchivesSpace that aren?t associated with a descriptive record?? To answer these questions, and others, we?ve typically used database queries. The API is not usually the most efficient way to retrieve ArchivesSpace data, though we have used the search endpoints for some reporting functions. For instance, this tool - https://github.com/ucancallmealicia/barcode_search - will take a list of barcodes, which are stored in top container records, and retrieve data about the containers and their associated descriptive records. This helps us to manage transfers of material to off-site storage. For the most part, though, SQL queries are the way to go. You?ll find a bunch of examples in these repos: https://github.com/ucancallmealicia/mysql_demo https://github.com/ucancallmealicia/archivesspace-sql https://github.com/YaleArchivesSpace/yams_data_auditing We haven?t used the out-of-the box reporting functionality, but we are considering it now that the module has been updated to allow users to add custom reports using raw SQL. Doing so would allow non-technical users to run these reports without having to ask technical staff for assistance. It has worked well during testing, though I think we as an institution will need to determine some criteria re: which reports we want to add before we start using it, since the reports are shared across repositories. Hope this helps, Alicia Alicia Detelich Archivist Manuscripts and Archives Yale University Libraries From: on behalf of "Hilton, Adrien" Reply-To: Archivesspace Users Group Date: Tuesday, March 19, 2019 at 9:53 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Container and Location management reports Dear Colleagues, I?m wondering if anyone at a repository that currently uses containers, container profiles, locations, and/or location profiles might offer me some advice regarding reporting. What kinds of data do you find yourself needing most regularly? How are you getting that data? Customized reporting, out of the box reports, database queries, API, others? Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Thu Mar 21 15:42:27 2019 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 21 Mar 2019 19:42:27 +0000 Subject: [Archivesspace_Users_Group] Container and Location management reports In-Reply-To: <7074D2C0-E1E9-4A13-ACE4-765D71898AD4@yale.edu> References: <7074D2C0-E1E9-4A13-ACE4-765D71898AD4@yale.edu> Message-ID: Thanks Alicia, this information is much appreciated as is all the work you?ve done writing those SQL queries that are on Github. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Detelich, Alicia Sent: Tuesday, March 19, 2019 12:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Container and Location management reports Hi Adrien, We use top containers, container profiles, and locations. Our reporting needs vary, but often they are related to answering questions like: ?What boxes/materials are in this location?? ?How much space do those boxes occupy?? ?What?s in the box(es)?? ?How many VHS boxes do we have?? ?How many linear feet is collection X?? ?Here?s a list of barcodes that should be in X location, are they actually there?? ?How many boxes are in ArchivesSpace that aren?t associated with a descriptive record?? To answer these questions, and others, we?ve typically used database queries. The API is not usually the most efficient way to retrieve ArchivesSpace data, though we have used the search endpoints for some reporting functions. For instance, this tool - https://github.com/ucancallmealicia/barcode_search - will take a list of barcodes, which are stored in top container records, and retrieve data about the containers and their associated descriptive records. This helps us to manage transfers of material to off-site storage. For the most part, though, SQL queries are the way to go. You?ll find a bunch of examples in these repos: https://github.com/ucancallmealicia/mysql_demo https://github.com/ucancallmealicia/archivesspace-sql https://github.com/YaleArchivesSpace/yams_data_auditing We haven?t used the out-of-the box reporting functionality, but we are considering it now that the module has been updated to allow users to add custom reports using raw SQL. Doing so would allow non-technical users to run these reports without having to ask technical staff for assistance. It has worked well during testing, though I think we as an institution will need to determine some criteria re: which reports we want to add before we start using it, since the reports are shared across repositories. Hope this helps, Alicia Alicia Detelich Archivist Manuscripts and Archives Yale University Libraries From: > on behalf of "Hilton, Adrien" > Reply-To: Archivesspace Users Group > Date: Tuesday, March 19, 2019 at 9:53 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Container and Location management reports Dear Colleagues, I?m wondering if anyone at a repository that currently uses containers, container profiles, locations, and/or location profiles might offer me some advice regarding reporting. What kinds of data do you find yourself needing most regularly? How are you getting that data? Customized reporting, out of the box reports, database queries, API, others? Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhughes at huntington.org Thu Mar 21 16:58:18 2019 From: mhughes at huntington.org (Hughes, Maggie) Date: Thu, 21 Mar 2019 20:58:18 +0000 Subject: [Archivesspace_Users_Group] Problems with reordering archival objects? Message-ID: Hi everyone, I'm reaching out on behalf of the Dev Pri sub-team and ASpace developers regarding murky issues when trying to reorder archival objects. So far we know this is a problem, but it's been very difficult to replicate and understand the conditions under which it occurs. This slipperiness makes it difficult to know how to fix it. If you experience archival objects that fail to move to desired locations when using "Enable Reorder Mode" (drag/drop, move pulldown, and copy/paste) and can provide details about how you're seeing it in your specific environments, please take a look at the ticket and leave the details in the comments. The developers are looking for points of commonality in descriptions of the issue such as whether your database/record was migrated, qualities of the archival object (was it created as a child or sibling?), and anything you notice about when it tends to happen. Here's the link to the ticket ANW-736: https://archivesspace.atlassian.net/browse/ANW-736 Thanks for your help! -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Wed Mar 27 16:08:36 2019 From: mang.sun at rice.edu (Mang Sun) Date: Wed, 27 Mar 2019 15:08:36 -0500 Subject: [Archivesspace_Users_Group] Configuring Levels to Return in ArchivesSpace OAI-PMH In-Reply-To: References: Message-ID: <8cc5145a-0538-ddab-06e9-f0aeeeea583d@rice.edu> We are still on v2.2.1 and? trying to load resource or collection level (recordgrp) records into our Primo sandbox, but we only see six? harvested and imported.Run OAI request by hand,we do see "==" in the resumptionToken after six records have been harvested. Does this "==" cause premature end of harvesting? We have more than 1000 records at collection level. Thank you. Mang Sun Rice U. On 10/22/2018 7:51 AM, Christine Di Bella wrote: > > Thanks for this, Terry. We track development requests in JIRA: > http://development.archivesspace.org. I?d encourage you to file the > feature request there for future consideration. > > Christine > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > *On Behalf > Of *Terry Brady > *Sent:* Friday, October 19, 2018 6:31 PM > *To:* Archivesspace Users Group > > *Subject:* Re: [Archivesspace_Users_Group] Configuring Levels to > Return in ArchivesSpace OAI-PMH > > It seems like a resumptionToken ending in "==" signals that the set is > complete. > > I would like to file an enhancement request. > > When the OAI delivery of a set is complete, one of the following > should happen: (1)no resumption token is returned or (2)any subsequent > request using the final resumption token should return no results. > > Where is the best place to file this request? > > On Fri, Oct 19, 2018 at 3:17 PM Terry Brady > > wrote: > > Christine, > > Thank you for the clarification.? I was looking in the > configuration and did not think to check the admin interface.? > This is much closer to what I hoped to see. > > My results have improved since I implemented this change. > > I have one set with a very small number of objects.? Once the > initial set of 3 items is returned, a resumption token is provided > even though the list is complete.? When I used that resumption > token, I seem to pull an inconsistent set of results. > > Should a resumption token be present when a complete set has been > delivered? > > On Fri, Oct 19, 2018 at 1:10 PM Christine Di Bella > > wrote: > > Hi Terry, > > Are you limiting your set to just the level of description > Collection (or Fonds, if that?s highest level of description > at your repository)? That would probably be the easiest way to > limit to just resources. It?s possible to do this in the > config file (prior to v.2.5.0) or (as of v2.5.0) on the > repository record within the staff interface. > > Christine > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > > 800.999.8558 x2905 > > 678-235-2905 > > cdibella13 (Skype) > > *From:* > archivesspace_users_group-bounces at lyralists.lyrasis.org > > > > *On Behalf Of *Terry Brady > *Sent:* Thursday, October 18, 2018 6:30 PM > *To:* Archivesspace Users Group > > > *Subject:* [Archivesspace_Users_Group] Configuring Levels to > Return in ArchivesSpace OAI-PMH > > I am testing the OAI-PMH service in ArchivesSpace, and I would > like to reduce the level of detail being returned. > > Is there a configuration setting that would allow me to reduce > the records returned to just Collection/Resource objects? > > I see where I can configure repository sets, but I was unclear > how to configure the granularity of results. > > 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) > > > -- > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Wed Mar 27 17:30:06 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 27 Mar 2019 21:30:06 +0000 Subject: [Archivesspace_Users_Group] Container and Location management reports In-Reply-To: References: Message-ID: Hi Adrien, We have a report for this: https://github.com/duspeccoll/archivesspace_reports/blob/master/top_container_list_report.rb At Denver we do this to do side-by-side comparisons of Top Containers and their corresponding Alma items to make sure the information is the same in each system, so we limit the ArchivesSpace report to the fields whose metadata end up in Alma. Our Alma integrations plugin also does some side-by-side comparisons of metadata if you search for items within a collection, though that data is inaccessible outside of the plugin interface: [cid:image001.png at 01D4E4B1.F4024200] Let me know if you have any other questions about how we do this! -k From: on behalf of "Hilton, Adrien" Reply-To: Archivesspace Group Date: Tuesday, March 19, 2019 at 7:53 AM To: Archivesspace Group Subject: [Archivesspace_Users_Group] Container and Location management reports Dear Colleagues, I?m wondering if anyone at a repository that currently uses containers, container profiles, locations, and/or location profiles might offer me some advice regarding reporting. What kinds of data do you find yourself needing most regularly? How are you getting that data? Customized reporting, out of the box reports, database queries, API, others? Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 366172 bytes Desc: image001.png URL: From sdm7g at virginia.edu Thu Mar 28 17:38:00 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 28 Mar 2019 21:38:00 +0000 Subject: [Archivesspace_Users_Group] Configuring Levels to Return in ArchivesSpace OAI-PMH In-Reply-To: References: Message-ID: <4D5ADA7C-4166-43D2-9C36-AA104A48B044@virginia.edu> I?m not seeing this resumptionToken bug on my 2.5.2 . What version are you using? What request params ? To avoid cycling thru *everything*, I tested starting with: https://archives-oai.lib.virginia.edu/oai?verb=ListRecords&set=uva-sc&metadataPrefix=oai_dc&from=2019-03-26 And then used the resumptionToken from that result in the next request. Results of that 2nd and final request did not include another resumptionToken. ? Steve M. > On Oct 19, 2018, at 6:30 PM, Terry Brady wrote: > > It seems like a resumptionToken ending in "==" signals that the set is complete. > > I would like to file an enhancement request. > > When the OAI delivery of a set is complete, one of the following should happen: (1)no resumption token is returned or (2)any subsequent request using the final resumption token should return no results. > > Where is the best place to file this request? > > On Fri, Oct 19, 2018 at 3:17 PM Terry Brady > wrote: > Christine, > > Thank you for the clarification. I was looking in the configuration and did not think to check the admin interface. This is much closer to what I hoped to see. > > My results have improved since I implemented this change. > > I have one set with a very small number of objects. Once the initial set of 3 items is returned, a resumption token is provided even though the list is complete. When I used that resumption token, I seem to pull an inconsistent set of results. > > Should a resumption token be present when a complete set has been delivered? > > > On Fri, Oct 19, 2018 at 1:10 PM Christine Di Bella > wrote: > Hi Terry, > > > > Are you limiting your set to just the level of description Collection (or Fonds, if that?s highest level of description at your repository)? That would probably be the easiest way to limit to just resources. It?s possible to do this in the config file (prior to v.2.5.0) or (as of v2.5.0) on the repository record within the staff interface. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > 800.999.8558 x2905 > > 678-235-2905 > > cdibella13 (Skype) > > > > > > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Terry Brady > Sent: Thursday, October 18, 2018 6:30 PM > To: Archivesspace Users Group > > Subject: [Archivesspace_Users_Group] Configuring Levels to Return in ArchivesSpace OAI-PMH > > > > I am testing the OAI-PMH service in ArchivesSpace, and I would like to reduce the level of detail being returned. > > > > Is there a configuration setting that would allow me to reduce the records returned to just Collection/Resource objects? > > > > I see where I can configure repository sets, but I was unclear how to configure the granularity of results. > > > > 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) > > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From buschedw at msu.edu Fri Mar 29 13:37:23 2019 From: buschedw at msu.edu (Busch, Ed) Date: Fri, 29 Mar 2019 17:37:23 +0000 Subject: [Archivesspace_Users_Group] Error when creating PDF Finding Aid Export Message-ID: We are doing Print Resource to PDF for a Resource that fails during the background job execution. The errors that appear are below. Any suggestions on pinpointing what is causing the problem? I'm wondering if it's this component line Betty MacDowell Resource Files for Publication: Michigan Women: First & Founders as it's the first use of & that isn't &. Grasping at straws. Thanks! Ed Generating PDF for Michigan Women's Studies Association records org.xml.sax.SAXParseException; lineNumber: 84; columnNumber: 49129; The entity name must immediately follow the '&' in the entity reference. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:45) usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther45:run(usr/local/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-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) Ed Busch, MLIS Acting Director 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Mar 29 13:38:59 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 29 Mar 2019 17:38:59 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - March 2019 Message-ID: [ASpaceOrgHome.jpg] March 2019 Update Development We continue to work on our next release, which, pending further development and testing, we are aiming to put out in April. Thanks to all who have helped with testing or pull requests so far. 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. Open Call on Reports - April 3 Please join us at 1:00 p.m. Eastern time on Wednesday, April 3, for an ArchivesSpace open call discussion focused on reports. The User Advisory Council Reports sub-team is interested in learning about the community's use of the existing reports, use cases, and pain points. The sub-team will use this feedback to inform their next steps. Some questions and discussion items are posted on the wiki page for the call. Feel free to add more by using the comments section on the page. https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call. Connection information: https://zoom.us/j/926134522 Dial by your location (if you cannot connect to the audio with your computer) +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) Meeting ID: 926 134 522 Find your local number: https://zoom.us/u/abY0PUiwRs Follow Up from ArchivesSpace Online Forum - March 18 Thank you to all who attended our first Online Forum on March 18. We were so thrilled with the variety of speakers, topics, and attendees, and the possibilities for the future. Links to presentations, notes, and other materials are at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ASpace+Online+Forum+2019. We are still editing the recordings, but hope to make them available soon. Given the wonderful response, we expect to hold similar events in the future, but we want to hear from you what you liked, what would have made it better, and your ideas for future topics, speakers, and formats. Please fill out an evaluation to give us your feedback: https://www.surveymonkey.com/r/7VXYKQK. Nominations Being Accepted for Our Advisory Councils Through April 19 Community governance is vital to ArchivesSpace, and the community members that serve on our governance groups provide essential leadership and coordination for a wide range of activities. More information about these groups is available at https://archivesspace.org/governance-board-and-councils. The Nominating Committee is accepting nominations for several openings on our User Advisory Council and Technical Advisory Council through April 19. The User Advisory Council is open to those from ArchivesSpace member institutions only. The Technical Advisory Council is open to non-members as well. We especially encourage those from small institutions and non-academic institutions to apply. If you have questions about or are interested in nominating yourself or someone else for a two-year term on one of the Councils, please contact Christine Di Bella (christine.dibella at lyrasis.org). Connect with ArchivesSpace in Person Christine will be at the Midwest Archives Conference (MAC) annual meeting in Detroit from April 4-5. Come find her in the exhibit hall to talk about the ArchivesSpace application, our community activities, membership, and more. Our organizational home, LYRASIS, will also have a table at MAC, and Tom Clareson (Senior Digital and Preservation Services Consultant ) and Katy Klettinger (Outreach Representative, Mid-Atlantic & Great Lakes ) will be on hand to advise on the many services LYRASIS offers, including ArchivesSpace hosting. You can also catch up with Katy at the LYRASIS happy hour at Ready Player One, 407 E. Fort St., on Friday April 5 from 5-7 p.m. Hannah Rosen (Licensing Specialist and Digitization Program Coordinator) will host a LYRASIS happy hour at the Mid-Atlantic Regional Archives Conference (MARAC) spring meeting in Morgantown, West Virginia, on Thursday, April 11, from 6-7:30 p.m., at Table 9, 40 Donley St. You can also meet up with Hannah at the LYRASIS table in the exhibit hall on Friday, April 12. Membership Update We are excited to welcome our newest members to our community! Our new members since February 28 include: * Medical University of South Carolina * Mike Kelley Foundation for the Arts * Pratt Institute Libraries As of March 29, we have 380 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: image002.jpg Type: image/jpeg Size: 20006 bytes Desc: image002.jpg URL: From seth.shaw at unlv.edu Fri Mar 29 13:42:20 2019 From: seth.shaw at unlv.edu (Seth Shaw) Date: Fri, 29 Mar 2019 10:42:20 -0700 Subject: [Archivesspace_Users_Group] Error when creating PDF Finding Aid Export In-Reply-To: References: Message-ID: Your guess that "Michigan Women: First & Founders" is causing the failure is probably correct. ArchivesSpace won't encode those ampersands for you. We explicitly train our staff to replace ampersands with `&` but we still occasionally see these errors pop up when someone copy/pastes text and misses one (mostly in citation URLs in notes). Just search for the offending phrase and update the corresponding value. On Fri, Mar 29, 2019 at 10:37 AM Busch, Ed wrote: > We are doing Print Resource to PDF for a Resource that fails during the > background job execution. The errors that appear are below. > > Any suggestions on pinpointing what is causing the problem? I?m wondering > if it?s this component line > > Betty MacDowell Resource Files for Publication: render="italic">Michigan Women: First & Founders as it?s the first > use of & that isn?t &. Grasping at straws. > > > > Thanks! > > > > Ed > > > > Generating PDF for Michigan Women's Studies Association records > > org.xml.sax.SAXParseException; lineNumber: 84; columnNumber: 49129; The > entity name must immediately follow the '&' in the entity reference. > > > net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) > > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) > > > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) > > > org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) > > > RUBY.parse(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) > > > RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) > > > RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) > > > RUBY.to_fo(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) > > > RUBY.to_pdf(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) > > RUBY.block in > run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:45) > > > usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) > > > RUBY.run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) > > > usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther45:run(usr/local/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > > > usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > > RUBY.block in > start_background_thread(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-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) > > > > > > > > *Ed Busch, MLIS* > > Acting Director > > 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 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Mar 29 13:45:36 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 29 Mar 2019 17:45:36 +0000 Subject: [Archivesspace_Users_Group] Error when creating PDF Finding Aid Export In-Reply-To: References: Message-ID: Yes: that unescaped ampersand is the likely the problem. I don?t think they have to be escaped everywhere, but having the text wrapped in triggers it being parsed as mixed content rather than just text, so inside the tags, the serializer is expecting valid XML text() . When having problems with the Staff interface PDF output, it?s often a good idea to export as EAD and validate the XML output to locate the source of the problems. ? Steve. > On Mar 29, 2019, at 1:37 PM, Busch, Ed wrote: > > We are doing Print Resource to PDF for a Resource that fails during the background job execution. The errors that appear are below. > Any suggestions on pinpointing what is causing the problem? I?m wondering if it?s this component line > Betty MacDowell Resource Files for Publication: Michigan Women: First & Founders as it?s the first use of & that isn?t &. Grasping at straws. > > Thanks! > > Ed > > Generating PDF for Michigan Women's Studies Association records > org.xml.sax.SAXParseException; lineNumber: 84; columnNumber: 49129; The entity name must immediately follow the '&' in the entity reference. > net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) > org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) > RUBY.parse(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) > RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) > RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) > RUBY.to_fo(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) > RUBY.to_pdf(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) > RUBY.block in run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:45) > usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) > RUBY.run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) > usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther45:run(usr/local/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) > RUBY.block in start_background_thread(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-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) > > > > Ed Busch, MLIS > Acting Director > 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 > > _______________________________________________ > 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: 3598 bytes Desc: not available URL: From buschedw at msu.edu Fri Mar 29 13:55:33 2019 From: buschedw at msu.edu (Busch, Ed) Date: Fri, 29 Mar 2019 17:55:33 +0000 Subject: [Archivesspace_Users_Group] Error when creating PDF Finding Aid Export In-Reply-To: References: Message-ID: Yep, that was it. I thought they were okay within the . Thanks! From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Seth Shaw Sent: Friday, March 29, 2019 1:42 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when creating PDF Finding Aid Export Your guess that "Michigan Women: First & Founders" is causing the failure is probably correct. ArchivesSpace won't encode those ampersands for you. We explicitly train our staff to replace ampersands with `&` but we still occasionally see these errors pop up when someone copy/pastes text and misses one (mostly in citation URLs in notes). Just search for the offending phrase and update the corresponding value. On Fri, Mar 29, 2019 at 10:37 AM Busch, Ed > wrote: We are doing Print Resource to PDF for a Resource that fails during the background job execution. The errors that appear are below. Any suggestions on pinpointing what is causing the problem? I?m wondering if it?s this component line Betty MacDowell Resource Files for Publication: Michigan Women: First & Founders as it?s the first use of & that isn?t &. Grasping at straws. Thanks! Ed Generating PDF for Michigan Women's Studies Association records org.xml.sax.SAXParseException; lineNumber: 84; columnNumber: 49129; The entity name must immediately follow the '&' in the entity reference. net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) RUBY.parse(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:28) RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/processor.rb:58) RUBY.XML(/usr/local/archivesspace/gems/gems/saxon-xslt-0.8.2.1-java/lib/saxon/xml.rb:10) RUBY.to_fo(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:32) RUBY.to_pdf(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38) RUBY.block in run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:45) usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther45:run(usr/local/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) usr.local.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8099_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/usr/local/archivesspace/data/tmp/jetty-0.0.0.0-8099-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) Ed Busch, MLIS Acting Director 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 _______________________________________________ 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: