From nmargulis at astate.edu Tue Sep 4 09:26:28 2018 From: nmargulis at astate.edu (Natasha Margulis) Date: Tue, 4 Sep 2018 13:26:28 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace and Integrated Library Systems? Message-ID: <7ccb423817054362bc6c73a14a8028dd@MBX13-02.astate.edu> Hello ArchivesSpace community! The Dean B Ellis Library is looking for a new Integrated Library System and one of the features we would love to have, but aren't sure it exists, is an integration of Preservica with the ILS. In fact, we would also be thrilled if anyone can share how they got Preservica to work with their Library Catalog. I look forward to hearing what is out there and available. Thank you for any responses! Natasha ________________________________ [http://area51.astate.edu/e-footer/astatelogo-email.jpg] Natasha R. Margulis Political Collections and Access Management Archivist Archives & Special Collections 7th Floor, Dean B. Ellis Library P.O. Box 2040 | State University, AR 72467 p: (870) 972-3128 | f: (870) 972-3199 Arkansas State educates leaders, enhances intellectual growth, and enriches lives. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 10901 bytes Desc: image001.jpg URL: From alexanderduryee at nypl.org Tue Sep 4 10:22:10 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Tue, 4 Sep 2018 10:22:10 -0400 Subject: [Archivesspace_Users_Group] barcodes saga continues... In-Reply-To: References: Message-ID: Lydia, You may want to take a look at NYU's MARC exporter plugin - https://github.com/NYULibraries/nyu_marcxml_export_plugin. This supports exporting item records via the 949 field, including container location, barcode, number, etc. ( https://github.com/NYULibraries/nyu_marcxml_export_plugin/blob/master/backend/lib/marc_custom_field_serialize.rb#L166 ). Depending on your ILS and local policies, you'll need to modify the mappings of ASpace data models to MARCXML via the plugin, but it should do what you're looking for. We use a modified version of the plugin here at the NYPL to generate our MARC + item records in the 949. I'm not aware of a MARC importer that will generate containers from item records, but it's not something that I've ever looked into. Thanks, --Alex On Fri, Aug 31, 2018 at 12:12 PM, Tang, Lydia wrote: > Hi all, > I have a wishful dream about barcoded top containers importing and > exporting out of our catalog system. Does anyone know of a plugin or tool > for enable this to happen? Example scenario: I have a collection with 60+ > barcoded containers nicely described in ArchivesSpace. I can easily export > the MARC record for the collection, but I just wish that it would also > export the item records for the barcoded top containers as well. This way, > when I import the MARCXML into my ILS, it also imports the barcoded and > attached item records. Ideally in the other direction, if a collection is > only described in MARC with attached barcoded item records for each box, > that could be imported into ArchivesSpace to create a stub resource record > with already created top containers. Is it possible? Has it been built? > Thanks, all! > > Lydia > -- > Dr. Lydia Tang, CA, DAS, DMA, MLIS > Special Collections Archivist-Librarian > Philosophy, Aesthetics, and Ethics Bibliographer > Michigan State University Libraries > 366 W. Circle Drive (DB 6) > East Lansing, MI 48824-1048 > Email: ltang5 at msu.edu > Phone: 517-884-8984 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Tue Sep 4 10:38:17 2018 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Tue, 4 Sep 2018 10:38:17 -0400 Subject: [Archivesspace_Users_Group] barcodes saga continues... In-Reply-To: References: Message-ID: If interested, I would advise using the most recent release and not cloning the repo directly, there is active development on this plungin. Don On Tuesday, September 4, 2018, Alexander Duryee wrote: > Lydia, > > You may want to take a look at NYU's MARC exporter plugin - > https://github.com/NYULibraries/nyu_marcxml_export_plugin. This supports > exporting item records via the 949 field, including container location, > barcode, number, etc. (https://github.com/NYULibraries/nyu_marcxml_ > export_plugin/blob/master/backend/lib/marc_custom_field_serialize.rb#L166 > ). > > Depending on your ILS and local policies, you'll need to modify the > mappings of ASpace data models to MARCXML via the plugin, but it should do > what you're looking for. We use a modified version of the plugin here at > the NYPL to generate our MARC + item records in the 949. > > I'm not aware of a MARC importer that will generate containers from item > records, but it's not something that I've ever looked into. > > Thanks, > --Alex > > On Fri, Aug 31, 2018 at 12:12 PM, Tang, Lydia wrote: > >> Hi all, >> I have a wishful dream about barcoded top containers importing and >> exporting out of our catalog system. Does anyone know of a plugin or tool >> for enable this to happen? Example scenario: I have a collection with 60+ >> barcoded containers nicely described in ArchivesSpace. I can easily export >> the MARC record for the collection, but I just wish that it would also >> export the item records for the barcoded top containers as well. This way, >> when I import the MARCXML into my ILS, it also imports the barcoded and >> attached item records. Ideally in the other direction, if a collection is >> only described in MARC with attached barcoded item records for each box, >> that could be imported into ArchivesSpace to create a stub resource record >> with already created top containers. Is it possible? Has it been built? >> Thanks, all! >> >> Lydia >> -- >> Dr. Lydia Tang, CA, DAS, DMA, MLIS >> Special Collections Archivist-Librarian >> Philosophy, Aesthetics, and Ethics Bibliographer >> Michigan State University Libraries >> 366 W. Circle Drive (DB 6) >> East Lansing, MI 48824-1048 >> Email: ltang5 at msu.edu >> Phone: 517-884-8984 >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderduryee at nypl.org > -- Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Tue Sep 4 11:58:00 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Tue, 4 Sep 2018 11:58:00 -0400 Subject: [Archivesspace_Users_Group] How do you describe/include archived websites in your finding aids? Message-ID: Hi everyone, I'd love to see examples of how you're entering information about archived websites (e.g. captured in Archive-It) into ArchivesSpace. Are you using the Digital Object module? Are you also creating Archival Objects? What fields are you filling in? I know there are some plugins to support this (e.g. https://github.com/NYULibraries/Archivesspace-DO-Plugin/wiki/Archive-It-Integration or https://github.com/bentley-historical-library/bhl_aspace_archive_it) but I want to think it through before asking the sysadmin to install anything. We are using the PUI so I would especially appreciate examples in the PUI. Thanks in advance! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Tue Sep 4 18:26:30 2018 From: mkottman at ku.edu (Kottman, Miloche) Date: Tue, 4 Sep 2018 22:26:30 +0000 Subject: [Archivesspace_Users_Group] How do you describe/include archived websites in your finding aids? In-Reply-To: References: Message-ID: <0ad69b2b6c654d0abe2f248fda5c8bf1@ex13-ell-cr-12.home.ku.edu> Celia, I don?t have any examples to share however did you see the recent notification that version 2.0 of the NYARC Metadata Application Profile for Description of Websites with Archives Versions was recently released? I?ve copied the announcement and links that was sent to the PCC list below? --Miloche ?????????????????????????????? Miloche Kottman Head of Cataloging and Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 With apologies for any cross-posting, we announce the recent publication of a consortially developed metadata profile for describing websites. The Frick Art Reference Library, which administers the NYARC Web Archives, is a PCC member (BIBCO and NACO). August 2018 Version 2 Released: Metadata Application Profile for Description of Websites with Archived Versions The second version of the New York Art Resources Consortium (NYARC) Metadata Application Profile for Description of Websites with Archived Versions has recently been released and is available via the NYARC Wiki and via the DLF AIG Metadata Application Profile Clearinghouse Project. The new version of the profile reflects the current practice of describing websites, which has evolved over the past three years since the release of version 1, and specifies the core elements that are recommended for describing websites that are both live and archived, especially in the context of bibliographic description. While based on NYARC?s cataloging practices using MARC, Version 2.0 is intended to be a reference for the library and archives community at large. Originally authored in June 2015 and revised in August 2018 by consultant Rebecca Guenther, the metadata application profile includes a summary and data dictionary of data elements for description of websites with archived versions in a MARC/RDA environment, notes on MARC record coding, and sample records created by NYARC catalogers. In addition, the data dictionary entries include mappings between the elements and those in other metadata standards, including BIBFRAME, EAD, schema.org, and OCLC guidelines, among others. NYARC has implemented these updated guidelines into our workflow for describing the archived websites included in NYARC?s 10 Archive-It collections. We welcome feedback from the community on our application profile for describing websites with archived versions. Many thanks to Rebecca Guenther for her excellent work on the profile and to NYARC?s technical services staff for their input and testing along the way! Best regards, Sumitra Duncan Head, Web Archiving Program Frick Art Reference Library The Frick Collection 10 East 71st Street New York, NY 10021 duncan at frick.org (212) 547-0676 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Celia Caust-Ellenbogen Sent: Tuesday, September 4, 2018 10:58 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] How do you describe/include archived websites in your finding aids? Hi everyone, I'd love to see examples of how you're entering information about archived websites (e.g. captured in Archive-It) into ArchivesSpace. Are you using the Digital Object module? Are you also creating Archival Objects? What fields are you filling in? I know there are some plugins to support this (e.g. https://github.com/NYULibraries/Archivesspace-DO-Plugin/wiki/Archive-It-Integration or https://github.com/bentley-historical-library/bhl_aspace_archive_it) but I want to think it through before asking the sysadmin to install anything. We are using the PUI so I would especially appreciate examples in the PUI. Thanks in advance! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From abersch at calhist.org Tue Sep 4 18:53:23 2018 From: abersch at calhist.org (Al Bersch) Date: Tue, 4 Sep 2018 22:53:23 +0000 Subject: [Archivesspace_Users_Group] server error when adding sibling In-Reply-To: References: Message-ID: Hello Blake, Thanks for getting back to me. As of this morning, the issue is resolved/has disappeared and cannot be replicated. To answer your questions, though - we're running version 2.2.1. I don't have access at this point to see the logs (that I know of) - our instance of Aspace is being hosted by LibraryHost. Thanks again - Al -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver Sent: Friday, August 31, 2018 6:04 PM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] server error when adding sibling What version are you running? Can you find that error in the logs? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Al Bersch Sent: Friday, August 31, 2018 8:00:13 PM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] server error when adding sibling Hello, We're having an issue/bug when attempting to add a sibling to a series. Clicking on the "add sibling" button results in the message "An error occurred loading this form. Server error", and a New Archival Object entry that appears to duplicate the files of the above sub-series. When the record is closed, I am unable to open the series, sub-series, or files in that record, getting an error message that says "an error occurred loading this form. Server error." Screenshots are attached. If anyone has any ideas about this, it'd be great to hear! Many thanks, Al Al Bersch, Metadata and Systems Librarian California Historical Society 678 Mission Street, San Francisco, CA 94105 415.357.1848 http://www.californiahistoricalsociety.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From melissa.wisner at yale.edu Thu Sep 6 15:39:12 2018 From: melissa.wisner at yale.edu (Wisner, Melissa) Date: Thu, 6 Sep 2018 19:39:12 +0000 Subject: [Archivesspace_Users_Group] debut of ArchivesSpace Public User Interface at Yale Message-ID: Hello, This week Yale University has launched the ArchivesSpace public user interface as "Archives at Yale." We have been working over the last year to develop and customize the public user interface, address accessibility and usability issues, and integrate the PUI with our special collections request workflow in Aeon. Throughout our implementation we called upon our colleagues at LYRASIS, Harvard, University of Louisville, and Georgia Tech; as well as Duke and North Carolina State University, creators of the awesome EAD3 export option - thanks, Noah and Trevor! And of course, Hudson Molonglo - thanks, James, Payten, and Mark!!! We couldn't have reached this week without all of you, and sincere thanks are due. We hope to share as much of our work as possible, so if there is anything you see that you don't have in place, please let us know. Melissa Wisner and Mark Custer -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Sep 7 10:41:12 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 7 Sep 2018 14:41:12 +0000 Subject: [Archivesspace_Users_Group] upcoming online series highlighting sustainability for open source projects Message-ID: Dear ArchivesSpace members, For those of you who might be interested in open source more broadly, I wanted to pass along information about an upcoming four-part online series that LYRASIS is offering based on the IMLS-funded It Takes a Village project. It Takes a Village brought together 27 open source software projects in the cultural and scientific heritage sector to identify key factors for sustainability and success. ArchivesSpace participated in the activities and will be featured in several of the sessions of the online series. This series may be especially useful for those involved in or considering how to move their own open source projects forward. More information is online at https://www.lyrasis.org/technology/Pages/itav-classes.aspx. Please also feel free to reach out to Laurie Arp (laurie.arp at lyrasis.org) if you have any questions about the series or the project itself. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From jsuszczynski at library.rochester.edu Mon Sep 10 14:53:46 2018 From: jsuszczynski at library.rochester.edu (Suszczynski, Jeffrey) Date: Mon, 10 Sep 2018 18:53:46 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Message-ID: Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmcphee at ucsd.edu Mon Sep 10 15:14:23 2018 From: lmcphee at ucsd.edu (McPhee, Laurel) Date: Mon, 10 Sep 2018 19:14:23 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: Hi Jeff, Other folks might have smarter solutions than I (or more directly answer to why this is happening) but I would suggest this work-around: Don't round-trip your whole finding aids (export, add data, re-import). I would do the following: take your exported EAD files, convert them to CSV, make sure the new ID elements you want are in a column of the CSV. Then, take that CSV file, using the ASpace-generated item or folder-level REFIDs as "hooks," to make ASpace generate the ID attribute you want directly in the resource record via the API. We haven't done that exact task, so I can't promise it would work, but we've done very similar things (mass additions/creations of data and linking of digital objects) to records using CSVs and the API. Takes some scripting knowledge, and familiarity with using the API-but it sounds like you have that ability. Hope this is helpful, let me know off-list if you need more details. Laurel Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suszczynski, Jeffrey Sent: Monday, September 10, 2018 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Mon Sep 10 15:15:16 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Mon, 10 Sep 2018 19:15:16 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: Hi Jeff, We use the id attribute of the component tag in EAD ( or ) to link from finding aids to digital objects in our repository. On EAD import, the component ID attribute value is mapped to the archival object ref_id field in ASpace. On EAD export, the ref_id maps back to c/@id. So, you might consider adding those unique identifiers to your component or tags instead of tags. -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Suszczynski, Jeffrey Sent: Monday, September 10, 2018 2:54 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Mon Sep 10 15:27:17 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Mon, 10 Sep 2018 19:27:17 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: I second Laurel's advice about NOT round-tripping EAD if you can avoid it, but I vaguely remember trying the exact approach she describes some time ago and I was unable to POST new ref_id values to existing Archival Objects using the API. Ref ID values are not editable in the staff interface (even though the tooltip says they are "updatable"), so I wonder if they are not editable via the API either? If they were editable, then this would definitely be the way to go. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of McPhee, Laurel Sent: Monday, September 10, 2018 3:14 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hi Jeff, Other folks might have smarter solutions than I (or more directly answer to why this is happening) but I would suggest this work-around: Don't round-trip your whole finding aids (export, add data, re-import). I would do the following: take your exported EAD files, convert them to CSV, make sure the new ID elements you want are in a column of the CSV. Then, take that CSV file, using the ASpace-generated item or folder-level REFIDs as "hooks," to make ASpace generate the ID attribute you want directly in the resource record via the API. We haven't done that exact task, so I can't promise it would work, but we've done very similar things (mass additions/creations of data and linking of digital objects) to records using CSVs and the API. Takes some scripting knowledge, and familiarity with using the API-but it sounds like you have that ability. Hope this is helpful, let me know off-list if you need more details. Laurel Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suszczynski, Jeffrey Sent: Monday, September 10, 2018 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Mon Sep 10 15:29:17 2018 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 10 Sep 2018 19:29:17 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: <7ec84bc7b589405c8204c024a7cd4e10@RACEX13.ad.rockarchive.org> We have a hacky way of editing them that I turn off and on if we ever need to edit them, but they can be editable if you enable it. -Patrick Galligan Digital Archivist Rockefeller Archive Center From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Noah Huffman Sent: Monday, September 10, 2018 3:27 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes I second Laurel's advice about NOT round-tripping EAD if you can avoid it, but I vaguely remember trying the exact approach she describes some time ago and I was unable to POST new ref_id values to existing Archival Objects using the API. Ref ID values are not editable in the staff interface (even though the tooltip says they are "updatable"), so I wonder if they are not editable via the API either? If they were editable, then this would definitely be the way to go. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of McPhee, Laurel Sent: Monday, September 10, 2018 3:14 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hi Jeff, Other folks might have smarter solutions than I (or more directly answer to why this is happening) but I would suggest this work-around: Don't round-trip your whole finding aids (export, add data, re-import). I would do the following: take your exported EAD files, convert them to CSV, make sure the new ID elements you want are in a column of the CSV. Then, take that CSV file, using the ASpace-generated item or folder-level REFIDs as "hooks," to make ASpace generate the ID attribute you want directly in the resource record via the API. We haven't done that exact task, so I can't promise it would work, but we've done very similar things (mass additions/creations of data and linking of digital objects) to records using CSVs and the API. Takes some scripting knowledge, and familiarity with using the API-but it sounds like you have that ability. Hope this is helpful, let me know off-list if you need more details. Laurel Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suszczynski, Jeffrey Sent: Monday, September 10, 2018 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Sep 10 15:54:20 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 10 Sep 2018 19:54:20 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: <42EE5CB0-E4BD-46C1-AF72-292CA4FA0374@virginia.edu> You might also consider using component instead of unittitle/@id?s. A while ago, I added capability on EAD import/export to handle multiple ?s so that we could like to components in other internal systems. If they have a @type attribute, they will be mapped to external id?s in ArchivesSpace. So for example, this EAD fragment: 00704001 Letter from Henry Rose Carter to Emma Coleman CarterDecember 17, 1883 uva-lib:2222445 7 4 6 pages English Carter, Henry Rose, 1852-1925

Carter provides family news and describes Christmas celebrations.

http://tracksys.lib.virginia.edu/admin/components/500473

Carter provides family news and describes Christmas celebrations.

Interpersonal relations Social history Yellow fever letters (correspondence)
maps to: > On Sep 10, 2018, at 2:53 PM, Suszczynski, Jeffrey wrote: > > Hello, all ? > > I?ve searched through the listserv archives and didn?t find anything directly related to the issue I am about to describe; apologies in advance if I?ve missed something and this topic has already been discussed. > > At the University of Rochester, we have some finding aids that I?ve programmatically exported from ArchivesSpace, then modified, adding the attribute ?ID? to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora? > > From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) ? all of the elements were intact, but no longer had ID attributes? I?ve tried several tactics in attempts to preserve those ID attributes, thus far to no avail. > > Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I?ve overlooked somehow. > > Many thanks in advance for any ideas you may have! > > Jeff > > Jeff Suszczynski > Web Developer, River Campus Libraries > University of Rochester > > > > _______________________________________________ > 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: as-ext-id.png Type: image/png Size: 651043 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From adrien_hilton at harvard.edu Mon Sep 10 16:33:57 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Mon, 10 Sep 2018 20:33:57 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: Hi Laurel, This is probably a dumb question, but what mechanism do you use to convert the EAD to CSV. That would be helpful for me as well. Thanks! Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of McPhee, Laurel Sent: Monday, September 10, 2018 3:14 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hi Jeff, Other folks might have smarter solutions than I (or more directly answer to why this is happening) but I would suggest this work-around: Don't round-trip your whole finding aids (export, add data, re-import). I would do the following: take your exported EAD files, convert them to CSV, make sure the new ID elements you want are in a column of the CSV. Then, take that CSV file, using the ASpace-generated item or folder-level REFIDs as "hooks," to make ASpace generate the ID attribute you want directly in the resource record via the API. We haven't done that exact task, so I can't promise it would work, but we've done very similar things (mass additions/creations of data and linking of digital objects) to records using CSVs and the API. Takes some scripting knowledge, and familiarity with using the API-but it sounds like you have that ability. Hope this is helpful, let me know off-list if you need more details. Laurel Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suszczynski, Jeffrey Sent: Monday, September 10, 2018 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmcphee at ucsd.edu Mon Sep 10 17:02:27 2018 From: lmcphee at ucsd.edu (McPhee, Laurel) Date: Mon, 10 Sep 2018 21:02:27 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: References: Message-ID: Hi Adrien, The UCSD EAD stylesheets are here: https://github.com/mdpeters/EAD_stylesheets. You'll see the ead_to_csv template (as well as some local-use stuff). The ead to csv script is just an XSLT script, you can use it with any XSLT 2.0 capable processor. Matt Peters, who create it, has tied it into our ASpace export tool but that's not necessary for its use. This allows archivists and processors, whenever they want to "harvest" a container list, to simply run a command from the command line and basically pull a container list straight from ASpace into a CSV (and from there, Excel). It's really useful, especially for fixing weird legacy finding aids. We do the fixing in Excel and then re-import the updated container list with a stub of dummy front matter, and merge it into the parent resource record from whence it came (and delete the old stuff). Laurel From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilton, Adrien Sent: Monday, September 10, 2018 1:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hi Laurel, This is probably a dumb question, but what mechanism do you use to convert the EAD to CSV. That would be helpful for me as well. Thanks! Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of McPhee, Laurel Sent: Monday, September 10, 2018 3:14 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hi Jeff, Other folks might have smarter solutions than I (or more directly answer to why this is happening) but I would suggest this work-around: Don't round-trip your whole finding aids (export, add data, re-import). I would do the following: take your exported EAD files, convert them to CSV, make sure the new ID elements you want are in a column of the CSV. Then, take that CSV file, using the ASpace-generated item or folder-level REFIDs as "hooks," to make ASpace generate the ID attribute you want directly in the resource record via the API. We haven't done that exact task, so I can't promise it would work, but we've done very similar things (mass additions/creations of data and linking of digital objects) to records using CSVs and the API. Takes some scripting knowledge, and familiarity with using the API-but it sounds like you have that ability. Hope this is helpful, let me know off-list if you need more details. Laurel Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suszczynski, Jeffrey Sent: Monday, September 10, 2018 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes Hello, all - I've searched through the listserv archives and didn't find anything directly related to the issue I am about to describe; apologies in advance if I've missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I've programmatically exported from ArchivesSpace, then modified, adding the attribute 'ID' to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora... >From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) - all of the elements were intact, but no longer had ID attributes... I've tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I've overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsuszczynski at library.rochester.edu Mon Sep 10 18:34:20 2018 From: jsuszczynski at library.rochester.edu (Suszczynski, Jeffrey) Date: Mon, 10 Sep 2018 22:34:20 +0000 Subject: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes In-Reply-To: <42EE5CB0-E4BD-46C1-AF72-292CA4FA0374@virginia.edu> References: <42EE5CB0-E4BD-46C1-AF72-292CA4FA0374@virginia.edu> Message-ID: Thank you to all who responded ? it?s much appreciated, and I now have a few new options to think about and potentially try. I?ll post back to the listserv in the coming days after I?ve talked with some of my colleagues here at the UR and we?ve tested one or more of the suggested solutions. Thanks again more making this such a fruitful post! jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Monday, September 10, 2018 3:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: elements with ID attributes You might also consider using component instead of unittitle/@id?s. A while ago, I added capability on EAD import/export to handle multiple ?s so that we could like to components in other internal systems. If they have a @type attribute, they will be mapped to external id?s in ArchivesSpace. So for example, this EAD fragment: 00704001 Letter from Henry Rose Carter to Emma Coleman CarterDecember 17, 1883 uva-lib:2222445 7 4 6 pages English Carter, Henry Rose, 1852-1925

Carter provides family news and describes Christmas celebrations.

http://tracksys.lib.virginia.edu/admin/components/500473

Carter provides family news and describes Christmas celebrations.

Interpersonal relations Social history Yellow fever letters (correspondence)
maps to: [cid:image001.png at 01D44934.DB2CF270] On Sep 10, 2018, at 2:53 PM, Suszczynski, Jeffrey > wrote: Hello, all ? I?ve searched through the listserv archives and didn?t find anything directly related to the issue I am about to describe; apologies in advance if I?ve missed something and this topic has already been discussed. At the University of Rochester, we have some finding aids that I?ve programmatically exported from ArchivesSpace, then modified, adding the attribute ?ID? to our elements so that we can use unique identifiers as a means of linking from our finding aids to digital objects in our instance of Islandora? From everything that I can see, this ID attribute for is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) ? all of the elements were intact, but no longer had ID attributes? I?ve tried several tactics in attempts to preserve those ID attributes, thus far to no avail. Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious solution that I?ve overlooked somehow. Many thanks in advance for any ideas you may have! Jeff Jeff Suszczynski Web Developer, River Campus Libraries University of Rochester _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 651043 bytes Desc: image001.png URL: From ahueb2 at uis.edu Tue Sep 11 09:53:37 2018 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Tue, 11 Sep 2018 13:53:37 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace color scheme customization Message-ID: <2fb2d0831493414b8a309b60a0ac948c@uismbx02.uisad.uis.edu> Hi all, I've been working on customizing the ArchivesSpace public interface for our institution, but I keep running into issues when trying to change the colors used under ./public/app/assets/stylesheets/archivesspace/colors.scss. I'm running version 2.5.0 on our test instance and working with the 2.5.0.a source code. Every time I compile the public.war file and replace it in the wars folder in my test distribution, I get an internal server error 500. The only thing I've been changing are the hex values for the colors, so I would think these files should be easily interchangeable. Does anyone have some insight? Any help would be appreciated. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahueb2 at uis.edu Tue Sep 11 13:06:59 2018 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Tue, 11 Sep 2018 17:06:59 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace color scheme customization In-Reply-To: <58DAAEC0-D2E7-452F-9CF4-EE1CEAAEFC6C@virginia.edu> References: <2fb2d0831493414b8a309b60a0ac948c@uismbx02.uisad.uis.edu> <58DAAEC0-D2E7-452F-9CF4-EE1CEAAEFC6C@virginia.edu> Message-ID: <156cfceacd16417088249b91bdeef77c@uismbx02.uisad.uis.edu> I?ve attached a screenshot of the full error. I?ve tried using the source code using git checkout 2.5.0 and downloading the source code directly from the v2.5.0 release, both list ?v2.5.0.a? at the bottom of the rendered pages for the frontend and public interface, the same error occurs when building the public.war file from both sources. I have also tried taking the public.war file directly out of the official v2.5.0 release, opening it with winrar and replacing the colors.scss file which had absolutely no effect (no changes and no errors). I decided to build just the war file because I figured it might make upgrades go a little smoother in the future. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 From: Majewski, Steven Dennis (sdm7g) Sent: Tuesday, September 11, 2018 10:49 AM To: Huebschen, Alan M Subject: Re: [Archivesspace_Users_Group] ArchivesSpace color scheme customization What sort of errors are you getting in the log file ? I don?t know what you mean by ?2.5.0.a? source code: Are you working with git tag v2.5.0 or source code release from https://github.com/archivesspace/archivesspace/releases/tag/v2.5.0 ? Why not build a complete distribution instead of just replacing public war file ? ( I can imagine ways that source code and distribution could get out of sync? ) ? Steve Majewski On Sep 11, 2018, at 9:53 AM, Huebschen, Alan M > wrote: Hi all, I?ve been working on customizing the ArchivesSpace public interface for our institution, but I keep running into issues when trying to change the colors used under ./public/app/assets/stylesheets/archivesspace/colors.scss. I?m running version 2.5.0 on our test instance and working with the 2.5.0.a source code. Every time I compile the public.war file and replace it in the wars folder in my test distribution, I get an internal server error 500. The only thing I?ve been changing are the hex values for the colors, so I would think these files should be easily interchangeable. Does anyone have some insight? Any help would be appreciated. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2018-09-11 12_01_54-Internal Server Error at _ - Firefox Developer Editi....png Type: image/png Size: 42032 bytes Desc: 2018-09-11 12_01_54-Internal Server Error at _ - Firefox Developer Editi....png URL: From sdm7g at virginia.edu Tue Sep 11 13:47:13 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 11 Sep 2018 17:47:13 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace color scheme customization In-Reply-To: <156cfceacd16417088249b91bdeef77c@uismbx02.uisad.uis.edu> References: <2fb2d0831493414b8a309b60a0ac948c@uismbx02.uisad.uis.edu> <58DAAEC0-D2E7-452F-9CF4-EE1CEAAEFC6C@virginia.edu> <156cfceacd16417088249b91bdeef77c@uismbx02.uisad.uis.edu> Message-ID: public_suffix-3.0.2 is in the build/gems/gems/ directory in my source/development repo, however I don?t see it in an unpacked production server distribution gems directory. I find it in public/Gemfile.lock: https://github.com/archivesspace/archivesspace/blame/v2.5.0/public/Gemfile.lock Nothing about those specs has changed immediately before or after v2.5.0 release, but the commit for that addition 4 months ago says it was to ?Add Capybara + Selenium test to PUI? and public_suffix appears to be pulled in as part of those gems. Looking in public/Gemfile, capybara gem is inside a 'group :test do? block: https://github.com/archivesspace/archivesspace/blob/v2.5.0/public/Gemfile#L77 So it would appear that those gems are only included for test in the development server and aren?t packaged for production server. Are you building public.war as a build.xml target ? : ?./build/run public:war? Looking at the dist build target in build/build.xml, I see that when it calls the war file build targets, it sets an excluded-gem-groups parameter to ?test development doc? . This is probably the source of you problem. ? Steve M. > On Sep 11, 2018, at 1:06 PM, Huebschen, Alan M wrote: > > I?ve attached a screenshot of the full error. > I?ve tried using the source code using git checkout 2.5.0 and downloading the source code directly from the v2.5.0 release, both list ?v2.5.0.a? at the bottom of the rendered pages for the frontend and public interface, the same error occurs when building the public.war file from both sources. I have also tried taking the public.war file directly out of the official v2.5.0 release, opening it with winrar and replacing the colors.scss file which had absolutely no effect (no changes and no errors). > I decided to build just the war file because I figured it might make upgrades go a little smoother in the future. > > -Alan Huebschen > Brookens Library > Information Systems > (217) 206-7115 > > From: Majewski, Steven Dennis (sdm7g) > Sent: Tuesday, September 11, 2018 10:49 AM > To: Huebschen, Alan M > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace color scheme customization > > > What sort of errors are you getting in the log file ? > > > I don?t know what you mean by ?2.5.0.a? source code: > Are you working with git tag v2.5.0 or source code release from https://github.com/archivesspace/archivesspace/releases/tag/v2.5.0 ? > > Why not build a complete distribution instead of just replacing public war file ? > ( I can imagine ways that source code and distribution could get out of sync? ) > > > ? Steve Majewski > > > On Sep 11, 2018, at 9:53 AM, Huebschen, Alan M > wrote: > > Hi all, > > I?ve been working on customizing the ArchivesSpace public interface for our institution, but I keep running into issues when trying to change the colors used under ./public/app/assets/stylesheets/archivesspace/colors.scss. I?m running version 2.5.0 on our test instance and working with the 2.5.0.a source code. Every time I compile the public.war file and replace it in the wars folder in my test distribution, I get an internal server error 500. The only thing I?ve been changing are the hex values for the colors, so I would think these files should be easily interchangeable. Does anyone have some insight? Any help would be appreciated. > > -Alan Huebschen > Brookens Library > Information Systems > (217) 206-7115 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > <2018-09-11 12_01_54-Internal Server Error at _ - Firefox Developer Editi....png> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From ahueb2 at uis.edu Tue Sep 11 14:07:04 2018 From: ahueb2 at uis.edu (Huebschen, Alan M) Date: Tue, 11 Sep 2018 18:07:04 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace color scheme customization In-Reply-To: References: <2fb2d0831493414b8a309b60a0ac948c@uismbx02.uisad.uis.edu> <58DAAEC0-D2E7-452F-9CF4-EE1CEAAEFC6C@virginia.edu> <156cfceacd16417088249b91bdeef77c@uismbx02.uisad.uis.edu> Message-ID: <12dfc8c01ab649f3bb9420266e715e2d@uismbx02.uisad.uis.edu> Excluding test development doc fixed the issue, thanks for the help Steve! -Alan Huebschen Brookens Library Information Systems (217) 206-7115 From: Majewski, Steven Dennis (sdm7g) Sent: Tuesday, September 11, 2018 12:47 PM To: Huebschen, Alan M Cc: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace color scheme customization public_suffix-3.0.2 is in the build/gems/gems/ directory in my source/development repo, however I don?t see it in an unpacked production server distribution gems directory. I find it in public/Gemfile.lock: https://github.com/archivesspace/archivesspace/blame/v2.5.0/public/Gemfile.lock Nothing about those specs has changed immediately before or after v2.5.0 release, but the commit for that addition 4 months ago says it was to ?Add Capybara + Selenium test to PUI? and public_suffix appears to be pulled in as part of those gems. Looking in public/Gemfile, capybara gem is inside a 'group :test do? block: https://github.com/archivesspace/archivesspace/blob/v2.5.0/public/Gemfile#L77 So it would appear that those gems are only included for test in the development server and aren?t packaged for production server. Are you building public.war as a build.xml target ? : ?./build/run public:war? Looking at the dist build target in build/build.xml, I see that when it calls the war file build targets, it sets an excluded-gem-groups parameter to ?test development doc? . This is probably the source of you problem. ? Steve M. On Sep 11, 2018, at 1:06 PM, Huebschen, Alan M > wrote: I?ve attached a screenshot of the full error. I?ve tried using the source code using git checkout 2.5.0 and downloading the source code directly from the v2.5.0 release, both list ?v2.5.0.a? at the bottom of the rendered pages for the frontend and public interface, the same error occurs when building the public.war file from both sources. I have also tried taking the public.war file directly out of the official v2.5.0 release, opening it with winrar and replacing the colors.scss file which had absolutely no effect (no changes and no errors). I decided to build just the war file because I figured it might make upgrades go a little smoother in the future. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 From: Majewski, Steven Dennis (sdm7g) > Sent: Tuesday, September 11, 2018 10:49 AM To: Huebschen, Alan M > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace color scheme customization What sort of errors are you getting in the log file ? I don?t know what you mean by ?2.5.0.a? source code: Are you working with git tag v2.5.0 or source code release from https://github.com/archivesspace/archivesspace/releases/tag/v2.5.0 ? Why not build a complete distribution instead of just replacing public war file ? ( I can imagine ways that source code and distribution could get out of sync? ) ? Steve Majewski On Sep 11, 2018, at 9:53 AM, Huebschen, Alan M > wrote: Hi all, I?ve been working on customizing the ArchivesSpace public interface for our institution, but I keep running into issues when trying to change the colors used under ./public/app/assets/stylesheets/archivesspace/colors.scss. I?m running version 2.5.0 on our test instance and working with the 2.5.0.a source code. Every time I compile the public.war file and replace it in the wars folder in my test distribution, I get an internal server error 500. The only thing I?ve been changing are the hex values for the colors, so I would think these files should be easily interchangeable. Does anyone have some insight? Any help would be appreciated. -Alan Huebschen Brookens Library Information Systems (217) 206-7115 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <2018-09-11 12_01_54-Internal Server Error at _ - Firefox Developer Editi....png> -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Tue Sep 11 15:36:28 2018 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Tue, 11 Sep 2018 19:36:28 +0000 Subject: [Archivesspace_Users_Group] TAC Integrations Update Message-ID: <6128c5ad455c4b01b5a867b90c329b4e@RACEX13.ad.rockarchive.org> Hi all, I'm writing on behalf of the TAC Integrations subteam to remind everyone that if you're currently working on or plan to work on an ArchivesSpace Integration, we'd like to hear about it! You can give us information through the ArchivesSpace Integrations Information Google Form. Please let us know about your integration work by filling out the form to the best of your ability. Once submitted, we'll take a look during one of our monthly calls. The responses to this form and other surveys help us figure out the best way to help you! One of our team members, Maggie Hughes also recently gathered a lot of community information about integrations you would like to see, and we're trying to figure out the best way to share that back to the community. What would you like to see? We have a list of types of integrations the community is interested in, and we could share a list of the most requested systems integrations back with the community? We're hoping that could help stimulate some conversation. Would that be helpful for you? Let us know. Thanks! Patrick Galligan Digital Archivist Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Tue Sep 11 16:30:17 2018 From: smithkr at mit.edu (Kari R Smith) Date: Tue, 11 Sep 2018 20:30:17 +0000 Subject: [Archivesspace_Users_Group] Looking to talk with folks who have both Alma (LMS) and ArchivesSpace (AMS) working together Message-ID: <29F559819ACA9A4FBF208407D4B63ABB018FFF91F6@W92EXPO28.exchange.mit.edu> Hi all, I'm piggy-backing on Patrick's Integrations message to ask if any who has both Alma (library catalog system) and ArchivesSpace working together in any (positive) fashion would be up to talking with me about how / what you are doing to push/pull metadata between these systems. Please respond directly to me and I'll summarize for the group. Thanks! Kari -------------------------------------------------------------------------- Kari R. Smith Institute Archivist and Program Head, Digital Archives Institute Archives & Special Collections, MIT Libraries Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 IASC office: 617.258.5568 http://libraries.mit.edu/archives/ she | her | hers @karirene69 [smithkr at mit.edu] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Galligan, Patrick Sent: Tuesday, September 11, 2018 3:36 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] TAC Integrations Update Hi all, I'm writing on behalf of the TAC Integrations subteam to remind everyone that if you're currently working on or plan to work on an ArchivesSpace Integration, we'd like to hear about it! You can give us information through the ArchivesSpace Integrations Information Google Form. Please let us know about your integration work by filling out the form to the best of your ability. Once submitted, we'll take a look during one of our monthly calls. The responses to this form and other surveys help us figure out the best way to help you! One of our team members, Maggie Hughes also recently gathered a lot of community information about integrations you would like to see, and we're trying to figure out the best way to share that back to the community. What would you like to see? We have a list of types of integrations the community is interested in, and we could share a list of the most requested systems integrations back with the community? We're hoping that could help stimulate some conversation. Would that be helpful for you? Let us know. Thanks! Patrick Galligan Digital Archivist Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Tue Sep 11 18:31:51 2018 From: luftsche at usc.edu (Susan Luftschein) Date: Tue, 11 Sep 2018 22:31:51 +0000 Subject: [Archivesspace_Users_Group] MARC export in v 2.5 Message-ID: HI all, We just upgraded to 2.5 and I am seeing some interesting things happening in the MARC export. First, a subfield b is being added to the 041, and subfield e is being added to 600 and 610 fields. Is there any way to turn these off? The relator term "subject" in a 6xx field seems rather redundant. Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Wed Sep 12 09:54:33 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 12 Sep 2018 08:54:33 -0500 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 Message-ID: Hello all, We have been having a problem with the auto-complete suggestions for linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always present relevant suggestions. For example, we have an existing corporate agent, "Texas Federation of Music Clubs." When I try to add the agent, it presents the following: [image: Screen Shot 2018-08-31 at 2.41.48 PM.png] So it is pulling suggestions from the family agents. Similarly, we have an agent person "Smith, Liz, 1923-2017." It does not present her as an option unless we type ", " after her name. Someone who wants to add her, though, won't necessarily know that she's got a date addition. Again it pulls from family agents. [image: Screen Shot 2018-09-12 at 8.44.48 AM.png] [image: Screen Shot 2018-09-12 at 8.44.59 AM.png] This what the suggestions looked like in 1.5.3 for us: [image: Screen Shot 2018-08-31 at 3.49.41 PM.png] [image: image.png] Has anyone else had a problem with this? Trying to figure out if this is an issue with 2.4.1 or with our data. Perhaps we've got something configured incorrectly in our settings? We've already tried re-indexing, but that did not help. Any suggestions would be great! 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-31 at 2.41.48 PM.png Type: image/png Size: 49861 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-12 at 8.44.48 AM.png Type: image/png Size: 57049 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-12 at 8.44.59 AM.png Type: image/png Size: 60143 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-31 at 3.49.41 PM.png Type: image/png Size: 93731 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 54757 bytes Desc: not available URL: From eckardm at umich.edu Wed Sep 12 09:58:53 2018 From: eckardm at umich.edu (Max Eckard) Date: Wed, 12 Sep 2018 09:58:53 -0400 Subject: [Archivesspace_Users_Group] Looking to talk with folks who have both Alma (LMS) and ArchivesSpace (AMS) working together In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB018FFF91F6@W92EXPO28.exchange.mit.edu> References: <29F559819ACA9A4FBF208407D4B63ABB018FFF91F6@W92EXPO28.exchange.mit.edu> Message-ID: Hi Patrick, Regarding the feedback Maggie gathered--for each of the integration scenarios (by system or function, see below) you received, it might be helpful to facilitate community conversations (and document the outcome of them) around the purpose of such an integration (i.e., what problem it's solving), whose interested, and what, in more precise terms, needs to happen in the integration (i.e., what components of the respective systems need to communicate, what kind of data needs to flow, which direction it needs to flow, how you might facilitate that flow in the near term and in a perfect world, etc.). It might also be helpful to identify similar completed or in-progress integration projects that future integration projects could riff off. I could see the resulting documentation being really helpful. It can see this being mapped to particular systems (like Kari's example of an Alma-ArchivesSpace integration), or even generalized more to the function of systems (e.g., ArchivesSpace and ILS), with systems used as examples. Maybe that helps? Max On Tue, Sep 11, 2018 at 4:30 PM Kari R Smith wrote: > Hi all, > > I?m piggy-backing on Patrick?s Integrations message to ask if any who has > both Alma (library catalog system) and ArchivesSpace working together in > any (positive) fashion would be up to talking with me about how / what you > are doing to push/pull metadata between these systems. > > > > Please respond directly to me and I?ll summarize for the group. > > > > Thanks! > > Kari > > > > -------------------------------------------------------------------------- > > Kari R. Smith > > Institute Archivist and Program Head, Digital Archives > > Institute Archives & Special Collections, MIT Libraries > > Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 > > IASC office: 617.258.5568 http://libraries.mit.edu/archives/ > > she | her | hers @karirene69 [smithkr at mit.edu] > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Galligan, > Patrick > *Sent:* Tuesday, September 11, 2018 3:36 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] TAC Integrations Update > > > > Hi all, > > > > I?m writing on behalf of the TAC Integrations subteam to remind everyone > that if you?re currently working on or plan to work on an ArchivesSpace > Integration, we?d like to hear about it! You can give us information > through the ArchivesSpace Integrations Information > Google > Form. Please let us know about your integration work by filling out the > form to the best of your ability. Once submitted, we'll take a look during > one of our monthly calls. > > > > The responses to this form and other surveys help us figure out the best > way to help you! > > > > One of our team members, Maggie Hughes also recently gathered a lot of > community information about integrations you would like to see, and we?re > trying to figure out the best way to share that back to the community. What > would you like to see? We have a list of types of integrations the > community is interested in, and we could share a list of the most requested > systems integrations back with the community? We?re hoping that could help > stimulate some conversation. Would that be helpful for you? Let us know. > > > > Thanks! > > > > Patrick Galligan > > Digital Archivist > > Rockefeller Archive Center > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Max Eckard* Lead Archivist for Digital Initiatives 1150 Beal Avenue Ann Arbor, MI 48109-2113 *(734) 763-7518* *http://bentley.umich.edu/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Sep 12 10:29:45 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 12 Sep 2018 14:29:45 +0000 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 In-Reply-To: References: Message-ID: Is this the same issue? https://archivesspace.atlassian.net/browse/ANW-762 ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Olivia S Solis Sent: Wednesday, September 12, 2018 9:54:33 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 Hello all, We have been having a problem with the auto-complete suggestions for linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always present relevant suggestions. For example, we have an existing corporate agent, "Texas Federation of Music Clubs." When I try to add the agent, it presents the following: [Screen Shot 2018-08-31 at 2.41.48 PM.png] So it is pulling suggestions from the family agents. Similarly, we have an agent person "Smith, Liz, 1923-2017." It does not present her as an option unless we type ", " after her name. Someone who wants to add her, though, won't necessarily know that she's got a date addition. Again it pulls from family agents. [Screen Shot 2018-09-12 at 8.44.48 AM.png] [Screen Shot 2018-09-12 at 8.44.59 AM.png] This what the suggestions looked like in 1.5.3 for us: [Screen Shot 2018-08-31 at 3.49.41 PM.png] [image.png] Has anyone else had a problem with this? Trying to figure out if this is an issue with 2.4.1 or with our data. Perhaps we've got something configured incorrectly in our settings? We've already tried re-indexing, but that did not help. Any suggestions would be great! 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-31 at 2.41.48 PM.png Type: image/png Size: 49861 bytes Desc: Screen Shot 2018-08-31 at 2.41.48 PM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-12 at 8.44.48 AM.png Type: image/png Size: 57049 bytes Desc: Screen Shot 2018-09-12 at 8.44.48 AM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-12 at 8.44.59 AM.png Type: image/png Size: 60143 bytes Desc: Screen Shot 2018-09-12 at 8.44.59 AM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-31 at 3.49.41 PM.png Type: image/png Size: 93731 bytes Desc: Screen Shot 2018-08-31 at 3.49.41 PM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 54757 bytes Desc: image.png URL: From ldfs at umn.edu Wed Sep 12 10:34:21 2018 From: ldfs at umn.edu (Lara Friedman-Shedlov) Date: Wed, 12 Sep 2018 09:34:21 -0500 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 In-Reply-To: References: Message-ID: Yes, that's the same issue. We've been having it here at the University of Minnesota as well. Reindexing did not solve the issue. On Wed, Sep 12, 2018 at 9:30 AM Blake Carver wrote: > Is this the same issue? > > https://archivesspace.atlassian.net/browse/ANW-762 > > ________________________________________ > 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, September 12, 2018 9:54:33 AM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 > > Hello all, > > We have been having a problem with the auto-complete suggestions for > linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always > present relevant suggestions. For example, we have an existing corporate > agent, "Texas Federation of Music Clubs." When I try to add the agent, it > presents the following: > > [Screen Shot 2018-08-31 at 2.41.48 PM.png] > > So it is pulling suggestions from the family agents. Similarly, we have an > agent person "Smith, Liz, 1923-2017." It does not present her as an option > unless we type ", " after her name. Someone who wants to add her, though, > won't necessarily know that she's got a date addition. Again it pulls from > family agents. > [Screen Shot 2018-09-12 at 8.44.48 AM.png] > [Screen Shot 2018-09-12 at 8.44.59 AM.png] > > This what the suggestions looked like in 1.5.3 for us: > [Screen Shot 2018-08-31 at 3.49.41 PM.png] > [image.png] > > Has anyone else had a problem with this? Trying to figure out if this is > an issue with 2.4.1 or with our data. Perhaps we've got something > configured incorrectly in our settings? > > We've already tried re-indexing, but that did not help. > > Any suggestions would be great! > > 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 > -- _________________________________ Lara D. Friedman-Shedlov (She/Her/Hers) Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [image: www.facebook.com/IHRCA] [image: https://twitter.com/yarchives] -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Wed Sep 12 10:47:04 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 12 Sep 2018 14:47:04 +0000 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 In-Reply-To: References: , Message-ID: We had this problem at Denver and resolved it by installing the and_search plugin (https://github.com/hudmol/and_search) to change Solr's default Boolean operator to 'and'. I think (but am not 100% certain) that this is the default in 2.5.0. -k [https://avatars2.githubusercontent.com/u/1821448?s=400&v=4] GitHub - hudmol/and_search: An ArchivesSpace plugin that ... github.com GitHub is where people build software. More than 28 million people use GitHub to discover, fork, and contribute to over 85 million projects. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Lara Friedman-Shedlov Sent: Wednesday, September 12, 2018 8:34:21 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 Yes, that's the same issue. We've been having it here at the University of Minnesota as well. Reindexing did not solve the issue. On Wed, Sep 12, 2018 at 9:30 AM Blake Carver > wrote: Is this the same issue? https://archivesspace.atlassian.net/browse/ANW-762 ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Olivia S Solis > Sent: Wednesday, September 12, 2018 9:54:33 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 Hello all, We have been having a problem with the auto-complete suggestions for linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always present relevant suggestions. For example, we have an existing corporate agent, "Texas Federation of Music Clubs." When I try to add the agent, it presents the following: [Screen Shot 2018-08-31 at 2.41.48 PM.png] So it is pulling suggestions from the family agents. Similarly, we have an agent person "Smith, Liz, 1923-2017." It does not present her as an option unless we type ", " after her name. Someone who wants to add her, though, won't necessarily know that she's got a date addition. Again it pulls from family agents. [Screen Shot 2018-09-12 at 8.44.48 AM.png] [Screen Shot 2018-09-12 at 8.44.59 AM.png] This what the suggestions looked like in 1.5.3 for us: [Screen Shot 2018-08-31 at 3.49.41 PM.png] [image.png] Has anyone else had a problem with this? Trying to figure out if this is an issue with 2.4.1 or with our data. Perhaps we've got something configured incorrectly in our settings? We've already tried re-indexing, but that did not help. Any suggestions would be great! 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 -- _________________________________ Lara D. Friedman-Shedlov (She/Her/Hers) Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [www.facebook.com/IHRCA] [https://twitter.com/yarchives] -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Wed Sep 12 10:51:59 2018 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Wed, 12 Sep 2018 10:51:59 -0400 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 In-Reply-To: References: Message-ID: I think that this is related to the issue discussed in this thread: http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2018-February/005664.html which I believe started happening in version 2.3. The 'AND' search (which does look to be the default in 2.5 as Kevin said) is one solution and may be good enough. We opted to modify the default search parameters to boost matches on the title field. This can now be done via the config and there are instructions on how to do it in the comments: https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L81 On Wed, Sep 12, 2018 at 10:34 AM Lara Friedman-Shedlov wrote: > Yes, that's the same issue. We've been having it here at the University > of Minnesota as well. Reindexing did not solve the issue. > > On Wed, Sep 12, 2018 at 9:30 AM Blake Carver > wrote: > >> Is this the same issue? >> >> https://archivesspace.atlassian.net/browse/ANW-762 >> >> ________________________________________ >> 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, September 12, 2018 9:54:33 AM >> To: Archivesspace Users Group >> Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 >> >> Hello all, >> >> We have been having a problem with the auto-complete suggestions for >> linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always >> present relevant suggestions. For example, we have an existing corporate >> agent, "Texas Federation of Music Clubs." When I try to add the agent, it >> presents the following: >> >> [Screen Shot 2018-08-31 at 2.41.48 PM.png] >> >> So it is pulling suggestions from the family agents. Similarly, we have >> an agent person "Smith, Liz, 1923-2017." It does not present her as an >> option unless we type ", " after her name. Someone who wants to add her, >> though, won't necessarily know that she's got a date addition. Again it >> pulls from family agents. >> [Screen Shot 2018-09-12 at 8.44.48 AM.png] >> [Screen Shot 2018-09-12 at 8.44.59 AM.png] >> >> This what the suggestions looked like in 1.5.3 for us: >> [Screen Shot 2018-08-31 at 3.49.41 PM.png] >> [image.png] >> >> Has anyone else had a problem with this? Trying to figure out if this is >> an issue with 2.4.1 or with our data. Perhaps we've got something >> configured incorrectly in our settings? >> >> We've already tried re-indexing, but that did not help. >> >> Any suggestions would be great! >> >> 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 >> > > > -- > _________________________________ > > Lara D. Friedman-Shedlov (She/Her/Hers) > Kautz Family YMCA Archives | University of > Minnesota Libraries > ldfs at umn.edu | 612.626.7972 | > > [image: www.facebook.com/IHRCA] [image: > https://twitter.com/yarchives] > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhughes at library.ucla.edu Wed Sep 12 12:05:56 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Wed, 12 Sep 2018 16:05:56 +0000 Subject: [Archivesspace_Users_Group] Viewing suppressed records permission Message-ID: Hi all, We're having trouble with the "view suppressed records in this repository" permission. I've recreated it in the sandbox and have attached screenshots here. Here are my steps: 1. I edited the Archivists of the test repository group to give them permission to both suppress the major record types and view suppressed records. 2. I created another user called "other user" and added them to the Archivists group. (see screenshot) 3. I created a resource called "testing suppression". 4. Logged in as "other user" I suppressed the "testing suppression" resource. 5. I got an error message saying I no longer had permission to view the record. 6. I searched for "testing suppression" and no search results display (still logged in as "other user"). (see screenshot) 7. I logged in as admin and searched for "test suppression" and the suppressed in included in search results. (see screenshot) Are there any other dependent permissions that needs to be enabled that could be blocking the ability to view suppressed records? Am I missing something? I know there have been other conversations about suppression being buggy - I actually was not able to un-suppress the test resource and crashed the sandbox when I tried. I searched quickly for a JIRA ticket and didn't see this issue. Are institutions successfully using the suppress records functionality? Thanks for your help! Maggie ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: grouppermissions_suppressed.JPG Type: image/jpeg Size: 97248 bytes Desc: grouppermissions_suppressed.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: admin_SA_suppression.JPG Type: image/jpeg Size: 79812 bytes Desc: admin_SA_suppression.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: otheruser_nonSA_suppression.JPG Type: image/jpeg Size: 64380 bytes Desc: otheruser_nonSA_suppression.JPG URL: From powers at tulane.edu Wed Sep 12 10:46:33 2018 From: powers at tulane.edu (Powers, Susanna S) Date: Wed, 12 Sep 2018 14:46:33 +0000 Subject: [Archivesspace_Users_Group] unsubscribe request Message-ID: unsubscribe Susanna Powers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Wed Sep 12 17:15:01 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 12 Sep 2018 21:15:01 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 Message-ID: ArchivesSpace Implementation Buddies When: Wednesday, September 26, 2018 Time: 1:00 p.m. - 1:30 p.m. EST (10:00 a.m. - 10:30 a.m. PST) Where: Webinar at https://zoom.us/j/834400938 Dial-in only option: 669-900-6833 or 646-876-9923 - Meeting ID is 834-400-938 International numbers available: https://zoom.us/u/iZNgWlhI No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Please note: We are using Zoom Video Communications to host this webinar, taking a break from Adobe Connect temporarily. If this is your first time using Zoom, please join this Test meeting to make sure you are all set up: https://zoom.us/test Webinar description: At our Annual Member Forum, we announced our idea to facilitate an "implementation buddy" program to help connect our ArchivesSpace community members so we can work through challenges together. We shared our thoughts on how stepping up as a mentor comes with the expectations that may exceed the bandwidth that most of our extremely busy community currently may have. Our vision for "implementation buddies" aims to lift that burden of mentorship while connecting members who can help each other out in balanced harmony. We are offering a webinar on September 26 at 1-1:30pm ET (10-10:30am PT) to provide a background on the ASpace Implementation Buddy program as well as a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form (link to announcement) and the Implementation Buddy sign-up sheet. Please feel free to bring any questions you have. Presenters: Christine Kim (Community Engagement Coordinator, ArchivesSpace) is responsible for facilitating community activities, and is inspired by the incredible projects, initiatives, and accomplishments of the ASpace community. Who should attend: Everyone interested in learning about the ArchivesSpace implementation buddy program, as well as anyone who wants a deeper look at the member directory submission form. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From bzhang at csus.edu Wed Sep 12 17:29:57 2018 From: bzhang at csus.edu (Zhang, Bin) Date: Wed, 12 Sep 2018 21:29:57 +0000 Subject: [Archivesspace_Users_Group] Moving AS to another server? Message-ID: <5829E7A3-D04B-4588-B519-C67D41CE3203@csus.edu> I am trying to find out the steps needed to move an AS instance from one server to another. Both servers are running the same OS (ubuntu 16.04 LTS) and will be pointing to the same mysql server. I tried just copy the whole archivesspace directory over. I changed hostnames in the config.rb file. Is there anything else I need to do before starting AS? When I started archivesspace.sh, and went to the site url, I got this in the browser: Internal Server Error (500) Request Method: GET Request URL: http://hostname.domain:8080/ load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11:in `(root)' from /data/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1:in `(root)' from /data/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:168:in `main' from launcher/launcher.rb:261:in `
' You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. Any idea what went wrong? Thanks! Bin Zhang California State University, Sacramento -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Sep 12 18:07:11 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 12 Sep 2018 22:07:11 +0000 Subject: [Archivesspace_Users_Group] Moving AS to another server? In-Reply-To: <5829E7A3-D04B-4588-B519-C67D41CE3203@csus.edu> References: <5829E7A3-D04B-4588-B519-C67D41CE3203@csus.edu> Message-ID: You should check the logs/archivesspace.out log file when you start server to see if it starts up without error. Error message from startup may more clearly point to the problem ? error message from failed GET is already another step removed from the original problem. You might also look at file ownership and permissions in archivesspace/data/ and elsewhere. If you?ve copied file tree from one server to another, owner of that temp directory may be different from user who is running new archivesspace. If you don?t find anything obviously wrong, starting from a clean install and just copying the config.rb file from old to new server may be easier and keep things more consistent. ? Steve Majewski > On Sep 12, 2018, at 5:29 PM, Zhang, Bin wrote: > > I am trying to find out the steps needed to move an AS instance from one server to another. Both servers are running the same OS (ubuntu 16.04 LTS) and will be pointing to the same mysql server. I tried just copy the whole archivesspace directory over. I changed hostnames in the config.rb file. Is there anything else I need to do before starting AS? When I started archivesspace.sh, and went to the site url, I got this in the browser: > > Internal Server Error (500) > Request Method: > GET > Request URL: > http://hostname.domain:8080/ > load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11:in `(root)' from /data/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1:in `(root)' from /data/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:168:in `main' from launcher/launcher.rb:261:in `
' > You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. > > Any idea what went wrong? > > Thanks! > Bin Zhang > California State University, Sacramento > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From livsolis at utexas.edu Wed Sep 12 18:57:31 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 12 Sep 2018 17:57:31 -0500 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 In-Reply-To: References: Message-ID: Thank you all for the feedback and validation! I suppose I'm relieved to know that their is nothing inherently wrong with our particular configuration or data. I should have checked the user group before posting, but thank you all for pointing us in the right direction! -Olivia On Wed, Sep 12, 2018 at 9:52 AM Trevor Thornton wrote: > I think that this is related to the issue discussed in this thread: > > http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2018-February/005664.html > which I believe started happening in version 2.3. > > The 'AND' search (which does look to be the default in 2.5 as Kevin said) > is one solution and may be good enough. We opted to modify the default > search parameters to boost matches on the title field. This can now be done > via the config and there are instructions on how to do it in the comments: > > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L81 > > On Wed, Sep 12, 2018 at 10:34 AM Lara Friedman-Shedlov > wrote: > >> Yes, that's the same issue. We've been having it here at the University >> of Minnesota as well. Reindexing did not solve the issue. >> >> On Wed, Sep 12, 2018 at 9:30 AM Blake Carver >> wrote: >> >>> Is this the same issue? >>> >>> https://archivesspace.atlassian.net/browse/ANW-762 >>> >>> ________________________________________ >>> 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, September 12, 2018 9:54:33 AM >>> To: Archivesspace Users Group >>> Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 >>> >>> Hello all, >>> >>> We have been having a problem with the auto-complete suggestions for >>> linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always >>> present relevant suggestions. For example, we have an existing corporate >>> agent, "Texas Federation of Music Clubs." When I try to add the agent, it >>> presents the following: >>> >>> [Screen Shot 2018-08-31 at 2.41.48 PM.png] >>> >>> So it is pulling suggestions from the family agents. Similarly, we have >>> an agent person "Smith, Liz, 1923-2017." It does not present her as an >>> option unless we type ", " after her name. Someone who wants to add her, >>> though, won't necessarily know that she's got a date addition. Again it >>> pulls from family agents. >>> [Screen Shot 2018-09-12 at 8.44.48 AM.png] >>> [Screen Shot 2018-09-12 at 8.44.59 AM.png] >>> >>> This what the suggestions looked like in 1.5.3 for us: >>> [Screen Shot 2018-08-31 at 3.49.41 PM.png] >>> [image.png] >>> >>> Has anyone else had a problem with this? Trying to figure out if this is >>> an issue with 2.4.1 or with our data. Perhaps we've got something >>> configured incorrectly in our settings? >>> >>> We've already tried re-indexing, but that did not help. >>> >>> Any suggestions would be great! >>> >>> 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 >>> >> >> >> -- >> _________________________________ >> >> Lara D. Friedman-Shedlov (She/Her/Hers) >> Kautz Family YMCA Archives | University of >> Minnesota Libraries >> ldfs at umn.edu | 612.626.7972 | >> >> [image: www.facebook.com/IHRCA] [image: >> https://twitter.com/yarchives] >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Trevor Thornton > Applications Developer, Digital Library Initiatives > North Carolina State University Libraries > _______________________________________________ > 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 KennedyN at si.edu Thu Sep 13 08:20:33 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Thu, 13 Sep 2018 12:20:33 +0000 Subject: [Archivesspace_Users_Group] Publish All workflows Message-ID: Hello all, We have had a few cases where users hit the 'Publish All' button for collections containing 'internal' archival_objects or notes (i.e. where the EAD @audience is "internal"). I wonder how other institutions handle collections with 'internal' content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. In our situation, an ideal solution would be to separate 'publish' into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if 'Publish?' vs 'Audience?' could be separate elements, so that I can protect internal audience material from publishing. What do you all think? Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Thu Sep 13 09:10:04 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Thu, 13 Sep 2018 13:10:04 +0000 Subject: [Archivesspace_Users_Group] Publish All workflows In-Reply-To: References: Message-ID: Hi Nancy, We ran into a similar problem to the one you describe-folks accidentally clicking "publish all" when a resource record contained some archival objects that should remain unpublished. To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking "publish all." We also have some scripts that batch export EADs and publish all at the same time. Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding. This isn't a fail-proof solution, but has helped mitigate the problem of publishing things we didn't intend to publish. We're also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD. RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.). That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another. I'm also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kennedy, Nancy Sent: Thursday, September 13, 2018 8:21 AM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Publish All workflows Hello all, We have had a few cases where users hit the 'Publish All' button for collections containing 'internal' archival_objects or notes (i.e. where the EAD @audience is "internal"). I wonder how other institutions handle collections with 'internal' content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. In our situation, an ideal solution would be to separate 'publish' into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if 'Publish?' vs 'Audience?' could be separate elements, so that I can protect internal audience material from publishing. What do you all think? Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bthomas at tsl.texas.gov Thu Sep 13 09:22:07 2018 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Thu, 13 Sep 2018 13:22:07 +0000 Subject: [Archivesspace_Users_Group] Publish All workflows In-Reply-To: References: Message-ID: Hi all, I cannot speak to Noah's questions re how to keep track of published vs. unpublished elements as I am more on the techy side here in electronic records v. the processing side. But I wanted to voice an agreement with Nancy that having an internal audience only checkbox that blocks publication would be a good enhancement. That way one can in a fell swoop still publish all things intended for the public, without having to go back and unpublish all the things that should not have been. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Noah Huffman Sent: Thursday, September 13, 2018 8:10 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Publish All workflows Hi Nancy, We ran into a similar problem to the one you describe-folks accidentally clicking "publish all" when a resource record contained some archival objects that should remain unpublished. To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking "publish all." We also have some scripts that batch export EADs and publish all at the same time. Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding. This isn't a fail-proof solution, but has helped mitigate the problem of publishing things we didn't intend to publish. We're also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD. RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.). That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another. I'm also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Kennedy, Nancy Sent: Thursday, September 13, 2018 8:21 AM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) > Subject: [Archivesspace_Users_Group] Publish All workflows Hello all, We have had a few cases where users hit the 'Publish All' button for collections containing 'internal' archival_objects or notes (i.e. where the EAD @audience is "internal"). I wonder how other institutions handle collections with 'internal' content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. In our situation, an ideal solution would be to separate 'publish' into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if 'Publish?' vs 'Audience?' could be separate elements, so that I can protect internal audience material from publishing. What do you all think? Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From KennedyN at si.edu Thu Sep 13 09:54:45 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Thu, 13 Sep 2018 13:54:45 +0000 Subject: [Archivesspace_Users_Group] Publish All workflows In-Reply-To: References: Message-ID: Thanks, Noah, Brian. Noah - re: "we keep track of the publication status of a finding aid using the Finding Aid Status field" . We do the same thing, using Finding Aid Status to drive the EAD export. Using FA Status has worked pretty well... except that screen labels like "publish?" leads to some (I'd say legitimately!) confused users. Especially when there is, say, a network slow down and people try to troubleshoot by clicking on lots of inviting buttons... like "publish all". We try to train everyone on what "Publish?" checkbox means, but it's easy to confuse. I've considered relabeling the ''Publish?" field to something like 'External Audience' ... but I don't want to move us far afield form the core archivesspace code/documentation. If I change the display label, my users will understand that we mean audience and not status . The problem is changing labels means our views will drift away from the main core archivesspace documentation, screencasts etc. And the term 'publish" appears in many places. Label translation seems like a band aid (and not a very good one). A 2nd element specific to audience would probably be much better than a label change. Nancy From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Brian Thomas Sent: Thursday, September 13, 2018 9:22 AM To: 'Archivesspace Users Group' Subject: Re: [Archivesspace_Users_Group] Publish All workflows Hi all, I cannot speak to Noah's questions re how to keep track of published vs. unpublished elements as I am more on the techy side here in electronic records v. the processing side. But I wanted to voice an agreement with Nancy that having an internal audience only checkbox that blocks publication would be a good enhancement. That way one can in a fell swoop still publish all things intended for the public, without having to go back and unpublish all the things that should not have been. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Noah Huffman Sent: Thursday, September 13, 2018 8:10 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Publish All workflows Hi Nancy, We ran into a similar problem to the one you describe-folks accidentally clicking "publish all" when a resource record contained some archival objects that should remain unpublished. To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking "publish all." We also have some scripts that batch export EADs and publish all at the same time. Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding. This isn't a fail-proof solution, but has helped mitigate the problem of publishing things we didn't intend to publish. We're also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD. RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.). That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another. I'm also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Kennedy, Nancy Sent: Thursday, September 13, 2018 8:21 AM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) > Subject: [Archivesspace_Users_Group] Publish All workflows Hello all, We have had a few cases where users hit the 'Publish All' button for collections containing 'internal' archival_objects or notes (i.e. where the EAD @audience is "internal"). I wonder how other institutions handle collections with 'internal' content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. In our situation, an ideal solution would be to separate 'publish' into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if 'Publish?' vs 'Audience?' could be separate elements, so that I can protect internal audience material from publishing. What do you all think? Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From k-miller3 at northwestern.edu Thu Sep 13 11:11:59 2018 From: k-miller3 at northwestern.edu (Karen Miller) Date: Thu, 13 Sep 2018 15:11:59 +0000 Subject: [Archivesspace_Users_Group] Publish All workflows In-Reply-To: References: Message-ID: We've addressed this by querying the backend for a Resource before clicking the "Publish All" button. The following SQL code has been embedded into an Excel worksheet with prompt for the Resource Identifier ( WHERE T8.root_record_id=?) and then displays a list of archival object unittitles with a Publish? status of 1 for published, 0 for unpublished. You could certainly just drop in the resource identifier in the SQL below. I can provide more information about how I set this up in Excel offline if anyone's interested. SELECT CONCAT(T9.value, " ", T6.indicator) AS `Container`, T8.component_id AS `Level`, T8.display_string AS `Component Title`, T8.publish AS `Publish?` FROM archivesspace.archival_object T8 LEFT OUTER JOIN archivesspace.instance T1 ON T1.archival_object_id=T8.id LEFT JOIN archivesspace.sub_container T2 ON T1.id = T2.instance_id LEFT JOIN archivesspace.top_container_link_rlshp T3 ON T2.id = T3.sub_container_id LEFT OUTER JOIN archivesspace.top_container T6 ON T3.top_container_id = T6.id LEFT JOIN archivesspace.top_container_housed_at_rlshp T4 ON T4.top_container_id = T6.id LEFT JOIN archivesspace.location T5 ON T4.location_id = T5.id LEFT JOIN archivesspace.enumeration_value T9 ON T6.type_id=T9.id WHERE T8.root_record_id=? ORDER by T8.publish, T9.value, T8.component_id ASC Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kennedy, Nancy Sent: Thursday, September 13, 2018 8:55 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Publish All workflows Thanks, Noah, Brian. Noah - re: "we keep track of the publication status of a finding aid using the Finding Aid Status field" . We do the same thing, using Finding Aid Status to drive the EAD export. Using FA Status has worked pretty well... except that screen labels like "publish?" leads to some (I'd say legitimately!) confused users. Especially when there is, say, a network slow down and people try to troubleshoot by clicking on lots of inviting buttons... like "publish all". We try to train everyone on what "Publish?" checkbox means, but it's easy to confuse. I've considered relabeling the ''Publish?" field to something like 'External Audience' ... but I don't want to move us far afield form the core archivesspace code/documentation. If I change the display label, my users will understand that we mean audience and not status . The problem is changing labels means our views will drift away from the main core archivesspace documentation, screencasts etc. And the term 'publish" appears in many places. Label translation seems like a band aid (and not a very good one). A 2nd element specific to audience would probably be much better than a label change. Nancy From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Brian Thomas Sent: Thursday, September 13, 2018 9:22 AM To: 'Archivesspace Users Group' > Subject: Re: [Archivesspace_Users_Group] Publish All workflows Hi all, I cannot speak to Noah's questions re how to keep track of published vs. unpublished elements as I am more on the techy side here in electronic records v. the processing side. But I wanted to voice an agreement with Nancy that having an internal audience only checkbox that blocks publication would be a good enhancement. That way one can in a fell swoop still publish all things intended for the public, without having to go back and unpublish all the things that should not have been. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Noah Huffman Sent: Thursday, September 13, 2018 8:10 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Publish All workflows Hi Nancy, We ran into a similar problem to the one you describe-folks accidentally clicking "publish all" when a resource record contained some archival objects that should remain unpublished. To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking "publish all." We also have some scripts that batch export EADs and publish all at the same time. Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding. This isn't a fail-proof solution, but has helped mitigate the problem of publishing things we didn't intend to publish. We're also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD. RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.). That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another. I'm also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Kennedy, Nancy Sent: Thursday, September 13, 2018 8:21 AM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) > Subject: [Archivesspace_Users_Group] Publish All workflows Hello all, We have had a few cases where users hit the 'Publish All' button for collections containing 'internal' archival_objects or notes (i.e. where the EAD @audience is "internal"). I wonder how other institutions handle collections with 'internal' content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. In our situation, an ideal solution would be to separate 'publish' into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if 'Publish?' vs 'Audience?' could be separate elements, so that I can protect internal audience material from publishing. What do you all think? Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From sdm7g at virginia.edu Thu Sep 13 11:27:56 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 13 Sep 2018 15:27:56 +0000 Subject: [Archivesspace_Users_Group] Publish All workflows In-Reply-To: References: Message-ID: <1810ADDF-5FAE-40FE-86F9-D1266EED4234@virginia.edu> Yes: I think publish/publish-all was a design error that has caused much confusion for users. First, ?publish? is a verb that?s being used as an attribute. It should have been ?public? . And the ?publish all? button, which is a verb, just made if more confusing. In most cases, for most libraries, public is a better default. If public was the default and the checkbox was ?internal? , there would be less need for a button to change the status of all children to ?publish? . ( Maybe there is a way to make the defaults for different records configurable, or make the defaults for different kinds of notes different. ) But there is still a use case for a ?publish? (as a verb) button, that would trigger PUI indexing and perhaps some other actions. As it works currently, incomplete records that are correctly marked to be public go out to the PUI and OAI endpoints. Changing the finding aid status to complete does not trigger any action. So perhaps there should be a ?publish? button that changes finding aid status, creates an event record that indicates that the resource was published, and triggers PUI indexing. ? Steve Majewski > On Sep 13, 2018, at 9:54 AM, Kennedy, Nancy wrote: > > Thanks, Noah, Brian. > > Noah ? re: ?we keep track of the publication status of a finding aid using the Finding Aid Status field? . We do the same thing, using Finding Aid Status to drive the EAD export. > > Using FA Status has worked pretty well? except that screen labels like ?publish?? leads to some (I?d say legitimately!) confused users. Especially when there is, say, a network slow down and people try to troubleshoot by clicking on lots of inviting buttons? like ?publish all?. We try to train everyone on what ?Publish?? checkbox means, but it?s easy to confuse. > > I?ve considered relabeling the ??Publish?? field to something like ?External Audience? ? but I don?t want to move us far afield form the core archivesspace code/documentation. If I change the display label, my users will understand that we mean audience and not status . The problem is changing labels means our views will drift away from the main core archivesspace documentation, screencasts etc. And the term ?publish? appears in many places. Label translation seems like a band aid (and not a very good one). A 2nd element specific to audience would probably be much better than a label change. > > Nancy > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Brian Thomas > Sent: Thursday, September 13, 2018 9:22 AM > To: 'Archivesspace Users Group' > Subject: Re: [Archivesspace_Users_Group] Publish All workflows > > Hi all, > I cannot speak to Noah?s questions re how to keep track of published vs. unpublished elements as I am more on the techy side here in electronic records v. the processing side. But I wanted to voice an agreement with Nancy that having an internal audience only checkbox that blocks publication would be a good enhancement. That way one can in a fell swoop still publish all things intended for the public, without having to go back and unpublish all the things that should not have been. > Thanks, > > Brian Thomas > Electronic Records Specialist > Texas State Library and Archives Commission > 1201 Brazos Street > Austin, TX 78701 > PH: (512) 475-3374 > e-mail: bthomas at tsl.texas.gov > tsl.texas.gov > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Noah Huffman > Sent: Thursday, September 13, 2018 8:10 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Publish All workflows > > Hi Nancy, > > We ran into a similar problem to the one you describe?folks accidentally clicking ?publish all? when a resource record contained some archival objects that should remain unpublished. > > To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking ?publish all.? We also have some scripts that batch export EADs and publish all at the same time. Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding. This isn?t a fail-proof solution, but has helped mitigate the problem of publishing things we didn?t intend to publish. We?re also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD. > > RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.). That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another. > > I?m also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource. > > -Noah > > ================ > Noah Huffman > Archivist for Metadata, Systems, and Digital Records > David M. Rubenstein Rare Book & Manuscript Library > Duke University | 919-660-5982 > http://library.duke.edu/rubenstein/ > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Kennedy, Nancy > Sent: Thursday, September 13, 2018 8:21 AM > To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org ) > > Subject: [Archivesspace_Users_Group] Publish All workflows > > Hello all, > We have had a few cases where users hit the ?Publish All? button for collections containing ?internal? archival_objects or notes (i.e. where the EAD @audience is ?internal?). > > I wonder how other institutions handle collections with ?internal? content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. > > In our situation, an ideal solution would be to separate ?publish? into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if ?Publish?? vs ?Audience?? could be separate elements, so that I can protect internal audience material from publishing. > > What do you all think? > > Nancy > > > Nancy Kennedy > Smithsonian Institution > kennedyn at si.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From PGalligan at rockarch.org Fri Sep 14 10:54:55 2018 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Fri, 14 Sep 2018 14:54:55 +0000 Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Message-ID: <1EC17990-1D8C-4034-B670-0A2C6997ABAC@rockarch.org> Hi all, I?m testing out version 2.5.0 and I?m noticing that I can?t ?Edit Groups? for some members under the ?Manage User Access? page. I am logged in as an admin user, and logging in as a different admin user doesn?t help. I also checked on the sandbox.archivesspace.org installation and noticed that the one user available can?t edit their own groups either. Anyone else seeing this? Thanks, Patrick Galligan -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Sep 14 11:12:07 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 14 Sep 2018 15:12:07 +0000 Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 In-Reply-To: <1EC17990-1D8C-4034-B670-0A2C6997ABAC@rockarch.org> References: <1EC17990-1D8C-4034-B670-0A2C6997ABAC@rockarch.org> Message-ID: I do see that same thing under 2.4.1 as well. I have the same DB running under 2.5 and 2.41 and I can't touch the same users in both versions. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Friday, September 14, 2018 10:54:55 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Hi all, I?m testing out version 2.5.0 and I?m noticing that I can?t ?Edit Groups? for some members under the ?Manage User Access? page. I am logged in as an admin user, and logging in as a different admin user doesn?t help. I also checked on the sandbox.archivesspace.org installation and noticed that the one user available can?t edit their own groups either. Anyone else seeing this? Thanks, Patrick Galligan From PGalligan at rockarch.org Fri Sep 14 11:18:50 2018 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Fri, 14 Sep 2018 15:18:50 +0000 Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Message-ID: Blake, Interesting. We?re still on 2.3.2 on production, and we were going to skip 2.4 entirely, so I haven?t done any testing on those versions. I should have attached a screenshot, so I have now. Any insight on why this might be happening? -Patrick On 9/14/18, 11:12 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver" wrote: I do see that same thing under 2.4.1 as well. I have the same DB running under 2.5 and 2.41 and I can't touch the same users in both versions. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Friday, September 14, 2018 10:54:55 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Hi all, I?m testing out version 2.5.0 and I?m noticing that I can?t ?Edit Groups? for some members under the ?Manage User Access? page. I am logged in as an admin user, and logging in as a different admin user doesn?t help. I also checked on the sandbox.archivesspace.org installation and noticed that the one user available can?t edit their own groups either. Anyone else seeing this? Thanks, Patrick Galligan _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-14 at 11.02.46 AM.png Type: image/png Size: 52419 bytes Desc: Screen Shot 2018-09-14 at 11.02.46 AM.png URL: From christine.dibella at lyrasis.org Fri Sep 14 11:24:11 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 14 Sep 2018 15:24:11 +0000 Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 In-Reply-To: References: Message-ID: Hi Patrick and Blake, If a user has the ?Grant system administrator permissions? checked in their user record, even an admin cannot edit groups for them from the Manage User Access page. (Because they have access to everything already.) You?d need to remove that permission from their record in Manage Users, then Edit Groups. Hopefully that's it, but if not, are there common characteristics of these users? Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Galligan, Patrick Sent: Friday, September 14, 2018 11:19 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Blake, Interesting. We?re still on 2.3.2 on production, and we were going to skip 2.4 entirely, so I haven?t done any testing on those versions. I should have attached a screenshot, so I have now. Any insight on why this might be happening? -Patrick On 9/14/18, 11:12 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver" wrote: I do see that same thing under 2.4.1 as well. I have the same DB running under 2.5 and 2.41 and I can't touch the same users in both versions. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Friday, September 14, 2018 10:54:55 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Hi all, I?m testing out version 2.5.0 and I?m noticing that I can?t ?Edit Groups? for some members under the ?Manage User Access? page. I am logged in as an admin user, and logging in as a different admin user doesn?t help. I also checked on the sandbox.archivesspace.org installation and noticed that the one user available can?t edit their own groups either. Anyone else seeing this? Thanks, Patrick Galligan _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From djpillen at umich.edu Fri Sep 14 11:29:14 2018 From: djpillen at umich.edu (Dallas Pillen) Date: Fri, 14 Sep 2018 11:29:14 -0400 Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 In-Reply-To: References: Message-ID: Hi Patrick, Are the only users for which you are unable to "Edit groups" other administrators? If so, it looks like this was a change introduced by this pull request: https://github.com/archivesspace/archivesspace/commit/29bd91135626fb6a911bf65269167f6a9c4d79cd#diff-a3896310fef308a3755090d3590e0ce7 >From the commit message: "Prevents group assignment for 'admin' users. They already have all the privileges so groups are unnecessary, but this prevents a side effect where an 'admin' user (including the global admin) can lose admin group permissions if they are assigned to a group by another admin level user." On Fri, Sep 14, 2018 at 11:18 AM, Galligan, Patrick wrote: > Blake, > > Interesting. We?re still on 2.3.2 on production, and we were going to skip > 2.4 entirely, so I haven?t done any testing on those versions. > > I should have attached a screenshot, so I have now. Any insight on why > this might be happening? > > -Patrick > > On 9/14/18, 11:12 AM, "archivesspace_users_group- > bounces at lyralists.lyrasis.org on behalf of Blake Carver" < > archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of > blake.carver at lyrasis.org> wrote: > > I do see that same thing under 2.4.1 as well. I have the same DB > running under 2.5 and 2.41 and I can't touch the same users in both > versions. > > ________________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Galligan, Patrick > Sent: Friday, September 14, 2018 10:54:55 AM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 > > Hi all, > > I?m testing out version 2.5.0 and I?m noticing that I can?t ?Edit > Groups? for some members under the ?Manage User Access? page. I am logged > in as an admin user, and logging in as a different admin user doesn?t help. > > I also checked on the sandbox.archivesspace.org installation and > noticed that the one user available can?t edit their own groups either. > > Anyone else seeing this? > > Thanks, > Patrick Galligan > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/ > archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Dallas Pillen*Archivist for Metadata and Digital Projects Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Sep 14 11:41:46 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 14 Sep 2018 15:41:46 +0000 Subject: [Archivesspace_Users_Group] MARC export in v 2.5 In-Reply-To: References: Message-ID: Hi Sue, Updates to the MARCXML export have been included in several recent releases of ArchivesSpace. These changes have been the result of an updated mapping and individual issues submitted by ArchivesSpace community members and went through the review and testing process. One of the additions was including relators for agents when there is a value in the relator field. That said, supplying a value of "subject" for agents with a role of subject when there is no relator is not intended behavior and we'll get that bug fixed for the next release. More generally, to explain a little more about how the exports work, we maintain one mapping for each, with the intent that it covers broadly agreed upon needs. More specific needs can be accommodated locally via either the use of a custom export plugin or processing the MARCXML with stylesheets or macros outside of ArchivesSpace. Besides changing appearance things like colors and logos, this is probably one of the most common types of customizations people make to the staff interface. So I know people here are likely to have lots of great examples of how they're doing this, but we can provide some more specific guidance on that too. 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 Susan Luftschein Sent: Tuesday, September 11, 2018 6:32 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] MARC export in v 2.5 HI all, We just upgraded to 2.5 and I am seeing some interesting things happening in the MARC export. First, a subfield b is being added to the 041, and subfield e is being added to 600 and 610 fields. Is there any way to turn these off? The relator term "subject" in a 6xx field seems rather redundant. Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From PGalligan at rockarch.org Mon Sep 17 09:09:13 2018 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 17 Sep 2018 13:09:13 +0000 Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 In-Reply-To: References: Message-ID: <3F008602-D63E-4B26-AA6E-F1A35E2218D3@rockarch.org> Yeah, that looks like it. Thanks for pointing me in the right direction! Just noticed it and wanted to make sure it was expected! From: on behalf of Dallas Pillen Reply-To: Archivesspace Users Group Date: Friday, September 14, 2018 at 11:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Hi Patrick, Are the only users for which you are unable to "Edit groups" other administrators? If so, it looks like this was a change introduced by this pull request: https://github.com/archivesspace/archivesspace/commit/29bd91135626fb6a911bf65269167f6a9c4d79cd#diff-a3896310fef308a3755090d3590e0ce7 From the commit message: "Prevents group assignment for 'admin' users. They already have all the privileges so groups are unnecessary, but this prevents a side effect where an 'admin' user (including the global admin) can lose admin group permissions if they are assigned to a group by another admin level user." On Fri, Sep 14, 2018 at 11:18 AM, Galligan, Patrick > wrote: Blake, Interesting. We?re still on 2.3.2 on production, and we were going to skip 2.4 entirely, so I haven?t done any testing on those versions. I should have attached a screenshot, so I have now. Any insight on why this might be happening? -Patrick On 9/14/18, 11:12 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver" on behalf of blake.carver at lyrasis.org> wrote: I do see that same thing under 2.4.1 as well. I have the same DB running under 2.5 and 2.41 and I can't touch the same users in both versions. ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Galligan, Patrick > Sent: Friday, September 14, 2018 10:54:55 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0 Hi all, I?m testing out version 2.5.0 and I?m noticing that I can?t ?Edit Groups? for some members under the ?Manage User Access? page. I am logged in as an admin user, and logging in as a different admin user doesn?t help. I also checked on the sandbox.archivesspace.org installation and noticed that the one user available can?t edit their own groups either. Anyone else seeing this? Thanks, Patrick Galligan _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcarll at radcliffe.harvard.edu Mon Sep 17 09:32:40 2018 From: jcarll at radcliffe.harvard.edu (Carll, Johanna) Date: Mon, 17 Sep 2018 13:32:40 +0000 Subject: [Archivesspace_Users_Group] PUI search functionality documentation Message-ID: Dear Christine, Now that we have had a few months of experience with the ArchivesSpace PUI here at Harvard, we are reviewing user feedback to help us prioritize post-launch development needs. One area of concern is the PUI search functionality, as we've received multiple reports of unsatisfactory and unexpected search results. Can you direct us to - or share - documentation on the PUI search functionality, including relevance ranking, weighting, and indexed fields? This will help us evaluate what may be done locally to improve results, as well as participate in the discussion and planning for changes to the core code that would improve search results. Thanks Johanna Johanna Carll Archivist and Metadata Specialist Schlesinger Library Radcliffe Institute for Advanced Study Harvard University 10 Garden Street Cambridge, MA 02138 617-495-8524 jcarll at radcliffe.harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Mon Sep 17 13:06:52 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 17 Sep 2018 17:06:52 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Message-ID: <34F5E82E-D81C-42CA-A148-7692DBAF97AE@lib.msu.edu> Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 -------------- next part -------------- A non-text attachment was scrubbed... Name: Multi Series CUI Top Containers.png Type: image/png Size: 32519 bytes Desc: Multi Series CUI Top Containers.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Series label and free text.png Type: image/png Size: 99436 bytes Desc: Series label and free text.png URL: From ltang5 at lib.msu.edu Mon Sep 17 13:31:47 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 17 Sep 2018 17:31:47 +0000 Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 In-Reply-To: References: Message-ID: <794BFEA1-0AF1-4923-A3D9-181C8E793CE7@lib.msu.edu> Hi again, Dev. Pri. has this ticket on our next meeting later this month. If anyone has additional comments for the ticket, please feel free to add it! https://archivesspace.atlassian.net/browse/ANW-762 Lydia Chair, Development Prioritization subteam ?On 9/12/18, 10:30 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver" wrote: Is this the same issue? https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D762&d=DwIFAg&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=UGQX00RY1bhZvTYQZVCzZljyHsOqXl9h456hV5cKkx0&s=a3NA9S9rgzKuiLZ38r4J73kKR4UetSDWTPHGQGWVRTg&e= ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Olivia S Solis Sent: Wednesday, September 12, 2018 9:54:33 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1 Hello all, We have been having a problem with the auto-complete suggestions for linked agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always present relevant suggestions. For example, we have an existing corporate agent, "Texas Federation of Music Clubs." When I try to add the agent, it presents the following: [Screen Shot 2018-08-31 at 2.41.48 PM.png] So it is pulling suggestions from the family agents. Similarly, we have an agent person "Smith, Liz, 1923-2017." It does not present her as an option unless we type ", " after her name. Someone who wants to add her, though, won't necessarily know that she's got a date addition. Again it pulls from family agents. [Screen Shot 2018-09-12 at 8.44.48 AM.png] [Screen Shot 2018-09-12 at 8.44.59 AM.png] This what the suggestions looked like in 1.5.3 for us: [Screen Shot 2018-08-31 at 3.49.41 PM.png] [image.png] Has anyone else had a problem with this? Trying to figure out if this is an issue with 2.4.1 or with our data. Perhaps we've got something configured incorrectly in our settings? We've already tried re-indexing, but that did not help. Any suggestions would be great! 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 From buschedw at msu.edu Wed Sep 19 08:17:40 2018 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 19 Sep 2018 12:17:40 +0000 Subject: [Archivesspace_Users_Group] Setting Global Preferences Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164ACC5D4@CAD-EX01.campusad.msu.edu> HI- I know there was a discussion recently about setting global preferences and I've got them to work in the past when testing prior releases. We just did our official migration from AT to ASpace and for some reason, the global preferences I set for Accessions, Resources browse columns and pre-populate default values in those are not getting to other users. Is this something the indexing needs to do? Maybe it needs to be restarted? In the past as admin user, I set the pre-populate toggle and set the browse columns in Global Preferences and it worked. Not working this time. We are on v2.5.0. I tried also setting Repository Preferences but that didn't help. Any ideas? Ed Busch Electronic Records Archivist, MLIS MSU Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhughes at library.ucla.edu Wed Sep 19 18:31:41 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Wed, 19 Sep 2018 22:31:41 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: <34F5E82E-D81C-42CA-A148-7692DBAF97AE@lib.msu.edu> References: <34F5E82E-D81C-42CA-A148-7692DBAF97AE@lib.msu.edu> Message-ID: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 -------------- next part -------------- A non-text attachment was scrubbed... Name: topcontainer.JPG Type: image/jpeg Size: 16522 bytes Desc: topcontainer.JPG URL: From ltang5 at lib.msu.edu Thu Sep 20 09:24:58 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 20 Sep 2018 13:24:58 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: References: <34F5E82E-D81C-42CA-A148-7692DBAF97AE@lib.msu.edu> Message-ID: <4E43DEBE-C3A1-47B0-87C7-33B96E13B2B1@lib.msu.edu> Hi Maggie, Thanks for following up with my questions, I'm glad we're having this discussion because I think we could create a JIRA ticket about this issue if we (as the membership) would like to see this area potentially altered/clarified. I personally would support having the CUI default to a public audience and have it appear before the , not be visually associated with a top container. However, where would it be viewed instead in the staff interface? I would prefer if the CUI was a free-text field which *wouldn't* autopopulate the level of description because I can think of other formats of a CUI - such as if someone wants to record the identifiers that the creator used for their working filing system or recording the corresponding file id for digitized content derived from the original format. Or, are people recording this sort of information in a note field instead? How would others feel about this? Thanks! Lydia ?On 9/19/18, 6:31 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Hughes, Margaret" wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D279&d=DwIGaQ&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=cxdroSAnMNN8v-ziOfa-FfAKri3ejziRJdFf2j2n25E&s=eIJZHSrMBRwzDOHE6Gr1BPXa2gRqmtrrY_xI0FAb0co&e= Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 From lhocking at litchfieldhistoricalsociety.org Thu Sep 20 09:41:12 2018 From: lhocking at litchfieldhistoricalsociety.org (Linda Hocking) Date: Thu, 20 Sep 2018 13:41:12 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: <4E43DEBE-C3A1-47B0-87C7-33B96E13B2B1@lib.msu.edu> References: <34F5E82E-D81C-42CA-A148-7692DBAF97AE@lib.msu.edu> , <4E43DEBE-C3A1-47B0-87C7-33B96E13B2B1@lib.msu.edu> Message-ID: Lydia & Maggie, I'm glad you brought this up! I am using the CUI to identify the Series, subseries, or item number. We are currently not using (and may decide not to use) the container management system. Every time I print a finding aid for someone (our users are not all computer savvy) I have to write those numbers in or manually count them. In the public interface, I can see the level of the item or folder I'm looking at, but not where it belongs in the overall hierarchy (so I can see "Item 1" but not that it's part of Series 2, Folder 7). It's incredibly time consuming to have to go back to the staff interface to figure out where something someone wants to see is. I get that the container management system might rectify this problem to some extent, but our intellectual description almost always matches physical location so it seems like a heck of a lot of work to implement that for little reward, especially since the information is in the system- there's just no good way to see it. Thanks again. Linda Linda Hocking, CA Curator of Library & Archives Litchfield Historical Society P.O. Box 385 Litchfield, CT 06759 860-567-4501 lhocking at litchfieldhistoricalsociety.org eboardman.tumblr.com ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Thursday, September 20, 2018 9:24 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi Maggie, Thanks for following up with my questions, I'm glad we're having this discussion because I think we could create a JIRA ticket about this issue if we (as the membership) would like to see this area potentially altered/clarified. I personally would support having the CUI default to a public audience and have it appear before the , not be visually associated with a top container. However, where would it be viewed instead in the staff interface? I would prefer if the CUI was a free-text field which *wouldn't* autopopulate the level of description because I can think of other formats of a CUI - such as if someone wants to record the identifiers that the creator used for their working filing system or recording the corresponding file id for digitized content derived from the original format. Or, are people recording this sort of information in a note field instead? How would others feel about this? Thanks! Lydia ?On 9/19/18, 6:31 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Hughes, Margaret" wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D279&d=DwIGaQ&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=cxdroSAnMNN8v-ziOfa-FfAKri3ejziRJdFf2j2n25E&s=eIJZHSrMBRwzDOHE6Gr1BPXa2gRqmtrrY_xI0FAb0co&e= Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry.weimer at nyhistory.org Thu Sep 20 10:15:41 2018 From: larry.weimer at nyhistory.org (Larry Weimer) Date: Thu, 20 Sep 2018 10:15:41 -0400 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: References: <34F5E82E-D81C-42CA-A148-7692DBAF97AE@lib.msu.edu> Message-ID: Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret wrote: > Confusion over the CUI field came up recently for us, as well, and we're > wondering how we should move forward using it. > > Regarding the first question: I'm wondering if other institutions are > using the CUI to record information like "Series I" or "Subseries 8.4"? And > if so, are you happy with how the CUI exports in the EAD? As far as I > understand, the CUI field exports in EAD as which comes after the > title . Maybe this is specific to our practice, and it's > something that could also be fixed with a stylesheet, but it seems like it > would make more sense for the to precede the , if it is > indeed intended for information like "Series I" or "Subseries 8.4". Then > the result in the EAD would likely display as "Series 1 Correspondence". If > institutions are not using the CUI to record "Series 1", are you including > that in the title field? Or not noting series and subseries numbers at all? > > Relating to the second question, as you said the top container field pulls > and displays both the Level of Description (if it is "series") and the > information in the CUI, so it results in top containers like ?Series Series > X". Is this the intended behavior? My inclination is that displaying this > information in the top container does not make sense and is not helpful, > especially in cases where containers belong to multiple series. I tested it > with adding a box to four different series and it lists all four in the top > container (see attached screenshot). Are others experiencing this and > accepting it/ignoring it? > > Any help is much appreciated! > > Maggie > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of > Tang, Lydia > Sent: Monday, September 17, 2018 10:07 AM > To: Archivesspace Users Group lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions > > Hi all, > I?m passing along a question for a friend and then have a set of slightly > related questions of my own: > > 1. I am trying to find a way to have a series identifier code appear on > the finding aid. The Component Unique Identifier does not appear to print, > and the only examples I have come across have just added Series 1 to the > beginning of the series name as in: > Series 1. Athletic Council records, 1903-1975. Does anyone use the Series > code on your finding aid, and if so, where do you add it? > 2. My question: I have a legacy imported collection which uses the > Series info in the CUI. It displays as ?Series Series X? in the top > container field. Sorry if I?m stating the obvious, but this label pulls > the first ?series? from the level of description ? only if it is at a > series level (I tried changing it to subseries and other smaller levels) > and the rest is free text from the CUI. When there are materials from more > than one series are shared in a Top Container, it lists off possibly up to > two series (it didn?t seem like it listed off 3 or more, but I might have > been confusing myself). I am not sure that Staff Interface recommendations > by SIEWG touched on the CUI, so I wanted to ask: > * Would it be helpful to have a publish function for the CUI? Just > trying to imagine it, it would be an established default setting with a > check box to manually change. > * Is displaying the information in the Top Container the most > efficient/logical place - especially in cases of extensive intellectual > arrangement of items belonging to multiple series sharing a container? > There is a JIRA relating to CUI display: https://archivesspace. > atlassian.net/browse/ANW-279 Does this resonate with the broader > membership (you all)? > * Is deriving a portion of the label from the level of description > for the CUI universally helpful? How about in cases of electronic file > names or labeling physical objects with the corresponding scanned object > identifier? Alternatively, would enabling this action for smaller levels > of description (sub-series, file, item, etc), be helpful? > I?m just trying to wrap my head around it, so any feedback/clarifications > are greatly appreciated! > Lydia > -- > Dr. Lydia Tang, CA, DAS, DMA, MLIS > Special Collections Archivist-Librarian > Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University > Libraries > 366 W. Circle Drive (DB 6) > East Lansing, MI 48824-1048 > Email: ltang5 at msu.edu > Phone: 517-884-8984 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From harmeyna at purdue.edu Thu Sep 20 11:57:45 2018 From: harmeyna at purdue.edu (Harmeyer, Neal A) Date: Thu, 20 Sep 2018 15:57:45 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Message-ID: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl> Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1 at the moment), we do use the CUI to help distinguish the intellectual arrangement; this has proven very helpful in search results and has eliminated confusion we encountered after our migration from Archon. We use the CUI to note Collection #, Series #, and Sub-Series #, with notes of File # and/or Item# if necessary. Basically, by doing this a researcher or staff member can ?drop? themselves into the intellectual arrangement of the resource and know where they are really quickly. We?re not using the EAD outputs at this time. I would also like to join Maggie and Lydia in noting the idiosyncratic way the Level of Description displays in Instance top containers. From my experience?and someone please correct me if I am wrong?the CUI/Level of Description only displays in the Instance when Series is selected as the Level of Description. I also wonder if this is intended behavior? As noted by Maggie and Lydia?s screenshots, this can become a long string of text. Furthermore, it then is exported into the public interface-generated PDF output under Summary Information container info (see attached on page 3). This gives a greater importance to a Series than other aspects of the collection. I do not believe it is necessary to note the Level of Description/CUI the Summary Information here, as it those details are visualized and recorded elsewhere to greater effect. Unless there is a reason behind it, I do support eliminating the display of Level of Description and CUI in the Instance top container display on the staff side and the public outputs. Cheers, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Larry Weimer Sent: Thursday, September 20, 2018 10:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret > wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MSA_277.pdf Type: application/pdf Size: 33356 bytes Desc: MSA_277.pdf URL: From mhughes at library.ucla.edu Thu Sep 20 12:54:08 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Thu, 20 Sep 2018 16:54:08 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl> References: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl> Message-ID: Larry?Thank you for sharing how you?re (not) working with the CUI. Regarding the other ASpace example for the field, accession number, we also track that information via linked accessions or an Immediate Source of Acquisition note. Linda and Neal ? I?m glad you brought up the PUI as that?s not something we?re using right now, and so I wasn?t familiar with how the CUI is utilized in the PUI. Do I understand correctly that not being able to see where an archival object belongs in the overall hierarchy is only an issue when discovering archival objects (files, items, etc) via search? And this is because the CUI does not display in the PUI at all currently? Lydia?I agree that a JIRA ticket about this issue is needed. I would also support having the CUI default to a public audience, have it appear before the , and not be visually associated with a top container. Could it continue to be located in the same place as it is now in the staff interface?s edit mode? And we could make the CUI visible in the same place in the staff interface in view mode, as well? I agree with the reasons you stated (working filing system, file id, etc) that the CUI should be a free-text field which *wouldn't* autopopulate the level of description. Maggie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, September 20, 2018 8:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1 at the moment), we do use the CUI to help distinguish the intellectual arrangement; this has proven very helpful in search results and has eliminated confusion we encountered after our migration from Archon. We use the CUI to note Collection #, Series #, and Sub-Series #, with notes of File # and/or Item# if necessary. Basically, by doing this a researcher or staff member can ?drop? themselves into the intellectual arrangement of the resource and know where they are really quickly. We?re not using the EAD outputs at this time. I would also like to join Maggie and Lydia in noting the idiosyncratic way the Level of Description displays in Instance top containers. From my experience?and someone please correct me if I am wrong?the CUI/Level of Description only displays in the Instance when Series is selected as the Level of Description. I also wonder if this is intended behavior? As noted by Maggie and Lydia?s screenshots, this can become a long string of text. Furthermore, it then is exported into the public interface-generated PDF output under Summary Information container info (see attached on page 3). This gives a greater importance to a Series than other aspects of the collection. I do not believe it is necessary to note the Level of Description/CUI the Summary Information here, as it those details are visualized and recorded elsewhere to greater effect. Unless there is a reason behind it, I do support eliminating the display of Level of Description and CUI in the Instance top container display on the staff side and the public outputs. Cheers, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Larry Weimer Sent: Thursday, September 20, 2018 10:16 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret > wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From mhughes at library.ucla.edu Thu Sep 20 12:55:17 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Thu, 20 Sep 2018 16:55:17 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: References: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl> Message-ID: Correction: I just realized that the CUI is already visible in the staff interface view-mode. So, in response to Lydia?s question, I wonder if we could keep the CUI in the same place in staff interface? From: Hughes, Margaret Sent: Thursday, September 20, 2018 9:54 AM To: Archivesspace Users Group Subject: RE: [Archivesspace_Users_Group] Component Unique Identifiers questions Larry?Thank you for sharing how you?re (not) working with the CUI. Regarding the other ASpace example for the field, accession number, we also track that information via linked accessions or an Immediate Source of Acquisition note. Linda and Neal ? I?m glad you brought up the PUI as that?s not something we?re using right now, and so I wasn?t familiar with how the CUI is utilized in the PUI. Do I understand correctly that not being able to see where an archival object belongs in the overall hierarchy is only an issue when discovering archival objects (files, items, etc) via search? And this is because the CUI does not display in the PUI at all currently? Lydia?I agree that a JIRA ticket about this issue is needed. I would also support having the CUI default to a public audience, have it appear before the , and not be visually associated with a top container. Could it continue to be located in the same place as it is now in the staff interface?s edit mode? And we could make the CUI visible in the same place in the staff interface in view mode, as well? I agree with the reasons you stated (working filing system, file id, etc) that the CUI should be a free-text field which *wouldn't* autopopulate the level of description. Maggie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, September 20, 2018 8:58 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1 at the moment), we do use the CUI to help distinguish the intellectual arrangement; this has proven very helpful in search results and has eliminated confusion we encountered after our migration from Archon. We use the CUI to note Collection #, Series #, and Sub-Series #, with notes of File # and/or Item# if necessary. Basically, by doing this a researcher or staff member can ?drop? themselves into the intellectual arrangement of the resource and know where they are really quickly. We?re not using the EAD outputs at this time. I would also like to join Maggie and Lydia in noting the idiosyncratic way the Level of Description displays in Instance top containers. From my experience?and someone please correct me if I am wrong?the CUI/Level of Description only displays in the Instance when Series is selected as the Level of Description. I also wonder if this is intended behavior? As noted by Maggie and Lydia?s screenshots, this can become a long string of text. Furthermore, it then is exported into the public interface-generated PDF output under Summary Information container info (see attached on page 3). This gives a greater importance to a Series than other aspects of the collection. I do not believe it is necessary to note the Level of Description/CUI the Summary Information here, as it those details are visualized and recorded elsewhere to greater effect. Unless there is a reason behind it, I do support eliminating the display of Level of Description and CUI in the Instance top container display on the staff side and the public outputs. Cheers, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Larry Weimer Sent: Thursday, September 20, 2018 10:16 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret > wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From lhocking at litchfieldhistoricalsociety.org Thu Sep 20 14:05:55 2018 From: lhocking at litchfieldhistoricalsociety.org (Linda Hocking) Date: Thu, 20 Sep 2018 18:05:55 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: References: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl>, Message-ID: Maggie- This is what I see when looking at a finding aid in the public interface after having selected a particular item from the pull down "Collection Organization" list- Balance book, 1795-1796 Item 1 Item Identifier: Item 1 Litchfield Historical Society Elijah Boardman Papers Elijah Boardman Business Papers, 1794-1824 Balance books Balance book, 1795-1796 Here's the link if you want to look at it- http://archives.litchfieldhistoricalsociety.org:8081/repositories/2/archival_objects/14454 So I can tell that it's Item 1, and if I clicked up to "Elijah Boardman Business Papers" it would show me the series number, but it won't show them together. I'm wary of manually entering the whole string in the CUI, but maybe that's the only way to get it to display. On the other hand, if I do that, and the system is changed to show the whole hierarchy, it will be redundant. Anyway, for us, this is an issue of having to go through multiple steps to figure out where something is within the order of the collection more so than anything to do with the search. Thanks, Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Hughes, Margaret Sent: Thursday, September 20, 2018 12:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Larry?Thank you for sharing how you?re (not) working with the CUI. Regarding the other ASpace example for the field, accession number, we also track that information via linked accessions or an Immediate Source of Acquisition note. Linda and Neal ? I?m glad you brought up the PUI as that?s not something we?re using right now, and so I wasn?t familiar with how the CUI is utilized in the PUI. Do I understand correctly that not being able to see where an archival object belongs in the overall hierarchy is only an issue when discovering archival objects (files, items, etc) via search? And this is because the CUI does not display in the PUI at all currently? Lydia?I agree that a JIRA ticket about this issue is needed. I would also support having the CUI default to a public audience, have it appear before the , and not be visually associated with a top container. Could it continue to be located in the same place as it is now in the staff interface?s edit mode? And we could make the CUI visible in the same place in the staff interface in view mode, as well? I agree with the reasons you stated (working filing system, file id, etc) that the CUI should be a free-text field which *wouldn't* autopopulate the level of description. Maggie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, September 20, 2018 8:58 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1 at the moment), we do use the CUI to help distinguish the intellectual arrangement; this has proven very helpful in search results and has eliminated confusion we encountered after our migration from Archon. We use the CUI to note Collection #, Series #, and Sub-Series #, with notes of File # and/or Item# if necessary. Basically, by doing this a researcher or staff member can ?drop? themselves into the intellectual arrangement of the resource and know where they are really quickly. We?re not using the EAD outputs at this time. I would also like to join Maggie and Lydia in noting the idiosyncratic way the Level of Description displays in Instance top containers. From my experience?and someone please correct me if I am wrong?the CUI/Level of Description only displays in the Instance when Series is selected as the Level of Description. I also wonder if this is intended behavior? As noted by Maggie and Lydia?s screenshots, this can become a long string of text. Furthermore, it then is exported into the public interface-generated PDF output under Summary Information container info (see attached on page 3). This gives a greater importance to a Series than other aspects of the collection. I do not believe it is necessary to note the Level of Description/CUI the Summary Information here, as it those details are visualized and recorded elsewhere to greater effect. Unless there is a reason behind it, I do support eliminating the display of Level of Description and CUI in the Instance top container display on the staff side and the public outputs. Cheers, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Larry Weimer Sent: Thursday, September 20, 2018 10:16 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret > wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From ltang5 at lib.msu.edu Thu Sep 20 14:35:24 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 20 Sep 2018 18:35:24 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: References: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl> Message-ID: <437CF0C0-7617-4E93-8B87-07F519E98D56@lib.msu.edu> Hi all, Just FYI, here is my drafted JIRA ticket. I didn?t mention anything about changing the placement of the CUI in the data entry of the staff interface. Please feel free to comment on the ticket, in case I missed or misinterpreted anything! https://archivesspace.atlassian.net/browse/ANW-770 On a slightly related note, I drafted up this ticket about the Collection Organization view of the PUI. I would love to start a conversation about this. https://archivesspace.atlassian.net/browse/ANW-769 I was reading up on Yale?s usability studies, Grand Valley State U also did a usability study recently, and just from my own observations, and I feel like the collection navigation sidebar view is possibly more helpful than the current main view. I?m proposing expanding the sidebar to become the primary view of the collection (but with box and folder visible in this view) and possibly if an archival component is clicked upon, it expands open within this view. I noted that it?s difficult currently to see the hierarchy of a long finding aid and suggested that the hierarchy be collapsed but always visible in this view. What do people think about this idea? I?d love to hear your thoughts on the list or on the ticket. If there?s a lot of disagreement, I can close the ticket. Looking forward to hearing your thoughts! Lydia From mhughes at library.ucla.edu Thu Sep 20 17:00:02 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Thu, 20 Sep 2018 21:00:02 +0000 Subject: [Archivesspace_Users_Group] Viewing suppressed records permission In-Reply-To: References: Message-ID: FYI to any interested parties, I created a JIRA ticket for this issue: https://archivesspace.atlassian.net/browse/ANW-771 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hughes, Margaret Sent: Wednesday, September 12, 2018 9:06 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Viewing suppressed records permission Hi all, We're having trouble with the "view suppressed records in this repository" permission. I've recreated it in the sandbox and have attached screenshots here. Here are my steps: 1. I edited the Archivists of the test repository group to give them permission to both suppress the major record types and view suppressed records. 2. I created another user called "other user" and added them to the Archivists group. (see screenshot) 3. I created a resource called "testing suppression". 4. Logged in as "other user" I suppressed the "testing suppression" resource. 5. I got an error message saying I no longer had permission to view the record. 6. I searched for "testing suppression" and no search results display (still logged in as "other user"). (see screenshot) 7. I logged in as admin and searched for "test suppression" and the suppressed in included in search results. (see screenshot) Are there any other dependent permissions that needs to be enabled that could be blocking the ability to view suppressed records? Am I missing something? I know there have been other conversations about suppression being buggy - I actually was not able to un-suppress the test resource and crashed the sandbox when I tried. I searched quickly for a JIRA ticket and didn't see this issue. Are institutions successfully using the suppress records functionality? Thanks for your help! Maggie ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lcalahan at umn.edu Thu Sep 20 17:07:24 2018 From: lcalahan at umn.edu (Lisa Calahan) Date: Thu, 20 Sep 2018 16:07:24 -0500 Subject: [Archivesspace_Users_Group] Viewing suppressed records permission In-Reply-To: References: Message-ID: Hi Margaret, I wonder if you need to set either the Global or Repository Preference to "Show Suppressed?" in order to view the records? I haven't had a chance to recreate your issue, but that might be at play. Lisa On Wed, Sep 12, 2018 at 11:05 AM, Hughes, Margaret wrote: > Hi all, > > > > We?re having trouble with the ?view suppressed records in this repository? > permission. I?ve recreated it in the sandbox and have attached screenshots > here. Here are my steps: > > > > 1. I edited the Archivists of the test repository group to give > them permission to both suppress the major record types and view suppressed > records. > > 2. I created another user called ?other user? and added them to the > Archivists group. (see screenshot) > > 3. I created a resource called ?testing suppression?. > > 4. Logged in as ?other user? I suppressed the ?testing suppression? > resource. > > 5. I got an error message saying I no longer had permission to view > the record. > > 6. I searched for ?testing suppression? and no search results > display (still logged in as ?other user?). (see screenshot) > > 7. I logged in as admin and searched for ?test suppression? and the > suppressed in included in search results. (see screenshot) > > > > Are there any other dependent permissions that needs to be enabled that > could be blocking the ability to view suppressed records? Am I missing > something? > > > > I know there have been other conversations about suppression being buggy ? > I actually was not able to un-suppress the test resource and crashed the > sandbox when I tried. I searched quickly for a JIRA ticket and didn?t see > this issue. Are institutions successfully using the suppress records > functionality? > > > > Thanks for your help! > > > > Maggie > > > > ---------------------------------- > > Margaret Hughes > > Collections Data Archivist > > 310.206.6203 > > > > UCLA Library Special Collections > > A1713 Charles E. Young Research Library > > Los Angeles, CA 90095-1575 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Pronouns: She/her/hers Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library, Suite 315 222-21st Ave. S. Minneapolis MN 55455 Phone: 612.626.2531 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-20 at 4.06.00 PM.png Type: image/png Size: 18244 bytes Desc: not available URL: From mhughes at library.ucla.edu Thu Sep 20 17:26:37 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Thu, 20 Sep 2018 21:26:37 +0000 Subject: [Archivesspace_Users_Group] Viewing suppressed records permission In-Reply-To: References: Message-ID: Lisa, that?s it! Thank you so much for pointing me to that other setting. It still seems a bit wonky, though. First I enabled the Show Suppressed under Global Preferences? didn?t work for other users. Then enabled the Show Suppressed under Repository Preferences ? didn?t work for other users. Then enabled the Show Suppressed under User Preferences, and it is now displaying suppressed records to other users who should have permission to view them! It seems redundant to have view/show suppressed be a global/repo/user preference setting as well as a user group permission. Also I still don?t quite get how the global/repo/user preferences defer to each other. But I?m glad to have figured this out! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lisa Calahan Sent: Thursday, September 20, 2018 2:07 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Viewing suppressed records permission Hi Margaret, I wonder if you need to set either the Global or Repository Preference to "Show Suppressed?" in order to view the records? I haven't had a chance to recreate your issue, but that might be at play. Lisa [cid:image001.png at 01D450ED.EE904310] On Wed, Sep 12, 2018 at 11:05 AM, Hughes, Margaret > wrote: Hi all, We?re having trouble with the ?view suppressed records in this repository? permission. I?ve recreated it in the sandbox and have attached screenshots here. Here are my steps: 1. I edited the Archivists of the test repository group to give them permission to both suppress the major record types and view suppressed records. 2. I created another user called ?other user? and added them to the Archivists group. (see screenshot) 3. I created a resource called ?testing suppression?. 4. Logged in as ?other user? I suppressed the ?testing suppression? resource. 5. I got an error message saying I no longer had permission to view the record. 6. I searched for ?testing suppression? and no search results display (still logged in as ?other user?). (see screenshot) 7. I logged in as admin and searched for ?test suppression? and the suppressed in included in search results. (see screenshot) Are there any other dependent permissions that needs to be enabled that could be blocking the ability to view suppressed records? Am I missing something? I know there have been other conversations about suppression being buggy ? I actually was not able to un-suppress the test resource and crashed the sandbox when I tried. I searched quickly for a JIRA ticket and didn?t see this issue. Are institutions successfully using the suppress records functionality? Thanks for your help! Maggie ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Pronouns: She/her/hers Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library, Suite 315 222-21st Ave. S. Minneapolis MN 55455 Phone: 612.626.2531 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 18244 bytes Desc: image001.png URL: From KennedyN at si.edu Fri Sep 21 13:14:10 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 21 Sep 2018 17:14:10 +0000 Subject: [Archivesspace_Users_Group] External ID Message-ID: Has anyone tried to set up the external id field so that a user can create (or edit) an external_id via the staff UI? Is that possible? Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Sep 21 14:23:18 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 21 Sep 2018 18:23:18 +0000 Subject: [Archivesspace_Users_Group] External ID In-Reply-To: References: Message-ID: <7EDDE417-B708-4A47-9222-764599D12C7B@virginia.edu> AppConfig[:show_external_ids] = true will allow you to view and edit existing external ids in staff interface, but it doesn?t allow you to create them. Ours are added either from EAD import or via backend API. I had once forked changes in an older version to allow creating them from the staff webapp. If I?m remembering correctly, the required changes touched too many modules and were not localized, so it didn?t seem practical to maintain them in a plugin. If there is interest in adding this feature to the core code, I could review that branch and see if it could be merged into current code base. That code still followed that config setting, so edit option was not visible unless set to true. ? Steve Majewski > On Sep 21, 2018, at 1:14 PM, Kennedy, Nancy wrote: > > Has anyone tried to set up the external id field so that a user can create (or edit) an external_id via the staff UI? Is that possible? > > Nancy Kennedy > Smithsonian Institution > kennedyn at si.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From sdm7g at virginia.edu Fri Sep 21 14:45:48 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 21 Sep 2018 18:45:48 +0000 Subject: [Archivesspace_Users_Group] External ID In-Reply-To: <7EDDE417-B708-4A47-9222-764599D12C7B@virginia.edu> References: <7EDDE417-B708-4A47-9222-764599D12C7B@virginia.edu> Message-ID: We?ve used this config feature for so long (since v1.4.*) that I had forgotten it was necessary to turn it on to see external_ids. My advice, in earlier threads, to use the EAD mapping between multiple unitids and external_ids for some issues must have seemed somewhat confusing if anyone tried it without also having that feature enabled. ? Steve Majewski > On Sep 21, 2018, at 2:23 PM, Majewski, Steven Dennis (sdm7g) wrote: > > > AppConfig[:show_external_ids] = true > > will allow you to view and edit existing external ids in staff interface, but it doesn?t allow you to create them. > Ours are added either from EAD import or via backend API. > > I had once forked changes in an older version to allow creating them from the staff webapp. > If I?m remembering correctly, the required changes touched too many modules and were not localized, so it didn?t seem practical to maintain them in a plugin. > > If there is interest in adding this feature to the core code, I could review that branch and see if it could be merged into current code base. That code still followed that config setting, so edit option was not visible unless set to true. > > ? Steve Majewski > > >> On Sep 21, 2018, at 1:14 PM, Kennedy, Nancy > wrote: >> >> Has anyone tried to set up the external id field so that a user can create (or edit) an external_id via the staff UI? Is that possible? >> >> Nancy Kennedy >> Smithsonian Institution >> kennedyn at si.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From Joshua.D.Shaw at dartmouth.edu Fri Sep 21 14:53:58 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Fri, 21 Sep 2018 18:53:58 +0000 Subject: [Archivesspace_Users_Group] External ID In-Reply-To: References: <7EDDE417-B708-4A47-9222-764599D12C7B@virginia.edu>, Message-ID: There's actually a plugin that we had HM develop that does allow users to create and edit external ids: https://github.com/hudmol/editable_external_ids I've tested against the 2.3 release, but not anything newer. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Friday, September 21, 2018 2:45 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] External ID We?ve used this config feature for so long (since v1.4.*) that I had forgotten it was necessary to turn it on to see external_ids. My advice, in earlier threads, to use the EAD mapping between multiple unitids and external_ids for some issues must have seemed somewhat confusing if anyone tried it without also having that feature enabled. ? Steve Majewski On Sep 21, 2018, at 2:23 PM, Majewski, Steven Dennis (sdm7g) > wrote: AppConfig[:show_external_ids] = true will allow you to view and edit existing external ids in staff interface, but it doesn?t allow you to create them. Ours are added either from EAD import or via backend API. I had once forked changes in an older version to allow creating them from the staff webapp. If I?m remembering correctly, the required changes touched too many modules and were not localized, so it didn?t seem practical to maintain them in a plugin. If there is interest in adding this feature to the core code, I could review that branch and see if it could be merged into current code base. That code still followed that config setting, so edit option was not visible unless set to true. ? Steve Majewski On Sep 21, 2018, at 1:14 PM, Kennedy, Nancy > wrote: Has anyone tried to set up the external id field so that a user can create (or edit) an external_id via the staff UI? Is that possible? Nancy Kennedy Smithsonian Institution kennedyn at si.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Fri Sep 21 14:57:48 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 21 Sep 2018 18:57:48 +0000 Subject: [Archivesspace_Users_Group] External ID In-Reply-To: References: <7EDDE417-B708-4A47-9222-764599D12C7B@virginia.edu>, Message-ID: Aha! Thank you both. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Friday, September 21, 2018 2:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] External ID There's actually a plugin that we had HM develop that does allow users to create and edit external ids: https://github.com/hudmol/editable_external_ids I've tested against the 2.3 release, but not anything newer. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, September 21, 2018 2:45 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] External ID We've used this config feature for so long (since v1.4.*) that I had forgotten it was necessary to turn it on to see external_ids. My advice, in earlier threads, to use the EAD mapping between multiple unitids and external_ids for some issues must have seemed somewhat confusing if anyone tried it without also having that feature enabled. - Steve Majewski On Sep 21, 2018, at 2:23 PM, Majewski, Steven Dennis (sdm7g) > wrote: AppConfig[:show_external_ids] = true will allow you to view and edit existing external ids in staff interface, but it doesn't allow you to create them. Ours are added either from EAD import or via backend API. I had once forked changes in an older version to allow creating them from the staff webapp. If I'm remembering correctly, the required changes touched too many modules and were not localized, so it didn't seem practical to maintain them in a plugin. If there is interest in adding this feature to the core code, I could review that branch and see if it could be merged into current code base. That code still followed that config setting, so edit option was not visible unless set to true. - Steve Majewski On Sep 21, 2018, at 1:14 PM, Kennedy, Nancy > wrote: Has anyone tried to set up the external id field so that a user can create (or edit) an external_id via the staff UI? Is that possible? Nancy Kennedy Smithsonian Institution kennedyn at si.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Sep 21 15:35:40 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 21 Sep 2018 19:35:40 +0000 Subject: [Archivesspace_Users_Group] External ID In-Reply-To: References: <7EDDE417-B708-4A47-9222-764599D12C7B@virginia.edu> Message-ID: Aha! I see that they redefined render_aspace_partial and the external id template, instead of what I did, which was to change the line where render_aspace_partial was called in 10 different files ? which was why I didn?t want to maintain those changes in a plugin. ( I don?t think I understood the ASpace code base or Rails well enough back then to dare to do that. ;-) However, I would now propose that external ids are generally useful and ought to be enabled for creation, view and edit by default. ? Steve Majewski > On Sep 21, 2018, at 2:53 PM, Joshua D. Shaw wrote: > > There's actually a plugin that we had HM develop that does allow users to create and edit external ids:https://github.com/hudmol/editable_external_ids I've tested against the 2.3 release, but not anything newer. > > Joshua > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Friday, September 21, 2018 2:45 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] External ID > > > We?ve used this config feature for so long (since v1.4.*) that I had forgotten it was necessary to turn it on to see external_ids. > > My advice, in earlier threads, to use the EAD mapping between multiple unitids and external_ids for some issues must have seemed somewhat confusing if anyone tried it without also having that feature enabled. > > > ? Steve Majewski > > >> On Sep 21, 2018, at 2:23 PM, Majewski, Steven Dennis (sdm7g) > wrote: >> >> >> AppConfig[:show_external_ids] = true >> >> will allow you to view and edit existing external ids in staff interface, but it doesn?t allow you to create them. >> Ours are added either from EAD import or via backend API. >> >> I had once forked changes in an older version to allow creating them from the staff webapp. >> If I?m remembering correctly, the required changes touched too many modules and were not localized, so it didn?t seem practical to maintain them in a plugin. >> >> If there is interest in adding this feature to the core code, I could review that branch and see if it could be merged into current code base. That code still followed that config setting, so edit option was not visible unless set to true. >> >> ? Steve Majewski >> >> >>> On Sep 21, 2018, at 1:14 PM, Kennedy, Nancy > wrote: >>> >>> Has anyone tried to set up the external id field so that a user can create (or edit) an external_id via the staff UI? Is that possible? >>> >>> Nancy Kennedy >>> Smithsonian Institution >>> kennedyn at si.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From cory_nimer at byu.edu Fri Sep 21 16:00:38 2018 From: cory_nimer at byu.edu (Cory Nimer) Date: Fri, 21 Sep 2018 20:00:38 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: References: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl>, Message-ID: <6d2a21b9654a40ca90f9d4127c30a1dc@MB7.byu.local> Linda, We are still working on our PUI implementation locally, but I believe it should be possible to set your ArchivesSpace configuration options to display a composite identifier rather than just the immediate CUI level/value. This would prevent having to reenter data for each component, while providing a public view of the whole string. With the composite identifier option enabled, rather than displaying "Item 1" in the linked example, it should appear as "2012-07-0 Series 1 Sub-Series 1 Item 1" at that item level. The delimiter between the different levels' CUIs and the optional inclusion of the level of description is also configurable. Instructions are available in the roll-out documentation at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-CompositeIdentifierInheritance, and in the configuration documentation (http://archivesspace.github.io/archivesspace/user/configuring-archivesspace/). Information on the duplication of the level of description and the CUI value from the top container feature's development is available on the Yale ArchivesSpace guide (https://guides.library.yale.edu/archivesspace/ASpaceContainerManagement, at the bottom of the page). Their recommendation at the time seemed to be to remove the level information from your CUI value. Perhaps someone from Yale or elsewhere could weigh in about your options regarding this functionality. Thanks, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Linda Hocking Sent: Thursday, September 20, 2018 12:06 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie- This is what I see when looking at a finding aid in the public interface after having selected a particular item from the pull down "Collection Organization" list- Balance book, 1795-1796 Item 1 Item Identifier: Item 1 Litchfield Historical Society Elijah Boardman Papers Elijah Boardman Business Papers, 1794-1824 Balance books Balance book, 1795-1796 Here's the link if you want to look at it- http://archives.litchfieldhistoricalsociety.org:8081/repositories/2/archival_objects/14454 So I can tell that it's Item 1, and if I clicked up to "Elijah Boardman Business Papers" it would show me the series number, but it won't show them together. I'm wary of manually entering the whole string in the CUI, but maybe that's the only way to get it to display. On the other hand, if I do that, and the system is changed to show the whole hierarchy, it will be redundant. Anyway, for us, this is an issue of having to go through multiple steps to figure out where something is within the order of the collection more so than anything to do with the search. Thanks, Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Hughes, Margaret > Sent: Thursday, September 20, 2018 12:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Larry-Thank you for sharing how you're (not) working with the CUI. Regarding the other ASpace example for the field, accession number, we also track that information via linked accessions or an Immediate Source of Acquisition note. Linda and Neal - I'm glad you brought up the PUI as that's not something we're using right now, and so I wasn't familiar with how the CUI is utilized in the PUI. Do I understand correctly that not being able to see where an archival object belongs in the overall hierarchy is only an issue when discovering archival objects (files, items, etc) via search? And this is because the CUI does not display in the PUI at all currently? Lydia-I agree that a JIRA ticket about this issue is needed. I would also support having the CUI default to a public audience, have it appear before the , and not be visually associated with a top container. Could it continue to be located in the same place as it is now in the staff interface's edit mode? And we could make the CUI visible in the same place in the staff interface in view mode, as well? I agree with the reasons you stated (working filing system, file id, etc) that the CUI should be a free-text field which *wouldn't* autopopulate the level of description. Maggie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, September 20, 2018 8:58 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1 at the moment), we do use the CUI to help distinguish the intellectual arrangement; this has proven very helpful in search results and has eliminated confusion we encountered after our migration from Archon. We use the CUI to note Collection #, Series #, and Sub-Series #, with notes of File # and/or Item# if necessary. Basically, by doing this a researcher or staff member can "drop" themselves into the intellectual arrangement of the resource and know where they are really quickly. We're not using the EAD outputs at this time. I would also like to join Maggie and Lydia in noting the idiosyncratic way the Level of Description displays in Instance top containers. From my experience-and someone please correct me if I am wrong-the CUI/Level of Description only displays in the Instance when Series is selected as the Level of Description. I also wonder if this is intended behavior? As noted by Maggie and Lydia's screenshots, this can become a long string of text. Furthermore, it then is exported into the public interface-generated PDF output under Summary Information container info (see attached on page 3). This gives a greater importance to a Series than other aspects of the collection. I do not believe it is necessary to note the Level of Description/CUI the Summary Information here, as it those details are visualized and recorded elsewhere to greater effect. Unless there is a reason behind it, I do support eliminating the display of Level of Description and CUI in the Instance top container display on the staff side and the public outputs. Cheers, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Larry Weimer Sent: Thursday, September 20, 2018 10:16 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret > wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like "Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I'm passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as "Series Series X" in the top container field. Sorry if I'm stating the obvious, but this label pulls the first "series" from the level of description - only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn't seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I'm just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From lhocking at litchfieldhistoricalsociety.org Mon Sep 24 09:56:20 2018 From: lhocking at litchfieldhistoricalsociety.org (Linda Hocking) Date: Mon, 24 Sep 2018 13:56:20 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions In-Reply-To: <6d2a21b9654a40ca90f9d4127c30a1dc@MB7.byu.local> References: <3a2df5eaa71d498fabdfea3ca92fed6f@wppexc12.purdue.lcl>, , <6d2a21b9654a40ca90f9d4127c30a1dc@MB7.byu.local> Message-ID: Cory, Thank you so much for this. I will send it to our developer and see if he can set it up. When/if we implement container management, we can change it back. Thanks again! Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Cory Nimer Sent: Friday, September 21, 2018 4:00 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Linda, We are still working on our PUI implementation locally, but I believe it should be possible to set your ArchivesSpace configuration options to display a composite identifier rather than just the immediate CUI level/value. This would prevent having to reenter data for each component, while providing a public view of the whole string. With the composite identifier option enabled, rather than displaying "Item 1" in the linked example, it should appear as "2012-07-0 Series 1 Sub-Series 1 Item 1" at that item level. The delimiter between the different levels' CUIs and the optional inclusion of the level of description is also configurable. Instructions are available in the roll-out documentation at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-CompositeIdentifierInheritance, and in the configuration documentation (http://archivesspace.github.io/archivesspace/user/configuring-archivesspace/). Information on the duplication of the level of description and the CUI value from the top container feature's development is available on the Yale ArchivesSpace guide (https://guides.library.yale.edu/archivesspace/ASpaceContainerManagement, at the bottom of the page). Their recommendation at the time seemed to be to remove the level information from your CUI value. Perhaps someone from Yale or elsewhere could weigh in about your options regarding this functionality. Thanks, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Linda Hocking Sent: Thursday, September 20, 2018 12:06 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie- This is what I see when looking at a finding aid in the public interface after having selected a particular item from the pull down "Collection Organization" list- Balance book, 1795-1796 Item 1 Item Identifier: Item 1 Litchfield Historical Society Elijah Boardman Papers Elijah Boardman Business Papers, 1794-1824 Balance books Balance book, 1795-1796 Here's the link if you want to look at it- http://archives.litchfieldhistoricalsociety.org:8081/repositories/2/archival_objects/14454 So I can tell that it's Item 1, and if I clicked up to "Elijah Boardman Business Papers" it would show me the series number, but it won't show them together. I'm wary of manually entering the whole string in the CUI, but maybe that's the only way to get it to display. On the other hand, if I do that, and the system is changed to show the whole hierarchy, it will be redundant. Anyway, for us, this is an issue of having to go through multiple steps to figure out where something is within the order of the collection more so than anything to do with the search. Thanks, Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Hughes, Margaret > Sent: Thursday, September 20, 2018 12:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Larry?Thank you for sharing how you?re (not) working with the CUI. Regarding the other ASpace example for the field, accession number, we also track that information via linked accessions or an Immediate Source of Acquisition note. Linda and Neal ? I?m glad you brought up the PUI as that?s not something we?re using right now, and so I wasn?t familiar with how the CUI is utilized in the PUI. Do I understand correctly that not being able to see where an archival object belongs in the overall hierarchy is only an issue when discovering archival objects (files, items, etc) via search? And this is because the CUI does not display in the PUI at all currently? Lydia?I agree that a JIRA ticket about this issue is needed. I would also support having the CUI default to a public audience, have it appear before the , and not be visually associated with a top container. Could it continue to be located in the same place as it is now in the staff interface?s edit mode? And we could make the CUI visible in the same place in the staff interface in view mode, as well? I agree with the reasons you stated (working filing system, file id, etc) that the CUI should be a free-text field which *wouldn't* autopopulate the level of description. Maggie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, September 20, 2018 8:58 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1 at the moment), we do use the CUI to help distinguish the intellectual arrangement; this has proven very helpful in search results and has eliminated confusion we encountered after our migration from Archon. We use the CUI to note Collection #, Series #, and Sub-Series #, with notes of File # and/or Item# if necessary. Basically, by doing this a researcher or staff member can ?drop? themselves into the intellectual arrangement of the resource and know where they are really quickly. We?re not using the EAD outputs at this time. I would also like to join Maggie and Lydia in noting the idiosyncratic way the Level of Description displays in Instance top containers. From my experience?and someone please correct me if I am wrong?the CUI/Level of Description only displays in the Instance when Series is selected as the Level of Description. I also wonder if this is intended behavior? As noted by Maggie and Lydia?s screenshots, this can become a long string of text. Furthermore, it then is exported into the public interface-generated PDF output under Summary Information container info (see attached on page 3). This gives a greater importance to a Series than other aspects of the collection. I do not believe it is necessary to note the Level of Description/CUI the Summary Information here, as it those details are visualized and recorded elsewhere to greater effect. Unless there is a reason behind it, I do support eliminating the display of Level of Description and CUI in the Instance top container display on the staff side and the public outputs. Cheers, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Larry Weimer Sent: Thursday, September 20, 2018 10:16 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions Maggie, To answer your first question, we (New-York Historical) do not currently use the CUI field at all. We include "Series X" or "Subseries X.1" in the component title. The other ASpace example for this field, accession number, we would include in an Immediate Source of Acquisition note (though we more commonly just refer to the source by their name and date, rather than the number. We use the "Related Resource" field to link the accession number to the collection.) Larry Larry Weimer Head of Archival Processing New-York Historical Society On Wed, Sep 19, 2018 at 6:31 PM, Hughes, Margaret > wrote: Confusion over the CUI field came up recently for us, as well, and we're wondering how we should move forward using it. Regarding the first question: I'm wondering if other institutions are using the CUI to record information like "Series I" or "Subseries 8.4"? And if so, are you happy with how the CUI exports in the EAD? As far as I understand, the CUI field exports in EAD as which comes after the title . Maybe this is specific to our practice, and it's something that could also be fixed with a stylesheet, but it seems like it would make more sense for the to precede the , if it is indeed intended for information like "Series I" or "Subseries 8.4". Then the result in the EAD would likely display as "Series 1 Correspondence". If institutions are not using the CUI to record "Series 1", are you including that in the title field? Or not noting series and subseries numbers at all? Relating to the second question, as you said the top container field pulls and displays both the Level of Description (if it is "series") and the information in the CUI, so it results in top containers like ?Series Series X". Is this the intended behavior? My inclination is that displaying this information in the top container does not make sense and is not helpful, especially in cases where containers belong to multiple series. I tested it with adding a box to four different series and it lists all four in the top container (see attached screenshot). Are others experiencing this and accepting it/ignoring it? Any help is much appreciated! Maggie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Monday, September 17, 2018 10:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Component Unique Identifiers questions Hi all, I?m passing along a question for a friend and then have a set of slightly related questions of my own: 1. I am trying to find a way to have a series identifier code appear on the finding aid. The Component Unique Identifier does not appear to print, and the only examples I have come across have just added Series 1 to the beginning of the series name as in: Series 1. Athletic Council records, 1903-1975. Does anyone use the Series code on your finding aid, and if so, where do you add it? 2. My question: I have a legacy imported collection which uses the Series info in the CUI. It displays as ?Series Series X? in the top container field. Sorry if I?m stating the obvious, but this label pulls the first ?series? from the level of description ? only if it is at a series level (I tried changing it to subseries and other smaller levels) and the rest is free text from the CUI. When there are materials from more than one series are shared in a Top Container, it lists off possibly up to two series (it didn?t seem like it listed off 3 or more, but I might have been confusing myself). I am not sure that Staff Interface recommendations by SIEWG touched on the CUI, so I wanted to ask: * Would it be helpful to have a publish function for the CUI? Just trying to imagine it, it would be an established default setting with a check box to manually change. * Is displaying the information in the Top Container the most efficient/logical place - especially in cases of extensive intellectual arrangement of items belonging to multiple series sharing a container? There is a JIRA relating to CUI display: https://archivesspace.atlassian.net/browse/ANW-279 Does this resonate with the broader membership (you all)? * Is deriving a portion of the label from the level of description for the CUI universally helpful? How about in cases of electronic file names or labeling physical objects with the corresponding scanned object identifier? Alternatively, would enabling this action for smaller levels of description (sub-series, file, item, etc), be helpful? I?m just trying to wrap my head around it, so any feedback/clarifications are greatly appreciated! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From bdysonsm at utk.edu Mon Sep 24 13:40:46 2018 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Mon, 24 Sep 2018 17:40:46 +0000 Subject: [Archivesspace_Users_Group] Reports Questions: generating reports from a selection Message-ID: Hi all - I'm hoping someone can provide a bit of direction for me. Are there any shared plugins or repositories that allow users to generate reports from a selection; i.e. a search/browse, select multiple entries (of accessions, e.g.), then create > backend jobs > some particular report that will only return results for the selected accession entries? Apologies for the poorly worded question. Thank you in advance for any suggestions or pointers you can share. Best, Bridger From ltang5 at lib.msu.edu Mon Sep 24 14:25:17 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 24 Sep 2018 18:25:17 +0000 Subject: [Archivesspace_Users_Group] seeking community input for JIRA tickets Message-ID: Good afternoon, all! The Development Prioritization subteam is seeking community input/discussion on the following JIRA tickets: https://archivesspace.atlassian.net/browse/ANW-534 As a user, I want to directly edit / modify my user account and password We are seeking information on which fields should not be editable by the user. See additional comments in the ticket. https://archivesspace.atlassian.net/browse/ANW-436 As a repository manager, I want to be able to bulk delete Events using a checkbox on the Browse Events page. Since Events can be automatically generated as a sort of verification measure, we are interested in hearing whether they should be delete-able. https://archivesspace.atlassian.net/browse/ANW-297 Move Biographical / Historical Note from Additional Description Collapsed Menu Currently, the Collection Overview view of the PUI has only DACS required notes in the main view. You have to click on "Additional Description" or "Expand All" in order to access Biog-Hist. One question is whether the "Additional Description" should be replaced by just having "see all/see less" for all elements, or just move the biog-hist only out or make its own accordion, or possibly enable users with repository manager levels of permission to set a customizable order of finding aid elements (this last option would require a new ticket). Thoughts? Please feel free to share your thoughts by commenting and voting on the tickets and/or this member list! Lydia Chair, Dev. Pri. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Mon Sep 24 14:49:55 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Mon, 24 Sep 2018 18:49:55 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 In-Reply-To: References: Message-ID: Reminder - Join us for the ArchivesSpace Implementation Buddies info webinar on Wednesday, September 26! Details: http://archivesspace.org/archives/3175 Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_uac-bounces at lyralists.lyrasis.org On Behalf Of Christine Kim Sent: Wednesday, September 12, 2018 2:15 PM Subject: [Archivesspace_uac] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 ArchivesSpace Implementation Buddies When: Wednesday, September 26, 2018 Time: 1:00 p.m. - 1:30 p.m. EST (10:00 a.m. - 10:30 a.m. PST) Where: Webinar at https://zoom.us/j/834400938 Dial-in only option: 669-900-6833 or 646-876-9923 - Meeting ID is 834-400-938 International numbers available: https://zoom.us/u/iZNgWlhI No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Please note: We are using Zoom Video Communications to host this webinar, taking a break from Adobe Connect temporarily. If this is your first time using Zoom, please join this Test meeting to make sure you are all set up: https://zoom.us/test Webinar description: At our Annual Member Forum, we announced our idea to facilitate an "implementation buddy" program to help connect our ArchivesSpace community members so we can work through challenges together. We shared our thoughts on how stepping up as a mentor comes with the expectations that may exceed the bandwidth that most of our extremely busy community currently may have. Our vision for "implementation buddies" aims to lift that burden of mentorship while connecting members who can help each other out in balanced harmony. We are offering a webinar on September 26 at 1-1:30pm ET (10-10:30am PT) to provide a background on the ASpace Implementation Buddy program as well as a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form (link to announcement) and the Implementation Buddy sign-up sheet. Please feel free to bring any questions you have. Presenters: Christine Kim (Community Engagement Coordinator, ArchivesSpace) is responsible for facilitating community activities, and is inspired by the incredible projects, initiatives, and accomplishments of the ASpace community. Who should attend: Everyone interested in learning about the ArchivesSpace implementation buddy program, as well as anyone who wants a deeper look at the member directory submission form. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Mon Sep 24 15:09:28 2018 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Mon, 24 Sep 2018 19:09:28 +0000 Subject: [Archivesspace_Users_Group] exporting bioghist attached to agent with EAD Message-ID: Speaking of the Biographical/Historical Note (I've already voted for ANW-297), does anyone know if there is a method or existing ticket for getting a Biographical/Historical Note that is attached to an Agent record (as the creator), and is associated with a particular Resource, to export with a Resource record's EAD? We keep our bioghist notes attached to our Agents, which is okay for displaying in the PUI but does not get carried along with EAD or PDF exports. I'm not sure about OAI-PMH as we don't yet have it configured on 2.4.1. Right now our workaround is to export EAD and then copy/paste in the bioghist. Fortunately this doesn't come up all that much! Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Monday, September 24, 2018 1:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] seeking community input for JIRA tickets Good afternoon, all! The Development Prioritization subteam is seeking community input/discussion on the following JIRA tickets: https://archivesspace.atlassian.net/browse/ANW-534 As a user, I want to directly edit / modify my user account and password We are seeking information on which fields should not be editable by the user. See additional comments in the ticket. https://archivesspace.atlassian.net/browse/ANW-436 As a repository manager, I want to be able to bulk delete Events using a checkbox on the Browse Events page. Since Events can be automatically generated as a sort of verification measure, we are interested in hearing whether they should be delete-able. https://archivesspace.atlassian.net/browse/ANW-297 Move Biographical / Historical Note from Additional Description Collapsed Menu Currently, the Collection Overview view of the PUI has only DACS required notes in the main view. You have to click on "Additional Description" or "Expand All" in order to access Biog-Hist. One question is whether the "Additional Description" should be replaced by just having "see all/see less" for all elements, or just move the biog-hist only out or make its own accordion, or possibly enable users with repository manager levels of permission to set a customizable order of finding aid elements (this last option would require a new ticket). Thoughts? Please feel free to share your thoughts by commenting and voting on the tickets and/or this member list! Lydia Chair, Dev. Pri. -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Mon Sep 24 15:51:05 2018 From: luftsche at usc.edu (Susan Luftschein) Date: Mon, 24 Sep 2018 19:51:05 +0000 Subject: [Archivesspace_Users_Group] Another MARC export glitch? Message-ID: Hi all, I think I may have found another glitch in the new MARC export. See attached. There is no subordinate name in this agent record, so why is subfield b showing up in the export, nor is there a relationship term in that agent record, so how is that subfield 4 showing up? Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 2278 bytes Desc: Capture.PNG URL: From mkottman at ku.edu Tue Sep 25 10:33:04 2018 From: mkottman at ku.edu (Kottman, Miloche) Date: Tue, 25 Sep 2018 14:33:04 +0000 Subject: [Archivesspace_Users_Group] Another MARC export glitch? In-Reply-To: References: Message-ID: <75f04410a49e444f81757d0585b20f73@ex13-ell-cr-12.home.ku.edu> I can confirm that we're seeing this behavior also (version 2.5). It happens for corporate bodies used as a subject or as a creator: Subject: Kansas Federation of Women's Clubs, subject. local Creator: Lawrence Music Club (Lawrence, Kan.), creator. --Miloche ****************************** Miloche Kottman Head of Cataloging and Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Susan Luftschein Sent: Monday, September 24, 2018 2:51 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Another MARC export glitch? Hi all, I think I may have found another glitch in the new MARC export. See attached. There is no subordinate name in this agent record, so why is subfield b showing up in the export, nor is there a relationship term in that agent record, so how is that subfield 4 showing up? Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Tue Sep 25 11:16:07 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Tue, 25 Sep 2018 10:16:07 -0500 Subject: [Archivesspace_Users_Group] Display issues for records with multiple date records attached Message-ID: Hello all, We have noticed the behavior documented in this bug regarding multiple date records attached to a record not displaying in the staff interface: https://archivesspace.atlassian.net/browse/ANW-172 We've also noticed this in a number of other places, including: PDFs exported from the public interface, though the dates (perhaps redundantly) since the dates are also displayed below the title plus the first date: [image: Screen Shot 2018-09-25 at 9.48.52 AM.png] The record tree in the public interface: [image: Screen Shot 2018-09-25 at 10.02.48 AM.png] Search results in the public interface: [image: Screen Shot 2018-09-25 at 10.07.34 AM.png] There may be more places as well. Is this the same bug as ANW-172? Should this be reported there or are all the places this happens to be considered separate bugs? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-25 at 9.48.52 AM.png Type: image/png Size: 75641 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-25 at 10.02.48 AM.png Type: image/png Size: 204265 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-09-25 at 10.07.34 AM.png Type: image/png Size: 85190 bytes Desc: not available URL: From mmims at library.rochester.edu Tue Sep 25 11:34:40 2018 From: mmims at library.rochester.edu (Mims, Miranda) Date: Tue, 25 Sep 2018 15:34:40 +0000 Subject: [Archivesspace_Users_Group] Extent Calculator Message-ID: Hi Everyone, We've just updated from 1.5.1 to 2.3.2. In this new version, we no longer have extent calculating capability. Is there a separate plug-in for this function? Thanks, Miranda Miranda Mims Special Collections Archivist for Discovery & Access Department of Rare Books, Special Collections, and Preservation River Campus Libraries 585.276.7495 mmims at library.rochester.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Tue Sep 25 12:14:11 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Tue, 25 Sep 2018 16:14:11 +0000 Subject: [Archivesspace_Users_Group] Modifying user account and passwords Message-ID: Lydia, all - ANW-534 could introduce challenges for our users and workflows. We use LDAP, and would want to prevent users from modifying usernames or passwords in the archivesspace UI. Could user account editing be configurable, to accommodate LDAP workflows? For example, perhaps this could be configurable to admin users only, or on/off entirely. It could be helpful for admins to be able to edit usernames in the UI, but not necessarily all staff users. Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Monday, September 24, 2018 2:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] seeking community input for JIRA tickets Good afternoon, all! The Development Prioritization subteam is seeking community input/discussion on the following JIRA tickets: https://archivesspace.atlassian.net/browse/ANW-534 As a user, I want to directly edit / modify my user account and password We are seeking information on which fields should not be editable by the user. See additional comments in the ticket. https://archivesspace.atlassian.net/browse/ANW-436 As a repository manager, I want to be able to bulk delete Events using a checkbox on the Browse Events page. Since Events can be automatically generated as a sort of verification measure, we are interested in hearing whether they should be delete-able. https://archivesspace.atlassian.net/browse/ANW-297 Move Biographical / Historical Note from Additional Description Collapsed Menu Currently, the Collection Overview view of the PUI has only DACS required notes in the main view. You have to click on "Additional Description" or "Expand All" in order to access Biog-Hist. One question is whether the "Additional Description" should be replaced by just having "see all/see less" for all elements, or just move the biog-hist only out or make its own accordion, or possibly enable users with repository manager levels of permission to set a customizable order of finding aid elements (this last option would require a new ticket). Thoughts? Please feel free to share your thoughts by commenting and voting on the tickets and/or this member list! Lydia Chair, Dev. Pri. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Tue Sep 25 12:33:56 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Tue, 25 Sep 2018 16:33:56 +0000 Subject: [Archivesspace_Users_Group] Modifying user account and passwords Message-ID: <7069AD17-5FDF-4AEB-B88C-3D164497C971@lib.msu.edu> Hi Nancy, Thanks for your feedback! Ed Busch added your idea into the JIRA ticket. https://archivesspace.atlassian.net/browse/ANW-534 Keeping the username static makes a lot of sense. On a tangential note, for people who are using LDAP, how do you handle people who aren?t affiliated with your institution? We sometimes have volunteers help with data entry, so it would be great to know of a workaround for them. Thanks, all! Lydia From: on behalf of "Kennedy, Nancy" Reply-To: Archivesspace Users Group Date: Tuesday, September 25, 2018 at 12:14 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Modifying user account and passwords Lydia, all ? ANW-534 could introduce challenges for our users and workflows. We use LDAP, and would want to prevent users from modifying usernames or passwords in the archivesspace UI. Could user account editing be configurable, to accommodate LDAP workflows? For example, perhaps this could be configurable to admin users only, or on/off entirely. It could be helpful for admins to be able to edit usernames in the UI, but not necessarily all staff users. Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Monday, September 24, 2018 2:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] seeking community input for JIRA tickets Good afternoon, all! The Development Prioritization subteam is seeking community input/discussion on the following JIRA tickets: https://archivesspace.atlassian.net/browse/ANW-534 As a user, I want to directly edit / modify my user account and password We are seeking information on which fields should not be editable by the user. See additional comments in the ticket. https://archivesspace.atlassian.net/browse/ANW-436 As a repository manager, I want to be able to bulk delete Events using a checkbox on the Browse Events page. Since Events can be automatically generated as a sort of verification measure, we are interested in hearing whether they should be delete-able. https://archivesspace.atlassian.net/browse/ANW-297 Move Biographical / Historical Note from Additional Description Collapsed Menu Currently, the Collection Overview view of the PUI has only DACS required notes in the main view. You have to click on ?Additional Description? or ?Expand All? in order to access Biog-Hist. One question is whether the ?Additional Description? should be replaced by just having ?see all/see less? for all elements, or just move the biog-hist only out or make its own accordion, or possibly enable users with repository manager levels of permission to set a customizable order of finding aid elements (this last option would require a new ticket). Thoughts? Please feel free to share your thoughts by commenting and voting on the tickets and/or this member list! Lydia Chair, Dev. Pri. From trthorn2 at ncsu.edu Tue Sep 25 12:40:19 2018 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Tue, 25 Sep 2018 12:40:19 -0400 Subject: [Archivesspace_Users_Group] Modifying user account and passwords In-Reply-To: <7069AD17-5FDF-4AEB-B88C-3D164497C971@lib.msu.edu> References: <7069AD17-5FDF-4AEB-B88C-3D164497C971@lib.msu.edu> Message-ID: I believe that if you use LDAP for authentication it can still fall back to the standard database authentication (where you set the user's password within ArchivesSpace). The 'admin' user is authenticated this way. On Tue, Sep 25, 2018 at 12:34 PM Tang, Lydia wrote: > Hi Nancy, > Thanks for your feedback! Ed Busch added your idea into the JIRA ticket. > https://archivesspace.atlassian.net/browse/ANW-534 Keeping the username > static makes a lot of sense. > On a tangential note, for people who are using LDAP, how do you handle > people who aren?t affiliated with your institution? We sometimes have > volunteers help with data entry, so it would be great to know of a > workaround for them. > Thanks, all! > Lydia > > From: on behalf > of "Kennedy, Nancy" > Reply-To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Date: Tuesday, September 25, 2018 at 12:14 PM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Modifying user account and passwords > > Lydia, all ? > ANW-534 could introduce challenges for our users and workflows. We use > LDAP, and would want to prevent users from modifying usernames or passwords > in the archivesspace UI. > > Could user account editing be configurable, to accommodate LDAP > workflows? For example, perhaps this could be configurable to admin users > only, or on/off entirely. It could be helpful for admins to be able to > edit usernames in the UI, but not necessarily all staff users. > > Nancy > > > Nancy Kennedy > Smithsonian Institution > kennedyn at si.edu > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of > Tang, Lydia > Sent: Monday, September 24, 2018 2:25 PM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] seeking community input for JIRA > tickets > > Good afternoon, all! > The Development Prioritization subteam is seeking community > input/discussion on the following JIRA tickets: > https://archivesspace.atlassian.net/browse/ANW-534< > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D534&d=DwMFAg&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=-IeuoyGl2NFFkVZJ3tKexIDyUaWAAf4sznY-P36w05U&s=mcxvBd-5eO4Qrd9wHp0xBXNTanLDvP57oDOBt8XSnwU&e= > > > As a user, I want to directly edit / modify my user account and password > We are seeking information on which fields should not be editable by the > user. See additional comments in the ticket. > > https://archivesspace.atlassian.net/browse/ANW-436< > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D436&d=DwMFAg&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=-IeuoyGl2NFFkVZJ3tKexIDyUaWAAf4sznY-P36w05U&s=2gR402aPxREbhiaKUiLmczGMWGkYWXcmQIMkiZAwv1c&e= > > > As a repository manager, I want to be able to bulk delete Events using a > checkbox on the Browse Events page. > Since Events can be automatically generated as a sort of verification > measure, we are interested in hearing whether they should be delete-able. > > https://archivesspace.atlassian.net/browse/ANW-297< > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D297&d=DwMFAg&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=-IeuoyGl2NFFkVZJ3tKexIDyUaWAAf4sznY-P36w05U&s=X4sXE8EuiEj6hzDigoHZH_pUMacY0Q1-4n5glLaR8l4&e= > > > Move Biographical / Historical Note from Additional Description Collapsed > Menu > Currently, the Collection Overview view of the PUI has only DACS required > notes in the main view. You have to click on ?Additional Description? or > ?Expand All? in order to access Biog-Hist. One question is whether the > ?Additional Description? should be replaced by just having ?see all/see > less? for all elements, or just move the biog-hist only out or make its own > accordion, or possibly enable users with repository manager levels of > permission to set a customizable order of finding aid elements (this last > option would require a new ticket). > > Thoughts? Please feel free to share your thoughts by commenting and > voting on the tickets and/or this member list! > Lydia > Chair, Dev. Pri. > > _______________________________________________ > 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 KennedyN at si.edu Tue Sep 25 12:41:49 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Tue, 25 Sep 2018 16:41:49 +0000 Subject: [Archivesspace_Users_Group] Modifying user account and passwords In-Reply-To: <7069AD17-5FDF-4AEB-B88C-3D164497C971@lib.msu.edu> References: <7069AD17-5FDF-4AEB-B88C-3D164497C971@lib.msu.edu> Message-ID: We require everyone to have LDAP credentials (volunteers too) to log in and use any systems. If for some reason that couldn't work, I'd have the volunteer work in Excel or other txt file format. We have workflows to import data from CSV or spreadsheet templates. That covers most cases! -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Tuesday, September 25, 2018 12:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Modifying user account and passwords Hi Nancy, Thanks for your feedback! Ed Busch added your idea into the JIRA ticket. https://archivesspace.atlassian.net/browse/ANW-534 Keeping the username static makes a lot of sense. On a tangential note, for people who are using LDAP, how do you handle people who aren?t affiliated with your institution? We sometimes have volunteers help with data entry, so it would be great to know of a workaround for them. Thanks, all! Lydia From: on behalf of "Kennedy, Nancy" Reply-To: Archivesspace Users Group Date: Tuesday, September 25, 2018 at 12:14 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Modifying user account and passwords Lydia, all ? ANW-534 could introduce challenges for our users and workflows. We use LDAP, and would want to prevent users from modifying usernames or passwords in the archivesspace UI. Could user account editing be configurable, to accommodate LDAP workflows? For example, perhaps this could be configurable to admin users only, or on/off entirely. It could be helpful for admins to be able to edit usernames in the UI, but not necessarily all staff users. Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Monday, September 24, 2018 2:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] seeking community input for JIRA tickets Good afternoon, all! The Development Prioritization subteam is seeking community input/discussion on the following JIRA tickets: https://archivesspace.atlassian.net/browse/ANW-534 As a user, I want to directly edit / modify my user account and password We are seeking information on which fields should not be editable by the user. See additional comments in the ticket. https://archivesspace.atlassian.net/browse/ANW-436 As a repository manager, I want to be able to bulk delete Events using a checkbox on the Browse Events page. Since Events can be automatically generated as a sort of verification measure, we are interested in hearing whether they should be delete-able. https://archivesspace.atlassian.net/browse/ANW-297 Move Biographical / Historical Note from Additional Description Collapsed Menu Currently, the Collection Overview view of the PUI has only DACS required notes in the main view. You have to click on ?Additional Description? or ?Expand All? in order to access Biog-Hist. One question is whether the ?Additional Description? should be replaced by just having ?see all/see less? for all elements, or just move the biog-hist only out or make its own accordion, or possibly enable users with repository manager levels of permission to set a customizable order of finding aid elements (this last option would require a new ticket). Thoughts? Please feel free to share your thoughts by commenting and voting on the tickets and/or this member list! Lydia Chair, Dev. Pri. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From jrg5 at princeton.edu Tue Sep 25 14:36:25 2018 From: jrg5 at princeton.edu (James R Griffin III) Date: Tue, 25 Sep 2018 18:36:25 +0000 Subject: [Archivesspace_Users_Group] Event Outcome Problems Message-ID: Hello Everyone, Please forgive any misunderstandings on my part, as I'm relatively new to this software and the project. I'm currently working with an installation of ArchivesSpace which has been updated to 2.5.0, and I've encountered a problem in which Event "Outcome" values can be persisted into the database with NULL foreign keys: [archivesspace]> select count(e.id) from event as e where e.outcome_id IS NULL; +-------------+ | count(e.id) | +-------------+ | 14324 | +-------------+ Is this expected? When these are set as NULL, the corresponding enumeration_value cannot be retrieved for translation in the locale, leading to the following errors: translation missing: enumerations.event_outcome. ...where the tag following enumerations.event_outcome (normally some value like pass or fail, as found in https://github.com/archivesspace/archivesspace/blob/v2.5.0/common/locales/enums/en.yml#L442) is simply blank. Is this something which others have encountered before? Might this be an issue which must be addressed with database record cleaning for these NULL foreign keys? Thank you for your time and support. Sincerely, James Griffin -- Digital Infrastructure Developer Princeton University Library Princeton, NJ 08544 -------------- next part -------------- An HTML attachment was scrubbed... URL: From epyers at slv.vic.gov.au Tue Sep 25 23:18:08 2018 From: epyers at slv.vic.gov.au (Emily Pyers) Date: Wed, 26 Sep 2018 03:18:08 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 In-Reply-To: References: Message-ID: Hi Kim, I was just wondering if there was any chance the webinar might be recorded and distributed so international users who aren?t able to attend can get some further information on the program? I?m in Melbourne (AEST), and I know there are a couple of other Australian institutions using Aspace who might also be interested. Cheers, Emily Emily Pyers | Metadata & Archival Systems Specialist | Collection Resources In the office Monday, Wednesday - Friday 9.30am-3pm State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 T +61 3 8664 7368 | epyers at slv.vic.gov.au slv.vic.gov.au [http://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?5] [follow us] [SLV facebook] [SLV twitter] [SLV youtube] [SLV instagram] [RACV logo] From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, 25 September 2018 4:50 AM To: Archivesspace Users Group; Archivesspace Member Reps; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: Re: [Archivesspace_member_reps] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 Reminder ? Join us for the ArchivesSpace Implementation Buddies info webinar on Wednesday, September 26! Details: http://archivesspace.org/archives/3175 Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_uac-bounces at lyralists.lyrasis.org > On Behalf Of Christine Kim Sent: Wednesday, September 12, 2018 2:15 PM Subject: [Archivesspace_uac] Webinar Announcement: ArchivesSpace Implementation Buddies - September 26 ArchivesSpace Implementation Buddies When: Wednesday, September 26, 2018 Time: 1:00 p.m. ? 1:30 p.m. EST (10:00 a.m. ? 10:30 a.m. PST) Where: Webinar at https://zoom.us/j/834400938 Dial-in only option: 669-900-6833 or 646-876-9923 ? Meeting ID is 834-400-938 International numbers available: https://zoom.us/u/iZNgWlhI No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Please note: We are using Zoom Video Communications to host this webinar, taking a break from Adobe Connect temporarily. If this is your first time using Zoom, please join this Test meeting to make sure you are all set up: https://zoom.us/test Webinar description: At our Annual Member Forum, we announced our idea to facilitate an ?implementation buddy? program to help connect our ArchivesSpace community members so we can work through challenges together. We shared our thoughts on how stepping up as a mentor comes with the expectations that may exceed the bandwidth that most of our extremely busy community currently may have. Our vision for ?implementation buddies? aims to lift that burden of mentorship while connecting members who can help each other out in balanced harmony. We are offering a webinar on September 26 at 1-1:30pm ET (10-10:30am PT) to provide a background on the ASpace Implementation Buddy program as well as a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form (link to announcement) and the Implementation Buddy sign-up sheet. Please feel free to bring any questions you have. Presenters: Christine Kim (Community Engagement Coordinator, ArchivesSpace) is responsible for facilitating community activities, and is inspired by the incredible projects, initiatives, and accomplishments of the ASpace community. Who should attend: Everyone interested in learning about the ArchivesSpace implementation buddy program, as well as anyone who wants a deeper look at the member directory submission form. Questions? Please contact Kim at christine.kim at lyrasis.org This message and any attachment is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please delete all copies of the message and its attachments and notify the sender immediately. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Wed Sep 26 10:08:44 2018 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Wed, 26 Sep 2018 14:08:44 +0000 Subject: [Archivesspace_Users_Group] MARCxml importer Message-ID: Hi Everyone, I have over 1000 collection level MARC records that I'd like to import into ArchivesSpace as resource records. We've exported them from Aleph as MARCxml and made a number of adjustments in preparation for import. A couple of points of information: * Harvard has a custom requirement in our ASpace instance on the EADID field. It's needed in order to save the resource record and in a specific format. * We machine added those EADIDs into our MARCxml using the 555 field as this is the MARC field that ID goes (as part of our url to the finding aid). The problem, as I understand it, is that the ArchivesSpace importer for MARCxml doesn't include a mapping to the EADID field so that data gets dropped on import and then the job fails for the Harvard specified requirement. Does anyone have suggestions on how to start thinking through a solution? For me, the best solution is to adapt the importer, but I assume that's the most challenging or problematic. Thanks in advance for thoughts, Adrien Adrien Hilton Head of the Manuscript Section Houghton Library Harvard University Cambridge, MA 02138 adrien_hilton at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Wed Sep 26 10:35:41 2018 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Wed, 26 Sep 2018 10:35:41 -0400 Subject: [Archivesspace_Users_Group] MARCxml importer In-Reply-To: References: Message-ID: Hi Adrien, We recently imported our collection-level MARC records into AS. Lyrasis was contracted to do the import. They were able to make our requested custom tweaks to the MARC importer fairly easily, and I'd agree that that will likely be best solution for you. Unfortunately, I don't know how exactly they did so because we are hosted, but I think a place to start would be here: https://github.com/archivesspace/archivesspace/blob/fb02a77fa62d2dfad4b7984b627ecddf8f03eec0/backend/spec/lib_marcxml_converter_spec.rb Alternately, if you can temporarily disable the Harvard-specified requirement, you could copy the EAD IDs into some other MARC field that does import. Once the records are in, you could do an API call to move the EAD IDs where you want them, and then re-enable the requirement. Kevin On Wed, Sep 26, 2018 at 10:10 AM Hilton, Adrien wrote: > > Hi Everyone, > > > > I have over 1000 collection level MARC records that I?d like to import into ArchivesSpace as resource records. We?ve exported them from Aleph as MARCxml and made a number of adjustments in preparation for import. > > > > A couple of points of information: > > > > Harvard has a custom requirement in our ASpace instance on the EADID field. It?s needed in order to save the resource record and in a specific format. > > > > We machine added those EADIDs into our MARCxml using the 555 field as this is the MARC field that ID goes (as part of our url to the finding aid). > > > > The problem, as I understand it, is that the ArchivesSpace importer for MARCxml doesn?t include a mapping to the EADID field so that data gets dropped on import and then the job fails for the Harvard specified requirement. > > > > Does anyone have suggestions on how to start thinking through a solution? For me, the best solution is to adapt the importer, but I assume that?s the most challenging or problematic. > > > > Thanks in advance for thoughts, > > Adrien > > > > > > > > Adrien Hilton > > Head of the Manuscript Section > > Houghton Library > > Harvard University > > Cambridge, MA 02138 > > adrien_hilton at harvard.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 From jrc88 at cornell.edu Thu Sep 27 09:49:54 2018 From: jrc88 at cornell.edu (Jenn Colt) Date: Thu, 27 Sep 2018 13:49:54 +0000 Subject: [Archivesspace_Users_Group] Event Outcome Problems In-Reply-To: References: Message-ID: I'm seeing this as well when I make a new event but leave the outcome blank. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James R Griffin III Sent: Tuesday, September 25, 2018 2:36:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Event Outcome Problems Hello Everyone, Please forgive any misunderstandings on my part, as I'm relatively new to this software and the project. I'm currently working with an installation of ArchivesSpace which has been updated to 2.5.0, and I've encountered a problem in which Event "Outcome" values can be persisted into the database with NULL foreign keys: [archivesspace]> select count(e.id) from event as e where e.outcome_id IS NULL; +-------------+ | count(e.id) | +-------------+ | 14324 | +-------------+ Is this expected? When these are set as NULL, the corresponding enumeration_value cannot be retrieved for translation in the locale, leading to the following errors: translation missing: enumerations.event_outcome. ...where the tag following enumerations.event_outcome (normally some value like pass or fail, as found in https://github.com/archivesspace/archivesspace/blob/v2.5.0/common/locales/enums/en.yml#L442) is simply blank. Is this something which others have encountered before? Might this be an issue which must be addressed with database record cleaning for these NULL foreign keys? Thank you for your time and support. Sincerely, James Griffin -- Digital Infrastructure Developer Princeton University Library Princeton, NJ 08544 -------------- next part -------------- An HTML attachment was scrubbed... URL: From psutherland at amphilsoc.org Thu Sep 27 11:36:26 2018 From: psutherland at amphilsoc.org (Paul Sutherland) Date: Thu, 27 Sep 2018 11:36:26 -0400 Subject: [Archivesspace_Users_Group] Fwd: Re-ordering plugins In-Reply-To: References: Message-ID: Hi Christine and all, Just following up on ANW-373 to ask if there are still plans for this to be addressed this year? From the perspective of our day-to-day processors, it's perhaps the most pressing feature to add and we are very excited for it. Thank you, Paul Sutherland On Fri, Jun 29, 2018 at 1:47 PM Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hi Paul, > > > > I don?t know that anyone has done any plugins for either of these, but > there is feature request for the application for the one about where new > siblings get inserted: https://archivesspace.atlassian.net/browse/ANW-373. > It has been assigned to a developer, so I?m hopeful that it can get > addressed this summer for a future release. > > > > (Now if someone has created a plugin for this function (or bulk > reordering), we?d love to hear about it and consider it for the core code. > Please get in touch with Laney or me if that?s the case!) > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 > > 678-235-2905 > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Paul > Sutherland > *Sent:* Thursday, June 28, 2018 1:14 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Fwd: Re-ordering plugins > > > > Hi all, > > > > I am forwarding this as I do not think it sent to the list last time (I > did not see a message at all in my inbox, although I do see a copy on the > listserv archive). Apologies it if actually sent. > > > > Best, > > Paul > > > > > > ---------- Forwarded message ---------- > From: *Paul Sutherland* > Date: Fri, Jun 22, 2018 at 1:53 PM > Subject: Re-ordering plugins > To: archivesspace_users_group at lyralists.lyrasis.org > > Hi all, > > > > I have checked Awesome ArchivesSpace and can't see anything that looks > like this. Please let me know if I'm missing it. > > > > I am wondering if anyone has created plugins for: > > - bulk re-ordering records at the same level and with the same parent > (e.g. children of a series, either alphabetically or chronologically by > begin date); > - inserting new records as adjacent siblings of a currently selected > record (a functionality that Archivists' Toolkit had) > > Since moving from Archivists' Toolkit, it has become difficult to deal > with very large series that are not already arranged before entry, as all > new records go to the end of their level. Plugins for these operations > would help greatly with daily entry. > > > > Thank you for any assistance, > > Paul > > > > -- > > *Paul Sutherland* (he/his) > > Archivist > > Center for Native American and Indigenous Research > > American Philosophical Society > > 105 S. 5th Street, 2nd Floor > > Philadelphia, PA 19406 > > 215-440-3408 > > amphilsoc.org/library/CNAIR > > Browse our new Indigenous Subject Guide > > > and read our latest blog posts > > > Twitter: @paulssutherland > > > > > > -- > > *Paul Sutherland* (he/his) > > Archivist > > Center for Native American and Indigenous Research > > American Philosophical Society > > 105 S. 5th Street, 2nd Floor > > Philadelphia, PA 19406 > > 215-440-3408 > > amphilsoc.org/library/CNAIR > > Browse our new Indigenous Subject Guide > > > and read our latest blog posts > > > Twitter: @paulssutherland > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Paul Sutherland* (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -------------- 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: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: From buschedw at msu.edu Thu Sep 27 13:09:40 2018 From: buschedw at msu.edu (Busch, Ed) Date: Thu, 27 Sep 2018 17:09:40 +0000 Subject: [Archivesspace_Users_Group] preferences Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164AD1D1B@CAD-EX01.campusad.msu.edu> Hi- I've created global and repository preferences that aren't taking effect for users. Users are also getting an error when they try to create their own user preferences. Does anyone have an idea on what's going on? Ed Busch Electronic Records Archivist, MLIS MSU Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hilary.Clifford at aidshealth.org Thu Sep 27 16:59:16 2018 From: Hilary.Clifford at aidshealth.org (Hilary Clifford) Date: Thu, 27 Sep 2018 20:59:16 +0000 Subject: [Archivesspace_Users_Group] Adding a pre-created archival object to a resource Message-ID: <79FD3770-4DCC-4894-9F40-1273CC0CF89C@aidshealth.org> Hello ArchivesSpace community! I?m new to ArchivesSpace, and have to add already created archival objects to a new resource I have created- I know this is not usually the ordered process, but because of the archives I work worth I needed to retro-actively create collections. I am able to add the digital object but not all of the information within the archival object. Has anyone come across this situation? Thanks so much! Hilary Clifford AIDS Healthcare Foundation Senior Program Manager of Archives Public Health Division 1710 N La Brea Ave Los Angeles, CA 90046 323-436-8900 ext. 5844 Cell: 323-219-8613 [cid:image001.png at 01D374F8.58141960][cid:image002.png at 01D374F8.58141960] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13303 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 16387 bytes Desc: image002.png URL: From lcalahan at umn.edu Thu Sep 27 17:05:58 2018 From: lcalahan at umn.edu (Lisa Calahan) Date: Thu, 27 Sep 2018 16:05:58 -0500 Subject: [Archivesspace_Users_Group] Adding a pre-created archival object to a resource In-Reply-To: <79FD3770-4DCC-4894-9F40-1273CC0CF89C@aidshealth.org> References: <79FD3770-4DCC-4894-9F40-1273CC0CF89C@aidshealth.org> Message-ID: Hi Hilary, If you want to give me a call, I can walk you through the process. It'd be easier than to type out the instructions and answer related questions :) My work number is in the signature below. On Thu, Sep 27, 2018 at 3:59 PM, Hilary Clifford < Hilary.Clifford at aidshealth.org> wrote: > Hello ArchivesSpace community! > > > > I?m new to ArchivesSpace, and have to add already created archival objects > to a new resource I have created- I know this is not usually the ordered > process, but because of the archives I work worth I needed to > retro-actively create collections. I am able to add the digital object but > not all of the information within the archival object. Has anyone come > across this situation? > > > > Thanks so much! > > > > Hilary Clifford > > AIDS Healthcare Foundation > > Senior Program Manager of Archives > > Public Health Division > > 1710 N La Brea Ave > > Los Angeles, CA 90046 > > 323-436-8900 ext. 5844 > > Cell: 323-219-8613 > > [image: cid:image001.png at 01D374F8.58141960][image: > cid:image002.png at 01D374F8.58141960] > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Pronouns: She/her/hers Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library, Suite 315 222-21st Ave. S. Minneapolis MN 55455 Phone: 612.626.2531 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13303 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 16387 bytes Desc: not available URL: From s.innes at auckland.ac.nz Fri Sep 28 02:00:32 2018 From: s.innes at auckland.ac.nz (Stephen Innes) Date: Fri, 28 Sep 2018 06:00:32 +0000 Subject: [Archivesspace_Users_Group] FW: ArchivesSpace Startup Error In-Reply-To: <8B52C081-0BD2-4735-9839-18F587CB7704@auckland.ac.nz> References: <8B52C081-0BD2-4735-9839-18F587CB7704@auckland.ac.nz> Message-ID: <7d42ca250d0a46b19fcd2ad78297343a@uxcn13-tdc-c.UoA.auckland.ac.nz> Dear Colleagues We are upgrading to v2.5.0 and about the launch the PUI, but our IT colleague has struck an error message on startup. Can anyone help us fix the problem? Regards, Stephen Innes Stephen Innes Special Collections Manager General Library, Te Herenga M?tauranga Wh?nui The University of Auckland Private Bag 92019 Auckland 1142 New Zealand Telephone (649) 373-7599 ext. 88062 | Fax (649) 373-7565 Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library Online exhibition: Special Collections First World War Centenary 2014-2018 Hi Steven On starting AS v2.5.0 I get the following error: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with `lock_jars` command load error: org/bouncycastle/bcpkix-jdk15on/1.56/bcpkix-jdk15on-1.56 -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory (LoadError) Backtrace for gem load error is: uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:348:in `do_require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:255:in `block in require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:297:in `require_jar_with_block' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:254:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:357:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:13:in `
' The full log is: tail: archivesspace.out: file truncated OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb Sep 28, 2018 3:32:45 PM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Sep 28, 2018 3:32:45 PM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/data/app/archivesspace/wars/backend.war!/ to /tmp/JettyContext4428490565332842972/webapp Sep 28, 2018 3:32:45 PM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Sep 28, 2018 3:32:45 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext4428490565332842972/webapp/},/data/app/archivesspace/wars/backend.war Sep 28, 2018 3:32:45 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext4428490565332842972/webapp/},/data/app/archivesspace/wars/backend.war Sep 28, 2018 3:32:45 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Sep 28, 2018 3:32:45 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb load error: racc/cparse-jruby -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/racc/parser.rb:196:in `' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/racc/parser.rb:187:in `' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/racc/parser.rb:181:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib/nokogiri/css/parser.rb:1:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib/nokogiri/css/parser.rb:7:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib/nokogiri/css.rb:1:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib/nokogiri/css.rb:5:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib/nokogiri.rb:1:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib/nokogiri.rb:40:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with `lock_jars` command load error: org/bouncycastle/bcpkix-jdk15on/1.56/bcpkix-jdk15on-1.56 -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory (LoadError) Backtrace for gem load error is: uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:348:in `do_require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:255:in `block in require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:297:in `require_jar_with_block' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:254:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:357:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:13:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: --- System jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Time: 2018-09-28 15:32:50 +1200 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemRequireError: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with `lock_jars` command load error: org/bouncycastle/bcpkix-jdk15on/1.56/bcpkix-jdk15on-1.56 -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory (LoadError) Backtrace for gem load error is: uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:348:in `do_require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:255:in `block in require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:297:in `require_jar_with_block' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:254:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:357:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:13:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: block in require at /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:85 each at org/jruby/RubyArray.java:1734 block in require at /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76 each at org/jruby/RubyArray.java:1734 require at /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65 require at /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114
at /tmp/JettyContext4428490565332842972/webapp/WEB-INF/app/main.rb:2 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 block in (root) at /tmp/JettyContext4428490565332842972/webapp/WEB-INF/config.ru:1 instance_eval at org/jruby/RubyBasicObject.java:1687 (root) at /tmp/JettyContext4428490565332842972/webapp/WEB-INF/config.ru:4
at uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: /data/app/archivesspace/gems Gem.path: /home/archivesspace/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared /data/app/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 rake-12.3.1 concurrent-ruby-1.0.5-java i18n-0.9.1 minitest-5.11.3 thread_safe-0.3.6-java tzinfo-1.2.5 activesupport-5.0.1 atomic-1.0.1-java backports-3.11.2 bcrypt-3.1.7-java builder-3.2.3 ffi-1.9.23-java childprocess-0.9.0 choice-0.2.0 multipart-post-1.2.0 faraday-0.14.0 faraday_middleware-0.12.2 jdbc-derby-10.12.1.1 jruby-jars-9.1.8.0 jruby-rack-1.1.21 json-1.8.6-java json-schema-1.0.10 rack-1.6.9 mizuno-0.6.11 multi_json-1.13.1 net-http-persistent-2.8 net-ldap-0.16.1 nokogiri-1.8.1-java oai-0.4.0 rack-protection-1.5.5 sequel-4.20.0 rack-session-sequel-0.0.1 rack-test-1.0.0 rjack-jackson-1.8.11.0-java rubyzip-1.2.1 rufus-lru-1.0.5 rufus-scheduler-2.0.24 saxerator-0.9.2 saxon-xslt-0.8.2.1-java tilt-2.0.8 sinatra-1.4.7 sinatra-contrib-1.4.7 tzinfo-data-1.2018.4 warbler-2.0.4 zip-zip-0.3 --- Bundler Bundler.bundle_path: /data/app/archivesspace/gems Bundler.root: /tmp/JettyContext4428490565332842972/webapp/WEB-INF Gemfile: /tmp/JettyContext4428490565332842972/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] bin_path = /data/app/archivesspace/gems/gems/bundler-1.16.1/exe/bundle gemfile = /tmp/JettyContext4428490565332842972/webapp/WEB-INF/Gemfile --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 52a75c12 equals = err = java.io.PrintStream at 98712fa filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 3b8d2abe logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 37c74e4e rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/tmp/JettyContext4428490565332842972/webapp/},/data/app/archivesspace/wars/backend.war throw_init_exception = false Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with `lock_jars` command load error: org/bouncycastle/bcpkix-jdk15on/1.56/bcpkix-jdk15on-1.56 -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory (LoadError) Backtrace for gem load error is: uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:348:in `do_require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:255:in `block in require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:297:in `require_jar_with_block' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:254:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:357:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:13:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: from /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:85:in `block in require' from org/jruby/RubyArray.java:1734:in `each' from /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' from org/jruby/RubyArray.java:1734:in `each' from /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' from /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' from /tmp/JettyContext4428490565332842972/webapp/WEB-INF/app/main.rb:2:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from /tmp/JettyContext4428490565332842972/webapp/WEB-INF/config.ru:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1687:in `instance_eval' from /tmp/JettyContext4428490565332842972/webapp/WEB-INF/config.ru:4:in `(root)' from uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131) at launcher.launcher.invokeOther148:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:358) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:195) at launcher.launcher.invokeOther269:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131) at launcher.launcher.invokeOther454:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.jruby.ir.Compiler$1.load(Compiler.java:95) at org.jruby.Ruby.runScript(Ruby.java:827) at org.jruby.Ruby.runNormally(Ruby.java:746) at org.jruby.Ruby.runNormally(Ruby.java:764) at org.jruby.Ruby.runFromMain(Ruby.java:577) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemRequireError) There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with `lock_jars` command load error: org/bouncycastle/bcpkix-jdk15on/1.56/bcpkix-jdk15on-1.56 -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory (LoadError) Backtrace for gem load error is: uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:348:in `do_require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:255:in `block in require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:297:in `require_jar_with_block' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:254:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jar_dependencies.rb:357:in `require_jar' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:13:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:961:in `require' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1734:in `each' /data/app/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:961:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' /data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: at RUBY.block in require(/data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:85) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1734) at RUBY.block in require(/data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1734) at RUBY.require(/data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65) at RUBY.require(/data/app/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114) at RUBY.
(/tmp/JettyContext4428490565332842972/webapp/WEB-INF/app/main.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.block in (root)(/tmp/JettyContext4428490565332842972/webapp/WEB-INF/config.ru:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1687) at RUBY.(root)(/tmp/JettyContext4428490565332842972/webapp/WEB-INF/config.ru:4) at RUBY.
(uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext4428490565332842972/webapp/},/data/app/archivesspace/wars/backend.war Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8089 Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Sep 28, 2018 3:32:50 PM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/data/app/archivesspace/wars/indexer.war!/ to /tmp/JettyContext4529338472015170330/webapp Sep 28, 2018 3:32:50 PM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /aspace-indexer, did not find org.apache.jasper.servlet.JspServlet Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/tmp/JettyContext4529338472015170330/webapp/},/data/app/archivesspace/wars/indexer.war Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/tmp/JettyContext4529338472015170330/webapp/},/data/app/archivesspace/wars/indexer.war Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Sep 28, 2018 3:32:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require': It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory --- System jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Time: 2018-09-28 15:32:51 +1200 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace LoadError: load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1 at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6 at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/base.rb:1 at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/base.rb:1 at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:1
at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:21 Simple at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:20 Backend at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:17 I18n at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:2
at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:1 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:1 require at org/jruby/RubyKernel.java:961 backend at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:19
at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:128 require at org/jruby/RubyKernel.java:961 load_path= at /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n.rb:43
at uri:classloader:/aspace_i18n.rb:7 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 block in (root) at /tmp/JettyContext4529338472015170330/webapp/WEB-INF/app/lib/indexer_common.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1687 (root) at /tmp/JettyContext4529338472015170330/webapp/WEB-INF/app/lib/indexer_common.rb:5
at uri:classloader:/jruby/kernel/kernel.rb:1 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:163
at launcher/launcher.rb:261 --- RubyGems Gem.dir: /data/app/archivesspace/gems Gem.path: /data/app/archivesspace/gems Activated gems: did_you_mean-1.0.1 rack-1.6.9 tilt-2.0.8 rack-protection-1.5.5 sinatra-1.4.7 atomic-1.0.1-java json-1.8.6-java concurrent-ruby-1.0.5-java i18n-0.9.1 jar-dependencies-0.3.10 psych-2.2.4-java --- Bundler undefined method `bundle_path' for Bundler:Module --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 7f53a31f equals = err = java.io.PrintStream at 98712fa filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 29d563bd logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 37c74e4e rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/aspace-indexer,file:/tmp/JettyContext4529338472015170330/webapp/},/data/app/archivesspace/wars/indexer.war throw_init_exception = false --- $LOAD_PATH: uri:classloader:/vendor/rack-1.6.8 /tmp/JettyContext4529338472015170330/webapp/WEB-INF /data/app/archivesspace/gems/gems/rack-1.6.9/lib /data/app/archivesspace/gems/gems/tilt-2.0.8/lib /data/app/archivesspace/gems/gems/rack-protection-1.5.5/lib /data/app/archivesspace/gems/gems/sinatra-1.4.7/lib /data/app/archivesspace/gems/gems/atomic-1.0.1-java/lib /data/app/archivesspace/gems/gems/json-1.8.6-java/lib /data/app/archivesspace/gems/gems/concurrent-ruby-1.0.5-java/lib /data/app/archivesspace/gems/gems/i18n-0.9.1/lib uri:classloader:/META-INF/jruby.home/lib/ruby/2.3/site_ruby uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1:in `
' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6:in `' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/base.rb:1:in `' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/base.rb:1:in `' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:1:in `' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:21:in `
' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:20:in `Simple' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:17:in `Backend' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:2:in `I18n' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:19:in `backend' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:128:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n.rb:43:in `load_path=' from uri:classloader:/aspace_i18n.rb:7:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from /tmp/JettyContext4529338472015170330/webapp/WEB-INF/app/lib/indexer_common.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1687:in `instance_eval' from /tmp/JettyContext4529338472015170330/webapp/WEB-INF/app/lib/indexer_common.rb:5:in `(root)' from uri:classloader:/jruby/kernel/kernel.rb:1:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:163:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:129) at launcher.launcher.invokeOther148:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:358) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:195) at launcher.launcher.invokeOther294:start_server(launcher/launcher.rb:163) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:163) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131) at launcher.launcher.invokeOther454:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.jruby.ir.Compiler$1.load(Compiler.java:95) at org.jruby.Ruby.runScript(Ruby.java:827) at org.jruby.Ruby.runNormally(Ruby.java:746) at org.jruby.Ruby.runNormally(Ruby.java:764) at org.jruby.Ruby.runFromMain(Ruby.java:577) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (LoadError) load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1) at RUBY.(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6) at RUBY.(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/base.rb:1) at RUBY.(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/base.rb:1) at RUBY.(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:1) at RUBY.
(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:21) at RUBY.Simple(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:20) at RUBY.Backend(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:17) at RUBY.I18n(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:2) at RUBY.
(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/backend/simple.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.backend(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:19) at RUBY.
(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n/config.rb:128) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.load_path=(/data/app/archivesspace/gems/gems/i18n-0.9.1/lib/i18n.rb:43) at RUBY.
(uri:classloader:/aspace_i18n.rb:7) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at uri_3a_classloader_3a_.META_minus_INF.jruby_dot_home.lib.ruby.stdlib.rubygems.core_ext.kernel_require.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.block in (root)(/tmp/JettyContext4529338472015170330/webapp/WEB-INF/app/lib/indexer_common.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1687) at RUBY.(root)(/tmp/JettyContext4529338472015170330/webapp/WEB-INF/app/lib/indexer_common.rb:5) at RUBY.
(uri:classloader:/jruby/kernel/kernel.rb:1) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:163) at launcher.launcher.
(launcher/launcher.rb:261) Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/tmp/JettyContext4529338472015170330/webapp/},/data/app/archivesspace/wars/indexer.war Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8091 Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Sep 28, 2018 3:32:52 PM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/data/app/archivesspace/wars/frontend.war!/ to /tmp/JettyContext3704697604768922350/webapp Sep 28, 2018 3:32:52 PM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext3704697604768922350/webapp/},/data/app/archivesspace/wars/frontend.war Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext3704697604768922350/webapp/},/data/app/archivesspace/wars/frontend.war Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Sep 28, 2018 3:32:52 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `require': It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory --- System jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Time: 2018-09-28 15:32:55 +1200 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rails.env = production --- Backtrace LoadError: load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6 require at org/jruby/RubyKernel.java:961
at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1 require at org/jruby/RubyKernel.java:961
at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1 require at org/jruby/RubyKernel.java:961
at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1 require at org/jruby/RubyKernel.java:961 (root) at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11 (root) at /data/app/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1
at /data/app/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:168
at launcher/launcher.rb:261 --- RubyGems Gem.dir: /data/app/archivesspace/gems Gem.path: /home/archivesspace/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared /data/app/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 rake-12.3.1 concurrent-ruby-1.0.5-java i18n-0.9.1 minitest-5.11.3 thread_safe-0.3.6-java tzinfo-1.2.5 activesupport-5.0.1 builder-3.2.3 erubis-2.7.0 nokogiri-1.8.1-java rails-dom-testing-2.0.3 loofah-2.0.3 rails-html-sanitizer-1.0.3 actionview-5.0.1 rack-2.0.4 rack-test-0.6.3 actionpack-5.0.1 nio4r-1.2.1-java websocket-extensions-0.1.3 websocket-driver-0.6.5-java actioncable-5.0.1 globalid-0.4.1 activejob-5.0.1 mini_mime-1.0.0 mail-2.7.0 actionmailer-5.0.1 activemodel-5.0.1 arel-7.1.4 activerecord-5.0.1 atomic-1.0.1-java ffi-1.9.23-java childprocess-0.9.0 choice-0.2.0 coffee-script-source-1.12.2 execjs-2.7.0 coffee-script-2.4.1 method_source-0.8.2 thor-0.20.0 railties-5.0.1 coffee-rails-4.2.1 commonjs-0.2.7 jquery-rails-4.3.1 jquery-ui-rails-6.0.1 jruby-jars-9.1.8.0 json-1.8.6-java json-schema-1.0.10 less-2.6.0 sprockets-3.7.1 tilt-2.0.8 less-rails-2.8.0 less-rails-bootstrap-3.3.5.0 mizuno-0.6.11 multi_json-1.13.1 multipart-post-1.2.0 net-http-persistent-2.8 sprockets-rails-2.3.3 rails-5.0.1 rb-fsevent-0.10.3 rb-inotify-0.9.10 rubyzip-1.2.1 sass-listen-4.0.0 sass-3.5.6 sass-rails-5.0.7 therubyrhino_jar-1.7.6 therubyrhino-2.0.4 tzinfo-data-1.2018.4 uglifier-3.0.4 zip-zip-0.3 --- Bundler Bundler.bundle_path: /data/app/archivesspace/gems Bundler.root: /tmp/JettyContext3704697604768922350/webapp/WEB-INF Gemfile: /tmp/JettyContext3704697604768922350/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] gemfile = /tmp/JettyContext3704697604768922350/webapp/WEB-INF/Gemfile bin_path = /data/app/archivesspace/gems/gems/bundler-1.16.1/exe/bundle --- JRuby-Rack Config compat_version = default_logger = org.jruby.rack.logging.StandardOutLogger at 5a35efac equals = err = java.io.PrintStream at 98712fa filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 58e9e852 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 37c74e4e rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/tmp/JettyContext3704697604768922350/webapp/},/data/app/archivesspace/wars/frontend.war throw_init_exception = false --- $LOAD_PATH: /data/app/archivesspace/gems/gems/bundler-1.16.1/lib /data/app/archivesspace/gems/gems/zip-zip-0.3/lib /data/app/archivesspace/gems/gems/uglifier-3.0.4/lib /data/app/archivesspace/gems/gems/tzinfo-data-1.2018.4/lib /data/app/archivesspace/gems/gems/therubyrhino-2.0.4/lib /data/app/archivesspace/gems/gems/therubyrhino_jar-1.7.6/jar /data/app/archivesspace/gems/gems/sass-rails-5.0.7/lib /data/app/archivesspace/gems/gems/sass-3.5.6/lib /data/app/archivesspace/gems/gems/sass-listen-4.0.0/lib /data/app/archivesspace/gems/gems/rubyzip-1.2.1/lib /data/app/archivesspace/gems/gems/rb-inotify-0.9.10/lib /data/app/archivesspace/gems/gems/rb-fsevent-0.10.3/lib /data/app/archivesspace/gems/gems/rails-5.0.1/lib /data/app/archivesspace/gems/gems/sprockets-rails-2.3.3/lib /data/app/archivesspace/gems/gems/net-http-persistent-2.8/lib /data/app/archivesspace/gems/gems/multipart-post-1.2.0/lib /data/app/archivesspace/gems/gems/multi_json-1.13.1/lib /data/app/archivesspace/gems/gems/mizuno-0.6.11/lib /data/app/archivesspace/gems/gems/less-rails-bootstrap-3.3.5.0/lib /data/app/archivesspace/gems/gems/less-rails-2.8.0/lib /data/app/archivesspace/gems/gems/tilt-2.0.8/lib /data/app/archivesspace/gems/gems/sprockets-3.7.1/lib /data/app/archivesspace/gems/gems/less-2.6.0/lib /data/app/archivesspace/gems/gems/json-schema-1.0.10/lib /data/app/archivesspace/gems/gems/json-1.8.6-java/lib /data/app/archivesspace/gems/gems/jruby-jars-9.1.8.0/lib /data/app/archivesspace/gems/gems/jquery-ui-rails-6.0.1/lib /data/app/archivesspace/gems/gems/jquery-rails-4.3.1/lib /data/app/archivesspace/gems/gems/commonjs-0.2.7/lib /data/app/archivesspace/gems/gems/coffee-rails-4.2.1/lib /data/app/archivesspace/gems/gems/railties-5.0.1/lib /data/app/archivesspace/gems/gems/thor-0.20.0/lib /data/app/archivesspace/gems/gems/method_source-0.8.2/lib /data/app/archivesspace/gems/gems/coffee-script-2.4.1/lib /data/app/archivesspace/gems/gems/execjs-2.7.0/lib /data/app/archivesspace/gems/gems/coffee-script-source-1.12.2/lib /data/app/archivesspace/gems/gems/choice-0.2.0/lib /data/app/archivesspace/gems/gems/childprocess-0.9.0/lib /data/app/archivesspace/gems/gems/ffi-1.9.23-java/lib /data/app/archivesspace/gems/gems/atomic-1.0.1-java/lib /data/app/archivesspace/gems/gems/activerecord-5.0.1/lib /data/app/archivesspace/gems/gems/arel-7.1.4/lib /data/app/archivesspace/gems/gems/activemodel-5.0.1/lib /data/app/archivesspace/gems/gems/actionmailer-5.0.1/lib /data/app/archivesspace/gems/gems/mail-2.7.0/lib /data/app/archivesspace/gems/gems/mini_mime-1.0.0/lib /data/app/archivesspace/gems/gems/activejob-5.0.1/lib /data/app/archivesspace/gems/gems/globalid-0.4.1/lib /data/app/archivesspace/gems/gems/actioncable-5.0.1/lib /data/app/archivesspace/gems/gems/websocket-driver-0.6.5-java/lib /data/app/archivesspace/gems/gems/websocket-extensions-0.1.3/lib /data/app/archivesspace/gems/gems/nio4r-1.2.1-java/lib /data/app/archivesspace/gems/gems/actionpack-5.0.1/lib /data/app/archivesspace/gems/gems/rack-test-0.6.3/lib /data/app/archivesspace/gems/gems/rack-2.0.4/lib /data/app/archivesspace/gems/gems/actionview-5.0.1/lib /data/app/archivesspace/gems/gems/rails-html-sanitizer-1.0.3/lib /data/app/archivesspace/gems/gems/loofah-2.0.3/lib /data/app/archivesspace/gems/gems/rails-dom-testing-2.0.3/lib /data/app/archivesspace/gems/gems/nokogiri-1.8.1-java/lib /data/app/archivesspace/gems/gems/erubis-2.7.0/lib /data/app/archivesspace/gems/gems/builder-3.2.3/lib /data/app/archivesspace/gems/gems/activesupport-5.0.1/lib /data/app/archivesspace/gems/gems/tzinfo-1.2.5/lib /data/app/archivesspace/gems/gems/thread_safe-0.3.6-java/lib /data/app/archivesspace/gems/gems/minitest-5.11.3/lib /data/app/archivesspace/gems/gems/i18n-0.9.1/lib /data/app/archivesspace/gems/gems/concurrent-ruby-1.0.5-java/lib /data/app/archivesspace/gems/gems/rake-12.3.1/lib uri:classloader:/META-INF/jruby.home/lib/ruby/2.3/site_ruby uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11:in `(root)' from /data/app/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1:in `(root)' from /data/app/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:168:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:129) at launcher.launcher.invokeOther148:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:191) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:378) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:227) at launcher.launcher.invokeOther308:start_server(launcher/launcher.rb:168) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:168) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131) at launcher.launcher.invokeOther454:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.jruby.ir.Compiler$1.load(Compiler.java:95) at org.jruby.Ruby.runScript(Ruby.java:827) at org.jruby.Ruby.runNormally(Ruby.java:746) at org.jruby.Ruby.runNormally(Ruby.java:764) at org.jruby.Ruby.runFromMain(Ruby.java:577) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (LoadError) load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.(root)(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11) at RUBY.(root)(/data/app/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1) at RUBY.
(/data/app/archivesspace/gems/gems/actionpack-5.0.1/lib/action_controller/railtie.rb:1) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:168) at launcher.launcher.
(launcher/launcher.rb:261) Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext3704697604768922350/webapp/},/data/app/archivesspace/wars/frontend.war Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8080 Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Sep 28, 2018 3:32:55 PM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/data/app/archivesspace/wars/public.war!/ to /tmp/JettyContext5642673766947546200/webapp Sep 28, 2018 3:32:55 PM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext5642673766947546200/webapp/},/data/app/archivesspace/wars/public.war Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext5642673766947546200/webapp/},/data/app/archivesspace/wars/public.war Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Sep 28, 2018 3:32:55 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `require': It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory --- System jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Time: 2018-09-28 15:32:57 +1200 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rails.env = production --- Backtrace LoadError: load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1 require at org/jruby/RubyKernel.java:961
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6 require at org/jruby/RubyKernel.java:961
at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1 require at org/jruby/RubyKernel.java:961 (root) at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1
at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1 require at org/jruby/RubyKernel.java:961 (root) at /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11 (root) at /tmp/JettyContext5642673766947546200/webapp/WEB-INF/config/application.rb:1
at /tmp/JettyContext5642673766947546200/webapp/WEB-INF/config/application.rb:3 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:173
at launcher/launcher.rb:261 --- RubyGems Gem.dir: /data/app/archivesspace/gems Gem.path: /home/archivesspace/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared /data/app/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 rake-12.3.1 concurrent-ruby-1.0.5-java i18n-0.9.1 minitest-5.11.3 thread_safe-0.3.6-java tzinfo-1.2.5 activesupport-5.0.1 builder-3.2.3 erubis-2.7.0 nokogiri-1.8.2-java rails-dom-testing-2.0.3 loofah-2.0.3 rails-html-sanitizer-1.0.3 actionview-5.0.1 rack-2.0.5 rack-test-0.6.3 actionpack-5.0.1 nio4r-1.2.1-java websocket-extensions-0.1.3 websocket-driver-0.6.5-java actioncable-5.0.1 globalid-0.4.1 activejob-5.0.1 mini_mime-1.0.0 mail-2.7.0 actionmailer-5.0.1 activemodel-5.0.1 arel-7.1.4 activerecord-5.0.1 atomic-1.0.1-java execjs-2.7.0 autoprefixer-rails-8.5.0 rb-fsevent-0.10.3 ffi-1.9.23-java rb-inotify-0.9.10 sass-listen-4.0.0 sass-3.5.6 bootstrap-sass-3.3.7 childprocess-0.9.0 choice-0.2.0 clipboard-rails-1.7.1 coffee-script-source-1.12.2 coffee-script-2.4.1 method_source-0.8.2 thor-0.20.0 railties-5.0.1 coffee-rails-4.2.1 font-awesome-sass-4.7.0 jquery-rails-4.3.3 json-1.8.6-java json-schema-1.0.10 mizuno-0.6.11 multipart-post-1.2.0 net-http-persistent-2.8 sprockets-3.7.1 sprockets-rails-2.3.3 rails-5.0.1 tilt-2.0.8 sass-rails-5.0.7 therubyrhino_jar-1.7.6 therubyrhino-2.0.4 turbolinks-source-5.1.0 turbolinks-5.1.1 tzinfo-data-1.2018.5 uglifier-3.0.4 --- Bundler Bundler.bundle_path: /data/app/archivesspace/gems Bundler.root: /tmp/JettyContext5642673766947546200/webapp/WEB-INF Gemfile: /tmp/JettyContext5642673766947546200/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] gemfile = /tmp/JettyContext5642673766947546200/webapp/WEB-INF/Gemfile bin_path = /data/app/archivesspace/gems/gems/bundler-1.16.1/exe/bundle --- JRuby-Rack Config compat_version = default_logger = org.jruby.rack.logging.StandardOutLogger at 51a6af38 equals = err = java.io.PrintStream at 98712fa filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 2350e46 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 37c74e4e rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/tmp/JettyContext5642673766947546200/webapp/},/data/app/archivesspace/wars/public.war throw_init_exception = false --- $LOAD_PATH: /data/app/archivesspace/gems/gems/bundler-1.16.1/lib /data/app/archivesspace/gems/gems/uglifier-3.0.4/lib /data/app/archivesspace/gems/gems/tzinfo-data-1.2018.5/lib /data/app/archivesspace/gems/gems/turbolinks-5.1.1/lib /data/app/archivesspace/gems/gems/turbolinks-source-5.1.0/lib /data/app/archivesspace/gems/gems/therubyrhino-2.0.4/lib /data/app/archivesspace/gems/gems/therubyrhino_jar-1.7.6/jar /data/app/archivesspace/gems/gems/sass-rails-5.0.7/lib /data/app/archivesspace/gems/gems/tilt-2.0.8/lib /data/app/archivesspace/gems/gems/rails-5.0.1/lib /data/app/archivesspace/gems/gems/sprockets-rails-2.3.3/lib /data/app/archivesspace/gems/gems/sprockets-3.7.1/lib /data/app/archivesspace/gems/gems/net-http-persistent-2.8/lib /data/app/archivesspace/gems/gems/multipart-post-1.2.0/lib /data/app/archivesspace/gems/gems/mizuno-0.6.11/lib /data/app/archivesspace/gems/gems/json-schema-1.0.10/lib /data/app/archivesspace/gems/gems/json-1.8.6-java/lib /data/app/archivesspace/gems/gems/jquery-rails-4.3.3/lib /data/app/archivesspace/gems/gems/font-awesome-sass-4.7.0/lib /data/app/archivesspace/gems/gems/coffee-rails-4.2.1/lib /data/app/archivesspace/gems/gems/railties-5.0.1/lib /data/app/archivesspace/gems/gems/thor-0.20.0/lib /data/app/archivesspace/gems/gems/method_source-0.8.2/lib /data/app/archivesspace/gems/gems/coffee-script-2.4.1/lib /data/app/archivesspace/gems/gems/coffee-script-source-1.12.2/lib /data/app/archivesspace/gems/gems/clipboard-rails-1.7.1/lib /data/app/archivesspace/gems/gems/choice-0.2.0/lib /data/app/archivesspace/gems/gems/childprocess-0.9.0/lib /data/app/archivesspace/gems/gems/bootstrap-sass-3.3.7/lib /data/app/archivesspace/gems/gems/sass-3.5.6/lib /data/app/archivesspace/gems/gems/sass-listen-4.0.0/lib /data/app/archivesspace/gems/gems/rb-inotify-0.9.10/lib /data/app/archivesspace/gems/gems/ffi-1.9.23-java/lib /data/app/archivesspace/gems/gems/rb-fsevent-0.10.3/lib /data/app/archivesspace/gems/gems/autoprefixer-rails-8.5.0/lib /data/app/archivesspace/gems/gems/execjs-2.7.0/lib /data/app/archivesspace/gems/gems/atomic-1.0.1-java/lib /data/app/archivesspace/gems/gems/activerecord-5.0.1/lib /data/app/archivesspace/gems/gems/arel-7.1.4/lib /data/app/archivesspace/gems/gems/activemodel-5.0.1/lib /data/app/archivesspace/gems/gems/actionmailer-5.0.1/lib /data/app/archivesspace/gems/gems/mail-2.7.0/lib /data/app/archivesspace/gems/gems/mini_mime-1.0.0/lib /data/app/archivesspace/gems/gems/activejob-5.0.1/lib /data/app/archivesspace/gems/gems/globalid-0.4.1/lib /data/app/archivesspace/gems/gems/actioncable-5.0.1/lib /data/app/archivesspace/gems/gems/websocket-driver-0.6.5-java/lib /data/app/archivesspace/gems/gems/websocket-extensions-0.1.3/lib /data/app/archivesspace/gems/gems/nio4r-1.2.1-java/lib /data/app/archivesspace/gems/gems/actionpack-5.0.1/lib /data/app/archivesspace/gems/gems/rack-test-0.6.3/lib /data/app/archivesspace/gems/gems/rack-2.0.5/lib /data/app/archivesspace/gems/gems/actionview-5.0.1/lib /data/app/archivesspace/gems/gems/rails-html-sanitizer-1.0.3/lib /data/app/archivesspace/gems/gems/loofah-2.0.3/lib /data/app/archivesspace/gems/gems/rails-dom-testing-2.0.3/lib /data/app/archivesspace/gems/gems/nokogiri-1.8.2-java/lib /data/app/archivesspace/gems/gems/erubis-2.7.0/lib /data/app/archivesspace/gems/gems/builder-3.2.3/lib /data/app/archivesspace/gems/gems/activesupport-5.0.1/lib /data/app/archivesspace/gems/gems/tzinfo-1.2.5/lib /data/app/archivesspace/gems/gems/thread_safe-0.3.6-java/lib /data/app/archivesspace/gems/gems/minitest-5.11.3/lib /data/app/archivesspace/gems/gems/i18n-0.9.1/lib /data/app/archivesspace/gems/gems/concurrent-ruby-1.0.5-java/lib /data/app/archivesspace/gems/gems/rake-12.3.1/lib uri:classloader:/META-INF/jruby.home/lib/ruby/2.3/site_ruby uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1:in `(root)' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1:in `
' from org/jruby/RubyKernel.java:961:in `require' from /data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11:in `(root)' from /tmp/JettyContext5642673766947546200/webapp/WEB-INF/config/application.rb:1:in `(root)' from /tmp/JettyContext5642673766947546200/webapp/WEB-INF/config/application.rb:3:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:173:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:129) at launcher.launcher.invokeOther148:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:191) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:378) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:227) at launcher.launcher.invokeOther321:start_server(launcher/launcher.rb:173) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:173) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:318) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:131) at launcher.launcher.invokeOther454:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.jruby.ir.Compiler$1.load(Compiler.java:95) at org.jruby.Ruby.runScript(Ruby.java:827) at org.jruby.Ruby.runNormally(Ruby.java:746) at org.jruby.Ruby.runNormally(Ruby.java:764) at org.jruby.Ruby.runFromMain(Ruby.java:577) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (LoadError) load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:6) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.
(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.(root)(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails/application.rb:1) at RUBY.
(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:1) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:961) at RUBY.(root)(/data/app/archivesspace/gems/gems/railties-5.0.1/lib/rails.rb:11) at RUBY.(root)(/tmp/JettyContext5642673766947546200/webapp/WEB-INF/config/application.rb:1) at RUBY.
(/tmp/JettyContext5642673766947546200/webapp/WEB-INF/config/application.rb:3) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:173) at launcher.launcher.
(launcher/launcher.rb:261) Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext5642673766947546200/webapp/},/data/app/archivesspace/wars/public.war Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8081 Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8888 Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Sep 28, 2018 3:32:57 PM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/data/app/archivesspace/wars/oai.war!/ to /tmp/JettyContext883674403228122161/webapp Sep 28, 2018 3:32:57 PM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext883674403228122161/webapp/},/data/app/archivesspace/wars/oai.war Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext883674403228122161/webapp/},/data/app/archivesspace/wars/oai.war Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.91-b14 on 1.8.0_91-b14 +jit [linux-x86_64] Sep 28, 2018 3:32:57 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /data/app/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/data/app/archivesspace/thread_dump_oai.txt' to trigger a thread dump Sep 28, 2018 3:32:58 PM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/tmp/JettyContext883674403228122161/webapp/},/data/app/archivesspace/wars/oai.war Sep 28, 2018 3:32:58 PM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8082 ************************************************************ Welcome to ArchivesSpace! You can now point your browser to http://localhost:8080 ************************************************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Sep 28 09:20:45 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 28 Sep 2018 13:20:45 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Startup Error In-Reply-To: <7d42ca250d0a46b19fcd2ad78297343a@uxcn13-tdc-c.UoA.auckland.ac.nz> References: <8B52C081-0BD2-4735-9839-18F587CB7704@auckland.ac.nz>, <7d42ca250d0a46b19fcd2ad78297343a@uxcn13-tdc-c.UoA.auckland.ac.nz> Message-ID: Are you running that on Windows or Linux? Are you sure that the source code wasn't downloaded by mistake? You'll want this release: https://github.com/archivesspace/archivesspace/releases/download/v2.5.0/archivesspace-v2.5.0.zip From shaune at Princeton.EDU Fri Sep 28 10:04:16 2018 From: shaune at Princeton.EDU (Shaun D. Ellis) Date: Fri, 28 Sep 2018 14:04:16 +0000 Subject: [Archivesspace_Users_Group] Event Outcome Problems Message-ID: <253EFE19-844E-4C04-8E45-7367A0073F3A@princeton.edu> This sounds like a bug to me. Is there some place other than this list where it should be reported? It seems to me that the solution is to place a database constraint on that field, so that NULL values can?t be used for foreign keys, but perhaps there is more to the issue? Shaun Ellis -- UX Web Developer / Frontend Engineer Princeton University Library Princeton, NJ 08544 From: on behalf of Jenn Colt Reply-To: Archivesspace Users Group Date: Thursday, September 27, 2018 at 9:54 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Event Outcome Problems I'm seeing this as well when I make a new event but leave the outcome blank. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James R Griffin III Sent: Tuesday, September 25, 2018 2:36:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Event Outcome Problems Hello Everyone, Please forgive any misunderstandings on my part, as I'm relatively new to this software and the project. I'm currently working with an installation of ArchivesSpace which has been updated to 2.5.0, and I've encountered a problem in which Event "Outcome" values can be persisted into the database with NULL foreign keys: [archivesspace]> select count(e.id) from event as e where e.outcome_id IS NULL; +-------------+ | count(e.id) | +-------------+ | 14324 | +-------------+ Is this expected? When these are set as NULL, the corresponding enumeration_value cannot be retrieved for translation in the locale, leading to the following errors: translation missing: enumerations.event_outcome. ...where the tag following enumerations.event_outcome (normally some value like pass or fail, as found in https://github.com/archivesspace/archivesspace/blob/v2.5.0/common/locales/enums/en.yml#L442) is simply blank. Is this something which others have encountered before? Might this be an issue which must be addressed with database record cleaning for these NULL foreign keys? Thank you for your time and support. Sincerely, James Griffin -- Digital Infrastructure Developer Princeton University Library Princeton, NJ 08544 -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.clem at wilkes.edu Fri Sep 28 10:10:16 2018 From: carl.clem at wilkes.edu (Eddie Clem) Date: Fri, 28 Sep 2018 10:10:16 -0400 Subject: [Archivesspace_Users_Group] New to ArchivesSpace and LDAP/public Interface Questions Message-ID: <40a158de15357e2db1f46fff774db573@mail.gmail.com> Good morning everyone! We are new to ArchivesSpace and migrated from Archon. Our network administrator has our data migrated and our resource and location records appear to be in working order in AS; however, we can?t seem to figure out how to setup the public catalog?where the public can search our collection. Does anyone have suggestions or instructions on how we can do that? Our network administrator has also followed all of the instructions for setting up LDAP, but we can?t seem to get it to accept a users credentials. Do we need to prepopulate/create users in AS before using LDAP? Is there an LDAP expert in the group who may be willing to help tell us what we may be doing incorrectly? J Thank you for any help! Eddie [image: vert1_BLUE_seal_wilkes] *Eddie Clem, MLS* Technical Services Librarian Acquisitions, Cataloging, & Systems E.S. Farley Library 84 W. South St., Wilkes-Barre, PA, 18766 Office: 570-408-4258 Fax: 570-408-7823 eddie.clem at wilkes.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 14733 bytes Desc: not available URL: From ltang5 at lib.msu.edu Fri Sep 28 10:24:31 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 28 Sep 2018 14:24:31 +0000 Subject: [Archivesspace_Users_Group] Event Outcome Problems In-Reply-To: <253EFE19-844E-4C04-8E45-7367A0073F3A@princeton.edu> References: <253EFE19-844E-4C04-8E45-7367A0073F3A@princeton.edu> Message-ID: <345A181B-C63F-44FB-9ADC-92D9F469CF17@lib.msu.edu> Hi all, James created a Jira ticket for this bug here: https://archivesspace.atlassian.net/browse/ANW-778 Thanks, James! Here is information on how to report bugs: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202056/How+to+Report+a+Bug Thanks for helping to make ArchivesSpace better! Lydia * On behalf of the Development Prioritization subteam From: on behalf of "Shaun D. Ellis" Reply-To: Archivesspace Users Group Date: Friday, September 28, 2018 at 10:04 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Event Outcome Problems This sounds like a bug to me. Is there some place other than this list where it should be reported? It seems to me that the solution is to place a database constraint on that field, so that NULL values can?t be used for foreign keys, but perhaps there is more to the issue? Shaun Ellis -- UX Web Developer / Frontend Engineer Princeton University Library Princeton, NJ 08544 From: on behalf of Jenn Colt Reply-To: Archivesspace Users Group Date: Thursday, September 27, 2018 at 9:54 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Event Outcome Problems I'm seeing this as well when I make a new event but leave the outcome blank. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James R Griffin III Sent: Tuesday, September 25, 2018 2:36:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Event Outcome Problems Hello Everyone, Please forgive any misunderstandings on my part, as I'm relatively new to this software and the project. I'm currently working with an installation of ArchivesSpace which has been updated to 2.5.0, and I've encountered a problem in which Event "Outcome" values can be persisted into the database with NULL foreign keys: [archivesspace]> select count(e.id) from event as e where e.outcome_id IS NULL; +-------------+ | count(e.id) | +-------------+ | 14324 | +-------------+ Is this expected? When these are set as NULL, the corresponding enumeration_value cannot be retrieved for translation in the locale, leading to the following errors: translation missing: enumerations.event_outcome. ...where the tag following enumerations.event_outcome (normally some value like pass or fail, as found in https://github.com/archivesspace/archivesspace/blob/v2.5.0/common/locales/enums/en.yml#L442) is simply blank. Is this something which others have encountered before? Might this be an issue which must be addressed with database record cleaning for these NULL foreign keys? Thank you for your time and support. Sincerely, James Griffin -- Digital Infrastructure Developer Princeton University Library Princeton, NJ 08544 From ndroark at anderson.edu Fri Sep 28 10:35:13 2018 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Fri, 28 Sep 2018 10:35:13 -0400 Subject: [Archivesspace_Users_Group] Unprocessed label on processed accessions Message-ID: Hello all, For some time we have been using Aspace for cataloging while using a legacy database for accessioning. We are now in the process of accessioning new materials in Aspace, but it is not working entirely as we expected. After an item is accessioned, we spawn one or multiple resources from the accession record. After the accession is fully cataloged and processed, we create a "Processed" event on the accession record. But the accession record still displays the Unprocessed label (see attached) and is categorized that way in reports. What am I missing? [image: image.png] *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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 6120 bytes Desc: not available URL: From KennedyN at si.edu Fri Sep 28 10:46:48 2018 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 28 Sep 2018 14:46:48 +0000 Subject: [Archivesspace_Users_Group] Agent merge error - event link rlshp Message-ID: All, Has anyone seen this error before? Solutions? In version 2.5, the agents merge function, results in record deletion errors. Some agents do merge successfully, but a handful have started to result in this error, below. After which staff cannot view or edit the to-be-merged agent and any linked resource records. Merging agent(s) could not complete: Record deletion failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace`.`event_link_rlshp`, CONSTRAINT `event_link_rlshp_ibfk_6` FOREIGN KEY (`agent_person_id`) REFERENCES `agent_person` (`id`)) Perhaps related to the other event foreign key thread? Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Sep 28 10:47:46 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 28 Sep 2018 14:47:46 +0000 Subject: [Archivesspace_Users_Group] Unprocessed label on processed accessions In-Reply-To: References: Message-ID: Hi Nic, I can?t speak to reports, but as for the ArchivesSpace Public User Interface, published accession records will always show up right now. In other words, until the ?Publish?? checkbox is not selected, it gets indexed in the PUI. We?ve just started publishing accession records in one of our repositories, and right now we have an extra step of unpublishing those records once an associated finding aid is published. So, it?s a manual process right now, but I agree that it would be great to have other logic handle this in more streamlined fashion. There were discussions about handling this differently when the PUI was updated with version 2.1, but since there were/are multiple ways to indicate that an accession is processed (we?re using the ?Processing Status? right now, rather than an event record, for instance), the decision at the time was just to rely on the ?publish? button. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nic Stanton-Roark Sent: Friday, 28 September, 2018 10:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Unprocessed label on processed accessions Hello all, For some time we have been using Aspace for cataloging while using a legacy database for accessioning. We are now in the process of accessioning new materials in Aspace, but it is not working entirely as we expected. After an item is accessioned, we spawn one or multiple resources from the accession record. After the accession is fully cataloged and processed, we create a "Processed" event on the accession record. But the accession record still displays the Unprocessed label (see attached) and is categorized that way in reports. What am I missing? [image.png] [http://www.anderson.edu/sites/default/files/inline-images/au-email-logo.gif] Nicholas Stanton-Roark | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 | ndroark at anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6120 bytes Desc: image001.png URL: From trthorn2 at ncsu.edu Fri Sep 28 10:50:54 2018 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Fri, 28 Sep 2018 10:50:54 -0400 Subject: [Archivesspace_Users_Group] New to ArchivesSpace and LDAP/public Interface Questions In-Reply-To: <40a158de15357e2db1f46fff774db573@mail.gmail.com> References: <40a158de15357e2db1f46fff774db573@mail.gmail.com> Message-ID: I can answer the second part: Yes, the user needs to be created in ArchivesSpace before being able to log in, even with LDAP authentication enabled. You can log in as the 'admin' user using the password set in config/config.rb in the AppConfig[:default_admin_password] setting (default password is 'admin' - but it's a good idea to change that after logging in). Once logged in as admin you can create users and assign them to groups. You will still need to assign a password but the user will be able to log in with their LDAP password instead. On Fri, Sep 28, 2018 at 10:10 AM Eddie Clem wrote: > Good morning everyone! We are new to ArchivesSpace and migrated from > Archon. Our network administrator has our data migrated and our resource > and location records appear to be in working order in AS; however, we can?t > seem to figure out how to setup the public catalog?where the public can > search our collection. Does anyone have suggestions or instructions on how > we can do that? > > > > Our network administrator has also followed all of the instructions for > setting up LDAP, but we can?t seem to get it to accept a users credentials. > Do we need to prepopulate/create users in AS before using LDAP? Is there an > LDAP expert in the group who may be willing to help tell us what we may be > doing incorrectly? J > > > > Thank you for any help! > > > > Eddie > > > > [image: vert1_BLUE_seal_wilkes] > > > > *Eddie Clem, MLS* > Technical Services Librarian > > Acquisitions, Cataloging, & Systems > E.S. Farley Library > 84 W. South St., Wilkes-Barre, PA, 18766 > > Office: 570-408-4258 Fax: 570-408-7823 > eddie.clem at wilkes.edu > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 14733 bytes Desc: not available URL: From ndroark at anderson.edu Fri Sep 28 10:52:12 2018 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Fri, 28 Sep 2018 10:52:12 -0400 Subject: [Archivesspace_Users_Group] Top Container autocomplete issue Message-ID: Hello all, Have encountered a bug that I can't find described anywhere. The Top Container autocomplete drop-down no longer returns any results on *new* accessions/records (but still works in older records). The browse function can still locate the appropriate container, but this is not an option in Rapid Data Entry. The Agent Link autocomplete drop down still works as before. Has anyone encountered a similar issue? *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 smithkr at mit.edu Fri Sep 28 12:22:10 2018 From: smithkr at mit.edu (Kari R Smith) Date: Fri, 28 Sep 2018 16:22:10 +0000 Subject: [Archivesspace_Users_Group] New to ArchivesSpace and LDAP/public Interface Questions In-Reply-To: References: <40a158de15357e2db1f46fff774db573@mail.gmail.com> Message-ID: <29F559819ACA9A4FBF208407D4B63ABB0195D24C58@OC11expo28.exchange.mit.edu> Also, Note that no one needs to login for the Public User Interface ? it is publically open on the Web if you have it running on the open network / Web. The LDAP is for logging into ArchivesSpace as a User (for staff side.) So, the LDAP functionality is not necessary to implement for your Libraries? patrons to access the public ?catalog? of your collections in ArchivesSpace. If I am incorrect about this, someone lease correct me! Kari From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Trevor Thornton Sent: Friday, September 28, 2018 10:51 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] New to ArchivesSpace and LDAP/public Interface Questions I can answer the second part: Yes, the user needs to be created in ArchivesSpace before being able to log in, even with LDAP authentication enabled. You can log in as the 'admin' user using the password set in config/config.rb in the AppConfig[:default_admin_password] setting (default password is 'admin' - but it's a good idea to change that after logging in). Once logged in as admin you can create users and assign them to groups. You will still need to assign a password but the user will be able to log in with their LDAP password instead. On Fri, Sep 28, 2018 at 10:10 AM Eddie Clem > wrote: Good morning everyone! We are new to ArchivesSpace and migrated from Archon. Our network administrator has our data migrated and our resource and location records appear to be in working order in AS; however, we can?t seem to figure out how to setup the public catalog?where the public can search our collection. Does anyone have suggestions or instructions on how we can do that? Our network administrator has also followed all of the instructions for setting up LDAP, but we can?t seem to get it to accept a users credentials. Do we need to prepopulate/create users in AS before using LDAP? Is there an LDAP expert in the group who may be willing to help tell us what we may be doing incorrectly? ? Thank you for any help! Eddie [vert1_BLUE_seal_wilkes] Eddie Clem, MLS Technical Services Librarian Acquisitions, Cataloging, & Systems E.S. Farley Library 84 W. South St., Wilkes-Barre, PA, 18766 Office: 570-408-4258 Fax: 570-408-7823 eddie.clem at wilkes.edu _______________________________________________ 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 Christine.Kim at lyrasis.org Fri Sep 28 14:37:18 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 28 Sep 2018 18:37:18 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - September 2018 Message-ID: [ASpaceOrgHome.jpg] September 2018 Update The recordings from our Annual Member Forum in Washington D.C. are now available on our YouTube channel! Special thanks to Atlas Systems for recording and editing this footage. We are also ramping up our effort to get the new ArchivesSpace Member Directory out to you very soon, and we're excited to share more information on how the new ArchivesSpace Implementation Buddies program can help our community collaborate. We also have updates on the upcoming Kansas City Regional Forum, as well as an online forum to look forward to next year! Read on for more news! Development We're working on the next release of ArchivesSpace and expect to have a release candidate out in early October. This release will include accessibility improvements to both the public user interface and staff interface, an RTF option for reports, and a number of small improvements to the interfaces and the underlying infrastructure. We expect to have one more release before the end of 2018. We're currently determining what is likely to be included and updating the roadmap. 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. ArchivesSpace Member Directory We are thrilled to announce our latest effort to provide information on how our community is using ArchivesSpace! We are compiling an ArchivesSpace Member Directory to bring together information about our diverse ArchivesSpace member community and use of the ArchivesSpace application. We hope the compiled directory will help you identify others in similar situations or facing similar challenges to your own as well as provide a way for all of us to better engage each other for questions, ideas, and insights. The information collected will be shared only with ArchivesSpace members. Aside from publicly available information about institutions like names and locations, information about the use of ArchivesSpace will be shared only for those who consent to have it included. The submission form for the ArchivesSpace Member Directory is available here: https://tinyurl.com/aspace-directory. Most questions are optional. Please feel free to leave blank fields for anything you cannot answer or do not feel comfortable answering. A digital copy of the ArchivesSpace Member Directory will be distributed to all member representatives within the next couple of weeks. Please email us at ArchivesSpaceHome at lyrasis.org if you have any questions. ArchivesSpace Implementation Buddies Thank you to all who joined the info webinar on the ArchivesSpace Implementation Buddies program on September 26, in which we shared our goal to facilitate an "implementation buddy" program to help connect our ArchivesSpace community members so we can work through challenges together. In this webinar, we provided a detailed overview on how you can get involved, including a walkthrough of the ArchivesSpace Member Directory form and the Implementation Buddy sign-up sheet. Resources from the webinar are now available: http://archivesspace.org/archives/3183. You are welcome to submit your individual interest to be an "implementation buddy" through this Implementation Buddy sign-up sheet. A digital listing of all interested implementation buddies will be regularly circulated through email to individuals who have submitted their interest through this sign-up sheet. If you have any questions, please contact Christine Kim at christine.kim at lyrasis.org. Feedback on Webinars & Ideas for the Future We are interested in hearing your feedback on ArchivesSpace webinars -- What do you enjoy about the webinars? How can we improve them? How does the schedule work for you? These are some of the questions we ask, as well as an opportunity to provide insight into potential themes and topics we should explore in the future. This will be an ongoing survey. Please share your thoughts with us when you have a chance. https://tinyurl.com/aspace-webinarsurvey Open Members Call on Zoom, October 25, 2-3pm ET (11-noon PT) Please save the date for our next informal open call, coming up on October 25 at 2-3pm ET (11-noon PT). Open calls provide an opportunity to hear updates from each other and encourage group discussion. It's a space to surface news, ideas, and challenges. You will be able to join by either computer or phone. An announcement with call in details will be sent out shortly, along with a pre-survey to generate discussion topics. Please email Kim at christine.kim at lyrasis.org if you have any questions. We look forward to "seeing" you there! Annual Member Forum in Washington D.C. We're thrilled to share that the recordings from the Annual Member Forum are now available! Special thanks to Atlas Systems for providing this service! * Recordings: All recordings are available through the ArchivesSpace Member Forum 2018 playlist on our YouTube channel. * Please note: Each presentation is also linked through the wiki program page! * Evaluation: Please take a moment to provide your feedback and help us improve our future programs by submitting this survey: https://www.surveymonkey.com/r/K8R7BYS Regional Forum updates Planning for our Fall regional forum is under way. We are also exploring an online forum for the Winter season. Here are some of the most relevant news, dates, and links to keep you up to date on all the activity! Upcoming: Kansas City Regional Forum: November 30, 2018 Hang onto your hats! We're excited to announce the Kansas City Regional Forum! Location: Midwest Genealogy Center in Independence, MO Date: November 30, 2018 (Friday) We'll be sending out a formal announcement next week, which will include a call for presenter submissions. Registration information will follow shortly. Upcoming: ArchivesSpace Online Forum: Winter (February 2019) We are thrilled about all the opportunities we had to get together in person through our regional forums this past year! With this momentum, we'd like to explore new ways our community can collaborate, communicate, and engage with each other through an online forum! All community members are welcome to participate! However, we would love to focus on themes that are especially relevant to our small and very small community members, including our lone arrangers. Would you like to participate in a Working Group to help shape the program content for the online forum? Community members from institutions of all sizes are welcome, but we especially encourage our small and very small members to participate as we build this program. Response requested by October 31. Email Christine Kim at christine.kim at lyrasis.org. If you have any questions (or ideas) related to the regional forums, feel free to email Christine Kim at christine.kim at lyrasis.org. The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. We look forward to having the content shaped by our community. New Stories on the Blog In User Insights (http://archivesspace.org/archives/category/user-insights), Kelly Spring (Access Archivist, East Carolina University) provides an update in the blog series "Arrr-chivesSpace Migration" to provide insight into the migration process at ECU. Follow along throughout their two-year journey! We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Christine Kim at christine.kim at lyrasis.org. Membership Update We are excited to welcome our newest members to our community! Our new members since August 31 include: * The Museum of Flight (Seattle, WA) * Stephens College (Columbia, MO) As of September 28, we have 362 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: image003.jpg Type: image/jpeg Size: 20006 bytes Desc: image003.jpg URL: From luftsche at usc.edu Fri Sep 28 18:45:14 2018 From: luftsche at usc.edu (Susan Luftschein) Date: Fri, 28 Sep 2018 22:45:14 +0000 Subject: [Archivesspace_Users_Group] Another MARC export glitch? In-Reply-To: <75f04410a49e444f81757d0585b20f73@ex13-ell-cr-12.home.ku.edu> References: <75f04410a49e444f81757d0585b20f73@ex13-ell-cr-12.home.ku.edu> Message-ID: And here's another one (see attached). It seems that if you hit enter at the end of a note text, the MARC export automatically inserts a period. Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kottman, Miloche Sent: Tuesday, September 25, 2018 7:33 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Another MARC export glitch? I can confirm that we're seeing this behavior also (version 2.5). It happens for corporate bodies used as a subject or as a creator: Subject: Kansas Federation of Women's Clubs, subject. local Creator: Lawrence Music Club (Lawrence, Kan.), creator. --Miloche ****************************** Miloche Kottman Head of Cataloging and Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Susan Luftschein Sent: Monday, September 24, 2018 2:51 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Another MARC export glitch? Hi all, I think I may have found another glitch in the new MARC export. See attached. There is no subordinate name in this agent record, so why is subfield b showing up in the export, nor is there a relationship term in that agent record, so how is that subfield 4 showing up? Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 2444 bytes Desc: Capture.PNG URL: From Christine.Kim at lyrasis.org Sun Sep 30 14:28:25 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Sun, 30 Sep 2018 18:28:25 +0000 Subject: [Archivesspace_Users_Group] Thank you from ArchivesSpace! Message-ID: [cid:image003.jpg at 01D458B0.B21D73B0] Dear ArchivesSpace community, Thanks for sharing five years of ArchivesSpace with us since our v1.0.0 release on September 30, 2013! Our community's incredibly collaborative spirit, generosity, and creativity have inspired so much. We look forward to working together on the next five years of ArchivesSpace! P.S. In the spirit of celebrating, we'd love to hear why you choose to support ArchivesSpace. Share your story at https://goo.gl/forms/xf8YJvlfK4XxXbZt1 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 28255 bytes Desc: image003.jpg URL: