From scheirw at newschool.edu Sat Aug 1 14:00:55 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Sat, 1 Aug 2020 14:00:55 -0400 Subject: [Archivesspace_Users_Group] embedding digital object thumbnails in PUI Message-ID: Dear ASpace Community, We have recently begun working in a development instance of ASpace v2.8. I am able to successfully display the generic digital object link in a resource record: [image: Screenshot_1.png] However, after attempting variations on the instructions provided here to replace the generic button with a thumbnail button, I've been unsuccessful in successfully embedding a thumbnail. Instead I get this: [image: Screenshot_2.png] I've tried following the instructions for adding 2 file versions of the URI--the last one with the setting XLink Show Attribute=embed. I've also tried a single URI with the XLink Show Attribute=embed -- neither of these options work. Might there be a PUI configuration setting that needs to be changed from the default in order to enable the thumbnail functionality. I'd appreciate any guidance you can offer. Many thanks, Wendy ____________________________________ WENDY SCHEIR *DIRECTOR* 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_1.png Type: image/png Size: 79624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_2.png Type: image/png Size: 80927 bytes Desc: not available URL: From mark.custer at yale.edu Sat Aug 1 19:47:48 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Sat, 1 Aug 2020 23:47:48 +0000 Subject: [Archivesspace_Users_Group] embedding digital object thumbnails in PUI In-Reply-To: References: Message-ID: Wendy, I just tried things out in the sandbox, and those instructions still appear to work (although they could certainly be updated!). Here's an example that I just added: http://test.archivesspace.org/repositories/2/archival_objects/22461 (and on the staff side, http://test.archivesspace.org/staff/digital_objects/752#tree::digital_object_752) In your second screenshot, it looks like the link might be active but the thumbnail image is unable to load. Is the URL that you're using for the image accessible from anywhere? Do the 2 URLs in the above digital object work in your instance? Last, I'm not sure about this, but I think that ASpace might just try to embed a thumbnail if the file extension is a jpeg or a gif. I thought this also happened in the staff interface, but I don't see that behavior in the sandbox, so I could be mistaken about that. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Wendy Scheir Sent: Saturday, August 1, 2020 2:00 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] embedding digital object thumbnails in PUI Dear ASpace Community, We have recently begun working in a development instance of ASpace v2.8. I am able to successfully display the generic digital object link in a resource record: [Screenshot_1.png] However, after attempting variations on the instructions provided here to replace the generic button with a thumbnail button, I've been unsuccessful in successfully embedding a thumbnail. Instead I get this: [Screenshot_2.png] I've tried following the instructions for adding 2 file versions of the URI--the last one with the setting XLink Show Attribute=embed. I've also tried a single URI with the XLink Show Attribute=embed -- neither of these options work. Might there be a PUI configuration setting that needs to be changed from the default in order to enable the thumbnail functionality. I'd appreciate any guidance you can offer. Many thanks, Wendy ____________________________________ WENDY SCHEIR DIRECTOR [https://docs.google.com/uc?export=download&id=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o&revid=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ] 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_1.png Type: image/png Size: 79624 bytes Desc: Screenshot_1.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_2.png Type: image/png Size: 80927 bytes Desc: Screenshot_2.png URL: From scheirw at newschool.edu Sun Aug 2 10:22:35 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Sun, 2 Aug 2020 10:22:35 -0400 Subject: [Archivesspace_Users_Group] embedding digital object thumbnails in PUI In-Reply-To: References: Message-ID: Mark, That worked! I think you may be right about the file extension. And excellent choice of image, by the way. Thanks so much, Wendy On Sat, Aug 1, 2020 at 7:48 PM Custer, Mark wrote: > Wendy, > > I just tried things out in the sandbox, and those instructions still > appear to work (although they could certainly be updated!). > > Here's an example that I just added: > http://test.archivesspace.org/repositories/2/archival_objects/22461 (and > on the staff side, > http://test.archivesspace.org/staff/digital_objects/752#tree::digital_object_752 > ) > > In your second screenshot, it looks like the link might be active but the > thumbnail image is unable to load. Is the URL that you're using for the > image accessible from anywhere? Do the 2 URLs in the above digital object > work in your instance? > > Last, I'm not sure about this, but I think that ASpace might just try to > embed a thumbnail if the file extension is a jpeg or a gif. I thought this > also happened in the staff interface, but I don't see that behavior in the > sandbox, so I could be mistaken about that. > > Mark > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Wendy Scheir > *Sent:* Saturday, August 1, 2020 2:00 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] embedding digital object > thumbnails in PUI > > Dear ASpace Community, > > We have recently begun working in a development instance of ASpace v2.8. I > am able to successfully display the generic digital object link in a > resource record: > > [image: Screenshot_1.png] > > However, after attempting variations on the instructions provided here > > to replace the generic button with a thumbnail button, I've been > unsuccessful in successfully embedding a thumbnail. Instead I get this: > > [image: Screenshot_2.png] > > I've tried following the instructions for adding 2 file versions of the > URI--the last one with the setting XLink Show Attribute=embed. I've also > tried a single URI with the XLink Show Attribute=embed -- neither of these > options work. > > Might there be a PUI configuration setting that needs to be changed from > the default in order to enable the thumbnail functionality. > > I'd appreciate any guidance you can offer. > > Many thanks, > Wendy > > ____________________________________ > > WENDY SCHEIR > *DIRECTOR* > > 66 5TH AVENUE, NEW YORK, NY 10011 > scheirw at newschool.edu > > T 212.229.5942 x2888 > > Explore the Archives > > | Digital Collections from the Archives > > | New School Histories > > | @tnsarchives > > > > _______________________________________________ > 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: Screenshot_1.png Type: image/png Size: 79624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_2.png Type: image/png Size: 80927 bytes Desc: not available URL: From ph448 at cam.ac.uk Mon Aug 3 01:57:07 2020 From: ph448 at cam.ac.uk (Peter Heiner) Date: Mon, 3 Aug 2020 06:57:07 +0100 Subject: [Archivesspace_Users_Group] Survey on API usage In-Reply-To: References: Message-ID: <20200803055707.5libmmwhyfncs7le@axolotl> Dear Adrien, Can you please send me the text? Thanks, p Hilton, Adrien wrote on 2020-07-30 19:30:24: > Apologies, the wiki page for background info is restricted, and permissions are at a much higher level. If folks are interested, feel free to reach out and I can share the text with you individually. > > Best wishes, > Adrien > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Hilton, Adrien > Sent: Thursday, July 30, 2020 1:58 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Survey on API usage > > Dear Colleagues, > > At Harvard Library, our Library Technology Services unit is exploring how to support usage of the ArchivesSpace API. We've compiled a brief survey that we're hoping you can fill out. It will take about 20-30 minutes to complete. Your responses will be incredibly useful in helping us to establish sustainable models for maintenance and support. > > https://docs.google.com/forms/d/e/1FAIpQLSd_-Tx8xllx-vvVrTgBHKGhQ3XvgxZriZ_dni_bbJugHBoX1A/viewform?usp=sf_link > > You can find background information about the project here: https://wiki.harvard.edu/confluence/pages/viewpage.action?pageId=254280364 > > Responses by August 14th would be wonderful! > > Thanks in advance, > Adrien > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From jgd1 at williams.edu Tue Aug 4 08:36:30 2020 From: jgd1 at williams.edu (Drmacich, Jessika) Date: Tue, 4 Aug 2020 08:36:30 -0400 Subject: [Archivesspace_Users_Group] looking for digital object component Message-ID: Dear all, ArchivesSpace is throwing some errors when I run the validation script. I was able to remove many of the errors, but I'm still unable to locate the following even when I add the path to the url. Any tips on finding this digital object component? Record not found in index: /repositories/2/digital_object_components/817 *Jessika Drmacich * *Records Manager & Digital Resources Archivist * *Williams College Libraries* *Special Collections* *413-597-4725 (o)* *she/her/hers* *Please Note: Due to COVID-19 library services have changed. See **the library?s webpage for information on how to access collections and services. I am now working from home and I will be checking email regularly. I?m also available for virtual consultations via GoogleMeet.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Tue Aug 4 17:36:03 2020 From: cory_nimer at byu.edu (Cory Nimer) Date: Tue, 4 Aug 2020 21:36:03 +0000 Subject: [Archivesspace_Users_Group] Technical Subcommittee on Encoded Archival Standards annual meeting Message-ID: The Technical Subcommittee on Encoded Archival Standards is holding an open working meeting on Thursday, August 13, 2020 at 9 AM PDT / 10 AM MDT / 11 AM CDT / 12 PM EDT / 5 PM BST / 6 PM CEST/ 2 AM Friday AEST (https://sched.co/dQd6). The meeting is open for all to attend, and will cover our new outreach work, the on-going revision of Encoded Archival Context--Corporate bodies, Persons, and Families (EAC-CPF), and an update on current Encoded Archival Description (EAD) work. We will provide updates on ongoing initiatives and will answer questions from attendees. The agenda for the meeting is as follows: * Welcome * Administrative updates * Standard models * EAC-CPF revision updates * Upcoming EAD revisions * Outreach and communications For security reasons, attendees must register in advance to attend. Please complete the SAA registration form at https://zoom.us/meeting/register/tJEsd-Cupz8pHdfjGcIf9XNholrPhQ9rogbB. We look forward to sharing more about the current efforts of the subcommittee. Cory Nimer University Archivist Brigham Young University Provo, UT -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Tue Aug 4 19:01:12 2020 From: cory_nimer at byu.edu (Cory Nimer) Date: Tue, 4 Aug 2020 23:01:12 +0000 Subject: [Archivesspace_Users_Group] Migration data/indexing error Message-ID: Colleagues, We are currently working on a test migration from ArchivesSpace 2.5.1 to 2.7.1 and have run into an indexing issue once the migration is complete. The error message we are seeing is: Jul 10, 2020 3:45:39 PM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {add=[/repositories/14/archival_objects/247222, /repositories/14/archival_objects/247223, /repositories/14/archival_objects/247224, /repositories/14/archival_objects/247225, /repositories/14/archival_objects/247226, /repositories/14/archival_objects/247227, /repositories/14/archival_objects/247228, /repositories/14/archival_objects/247229, /repositories/14/archival_objects/247230, /repositories/14/archival_objects/247231, ... (25 adds)]} 0 23 E, [2020-07-10T15:45:39.030803 #3667] ERROR -- : Thread-2602: Failure in Staff Indexer worker thread: undefined method `[]' for nil:NilClass E, [2020-07-10T15:45:39.040422 #3667] ERROR -- : Thread-2016: /srv/archivesspace-2.7.1-stg/archivesspace/data/tmp/jetty-0.0.0.0-10091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/indexer_common.rb:510:in `block in configure_doc_rules' Checking the data in the staff side, it appears that references to one top container were changed during the migration, and as a result the indexing for the PUI fails and keeps repeating. The error also seems to prevent us from correcting the error through the staff interface. Re-running the migration produced a similar result. Has anyone encountered this error during their migration process? Looking at previous postings led us to suspect problems with orphan records, but after testing it appears this is not the issue here. Any suggestions would be greatly appreciated. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Wed Aug 5 10:48:56 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 5 Aug 2020 14:48:56 +0000 Subject: [Archivesspace_Users_Group] Feedback form for ArchivesSpace antiracism and inclusion ideas now available Message-ID: <9A59E3DB-DFF0-4007-BA88-3AE42DA983FD@lyrasis.org> Dear ArchivesSpace community, Thank you to all who have been contributing thoughts and suggestions to our continuing discussions around how ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive over the last few months. We announced at the Annual Forum yesterday that we've compiled the many ideas into a feedback form that will help guide some decisions about next steps. All ArchivesSpace users and community members are welcome to comment on these ideas or contribute new ideas. We are fortunate that we have received many excellent suggestions; you do not have to comment on all suggestions unless you want to. The feedback form is available at https://www.surveymonkey.com/r/NQWT6JQ. Some ideas may be fairly simple to implement, others may require considerable cooperation and discussion across the community, including the involvement of the ArchivesSpace Governance Board. The feedback you provide will help us work together to make as much progress as we can on these issues. Please submit your feedback form responses by August 28 if you can. If you would like to reach out about this form, ideas, or next steps, please contact us at ArchivesSpaceHome at lyrasis.org at any time. We welcome your participation in any form. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From buschedw at msu.edu Wed Aug 5 14:52:03 2020 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 5 Aug 2020 18:52:03 +0000 Subject: [Archivesspace_Users_Group] temporary location Message-ID: <1BA6FA8C-E6A4-4AA4-81C5-C4A8FF605D75@msu.edu> I?m trying to use the temporary location feature in ASpace and have a question. In Create Location, I can select the temporary location check box but the Temporary selection box is un-selectable. The Controlled Value List: Location Temporary (location_temporary) is populated with values. Ideas? Ed Busch -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Wed Aug 5 15:55:25 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Wed, 5 Aug 2020 15:55:25 -0400 Subject: [Archivesspace_Users_Group] linking FROM digital object TO archival object record Message-ID: Hello, Is it possible in the SUI to create a link, while inside an unlinked individual DO record, to an archival object record? Many thanks, Wendy ____________________________________ WENDY SCHEIR *DIRECTOR* 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Aug 6 09:43:28 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 6 Aug 2020 13:43:28 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Friday cancelled this week Message-ID: Dear ArchivesSpace Users, Our regular Friday break with ArchivesSpace will be cancelled this week since many of us are attending ArchivesSpace Annual Forum and SAA activities during this time. We will resume our Friday breaks with ArchivesSpace next Friday, August 14th at noon ET. Thank you to everyone who joined us last week for a great chat. We look forward to seeing you again next Friday. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From mmwisner at fas.harvard.edu Thu Aug 6 14:17:20 2020 From: mmwisner at fas.harvard.edu (Wisner, Melanie) Date: Thu, 6 Aug 2020 18:17:20 +0000 Subject: [Archivesspace_Users_Group] API Message-ID: Do you all know if the API is governed by an on/off switch in ASpace, like the PUI (and by default set one way or the other), or has to be created? Thanks! Melanie Melanie Wisner (she / her / hers) Accessioning Archivist Houghton Library Harvard University 617-384-7373 | mmwisner at fas.harvard.edu Building an Accessible Future | Houghton Library Renovation -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Thu Aug 6 15:08:03 2020 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Thu, 6 Aug 2020 19:08:03 +0000 Subject: [Archivesspace_Users_Group] API In-Reply-To: References: Message-ID: <07210101-D3FE-4118-B6CF-405B3645D3AE@harvard.edu> It is not ? the API is fundamentally required for the application to function at all, so it?s more or less always going to be running if any component is running. On a separate note, many installations don?t necessarily _expose_ it; the API by default is run so that it?s only accessible to other things on the same computer (technically speaking, served on a port that?s not exposed externally) -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: on behalf of "Wisner, Melanie" Reply-To: Archivesspace Users Group Date: Thursday, August 6, 2020 at 2:17 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] API Do you all know if the API is governed by an on/off switch in ASpace, like the PUI (and by default set one way or the other), or has to be created? Thanks! Melanie Melanie Wisner (she / her / hers) Accessioning Archivist Houghton Library Harvard University 617-384-7373 | mmwisner at fas.harvard.edu Building an Accessible Future | Houghton Library Renovation -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmwisner at fas.harvard.edu Thu Aug 6 15:12:24 2020 From: mmwisner at fas.harvard.edu (Wisner, Melanie) Date: Thu, 6 Aug 2020 19:12:24 +0000 Subject: [Archivesspace_Users_Group] API In-Reply-To: <07210101-D3FE-4118-B6CF-405B3645D3AE@harvard.edu> References: , <07210101-D3FE-4118-B6CF-405B3645D3AE@harvard.edu> Message-ID: Thanks, Dave, for your forebearance in addressing this question! Great details. Melanie ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mayo, Dave Sent: Thursday, August 6, 2020 3:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] API It is not ? the API is fundamentally required for the application to function at all, so it?s more or less always going to be running if any component is running. On a separate note, many installations don?t necessarily _expose_ it; the API by default is run so that it?s only accessible to other things on the same computer (technically speaking, served on a port that?s not exposed externally) -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: on behalf of "Wisner, Melanie" Reply-To: Archivesspace Users Group Date: Thursday, August 6, 2020 at 2:17 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] API Do you all know if the API is governed by an on/off switch in ASpace, like the PUI (and by default set one way or the other), or has to be created? Thanks! Melanie Melanie Wisner (she / her / hers) Accessioning Archivist Houghton Library Harvard University 617-384-7373 | mmwisner at fas.harvard.edu Building an Accessible Future | Houghton Library Renovation -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.walker at Vanderbilt.Edu Fri Aug 7 16:46:55 2020 From: scott.walker at Vanderbilt.Edu (Walker, Scott) Date: Fri, 7 Aug 2020 20:46:55 +0000 Subject: [Archivesspace_Users_Group] Record can be found through public, but not frontend Message-ID: Hi! I work for Vanderbilt University Libraries. We are having a strange problem. After moving ArchivesSpace to a new server, some items are giving a "record not found" error when accessed from the staff (frontend) interface, but are visible from the public interface. They are from a collection that was being worked with shortly before switching over servers. There don't seem to be any other issues. We thought it might be an issue with orphaned records, but none turned up when we checked the database. Has anybody else run into something like this? Scott Walker Library Web Application Administrator Library Technology and Digital Services Jean and Alexander Heard Libraries, Vanderbilt University 615-936-2446 | scott.walker at vanderbilt.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Sun Aug 9 10:34:25 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Sun, 9 Aug 2020 14:34:25 +0000 Subject: [Archivesspace_Users_Group] bringing the LCNAF plugin back online Message-ID: If you tried to use the LCNAF plugin in any version of ArchivesSpace the last few days you may have discovered that it was no longer able to connect to the LC service. This is because of a change on their end that needed to be reflected in the plugin. To get the plugin back online for any version up to and including v2.8.0: 1. Download the updated lcnaf plugin from the archivesspace-plugins repository: https://github.com/archivesspace-plugins/lcnaf 2. Stop your ArchivesSpace. 3. Replace the lcnaf plugin folder on your server with this slightly newer version of the plugin. (rename the new folder lcnaf if it is named anything else) 4. Restart ArchivesSpace. The updated version of the plugin with be included in future releases of ArchivesSpace. Please note, if you have customized this plugin at all, replacing it like this will cause you to lose those changes. Email us at ArchivesSpaceHome at lyrasis.org if you need help working the changes into a customized version of the plugin. If you need any assistance, please contact us at ArchivesSpaceHome at lyrasis.org to open up a technical support ticket. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13905 bytes Desc: image001.jpg URL: From jenking at gwu.edu Mon Aug 10 14:26:57 2020 From: jenking at gwu.edu (Jennifer King) Date: Mon, 10 Aug 2020 14:26:57 -0400 Subject: [Archivesspace_Users_Group] question about datasets in Aspace Message-ID: Hello colleagues, Special Collections was approached by a colleague in our research services unit who would like to use Aspace to manage datasets created by university faculty. Sounds good to us and as we start to consider description and possible collection structures I was wondering if anyone is doing this and has any advice especially curious to see how these may display in the PUI. Thank you, Jen King -- Jennifer King Collections Coordinator and Manuscripts Librarian Special Collections Research Center George Washington University Jenking at gwu.edu 202-994-0628 my pronouns are she/her/hers Schedule an appointment with me -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Aug 11 09:35:23 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 11 Aug 2020 13:35:23 +0000 Subject: [Archivesspace_Users_Group] bring out your spreadsheets or csvs (for testing the archival object importer) Message-ID: Hello ArchivesSpace users, For some testing we're doing for some new features for the archival objects importer (formerly "the Harvard plugin") I'm looking for a variety of spreadsheets and CSV files of real (or realish) data. This is only for testing this area - not for other kinds of imports in ArchivesSpace that use spreadsheets. I'm particularly looking for: * Spreadsheets that use the linked digital objects option * Spreadsheets with many linked records like agents, subjects, and containers * Spreadsheets with known, fixable errors that prevent initial import * CSVs of the above structured like the original template i.e. not in Microsoft Excel format (see CSV templates attached) * Older spreadsheets created using earlier versions of the template (could be ones you imported a few years ago and didn't need anymore) If you have some spreadsheets you'd be willing to donate to the cause, would you please send them my way? They will be used for testing only. Thanks for your help, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bulk_import_DO_template.csv Type: application/octet-stream Size: 3593 bytes Desc: bulk_import_DO_template.csv URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bulk_import_template.csv Type: application/octet-stream Size: 5639 bytes Desc: bulk_import_template.csv URL: From christine.dibella at lyrasis.org Thu Aug 13 12:47:58 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 13 Aug 2020 16:47:58 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays Message-ID: Dear ArchivesSpace Users, After a short hiatus, we?ll be back hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nigel.bond at auckland.ac.nz Thu Aug 13 18:36:31 2020 From: nigel.bond at auckland.ac.nz (Nigel Bond) Date: Thu, 13 Aug 2020 22:36:31 +0000 Subject: [Archivesspace_Users_Group] Advice on new upgrade Message-ID: <582394f220b84c519271de42ae72709a@uxcn13-tdc-a.UoA.auckland.ac.nz> Kia ora all, Looking for some advice. We are testing a new AS upgrade (2.7.x) and running into a couple of issues in our test environment. 1. Search results. Is there any way to reorder the way Search results are returned. In our previous version (2.5.x) search results were returned with COLLECION level being given priority. The new version returns it by 'relevance' which means there is no structure to the search results (could be file name, item, or series level, intermixed). For us, ideally we want search results at the Collection level first. I know we can then apply filters, but this seems to be an additional step, we have never needed before. 2. Is there any way to modify the way AS draws the 'preferred citation' field. It seems to be pulling text from various fields, and returning a result that does not make sense (despite us entering in a preferred citation in the appropriate field, for each (at the collection level). If working at the series or item level we are getting very mixed results. Are you now required to enter a citation note, at every level? 3. IS there a way to have the "Language of Finding aid" default to English,. It seems for some reason it is defaulting to "language undetermined" despite the Language field being set to English for each collection item. We do not want to have to alter this manually for every record. Any advice greatly received. Nga mihi nui. Dr. Nigel Bond, Team Leader, Cultural Collections (Special Collections) Cultural Collections | Te Tumu Herenga - Libraries and Learning Services | The University of Auckland 5 Alfred Street, Auckland 1010 Private Bag 92019 | Auckland 1142 | New Zealand | Telephone (649) 9237168 Blog: http://www.news.library.auckland.ac.nz/tag/special-collections/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Fri Aug 14 11:10:18 2020 From: buschedw at msu.edu (Busch, Ed) Date: Fri, 14 Aug 2020 15:10:18 +0000 Subject: [Archivesspace_Users_Group] No records found Message-ID: <3DB39251-5FB8-447F-9AA0-FDC8AD6665BE@msu.edu> Hi- We?re suddenly experiencing an odd problem. We did a reindex last week and now we can only browse Accessions, Resources and DOs. Everything else returns a No records found. If we are in a resource or accession, we can see the Agents and Subjects, etc linked to them find. It?s only when we try to Browse and see all. Anyone have any clues? We?ve tried rolling back the data but that doesn?t seem to be it. It seems like a system problem cropped up. Ed Busch, MLIS Interim Head of University Archives and Electronic Records Archivist Michigan State University Archives and Historical Collections Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Mon Aug 17 08:52:49 2020 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 17 Aug 2020 13:52:49 +0100 Subject: [Archivesspace_Users_Group] No records found In-Reply-To: <3DB39251-5FB8-447F-9AA0-FDC8AD6665BE@msu.edu> References: <3DB39251-5FB8-447F-9AA0-FDC8AD6665BE@msu.edu> Message-ID: One possible cause is the indexer timing out at some stage after indexing the things you can see, but before indexing the things you cannot. For example, it could happen if Solr takes a long time to commit changes from memory to disk storage, if the latter is slow, and if you have a lot of records. You could try doubling the value for /AppConfig[:indexer_solr_timeout_seconds]/ in your config.rb file and then trigger a re-index . Also try monitoring the application log file while the indexer is running. Errors messages there could help with further diagnosis. Andrew. On 14/08/2020 16:10, Busch, Ed wrote: > > Hi- > > We?re suddenly experiencing an odd problem. We did a reindex last week > and now we can only browse Accessions, Resources and DOs. Everything > else returns a No records found. > > If we are in a resource or accession, we can see the Agents and > Subjects, etc linked to them find. It?s only when we try to Browse and > see all. > > Anyone have any clues? We?ve tried rolling back the data but that > doesn?t seem to be it. It seems like a system problem cropped up. > > *Ed Busch, MLIS* > > Interim Head of University Archives and Electronic Records Archivist > > Michigan State University Archives and Historical Collections > > Conrad Hall > > 943 Conrad Road, Room 101 > > East Lansing, MI 48824 > > 517-884-6438 > > buschedw at msu.edu > > he/him/his > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Mon Aug 17 10:12:40 2020 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 17 Aug 2020 15:12:40 +0100 Subject: [Archivesspace_Users_Group] Advice on new upgrade In-Reply-To: <582394f220b84c519271de42ae72709a@uxcn13-tdc-a.UoA.auckland.ac.nz> References: <582394f220b84c519271de42ae72709a@uxcn13-tdc-a.UoA.auckland.ac.nz> Message-ID: <19fb6df9-c7cd-c33e-4ede-1caea409d1df@bodleian.ox.ac.uk> Here are some, at least partial, answers to your questions: 1. You can boost collection-level records relative to everything else by setting /AppConfig[:solr_params]/ in your config.rb file to something like /{ "bq" => "level:collection^1.25" }/ or add that in if you're already setting other Solr parameters. After a restart (re-indexing should not be required) it should have some effect, in both the staff and public interfaces. Increasing the number after the ^ symbol increases the boost. But take it too far and, for a query that returns lots of collections, you may find a lot of not-very-relevant collections crowding everything else out from the first several pages. 2. Do you mean you would like the "Citation" button in the public user interface to display the contents of preferred citation notes you've added in the staff interface (or have been imported from EAD containing prefercite)? That can be done, via a plug-in, but it is too complicated (at least the way we did it, with different rules for different levels, and overriding the standard JavaScript) to explain in an email. I've been meaning to split up our customizations into separate plug-ins, and put them on GitHub, but haven't got round to it yet. Maybe someone else has something you can use off-the-shelf? 3. Log in to your staff interface (you need to be an admin to do the following), click the drop-down arrow next to your username in the top-right corner, and select /Repository Preferences/. Enable /Pre-populate Records/ and save. Then go to /Browse > Resources/, and there should be a button labelled /Edit Default Values/. Click on that and select /Resource/. Here you can set the language to English, and anything else you don't want to fill in every time you create a new collection. Save, then repeat for /Resource Component/. If you have multiple repositories I think you have to repeat this entire process for every one, as I do not think it works globally. Andrew. On 13/08/2020 23:36, Nigel Bond wrote: > > Kia ora all, > > Looking for some advice.? We are testing a new AS upgrade (2.7.x) and > running into a couple of issues in our test environment. > > 1. Search results.? Is there any way to reorder the way Search > results are returned. In our previous version (2.5.x) search > results were returned with COLLECION level being given priority. > The new version returns it by ?relevance? which means there is no > structure to the search results (could be file name, item, or > series level, intermixed). For us, ideally we want search results > at the Collection level first. I know we can then apply filters, > but this seems to be an additional step, we have never needed before. > 2. Is there any way to modify the way AS draws the ?preferred > citation? field. It seems to be pulling text from various fields, > and returning a result? that does not make sense (despite us > entering in a preferred citation in the appropriate field, for > each (at the collection level). If working at the series or item > level we are getting very mixed results.? Are you now required to > enter a citation note, at every level? > 3. IS there a way to have the ?Language of Finding aid? default to > English,.? It seems for some reason it is defaulting to ?language > undetermined? despite the Language field being set to English for > each collection item.? We do not want to have to alter this > manually for every record. > > Any advice greatly received. > > Nga mihi nui. > > *Dr. Nigel Bond*, Team Leader, Cultural Collections (Special Collections) > > > Cultural Collections | Te Tumu Herenga - Libraries and Learning > Services | The University of Auckland > > 5 Alfred Street, Auckland 1010 > > Private Bag 92019 | Auckland 1142 | New Zealand | Telephone (649) 9237168 > Blog: http://www.news.library.auckland.ac.nz/tag/special-collections/ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Aug 17 12:18:42 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 17 Aug 2020 16:18:42 +0000 Subject: [Archivesspace_Users_Group] Reminder - Feedback form for ArchivesSpace antiracism and inclusion ideas now available Message-ID: <840DDC1F-B19F-4349-A879-63485E38C2AD@lyrasis.org> Dear ArchivesSpace community, Thank you to all who have been contributing thoughts and suggestions to our continuing discussions around how ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive over the last few months. We?ve compiled the many ideas into a feedback form that will help guide some decisions about next steps. All ArchivesSpace users and community members are welcome to comment on these ideas or contribute new ideas. We are fortunate that we have received many excellent suggestions; you do not have to comment on all suggestions unless you want to. The feedback form is available at https://www.surveymonkey.com/r/NQWT6JQ. Some ideas may be fairly simple to implement, others may require considerable cooperation and discussion across the community, including the involvement of the ArchivesSpace Governance Board. The feedback you provide will help us work together to make as much progress as we can on these issues. Please submit your feedback form responses by August 28 if you can. If you would like to reach out about this form, ideas, or next steps, please contact us at ArchivesSpaceHome at lyrasis.org at any time. We welcome your participation in any form. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29062 bytes Desc: image001.jpg URL: From mayoc at bc.edu Mon Aug 17 13:31:41 2020 From: mayoc at bc.edu (Chris Mayo) Date: Mon, 17 Aug 2020 13:31:41 -0400 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Message-ID: Hi all, We keep a modified in-house version of the ead-to-pdf stylesheet so that we can put out Finding Aids with our own branding and a few other changes. When we recently installed 2.8 on our test server, we discovered that the export to PDF job was failing with the following error info: "The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:subst" Our production server is currently running on 2.6, and we had previously updated the test server to 2.7 without that upgrade breaking our stylesheet, so the issue appears to have been introduced between 2.7 and 2.8. As far as I can tell, the base code for the stylesheet didn't change between those versions, and while the error message looks like an Xpath problem, the EAD structure doesn't appear to have changed either. Has anyone else encountered problems with modified finding aid stylesheets in 2.8, or have any thoughts on what could be causing this error? Chris Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Aug 17 13:48:59 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 17 Aug 2020 17:48:59 +0000 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: References: Message-ID: Chris, No clue if it's related or not, but it looks like a gem that's utilized for XSLT transformations in ASpace was switched out recently (saxon-xslt -> saxon-rb). I wonder if the new gem (and/or new version of saxon) is more strict, and only now throwing an error because of that? In any event, have you tried running the transformations outside of ASpace? Either way, if you can share a sample EAD file that throws the error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that I'm sure I can help, of course :) Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Mayo Sent: Monday, August 17, 2020 1:31 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi all, We keep a modified in-house version of the ead-to-pdf stylesheet so that we can put out Finding Aids with our own branding and a few other changes. When we recently installed 2.8 on our test server, we discovered that the export to PDF job was failing with the following error info: "The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:subst" Our production server is currently running on 2.6, and we had previously updated the test server to 2.7 without that upgrade breaking our stylesheet, so the issue appears to have been introduced between 2.7 and 2.8. As far as I can tell, the base code for the stylesheet didn't change between those versions, and while the error message looks like an Xpath problem, the EAD structure doesn't appear to have changed either. Has anyone else encountered problems with modified finding aid stylesheets in 2.8, or have any thoughts on what could be causing this error? Chris Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayoc at bc.edu Mon Aug 17 15:03:20 2020 From: mayoc at bc.edu (Chris Mayo) Date: Mon, 17 Aug 2020 15:03:20 -0400 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: References: Message-ID: Hi Mark, Thanks for the suggestion - I hadn't tried yet, but I can successfully run the transform outside of Aspace using Oxygen (I don't know how to run XSL from the command line). I'm not sure whether that obviates the question about the files, but I've attached a sample EAD and the stylesheet (plus a couple of sidecar files) here. It sounds like what's going on is that the version of saxon bundled into Aspace has gotten stricter, and I'm not sure what to do about that. It's fairly important for us to be able to output PDFs directly from the application. Best, Chris On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark wrote: > Chris, > > No clue if it's related or not, but it looks like a gem that's utilized > for XSLT transformations in ASpace was switched out recently (saxon-xslt -> > saxon-rb). I wonder if the new gem (and/or new version of saxon) is more > strict, and only now throwing an error because of that? > > In any event, have you tried running the transformations outside of > ASpace? Either way, if you can share a sample EAD file that throws the > error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to > take a look. Not that I'm sure I can help, of course :) > > Mark > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Chris Mayo > *Sent:* Monday, August 17, 2020 1:31 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Changes to PDF export in 2.8? > > Hi all, > > We keep a modified in-house version of the ead-to-pdf stylesheet so that > we can put out Finding Aids with our own branding and a few other changes. > When we recently installed 2.8 on our test server, we discovered that the > export to PDF job was failing with the following error info: > > "The context item for axis step ./ead is absent. Found while atomizing the > first argument of fn:subst" > > Our production server is currently running on 2.6, and we had previously > updated the test server to 2.7 without that upgrade breaking our > stylesheet, so the issue appears to have been introduced between 2.7 and > 2.8. As far as I can tell, the base code for the stylesheet didn't change > between those versions, and while the error message looks like an Xpath > problem, the EAD structure doesn't appear to have changed either. > > Has anyone else encountered problems with modified finding aid stylesheets > in 2.8, or have any thoughts on what could be causing this error? > > Chris > > Chris Mayo > Digital Production Librarian > Boston College > chris.mayo at bc.edu > pronouns: they/them/theirs > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mcaleer_ead.xml Type: text/xml Size: 648258 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: as-ead-pdf.xsl Type: text/xml Size: 105534 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: as-helper-functions.xsl Type: text/xml Size: 47271 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fop-config.xml Type: text/xml Size: 724 bytes Desc: not available URL: From j.fishman at austin.utexas.edu Tue Aug 18 10:43:01 2020 From: j.fishman at austin.utexas.edu (Fishman, Jessi) Date: Tue, 18 Aug 2020 14:43:01 +0000 Subject: [Archivesspace_Users_Group] mapping legacy location information Message-ID: Hi all, We're starting a project to map out and transfer our box location information from Excel and Google spreadsheet "shelf lists" into ArchivesSpace. As we're in the planning stages, I thought I'd reach out and see if anyone has experience with this and can offer any helpful tips regarding irregular legacy location information; specific things we're considering include: oversize and artifact items of multiple collections in one area; accession numbers not always being linked to box numbers; and how to deal with the loss of information like amount of space left vacant on a shelf. Any tips or encouragement would be appreciated! Thank you! Jessi Fishman, MSIS, CA Archivist Briscoe Center for American History The University of Texas at Austin 512-232-3371 j.fishman at austin.utexas.edu ?www.briscoecenter.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Tue Aug 18 14:19:13 2020 From: buschedw at msu.edu (Busch, Ed) Date: Tue, 18 Aug 2020 18:19:13 +0000 Subject: [Archivesspace_Users_Group] No records found In-Reply-To: References: <3DB39251-5FB8-447F-9AA0-FDC8AD6665BE@msu.edu> Message-ID: <096D4BE0-EA5C-42B2-B54B-00A51B6D0626@msu.edu> Related to this we see in the logs ?Failure in Staff Indexer worker thread: {"error":{"db_error":["Database integrity constraint conflict: Java::JavaSql::SQLSyntaxErrorException: The SELECT would examine more than MAX_JOIN_SIZE rows;? We?re running v2.7.1. Anyone else seeing this? Ed Busch, MLIS Interim Head of University Archives and Electronic Records Archivist Michigan State University Archives and Historical Collections Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his From: on behalf of Andrew Morrison Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Monday, August 17, 2020 at 8:53 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] No records found One possible cause is the indexer timing out at some stage after indexing the things you can see, but before indexing the things you cannot. For example, it could happen if Solr takes a long time to commit changes from memory to disk storage, if the latter is slow, and if you have a lot of records. You could try doubling the value for AppConfig[:indexer_solr_timeout_seconds] in your config.rb file and then trigger a re-index. Also try monitoring the application log file while the indexer is running. Errors messages there could help with further diagnosis. Andrew. On 14/08/2020 16:10, Busch, Ed wrote: Hi- We?re suddenly experiencing an odd problem. We did a reindex last week and now we can only browse Accessions, Resources and DOs. Everything else returns a No records found. If we are in a resource or accession, we can see the Agents and Subjects, etc linked to them find. It?s only when we try to Browse and see all. Anyone have any clues? We?ve tried rolling back the data but that doesn?t seem to be it. It seems like a system problem cropped up. Ed Busch, MLIS Interim Head of University Archives and Electronic Records Archivist Michigan State University Archives and Historical Collections Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From dullj at newschool.edu Tue Aug 18 16:33:51 2020 From: dullj at newschool.edu (Joshua Dull) Date: Tue, 18 Aug 2020 16:33:51 -0400 Subject: [Archivesspace_Users_Group] Internal Linking Issue Message-ID: Hello, We've had some trouble with the internal linking system that uses ref ids (described here https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff). The links resolved correctly when testing using the default port setup. When we switched to staff & public proxies under different paths (/staff & /public) the link resolver didn't add '/public' to the path. So links resolve to the correct object, but is missing the first part of the path. The config file has the correct proxy paths and other links work. I tried the same method for internal linking in the sandbox and got the same error; the /public is dropped when the link is resolved. (See link in 'Additional Description' for this test record ). If we switch to running over different subdomains for staff & public, it seems like that will solve this issue? Thank You, Joshua -- JOSHUA DULL *ASSISTANT DIRECTOR OF LIBRARY SYSTEMS* THE NEW SCHOOL LIBRARIES & ARCHIVES dullj at newschool.edu [image: The New School] -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lora.Woodford at lyrasis.org Tue Aug 18 16:39:46 2020 From: Lora.Woodford at lyrasis.org (Lora Woodford) Date: Tue, 18 Aug 2020 20:39:46 +0000 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: References: Message-ID: Hi Chris, I took a quick look at this, and I do think Mark?s instinct is correct. It seems an existing (custom to you folks) function in your xsl isn?t working with the recent updates/transition to saxon-rb. My XSL is pretty rusty these days, but the following lines (ln 364-371) in your as-ead-pdf.xsl are the culprits: Irish Music Archives The error ?The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:substring()? points to the fact that the transformation no longer knows how to handle the $repo provided as the first argument in that substring function. For what it?s worth, removing this customization from your stylesheet (only this customization) results in being able to successfully export/print pdfs over here. I?ll keep poking, but wanted to give you this partial update sooner rather than later. Lora From: on behalf of Chris Mayo Reply-To: Archivesspace Users Group Date: Monday, August 17, 2020 at 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Mark, Thanks for the suggestion - I hadn't tried yet, but I can successfully run the transform outside of Aspace using Oxygen (I don't know how to run XSL from the command line). I'm not sure whether that obviates the question about the files, but I've attached a sample EAD and the stylesheet (plus a couple of sidecar files) here. It sounds like what's going on is that the version of saxon bundled into Aspace has gotten stricter, and I'm not sure what to do about that. It's fairly important for us to be able to output PDFs directly from the application. Best, Chris On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark > wrote: Chris, No clue if it's related or not, but it looks like a gem that's utilized for XSLT transformations in ASpace was switched out recently (saxon-xslt -> saxon-rb). I wonder if the new gem (and/or new version of saxon) is more strict, and only now throwing an error because of that? In any event, have you tried running the transformations outside of ASpace? Either way, if you can share a sample EAD file that throws the error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that I'm sure I can help, of course :) Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Chris Mayo > Sent: Monday, August 17, 2020 1:31 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi all, We keep a modified in-house version of the ead-to-pdf stylesheet so that we can put out Finding Aids with our own branding and a few other changes. When we recently installed 2.8 on our test server, we discovered that the export to PDF job was failing with the following error info: "The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:subst" Our production server is currently running on 2.6, and we had previously updated the test server to 2.7 without that upgrade breaking our stylesheet, so the issue appears to have been introduced between 2.7 and 2.8. As far as I can tell, the base code for the stylesheet didn't change between those versions, and while the error message looks like an Xpath problem, the EAD structure doesn't appear to have changed either. Has anyone else encountered problems with modified finding aid stylesheets in 2.8, or have any thoughts on what could be causing this error? Chris Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lora.Woodford at lyrasis.org Tue Aug 18 17:07:57 2020 From: Lora.Woodford at lyrasis.org (Lora Woodford) Date: Tue, 18 Aug 2020 21:07:57 +0000 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: References: Message-ID: <1301B2CE-71E0-4D6B-8768-32891EB2A1B9@lyrasis.org> And, as soon as I sent this, I found where that repo variable is being set up at line 126 of your xsl. If you move that down into the publicationstmt template starting on ln 358 you should be golden. Lora From: on behalf of Lora Woodford Reply-To: Archivesspace Users Group Date: Tuesday, August 18, 2020 at 4:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Chris, I took a quick look at this, and I do think Mark?s instinct is correct. It seems an existing (custom to you folks) function in your xsl isn?t working with the recent updates/transition to saxon-rb. My XSL is pretty rusty these days, but the following lines (ln 364-371) in your as-ead-pdf.xsl are the culprits: Irish Music Archives The error ?The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:substring()? points to the fact that the transformation no longer knows how to handle the $repo provided as the first argument in that substring function. For what it?s worth, removing this customization from your stylesheet (only this customization) results in being able to successfully export/print pdfs over here. I?ll keep poking, but wanted to give you this partial update sooner rather than later. Lora From: on behalf of Chris Mayo Reply-To: Archivesspace Users Group Date: Monday, August 17, 2020 at 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Mark, Thanks for the suggestion - I hadn't tried yet, but I can successfully run the transform outside of Aspace using Oxygen (I don't know how to run XSL from the command line). I'm not sure whether that obviates the question about the files, but I've attached a sample EAD and the stylesheet (plus a couple of sidecar files) here. It sounds like what's going on is that the version of saxon bundled into Aspace has gotten stricter, and I'm not sure what to do about that. It's fairly important for us to be able to output PDFs directly from the application. Best, Chris On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark > wrote: Chris, No clue if it's related or not, but it looks like a gem that's utilized for XSLT transformations in ASpace was switched out recently (saxon-xslt -> saxon-rb). I wonder if the new gem (and/or new version of saxon) is more strict, and only now throwing an error because of that? In any event, have you tried running the transformations outside of ASpace? Either way, if you can share a sample EAD file that throws the error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that I'm sure I can help, of course :) Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Chris Mayo > Sent: Monday, August 17, 2020 1:31 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi all, We keep a modified in-house version of the ead-to-pdf stylesheet so that we can put out Finding Aids with our own branding and a few other changes. When we recently installed 2.8 on our test server, we discovered that the export to PDF job was failing with the following error info: "The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:subst" Our production server is currently running on 2.6, and we had previously updated the test server to 2.7 without that upgrade breaking our stylesheet, so the issue appears to have been introduced between 2.7 and 2.8. As far as I can tell, the base code for the stylesheet didn't change between those versions, and while the error message looks like an Xpath problem, the EAD structure doesn't appear to have changed either. Has anyone else encountered problems with modified finding aid stylesheets in 2.8, or have any thoughts on what could be causing this error? Chris Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Aug 18 18:12:05 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 18 Aug 2020 22:12:05 +0000 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: <1301B2CE-71E0-4D6B-8768-32891EB2A1B9@lyrasis.org> References: , <1301B2CE-71E0-4D6B-8768-32891EB2A1B9@lyrasis.org> Message-ID: Chris, Lora: Okay, so I just did a bit more digging (but not enough yet), and I'd say that there must either be a bug in the gem or in the way that it's invoked (I'm leaning toward the latter, but I haven't looked at the ASpace code yet). Whatever the issue is, it's not what I speculated the first time around. Chris, like you, I have no problems when running this stylesheet with any version of saxon outside of ArchiveSpace, and most everything looks fine with how you have things set up. I say "most everything looks fine" only because that $repo variable could select multiple values if you had, say, a "num" element hand-encoded in the primary finding aid title, and if you did, you'd get an error when trying to run the substring function anyway, since that function will always require a single string and never multiple items in a sequence. I'd probably change that same Xpath expression to look for the call number in the archdesc/did/unitid[1] area instead, just to play it safe. Also because I think it's strange that ASpace serializes the unitid to the finding aid title, but that might just be me ?. The issue here, I think, is that you cannot set a global variable in the XSLT stylesheets in ASpace 2.8. Luckily the default ones don't do that (although I'm surprised, since I do that all the time ?), but you should definitely have the option to do that, as you did before. Actually, it looks like the EAC-to-HTML one does declare at least one global variable, but that transformation is not used anywhere in ASpace I don't think, so no worries. But in the meantime, you can get things working again as Lora just mentioned, by moving your repo variable inside of the "publicationstmt" template instead. That's the important part right now; good find, Lora! Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Lora Woodford Sent: Tuesday, August 18, 2020 5:07 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? And, as soon as I sent this, I found where that repo variable is being set up at line 126 of your xsl. If you move that down into the publicationstmt template starting on ln 358 you should be golden. Lora From: on behalf of Lora Woodford Reply-To: Archivesspace Users Group Date: Tuesday, August 18, 2020 at 4:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Chris, I took a quick look at this, and I do think Mark?s instinct is correct. It seems an existing (custom to you folks) function in your xsl isn?t working with the recent updates/transition to saxon-rb. My XSL is pretty rusty these days, but the following lines (ln 364-371) in your as-ead-pdf.xsl are the culprits: Irish Music Archives The error ?The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:substring()? points to the fact that the transformation no longer knows how to handle the $repo provided as the first argument in that substring function. For what it?s worth, removing this customization from your stylesheet (only this customization) results in being able to successfully export/print pdfs over here. I?ll keep poking, but wanted to give you this partial update sooner rather than later. Lora From: on behalf of Chris Mayo Reply-To: Archivesspace Users Group Date: Monday, August 17, 2020 at 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Mark, Thanks for the suggestion - I hadn't tried yet, but I can successfully run the transform outside of Aspace using Oxygen (I don't know how to run XSL from the command line). I'm not sure whether that obviates the question about the files, but I've attached a sample EAD and the stylesheet (plus a couple of sidecar files) here. It sounds like what's going on is that the version of saxon bundled into Aspace has gotten stricter, and I'm not sure what to do about that. It's fairly important for us to be able to output PDFs directly from the application. Best, Chris On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark > wrote: Chris, No clue if it's related or not, but it looks like a gem that's utilized for XSLT transformations in ASpace was switched out recently (saxon-xslt -> saxon-rb). I wonder if the new gem (and/or new version of saxon) is more strict, and only now throwing an error because of that? In any event, have you tried running the transformations outside of ASpace? Either way, if you can share a sample EAD file that throws the error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that I'm sure I can help, of course :) Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Chris Mayo > Sent: Monday, August 17, 2020 1:31 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi all, We keep a modified in-house version of the ead-to-pdf stylesheet so that we can put out Finding Aids with our own branding and a few other changes. When we recently installed 2.8 on our test server, we discovered that the export to PDF job was failing with the following error info: "The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:subst" Our production server is currently running on 2.6, and we had previously updated the test server to 2.7 without that upgrade breaking our stylesheet, so the issue appears to have been introduced between 2.7 and 2.8. As far as I can tell, the base code for the stylesheet didn't change between those versions, and while the error message looks like an Xpath problem, the EAD structure doesn't appear to have changed either. Has anyone else encountered problems with modified finding aid stylesheets in 2.8, or have any thoughts on what could be causing this error? Chris Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayoc at bc.edu Wed Aug 19 09:26:36 2020 From: mayoc at bc.edu (Chris Mayo) Date: Wed, 19 Aug 2020 09:26:36 -0400 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: References: <1301B2CE-71E0-4D6B-8768-32891EB2A1B9@lyrasis.org> Message-ID: Lora, Mark, Thank you both! Moving the variable did fix the issue, and now I feel a bit sheepish for focusing on the './ead' segment of the error report, not the 'fn:substring' part. I may make more of the refinements Mark suggested later on, but it's working for now, which is the important part. Thanks for the help tracking that down. Best, Chris On Tue, Aug 18, 2020 at 6:12 PM Custer, Mark wrote: > Chris, Lora: > > Okay, so I just did a bit more digging (but not enough yet), and I'd say > that there must either be a bug in the gem or in the way that it's invoked > (I'm leaning toward the latter, but I haven't looked at the ASpace code > yet). Whatever the issue is, it's not what I speculated the first time > around. > > Chris, like you, I have no problems when running this stylesheet with any > version of saxon outside of ArchiveSpace, and most everything looks fine > with how you have things set up. I say "most everything looks fine" only > because that $repo variable could select multiple values if you had, say, > a "num" element hand-encoded in the primary finding aid title, and if you > did, you'd get an error when trying to run the substring function anyway, > since that function will always require a single string and never multiple > items in a sequence. I'd probably change that same Xpath expression to > look for the call number in the archdesc/did/unitid[1] area instead, just > to play it safe. Also because I think it's strange that ASpace serializes > the unitid to the finding aid title, but that might just be me ?. > > The issue here, I think, is that you cannot set a global variable in the > XSLT stylesheets in ASpace 2.8. Luckily the default ones don't do that > (although I'm surprised, since I do that all the time ?), but you should > definitely have the option to do that, as you did before. Actually, it > looks like the EAC-to-HTML one does declare at least one global variable, > but that transformation is not used anywhere in ASpace I don't think, so no > worries. > > But in the meantime, you can get things working again as Lora just > mentioned, by moving your repo variable inside of the "publicationstmt" > template instead. That's the important part right now; good find, Lora! > > Mark > > > > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Lora Woodford > *Sent:* Tuesday, August 18, 2020 5:07 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? > > > And, as soon as I sent this, I found where that repo variable is being set > up at line 126 of your xsl. If you move that down into the publicationstmt > template starting on ln 358 you should be golden. > > > > Lora > > > > *From: * on > behalf of Lora Woodford > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Tuesday, August 18, 2020 at 4:39 PM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? > > > > Hi Chris, > > I took a quick look at this, and I do think Mark?s instinct is correct. > It seems an existing (custom to you folks) function in your xsl isn?t > working with the recent updates/transition to saxon-rb. > > My XSL is pretty rusty these days, but the following lines (ln 364-371) in > your as-ead-pdf.xsl are the culprits: > > > > > > > Irish Music Archives > > > > > > > > > > > > > > The error ?The context item for axis step ./ead is absent. Found while > atomizing the first argument of fn:substring()? points to the fact that the > transformation no longer knows how to handle the $repo provided as the > first argument in that substring function. For what it?s worth, removing > this customization from your stylesheet (only this customization) results > in being able to successfully export/print pdfs over here. > > I?ll keep poking, but wanted to give you this partial update sooner rather > than later. > > > > Lora > > > > *From: * on > behalf of Chris Mayo > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Monday, August 17, 2020 at 3:04 PM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? > > > > Hi Mark, > > > > Thanks for the suggestion - I hadn't tried yet, but I can successfully run > the transform outside of Aspace using Oxygen (I don't know how to run XSL > from the command line). I'm not sure whether that obviates the question > about the files, but I've attached a sample EAD and the stylesheet (plus a > couple of sidecar files) here. It sounds like what's going on is that the > version of saxon bundled into Aspace has gotten stricter, and I'm not sure > what to do about that. It's fairly important for us to be able to output > PDFs directly from the application. > > > > Best, > > Chris > > > > On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark wrote: > > Chris, > > > > No clue if it's related or not, but it looks like a gem that's utilized > for XSLT transformations in ASpace was switched out recently (saxon-xslt -> > saxon-rb). I wonder if the new gem (and/or new version of saxon) is more > strict, and only now throwing an error because of that? > > > > In any event, have you tried running the transformations outside of > ASpace? Either way, if you can share a sample EAD file that throws the > error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to > take a look. Not that I'm sure I can help, of course :) > > > > Mark > > > > > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Chris Mayo > *Sent:* Monday, August 17, 2020 1:31 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Changes to PDF export in 2.8? > > > > Hi all, > > > > We keep a modified in-house version of the ead-to-pdf stylesheet so that > we can put out Finding Aids with our own branding and a few other changes. > When we recently installed 2.8 on our test server, we discovered that the > export to PDF job was failing with the following error info: > > > > "The context item for axis step ./ead is absent. Found while atomizing the > first argument of fn:subst" > > > > Our production server is currently running on 2.6, and we had previously > updated the test server to 2.7 without that upgrade breaking our > stylesheet, so the issue appears to have been introduced between 2.7 and > 2.8. As far as I can tell, the base code for the stylesheet didn't change > between those versions, and while the error message looks like an Xpath > problem, the EAD structure doesn't appear to have changed either. > > > > Has anyone else encountered problems with modified finding aid stylesheets > in 2.8, or have any thoughts on what could be causing this error? > > > > Chris > > > > Chris Mayo > > Digital Production Librarian > > Boston College > > chris.mayo at bc.edu > > pronouns: they/them/theirs > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > > Chris Mayo > > Digital Production Librarian > > Boston College > > chris.mayo at bc.edu > > pronouns: they/them/theirs > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Aug 19 11:27:43 2020 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 19 Aug 2020 15:27:43 +0000 Subject: [Archivesspace_Users_Group] File Version HREF Attribute Incorrectly Assigned from EAD Exports Message-ID: Dear all, Hello, this is Corey Schmidt, ArchivesSpace Project Manager at the University of Georgia Libraries. I hope everyone is staying safe, happy, and healthy. I'm having a problem with EAD exports from ArchivesSpace, particularly related to digital objects. When exporting EAD files, the digital object ID is assigned to the href attribute when in fact the File URI should be assigned to the href attribute. The converter is saying IF file_versions[0] != NULL THEN href="file_versions[0].file_url" ELSE href="digital_object_id". For our case, it is defaulting to ELSE, even though there are file versions attached to our digital objects and they are published. I confirmed this by making a get request for some digital objects and saw that the list of file versions for each one has at least 1 file version. Attached is a screenshot (because I'm from the "Show-Me" state). When exporting records, we normally include digital objects, but we exclude unpublished components. However, when I tried including unpublished components, the File URIs are assigned correctly to href attributes. I checked the MySQL database and all the file versions for the field publish = 1 (which I assume means Publish = True). Within the staff interface, it also shows Publish = True, so I don't think it's an issue with either the database or Solr Index. I should note that this behavior is inconsistent, where some (usually smaller) finding aids will export with the file URI assigned to the href attribute without including unpublished components. However, the vast majority do not. Any clarification and/or help would be greatly appreciated. Thanks! Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: digital_object-file_version_true-UGA-19-8-2020-001.JPG Type: image/jpeg Size: 89478 bytes Desc: digital_object-file_version_true-UGA-19-8-2020-001.JPG URL: From mark.custer at yale.edu Wed Aug 19 12:01:42 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 19 Aug 2020 16:01:42 +0000 Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? In-Reply-To: References: <1301B2CE-71E0-4D6B-8768-32891EB2A1B9@lyrasis.org> , Message-ID: Chris, I think you were spot on to focus on that '/.ead' part of the message. I *think* that indeed points to the root cause of the issue, but I've no clue how to untangle it. Anyhow, I put in a question for the developer who maintains that code (external to ASpace). You should be able to assign a global variable, just like you had done previously, so hopefully the workaround that you've employed will only be temporary. Very glad that Lora got you set up with the workaround, since 2.8 has a lot of amazing features (we're about to upgrade to 2.7.1, but already looking forward to the new features in 2.8 and beyond ? ) Thanks for reporting the issue! Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Mayo Sent: Wednesday, August 19, 2020 9:26 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Lora, Mark, Thank you both! Moving the variable did fix the issue, and now I feel a bit sheepish for focusing on the './ead' segment of the error report, not the 'fn:substring' part. I may make more of the refinements Mark suggested later on, but it's working for now, which is the important part. Thanks for the help tracking that down. Best, Chris On Tue, Aug 18, 2020 at 6:12 PM Custer, Mark > wrote: Chris, Lora: Okay, so I just did a bit more digging (but not enough yet), and I'd say that there must either be a bug in the gem or in the way that it's invoked (I'm leaning toward the latter, but I haven't looked at the ASpace code yet). Whatever the issue is, it's not what I speculated the first time around. Chris, like you, I have no problems when running this stylesheet with any version of saxon outside of ArchiveSpace, and most everything looks fine with how you have things set up. I say "most everything looks fine" only because that $repo variable could select multiple values if you had, say, a "num" element hand-encoded in the primary finding aid title, and if you did, you'd get an error when trying to run the substring function anyway, since that function will always require a single string and never multiple items in a sequence. I'd probably change that same Xpath expression to look for the call number in the archdesc/did/unitid[1] area instead, just to play it safe. Also because I think it's strange that ASpace serializes the unitid to the finding aid title, but that might just be me ?. The issue here, I think, is that you cannot set a global variable in the XSLT stylesheets in ASpace 2.8. Luckily the default ones don't do that (although I'm surprised, since I do that all the time ?), but you should definitely have the option to do that, as you did before. Actually, it looks like the EAC-to-HTML one does declare at least one global variable, but that transformation is not used anywhere in ASpace I don't think, so no worries. But in the meantime, you can get things working again as Lora just mentioned, by moving your repo variable inside of the "publicationstmt" template instead. That's the important part right now; good find, Lora! Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Lora Woodford > Sent: Tuesday, August 18, 2020 5:07 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? And, as soon as I sent this, I found where that repo variable is being set up at line 126 of your xsl. If you move that down into the publicationstmt template starting on ln 358 you should be golden. Lora From: > on behalf of Lora Woodford > Reply-To: Archivesspace Users Group > Date: Tuesday, August 18, 2020 at 4:39 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Chris, I took a quick look at this, and I do think Mark?s instinct is correct. It seems an existing (custom to you folks) function in your xsl isn?t working with the recent updates/transition to saxon-rb. My XSL is pretty rusty these days, but the following lines (ln 364-371) in your as-ead-pdf.xsl are the culprits: Irish Music Archives The error ?The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:substring()? points to the fact that the transformation no longer knows how to handle the $repo provided as the first argument in that substring function. For what it?s worth, removing this customization from your stylesheet (only this customization) results in being able to successfully export/print pdfs over here. I?ll keep poking, but wanted to give you this partial update sooner rather than later. Lora From: > on behalf of Chris Mayo > Reply-To: Archivesspace Users Group > Date: Monday, August 17, 2020 at 3:04 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi Mark, Thanks for the suggestion - I hadn't tried yet, but I can successfully run the transform outside of Aspace using Oxygen (I don't know how to run XSL from the command line). I'm not sure whether that obviates the question about the files, but I've attached a sample EAD and the stylesheet (plus a couple of sidecar files) here. It sounds like what's going on is that the version of saxon bundled into Aspace has gotten stricter, and I'm not sure what to do about that. It's fairly important for us to be able to output PDFs directly from the application. Best, Chris On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark > wrote: Chris, No clue if it's related or not, but it looks like a gem that's utilized for XSLT transformations in ASpace was switched out recently (saxon-xslt -> saxon-rb). I wonder if the new gem (and/or new version of saxon) is more strict, and only now throwing an error because of that? In any event, have you tried running the transformations outside of ASpace? Either way, if you can share a sample EAD file that throws the error and a copy of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that I'm sure I can help, of course :) Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Chris Mayo > Sent: Monday, August 17, 2020 1:31 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8? Hi all, We keep a modified in-house version of the ead-to-pdf stylesheet so that we can put out Finding Aids with our own branding and a few other changes. When we recently installed 2.8 on our test server, we discovered that the export to PDF job was failing with the following error info: "The context item for axis step ./ead is absent. Found while atomizing the first argument of fn:subst" Our production server is currently running on 2.6, and we had previously updated the test server to 2.7 without that upgrade breaking our stylesheet, so the issue appears to have been introduced between 2.7 and 2.8. As far as I can tell, the base code for the stylesheet didn't change between those versions, and while the error message looks like an Xpath problem, the EAD structure doesn't appear to have changed either. Has anyone else encountered problems with modified finding aid stylesheets in 2.8, or have any thoughts on what could be causing this error? Chris Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Aug 20 14:54:20 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 20 Aug 2020 18:54:20 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays In-Reply-To: <46CE10A0-3DD9-4139-BF15-B9D19408EC16@lyrasis.org> References: <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org> <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org> <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org> <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org> <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> <24DA2EB0-8EA2-42E8-9EC1-2377BAE51368@lyrasis.org> <46CE10A0-3DD9-4139-BF15-B9D19408EC16@lyrasis.org> Message-ID: Dear ArchivesSpace Users, We?ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly. Thank you to everyone who joined us last week for a great chat. We hope to see you all tomorrow. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29075 bytes Desc: image001.jpg URL: From Corey.Schmidt at uga.edu Fri Aug 21 16:05:39 2020 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Fri, 21 Aug 2020 20:05:39 +0000 Subject: [Archivesspace_Users_Group] File Version HREF Attribute Incorrectly Assigned from EAD Exports In-Reply-To: References: Message-ID: All, I was able to fix this issue with Mark Custer's help. Huge shoutout to him for spotting the issue. It turned out that the Solr Index was out of sync with the database. In Mark's words: "the EAD exporter will use the Solr index when it can.... [T]he index might actually be out of sync with the database, which could explain why you see those file URIs as published, but they are not being exported in the EAD because they aren't showing up as published in the Solr index." Since the EAD exports were being generated through the data stored in the Solr Index and the Index hadn't caught the updated File Versions (Publish = True), the export DO (Digital Object) href's were assigned the DO identifier. A very similar issue can be found on this post in the ArchivesSpace listserv: Importing from AT to AS - File Versions left unpublished (http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-April/006725.html) Again, thank you Mark for your help! Sincerely, Corey ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Corey Schmidt Sent: Wednesday, August 19, 2020 11:27 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] File Version HREF Attribute Incorrectly Assigned from EAD Exports Dear all, Hello, this is Corey Schmidt, ArchivesSpace Project Manager at the University of Georgia Libraries. I hope everyone is staying safe, happy, and healthy. I'm having a problem with EAD exports from ArchivesSpace, particularly related to digital objects. When exporting EAD files, the digital object ID is assigned to the href attribute when in fact the File URI should be assigned to the href attribute. The converter is saying IF file_versions[0] != NULL THEN href="file_versions[0].file_url" ELSE href="digital_object_id". For our case, it is defaulting to ELSE, even though there are file versions attached to our digital objects and they are published. I confirmed this by making a get request for some digital objects and saw that the list of file versions for each one has at least 1 file version. Attached is a screenshot (because I'm from the "Show-Me" state). When exporting records, we normally include digital objects, but we exclude unpublished components. However, when I tried including unpublished components, the File URIs are assigned correctly to href attributes. I checked the MySQL database and all the file versions for the field publish = 1 (which I assume means Publish = True). Within the staff interface, it also shows Publish = True, so I don't think it's an issue with either the database or Solr Index. I should note that this behavior is inconsistent, where some (usually smaller) finding aids will export with the file URI assigned to the href attribute without including unpublished components. However, the vast majority do not. Any clarification and/or help would be greatly appreciated. Thanks! Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Mon Aug 24 08:00:00 2020 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Mon, 24 Aug 2020 08:00:00 -0400 Subject: [Archivesspace_Users_Group] Non ISO 639-2b languages? Message-ID: Dear List, As we work through a hundred years of legacy description from home, we are encountering many interesting things. We recently converted from PDF the Elsie Worthington Clews Parsons collection (MARC view: https://clio.columbia.edu/catalog/4079199/librarian_view). There is a lot of important Hopi-language material in the collection, so we were hoping to add Hopi as a controlled language. However, ISO 639-2b doesn't include Hopi or even its parent language group. The 'hop' code is only in ISO 639-3: https://iso639-3.sil.org/code/hop For now, we've included the "uncoded languages" value in the controlled language dropdown in AS, and added a language note about the Hopi material as well. I'd be curious to hear how anyone else has handled non-ISO 6392b languages in ArchivesSpace. Best, Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Tue Aug 25 09:05:05 2020 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Tue, 25 Aug 2020 13:05:05 +0000 Subject: [Archivesspace_Users_Group] Jobs indexing error Message-ID: <68BB7664-2E3F-431F-B90C-745C6141E8C2@rockarch.org> Hi all, Posting here in the off chance someone has run into this before. We?re testing out AS version 2.8, coming from 2.6.0 and running into a weird issue. Indexing works fine until we get to the job records section of indexing, and then we run into an unhandled exception ultimately stops indexing from finishing, and it just starts up again at resource records after finishing the jobs. I?ve attached the relevant section of our log. Any ideas on how to fix this? I could just delete all of our job records from the table, but that seems like a bad solution to this issue. Thanks, Patrick Galligan He/Him Digital Archivist Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: rac_archivesspace.out Type: application/octet-stream Size: 16438 bytes Desc: rac_archivesspace.out URL: From blake.carver at lyrasis.org Tue Aug 25 09:30:37 2020 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 25 Aug 2020 13:30:37 +0000 Subject: [Archivesspace_Users_Group] Jobs indexing error In-Reply-To: <68BB7664-2E3F-431F-B90C-745C6141E8C2@rockarch.org> References: <68BB7664-2E3F-431F-B90C-745C6141E8C2@rockarch.org> Message-ID: You could just get rid of the aspace_check_job jobs. (back up the DB just in case) select * job where job_blob like '%aspace_check_job%'; Then: delete FROM job where job_blob like '%aspace_check_job%'; ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Tuesday, August 25, 2020 9:05 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Jobs indexing error Hi all, Posting here in the off chance someone has run into this before. We?re testing out AS version 2.8, coming from 2.6.0 and running into a weird issue. Indexing works fine until we get to the job records section of indexing, and then we run into an unhandled exception ultimately stops indexing from finishing, and it just starts up again at resource records after finishing the jobs. I?ve attached the relevant section of our log. Any ideas on how to fix this? I could just delete all of our job records from the table, but that seems like a bad solution to this issue. Thanks, Patrick Galligan He/Him Digital Archivist Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Aug 25 09:32:06 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 25 Aug 2020 13:32:06 +0000 Subject: [Archivesspace_Users_Group] Non ISO 639-2b languages? In-Reply-To: References: Message-ID: Kevin, What you've done for now sounds like the best option within the current structure of ArchivesSpace. Although ArchivesSpace could be updated with other controlled lists, like ISO-639-3, I'd be curious if it would be possible -- and, more importantly, useful -- to try to adopt the IETF BCP 47 language tag standard instead (https://en.wikipedia.org/wiki/IETF_language_tag). IETF BCP 47 is itself an amalgamation of different language and script codes (although for stability reasons might not always be fully compatible with those), with the added ability to specify a lot more detail (as well as to extend the codes for local uses as needed) based on its syntax. I suppose it's a bit like the ability to create pre-coordinated subject headings. This is on my mind right now, as well, especially in regard to EAD and EAC-CPF and their relationship to systems like ArchivesSpace. EAD2002 embedded a lot of code lists (like country codes, language codes, etc.) directly in the schema. This is nice for validation purposes, but those ISO standards change over time, and EAD2002 was only released once, which means that many of the country codes (e.g. the county code for Serbia) and language codes now in those ISO standards (and now in ArchivesSpace) are not in EAD2002. EAD3 went in a new direction, adding those code lists to a separate validation step. Right now, EAD3 supports validation processes for a variety of ISO code lists: ISO 639-1, 639-2, 639-3, ISO 3166, ISO 15924, and ISO 15511. So, no problem for using ISO 639-3 in EAD3, but you cannot import or export it into ArchivesSpace. I'd love to see both EAD/C and ArchivesSpace adopt IETF BCP 47 language tags, but I suspect that is a lot easier said than done. Aso, I've no clue if that would be a wise choice or not. Personally, I'm just persuaded by how expressive and extensible the IETF language tag best practice has been defined. But that type of specificity is usually not needed (or utilized) in archival description. And in this particular use case, you just need place to add a new language code that already exists in ISO 639-3, which in and of itself does not warrant adopting IETF BCP 47 language tags ? Anyhow, I'd love to hear what others think on this topic, are already doing, planning, etc. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin W. Schlottmann Sent: Monday, August 24, 2020 8:00 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Non ISO 639-2b languages? Dear List, As we work through a hundred years of legacy description from home, we are encountering many interesting things. We recently converted from PDF the Elsie Worthington Clews Parsons collection (MARC view: https://clio.columbia.edu/catalog/4079199/librarian_view). There is a lot of important Hopi-language material in the collection, so we were hoping to add Hopi as a controlled language. However, ISO 639-2b doesn't include Hopi or even its parent language group. The 'hop' code is only in ISO 639-3: https://iso639-3.sil.org/code/hop For now, we've included the "uncoded languages" value in the controlled language dropdown in AS, and added a language note about the Hopi material as well. I'd be curious to hear how anyone else has handled non-ISO 6392b languages in ArchivesSpace. Best, Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Tue Aug 25 09:42:51 2020 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Tue, 25 Aug 2020 13:42:51 +0000 Subject: [Archivesspace_Users_Group] Jobs indexing error Message-ID: <2F65D171-07E2-4985-9E05-2DFE8769B596@rockarch.org> Blake, Yeah, I?m guessing that the `asck` plugin we installed to check data a year ago makes those jobs invalid if the plugin isn?t installed. Which is annoying. Thanks for the help! From: on behalf of Blake Carver Reply-To: Archivesspace Users Group Date: Tuesday, August 25, 2020 at 9:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Jobs indexing error ***External*** This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.*** You could just get rid of the aspace_check_job jobs. (back up the DB just in case) select * job where job_blob like '%aspace_check_job%'; Then: delete FROM job where job_blob like '%aspace_check_job%'; ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Tuesday, August 25, 2020 9:05 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Jobs indexing error Hi all, Posting here in the off chance someone has run into this before. We?re testing out AS version 2.8, coming from 2.6.0 and running into a weird issue. Indexing works fine until we get to the job records section of indexing, and then we run into an unhandled exception ultimately stops indexing from finishing, and it just starts up again at resource records after finishing the jobs. I?ve attached the relevant section of our log. Any ideas on how to fix this? I could just delete all of our job records from the table, but that seems like a bad solution to this issue. Thanks, Patrick Galligan He/Him Digital Archivist Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Aug 25 10:00:30 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 25 Aug 2020 14:00:30 +0000 Subject: [Archivesspace_Users_Group] Jobs indexing error In-Reply-To: <2F65D171-07E2-4985-9E05-2DFE8769B596@rockarch.org> References: <2F65D171-07E2-4985-9E05-2DFE8769B596@rockarch.org> Message-ID: Hi Patrick (and all), Just a mention that we discovered this issue after the release of 2.8.0 and added this to the release notes: added July 30, 2020: Due the addition of background jobs to the index in this release, plugins that create background jobs will cause an indexing loop if they are disabled. While the vast majority of users will not encounter this, it is most likely to be encountered if users have run the language cleanup plugins released in conjunction with 2.6.0. The workaround for now is to reenable the plugin (or keep it enabled if the job is run in 2.8.0). The plugin itself should not be re-run. This issue will be corrected in a future release. You can either delete the jobs as Blake suggests or reenable the plugin. We expect to have this issue corrected in the next release. Apologies for the inconvenience, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Galligan, Patrick Sent: Tuesday, August 25, 2020 9:43 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Jobs indexing error Blake, Yeah, I?m guessing that the `asck` plugin we installed to check data a year ago makes those jobs invalid if the plugin isn?t installed. Which is annoying. Thanks for the help! From: > on behalf of Blake Carver > Reply-To: Archivesspace Users Group > Date: Tuesday, August 25, 2020 at 9:31 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Jobs indexing error ***External*** This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.*** You could just get rid of the aspace_check_job jobs. (back up the DB just in case) select * job where job_blob like '%aspace_check_job%'; Then: delete FROM job where job_blob like '%aspace_check_job%'; ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Galligan, Patrick > Sent: Tuesday, August 25, 2020 9:05 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Jobs indexing error Hi all, Posting here in the off chance someone has run into this before. We?re testing out AS version 2.8, coming from 2.6.0 and running into a weird issue. Indexing works fine until we get to the job records section of indexing, and then we run into an unhandled exception ultimately stops indexing from finishing, and it just starts up again at resource records after finishing the jobs. I?ve attached the relevant section of our log. Any ideas on how to fix this? I could just delete all of our job records from the table, but that seems like a bad solution to this issue. Thanks, Patrick Galligan He/Him Digital Archivist Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From Steve.Giessler at mail.wvu.edu Tue Aug 25 17:11:35 2020 From: Steve.Giessler at mail.wvu.edu (Steven Giessler) Date: Tue, 25 Aug 2020 21:11:35 +0000 Subject: [Archivesspace_Users_Group] CSV file for subjects not generating Message-ID: Dear ArchivesSpace user list, Here at West Virginia University, we are running version 2.7.0 of ArchivesSpace. On the admin side if we go to Subjects: https://archivesspace.lib.wvu.edu/subjects and try to click the Download CSV button, it gives us a file (excerpt below) that is not comma separated (has \n between each field) and only lists the first page worth of Subjects (25 in our case): tail 1597180067.csv "title\n4-H clubs -- West Virginia\nAbb's Valley (Va. and W. Va.)\nAbolition of slavery\nAbortions\nAbsentee Balloting -- Marion County.\nAcademic costume\nAcademic librarians -- Faculty status\nAcademies\nAcademies and Institutes.\nAcademies (Private schools)\n\"Accomack County, V.A.\"\nAccount books\nAccounting\nAccounts -- Church financial reocrds\nAcord family.\nAdams County (Ohio)\nAdmiralty Islands (Papua New Guinea)\nAdvertising\nAdvertising photography\nAerial photographs.\nAeronautics\n\"Afghanistan -- History -- Saur Revolution, 1978\"\nAfrica\nAfrican American churches -- West Virginia\nAfrican American soldiers\n" On the other hand, when we hit the Download CSV button while listing agents: https://archivesspace.lib.wvu.edu/agents we get what we would expect for all 10,000+ records (excerpt): tail 1597187282.csv agent_corporate_entity,Institute for the History of Technology and Industrial Archaeology,,ingest, agent_corporate_entity,West Virginia University. Institute for the History of Technology and Industrial Archaeology,http://id.loc.gov/authorities/names/nr91038362,Library of Congress Name Authority File, agent_corporate_entity,Society for Industrial Archeology,http://id.loc.gov/authorities/names/n78014220,Library of Congress Name Authority File, agent_person,"Barnette, Curtis H. and Others",,ingest, agent_person,"Barnette, Curtis H.",,ingest, agent_person,"Green, James Edwin",,ingest, agent_family,Green family,http://id.loc.gov/authorities/subjects/sh85057211,Library of Congress Name Authority File, agent_corporate_entity,Grand Army of the Republic,http://id.loc.gov/authorities/names/n84076025,Library of Congress Name Authority File, agent_family,Deeds family,,ingest, agent_person,"Pryzbylinski, Leon A.",,ingest, Any idea why we can't get a proper CSV file for Subjects? Logs show no errors. Thank you for any help you may be able to provide, or suggestions on how to fix this, Steve Giessler Professional Technologist West Virginia University From sdm7g at virginia.edu Tue Aug 25 21:53:53 2020 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 26 Aug 2020 01:53:53 +0000 Subject: [Archivesspace_Users_Group] CSV file for subjects not generating In-Reply-To: References: Message-ID: <0B52390D-718F-4236-A3D0-42C34A91C8DB@virginia.edu> I believe this has been fixed ? I can?t find the issue but this is the top entry in git log frontend/app/controllers/subjects_controller.rb commit f9035b7ef72c65ab854070022d55cbfa023e6429 Author: Lora Woodford Date: Thu Jun 11 17:33:21 2020 -0400 Make subjects subject and fix csv and sort So if that?s the required fix, it should be in the last 2.8.0 release. ( CSV export seems to work properly for me running current master devserver ) If upgrading right away to get the results is not convenient, you can try pulling the info from the backend on your current installed version. Using ASnake (https://github.com/archivesspace-labs/ArchivesSnake ), something like: client = ASnakeClient( baseurl="http://localhost:8089", username=?admin?, password=? ) client.authorize() for s in test.get_paged( 'subjects' ): print( s[?title?] ) # and any other fields you want to output?. Or you can access the backend API at /subjects, but you will have to iterate the paged results manually curl http://archives-test.$LIB:8089/subjects?page=1 | jq . { "first_page": 1, "last_page": 45, "this_page": 1, "total": 898, "results": [ { "lock_version": 22, "title": "Drawings (visual works)", "authority_id": "300033973", "scope_note": "Visual works produced by drawing, which is the application of lines on a surface, often paper, by using a pencil, pen, chalk, or some other tracing instrument to focus on the delineation of form rather than the application of color. This term is often defined broadly to refer to computer-generated images as well.", "created_by": "img7u", "last_modified_by": "ew8ff", "create_time": "2015-10-19T18:22:55Z", "system_mtime": "2019-11-18T20:57:54Z", "user_mtime": "2017-07-13T15:01:53Z", "is_slug_auto": false, "source": "aat", "jsonmodel_type": "subject", "external_ids": [], "publish": true, "used_within_repositories": [], "used_within_published_repositories": [], "terms": [ { "lock_version": 0, "term": "drawings (visual works)", "created_by": "img7u", "last_modified_by": "img7u", "create_time": "2015-10-19T18:22:55Z", "system_mtime": "2015-10-19T18:22:55Z", "user_mtime": "2015-10-19T18:22:55Z", "term_type": "genre_form", "jsonmodel_type": "term", "uri": "/terms/6", "vocabulary": "/vocabularies/1" } ], "external_documents": [], "uri": "/subjects/6", "vocabulary": "/vocabularies/1", "is_linked_to_published_record": true }, [ . . . ] > On Aug 25, 2020, at 5:11 PM, Steven Giessler wrote: > > Dear ArchivesSpace user list, > > Here at West Virginia University, we are running version 2.7.0 of > ArchivesSpace. > > On the admin side if we go to Subjects: > > https://archivesspace.lib.wvu.edu/subjects > > and try to click the Download CSV button, it gives us a file (excerpt below) > that is not comma separated (has \n between each field) and only lists > the first page worth of Subjects (25 in our case): > > tail 1597180067.csv > "title\n4-H clubs -- West Virginia\nAbb's Valley (Va. and W. > Va.)\nAbolition of slavery\nAbortions\nAbsentee Balloting -- Marion > County.\nAcademic costume\nAcademic librarians -- Faculty > status\nAcademies\nAcademies and Institutes.\nAcademies (Private > schools)\n\"Accomack County, V.A.\"\nAccount books\nAccounting\nAccounts > -- Church financial reocrds\nAcord family.\nAdams County > (Ohio)\nAdmiralty Islands (Papua New Guinea)\nAdvertising\nAdvertising > photography\nAerial photographs.\nAeronautics\n\"Afghanistan -- History > -- Saur Revolution, 1978\"\nAfrica\nAfrican American churches -- West > Virginia\nAfrican American soldiers\n" > > On the other hand, when we hit the Download CSV button while listing agents: > > https://archivesspace.lib.wvu.edu/agents > > we get what we would expect for all 10,000+ records (excerpt): > > tail 1597187282.csv > agent_corporate_entity,Institute for the History of Technology and > Industrial Archaeology,,ingest, > agent_corporate_entity,West Virginia University. Institute for the > History of Technology and Industrial > Archaeology,http://id.loc.gov/authorities/names/nr91038362,Library of > Congress Name Authority File, > agent_corporate_entity,Society for Industrial > Archeology,http://id.loc.gov/authorities/names/n78014220,Library of > Congress Name Authority File, > agent_person,"Barnette, Curtis H. and Others",,ingest, > agent_person,"Barnette, Curtis H.",,ingest, > agent_person,"Green, James Edwin",,ingest, > agent_family,Green > family,http://id.loc.gov/authorities/subjects/sh85057211,Library of > Congress Name Authority File, > agent_corporate_entity,Grand Army of the > Republic,http://id.loc.gov/authorities/names/n84076025,Library of > Congress Name Authority File, > agent_family,Deeds family,,ingest, > agent_person,"Pryzbylinski, Leon A.",,ingest, > > Any idea why we can't get a proper CSV file for Subjects? > > Logs show no errors. > > Thank you for any help you may be able to provide, or suggestions on how > to fix this, > > Steve Giessler > Professional Technologist > West Virginia University > > > > _______________________________________________ > 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: 3342 bytes Desc: not available URL: From Jessica.Crouch at lyrasis.org Thu Aug 27 10:52:20 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 27 Aug 2020 14:52:20 +0000 Subject: [Archivesspace_Users_Group] Atlas Systems Webinar Announcement: Know Thy Config: An Introduction Message-ID: <70108144-5626-4222-91D9-0928AB450A0E@lyrasis.org> [Posted on behalf of our Registered Service Provider Atlas Systems] Atlas Systems Webinar: Know Thy Config: An Introduction When: Wednesday, September 23, 2020, 2-3pm EST Please join Atlas Systems' Special Collections & Archives Technical Consultant Valerie Addonizio for a general introduction to the ArchivesSpace ?config,? a file of settings that controls aspects of ArchivesSpace that you may not be familiar with. This webinar is intended to raise general awareness of the config, what it does, how you can request to make changes to it, and how to maintain it over time by keeping track of updates. This webinar assumes no experience with the config, but does assume familiarity with the ArchivesSpace staff interface and PUI. A recording will be available if you are unable to attend the live presentation and a link will be sent to the listserv once it?s up and ready to be viewed at your convenience. Please register for the Atlas Systems webinar Know Thy Config: An Introduction on Sept 23, 2020, 2-3pm EST through EventBrite. After registering, you will receive a confirmation email. Zoom info will follow in a second email two days before the event. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From benn.joseph at northwestern.edu Thu Aug 27 12:45:50 2020 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Thu, 27 Aug 2020 16:45:50 +0000 Subject: [Archivesspace_Users_Group] ASpace v2.7.1 languages issue Message-ID: Hi all, We are upgrading from ArchivesSpace v2.4.1 to v2.7.1 as part of a plan to eventually get to 2.8-it was recommended that we to go to 2.7.1 first and sort out changes to the Languages sub-record first, so that's what we're doing. So far we've gone from 2.4.1 to 2.7.1 on our sandbox, and have discovered an unexpected behavior with languages for Archival Objects. Here's what we expected to happen (from the Atlas support site): "If you have values in both Basic Information > Language of Materials and under Notes > Language of Materials in any version prior to v2.7.0 (which we do for many records): * The values in Basic Information > Language of Materials will migrate to the new controlled value list under the new Languages sub-record in your Resource records as part of the update to v2.7.0. The presence of this information fulfills the requirement of the sub-record. You will not have to take any additional action for these records. * The notes in Notes > Language of Materials will move from under the Notes heading to under the Language of Materials sub-record. They will display as text. Though this note alone does not meet the requirements of the sub-record, since it is paired with a Language (per the above), so you will not need to take any additional actions on these records." This process worked successfully for Resource records, but for Archival Objects with both of the above values this is the result we're seeing: * The values in Basic Information > Language of Materials AND Notes > Language of Materials have both disappeared from the Archival Object. * There is now a new Language of Materials sub-record in the Archival Object that contains no data (just a blank text sub-note). Upon moving to v2.7.1 we ran the batch_update_lang_and_script plugin; but it doesn't seem like this would have affected the Archival Objects in the way are seeing. Has anyone else experienced this issue? We are following up with our hosting service too just in case there is a step we missed. Best, --Benn Benn Joseph Head, Collections Services McCormick Library of Special Collections & University Archives Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Aug 27 14:15:12 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 27 Aug 2020 18:15:12 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays In-Reply-To: References: <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org> <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org> <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org> <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org> <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> <24DA2EB0-8EA2-42E8-9EC1-2377BAE51368@lyrasis.org> <46CE10A0-3DD9-4139-BF15-B9D19408EC16@lyrasis.org> Message-ID: <3390E79B-70B8-4A34-86B1-2276E98B66F8@lyrasis.org> Dear ArchivesSpace Users, We?ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly. Thank you to everyone who joined us last week for a great chat. We hope to see you all tomorrow. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29076 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Mon Aug 31 13:39:41 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 31 Aug 2020 17:39:41 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - August 2020 Message-ID: <1EFC6030-BA0A-4DC1-8F6A-ABFBF0515FBF@lyrasis.org> [cid:image001.jpg at 01D67F9C.2CB651A0] August 2020 Update Development We're working on the next version of ArchivesSpace, which will come out later in the year. The major focus of work right now is finishing up expanding the agents module. We're also working on enhancements to the spreadsheet importer, reviewing some substantial community pull requests, and gem upgrades. If you upgraded to 2.8.0, please note that due the addition of background jobs to the index in this release, plugins that create background jobs will cause an indexing loop if they are disabled. While the vast majority of users will not encounter this, it is most likely to be encountered if users have run the language cleanup plugins released in conjunction with 2.6.0. The workaround for now is to reenable the plugin (or keep it enabled if the job is run in 2.8.0). The plugin itself should not be re-run. This issue will be corrected in a future release. Feedback form for ArchivesSpace antiracism and inclusion ideas now available Thank you to all who have been contributing thoughts and suggestions to our continuing discussions around how ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive over the last few months. We've compiled the many ideas into a feedback form that will help guide some decisions about next steps. All ArchivesSpace users and community members are welcome to comment on these ideas or contribute new ideas. We are fortunate that we have received many excellent suggestions; you do not have to comment on all suggestions unless you want to. The feedback form is available at https://www.surveymonkey.com/r/NQWT6JQ. Some ideas may be fairly simple to implement, others may require considerable cooperation and discussion across the community, including the involvement of the ArchivesSpace Governance Board. The feedback you provide will help us work together to make as much progress as we can on these issues. We have extended the date to submit feedback form responses to September 4. If you would like to reach out about this form, ideas, or next steps, please contact us at ArchivesSpaceHome at lyrasis.org at any time. We welcome your participation in any form. Webinar Announcement: Integrating ArchivesSpace with CollectionSpace The next webinar in the Integrations with ArchivesSpace series will be Wednesday, September 16, at 2pm ET. Each webinar in this series highlights an integration with another application used in archives that ArchivesSpace members have worked on or requested. Our tenth webinar in this series will be an open discussion on an integration between ArchivesSpace and CollectionSpace, a museum-focused open source collections management system. When: September 16, 2020 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_rmZEc6O6TMGQn85k3lgIOQ In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. In this webinar, representatives from both ArchivesSpace and CollectionSpace will briefly highlight the core elements of each application, how they are similar and where they differ in terms of functionality and the types of content they describe. An open discussion on community use cases and goals for an ArchivesSpace/CollectionSpace integration will follow. Please bring your ideas for how you would like to use ArchivesSpace and CollectionSpace together. The foundation of this discussion will be the initial feedback received on the recent survey disseminated by CollectionSpace about what their community wants in an ArchivesSpace/CollectionSpace integration. This survey is available at bit.ly/aspace_cspace. Webinar Presenters: Linda Colet has 20+ years experience in collections management and digital planning in the museum field. Her outreach work with CollectionSpace (LYRASIS) involves speaking with the museum community on how their collections management system needs fit within their overall digital strategy. She is also an adjunct art history teacher at Northern Virginia Community College. Christine Di Bella is the Program Manager for ArchivesSpace and involved in all aspects of the program, working closely and collaboratively with the community, advisory groups, and Governance Board to set and implement the strategy and goals for ArchivesSpace. Christine has worked as an archivist for over 20 years in academic and non-profit settings, including some where she managed both archives and art and artifact collections. Who should attend: Anyone using or interested in using ArchivesSpace or CollectionSpace and a possible integration between the two systems. Those with use cases they?d like to share are highly encouraged to attend and participate in the discussion. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. Webinar Announcement from our Registered Service Provider Atlas Systems Atlas Systems Webinar: Know Thy Config: An Introduction When: Wednesday, September 23, 2020, 2-3pm EST Please join Atlas Systems' Special Collections & Archives Technical Consultant Valerie Addonizio for a general introduction to the ArchivesSpace ?config,? a file of settings that controls aspects of ArchivesSpace that you may not be familiar with. This webinar is intended to raise general awareness of the config, what it does, how you can request to make changes to it, and how to maintain it over time by keeping track of updates. This webinar assumes no experience with the config, but does assume familiarity with the ArchivesSpace staff interface and PUI. A recording will be available for those who are unable to attend the live presentation. Please register for the Atlas Systems webinar Know Thy Config: An Introduction on Sept 23, 2020, 2-3pm EST through EventBrite. After registering, you will receive a confirmation email. Zoom info will follow in a second email two days before the event. Recordings and presentation slides from the ArchivesSpace Member Forum now available Thank you to everyone who attended the 6th Annual ArchivesSpace Member Forum on August 3-7, 2020. The recordings from the August 3 sessions and presentation slides from both August 3 and 4 activities are now available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1422819333/ArchivesSpace+Member+Forum+2020. If you attended any portion of the forum and have not yet completed our post forum evaluation, please take a few minutes to fill out the post-workshop evaluation at https://www.surveymonkey.com/r/7CBD37Z. We very much want to know what you liked, what we could have done better, and what you?d like for future events like this. Membership Update We are excited to welcome our newest members to our community! Our new members since July 31 include: * Cook County Government (Chicago, IL) * Sam Houston State University (Huntsville, TX) * University of New Mexico (Albuquerque, NM) As of August 31, we have 417 General members, 21 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 Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22469 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29061 bytes Desc: image002.jpg URL: