From elizabeth.russell1 at maine.edu Fri Sep 1 09:58:14 2017 From: elizabeth.russell1 at maine.edu (Elizabeth Russell) Date: Fri, 1 Sep 2017 09:58:14 -0400 Subject: [Archivesspace_Users_Group] Finding aid status Message-ID: Hello All, I've recently added a few values to the finding aid status controlled value list for options that fit our work flow. While they appear in the drop down list, and also appear in the PUI display, the status does not show up when I'm browsing resources. If the value is one of the original values, it shows. If the value was changed to one of the new values, it is blank. (We're running v2.1.1, hosted by Lyrasis). Does anyone know what's going on here? Best, Beth -- Beth Russell Archivist / Special Collections Librarian University of Maine, 5729 Raymond H. Fogler Library Orono, ME 04469-5729 207.581.1676 elizabeth.russell1 at maine.edu http://www.library.umaine.edu/speccoll -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Sep 1 10:45:49 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 1 Sep 2017 14:45:49 +0000 Subject: [Archivesspace_Users_Group] Finding aid status In-Reply-To: References: Message-ID: Beth, Just a guess, since I haven?t tested this out yet, but my hunch is that your new value is missing in the Staff Interface because there?s no translation value in the YML (Yet another Markup Language) file. The PUI is actually using the database value for this particular element (though that?s a bug, since it should be using the translation value when one exists). I?m not sure of how the code works, but my preference for these controlled value lists is that the ?translation value? from the YML file should always be used first; if there is no translation value (which you can?t add via the staff interface, but have to add directly to the text YML files), then the value that should display in its place would be the database value. So, just to be clear, if you add a finding aid status of ?edited? to the staff interface, all that you?ve done at that point is add ?edited? to the database. To add it the YML file, you?d also need to do something like this to your locales/enum/en.yml file (or, better yet, via a YML file in a local plugin: resource_finding_aid_status: completed: Completed in_progress: In Progress under_revision: Under Revision unprocessed: Unprocessed edited: Edited Or, if you had a Swedish YML file, it might be something like this (assuming Google translate didn?t leave me completely astray): edited: redigerade Again, I haven?t actually verified this, but that seems to be a likely possibility. But regardless of the cause, it should just show up in the staff interface and public interface in the correct way, of course ? Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Elizabeth Russell Sent: Friday, 01 September, 2017 9:58 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Finding aid status Hello All, I've recently added a few values to the finding aid status controlled value list for options that fit our work flow. While they appear in the drop down list, and also appear in the PUI display, the status does not show up when I'm browsing resources. If the value is one of the original values, it shows. If the value was changed to one of the new values, it is blank. (We're running v2.1.1, hosted by Lyrasis). Does anyone know what's going on here? Best, Beth -- Beth Russell Archivist / Special Collections Librarian University of Maine, 5729 Raymond H. Fogler Library Orono, ME 04469-5729 207.581.1676 elizabeth.russell1 at maine.edu http://www.library.umaine.edu/speccoll -------------- next part -------------- An HTML attachment was scrubbed... URL: From Elizbeth_Russell at umit.maine.edu Fri Sep 1 11:18:47 2017 From: Elizbeth_Russell at umit.maine.edu (Elizbeth Russell) Date: Fri, 01 Sep 2017 11:18:47 -0400 Subject: [Archivesspace_Users_Group] Finding aid status Message-ID: Thanks Mark. As I suspected its not something I can fix myself as a hosted member of Lyrasis. Luckily they are on it. Best, Beth Beth Russell Archivist/ Special Collections Librarian University of Maine, 5729 Raymond H. Fogler Library Orono, ME 04469-5729 207.581.1676 elizabeth.russell1 at maine.edu http://www.library.umaine.edu/speccoll/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Sep 1 13:27:53 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 1 Sep 2017 17:27:53 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.1.2 released Message-ID: Hello ArchivesSpace members, The ArchivesSpace program team is pleased to announce the availability of v2.1.2. This minor release contains several bug fixes, including for an issue with installing on Windows using a blank MySQL database and for an issue with archival objects with only dates/dates as titles not appearing in the new public interface. It also addresses some technical debt issues. A big thanks to Steve Majewski for submitting fixes for three of the items included in this release. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.1.2. The full list of bug fixes and improvements is included in the release notes. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.1.0, we would recommend going directly to 2.1.2, though you should read the considerations for upgrading to 2.1.0 at https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_2.1.0.md first. Thanks to the individual users who identified these issues on the Users Group listserv, Github, and directly to program team members and made suggestions for improvements. If you have any questions or need help upgrading, please let us know. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From jgd1 at williams.edu Wed Sep 6 11:37:31 2017 From: jgd1 at williams.edu (Drmacich, Jessika) Date: Wed, 6 Sep 2017 11:37:31 -0400 Subject: [Archivesspace_Users_Group] Connecting request to email Message-ID: Hi all, I am attempting to connect the request button in AS to our special collections email in the config. It's not working at all. Can someone lead me to how and where I make the changes in the config? Also, I'm having issues finding documentation regarding how to alter the "Search the Archives" message in the en.yml. I can easily change the welcome message, but not the "Search the Archives." Any suggestions? Thanks so much. My very best, Jessika Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries Special Collections 413-597-4725 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Sep 6 12:19:03 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 6 Sep 2017 16:19:03 +0000 Subject: [Archivesspace_Users_Group] Staff EDIT links from PUI resources? Message-ID: Are staff EDIT links from PUI resources working for anyone ( in 2.x ) ? They don't appear for me, and browser console shows javascript errors. >From this issue, it looks like there was a patch accepted, but issue not resolved. https://archivesspace.atlassian.net/browse/AR-1785 -- Steve Majewski / UVA Alderman Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From DUPREL at mailbox.sc.edu Thu Sep 7 09:07:57 2017 From: DUPREL at mailbox.sc.edu (DUPRE, LANCE) Date: Thu, 7 Sep 2017 13:07:57 +0000 Subject: [Archivesspace_Users_Group] Connecting request to email In-Reply-To: References: Message-ID: <2AF36D93-6FCB-449C-A325-706445AB54F3@mailbox.sc.edu> On my test instance I am just using sendmail installed on the server to send out email requests. I haven?t played around with using a separate smtp server server yet. I have also not yet figure out how to enable archivesspace to send emails to different addresses depending on what repository the object is in. I can only get the address in the pui_email_override config to work. Also, the email is sent but instead of returning to the object I get the "We?re sorry, but something went wrong? page. I?ll attach logs generated after a request is sent below. Here are the configs I have set up to get email working to this point. AppConfig[:pui_email_enabled] = true AppConfig[:pui_email_override] = 'fallback at your_email.com? AppConfig[:pui_request_email_fallback_to_address] = 'fallback at your_email.com? AppConfig[:pui_request_email_fallback_from_address] = 'fromaddress at your-email.com? AppConfig[:pui_email_delivery_method] = :sendmail AppConfig[:pui_email_sendmail_settings] = { location: '/usr/sbin/sendmail', arguments: '-i' } AppConfig[:pui_email_perform_deliveries] = true AppConfig[:pui_email_raise_delivery_errors] = true On Sep 6, 2017, at 11:37 AM, Drmacich, Jessika > wrote: Hi all, I am attempting to connect the request button in AS to our special collections email in the config. It's not working at all. Can someone lead me to how and where I make the changes in the config? Also, I'm having issues finding documentation regarding how to alter the "Search the Archives" message in the en.yml. I can easily change the welcome message, but not the "Search the Archives." Any suggestions? Thanks so much. My very best, Jessika Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries Special Collections 413-597-4725 _______________________________________________ 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 -------------- An embedded and charset-unspecified text was scrubbed... Name: log.txt URL: From HurtT at easternct.edu Thu Sep 7 11:36:31 2017 From: HurtT at easternct.edu (Hurt, Tara (Library)) Date: Thu, 7 Sep 2017 15:36:31 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 In-Reply-To: References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl> <2869dc51ee5f4bc4a47b17ab69b00814@evcspmbx05.ads.northwestern.edu> Message-ID: Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 7 11:48:33 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 7 Sep 2017 15:48:33 +0000 Subject: [Archivesspace_Users_Group] Connecting request to email In-Reply-To: <2AF36D93-6FCB-449C-A325-706445AB54F3@mailbox.sc.edu> References: , <2AF36D93-6FCB-449C-A325-706445AB54F3@mailbox.sc.edu> Message-ID: Email requests are disabled on our ArchivesSpace servers, so I have nothing to add about the config settings. However, if you need to debug on a test server and you don't want to configure sendmail or postfix or actually send messages out ( which I've had to do for testing other services ), and you need to debug addresses or content of generated mail, I found MailCatcher a very handy tool. https://mailcatcher.me -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of DUPRE, LANCE Sent: Thursday, September 7, 2017 9:07:57 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Connecting request to email On my test instance I am just using sendmail installed on the server to send out email requests. I haven?t played around with using a separate smtp server server yet. I have also not yet figure out how to enable archivesspace to send emails to different addresses depending on what repository the object is in. I can only get the address in the pui_email_override config to work. Also, the email is sent but instead of returning to the object I get the "We?re sorry, but something went wrong? page. I?ll attach logs generated after a request is sent below. Here are the configs I have set up to get email working to this point. AppConfig[:pui_email_enabled] = true AppConfig[:pui_email_override] = 'fallback at your_email.com? AppConfig[:pui_request_email_fallback_to_address] = 'fallback at your_email.com? AppConfig[:pui_request_email_fallback_from_address] = 'fromaddress at your-email.com? AppConfig[:pui_email_delivery_method] = :sendmail AppConfig[:pui_email_sendmail_settings] = { location: '/usr/sbin/sendmail', arguments: '-i' } AppConfig[:pui_email_perform_deliveries] = true AppConfig[:pui_email_raise_delivery_errors] = true On Sep 6, 2017, at 11:37 AM, Drmacich, Jessika > wrote: Hi all, I am attempting to connect the request button in AS to our special collections email in the config. It's not working at all. Can someone lead me to how and where I make the changes in the config? Also, I'm having issues finding documentation regarding how to alter the "Search the Archives" message in the en.yml. I can easily change the welcome message, but not the "Search the Archives." Any suggestions? Thanks so much. My very best, Jessika Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries Special Collections 413-597-4725 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 7 12:23:52 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 7 Sep 2017 16:23:52 +0000 Subject: [Archivesspace_Users_Group] Staff EDIT links from PUI resources? In-Reply-To: References: Message-ID: OK: I did manage to get staff EDIT links working on one test server. There seem to be a number of issues involved: browser differences in handling headers and tags ( and different error messages in different browser consoles ), AppConfig proxy settings, CORS issues with https: / http: security downgrade... and I'm not sure what else: testing config on my laptop, it also makes a difference if you connect and login on the server as 'localhost' or with actual server name. Maybe that makes a difference in the session cookies. We're currently running our staff interface thru https: behind some other security, and the public server more open and on http: There may be some problems getting that config to work. But a heads up to others: Since the 'Staff Only' button is hidden unless this is configured properly and working, I was not initially aware that something wasn't working! And the requirements to get it working seem to have changed from previous versions before the new PUI. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Wednesday, September 6, 2017 12:19:03 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Staff EDIT links from PUI resources? Are staff EDIT links from PUI resources working for anyone ( in 2.x ) ? They don't appear for me, and browser console shows javascript errors. >From this issue, it looks like there was a patch accepted, but issue not resolved. https://archivesspace.atlassian.net/browse/AR-1785 -- Steve Majewski / UVA Alderman Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From eloehr at smith.edu Thu Sep 7 12:36:02 2017 From: eloehr at smith.edu (Eric Loehr) Date: Thu, 7 Sep 2017 12:36:02 -0400 Subject: [Archivesspace_Users_Group] error message when trying to connect to the api Message-ID: Hi all, We're running ArchivesSpace 2.0.1 and are getting the following error message when trying to connect to the api: {"error":"Sinatra::NotFound"} This just suddenly started happening after having worked fine previously, with no changes to the server -- any clues what might have happened/how to fix it? Thanks -- Eric -- Eric Loehr Head of Library Technology Services Smith College Libraries eloehr at smith.edu (413) 585-2969 Smith College Libraries are on the move beginning May 21 . Our central campus hub will be Young Library as we make way for the renovation of the New Neilson Library . Please don't hesitate to be in touch with questions. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 7 12:44:59 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 7 Sep 2017 16:44:59 +0000 Subject: [Archivesspace_Users_Group] error message when trying to connect to the api In-Reply-To: References: Message-ID: Errors in the log on startup ? -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Eric Loehr Sent: Thursday, September 7, 2017 12:36:02 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] error message when trying to connect to the api Hi all, We're running ArchivesSpace 2.0.1 and are getting the following error message when trying to connect to the api: {"error":"Sinatra::NotFound"} This just suddenly started happening after having worked fine previously, with no changes to the server -- any clues what might have happened/how to fix it? Thanks -- Eric -- Eric Loehr Head of Library Technology Services Smith College Libraries eloehr at smith.edu (413) 585-2969 Smith College Libraries are on the move beginning May 21. Our central campus hub will be Young Library as we make way for the renovation of the New Neilson Library. Please don't hesitate to be in touch with questions. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 7 13:11:53 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 7 Sep 2017 17:11:53 +0000 Subject: [Archivesspace_Users_Group] error message when trying to connect to the api In-Reply-To: References: Message-ID: It looks like that's the message you get if you curl to an unrouted path or misspell the backend path: curl_as_osx http://archives-test.$LIB:8089/xyzzy {"error":"Sinatra::NotFound"} -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Eric Loehr Sent: Thursday, September 7, 2017 12:36:02 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] error message when trying to connect to the api Hi all, We're running ArchivesSpace 2.0.1 and are getting the following error message when trying to connect to the api: {"error":"Sinatra::NotFound"} This just suddenly started happening after having worked fine previously, with no changes to the server -- any clues what might have happened/how to fix it? Thanks -- Eric -- Eric Loehr Head of Library Technology Services Smith College Libraries eloehr at smith.edu (413) 585-2969 Smith College Libraries are on the move beginning May 21. Our central campus hub will be Young Library as we make way for the renovation of the New Neilson Library. Please don't hesitate to be in touch with questions. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmg17 at psu.edu Thu Sep 7 13:12:48 2017 From: bmg17 at psu.edu (Ben Goldman) Date: Thu, 7 Sep 2017 13:12:48 -0400 (EDT) Subject: [Archivesspace_Users_Group] locations and/or barcodes in EAD? Message-ID: <1280483767.6321976.1504804368656.JavaMail.zimbra@psu.edu> Hello everyone, We've never really used the locations modules in ASpace, and are still working our way through top container functionality. Out of curiosity, are the values for a top container's location and barcode included in the EAD export for a resource record? Thinking specifically about how such data can be incorporated into our Aeon requesting workflows. Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Thu Sep 7 13:58:22 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 7 Sep 2017 17:58:22 +0000 Subject: [Archivesspace_Users_Group] locations and/or barcodes in EAD? In-Reply-To: <1280483767.6321976.1504804368656.JavaMail.zimbra@psu.edu> References: <1280483767.6321976.1504804368656.JavaMail.zimbra@psu.edu> Message-ID: Ben, Barcodes are included in EAD exports, but locations are not included. If you need to use EAD for requesting workflows, I?d probably suggest just adding the top container URI to the EAD exports via a local plugin. That way, you could get much more than the name of a location if you ever needed more than that: you could also get info about whether the top container is restricted, if there?s a specific local restriction type, if there?s an a specific date range associated with that restriction, if the location itself also has a barcode (since ASpace supports barcoding physical locations, not just containers), etc., etc. Granted, you could do the same using the API with a barcode search, but having the top container URI in the EAD would mean that barcodes wouldn?t be required at all. None of that machine-readable access restriction information is include in the EAD exports, but it could be very helpful to have when requesting with Aeon, which I only mention since you?ve said that you?re still working your way through the top-container options in ASpace. And, even though I think that this could be accomplished most quickly with a local plugin, to me there would also be an argument for making it part of the core code (just as we include authority file URIs for agents in an exports, I don?t see why the EAD export couldn?t include URIs for containers). Or, much more simply, if you know that your requesting requirements won?t change, and you just need to add the name of a location to the EAD, that could be done with a local plugin that adds that name somewhere to the EAD file (such as an internal-only physloc note). I wouldn?t think that?s something that would belong in the core code, though, since others might consider that information to be sensitive, and it also hasn?t been added to the EAD export mappings. Just my two cents, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman Sent: Thursday, 07 September, 2017 1:13 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] locations and/or barcodes in EAD? Hello everyone, We've never really used the locations modules in ASpace, and are still working our way through top container functionality. Out of curiosity, are the values for a top container's location and barcode included in the EAD export for a resource record? Thinking specifically about how such data can be incorporated into our Aeon requesting workflows. Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From HurtT at easternct.edu Thu Sep 7 14:42:40 2017 From: HurtT at easternct.edu (Hurt, Tara (Library)) Date: Thu, 7 Sep 2017 18:42:40 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades Message-ID: Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From akroeger at unomaha.edu Thu Sep 7 15:01:09 2017 From: akroeger at unomaha.edu (Angela Kroeger) Date: Thu, 7 Sep 2017 19:01:09 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.1.1 quirks Message-ID: We are hosted by Lyrasis, and we recently updated to ArchivesSpace version 2.1.1. We've noticed several quirks and design issues with the new public search interface. (Here's a link to our public interface: http://unomaha-public.lyrasistechnology.org/). If you input multiple search terms, it automatically treats them as a Boolean OR search rather than an AND search. For example, if we search for "Cummington Press" (without quotation marks), it brings up a lot of "press releases" and "press conferences" that do not include the term "Cummington" anywhere. Relevance ranking seems off. Searching "file cabinets" (no quotation marks), the University Archives File Cabinet Collection doesn't appear until halfway down the first page of search results. Searching "file cabinet collection" (with quotation marks), it comes up as the ninth out of nine results (even after the "record group"/repository for University Archives), despite having that exact phrase in the title. If you have one search box and hit return, it executes the search. However, if you have two or more search boxes (added with the plus sign) and hit return, it deletes the second search box. (That is, if you have four search boxes and hit return, number two is the one that disappears.) If you've added multiple search boxes, you must actually click the search button to activate the search. Also, I have a general question regarding a longtime issue, nothing to do with the recent update. Is there some kind of global-edit feature in the staff interface that we're simply not aware of? Is there an API or plugin that could enable this? (And if so, is it available for a hosted site?) For example, we'd like to find and replace all instances of a text string with a different text string across the entire repository, regardless of what type of record or field that text string appears in. Thank you! Angela Kroeger Archives and Special Collections Associate UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu [Media:UniversityCommunications:Graphic Design:Brand tools:Logos- UNO:Vector files:Lock-up:Lockup-color on white backgrnd.eps] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5540 bytes Desc: image003.png URL: From smithkr at mit.edu Thu Sep 7 15:03:06 2017 From: smithkr at mit.edu (Kari R Smith) Date: Thu, 7 Sep 2017 19:03:06 +0000 Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Message-ID: <29F559819ACA9A4FBF208407D4B63ABB0140114217@OC11expo28.exchange.mit.edu> Hello, Is there guidance about the dos and don'ts for formatting (markup) of titles of archival objects? We are trying to find information about adding markup in a title field like when we want to have it formatted with italics or underlining, as we might for a bibliography or to include an "article title" as part of a folder title. I see that within Note fields you can wrap EAD markup but not in the archival objects. Thanks for help pointing to AS user info or organizational specific user manuals. Kari Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maura_carbone at harvard.edu Thu Sep 7 15:09:20 2017 From: maura_carbone at harvard.edu (Carbone, Maura) Date: Thu, 7 Sep 2017 19:09:20 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: References: Message-ID: Hi Tara, What links are broken that you?re trying to access? I?m able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: on behalf of "Hurt, Tara (Library)" Reply-To: Archivesspace Users Group Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From KUTZUBA at hws.edu Thu Sep 7 15:42:57 2017 From: KUTZUBA at hws.edu (Kutzuba, Jamie) Date: Thu, 7 Sep 2017 19:42:57 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: References: Message-ID: <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> Hi Tara- We also experienced the unzipping issue with 1.5.0. Try 1.5.1 instead. Thanks- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Carbone, Maura Sent: Thursday, September 07, 2017 3:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, What links are broken that you?re trying to access? I?m able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: > on behalf of "Hurt, Tara (Library)" > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Thu Sep 7 15:59:11 2017 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Thu, 7 Sep 2017 19:59:11 +0000 Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Message-ID: <890BE460-D888-4524-BC5D-E8A65970BF1B@harvard.edu> Hi Kari, I?m on the techy side of things, so I may be out in ?strictly accurate but not practical? land, but fundamentally, mixed content is more ?allowed in by accident? than ?explicitly supported? in ArchivesSpace. Markup in title fields isn?t handled specially, and, in the case of EAD markup, only works in cases where it _accidentally_ overlaps with HTML. So, I think in an ideal world, the dos and don?ts would be ?please don?t.? I realize that isn?t necessarily practical for all use cases. Bobbi Fox (and others) have done some mitigation work in the new PUI, but there?s not really a ?safe? subset of markup that?s guaranteed to be ok. - Dave Mayo Senior Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Dev Team From: on behalf of Kari R Smith Reply-To: Archivesspace Users Group Date: Thursday, September 7, 2017 at 3:03 PM To: "Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)" Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hello, Is there guidance about the dos and don?ts for formatting (markup) of titles of archival objects? We are trying to find information about adding markup in a title field like when we want to have it formatted with italics or underlining, as we might for a bibliography or to include an ?article title? as part of a folder title. I see that within Note fields you can wrap EAD markup but not in the archival objects. Thanks for help pointing to AS user info or organizational specific user manuals. Kari Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Thu Sep 7 16:12:41 2017 From: noah.huffman at duke.edu (Noah Huffman) Date: Thu, 7 Sep 2017 20:12:41 +0000 Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title In-Reply-To: <890BE460-D888-4524-BC5D-E8A65970BF1B@harvard.edu> References: <890BE460-D888-4524-BC5D-E8A65970BF1B@harvard.edu> Message-ID: Hi Kari, Just to add to Dave?s comments. We?ve been doing some testing of a new EAD3 exporter for ArchivesSpace and mixed content tagging creates all sorts or complications for producing valid EAD3 exports when tags stored in ArchivesSpace note fields and title fields are valid EAD2002 but not valid EAD3. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mayo, Dave Sent: Thursday, September 07, 2017 3:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hi Kari, I?m on the techy side of things, so I may be out in ?strictly accurate but not practical? land, but fundamentally, mixed content is more ?allowed in by accident? than ?explicitly supported? in ArchivesSpace. Markup in title fields isn?t handled specially, and, in the case of EAD markup, only works in cases where it _accidentally_ overlaps with HTML. So, I think in an ideal world, the dos and don?ts would be ?please don?t.? I realize that isn?t necessarily practical for all use cases. Bobbi Fox (and others) have done some mitigation work in the new PUI, but there?s not really a ?safe? subset of markup that?s guaranteed to be ok. - Dave Mayo Senior Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Dev Team From: > on behalf of Kari R Smith > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 3:03 PM To: "Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)" > Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hello, Is there guidance about the dos and don?ts for formatting (markup) of titles of archival objects? We are trying to find information about adding markup in a title field like when we want to have it formatted with italics or underlining, as we might for a bibliography or to include an ?article title? as part of a folder title. I see that within Note fields you can wrap EAD markup but not in the archival objects. Thanks for help pointing to AS user info or organizational specific user manuals. Kari Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Thu Sep 7 16:49:15 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 7 Sep 2017 20:49:15 +0000 Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title In-Reply-To: References: <890BE460-D888-4524-BC5D-E8A65970BF1B@harvard.edu> Message-ID: Kari, all: I?d also add that even though the ArchivesSpace note fields look like they can support EAD markup (and proclaim to be ?Mixed Content Enabled?), it?s not really full-blown support like you?d get with an XML editor or a WYSIWYG interface. For example, if I use the current tag-suggestion feature to add a ?title? element within a note, there?s no indication in the interface that I can then add an ?emph? element child, or even an empty ?lb? element child, etc. If you do, fine, then you?ll still wind up with valid EAD 2002 exports. But if you add a ?persname? child here, ASpace isn?t going to say anything is wrong, but you?ve just invalided your EAD since EAD2002 doesn?t permit ?persname? within a ?title? element. Or if I just make up a tag name, like ??, everything will still look fine (and be highlighted in green) in ASpace. All that said, as a literary archive, the Beinecke uses that ?title? tag a lot, and it?s often used in the title fields of ASpace. So, locally we do permit mixed content for a few things that EAD allows, but definitely not everything (even though you could add ?title? element to container elements in EAD2002, that is definitely not allowed by our best practices!!! ?). That said, we don?t currently rely on ASpace to ensure that we?re following those best practices right now since we don?t (yet) have a local-best-practices-validation button in ASpace, so for now we still ensure that our best practices are being followed by having EAD files exported and validated against a Schematron file. So Kari, I guess that?s a longwinded way of saying two things: * At Yale, we?re moving toward restricting the elements that are allowed in ASpace?s title fields, most likely down to just two: ?title? and ?emph?, even though ASpace does not encourage entering any data there. Before ASpace, we permitted 16 different elements here, although most of those were rarely if ever used. * Be wary of adding mixed-content elements to the ASpace notes, as well! The wrap feature is limited, and it doesn?t preclude folks from typing in anything they want (including HTML, MODS, PREMIS, whatever their poison), including just made up stuff that will still look like it?s valid as long as the start tag name matches the end tag. Usually that?s pretty harmless? but typos. I haven?t yet figured out what limited elements of EAD that we should support within ASpace notes moving forward, but that?s likely going to depend on the work that Noah is doing with Trevor to enable EAD3 support, since I?d like to start exporting valid EAD3 ASAP. Mark p.s. here?s a sample EAD export that illustrates the point about notes + the Mixed Content Enable feature in ASpace: Scope and Contents

title with an <emph>emph</emph>; all legal

type and then a title and a <persname>persname</persname>; not so fast, 'cause that's invalid according to EAD2002.

but seriously, someone might type in a tag name that looks like EAD, even though it?s not; and everything looks fine and valid in ASpace. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman Sent: Thursday, 07 September, 2017 4:13 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hi Kari, Just to add to Dave?s comments. We?ve been doing some testing of a new EAD3 exporter for ArchivesSpace and mixed content tagging creates all sorts or complications for producing valid EAD3 exports when tags stored in ArchivesSpace note fields and title fields are valid EAD2002 but not valid EAD3. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mayo, Dave Sent: Thursday, September 07, 2017 3:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hi Kari, I?m on the techy side of things, so I may be out in ?strictly accurate but not practical? land, but fundamentally, mixed content is more ?allowed in by accident? than ?explicitly supported? in ArchivesSpace. Markup in title fields isn?t handled specially, and, in the case of EAD markup, only works in cases where it _accidentally_ overlaps with HTML. So, I think in an ideal world, the dos and don?ts would be ?please don?t.? I realize that isn?t necessarily practical for all use cases. Bobbi Fox (and others) have done some mitigation work in the new PUI, but there?s not really a ?safe? subset of markup that?s guaranteed to be ok. - Dave Mayo Senior Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Dev Team From: > on behalf of Kari R Smith > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 3:03 PM To: "Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)" > Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hello, Is there guidance about the dos and don?ts for formatting (markup) of titles of archival objects? We are trying to find information about adding markup in a title field like when we want to have it formatted with italics or underlining, as we might for a bibliography or to include an ?article title? as part of a folder title. I see that within Note fields you can wrap EAD markup but not in the archival objects. Thanks for help pointing to AS user info or organizational specific user manuals. Kari Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 7 17:03:26 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 7 Sep 2017 21:03:26 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> References: , <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> Message-ID: As a rule, I usually pick the last point release in a series as expected to be the least buggy. In this case, that would be 1.5.4 and 2.1.2 . You can also look at the release notes for the point releases and see if any of the bug fixes seem significant or necessary. But when in doubt, I'ld go for the latest minor release in a series. The UPGRADING_2.1.0.md doc: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_2.1.0.md says that migrating from 1.4.2 or lower REQUIRES an intermediate upgrade to something between 1.5.0 and 2.0.1. But due to some problems we've seen from the container migration, see email thread from back in January with Subject: Indexer Errors in 1.5.2 http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-January/thread.html and probably some other threads, I recommend migrating first to 1.5.x and fixing all of the container issues before upgrading again. Going from 1.4.2 to 2.0.x without fixing the problems caused the indexer to break, but made it more difficult to find the problem resources. I don't find a 'database.dat' file anywhere in my distribution or anywhere that a file with that names is required. What error are you seeing and on what step? Did you run the scripts/setup-database.{sh,bat} command ? -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kutzuba, Jamie Sent: Thursday, September 7, 2017 3:42:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara- We also experienced the unzipping issue with 1.5.0. Try 1.5.1 instead. Thanks- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Carbone, Maura Sent: Thursday, September 07, 2017 3:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, What links are broken that you?re trying to access? I?m able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: > on behalf of "Hurt, Tara (Library)" > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From susan.thomas at bodleian.ox.ac.uk Tue Sep 5 08:59:05 2017 From: susan.thomas at bodleian.ox.ac.uk (Susan Thomas) Date: Tue, 5 Sep 2017 12:59:05 +0000 Subject: [Archivesspace_Users_Group] Vacancy: Software Engineer (XML-based Technologies), Bodleian Libraries, University of Oxford Message-ID: <5A99199617BA924BB452171D8946B12825310B5E@MBX05.ad.oak.ox.ac.uk> Please see below for an opportunity at the Bodleian Libraries, University of Oxford. The deadline for applications has been extended to 8 September 2017. ---------------------------------------------------- Software Engineer (XML-based Technologies) Bodleian Libraries, Digital Research Team, Bodleian Digital Library Systems and Services (BDLSS), Osney One Building, Osney Mead, Oxford Grade 7: ?31,076 - ?38,183 p.a. For further details and how to apply see: https://www.recruit.ox.ac.uk/pls/hrisliverecruit/erq_jobspec_version_4.jobspec?p_id=129976 The Bodleian Digital Library Systems and Services (BDLSS) at the Bodleian Libraries provide digital services for the students, researchers and staff of the University of Oxford. We are now seeking a talented XML-focused Software Engineer to work on a varied portfolio of projects led by BDLSS. Based in the BDLSS Digital Research team, you will work with a team of developers, project managers, and archivists on a number of key projects to enhance access and discoverability for the Bodleian's world-class special collections. You will initially focus on developing and implementing new technical solutions for post-medieval archival materials and will participate in the scoping and planning of future work in this area. Your role will include developing and helping maintain the Bodleian's growing collections of archives and manuscripts metadata, especially its XML-based catalogues, migrating XML-based catalogue records into new tools and contributing to establishing cataloguing workflows. You will also participate in related user and development communities and in training staff and act as a resource for technical questions and forward planning. You will also have the opportunity to contribute to a variety of future initiatives, including projects focused on metadata management and consolidation, Linked Open Data, and innovative approaches to search and discovery of digital resources. You will have a degree in a relevant technical field, or equivalent experience with structured text processing. You will also have a strong background in XML technologies, a collaborative approach to technical development, and an interest in and commitment to making the Bodleian's collections more widely available to students, researchers and the general public. A background in Digital Humanities or experience in working with EAD and TEI metadata environments is desirable. Owing to the nature of this post, the successful candidate will be required to undertake a Disclosure Scotland check as well as a financial background check. The possession of a criminal record or poor financial background will not necessarily prevent an applicant from obtaining this post, as all cases are judged individually according to the nature of the role and information provided. This post is part of a pilot scheme testing a new Supporting Evidence Form in place of the more usual 'supporting statement'. You MUST submit a completed Supporting Evidence Form and a copy of your CV in order for your application to be processed. Please ensure that you carefully read the How to Apply section provided in the Job Description, which you can download below along with the required Supporting Evidence Form. Only applications received online by 12.00 midday on Friday 8 September 2017 can be considered. Interviews are expected to take place in week commencing 18 September 2017. For further details and how to apply see: https://www.recruit.ox.ac.uk/pls/hrisliverecruit/erq_jobspec_version_4.jobspec?p_id=129976 ---------------------------------------------------- Susan Thomas Head of Archives & Modern Manuscripts Web: http://www.bodleian.ox.ac.uk/special-collections Tel: +44 (0) 1865 283821 Post: Weston Library, Broad Street, Oxford, OX1 3BG -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Sep 8 09:29:10 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 8 Sep 2017 13:29:10 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: References: , <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> Message-ID: Hi Tara, Hopefully the suggestions here on the listserv have gotten you what you need - the releases page in Github (https://github.com/archivesspace/archivesspace/releases) has notes and links for all past releases and the current release - but if you need more help in getting your ArchivesSpace upgraded, we can put a tech support ticket in for you. (This is a benefit of ArchivesSpace membership - more information on the process is available at http://archivesspace.org/member-area/technical-support/.) Please just email us at ArchivesSpaceHome at lyrasis.org if you decide you need that kind of assistance. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Thursday, September 7, 2017 5:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades As a rule, I usually pick the last point release in a series as expected to be the least buggy. In this case, that would be 1.5.4 and 2.1.2 . You can also look at the release notes for the point releases and see if any of the bug fixes seem significant or necessary. But when in doubt, I'ld go for the latest minor release in a series. The UPGRADING_2.1.0.md doc: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_2.1.0.md says that migrating from 1.4.2 or lower REQUIRES an intermediate upgrade to something between 1.5.0 and 2.0.1. But due to some problems we've seen from the container migration, see email thread from back in January with Subject: Indexer Errors in 1.5.2 http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-January/thread.html and probably some other threads, I recommend migrating first to 1.5.x and fixing all of the container issues before upgrading again. Going from 1.4.2 to 2.0.x without fixing the problems caused the indexer to break, but made it more difficult to find the problem resources. I don't find a 'database.dat' file anywhere in my distribution or anywhere that a file with that names is required. What error are you seeing and on what step? Did you run the scripts/setup-database.{sh,bat} command ? -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kutzuba, Jamie > Sent: Thursday, September 7, 2017 3:42:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara- We also experienced the unzipping issue with 1.5.0. Try 1.5.1 instead. Thanks- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Carbone, Maura Sent: Thursday, September 07, 2017 3:09 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, What links are broken that you're trying to access? I'm able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: > on behalf of "Hurt, Tara (Library)" > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- 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 WangCH at si.edu Fri Sep 8 10:03:12 2017 From: WangCH at si.edu (Wang, Ching-Hsien) Date: Fri, 8 Sep 2017 14:03:12 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: References: , <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> , Message-ID: <1195701820F3E943B6BD02FE119E41863CEA3F23@SI-MSEDAG02.US.SINET.SI.EDU> Christine I would like to say THANK YOU for the technical support we have been getting from LYRASIS for our ongoing efforts to migrate from AT. Our journey to migrate from AT to ASpace has many obstacles partially because the size of our collections as well as some extremely large EAD files. Technical staff Blake Carve and Mark Cooper have been knowledgeable and effective in helping us out. I wish the migration scripts can be improved and allow the migration to the more resent ASpace version directly instead of multiple scripts to step through each ASpace versions. If we have more straight forward migration routines, we will have more new archives going live with ASpace. Our technical team George Bowman and Nancy Kennedy will likely to publish our lessons learned after we complete our migration. This may help others in some ways. Thank you for your great support! Ching-hsien Wang Collections Systems & Digital Assets Division, OCIO Smithsonian Institution Capital Gallery, 600 Maryland Ave. SW, Suite 4000, MRC 503 Washington DC. 20024 Phone: 202-633-5581 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Christine Di Bella [christine.dibella at lyrasis.org] Sent: Friday, September 08, 2017 9:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, Hopefully the suggestions here on the listserv have gotten you what you need ? the releases page in Github (https://github.com/archivesspace/archivesspace/releases) has notes and links for all past releases and the current release - but if you need more help in getting your ArchivesSpace upgraded, we can put a tech support ticket in for you. (This is a benefit of ArchivesSpace membership ? more information on the process is available at http://archivesspace.org/member-area/technical-support/.) Please just email us at ArchivesSpaceHome at lyrasis.org if you decide you need that kind of assistance. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Thursday, September 7, 2017 5:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades As a rule, I usually pick the last point release in a series as expected to be the least buggy. In this case, that would be 1.5.4 and 2.1.2 . You can also look at the release notes for the point releases and see if any of the bug fixes seem significant or necessary. But when in doubt, I'ld go for the latest minor release in a series. The UPGRADING_2.1.0.md doc: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_2.1.0.md says that migrating from 1.4.2 or lower REQUIRES an intermediate upgrade to something between 1.5.0 and 2.0.1. But due to some problems we've seen from the container migration, see email thread from back in January with Subject: Indexer Errors in 1.5.2 http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-January/thread.html and probably some other threads, I recommend migrating first to 1.5.x and fixing all of the container issues before upgrading again. Going from 1.4.2 to 2.0.x without fixing the problems caused the indexer to break, but made it more difficult to find the problem resources. I don't find a 'database.dat' file anywhere in my distribution or anywhere that a file with that names is required. What error are you seeing and on what step? Did you run the scripts/setup-database.{sh,bat} command ? -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kutzuba, Jamie > Sent: Thursday, September 7, 2017 3:42:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara- We also experienced the unzipping issue with 1.5.0. Try 1.5.1 instead. Thanks- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Carbone, Maura Sent: Thursday, September 07, 2017 3:09 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, What links are broken that you?re trying to access? I?m able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: > on behalf of "Hurt, Tara (Library)" > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- 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 jane.labarbara at mail.wvu.edu Fri Sep 8 13:50:13 2017 From: jane.labarbara at mail.wvu.edu (Jane LaBarbara) Date: Fri, 8 Sep 2017 17:50:13 +0000 Subject: [Archivesspace_Users_Group] Normalizing dates in bulk? Message-ID: All, If anyone has successfully scripted a method of posting normalized dates into ArchivesSpace resource records en masse, please let me know. When we imported our resource record EAD files, most of our collections had inclusive dates that were not normalized. With the new PUI giving researchers the ability to search a specific range of years, we'd really like to normalize our dates without having a student worker go through and do it by hand for 4300+ resource records. If I can get the data into a spreadsheet, I can pretty easily separate what we have into beginning and ending years, but I need to be able to shove that data back into ArchivesSpace. Bonus points if you can also help us script posting of normalized dates to component records! Thank you, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From HurtT at easternct.edu Fri Sep 8 14:35:11 2017 From: HurtT at easternct.edu (Hurt, Tara (Library)) Date: Fri, 8 Sep 2017 18:35:11 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: References: , <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> Message-ID: Thank you Steve, this is very helpful. Will try Monday AM. Tara From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Thursday, September 7, 2017 5:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades As a rule, I usually pick the last point release in a series as expected to be the least buggy. In this case, that would be 1.5.4 and 2.1.2 . You can also look at the release notes for the point releases and see if any of the bug fixes seem significant or necessary. But when in doubt, I'ld go for the latest minor release in a series. The UPGRADING_2.1.0.md doc: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_2.1.0.md says that migrating from 1.4.2 or lower REQUIRES an intermediate upgrade to something between 1.5.0 and 2.0.1. But due to some problems we've seen from the container migration, see email thread from back in January with Subject: Indexer Errors in 1.5.2 http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-January/thread.html and probably some other threads, I recommend migrating first to 1.5.x and fixing all of the container issues before upgrading again. Going from 1.4.2 to 2.0.x without fixing the problems caused the indexer to break, but made it more difficult to find the problem resources. I don't find a 'database.dat' file anywhere in my distribution or anywhere that a file with that names is required. What error are you seeing and on what step? Did you run the scripts/setup-database.{sh,bat} command ? -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kutzuba, Jamie > Sent: Thursday, September 7, 2017 3:42:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara- We also experienced the unzipping issue with 1.5.0. Try 1.5.1 instead. Thanks- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Carbone, Maura Sent: Thursday, September 07, 2017 3:09 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, What links are broken that you're trying to access? I'm able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: > on behalf of "Hurt, Tara (Library)" > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From HurtT at easternct.edu Fri Sep 8 14:36:33 2017 From: HurtT at easternct.edu (Hurt, Tara (Library)) Date: Fri, 8 Sep 2017 18:36:33 +0000 Subject: [Archivesspace_Users_Group] Help with Upgrades In-Reply-To: <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> References: <536595a2c7204e78968721faaabff529@EXCH13MBX1.hws.edu> Message-ID: Thank you everyone. Trying some directions from UVA ? will see how that goes on Monday AM. If it works, we?ll be good ? if not I resend an update. We have been using github links so keeping my fingers crossed. Tara From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kutzuba, Jamie Sent: Thursday, September 7, 2017 3:43 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara- We also experienced the unzipping issue with 1.5.0. Try 1.5.1 instead. Thanks- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Carbone, Maura Sent: Thursday, September 07, 2017 3:09 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Help with Upgrades Hi Tara, What links are broken that you?re trying to access? I?m able to access the github links: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/ I was also able to unzip the 1.5.0 zip: https://github.com/archivesspace/archivesspace/releases/tag/v1.5.0 Are you attempting to access the github or looking somewhere else? Thanks, Maura From: > on behalf of "Hurt, Tara (Library)" > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 2:42 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Help with Upgrades Good afternoon again. I sent out the previous email this morning. We need some help upgrading from 1.4.2. In the process of using the installation links available, none of the links are working. Where can we find a clean installation file to take us from 1.4.2 to 2.1.2 We understand we may need to run two installations to get us from 1.4 to 2.1 But we cannot find installation files that work. The zip file for 1.5.0 will not properly unzip without errors. The zip file for 2.0.0 unzips but appears to be incomplete: missing set up database.dat file that we need. Thank you for any help you can give. We are at a stand still until we get some help with upgrade installation. Tara 860-326-9448 hurtt at easternct.edu From: Hurt, Tara (Library) Sent: Thursday, September 7, 2017 11:37 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Good morning. Hoping some can answer my question about upgrading to the current Archives Space version. We received the announcement for 2.1.1 and are in the process of upgrading from 1.4.2. When we go to the web site to upgrade there is now a 2.1.2. Can someone give us the best path to upgrade from 1.4.2? We were going to go from 1.4.2 to 1.5.0 then to 2.1.1 BUT now with 2.1.2 what is the best path? Can you also clarify when the My Sequel database is upgraded? We think it is 1.5.0, hence our plan, but we are not sure. Thank you so much. We are trying to complete the upgrades as soon as possible. Looking forward to hear soon. Tara Tara L. Hurt University Archivist Eastern Connecticut State University 860-465-5563 hurtt at easternct.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Fri Sep 8 15:09:41 2017 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Fri, 8 Sep 2017 19:09:41 +0000 Subject: [Archivesspace_Users_Group] Normalizing dates in bulk? Message-ID: Hi Jane, Have you looked at Alex Duryee?s Timewalk plugin? https://github.com/alexduryee/timewalk - it essentially rewires ASpace to do date normalization (if possible according to a fairly wide-ranging set of rules) automatically on save ? you?d then need to trigger save on the resources in question, which shouldn?t be too hard to script. - Dave From: on behalf of Jane LaBarbara Reply-To: Archivesspace Users Group Date: Friday, September 8, 2017 at 1:50 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Normalizing dates in bulk? All, If anyone has successfully scripted a method of posting normalized dates into ArchivesSpace resource records en masse, please let me know. When we imported our resource record EAD files, most of our collections had inclusive dates that were not normalized. With the new PUI giving researchers the ability to search a specific range of years, we?d really like to normalize our dates without having a student worker go through and do it by hand for 4300+ resource records. If I can get the data into a spreadsheet, I can pretty easily separate what we have into beginning and ending years, but I need to be able to shove that data back into ArchivesSpace. Bonus points if you can also help us script posting of normalized dates to component records! Thank you, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Fri Sep 8 16:30:38 2017 From: Kevin.Clair at du.edu (Kevin Clair) Date: Fri, 8 Sep 2017 20:30:38 +0000 Subject: [Archivesspace_Users_Group] PUI search result question Message-ID: <179CAE1B-04B5-41B9-8041-1203C800C7C2@du.edu> Hello, We upgraded to 2.1.1 about a week or two ago, and one of the issues our archivists noticed related to the new PUI is that collections show up very far down in the search results, relative to the staff interface. As an example, a keyword search for ?peter dominick? in the staff interface returns the collection of his papers as the very first hit; at http://duarchives.coalliance.org, it doesn?t show up until page seven. Is that something I can configure in the PUI settings in the config.rb file? For reference purposes it?s hard to have to scroll through multiple pages of results to land on the result for the collection. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From maderikra at vmi.edu Mon Sep 11 08:57:52 2017 From: maderikra at vmi.edu (Maderik, Rachel A) Date: Mon, 11 Sep 2017 12:57:52 +0000 Subject: [Archivesspace_Users_Group] PUI search result question In-Reply-To: <179CAE1B-04B5-41B9-8041-1203C800C7C2@du.edu> References: <179CAE1B-04B5-41B9-8041-1203C800C7C2@du.edu> Message-ID: We?re having the same problem, and have not migrated to the PUI for this reason. I mentioned it a few weeks ago on the list, but when searching our PUI for ?rockenbach papers?, the most relevant record (a collection called ?Samuel D. Rockenbach Papers? which comes up first in the staff interface) doesn?t appear until page 13, with the first 12 pages being filled with this collection?s components (none of which contain both those search terms). Our sandbox is firewalled off, so I?ve attached screenshots of the results. Rachel Maderik Systems and Technology Librarian 501D Preston Library Virginia Military Institute Lexington, VA 24450 540-464-7572 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Friday, September 08, 2017 4:31 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] PUI search result question Hello, We upgraded to 2.1.1 about a week or two ago, and one of the issues our archivists noticed related to the new PUI is that collections show up very far down in the search results, relative to the staff interface. As an example, a keyword search for ?peter dominick? in the staff interface returns the collection of his papers as the very first hit; at http://duarchives.coalliance.org, it doesn?t show up until page seven. Is that something I can configure in the PUI settings in the config.rb file? For reference purposes it?s hard to have to scroll through multiple pages of results to land on the result for the collection. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: searchresults2.jpg Type: image/jpeg Size: 435112 bytes Desc: searchresults2.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: searchresults1.jpg Type: image/jpeg Size: 462088 bytes Desc: searchresults1.jpg URL: From ltang5 at lib.msu.edu Mon Sep 11 10:10:14 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 11 Sep 2017 14:10:14 +0000 Subject: [Archivesspace_Users_Group] PUI search result question Message-ID: <27FCAD28-4F57-44E8-B645-C4A5C9E305EA@lib.msu.edu> Hi all, I?ve created a JIRA about this. Please let me know if I?ve described it accurately and please feel free to edit if you have other aspects to add! https://archivesspace.atlassian.net/browse/AR-1882 Lydia From: on behalf of "Maderik, Rachel A" Reply-To: Archivesspace Users Group Date: Monday, September 11, 2017 at 8:57 AM To: 'Archivesspace Users Group' Subject: Re: [Archivesspace_Users_Group] PUI search result question We?re having the same problem, and have not migrated to the PUI for this reason. I mentioned it a few weeks ago on the list, but when searching our PUI for ?rockenbach papers?, the most relevant record (a collection called ?Samuel D. Rockenbach Papers? which comes up first in the staff interface) doesn?t appear until page 13, with the first 12 pages being filled with this collection?s components (none of which contain both those search terms). Our sandbox is firewalled off, so I?ve attached screenshots of the results. Rachel Maderik Systems and Technology Librarian 501D Preston Library Virginia Military Institute Lexington, VA 24450 540-464-7572 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Friday, September 08, 2017 4:31 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] PUI search result question Hello, We upgraded to 2.1.1 about a week or two ago, and one of the issues our archivists noticed related to the new PUI is that collections show up very far down in the search results, relative to the staff interface. As an example, a keyword search for ?peter dominick? in the staff interface returns the collection of his papers as the very first hit; at http://duarchives.coalliance.org, it doesn?t show up until page seven. Is that something I can configure in the PUI settings in the config.rb file? For reference purposes it?s hard to have to scroll through multiple pages of results to land on the result for the collection. thanks! -k From kate_bowers at harvard.edu Mon Sep 11 11:40:30 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Mon, 11 Sep 2017 15:40:30 +0000 Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title In-Reply-To: References: <890BE460-D888-4524-BC5D-E8A65970BF1B@harvard.edu> Message-ID: Mark: This is a great summary of the issues, and because we have all kinds of mixed content migrated into AS in unit titles, I can see that lots of our EAD3 from AS will be invalid. Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Thursday, September 07, 2017 4:49 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Kari, all: I?d also add that even though the ArchivesSpace note fields look like they can support EAD markup (and proclaim to be ?Mixed Content Enabled?), it?s not really full-blown support like you?d get with an XML editor or a WYSIWYG interface. For example, if I use the current tag-suggestion feature to add a ?title? element within a note, there?s no indication in the interface that I can then add an ?emph? element child, or even an empty ?lb? element child, etc. If you do, fine, then you?ll still wind up with valid EAD 2002 exports. But if you add a ?persname? child here, ASpace isn?t going to say anything is wrong, but you?ve just invalided your EAD since EAD2002 doesn?t permit ?persname? within a ?title? element. Or if I just make up a tag name, like ??, everything will still look fine (and be highlighted in green) in ASpace. All that said, as a literary archive, the Beinecke uses that ?title? tag a lot, and it?s often used in the title fields of ASpace. So, locally we do permit mixed content for a few things that EAD allows, but definitely not everything (even though you could add ?title? element to container elements in EAD2002, that is definitely not allowed by our best practices!!! ?). That said, we don?t currently rely on ASpace to ensure that we?re following those best practices right now since we don?t (yet) have a local-best-practices-validation button in ASpace, so for now we still ensure that our best practices are being followed by having EAD files exported and validated against a Schematron file. So Kari, I guess that?s a longwinded way of saying two things: * At Yale, we?re moving toward restricting the elements that are allowed in ASpace?s title fields, most likely down to just two: ?title? and ?emph?, even though ASpace does not encourage entering any data there. Before ASpace, we permitted 16 different elements here, although most of those were rarely if ever used. * Be wary of adding mixed-content elements to the ASpace notes, as well! The wrap feature is limited, and it doesn?t preclude folks from typing in anything they want (including HTML, MODS, PREMIS, whatever their poison), including just made up stuff that will still look like it?s valid as long as the start tag name matches the end tag. Usually that?s pretty harmless? but typos. I haven?t yet figured out what limited elements of EAD that we should support within ASpace notes moving forward, but that?s likely going to depend on the work that Noah is doing with Trevor to enable EAD3 support, since I?d like to start exporting valid EAD3 ASAP. Mark p.s. here?s a sample EAD export that illustrates the point about notes + the Mixed Content Enable feature in ASpace: Scope and Contents

title with an <emph>emph</emph>; all legal

type and then a title and a <persname>persname</persname>; not so fast, 'cause that's invalid according to EAD2002.

but seriously, someone might type in a tag name that looks like EAD, even though it?s not; and everything looks fine and valid in ASpace. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman Sent: Thursday, 07 September, 2017 4:13 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hi Kari, Just to add to Dave?s comments. We?ve been doing some testing of a new EAD3 exporter for ArchivesSpace and mixed content tagging creates all sorts or complications for producing valid EAD3 exports when tags stored in ArchivesSpace note fields and title fields are valid EAD2002 but not valid EAD3. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mayo, Dave Sent: Thursday, September 07, 2017 3:59 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hi Kari, I?m on the techy side of things, so I may be out in ?strictly accurate but not practical? land, but fundamentally, mixed content is more ?allowed in by accident? than ?explicitly supported? in ArchivesSpace. Markup in title fields isn?t handled specially, and, in the case of EAD markup, only works in cases where it _accidentally_ overlaps with HTML. So, I think in an ideal world, the dos and don?ts would be ?please don?t.? I realize that isn?t necessarily practical for all use cases. Bobbi Fox (and others) have done some mitigation work in the new PUI, but there?s not really a ?safe? subset of markup that?s guaranteed to be ok. - Dave Mayo Senior Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Dev Team From: > on behalf of Kari R Smith > Reply-To: Archivesspace Users Group > Date: Thursday, September 7, 2017 at 3:03 PM To: "Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)" > Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title Hello, Is there guidance about the dos and don?ts for formatting (markup) of titles of archival objects? We are trying to find information about adding markup in a title field like when we want to have it formatted with italics or underlining, as we might for a bibliography or to include an ?article title? as part of a folder title. I see that within Note fields you can wrap EAD markup but not in the archival objects. Thanks for help pointing to AS user info or organizational specific user manuals. Kari Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Mon Sep 11 11:59:08 2017 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Mon, 11 Sep 2017 11:59:08 -0400 Subject: [Archivesspace_Users_Group] Pointer to choices for formatting the title of an archival object, such as an article title In-Reply-To: References: <890BE460-D888-4524-BC5D-E8A65970BF1B@harvard.edu> Message-ID: The EAD3 exporter we're working on will attempt to convert mixed content stored in the database to valid EAD3, either by renaming tags/attributes, adding new elements when appropriate (e.g. wrapping contents of controlled access elements in ), or "unwrapping" tagged content when a suitable substitution can't be easily determined. It's highly unlikely that it will account for every situation in every repository, but the output should have far fewer validation problems than it would otherwise, and there should be opportunities for incremental improvement to this functionality in the future. On Mon, Sep 11, 2017 at 11:40 AM, Bowers, Kate A. wrote: > Mark: > > > > This is a great summary of the issues, and because we have all kinds of > mixed content migrated into AS in unit titles, I can see that > lots of our EAD3 from AS will be invalid. > > > > Kate > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Custer, > Mark > *Sent:* Thursday, September 07, 2017 4:49 PM > > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Pointer to choices for > formatting the title of an archival object, such as an article title > > > > Kari, all: > > > > I?d also add that even though the ArchivesSpace note fields look like they > can support EAD markup (and proclaim to be ?Mixed Content Enabled?), it?s > not really full-blown support like you?d get with an XML editor or a > WYSIWYG interface. For example, if I use the current tag-suggestion > feature to add a ?title? element within a note, there?s no indication in > the interface that I can then add an ?emph? element child, or even an empty > ?lb? element child, etc. If you do, fine, then you?ll still wind up with > valid EAD 2002 exports. But if you add a ?persname? child here, ASpace > isn?t going to say anything is wrong, but you?ve just invalided your EAD > since EAD2002 doesn?t permit ?persname? within a ?title? element. Or if I > just make up a tag name, like ??, > everything will still look fine (and be highlighted in green) in ASpace. > > > > All that said, as a literary archive, the Beinecke uses that ?title? tag a > lot, and it?s often used in the title fields of ASpace. So, locally we do > permit mixed content for a few things that EAD allows, but definitely not > everything (even though you *could* add ?title? element to container > elements in EAD2002, that is definitely not allowed by our best > practices!!! J). That said, we don?t currently rely on ASpace to ensure > that we?re following those best practices right now since we don?t (yet) > have a local-best-practices-validation button in ASpace, so for now we > still ensure that our best practices are being followed by having EAD files > exported and validated against a Schematron file. > > > > So Kari, I guess that?s a longwinded way of saying two things: > > > > - At Yale, we?re moving toward restricting the elements that are > allowed in ASpace?s title fields, most likely down to just two: ?title? > and ?emph?, even though ASpace does not encourage entering any data there. > Before ASpace, we permitted 16 different elements here, although most of > those were rarely if ever used. > - Be wary of adding mixed-content elements to the ASpace notes, as > well! The wrap feature is limited, and it doesn?t preclude folks from > typing in anything they want (including HTML, MODS, PREMIS, whatever their > poison), including just made up stuff that will still look like it?s valid > as long as the start tag name matches the end tag. Usually that?s pretty > harmless? but typos. I haven?t yet figured out what limited elements of > EAD that we should support within ASpace notes moving forward, but that?s > likely going to depend on the work that Noah is doing with Trevor to enable > EAD3 support, since I?d like to start exporting valid EAD3 ASAP. > > > > Mark > > > > p.s. here?s a sample EAD export that illustrates the point about notes + > the Mixed Content Enable feature in ASpace: > > > > > Scope and Contents >

title with an <emph>emph</emph>; all legal

>

type and then a title and a <persname>persname > </persname>; not so fast, 'cause that's invalid according to > EAD2002.

>

but seriously, someone might type in a tag > name that looks like EAD, even though it?s not; and everything looks fine > and valid in ASpace. > > > > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Noah > Huffman > *Sent:* Thursday, 07 September, 2017 4:13 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Pointer to choices for > formatting the title of an archival object, such as an article title > > > > Hi Kari, > > > > Just to add to Dave?s comments. We?ve been doing some testing of a new > EAD3 exporter for ArchivesSpace and mixed content tagging creates all sorts > or complications for producing valid EAD3 exports when tags stored in > ArchivesSpace note fields and title fields are valid EAD2002 but not valid > EAD3. > > > > -Noah > > > > ================ > > Noah Huffman > > Archivist for Metadata, Systems, and Digital Records > > David M. Rubenstein Rare Book & Manuscript Library > > Duke University | 919-660-5982 <(919)%20660-5982> > > http://library.duke.edu/rubenstein/ > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Mayo, > Dave > *Sent:* Thursday, September 07, 2017 3:59 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Pointer to choices for > formatting the title of an archival object, such as an article title > > > > Hi Kari, > > I?m on the techy side of things, so I may be out in ?strictly accurate but > not practical? land, but fundamentally, mixed content is more ?allowed in > by accident? than ?explicitly supported? in ArchivesSpace. Markup in title > fields isn?t handled specially, and, in the case of EAD markup, only works > in cases where it _*accidentally*_ overlaps with HTML. So, I think in an > ideal world, the dos and don?ts would be ?please don?t.? I realize that > isn?t necessarily practical for all use cases. Bobbi Fox (and others) have > done some mitigation work in the new PUI, but there?s not really a ?safe? > subset of markup that?s guaranteed to be ok. > > - Dave Mayo > Senior Digital Library Software Engineer > Harvard University > HUIT > LTS > OSC Dev Team > > > > *From: * on > behalf of Kari R Smith > *Reply-To: *Archivesspace Users Group lyralists.lyrasis.org> > *Date: *Thursday, September 7, 2017 at 3:03 PM > *To: *"Archivesspace Users Group (archivesspace_users_group@ > lyralists.lyrasis.org)" > *Subject: *[Archivesspace_Users_Group] Pointer to choices for formatting > the title of an archival object, such as an article title > > > > Hello, > > Is there guidance about the dos and don?ts for formatting (markup) of > titles of archival objects? We are trying to find information about adding > markup in a title field like when we want to have it formatted with italics > or underlining, as we might for a bibliography or to include an ?article > title? as part of a folder title. > > > > I see that within Note fields you can wrap EAD markup but not in the > archival objects. > > > > Thanks for help pointing to AS user info or organizational specific user > manuals. > > > > Kari > > > > Kari R. Smith > > Digital Archivist and Program Head for Born-digital Archives > > Institute Archives and Special Collections > > Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts > > 617.253.5690 <(617)%20253-5690> smithkr at mit.edu > http://libraries.mit.edu/archives/ > > @karirene69 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From eef46 at cornell.edu Mon Sep 11 14:31:07 2017 From: eef46 at cornell.edu (Erin Faulder) Date: Mon, 11 Sep 2017 18:31:07 +0000 Subject: [Archivesspace_Users_Group] Migrating and maintaining item-level records in ILS and/or ASpace Message-ID: All, RMC at Cornell is in the weeds identifying bib records to migrate from our ILS into ASpace. Our practice, historically, has been to catalog collections and occasionally items within the collection in our ILS to better facilitate discovery. As we move into ASpace, we are cognizant that we should incorporate those item records within the context of the collection by including them as archival objects in ASpace under the appropriate resource record. We have three primary choices to do this, each with serious trade offs: - Leaving the item-level records in our ILS without representing them in ASpace other than a referencing note at collection/series level o We would lose contextual meaning of those items o We would maintain item-level discovery of content in OCLC/World-Cat o We would be unable to manage our location data of that material in ASpace alongside the rest of the collection - Leave the item-level records in our ILS and represent them in ASpace in their appropriate intellectual arrangement o We would have to build a way to connect the records between the two systems, designing complex methods for synchronizing descriptive metadata as well as location data between systems and setting currently minimally-enforceable rules about where the data is updated and which is the system of record o We would maintain contextual information about their collection and have item-level discovery in OCLC/World-Cat - Represent the item-level records only in ASpace and remove them from the ILS entirely o We would only have to manage the data in one system, eliminating complexity o We would lose item-level discovery of content in OCLC/World-Cat o We could manage location data the same across our content We would love to talk with anyone who has experience cataloging items in a collection at the item-level in their ILS and how they addressed the challenges presented when working with ASpace. Best, Erin -- Erin Faulder Digital Archivist Division of Rare and Manuscript Collections Cornell University Library Ithaca, NY 14853 erin.faulder at cornell.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at minorscience.com Mon Sep 11 14:59:21 2017 From: j at minorscience.com (Jason Loeffler) Date: Mon, 11 Sep 2017 14:59:21 -0400 Subject: [Archivesspace_Users_Group] Migrating and maintaining item-level records in ILS and/or ASpace In-Reply-To: References: Message-ID: Hi Erin, We've set up a few local processes to handle a similar use case. In the past, we've exported MARC formatted records from our Koha ILS then migrated them into ArchivesSpace-ready JSON format using Catmandu fixes, modifying descriptive and structural metadata as needed. Catmandu offers a fairly high-level meta-language with which you can script conditional rule sets. One major issue we're dealing with now is synchronizing and enforcing authority data between the two systems. That piece of the puzzle is very much a work-in-progress. Looking ahead, both Koha and ArchivesSpace have nascent OAI-PMH services, and we hope to exploit these capacities in the future, though the former is amidst QA. Feel free to continue the discussion here or contact me directly off list. Best wishes, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Mon, Sep 11, 2017 at 2:31 PM, Erin Faulder wrote: > All, > > RMC at Cornell is in the weeds identifying bib records to migrate from our > ILS into ASpace. Our practice, historically, has been to catalog > collections and occasionally items within the collection in our ILS to > better facilitate discovery. As we move into ASpace, we are cognizant that > we should incorporate those item records within the context of the > collection by including them as archival objects in ASpace under the > appropriate resource record. > > > > We have three primary choices to do this, each with serious trade offs: > > - Leaving the item-level records in our ILS without representing > them in ASpace other than a referencing note at collection/series level > > o We would lose contextual meaning of those items > > o We would maintain item-level discovery of content in OCLC/World-Cat > > o We would be unable to manage our location data of that material in > ASpace alongside the rest of the collection > > - Leave the item-level records in our ILS and represent them in > ASpace in their appropriate intellectual arrangement > > o We would have to build a way to connect the records between the two > systems, designing complex methods for synchronizing descriptive metadata > as well as location data between systems and setting currently > minimally-enforceable rules about where the data is updated and which is > the system of record > > o We would maintain contextual information about their collection and > have item-level discovery in OCLC/World-Cat > > - Represent the item-level records only in ASpace and remove them > from the ILS entirely > > o We would only have to manage the data in one system, eliminating > complexity > > o We would lose item-level discovery of content in OCLC/World-Cat > > o We could manage location data the same across our content > > > > We would love to talk with anyone who has experience cataloging items in a > collection at the item-level in their ILS and how they addressed the > challenges presented when working with ASpace. > > > > Best, > > Erin > > > > -- > > Erin Faulder > > Digital Archivist > > Division of Rare and Manuscript Collections > > Cornell University Library > > Ithaca, NY 14853 > > erin.faulder at cornell.edu > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From egadsby at towson.edu Mon Sep 11 15:44:51 2017 From: egadsby at towson.edu (Gadsby, Eric T.) Date: Mon, 11 Sep 2017 19:44:51 +0000 Subject: [Archivesspace_Users_Group] Best UNIX permissions for Aspace Message-ID: <0114BA9D-A89C-41A3-A2F7-50CD7958A2FF@towson.edu> Good Afternoon, I hope everybody is well. Our enterprise?s security staff have identified some issues with our filesystem security. What have folks found is the best permissions to use for their AS install? Thanks in advance! Eric T Gadsby ? IT Operations Specialist University Libraries Towson University ? 8000 York Road ? Towson, Maryland, 21252-0001 p. 410-704-3340 [cid:image001.gif at 01D2C97F.CDBCFCB0] Confidentiality Notice: This message may contain information that is confidential, privileged, proprietary, or otherwise legally exempt from disclosure. If you are not the intended recipient, you are notified that you are not authorized to read, print, copy or disseminate this message, any part of it, or any attachments. If this message has been sent to you in error, please notify the sender by replying to this transmission, or by calling University Libraries at 410-704-3340. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1459 bytes Desc: image001.gif URL: From kayiwa at princeton.edu Tue Sep 12 08:11:03 2017 From: kayiwa at princeton.edu (Francis Kayiwa) Date: Tue, 12 Sep 2017 08:11:03 -0400 Subject: [Archivesspace_Users_Group] Best UNIX permissions for Aspace In-Reply-To: <0114BA9D-A89C-41A3-A2F7-50CD7958A2FF@towson.edu> References: <0114BA9D-A89C-41A3-A2F7-50CD7958A2FF@towson.edu> Message-ID: <222d0b92-1686-970a-003b-8137be90737e@princeton.edu> Heya, On 9/11/17 3:44 PM, Gadsby, Eric T. wrote: > Good Afternoon, > > I hope everybody is well. Our enterprise?s security staff have > identified some issues with our filesystem security. What have folks > found is the best permissions to use for their AS install? Thanks in > advance!? > Are you willing (allowed) to share what they have found? We run ours with a _archivesspace service using /usr/sbin/nologin shell. That said I'd welcome the report they provided you to see if there's other things we can do. Cheers, ./fxk -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From smithkr at mit.edu Tue Sep 12 11:03:25 2017 From: smithkr at mit.edu (Kari R Smith) Date: Tue, 12 Sep 2017 15:03:25 +0000 Subject: [Archivesspace_Users_Group] Download CSV from Top Container Search Results - ERROR Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01401214AF@OC11expo28.exchange.mit.edu> We were trying to download the CSV file as noted on the Top container, search results download option. (See attached csv file and screenshot of the Search Results page. Top Container (VIEW) [see the list of Linked Records] button [Go To Search Results] Search Results button [download CSV] I tried this in the Sandbox, EUA repository (there's only 1 Resource record). As you can see from the CSV file, it is not a download of the search results, but rather a complete download of EVERYTHING in the repo, which we discovered when we tried this from one of our Top Containers and the resulting CSV file is 3.6GB. I don't think this is the intended behavior. Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: container_results_downloadCSV.JPG Type: image/jpeg Size: 133571 bytes Desc: container_results_downloadCSV.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 1505226755.csv Type: application/octet-stream Size: 1140438 bytes Desc: 1505226755.csv URL: From Alston.Cobourn at tamucc.edu Tue Sep 12 17:54:28 2017 From: Alston.Cobourn at tamucc.edu (Cobourn, Alston) Date: Tue, 12 Sep 2017 21:54:28 +0000 Subject: [Archivesspace_Users_Group] public-formats plugin issue on 2.1.2 Message-ID: We just upgraded from 1.5.3 to 2.1.2. My IT guy says that the public-formats plugin was not playing nice with the version of ArchivesSpace and therefore he has disabled it. Has anyone else encountered this issue? Also, the print button on the public user interface gives us an error message. I am assuming this is because the public-formats plugin is disabled. Does that seem correct? Thanks, Alston Cobourn Processing and Digital Assets Archivist Texas A&M-Corpus Christi Alston.cobourn at tamucc.edu 361-825-2300 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Daniel.Thacker at tamuk.edu Wed Sep 13 12:04:26 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Wed, 13 Sep 2017 16:04:26 +0000 Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Message-ID: Hello all, Can we add more identifier fields under basic information on the collection level? I attached a picture in case it helps. Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled.jpg Type: image/jpeg Size: 96995 bytes Desc: Untitled.jpg URL: From kayiwa at princeton.edu Wed Sep 13 14:06:55 2017 From: kayiwa at princeton.edu (Francis Kayiwa) Date: Wed, 13 Sep 2017 14:06:55 -0400 Subject: [Archivesspace_Users_Group] Global Admin vs admin Message-ID: <8254a8d7-de6e-da9a-e2e6-6f242d1d447e@princeton.edu> Based on these generated logs I, [2017-09-13T10:55:52.039150 #20051] INFO -- : Rendered shared/_templates.html.erb (4.1ms) I, [2017-09-13T10:55:52.039659 #20051] INFO -- : Filter chain halted as :user_needs_to_be_global_admin rendered or redirected I, [2017-09-13T10:55:52.039907 #20051] INFO -- : Completed 200 OK in 117ms (Views: 84.5ms) I am assuming only one user is allowed to be a global admin, yes? I have a user who is granted admin rights but unable to view the system info for example. Thank you in advance for any pointers. We are running Archivesspace v2.1.2 cheers, ./fxk -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From christine.dibella at lyrasis.org Thu Sep 14 13:38:24 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 14 Sep 2017 17:38:24 +0000 Subject: [Archivesspace_Users_Group] public-formats plugin issue on 2.1.2 In-Reply-To: References: Message-ID: Hi Alston, I believe the public formats plugin has not been updated to be compatible with 2.1.2. (In fact, I don't believe it's been updated for awhile.) It was developed outside of ArchivesSpace and is not part of what's maintained centrally by the program. The 2.1.x PUI versions do include a print button as part of a standard installation. This function is not tied in to the public-formats plugin. So disabling that plugin should not have an effect on whether the print button displays or works. If you/your IT people need help troubleshooting this particular issue, feel free to email ArchivesSpaceHome at lyrasis.org about putting in a tech support ticket. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Cobourn, Alston Sent: Tuesday, September 12, 2017 5:54 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] public-formats plugin issue on 2.1.2 We just upgraded from 1.5.3 to 2.1.2. My IT guy says that the public-formats plugin was not playing nice with the version of ArchivesSpace and therefore he has disabled it. Has anyone else encountered this issue? Also, the print button on the public user interface gives us an error message. I am assuming this is because the public-formats plugin is disabled. Does that seem correct? Thanks, Alston Cobourn Processing and Digital Assets Archivist Texas A&M-Corpus Christi Alston.cobourn at tamucc.edu 361-825-2300 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Thu Sep 14 13:48:10 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 14 Sep 2017 17:48:10 +0000 Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information In-Reply-To: References: Message-ID: Hi Daniel, This is the kind of thing that you could probably do with a plugin and others on here could give you some guidance on that. I'm curious, though, why you want to add another field for identifier. Each box can take up to something like 50 characters. I'm interested to know your use case and how you need to be able to represent your identifiers. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, September 13, 2017 12:04 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Hello all, Can we add more identifier fields under basic information on the collection level? I attached a picture in case it helps. Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From Daniel.Thacker at tamuk.edu Thu Sep 14 16:45:23 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Thu, 14 Sep 2017 20:45:23 +0000 Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information In-Reply-To: References: , Message-ID: Hello Christine, I was wondering if I would get this question and please correct us if we are doing something wrong. On the collection level, we are putting the accessions that make up the collection in the identifier fields. I attached an example. And if there were more than 4 we would put the rest of the accessions in the Repository Processing Note. This helps us because in our old database collections could only be put in one accession at time. You couldn't intermingle the accessions within a collection like you can with ArchiveSpace. It just lets us know the accessions in the collection. So, I guess there is a plug-in for this if this is how we wanted to proceed? I haven't heard from anybody yet. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Thursday, September 14, 2017 12:48:10 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Hi Daniel, This is the kind of thing that you could probably do with a plugin and others on here could give you some guidance on that. I?m curious, though, why you want to add another field for identifier. Each box can take up to something like 50 characters. I?m interested to know your use case and how you need to be able to represent your identifiers. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, September 13, 2017 12:04 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Hello all, Can we add more identifier fields under basic information on the collection level? I attached a picture in case it helps. Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled.jpg Type: image/jpeg Size: 135281 bytes Desc: Untitled.jpg URL: From christine.dibella at lyrasis.org Thu Sep 14 16:57:16 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 14 Sep 2017 20:57:16 +0000 Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information In-Reply-To: References: , Message-ID: Hi Daniel, Ah, thanks for the explanation. I think you may want to do this a different way. The more usual way to handle this would be to use the Related Accessions sub-record (or the Related Resources sub-record if you're doing this from the Accession side). You can link as many accessions as you want that way, and they'll also work as actual links to the accession records. The user manual has some information about this at https://docs.archivesspace.org/Default.htm#SubRecsRelatedAccessions.htm. The identifier field in a resource record would usually be for the call number or anything else you use to number/uniquely identify the collection itself. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, September 14, 2017 4:45 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Hello Christine, I was wondering if I would get this question and please correct us if we are doing something wrong. On the collection level, we are putting the accessions that make up the collection in the identifier fields. I attached an example. And if there were more than 4 we would put the rest of the accessions in the Repository Processing Note. This helps us because in our old database collections could only be put in one accession at time. You couldn't intermingle the accessions within a collection like you can with ArchiveSpace. It just lets us know the accessions in the collection. So, I guess there is a plug-in for this if this is how we wanted to proceed? I haven't heard from anybody yet. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Thursday, September 14, 2017 12:48:10 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Hi Daniel, This is the kind of thing that you could probably do with a plugin and others on here could give you some guidance on that. I'm curious, though, why you want to add another field for identifier. Each box can take up to something like 50 characters. I'm interested to know your use case and how you need to be able to represent your identifiers. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, September 13, 2017 12:04 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Can we add more Identifier fields under basic information Hello all, Can we add more identifier fields under basic information on the collection level? I attached a picture in case it helps. Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From brent_ellingson at byu.edu Thu Sep 14 17:29:09 2017 From: brent_ellingson at byu.edu (Brent Ellingson) Date: Thu, 14 Sep 2017 21:29:09 +0000 Subject: [Archivesspace_Users_Group] Error with collection level display in admin screen Message-ID: <2b7278fff6b84c21b50679be21b4622f@MB7.byu.local> Greeting all, We are running 1.5.4 and have 2 collections that error out when trying to access the Collection level data on the admin screen. The URL is [HOST]/resources/1540#tree::resource_1540 I'm seeing a HTML 404 error code when this URL is requested via JavaScript [HOST]/resources/1540?inline=true&resource_id=1540 In the browser below the hierarchy of the collection where the form and content usually display all I see is the following 'An error occurred loading this form. Not Found' The Series and Sub-Series links in the hierarchy seem to be working without problems. This is what I believe is the error in the logs that corresponds at least in part to the problem **** Error log message **** Started GET "/error/error.php" for 0:0:0:0:0:0:0:1 at 2017-09-14 12:44:03 -0600 ActionController::RoutingError (No route matches [GET] "/error/error.php"): actionpack (3.2.22.2) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.22.2) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.22.2) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.7) lib/rack/methodoverride.rb:21:in `call' rack (1.4.7) lib/rack/runtime.rb:17:in `call' activesupport (3.2.22.2) lib/active_support/cache/strategy/local_cache.rb:72:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/static.rb:83:in `call' rack-cache (1.6.1) lib/rack/cache/context.rb:140:in `forward' rack-cache (1.6.1) lib/rack/cache/context.rb:249:in `fetch' rack-cache (1.6.1) lib/rack/cache/context.rb:189:in `lookup' rack-cache (1.6.1) lib/rack/cache/context.rb:66:in `call!' rack-cache (1.6.1) lib/rack/cache/context.rb:51:in `call' railties (3.2.22.2) lib/rails/engine.rb:484:in `call' railties (3.2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' **** END error log message **** The response as shown in the browser dev tools is below **** Beginning of Dev tools response body **** Action Controller: Exception caught

Routing Error

No route matches [GET] "/error/error.php"

Try running rake routes for more information on available routes.

**** End of Dev tools response body **** Also, we recently upgraded from 1.4.2 to 1.5.4 I'm trying to figure out how to debug this and find where the problem is. Does anyone have any ideas on where to start or look to locate the problem? Thank you for your help. Regards, __________________________ Brent Ellingson Manager of Web Development BYU Library 801-422-6148 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brent_ellingson at byu.edu Fri Sep 15 11:13:04 2017 From: brent_ellingson at byu.edu (Brent Ellingson) Date: Fri, 15 Sep 2017 15:13:04 +0000 Subject: [Archivesspace_Users_Group] Error with collection level display in admin screen Message-ID: <81f15818f28340629dcd07eaa8d7ad42@MB7.byu.local> Here is an error log entry that I'm hoping will be more relevant to the root of the problem Started GET "/resources/1540" for 0:0:0:0:0:0:0:1 at 2017-09-15 08:57:57 -0600 Processing by ResourcesController#show as HTML Parameters: {"id"=>"1540"} Rendered shared/_breadcrumb.html.erb (1.0ms) Rendered transfer/_transfer_failures.html.erb (0.0ms) Rendered shared/_tree.html.erb (3.0ms) Rendered resources/show.html.erb within layouts/application (9.0ms) Rendered shared/_browser_support.html.erb (0.0ms) Rendered shared/_header_user.html.erb (5.0ms) Rendered shared/_header_global.html.erb (6.0ms) Rendered site/_branding.html.erb (0.0ms) Rendered shared/_advanced_search.html.erb (5.0ms) Rendered shared/_header_repository.html.erb (17.0ms) Rendered site/_footer.html.erb (0.0ms) Rendered shared/_templates.html.erb (3.0ms) Completed 200 OK in 2033.0ms (Views: 42.0ms) ri"=>"root", "hash"=>"tree::resource_1540", "id"=>"1540"} :resource_1540" for 0:0:0:0:0:0:0:1 at 2017-09-15 08:58:00 -0600 Processing by ResourcesController#tree as */* Parameters: {"node_uri"=>"root", "hash"=>"tree::resource_1540", "id"=>"1540"} Completed 200 OK in 860.0ms (Views: 17.0ms) Started GET "/resources/1540?inline=true&resource_id=1540" for 0:0:0:0:0:0:0:1 at 2017-09-15 08:58:01 -0600 Processing by ResourcesController#show as */* Parameters: {"inline"=>"true", "resource_id"=>"1540", "id"=>"1540"} .... ABOUT A MINUTE LATER This shows up in the logs at the same time as the 'An error occurred loading this form. Not Found' message shows up on the browser .... _dispatch/middleware/debug_exceptions.rb:21:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.22.2) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.22.2) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.7) lib/rack/methodoverride.rb:21:in `call' rack (1.4.7) lib/rack/runtime.rb:17:in `call' activesupport (3.2.22.2) lib/active_support/cache/strategy/local_cache.rb:72:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/static.rb:83:in `call' rack-cache (1.6.1) lib/rack/cache/context.rb:140:in `forward' rack-cache (1.6.1) lib/rack/cache/context.rb:249:in `fetch' rack-cache (1.6.1) lib/rack/cache/context.rb:189:in `lookup' rack-cache (1.6.1) lib/rack/cache/context.rb:66:in `call!' rack-cache (1.6.1) lib/rack/cache/context.rb:51:in `call' railties (3.2.22.2) lib/rails/engine.rb:484:in `call' railties (3.2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4-stg/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' 2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4-stg/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' Rendered /srv/asstg/gems/gems/actionpack-3.2.22.2/lib/action_dispatch/middleware/templates/rescues/routing_error.erb within rescues/layout (1.0ms) Any thoughts? Regards, Brent Ellingson From: Brent Ellingson Sent: Thursday, September 14, 2017 3:29 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) (archivesspace_users_group at lyralists.lyrasis.org) Subject: Error with collection level display in admin screen Greeting all, We are running 1.5.4 and have 2 collections that error out when trying to access the Collection level data on the admin screen. The URL is [HOST]/resources/1540#tree::resource_1540 I'm seeing a HTML 404 error code when this URL is requested via JavaScript [HOST]/resources/1540?inline=true&resource_id=1540 In the browser below the hierarchy of the collection where the form and content usually display all I see is the following 'An error occurred loading this form. Not Found' The Series and Sub-Series links in the hierarchy seem to be working without problems. This is what I believe is the error in the logs that corresponds at least in part to the problem **** Error log message **** Started GET "/error/error.php" for 0:0:0:0:0:0:0:1 at 2017-09-14 12:44:03 -0600 ActionController::RoutingError (No route matches [GET] "/error/error.php"): actionpack (3.2.22.2) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.22.2) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.22.2) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.7) lib/rack/methodoverride.rb:21:in `call' rack (1.4.7) lib/rack/runtime.rb:17:in `call' activesupport (3.2.22.2) lib/active_support/cache/strategy/local_cache.rb:72:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/static.rb:83:in `call' rack-cache (1.6.1) lib/rack/cache/context.rb:140:in `forward' rack-cache (1.6.1) lib/rack/cache/context.rb:249:in `fetch' rack-cache (1.6.1) lib/rack/cache/context.rb:189:in `lookup' rack-cache (1.6.1) lib/rack/cache/context.rb:66:in `call!' rack-cache (1.6.1) lib/rack/cache/context.rb:51:in `call' railties (3.2.22.2) lib/rails/engine.rb:484:in `call' railties (3.2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' **** END error log message **** The response as shown in the browser dev tools is below **** Beginning of Dev tools response body **** Action Controller: Exception caught

Routing Error

No route matches [GET] "/error/error.php"

Try running rake routes for more information on available routes.

**** End of Dev tools response body **** Also, we recently upgraded from 1.4.2 to 1.5.4 I'm trying to figure out how to debug this and find where the problem is. Does anyone have any ideas on where to start or look to locate the problem? Thank you for your help. Regards, __________________________ Brent Ellingson Manager of Web Development BYU Library 801-422-6148 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Fri Sep 15 11:17:31 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Fri, 15 Sep 2017 15:17:31 +0000 Subject: [Archivesspace_Users_Group] Migrating and maintaining item-level records in ILS and/or ASpace In-Reply-To: References: Message-ID: We also (rarely) provide MARC analytical records (single-level MARC descriptions for collection components) for items held within a collection when that collection is also represented in MARC with a collection-level record. This is done chiefly in response to a public services request for more prominent discoverability in the online catalog for selected items. Often, these items have fine-tuned subjects and authors that apply only to the component and not to the collection as a whole. Due to the rarity of the situation, my instinct is that Option 2 (in-context multi-level description of these items maintained in AS with additional single-level MARC descriptive records maintained in the ILS) is the currently workable solution. . In essence, this means there are two ?databases of record,? which is clearly problematic, but seems workable at the low levels we have for MARC records like this. (Our item-level image descriptions are another story.) However I have some follow-up questions ? and I?m hoping you are doing something brilliant So, my questions?sorry I have so many! 1) How rare is this situation for you? 2) When you write ?migration? do you mean that you will maintain all metadata in AS and not maintain data in the ILS at all? Will your ?complex methods? mean that you can maintain data in the ILS and ingest it to AS, or do you think you can get good MARC from AS? What would you do about things like alterative title tracings that are not possible in AS at all? 3) Do you agree that AS often cannot parse data finely enough to produce MARC that meets the expectations of an ILS or of OCLC or takes advantage of a discovery layer?s faceting based on MARC subfield codes? Is that OK in your institution? 4) Do you use automated authority processing in your ILS? These and other scripted updates change our MARC records without specific alerts to us (so many I would not want to get such alerts!). If AS is your database of record, won?t these updates to MARC be lost, and do you care if they are? 5) For us, the most common example of an item-level description in an alternate system is not items in our ILS, but rather digitized images that are described both in SharedShelf and in a finding aid. I am hopeful that someday I will be able to use AS as the database of record for all of our in-collection item-level image descriptions in AS only while sharing them with SharedShelf automatically send updates from AS to SharedShelf. Do you also have this situation? Thanks for focusing on this issue. It is fascinating and thorny! Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Erin Faulder Sent: Monday, September 11, 2017 2:31 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Migrating and maintaining item-level records in ILS and/or ASpace All, RMC at Cornell is in the weeds identifying bib records to migrate from our ILS into ASpace. Our practice, historically, has been to catalog collections and occasionally items within the collection in our ILS to better facilitate discovery. As we move into ASpace, we are cognizant that we should incorporate those item records within the context of the collection by including them as archival objects in ASpace under the appropriate resource record. We have three primary choices to do this, each with serious trade offs: - Leaving the item-level records in our ILS without representing them in ASpace other than a referencing note at collection/series level o We would lose contextual meaning of those items o We would maintain item-level discovery of content in OCLC/World-Cat o We would be unable to manage our location data of that material in ASpace alongside the rest of the collection - Leave the item-level records in our ILS and represent them in ASpace in their appropriate intellectual arrangement o We would have to build a way to connect the records between the two systems, designing complex methods for synchronizing descriptive metadata as well as location data between systems and setting currently minimally-enforceable rules about where the data is updated and which is the system of record o We would maintain contextual information about their collection and have item-level discovery in OCLC/World-Cat - Represent the item-level records only in ASpace and remove them from the ILS entirely o We would only have to manage the data in one system, eliminating complexity o We would lose item-level discovery of content in OCLC/World-Cat o We could manage location data the same across our content We would love to talk with anyone who has experience cataloging items in a collection at the item-level in their ILS and how they addressed the challenges presented when working with ASpace. Best, Erin -- Erin Faulder Digital Archivist Division of Rare and Manuscript Collections Cornell University Library Ithaca, NY 14853 erin.faulder at cornell.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Sep 15 11:25:32 2017 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 15 Sep 2017 15:25:32 +0000 Subject: [Archivesspace_Users_Group] Error with collection level display in admin screen In-Reply-To: <81f15818f28340629dcd07eaa8d7ad42@MB7.byu.local> References: <81f15818f28340629dcd07eaa8d7ad42@MB7.byu.local> Message-ID: Hi Brent, Did you do a full reindex when you did the upgrade? If not, give that a try. We've seen that error once before and rebuilding the index cleared it up. http://archivesspace.github.io/archivesspace/user/re-creating-indexes/ -Blake ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Brent Ellingson Sent: Friday, September 15, 2017 11:13:04 AM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) (archivesspace_users_group at lyralists.lyrasis.org) Subject: Re: [Archivesspace_Users_Group] Error with collection level display in admin screen Here is an error log entry that I?m hoping will be more relevant to the root of the problem Started GET "/resources/1540" for 0:0:0:0:0:0:0:1 at 2017-09-15 08:57:57 -0600 Processing by ResourcesController#show as HTML Parameters: {"id"=>"1540"} Rendered shared/_breadcrumb.html.erb (1.0ms) Rendered transfer/_transfer_failures.html.erb (0.0ms) Rendered shared/_tree.html.erb (3.0ms) Rendered resources/show.html.erb within layouts/application (9.0ms) Rendered shared/_browser_support.html.erb (0.0ms) Rendered shared/_header_user.html.erb (5.0ms) Rendered shared/_header_global.html.erb (6.0ms) Rendered site/_branding.html.erb (0.0ms) Rendered shared/_advanced_search.html.erb (5.0ms) Rendered shared/_header_repository.html.erb (17.0ms) Rendered site/_footer.html.erb (0.0ms) Rendered shared/_templates.html.erb (3.0ms) Completed 200 OK in 2033.0ms (Views: 42.0ms) ri"=>"root", "hash"=>"tree::resource_1540", "id"=>"1540"} :resource_1540" for 0:0:0:0:0:0:0:1 at 2017-09-15 08:58:00 -0600 Processing by ResourcesController#tree as */* Parameters: {"node_uri"=>"root", "hash"=>"tree::resource_1540", "id"=>"1540"} Completed 200 OK in 860.0ms (Views: 17.0ms) Started GET "/resources/1540?inline=true&resource_id=1540" for 0:0:0:0:0:0:0:1 at 2017-09-15 08:58:01 -0600 Processing by ResourcesController#show as */* Parameters: {"inline"=>"true", "resource_id"=>"1540", "id"=>"1540"} .... ABOUT A MINUTE LATER This shows up in the logs at the same time as the ?An error occurred loading this form. Not Found? message shows up on the browser .... _dispatch/middleware/debug_exceptions.rb:21:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.22.2) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.22.2) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.7) lib/rack/methodoverride.rb:21:in `call' rack (1.4.7) lib/rack/runtime.rb:17:in `call' activesupport (3.2.22.2) lib/active_support/cache/strategy/local_cache.rb:72:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/static.rb:83:in `call' rack-cache (1.6.1) lib/rack/cache/context.rb:140:in `forward' rack-cache (1.6.1) lib/rack/cache/context.rb:249:in `fetch' rack-cache (1.6.1) lib/rack/cache/context.rb:189:in `lookup' rack-cache (1.6.1) lib/rack/cache/context.rb:66:in `call!' rack-cache (1.6.1) lib/rack/cache/context.rb:51:in `call' railties (3.2.22.2) lib/rails/engine.rb:484:in `call' railties (3.2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4-stg/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' 2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4-stg/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' Rendered /srv/asstg/gems/gems/actionpack-3.2.22.2/lib/action_dispatch/middleware/templates/rescues/routing_error.erb within rescues/layout (1.0ms) Any thoughts? Regards, Brent Ellingson From: Brent Ellingson Sent: Thursday, September 14, 2017 3:29 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) (archivesspace_users_group at lyralists.lyrasis.org) Subject: Error with collection level display in admin screen Greeting all, We are running 1.5.4 and have 2 collections that error out when trying to access the Collection level data on the admin screen. The URL is [HOST]/resources/1540#tree::resource_1540 I?m seeing a HTML 404 error code when this URL is requested via JavaScript [HOST]/resources/1540?inline=true&resource_id=1540 In the browser below the hierarchy of the collection where the form and content usually display all I see is the following ?An error occurred loading this form. Not Found? The Series and Sub-Series links in the hierarchy seem to be working without problems. This is what I believe is the error in the logs that corresponds at least in part to the problem **** Error log message **** Started GET "/error/error.php" for 0:0:0:0:0:0:0:1 at 2017-09-14 12:44:03 -0600 ActionController::RoutingError (No route matches [GET] "/error/error.php"): actionpack (3.2.22.2) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.22.2) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.22.2) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.22.2) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.7) lib/rack/methodoverride.rb:21:in `call' rack (1.4.7) lib/rack/runtime.rb:17:in `call' activesupport (3.2.22.2) lib/active_support/cache/strategy/local_cache.rb:72:in `call' actionpack (3.2.22.2) lib/action_dispatch/middleware/static.rb:83:in `call' rack-cache (1.6.1) lib/rack/cache/context.rb:140:in `forward' rack-cache (1.6.1) lib/rack/cache/context.rb:249:in `fetch' rack-cache (1.6.1) lib/rack/cache/context.rb:189:in `lookup' rack-cache (1.6.1) lib/rack/cache/context.rb:66:in `call!' rack-cache (1.6.1) lib/rack/cache/context.rb:51:in `call' railties (3.2.22.2) lib/rails/engine.rb:484:in `call' railties (3.2.22.2) lib/rails/application.rb:231:in `call' file:/srv/archivesspace-1.5.4/archivesspace/gems/gems/jruby-rack-1.1.20/lib/jruby-rack-1.1.20.jar!/rack/handler/servlet.rb:22:in `call' **** END error log message **** The response as shown in the browser dev tools is below **** Beginning of Dev tools response body **** Action Controller: Exception caught

Routing Error

No route matches [GET] "/error/error.php"

Try running rake routes for more information on available routes.

**** End of Dev tools response body **** Also, we recently upgraded from 1.4.2 to 1.5.4 I?m trying to figure out how to debug this and find where the problem is. Does anyone have any ideas on where to start or look to locate the problem? Thank you for your help. Regards, __________________________ Brent Ellingson Manager of Web Development BYU Library 801-422-6148 From rstanonik at ucsd.edu Fri Sep 15 12:48:19 2017 From: rstanonik at ucsd.edu (Stanonik, Ronald) Date: Fri, 15 Sep 2017 16:48:19 +0000 Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop Message-ID: I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Sep 15 13:44:30 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 15 Sep 2017 17:44:30 +0000 Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop In-Reply-To: References: Message-ID: Hi Ron, This sounds like it might be particular to something with your data or installation, so I'm going to put a tech support ticket in for you on this. (You'll see another message about that directly to you in a minute.) Our tech folks will ask you for your full log to see if they can spot the cause. Sometimes when this has happened there is orphaned data that no longer meets ArchivesSpace requirements and that prevents the initial indexing from actually completing, but it's possible that something else is going on. It'd be great if when it gets resolved you would share the solution back to the lists. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 12:48 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- 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 rstanonik at ucsd.edu Fri Sep 15 13:44:44 2017 From: rstanonik at ucsd.edu (Stanonik, Ronald) Date: Fri, 15 Sep 2017 17:44:44 +0000 Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop In-Reply-To: References: Message-ID: I notice a repeating error and stacktrace in the log about an unhandled exception. E, [2017-09-15T09:45:13.168412 #10788] ERROR -- : Thread-5342: Unhandled exception! E, [2017-09-15T09:45:13.168722 #10788] ERROR -- : key not found: : org/jruby/RubyHash.java:1189:in `fetch' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:63:in `root_record' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:22:in `block in add_ancestors' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:12:in `add_ancestors' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/archival_object.rb:69:in `sequel_to_jsonmodel' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:105:in `listing_response' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in `handle_listing' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:95:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' D, [2017-09-15T09:45:13.169154 #10788] DEBUG -- : Thread-5342: Responded with [500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"29"}, ["{\"error\":\"key not found: :\"}\n"]]... in 247ms From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Fri Sep 15 15:13:16 2017 From: Kevin.Clair at du.edu (Kevin Clair) Date: Fri, 15 Sep 2017 19:13:16 +0000 Subject: [Archivesspace_Users_Group] no indexer_pui_state files in backup.sh output Message-ID: Hello, I?ve noticed with the 2.* releases that when running scripts/backup.sh, the indexer_pui_state files aren?t included in the output, only the indexer_state files. Is that an issue I should submit to JIRA or am I missing something? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Fri Sep 15 15:47:49 2017 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Fri, 15 Sep 2017 15:47:49 -0400 Subject: [Archivesspace_Users_Group] Configuring inheritances in PUI Message-ID: Hello ASpacers, I'm trying to configure the inheritances in the PUI and I've hit a roadblock. Is there anyone who has done this successfully who would be willing to chat with me about it? Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8498 ccauste1 at swarthmore.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Fri Sep 15 16:52:51 2017 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 15 Sep 2017 20:52:51 +0000 Subject: [Archivesspace_Users_Group] Classifications Message-ID: <4142170736420940ACB07EE9EECDC21F51BA6128@si-msedag04.US.SINET.SI.EDU> All - How are you using classifications at your institutions? In particular, can anyone speak to the nested 'child' classifications? I've been looking at the feature in our test installations, but am interested to see if anyone is using this out in the wild. What's the purpose of nested child classifications, given that it seems I can only attach a resource/accession/digital object to the top parent classification term? I see AR-1884 suggesting that classifications be available across multiple repositories. I can see some benefit there, though so far, most of my users have seemed to prefer the idea that classifications would be repo specific. We haven't adopted classifications yet, but if it looks like they would become global, I'd like to get more details sooner than later. Thanks! Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpeterson at smith.edu Fri Sep 15 17:13:13 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Fri, 15 Sep 2017 21:13:13 +0000 Subject: [Archivesspace_Users_Group] Classifications In-Reply-To: <4142170736420940ACB07EE9EECDC21F51BA6128@si-msedag04.US.SINET.SI.EDU> References: <4142170736420940ACB07EE9EECDC21F51BA6128@si-msedag04.US.SINET.SI.EDU> Message-ID: Hi Nancy, We're using the classifications strictly for our College Archives, which has a long-standing Record Group system in place. We're not using it for the Sophia Smith Collection or the Mortimer Rare Book Collection, both of which are set up as separate repositories within our ASpace instance. The classifications mirror the pre-existing RG system, so, for example, RG12 is "Special Events and People," and the child classification 12.01 is "Anniversaries." [image: Screen Shot 2017-09-15 at 5.10.27 PM.png] We just went into production with this, so I can't comment on how well it works yet, but it seemed like the logical thing for us to do. We do have accessions linked to both top-level and child-level classifications, so that functionality appears to work. Best, Christie Peterson On Fri, Sep 15, 2017 at 4:52 PM Kennedy, Nancy wrote: > All ? > > How are you using classifications at your institutions? In particular, > can anyone speak to the nested ?child? classifications? I?ve been looking > at the feature in our test installations, but am interested to see if > anyone is using this out in the wild. What?s the purpose of nested child > classifications, given that it seems I can only attach a > resource/accession/digital object to the top parent classification term? > > > > I see AR-1884 > suggesting that classifications be available across multiple repositories. > I can see some benefit there, though so far, most of my users have seemed > to prefer the idea that classifications would be repo specific. We haven?t > adopted classifications yet, but if it looks like they would become global, > I?d like to get more details sooner than later. > > > > > > Thanks! > > > > > > Nancy Kennedy > > Smithsonian Institution > > kennedyn at si.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- ? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-15 at 5.10.27 PM.png Type: image/png Size: 58683 bytes Desc: not available URL: From KennedyN at si.edu Fri Sep 15 17:59:29 2017 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 15 Sep 2017 21:59:29 +0000 Subject: [Archivesspace_Users_Group] Classifications In-Reply-To: References: <4142170736420940ACB07EE9EECDC21F51BA6128@si-msedag04.US.SINET.SI.EDU>, Message-ID: <4142170736420940ACB07EE9EECDC21F51BA6177@si-msedag04.US.SINET.SI.EDU> Thanks Christie. I see now .. I can add the classification parent or child from the accessions edit screen, even if I can't from the classification child screen itself. Are you all using the PUI? I wonder if it makes sense to make the classification available in the EAD. Nancy Kennedy Smithsonian Institution kennedyn at si.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Christie Peterson [cpeterson at smith.edu] Sent: Friday, September 15, 2017 5:13 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Classifications Hi Nancy, We're using the classifications strictly for our College Archives, which has a long-standing Record Group system in place. We're not using it for the Sophia Smith Collection or the Mortimer Rare Book Collection, both of which are set up as separate repositories within our ASpace instance. The classifications mirror the pre-existing RG system, so, for example, RG12 is "Special Events and People," and the child classification 12.01 is "Anniversaries." [Screen Shot 2017-09-15 at 5.10.27 PM.png] We just went into production with this, so I can't comment on how well it works yet, but it seemed like the logical thing for us to do. We do have accessions linked to both top-level and child-level classifications, so that functionality appears to work. Best, Christie Peterson On Fri, Sep 15, 2017 at 4:52 PM Kennedy, Nancy > wrote: All ? How are you using classifications at your institutions? In particular, can anyone speak to the nested ?child? classifications? I?ve been looking at the feature in our test installations, but am interested to see if anyone is using this out in the wild. What?s the purpose of nested child classifications, given that it seems I can only attach a resource/accession/digital object to the top parent classification term? I see AR-1884 suggesting that classifications be available across multiple repositories. I can see some benefit there, though so far, most of my users have seemed to prefer the idea that classifications would be repo specific. We haven?t adopted classifications yet, but if it looks like they would become global, I?d like to get more details sooner than later. Thanks! Nancy Kennedy Smithsonian Institution kennedyn at si.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- ?? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-15 at 5.10.27 PM.png Type: image/png Size: 58683 bytes Desc: Screen Shot 2017-09-15 at 5.10.27 PM.png URL: From sustasiula at pa.gov Sat Sep 16 13:55:14 2017 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Sat, 16 Sep 2017 17:55:14 +0000 Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Message-ID: <3134b6337c3a483d8af4316b4b507bbe@ENCTCEXCH008.PA.LCL> Hello, I am working in ArchivesSpace version 1.5.4. I'd like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren't linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D32EEF.C216EC60] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52962 bytes Desc: image001.png URL: From mark.custer at yale.edu Sun Sep 17 14:09:48 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Sun, 17 Sep 2017 18:09:48 +0000 Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers In-Reply-To: <3134b6337c3a483d8af4316b4b507bbe@ENCTCEXCH008.PA.LCL> References: <3134b6337c3a483d8af4316b4b507bbe@ENCTCEXCH008.PA.LCL> Message-ID: Hi, Suzanne. Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added. Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis. We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stasiulatis, Suzanne Sent: Saturday, September 16, 2017 1:55:14 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Hello, I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D32EEF.C216EC60] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52962 bytes Desc: image001.png URL: From PGalligan at rockarch.org Mon Sep 18 09:05:27 2017 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 18 Sep 2017 13:05:27 +0000 Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Message-ID: Hey Suzanne, We have automated this process for the most part. If you want to have a method to just delete all orphaned top containers, you chan check out this Python script I wrote up really quickly: https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asDeleteOrphanContainers.py Let me know if you have any questions. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Sunday, September 17, 2017 at 2:09 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers Hi, Suzanne. Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added. Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis. We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stasiulatis, Suzanne Sent: Saturday, September 16, 2017 1:55:14 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Hello, I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D3305D.44B4D5B0] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52963 bytes Desc: image001.png URL: From cpeterson at smith.edu Mon Sep 18 09:59:31 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Mon, 18 Sep 2017 13:59:31 +0000 Subject: [Archivesspace_Users_Group] Classifications In-Reply-To: <4142170736420940ACB07EE9EECDC21F51BA6177@si-msedag04.US.SINET.SI.EDU> References: <4142170736420940ACB07EE9EECDC21F51BA6128@si-msedag04.US.SINET.SI.EDU> <4142170736420940ACB07EE9EECDC21F51BA6177@si-msedag04.US.SINET.SI.EDU> Message-ID: Hi Nancy, We aren't using the PUI right now, but have plans in that direction over the next 1-2 years. I honestly don't know if the classifications appear in the EAD, but even if they did I doubt that the consortial service we use to display them would do anything interesting with it. Right now, our biggest users of it are internal staff, and for that alone it's worth it. Best, Christie On Fri, Sep 15, 2017 at 5:59 PM Kennedy, Nancy wrote: > Thanks Christie. I see now .. I can add the classification parent or > child from the accessions edit screen, even if I can't from the > classification child screen itself. > > Are you all using the PUI? I wonder if it makes sense to make the > classification available in the EAD. > > > Nancy Kennedy > Smithsonian Institution > kennedyn at si.edu > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of > Christie Peterson [cpeterson at smith.edu] > *Sent:* Friday, September 15, 2017 5:13 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Classifications > > Hi Nancy, > > We're using the classifications strictly for our College Archives, which > has a long-standing Record Group system in place. We're not using it for > the Sophia Smith Collection or the Mortimer Rare Book Collection, both of > which are set up as separate repositories within our ASpace instance. > > The classifications mirror the pre-existing RG system, so, for example, > RG12 is "Special Events and People," and the child classification 12.01 is > "Anniversaries." > > [image: Screen Shot 2017-09-15 at 5.10.27 PM.png] > We just went into production with this, so I can't comment on how well it > works yet, but it seemed like the logical thing for us to do. We do have > accessions linked to both top-level and child-level classifications, so > that functionality appears to work. > > Best, > > Christie Peterson > > On Fri, Sep 15, 2017 at 4:52 PM Kennedy, Nancy wrote: > >> All ? >> >> How are you using classifications at your institutions? In particular, >> can anyone speak to the nested ?child? classifications? I?ve been looking >> at the feature in our test installations, but am interested to see if >> anyone is using this out in the wild. What?s the purpose of nested child >> classifications, given that it seems I can only attach a >> resource/accession/digital object to the top parent classification term? >> >> >> >> I see AR-1884 >> suggesting that classifications be available across multiple repositories. >> I can see some benefit there, though so far, most of my users have seemed >> to prefer the idea that classifications would be repo specific. We haven?t >> adopted classifications yet, but if it looks like they would become global, >> I?d like to get more details sooner than later. >> >> >> >> >> >> Thanks! >> >> >> >> >> >> Nancy Kennedy >> >> Smithsonian Institution >> >> kennedyn at si.edu >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > -- > ?? > Christie S. Peterson > > Head of Technical Services for Special Collections > Smith College > Northampton, Mass. > 413-585-2996 <(413)%20585-2996> > cpeterson at smith.edu > > pronouns: she/her/hers > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- ? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-15 at 5.10.27 PM.png Type: image/png Size: 58683 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-15 at 5.10.27 PM.png Type: image/png Size: 58683 bytes Desc: not available URL: From Daniel.Thacker at tamuk.edu Mon Sep 18 10:18:11 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Mon, 18 Sep 2017 14:18:11 +0000 Subject: [Archivesspace_Users_Group] Deleting all the digital objects in a repository Message-ID: I was using a second repository to upload legacy collections into ASpace and then once the finding aid was complete I would transfer them over to our main repository. The trouble I ran into was the digital objects transferred but they stayed in the second repository. Is there anyway to do a mass deletion? There is around 11,000 digital objects and right now the only way I can delete them is one by one and 10 per page. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at minorscience.com Mon Sep 18 13:03:24 2017 From: j at minorscience.com (Jason Loeffler) Date: Mon, 18 Sep 2017 13:03:24 -0400 Subject: [Archivesspace_Users_Group] Deleting all the digital objects in a repository In-Reply-To: References: Message-ID: Hi Daniel, To my knowledge, bulk delete operations of resource components and digital objects from the staff interface is not currently supported. I'm not sure whether you can simply delete the repository, as it may orphan the digital objects it contains. Maybe someone else can confirm. If you're able to gain command line access to your instance, you can first list all of the ids in a given repository, then pipe that into a delete request. More here: https://archivesspace.github.io/archivesspace/api/#post-repo sitories-repo_id-digital_objects https://archivesspace.github.io/archivesspace/api/#delete-re positories-repo_id-digital_objects-id Lydia Tang pulled together existing JIRA tickets on this matter here: https://archivesspace.atlassian.net/browse/AR-1849 Some of us the Technical Advisory Council are interested in putting together an API cookbook for cases like yours. I'll add it to our work plan. It's also possible to do this with a plugin, though that's certainly more labor intensive. Note that you can increase the default page size by editing config.rb at "AppConfig[:default_page_size]". Best, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Mon, Sep 18, 2017 at 10:18 AM, Daniel L Thacker wrote: > I was using a second repository to upload legacy collections into ASpace > and then once the finding aid was complete I would transfer them over to > our main repository. The trouble I ran into was the digital objects > transferred but they stayed in the second repository. Is there anyway to > do a mass deletion? There is around 11,000 digital objects and right now > the only way I can delete them is one by one and 10 per page. > > > Thanks, > > > Daniel Thacker > > Digital Archivist > > James C. Jernigan Library > > Texas A&M University-Kingsville > > MSC 197 > > 700 University Blvd > > Kingsville, TX 78363-8202 > > 361-593-4154 <(361)%20593-4154> > > _______________________________________________ > 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 Daniel.Thacker at tamuk.edu Mon Sep 18 13:31:13 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Mon, 18 Sep 2017 17:31:13 +0000 Subject: [Archivesspace_Users_Group] Deleting all the digital objects in a repository In-Reply-To: References: , Message-ID: Thank you Jason, There is a plug in for digital object duplicates. I would think there might be a plug in for the current problem as well. We are re-updating some collections and I can change them quickly with a pythonscipt, where I can delete the collection and reupload it, and then delete the duplicates with the plug in. It seems like there would be a way to delete the collection along with the digital objects. Thank you again for your input. I may just delete that repository, but I will hold off until I get confirmation on the possible orphan digital objects. Sincerely, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Jason Loeffler Sent: Monday, September 18, 2017 12:03:24 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Deleting all the digital objects in a repository Hi Daniel, To my knowledge, bulk delete operations of resource components and digital objects from the staff interface is not currently supported. I'm not sure whether you can simply delete the repository, as it may orphan the digital objects it contains. Maybe someone else can confirm. If you're able to gain command line access to your instance, you can first list all of the ids in a given repository, then pipe that into a delete request. More here: https://archivesspace.github.io/archivesspace/api/#post-repositories-repo_id-digital_objects https://archivesspace.github.io/archivesspace/api/#delete-repositories-repo_id-digital_objects-id Lydia Tang pulled together existing JIRA tickets on this matter here: https://archivesspace.atlassian.net/browse/AR-1849 Some of us the Technical Advisory Council are interested in putting together an API cookbook for cases like yours. I'll add it to our work plan. It's also possible to do this with a plugin, though that's certainly more labor intensive. Note that you can increase the default page size by editing config.rb at "AppConfig[:default_page_size]". Best, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Mon, Sep 18, 2017 at 10:18 AM, Daniel L Thacker > wrote: I was using a second repository to upload legacy collections into ASpace and then once the finding aid was complete I would transfer them over to our main repository. The trouble I ran into was the digital objects transferred but they stayed in the second repository. Is there anyway to do a mass deletion? There is around 11,000 digital objects and right now the only way I can delete them is one by one and 10 per page. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 _______________________________________________ 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 mblair1 at stedwards.edu Mon Sep 18 17:04:34 2017 From: mblair1 at stedwards.edu (Megan Blair) Date: Mon, 18 Sep 2017 16:04:34 -0500 Subject: [Archivesspace_Users_Group] Top Containers Not Showing Message-ID: Hi, We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot. Any suggestions? Thanks! Megan[image: Inline image 1] -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-18 at 4.02.43 PM.png Type: image/png Size: 543297 bytes Desc: not available URL: From mark.custer at yale.edu Mon Sep 18 17:39:43 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 18 Sep 2017 21:39:43 +0000 Subject: [Archivesspace_Users_Group] Top Containers Not Showing In-Reply-To: References: Message-ID: Megan, I was just looking in the listserv archives, http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group, for this, because I swear that someone else provided a fantastic answer to a similar question a while ago. Anyhow, I can?t find it right now, so here?s my stab at answering the question: The best way to do this is *not* to type in Box in the typeahead form. Just type in something like 100. Here?s an example screen shot: [cid:image002.jpg at 01D330A5.1BF42AC0] There?s a lot of boxes in this collection, admittedly, but I think that the same basic idea should work whenever you have more than 10 boxes (since the typeahead suggestions stop at 10). Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Megan Blair Sent: Monday, 18 September, 2017 5:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Top Containers Not Showing Hi, We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot. Any suggestions? Thanks! Megan[Inline image 1] -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 24351 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 69063 bytes Desc: image006.png URL: From adrien_hilton at harvard.edu Mon Sep 18 17:40:21 2017 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Mon, 18 Sep 2017 21:40:21 +0000 Subject: [Archivesspace_Users_Group] Top Containers Not Showing In-Reply-To: References: Message-ID: Hi Megan, If you just type the number of the box ?10? rather than ?Box 10? the appropriate top container will show up in the search bar. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Megan Blair Sent: Monday, September 18, 2017 5:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Top Containers Not Showing Hi, We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot. Any suggestions? Thanks! Megan[Inline image 1] -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 69010 bytes Desc: image001.png URL: From Alston.Cobourn at tamucc.edu Mon Sep 18 18:23:39 2017 From: Alston.Cobourn at tamucc.edu (Cobourn, Alston) Date: Mon, 18 Sep 2017 22:23:39 +0000 Subject: [Archivesspace_Users_Group] Archivesspace_Users_Group Digest, Vol 50, Issue 5 In-Reply-To: References: Message-ID: Re 4- Classifications We have a Record Group classification and a Manuscript Collections classification. Therefore, we also find classifications useful for the reason Christie described, internal sorting and filter. However, in the new public interface (which I generally LOVE), it seems that classifications displays in the menu and the Resource Records notes section with the label "Record Groups". This seems odd to me, as if classifications is not mean to be broader, and clearly does not work well in our usage of Classifications. So I will be asking my IT guy to try and remove that label from the main menu and to make that note not display or to relabel it if easier for him. Just an FYI if you plan to implement PUI later. -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of archivesspace_users_group-request at lyralists.lyrasis.org Sent: Monday, September 18, 2017 4:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Archivesspace_Users_Group Digest, Vol 50, Issue 5 Send Archivesspace_Users_Group mailing list submissions to archivesspace_users_group at lyralists.lyrasis.org To subscribe or unsubscribe via the World Wide Web, visit http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group or, via email, send a message with subject or body 'help' to archivesspace_users_group-request at lyralists.lyrasis.org You can reach the person managing the list at archivesspace_users_group-owner at lyralists.lyrasis.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Archivesspace_Users_Group digest..." Today's Topics: 1. Deleting Empty Top Containers (Stasiulatis, Suzanne) 2. Re: Deleting Empty Top Containers (Custer, Mark) 3. Re: Deleting Empty Top Containers (Galligan, Patrick) 4. Re: Classifications (Christie Peterson) 5. Deleting all the digital objects in a repository (Daniel L Thacker) 6. Re: Deleting all the digital objects in a repository (Jason Loeffler) 7. Re: Deleting all the digital objects in a repository (Daniel L Thacker) 8. Top Containers Not Showing (Megan Blair) ---------------------------------------------------------------------- Message: 1 Date: Sat, 16 Sep 2017 17:55:14 +0000 From: "Stasiulatis, Suzanne" To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Message-ID: <3134b6337c3a483d8af4316b4b507bbe at ENCTCEXCH008.PA.LCL> Content-Type: text/plain; charset="us-ascii" Hello, I am working in ArchivesSpace version 1.5.4. I'd like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren't linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D32EEF.C216EC60] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52962 bytes Desc: image001.png URL: ------------------------------ Message: 2 Date: Sun, 17 Sep 2017 18:09:48 +0000 From: "Custer, Mark" To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers Message-ID: Content-Type: text/plain; charset="windows-1252" Hi, Suzanne. Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added. Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis. We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stasiulatis, Suzanne Sent: Saturday, September 16, 2017 1:55:14 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Hello, I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D32EEF.C216EC60] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52962 bytes Desc: image001.png URL: ------------------------------ Message: 3 Date: Mon, 18 Sep 2017 13:05:27 +0000 From: "Galligan, Patrick" To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers Message-ID: Content-Type: text/plain; charset="utf-8" Hey Suzanne, We have automated this process for the most part. If you want to have a method to just delete all orphaned top containers, you chan check out this Python script I wrote up really quickly: https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asDeleteOrphanContainers.py Let me know if you have any questions. From: on behalf of "Custer, Mark" Reply-To: Archivesspace Users Group Date: Sunday, September 17, 2017 at 2:09 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers Hi, Suzanne. Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added. Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis. We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stasiulatis, Suzanne Sent: Saturday, September 16, 2017 1:55:14 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Hello, I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D3305D.44B4D5B0] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52963 bytes Desc: image001.png URL: ------------------------------ Message: 4 Date: Mon, 18 Sep 2017 13:59:31 +0000 From: Christie Peterson To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Classifications Message-ID: Content-Type: text/plain; charset="utf-8" Hi Nancy, We aren't using the PUI right now, but have plans in that direction over the next 1-2 years. I honestly don't know if the classifications appear in the EAD, but even if they did I doubt that the consortial service we use to display them would do anything interesting with it. Right now, our biggest users of it are internal staff, and for that alone it's worth it. Best, Christie On Fri, Sep 15, 2017 at 5:59 PM Kennedy, Nancy wrote: > Thanks Christie. I see now .. I can add the classification parent or > child from the accessions edit screen, even if I can't from the > classification child screen itself. > > Are you all using the PUI? I wonder if it makes sense to make the > classification available in the EAD. > > > Nancy Kennedy > Smithsonian Institution > kennedyn at si.edu > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of > Christie Peterson [cpeterson at smith.edu] > *Sent:* Friday, September 15, 2017 5:13 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Classifications > > Hi Nancy, > > We're using the classifications strictly for our College Archives, > which has a long-standing Record Group system in place. We're not > using it for the Sophia Smith Collection or the Mortimer Rare Book > Collection, both of which are set up as separate repositories within our ASpace instance. > > The classifications mirror the pre-existing RG system, so, for > example, > RG12 is "Special Events and People," and the child classification > 12.01 is "Anniversaries." > > [image: Screen Shot 2017-09-15 at 5.10.27 PM.png] We just went into > production with this, so I can't comment on how well it works yet, but > it seemed like the logical thing for us to do. We do have accessions > linked to both top-level and child-level classifications, so that > functionality appears to work. > > Best, > > Christie Peterson > > On Fri, Sep 15, 2017 at 4:52 PM Kennedy, Nancy wrote: > >> All ? >> >> How are you using classifications at your institutions? In >> particular, can anyone speak to the nested ?child? classifications? >> I?ve been looking at the feature in our test installations, but am >> interested to see if anyone is using this out in the wild. What?s >> the purpose of nested child classifications, given that it seems I >> can only attach a resource/accession/digital object to the top parent classification term? >> >> >> >> I see AR-1884 >> suggesting that classifications be available across multiple repositories. >> I can see some benefit there, though so far, most of my users have >> seemed to prefer the idea that classifications would be repo >> specific. We haven?t adopted classifications yet, but if it looks >> like they would become global, I?d like to get more details sooner than later. >> >> >> >> >> >> Thanks! >> >> >> >> >> >> Nancy Kennedy >> >> Smithsonian Institution >> >> kennedyn at si.edu >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_gro >> up >> > -- > ?? > Christie S. Peterson > > Head of Technical Services for Special Collections Smith College > Northampton, Mass. > 413-585-2996 <(413)%20585-2996> > cpeterson at smith.edu > > pronouns: she/her/hers > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou > p > -- ? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-15 at 5.10.27 PM.png Type: image/png Size: 58683 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-15 at 5.10.27 PM.png Type: image/png Size: 58683 bytes Desc: not available URL: ------------------------------ Message: 5 Date: Mon, 18 Sep 2017 14:18:11 +0000 From: Daniel L Thacker To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Deleting all the digital objects in a repository Message-ID: Content-Type: text/plain; charset="iso-8859-1" I was using a second repository to upload legacy collections into ASpace and then once the finding aid was complete I would transfer them over to our main repository. The trouble I ran into was the digital objects transferred but they stayed in the second repository. Is there anyway to do a mass deletion? There is around 11,000 digital objects and right now the only way I can delete them is one by one and 10 per page. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 6 Date: Mon, 18 Sep 2017 13:03:24 -0400 From: Jason Loeffler To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Deleting all the digital objects in a repository Message-ID: Content-Type: text/plain; charset="utf-8" Hi Daniel, To my knowledge, bulk delete operations of resource components and digital objects from the staff interface is not currently supported. I'm not sure whether you can simply delete the repository, as it may orphan the digital objects it contains. Maybe someone else can confirm. If you're able to gain command line access to your instance, you can first list all of the ids in a given repository, then pipe that into a delete request. More here: https://archivesspace.github.io/archivesspace/api/#post-repo sitories-repo_id-digital_objects https://archivesspace.github.io/archivesspace/api/#delete-re positories-repo_id-digital_objects-id Lydia Tang pulled together existing JIRA tickets on this matter here: https://archivesspace.atlassian.net/browse/AR-1849 Some of us the Technical Advisory Council are interested in putting together an API cookbook for cases like yours. I'll add it to our work plan. It's also possible to do this with a plugin, though that's certainly more labor intensive. Note that you can increase the default page size by editing config.rb at "AppConfig[:default_page_size]". Best, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Mon, Sep 18, 2017 at 10:18 AM, Daniel L Thacker wrote: > I was using a second repository to upload legacy collections into > ASpace and then once the finding aid was complete I would transfer > them over to our main repository. The trouble I ran into was the digital objects > transferred but they stayed in the second repository. Is there anyway to > do a mass deletion? There is around 11,000 digital objects and right > now the only way I can delete them is one by one and 10 per page. > > > Thanks, > > > Daniel Thacker > > Digital Archivist > > James C. Jernigan Library > > Texas A&M University-Kingsville > > MSC 197 > > 700 University Blvd > > Kingsville, TX 78363-8202 > > 361-593-4154 <(361)%20593-4154> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou > p > > -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 7 Date: Mon, 18 Sep 2017 17:31:13 +0000 From: Daniel L Thacker To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Deleting all the digital objects in a repository Message-ID: Content-Type: text/plain; charset="us-ascii" Thank you Jason, There is a plug in for digital object duplicates. I would think there might be a plug in for the current problem as well. We are re-updating some collections and I can change them quickly with a pythonscipt, where I can delete the collection and reupload it, and then delete the duplicates with the plug in. It seems like there would be a way to delete the collection along with the digital objects. Thank you again for your input. I may just delete that repository, but I will hold off until I get confirmation on the possible orphan digital objects. Sincerely, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Jason Loeffler Sent: Monday, September 18, 2017 12:03:24 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Deleting all the digital objects in a repository Hi Daniel, To my knowledge, bulk delete operations of resource components and digital objects from the staff interface is not currently supported. I'm not sure whether you can simply delete the repository, as it may orphan the digital objects it contains. Maybe someone else can confirm. If you're able to gain command line access to your instance, you can first list all of the ids in a given repository, then pipe that into a delete request. More here: https://archivesspace.github.io/archivesspace/api/#post-repositories-repo_id-digital_objects https://archivesspace.github.io/archivesspace/api/#delete-repositories-repo_id-digital_objects-id Lydia Tang pulled together existing JIRA tickets on this matter here: https://archivesspace.atlassian.net/browse/AR-1849 Some of us the Technical Advisory Council are interested in putting together an API cookbook for cases like yours. I'll add it to our work plan. It's also possible to do this with a plugin, though that's certainly more labor intensive. Note that you can increase the default page size by editing config.rb at "AppConfig[:default_page_size]". Best, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Mon, Sep 18, 2017 at 10:18 AM, Daniel L Thacker > wrote: I was using a second repository to upload legacy collections into ASpace and then once the finding aid was complete I would transfer them over to our main repository. The trouble I ran into was the digital objects transferred but they stayed in the second repository. Is there anyway to do a mass deletion? There is around 11,000 digital objects and right now the only way I can delete them is one by one and 10 per page. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 _______________________________________________ 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: ------------------------------ Message: 8 Date: Mon, 18 Sep 2017 16:04:34 -0500 From: Megan Blair To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Top Containers Not Showing Message-ID: Content-Type: text/plain; charset="utf-8" Hi, We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot. Any suggestions? Thanks! Megan[image: Inline image 1] -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-18 at 4.02.43 PM.png Type: image/png Size: 543297 bytes Desc: not available URL: ------------------------------ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group End of Archivesspace_Users_Group Digest, Vol 50, Issue 5 ******************************************************** From luftsche at usc.edu Mon Sep 18 19:28:44 2017 From: luftsche at usc.edu (Susan Luftschein) Date: Mon, 18 Sep 2017 23:28:44 +0000 Subject: [Archivesspace_Users_Group] Top containers not showing up in new PUI Message-ID: Hi all, I've got a resource record with 14 top containers and only three of them are showing up in Container Inventory section of the new PUI. Does anyone have any explanation for this? All components are published but those 11 top containers give an error message when a patron clicks on a component from any of those boxes. Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From angwhite at iupui.edu Mon Sep 18 19:37:26 2017 From: angwhite at iupui.edu (White, Angela) Date: Mon, 18 Sep 2017 23:37:26 +0000 Subject: [Archivesspace_Users_Group] Top Containers Not Showing In-Reply-To: References: , Message-ID: <1505777846299.68110@iupui.edu> Adrien, I'm having the same problem as Megan, and just typing in the number doesn't work for us. We haven't upgraded as a result of this because we do so much data entry. -- Angela White, Ph.D. Philanthropic Studies Archivist IUPUI University Library 755 W. Michigan St., Room 0117C Indianapolis, IN 46202 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Hilton, Adrien Sent: Monday, September 18, 2017 5:40 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top Containers Not Showing Hi Megan, If you just type the number of the box "10" rather than "Box 10" the appropriate top container will show up in the search bar. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Megan Blair Sent: Monday, September 18, 2017 5:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Top Containers Not Showing Hi, We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot. Any suggestions? Thanks! Megan[Inline image 1] -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 69010 bytes Desc: image001.png URL: From angwhite at iupui.edu Tue Sep 19 08:03:41 2017 From: angwhite at iupui.edu (White, Angela) Date: Tue, 19 Sep 2017 12:03:41 +0000 Subject: [Archivesspace_Users_Group] Top Containers Not Showing In-Reply-To: <1505777846299.68110@iupui.edu> References: <1505777846299.68110@iupui.edu> Message-ID: <02DC3E7F-B93A-4D76-A587-0520159772AB@exchange.iu.edu> Hmmm?.it?s working now. But this was definitely something we tried, and we struggled to make anything work. In any case, this is a bug that really ought to be corrected, as we?re not the only ones flummoxed by it! Angela From: on behalf of "White, Angela" Reply-To: Archivesspace Users Group Date: Monday, September 18, 2017 at 7:37 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top Containers Not Showing Adrien, I'm having the same problem as Megan, and just typing in the number doesn't work for us. We haven't upgraded as a result of this because we do so much data entry. -- Angela White, Ph.D. Philanthropic Studies Archivist IUPUI University Library 755 W. Michigan St., Room 0117C Indianapolis, IN 46202 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Hilton, Adrien Sent: Monday, September 18, 2017 5:40 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top Containers Not Showing Hi Megan, If you just type the number of the box ?10? rather than ?Box 10? the appropriate top container will show up in the search bar. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Megan Blair Sent: Monday, September 18, 2017 5:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Top Containers Not Showing Hi, We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot. Any suggestions? Thanks! Megan[nline image 1] -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 69011 bytes Desc: image001.png URL: From sustasiula at pa.gov Tue Sep 19 08:20:41 2017 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Tue, 19 Sep 2017 12:20:41 +0000 Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers In-Reply-To: References: Message-ID: <6def224c76784507a6a1c35115ac0269@ENCTCEXCH008.PA.LCL> Thank you both! Suzanne From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Monday, September 18, 2017 9:05 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers Hey Suzanne, We have automated this process for the most part. If you want to have a method to just delete all orphaned top containers, you chan check out this Python script I wrote up really quickly: https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asDeleteOrphanContainers.py Let me know if you have any questions. From: > on behalf of "Custer, Mark" > Reply-To: Archivesspace Users Group > Date: Sunday, September 17, 2017 at 2:09 PM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers Hi, Suzanne. Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added. Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis. We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stasiulatis, Suzanne > Sent: Saturday, September 16, 2017 1:55:14 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers Hello, I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point. In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers? [cid:image001.png at 01D33120.2DF10100] Thanks! Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 52963 bytes Desc: image001.png URL: From christine.dibella at lyrasis.org Tue Sep 19 08:28:35 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 19 Sep 2017 12:28:35 +0000 Subject: [Archivesspace_Users_Group] Top containers not showing up in new PUI In-Reply-To: References: Message-ID: Der Sue, There is a bug that's been reported for the PUI that may be related to this - see https://archivesspace.atlassian.net/browse/ANW-204. If you edit one of the component records attached to the top containers that aren't showing up, as suggested in Mark Custer's comment, does it change what you see in the PUI display? (That isn't a solution for this issue - which still needs to be addressed in the code - I'm just trying to determine if what you're reporting is the same or if it's a different issue.) Thanks, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, September 18, 2017 7:29 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Top containers not showing up in new PUI Hi all, I've got a resource record with 14 top containers and only three of them are showing up in Container Inventory section of the new PUI. Does anyone have any explanation for this? All components are published but those 11 top containers give an error message when a patron clicks on a component from any of those boxes. Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From mblair1 at stedwards.edu Tue Sep 19 09:01:15 2017 From: mblair1 at stedwards.edu (Megan Blair) Date: Tue, 19 Sep 2017 08:01:15 -0500 Subject: [Archivesspace_Users_Group] Top Containers Not Showing In-Reply-To: <02DC3E7F-B93A-4D76-A587-0520159772AB@exchange.iu.edu> References: <1505777846299.68110@iupui.edu> <02DC3E7F-B93A-4D76-A587-0520159772AB@exchange.iu.edu> Message-ID: Hi all, I also tried just typing in the number last night before I emailed the group. I tried it again this morning like Angela and the boxes are now showing, but now I have multiples of box 10 so I need to go delete a couple top containers. Best, Megan On Tue, Sep 19, 2017 at 7:03 AM, White, Angela wrote: > Hmmm?.it?s working now. But this was definitely something we tried, and > we struggled to make anything work. In any case, this is a bug that really > ought to be corrected, as we?re not the only ones flummoxed by it! > > > > Angela > > > > *From: * on > behalf of "White, Angela" > *Reply-To: *Archivesspace Users Group lyralists.lyrasis.org> > *Date: *Monday, September 18, 2017 at 7:37 PM > *To: *Archivesspace Users Group lyralists.lyrasis.org> > > *Subject: *Re: [Archivesspace_Users_Group] Top Containers Not Showing > > > > Adrien, > > > > I'm having the same problem as Megan, and just typing in the number > doesn't work for us. We haven't upgraded as a result of this because we do > so much data entry. > > > > -- > > Angela White, Ph.D. > > Philanthropic Studies Archivist > > IUPUI University Library > > 755 W. Michigan St., Room 0117C > > Indianapolis, IN 46202 > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Hilton, Adrien > *Sent:* Monday, September 18, 2017 5:40 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Top Containers Not Showing > > > > Hi Megan, > > > > If you just type the number of the box ?10? rather than ?Box 10? the > appropriate top container will show up in the search bar. > > > > Best wishes, > Adrien > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Megan > Blair > *Sent:* Monday, September 18, 2017 5:05 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Top Containers Not Showing > > > > Hi, > > We had a issue start this weekend where top containers after number 9 are > no longer showing in the drop down. I have tried a couple of different > work arounds but the only way I am getting it to show up is to click browse > and then keyword search box 10 or box 11. I have attached a screenshot. > > Any suggestions? > > Thanks! > > Megan[image: nline image 1] > > > -- > > Megan M. Blair > Archivist and Public Services Librarian > Munday Library > St. Edward's University > 3001 S. Congress Ave. > Austin, TX 78704 > 512.428.1047 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 69011 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-19 at 7.57.17 AM.png Type: image/png Size: 611674 bytes Desc: not available URL: From Jeremy.Jones at unt.edu Tue Sep 19 12:20:09 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Tue, 19 Sep 2017 16:20:09 +0000 Subject: [Archivesspace_Users_Group] Failed to connect to database issue Message-ID: Hello, I've been using Archives Space since version 1.2. I've recently upgraded to version 2.1.2 using the directions included. Now I am getting a "Database connection failed" error. I'm using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at minorscience.com Tue Sep 19 12:32:52 2017 From: j at minorscience.com (Jason Loeffler) Date: Tue, 19 Sep 2017 12:32:52 -0400 Subject: [Archivesspace_Users_Group] Failed to connect to database issue In-Reply-To: References: Message-ID: Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy wrote: > Hello, > > > > I?ve been using Archives Space since version 1.2. I?ve recently upgraded > to version 2.1.2 using the directions included. Now I am getting a > ?Database connection failed? error. I?m using the same mysql connecter > that I used in my version 1.5.2 install and connecting to the same > database. The setup-database.sh script ran with no errors. Here is the > stack trace: > > > > "msg": "Database connection failed", > > "backtrace": [ > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in > `block in ArchivesSpaceService'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/ > sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in > `'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in > `
'", > > "org/jruby/RubyKernel.java:961:in `require'", > > "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/ > rubygems/core_ext/kernel_require.rb:55:in `require'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in > `block in (root)'", > > "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in > `(root)'", > > "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", > > "launcher/launcher.rb:92:in `start_server'", > > "launcher/launcher.rb:157:in `main'", > > "launcher/launcher.rb:261:in `
'" > > > > > > Any help solving this issue or any insight is appreciated. Thanks in > advance. > > > > jeremy > > > > _______________________________________________ > 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 luftsche at usc.edu Tue Sep 19 12:33:19 2017 From: luftsche at usc.edu (Susan Luftschein) Date: Tue, 19 Sep 2017 16:33:19 +0000 Subject: [Archivesspace_Users_Group] Top containers not showing up in new PUI In-Reply-To: References: Message-ID: Hi Christine, Yes, that worked! Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Tuesday, September 19, 2017 5:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top containers not showing up in new PUI Der Sue, There is a bug that's been reported for the PUI that may be related to this - see https://archivesspace.atlassian.net/browse/ANW-204. If you edit one of the component records attached to the top containers that aren't showing up, as suggested in Mark Custer's comment, does it change what you see in the PUI display? (That isn't a solution for this issue - which still needs to be addressed in the code - I'm just trying to determine if what you're reporting is the same or if it's a different issue.) Thanks, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, September 18, 2017 7:29 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Top containers not showing up in new PUI Hi all, I've got a resource record with 14 top containers and only three of them are showing up in Container Inventory section of the new PUI. Does anyone have any explanation for this? All components are published but those 11 top containers give an error message when a patron clicks on a component from any of those boxes. Thanks, Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 5342 bytes Desc: image001.jpg URL: From Jeremy.Jones at unt.edu Tue Sep 19 12:45:03 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Tue, 19 Sep 2017 16:45:03 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: Message-ID: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ 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 j at minorscience.com Tue Sep 19 13:43:52 2017 From: j at minorscience.com (Jason Loeffler) Date: Tue, 19 Sep 2017 13:43:52 -0400 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: Message-ID: The db connection error is thrown in only one place, in main.rb at lines 96-102 . It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy wrote: > Sure, > > > > The server is centOS 6.9. > > Mysql version 14.14 Distrib 5.1.73 > > Yes I can connect to the database directly using the username and > password. It?s the same combo that I?ve used since AS version 1.2. > > > > This is very strange that this is happening. I?ve never had any problems > including the great migration to get to version 1.5.2. > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jason > Loeffler > *Sent:* Tuesday, September 19, 2017 11:33 AM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* [EXT] Re: [Archivesspace_Users_Group] Failed to connect to > database issue > > > > Hi Jeremy, > > > > Can you include more information about your environment, e.g. server OS > and database server version? Can you connect to the database directly using > your ArchivesSpace username and password as stored in config.rb? > > > Jason Loeffler > > Technology Consultant | The American Academy in Rome > > Minor Science | Application Development & Metadata Strategy > > Brooklyn, New York > > jason at minorscience.com > > (347) 405-0826 > > minorscience (Skype) > > > > > > On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: > > Hello, > > > > I?ve been using Archives Space since version 1.2. I?ve recently upgraded > to version 2.1.2 using the directions included. Now I am getting a > ?Database connection failed? error. I?m using the same mysql connecter > that I used in my version 1.5.2 install and connecting to the same > database. The setup-database.sh script ran with no errors. Here is the > stack trace: > > > > "msg": "Database connection failed", > > "backtrace": [ > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in > `block in ArchivesSpaceService'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/ > sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in > `'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in > `
'", > > "org/jruby/RubyKernel.java:961:in `require'", > > "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/ > rubygems/core_ext/kernel_require.rb:55:in `require'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in > `block in (root)'", > > "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in > `(root)'", > > "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", > > "launcher/launcher.rb:92:in `start_server'", > > "launcher/launcher.rb:157:in `main'", > > "launcher/launcher.rb:261:in `
'" > > > > > > Any help solving this issue or any insight is appreciated. Thanks in > advance. > > > > jeremy > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmg17 at psu.edu Tue Sep 19 14:16:00 2017 From: bmg17 at psu.edu (Ben Goldman) Date: Tue, 19 Sep 2017 14:16:00 -0400 (EDT) Subject: [Archivesspace_Users_Group] exporting labels Message-ID: <87173006.1156631.1505844960867.JavaMail.zimbra@psu.edu> Hello everyone, I'm familiar with the Dartmouth label plugin, but am wondering if the built in label export function can be modified at all? It has everything we need, with the exception of the location string. Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Tue Sep 19 14:20:51 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Tue, 19 Sep 2017 18:20:51 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: Message-ID: Thanks looking into this. I tried going back to version 1.52 and got the same error. What is jruby and do I need to have it installed on the server? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 12:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue The db connection error is thrown in only one place, in main.rb at lines 96-102. It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From clobdel1 at swarthmore.edu Tue Sep 19 14:25:04 2017 From: clobdel1 at swarthmore.edu (Chelsea Lobdell) Date: Tue, 19 Sep 2017 14:25:04 -0400 Subject: [Archivesspace_Users_Group] DB Migration Question Message-ID: Hi Aspace! I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on our development server. After running setup-database.sh to migrate the data I noticed an odd table in the database called rights_statement_pre_088. The application starts up and runs fine but recently a staff member was editing labels in en.yml and config.rb for the new PUI and had to force a re-index. After the re-index, Archivesspace was complaining that rights_statement_pre_088 was not set to use UTF8 for its character encoding. I was able to resolve the issue by dropping and then re-creating our dev DB from our live DB but I am curious about rights_statement_pre_088. The table still exists though no errors are currently being thrown. Has anyone else encountered this or have any advice? Thanks, Chelsea *---------------* *Chelsea Lobdell* *Library Web Developer/ Swarthmore College* *clobdel1 at swarthmore.edu / (610)690-6818* -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Sep 19 14:39:16 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 19 Sep 2017 18:39:16 +0000 Subject: [Archivesspace_Users_Group] DB Migration Question In-Reply-To: References: Message-ID: Hi Chelsea, Version 2.1 of ArchivesSpace included an expanded rights statements module and setup-database has a data migration to move previous rights data to the new model (migration 088). The purpose of the rights_statement_pre_088 table is to serve as a backup of your previous rights statement data in case you find that your rights data did not migrate as expected. It is not needed if you?re happy with the way the data migrated. As to why ArchivesSpace would throw an error saying it was not set to UTF8, I would be curious if anyone else has experienced that during or post-upgrade. We have not heard of that occurring previously. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, September 19, 2017 2:25 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] DB Migration Question Hi Aspace! I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on our development server. After running setup-database.sh to migrate the data I noticed an odd table in the database called rights_statement_pre_088. The application starts up and runs fine but recently a staff member was editing labels in en.yml and config.rb for the new PUI and had to force a re-index. After the re-index, Archivesspace was complaining that rights_statement_pre_088 was not set to use UTF8 for its character encoding. I was able to resolve the issue by dropping and then re-creating our dev DB from our live DB but I am curious about rights_statement_pre_088. The table still exists though no errors are currently being thrown. Has anyone else encountered this or have any advice? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From kayiwa at princeton.edu Tue Sep 19 14:42:54 2017 From: kayiwa at princeton.edu (Francis Kayiwa) Date: Tue, 19 Sep 2017 14:42:54 -0400 Subject: [Archivesspace_Users_Group] DB Migration Question In-Reply-To: References: Message-ID: Hello, On 9/19/17 2:25 PM, Chelsea Lobdell wrote: > Hi Aspace! > > I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on > our development server. > > After running setup-database.sh to migrate the data I noticed an odd > table in the database called rights_statement_pre_088. > > The application starts up and runs fine but recently a staff member was > editing labels in en.yml and config.rb for the new PUI and had to force > a re-index. After the re-index, Archivesspace was complaining that > rights_statement_pre_088 was not set to use UTF8 for its character > encoding. > > I was able to resolve the issue by dropping and then re-creating our dev > DB from our live DB but I am curious about rights_statement_pre_088. The > table still exists though no errors are currently being thrown. > > Has anyone else encountered this or have any advice? I would make sure when you create the new DB you have the entire DB is set to utf8 (which I speculate isn't the case or at least certainly was in my case) on the command line that'd be create database yourv212newdatabase default character set utf8; Then import the v2.0.1 db into the db above and run the setup-database.sh script which should honor that. On completion it will be gone. Cheers, ./fxk -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From lwoodford at jhu.edu Tue Sep 19 14:44:03 2017 From: lwoodford at jhu.edu (Lora Woodford) Date: Tue, 19 Sep 2017 18:44:03 +0000 Subject: [Archivesspace_Users_Group] DB Migration Question In-Reply-To: References: Message-ID: Heya, Christine/all, We haven?t upgraded yet, but I have a few 2.1.2 local test instances running with our production data in them to do some testing/api script rewrites in advance of upgrading. I can confirm that I have seen this non-utf8 error message multiple times (but have ignored it since it didn?t impede my testing and aspace still booted up fine). But, yes, I?ve seen this warning. Lora From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Tuesday, September 19, 2017 2:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] DB Migration Question Hi Chelsea, Version 2.1 of ArchivesSpace included an expanded rights statements module and setup-database has a data migration to move previous rights data to the new model (migration 088). The purpose of the rights_statement_pre_088 table is to serve as a backup of your previous rights statement data in case you find that your rights data did not migrate as expected. It is not needed if you?re happy with the way the data migrated. As to why ArchivesSpace would throw an error saying it was not set to UTF8, I would be curious if anyone else has experienced that during or post-upgrade. We have not heard of that occurring previously. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, September 19, 2017 2:25 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] DB Migration Question Hi Aspace! I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on our development server. After running setup-database.sh to migrate the data I noticed an odd table in the database called rights_statement_pre_088. The application starts up and runs fine but recently a staff member was editing labels in en.yml and config.rb for the new PUI and had to force a re-index. After the re-index, Archivesspace was complaining that rights_statement_pre_088 was not set to use UTF8 for its character encoding. I was able to resolve the issue by dropping and then re-creating our dev DB from our live DB but I am curious about rights_statement_pre_088. The table still exists though no errors are currently being thrown. Has anyone else encountered this or have any advice? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4009 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Tue Sep 19 14:51:27 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 19 Sep 2017 18:51:27 +0000 Subject: [Archivesspace_Users_Group] Configuring inheritances in PUI In-Reply-To: References: Message-ID: Hi Celia, Jumping back to this from last week, I was curious if you?d be able to work through this with anyone yet. What are the specific roadblocks you?re encountering? Mark Custer put some explanation and a short video together about this feature in its planning stages (see https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-ArchivalInheritance), but we don?t yet have step-by-step instructions or a demonstration of how to change the settings in the config file. Laney and I were talking through inheritance with Blake and Mark from LYRASIS DTS today based on some other questions that have come in. They?re going to be testing out a few scenarios to see what is/isn?t possible and then I?m hoping to have some more detailed documentation to share soon. But if you?ve already gotten there, or if you?ve found certain things to work and others not, I?m sure the list would benefit from those observations. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Celia Caust-Ellenbogen Sent: Friday, September 15, 2017 3:48 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Configuring inheritances in PUI Hello ASpacers, I'm trying to configure the inheritances in the PUI and I've hit a roadblock. Is there anyone who has done this successfully who would be willing to chat with me about it? Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8498 ccauste1 at swarthmore.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From clobdel1 at swarthmore.edu Tue Sep 19 15:14:36 2017 From: clobdel1 at swarthmore.edu (Chelsea Lobdell) Date: Tue, 19 Sep 2017 15:14:36 -0400 Subject: [Archivesspace_Users_Group] DB Migration Question In-Reply-To: References: Message-ID: Hi All, Just to clarify, after I encountered the error I did: DROP DATABASE 2.1.2_dev CREATE DATABASE 2.1.2_dev default character set utf8; $ mysqldump 2.0.1_live > 2.0.1_live.sql $ mysql 2.1.2_dev < 2.0.1_live.sql $ cd archivesspace-2.1.2\archivesspace $ scripts\setup-database.sh rights_statement_pre_088 still exists. - Chelsea *---------------* *Chelsea Lobdell* *Library Web Developer/ Swarthmore College* *clobdel1 at swarthmore.edu / (610)690-6818* On Tue, Sep 19, 2017 at 2:44 PM, Lora Woodford wrote: > Heya, Christine/all, > > > > We haven?t upgraded yet, but I have a few 2.1.2 local test instances > running with our production data in them to do some testing/api script > rewrites in advance of upgrading. I can confirm that I have seen this > non-utf8 error message multiple times (but have ignored it since it didn?t > impede my testing and aspace still booted up fine). > > > > But, yes, I?ve seen this warning. > > > > Lora > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Christine > Di Bella > *Sent:* Tuesday, September 19, 2017 2:39 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] DB Migration Question > > > > Hi Chelsea, > > > > Version 2.1 of ArchivesSpace included an expanded rights statements module > and setup-database has a data migration to move previous rights data to the > new model (migration 088). The purpose of the rights_statement_pre_088 > table is to serve as a backup of your previous rights statement data in > case you find that your rights data did not migrate as expected. It is not > needed if you?re happy with the way the data migrated. > > > > As to why ArchivesSpace would throw an error saying it was not set to > UTF8, I would be curious if anyone else has experienced that during or > post-upgrade. We have not heard of that occurring previously. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Chelsea > Lobdell > *Sent:* Tuesday, September 19, 2017 2:25 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] DB Migration Question > > > > Hi Aspace! > > I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on our > development server. > > After running setup-database.sh to migrate the data I noticed an odd table > in the database called rights_statement_pre_088. > > The application starts up and runs fine but recently a staff member was > editing labels in en.yml and config.rb for the new PUI and had to force a > re-index. After the re-index, Archivesspace was complaining that > rights_statement_pre_088 was not set to use UTF8 for its character > encoding. > > I was able to resolve the issue by dropping and then re-creating our dev > DB from our live DB but I am curious about rights_statement_pre_088. The > table still exists though no errors are currently being thrown. > > Has anyone else encountered this or have any advice? > > Thanks, > > Chelsea > > *---------------* > *Chelsea Lobdell* > *Library Web Developer/ Swarthmore College* > *clobdel1 at swarthmore.edu / (610)690-6818 > <(610)%20690-6818>* > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4009 bytes Desc: not available URL: From j at minorscience.com Tue Sep 19 15:22:04 2017 From: j at minorscience.com (Jason Loeffler) Date: Tue, 19 Sep 2017 15:22:04 -0400 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: Message-ID: JRuby is a Java application that reads and runs the Ruby source code. You don't need to install anything. If rolling back results in the same connectivity issue, I suspect it is not an ArchivesSpace-specific problem and is arising from something lower in your stack, likely an issue with your database server. Re-confirm that your config.rb has the correct credentials and that you also have the MYSQL connector installed at in your lib directory. On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy wrote: > Thanks looking into this. I tried going back to version 1.52 and got the > same error. What is jruby and do I need to have it installed on the server? > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jason > Loeffler > *Sent:* Tuesday, September 19, 2017 12:44 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to > database issue > > > > The db connection error is thrown in only one place, in main.rb at lines > 96-102 > . > It's hard to say what may be impeding the connection. I can't think of any > reason the application can't connect, aside from a network issue. Feel free > to contact me offlist if you're unable to resolve the issue. > > > > On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: > > Sure, > > > > The server is centOS 6.9. > > Mysql version 14.14 Distrib 5.1.73 > > Yes I can connect to the database directly using the username and > password. It?s the same combo that I?ve used since AS version 1.2. > > > > This is very strange that this is happening. I?ve never had any problems > including the great migration to get to version 1.5.2. > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jason > Loeffler > *Sent:* Tuesday, September 19, 2017 11:33 AM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* [EXT] Re: [Archivesspace_Users_Group] Failed to connect to > database issue > > > > Hi Jeremy, > > > > Can you include more information about your environment, e.g. server OS > and database server version? Can you connect to the database directly using > your ArchivesSpace username and password as stored in config.rb? > > > Jason Loeffler > > Technology Consultant | The American Academy in Rome > > Minor Science | Application Development & Metadata Strategy > > Brooklyn, New York > > jason at minorscience.com > > (347) 405-0826 > > minorscience (Skype) > > > > > > On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: > > Hello, > > > > I?ve been using Archives Space since version 1.2. I?ve recently upgraded > to version 2.1.2 using the directions included. Now I am getting a > ?Database connection failed? error. I?m using the same mysql connecter > that I used in my version 1.5.2 install and connecting to the same > database. The setup-database.sh script ran with no errors. Here is the > stack trace: > > > > "msg": "Database connection failed", > > "backtrace": [ > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in > `block in ArchivesSpaceService'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/ > sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in > `'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in > `
'", > > "org/jruby/RubyKernel.java:961:in `require'", > > "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/ > rubygems/core_ext/kernel_require.rb:55:in `require'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in > `block in (root)'", > > "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/ > jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in > `(root)'", > > "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", > > "launcher/launcher.rb:92:in `start_server'", > > "launcher/launcher.rb:157:in `main'", > > "launcher/launcher.rb:261:in `
'" > > > > > > Any help solving this issue or any insight is appreciated. Thanks in > advance. > > > > jeremy > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laney.mcglohon at lyrasis.org Tue Sep 19 15:38:02 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Tue, 19 Sep 2017 19:38:02 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: Message-ID: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> Hey Jeremy, What version of the mysql connector are you using? I have been using mysql-connector-java-5.1.42-bin.jar. Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: on behalf of Jason Loeffler Reply-To: Archivesspace Users Group Date: Tuesday, September 19, 2017 at 3:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue JRuby is a Java application that reads and runs the Ruby source code. You don't need to install anything. If rolling back results in the same connectivity issue, I suspect it is not an ArchivesSpace-specific problem and is arising from something lower in your stack, likely an issue with your database server. Re-confirm that your config.rb has the correct credentials and that you also have the MYSQL connector installed at in your lib directory. On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy > wrote: Thanks looking into this. I tried going back to version 1.52 and got the same error. What is jruby and do I need to have it installed on the server? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue The db connection error is thrown in only one place, in main.rb at lines 96-102. It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Tue Sep 19 15:40:38 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Tue, 19 Sep 2017 19:40:38 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> References: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> Message-ID: I used 5.1.34 until today then I upgraded to 6.0.6. No luck. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Tuesday, September 19, 2017 2:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hey Jeremy, What version of the mysql connector are you using? I have been using mysql-connector-java-5.1.42-bin.jar. Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: > on behalf of Jason Loeffler > Reply-To: Archivesspace Users Group > Date: Tuesday, September 19, 2017 at 3:22 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue JRuby is a Java application that reads and runs the Ruby source code. You don't need to install anything. If rolling back results in the same connectivity issue, I suspect it is not an ArchivesSpace-specific problem and is arising from something lower in your stack, likely an issue with your database server. Re-confirm that your config.rb has the correct credentials and that you also have the MYSQL connector installed at in your lib directory. On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy > wrote: Thanks looking into this. I tried going back to version 1.52 and got the same error. What is jruby and do I need to have it installed on the server? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue The db connection error is thrown in only one place, in main.rb at lines 96-102. It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Tue Sep 19 15:57:37 2017 From: noah.huffman at duke.edu (Noah Huffman) Date: Tue, 19 Sep 2017 19:57:37 +0000 Subject: [Archivesspace_Users_Group] DB Migration Question In-Reply-To: References: Message-ID: Just chiming in to say that I?ve seen this uft8 error as well related to the rights_statement_pre_088 table. The error was preventing ASpace from starting up. To fix it, I just used MySQL Workbench to change that table?s collation to ?utf-8 ? default collation? Once I made that change, ASpace started up properly. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, September 19, 2017 3:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] DB Migration Question Hi All, Just to clarify, after I encountered the error I did: DROP DATABASE 2.1.2_dev CREATE DATABASE 2.1.2_dev default character set utf8; $ mysqldump 2.0.1_live > 2.0.1_live.sql $ mysql 2.1.2_dev < 2.0.1_live.sql $ cd archivesspace-2.1.2\archivesspace $ scripts\setup-database.sh rights_statement_pre_088 still exists. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Sep 19, 2017 at 2:44 PM, Lora Woodford > wrote: Heya, Christine/all, We haven?t upgraded yet, but I have a few 2.1.2 local test instances running with our production data in them to do some testing/api script rewrites in advance of upgrading. I can confirm that I have seen this non-utf8 error message multiple times (but have ignored it since it didn?t impede my testing and aspace still booted up fine). But, yes, I?ve seen this warning. Lora From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Tuesday, September 19, 2017 2:39 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] DB Migration Question Hi Chelsea, Version 2.1 of ArchivesSpace included an expanded rights statements module and setup-database has a data migration to move previous rights data to the new model (migration 088). The purpose of the rights_statement_pre_088 table is to serve as a backup of your previous rights statement data in case you find that your rights data did not migrate as expected. It is not needed if you?re happy with the way the data migrated. As to why ArchivesSpace would throw an error saying it was not set to UTF8, I would be curious if anyone else has experienced that during or post-upgrade. We have not heard of that occurring previously. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, September 19, 2017 2:25 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] DB Migration Question Hi Aspace! I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on our development server. After running setup-database.sh to migrate the data I noticed an odd table in the database called rights_statement_pre_088. The application starts up and runs fine but recently a staff member was editing labels in en.yml and config.rb for the new PUI and had to force a re-index. After the re-index, Archivesspace was complaining that rights_statement_pre_088 was not set to use UTF8 for its character encoding. I was able to resolve the issue by dropping and then re-creating our dev DB from our live DB but I am curious about rights_statement_pre_088. The table still exists though no errors are currently being thrown. Has anyone else encountered this or have any advice? Thanks, Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4009 bytes Desc: image001.jpg URL: From laney.mcglohon at lyrasis.org Tue Sep 19 16:30:43 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Tue, 19 Sep 2017 20:30:43 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> Message-ID: <97D928B6-DA9C-473C-8F67-25401A47C504@lyrasis.org> Hey Jeremy, I had the same problem on my server. To fix it I had to fix the permissions of my AS user to the database. I had granted permissions for localhost but the mysql server was on a different machine so I had to grant permissions for that machine. Could your mysql database be on a different machine? Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: on behalf of "Jones, Jeremy" Reply-To: Archivesspace Users Group Date: Tuesday, September 19, 2017 at 3:40 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue I used 5.1.34 until today then I upgraded to 6.0.6. No luck. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Tuesday, September 19, 2017 2:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hey Jeremy, What version of the mysql connector are you using? I have been using mysql-connector-java-5.1.42-bin.jar. Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: > on behalf of Jason Loeffler > Reply-To: Archivesspace Users Group > Date: Tuesday, September 19, 2017 at 3:22 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue JRuby is a Java application that reads and runs the Ruby source code. You don't need to install anything. If rolling back results in the same connectivity issue, I suspect it is not an ArchivesSpace-specific problem and is arising from something lower in your stack, likely an issue with your database server. Re-confirm that your config.rb has the correct credentials and that you also have the MYSQL connector installed at in your lib directory. On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy > wrote: Thanks looking into this. I tried going back to version 1.52 and got the same error. What is jruby and do I need to have it installed on the server? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue The db connection error is thrown in only one place, in main.rb at lines 96-102. It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Tue Sep 19 16:46:39 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Tue, 19 Sep 2017 20:46:39 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: <97D928B6-DA9C-473C-8F67-25401A47C504@lyrasis.org> References: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> <97D928B6-DA9C-473C-8F67-25401A47C504@lyrasis.org> Message-ID: Hello, Thanks for the update and suggestion. No, my database is on the same machine. It?s the same user and permissions that it?s always been. I commented out the bd_url declaration in the config.rb file and actually got the thing to start so I?m thinking it has something to do with the app talking to the database. I?ve got ssl on this machine with a force rewrite. I didn?t think that would cause any issues but I?m running out of ideas on this. It?s been a day and a half. Last update took less than 5 minutes. Lol. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Tuesday, September 19, 2017 3:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hey Jeremy, I had the same problem on my server. To fix it I had to fix the permissions of my AS user to the database. I had granted permissions for localhost but the mysql server was on a different machine so I had to grant permissions for that machine. Could your mysql database be on a different machine? Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: > on behalf of "Jones, Jeremy" > Reply-To: Archivesspace Users Group > Date: Tuesday, September 19, 2017 at 3:40 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue I used 5.1.34 until today then I upgraded to 6.0.6. No luck. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Tuesday, September 19, 2017 2:38 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hey Jeremy, What version of the mysql connector are you using? I have been using mysql-connector-java-5.1.42-bin.jar. Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: > on behalf of Jason Loeffler > Reply-To: Archivesspace Users Group > Date: Tuesday, September 19, 2017 at 3:22 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue JRuby is a Java application that reads and runs the Ruby source code. You don't need to install anything. If rolling back results in the same connectivity issue, I suspect it is not an ArchivesSpace-specific problem and is arising from something lower in your stack, likely an issue with your database server. Re-confirm that your config.rb has the correct credentials and that you also have the MYSQL connector installed at in your lib directory. On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy > wrote: Thanks looking into this. I tried going back to version 1.52 and got the same error. What is jruby and do I need to have it installed on the server? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue The db connection error is thrown in only one place, in main.rb at lines 96-102. It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Wed Sep 20 08:19:33 2017 From: KennedyN at si.edu (Kennedy, Nancy) Date: Wed, 20 Sep 2017 12:19:33 +0000 Subject: [Archivesspace_Users_Group] LCNAF import -- authority ID Message-ID: <4142170736420940ACB07EE9EECDC21F51BA6CA7@si-msedag04.US.SINET.SI.EDU> Morning, In version 2.1.1 and 2.1.2, it appears that the LCNAF import plugin no longer populates the Authority ID field. I'm fairly sure that this is a recent change and that we used to get the authority ID. Is this related to https://archivesspace.atlassian.net/browse/AR-1728? : "... Ultimately, the MARC 001 field (control number for the bib record) should not be mapped to the agent authority_id. Removing this line from the importer code should solve the problem..." Thanks, Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From HurtT at easternct.edu Wed Sep 20 09:42:30 2017 From: HurtT at easternct.edu (Hurt, Tara (Library)) Date: Wed, 20 Sep 2017 13:42:30 +0000 Subject: [Archivesspace_Users_Group] Export PDF and EAD Message-ID: Good morning everyone. Thank you for all the advice on our migration from 1.4.2 ...... we are running 2.1.2 now. Anyone who is using 2.1.2, are you having trouble generating PDF and EAD in the Export function? We are having trouble .... It looks like the output is all garbled and not consistent in any collection. Is this a known problem and the fix is in the works now? Tara L. Hurt -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Wed Sep 20 10:39:17 2017 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Wed, 20 Sep 2017 10:39:17 -0400 Subject: [Archivesspace_Users_Group] Export PDF and EAD In-Reply-To: References: Message-ID: Tara, Do you have an example of the bad EAD output? Thanks, --Alex On Wed, Sep 20, 2017 at 9:42 AM, Hurt, Tara (Library) wrote: > Good morning everyone. > > > > Thank you for all the advice on our migration from 1.4.2 ?? we are running > 2.1.2 now. > > > > Anyone who is using 2.1.2, are you having trouble generating PDF and EAD > in the Export function? > > > > We are having trouble ?. It looks like the output is all garbled and not > consistent in any collection. > > > > Is this a known problem and the fix is in the works now? > > > > Tara L. Hurt > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Sep 20 12:06:11 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 20 Sep 2017 16:06:11 +0000 Subject: [Archivesspace_Users_Group] new position at LYRASIS to support ArchivesSpace technical activities - DevOps Specialist Message-ID: Hello members, LYRASIS, the organizational home for ArchivesSpace, recently approved an additional staff position based in Technology Services to support ArchivesSpace technical needs. The position description is attached and can also be found at https://www.lyrasis.org/job/Pages/LYRASIS-Positions.aspx. While the position will report to the Director of Technology Services, the person in the position will work closely with the ArchivesSpace program team to provide technical support for ArchivesSpace members as well as coding and other technical assistance for the application. Over time the person will have additional responsibilities for supporting LYRASIS hosting clients. This position is ideal for someone who is familiar with ArchivesSpace or other archival/collection management systems and likes to help people with their technical questions. Previous experience with multiple platforms (Linux, Mac, Windows), MySQL, Java, Ruby, and Apache Solr is required. We are excited about this additional support within the organizational home for ArchivesSpace technical needs. If you are interested in applying, or know someone who is, applications, including a cover letter and resume, are being accepted via email at human.resources at lyrasis.org. If you have questions about the position, feel free to reach out to me or Laney. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: LYRASIS-DevOps.pdf Type: application/pdf Size: 404925 bytes Desc: LYRASIS-DevOps.pdf URL: From Jeremy.Jones at unt.edu Wed Sep 20 17:53:51 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Wed, 20 Sep 2017 21:53:51 +0000 Subject: [Archivesspace_Users_Group] can't view collections on the backend Message-ID: Hello, I'm having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Wed Sep 20 17:59:09 2017 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Wed, 20 Sep 2017 17:59:09 -0400 Subject: [Archivesspace_Users_Group] can't view collections on the backend In-Reply-To: References: Message-ID: Jeremy, Can you share the http requests you made to generate the error? Don On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy wrote: > Hello, > > > I?m having a few issues with Archivesspace. First, I cannot view the > contents of a collection on the backend view (:8089). I can view them on > the front end and edit them. But the backend view says (*We're sorry, > but something went wrong.* > > If you are the application owner check the logs for more information. > > > > The logs say: > > > > > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server > Error in 507ms > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error > (undefined method `[]' for nil:NilClass): > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && > @result.respond_to?(:metadata) %> > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in > `metadata' > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in > `_app_views_shared__metadata_html_erb__1424742346_2312' > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in > `_app_views_layouts_application_html_erb___1292011715_2310' > > > > I cannot make much from this log entry other than there was a fatal > error. Any ideas what could be causing this? > > > > Thank you > > jeremy > > _______________________________________________ > 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 Jeremy.Jones at unt.edu Wed Sep 20 18:10:29 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Wed, 20 Sep 2017 22:10:29 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend In-Reply-To: References: Message-ID: Sure, I think this is what the log captured: Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={q=(id:("\/repositories\/3\/resources\/243\/tree\/root"))&csv.escape=\&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_default:true&fq=publish:true&rows=1&wt=json&facet=true} hits=0 status=0 QTime=1 Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: http://localhost:8089/search?publish=true&page_size=10&q=collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%28types%3Apui+AND+types%3Apui_container%29&page=1 I simply clicked collections and then clicked on the first one. Repositories/3/resource/243. I hope this helps. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Wednesday, September 20, 2017 4:59 PM To: Archivesspace Users Group Subject: [EXT] Re: [Archivesspace_Users_Group] can't view collections on the backend Jeremy, Can you share the http requests you made to generate the error? Don On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy > wrote: Hello, I?m having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy _______________________________________________ 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 j at minorscience.com Wed Sep 20 18:08:28 2017 From: j at minorscience.com (Jason Loeffler) Date: Wed, 20 Sep 2017 22:08:28 +0000 Subject: [Archivesspace_Users_Group] can't view collections on the backend In-Reply-To: References: Message-ID: Can you post the request you're using to hit the endpoint? _____________________________ From: Jones, Jeremy > Sent: Wednesday, September 20, 2017 17:53 Subject: [Archivesspace_Users_Group] can't view collections on the backend To: > Hello, I?m having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From gsk5 at cornell.edu Thu Sep 21 11:06:59 2017 From: gsk5 at cornell.edu (George Stanley Kozak) Date: Thu, 21 Sep 2017 15:06:59 +0000 Subject: [Archivesspace_Users_Group] Top container record corrupted Message-ID: Hi, Everyone: Recently, one of our Archivists created a top container record attached to an archival object in ASpace. She then changed the access restriction on the archival object but deleted a sub-note field it expected to have. This gave her the following error: "Sub Notes - translation missing: en.validation_errors.must_contain_at_least_one_subnote". We believe that this corrupted the top container record. When she tried to create a new top container record attached to the same archival object, it was created, but when trying to view the container the "We're sorry, something went wrong" error occurred. I tried to go through the logs to find what exactly happened, but I am having trouble pinpointing where the error occurred in the logs. Has anyone else experienced something similar or has any hints to give us as to what we can do to fix this problem? Thanks! George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -------------- next part -------------- An HTML attachment was scrubbed... URL: From clobdel1 at swarthmore.edu Thu Sep 21 13:04:40 2017 From: clobdel1 at swarthmore.edu (Chelsea Lobdell) Date: Thu, 21 Sep 2017 13:04:40 -0400 Subject: [Archivesspace_Users_Group] Advice on Custom Theming Message-ID: Hi Archivesspace, I'm looking for some advice on how to get started with custom theming. I've been reviewing this custom theming documentation: https://github.com/archivesspace/archivesspace/blob/master/CUSTOMIZING_THEMING.md The initial change I'm trying to make is really simple. In layouts/application.html.erb I just need to change the header, navigation and maincontent from container-fluid to container to match the style of the other applications in our application suite. My first attempt was to add archivesspace/plugins/local/frontend/views/layouts/application.html.erb and to make the appropriate changes. However, after a restart I am not seeing my changes. Can anyone advise me on how to get this working? I also recognize that application.html.erb is a pretty important file to be customizing. If anybody has advice on how best to approach this, I would appreciate it. - Chelsea *---------------* *Chelsea Lobdell* *Library Web Developer/ Swarthmore College* *clobdel1 at swarthmore.edu / (610)690-6818* -------------- next part -------------- An HTML attachment was scrubbed... URL: From maderikra at vmi.edu Thu Sep 21 13:48:37 2017 From: maderikra at vmi.edu (Maderik, Rachel A) Date: Thu, 21 Sep 2017 17:48:37 +0000 Subject: [Archivesspace_Users_Group] classifications dropping links to records after being edited Message-ID: <5081f27ed0624886ae002f4d683d6a00@vmi.edu> We just discovered that if you make an edit to a child classification in 2.1.2 (e.g., changing the title or description), ALL linked records are dropped from that classification. I was able to replicate this on the sandbox: I added this classification http://sandbox.archivesspace.org/classifications/101/edit#tree::classification_term_1 to this record http://sandbox.archivesspace.org/resources/1316#tree::resource_1316, as you can see in "resource_before.JPG" and "classification_before.JPG". Then I made a change to the description of the classification, and after saving it, that record is no longer linked ("resource_after.JPG" and "classification_after.JPG"). I checked the classification_rlshp table in our own sandbox, and it appears the relevant entries don't even exist in there anymore (table_before.JPG and table_after.JPG, showing what happened after I made a change to classification_term_id 43), so it appears to be more than just an indexing issue (the actual relationship between the records has been lost). As far as I can tell this doesn't affect top-level classifications, only children. Has anyone else come across this? Rachel Maderik Systems and Technology Librarian 501D Preston Library Virginia Military Institute Lexington, VA 24450 540-464-7572 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: resource_before.JPG Type: image/jpeg Size: 148151 bytes Desc: resource_before.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: classification_before.JPG Type: image/jpeg Size: 155212 bytes Desc: classification_before.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: resource_after.JPG Type: image/jpeg Size: 159433 bytes Desc: resource_after.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: classification_after.JPG Type: image/jpeg Size: 157096 bytes Desc: classification_after.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: table_after.JPG Type: image/jpeg Size: 224457 bytes Desc: table_after.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: table_before.JPG Type: image/jpeg Size: 217468 bytes Desc: table_before.JPG URL: From ltang5 at lib.msu.edu Thu Sep 21 15:18:50 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 21 Sep 2017 19:18:50 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace Message-ID: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu> Hello, we recently upgraded from 2.1.1 from 1.5.3. With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request. Is this normal? Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI? Thanks! Lydia -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-09-21 at 3.12.56 PM.png Type: image/png Size: 82972 bytes Desc: Screen Shot 2017-09-21 at 3.12.56 PM.png URL: From benn.joseph at northwestern.edu Thu Sep 21 16:21:25 2017 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Thu, 21 Sep 2017 20:21:25 +0000 Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Message-ID: Hi all, We've encountered an issue with the v2.1.2 Print-to-PDF button in the public interface--apparently for any resource record with an ampersand that is followed immediately by another character that is not a space (e.g. "b&w" or "AT&T"), the ampersand is misinterpreted and causes the Print-to-PDF button to fail with an error. For me, that error is just "something went wrong", but the log shows this (when it gets tripped up on "b&w"): RuntimeError (Failed to clean XML: The reference to entity "w" must end with the ';' delimiter.): So we're guessing ArchivesSpace is thinking "&w" should be "&w;", and so forth for any other string of text with an ampersand. I checked this by going into a record that wouldn't print and changing the lone suspect ampersand ("AT&T" to "AT and T") and the PDF generated just fine. This doesn't impact being able to just view resource records in the public interface, it's just the PDF function that isn't working. It's a problem, though, because we want to be able to use that PDF functionality but we also have a lot of ampersands in our resource records! Has anyone else experienced this issue or possibly come up with a fix? Thanks, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Thu Sep 21 16:29:34 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 21 Sep 2017 20:29:34 +0000 Subject: [Archivesspace_Users_Group] FW: ArchivesSpace PUI request follow up Message-ID: <1C800ACF-E701-4B3D-ADE2-EB302BA35B1D@lib.msu.edu> Hi again, I?m just sending along the sample request from the PUI. Will there be further refining of visually rendering of the request? The staff who received the request was really surprised and not used to reading this sort of raw dump of information. Thanks, Lydia From: spc Date: Thursday, September 21, 2017 at 3:14 PM To: "Tang, Lydia" Subject: FW: *****SPAM*****Request for Harry Smith Tribute. Nostoc Magazine, The Numberless Issue; 40-47, 2013 From: aspace at as-prod.lib.msu.edu [mailto:aspace at as-prod.lib.msu.edu] Sent: Thursday, September 21, 2017 3:13 PM To: spc Subject: *****SPAM*****Request for Harry Smith Tribute. Nostoc Magazine, The Numberless Issue; 40-47, 2013 New Request Request received: 2017-09-21 15:12:42 -0400 Requester Name: Lydia Email: ltang5 at msu.edu Date: test Notes for Staff: test Record Requested user_name: Lydia user_email: ltang5 at msu.edu date: test note: test title: Harry Smith Tribute. Nostoc Magazine, The Numberless Issue; 40-47, 2013 identifier: cite: Harry Smith Tribute. Nostoc Magazine, The Numberless Issue; 40-47, 2013. The Smith collection, . Michigan State University Libraries Special Collections. http://as.lib.msu.edu/repositories/2/archival_objects/24679 Accessed September 21, 2017. request_uri: /repositories/2/archival_objects/24679 resource_name: The Smith collection resource_id: MSS 212 large repo_name: Michigan State University Libraries Special Collections hierarchy: ["The Smith collection", "CORRESPONDENCE, 1964-1997"] restrict: The collection is open for research.

The material is stored offsite. Please request materials 3 days ahead of your visit. machine: container: Box: 1, Folder: i (Mixed Materials) top_container_url: /repositories/2/top_containers/729 barcode: M01020603 location_title: Remote storage [Off-site] location_url: /locations/123 ["user_name: Lydia", "user_email: ltang5 at msu.edu", "date: test", "note: test", "title: Harry Smith Tribute. Nostoc Magazine, The Numberless Issue; 40-47, 2013", "identifier: ", "cite: Harry Smith Tribute. Nostoc Magazine, The Numberless Issue; 40-47, 2013. The Smith collection, . Michigan State University Libraries Special Collections. http://as.lib.msu.edu/repositories/2/archival_objects/24679 Accessed September 21, 2017.", "request_uri: /repositories/2/archival_objects/24679", "resource_name: The Smith collection", "resource_id: MSS 212 large", "repo_name: Michigan State University Libraries Special Collections", "hierarchy: [\"The Smith collection\", \"CORRESPONDENCE, 1964-1997\"]", "restrict: The collection is open for research.

The material is stored offsite. Please request materials 3 days ahead of your visit.", "machine: ", "container: Box: 1, Folder: i (Mixed Materials)", "top_container_url: /repositories/2/top_containers/729", "barcode: M01020603", "location_title: Remote storage [Off-site]", "location_url: /locations/123"] From Christine.Kim at lyrasis.org Thu Sep 21 16:39:01 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 21 Sep 2017 20:39:01 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - September 2017 Message-ID: [ASpaceOrgHome.jpg] September 2017 Update This month's update includes some exciting news! A Georgia Tech co-op student has joined our team to give special focus on updating the migration tool. We are also hiring a new DevOps Specialist to support the ArchivesSpace community. We have new incoming chairs for both the Technical Advisory Council and the User Advisory Council. And we're excited to share that we'll be hosting a webinar on implementation strategies for the new Public User Interface! Read on for more details. Development Release Updates: v2.1.1 and v2.1.2 Two minor releases have come out since the last update. The v2.1.1 release contains a couple dozen small bug fixes and enhancements, including improvements to the PUI and OAI-PMH implementations in v2.1.0. Most notably, it addresses a bug that caused initial indexing to take significantly longer than was desirable, particularly for large databases. Many thanks to the Hudson Molonglo team - James Bullen, Payten Giles, and Mark Triggs - for their work on these issues. This release was also improved by a community pull request from Chris Fitzpatrick. The full list of bug fixes and improvements for v2.1.1 is included in the release notes: https://github.com/archivesspace/archivesspace/releases/tag/v2.1.1 The v2.1.2 release also contains several bug fixes, including for an issue with installing on Windows using a blank MySQL database and for an issue with archival objects with only dates/dates as titles not appearing in the new public interface. It also addresses some technical debt issues. A big thanks to Steve Majewski for submitting fixes for three of the items included in this release. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.1.2. The full list of bug fixes and improvements is included in the release notes. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.1.0, we would recommend going directly to 2.1.2, though you should read the considerations for upgrading to 2.1.0 at https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_2.1.0.md first. Thanks to our Development Prioritization subteam for prioritizing the bug fixes to be addressed, the Testing subteam for their quick work in putting the delivered bug fixes through their paces, and to all the individual members who identified issues on the Users Group listserv, Github, and directly to program team members and made suggestions for improvements. If you have any questions or need help upgrading, please let us know. Other Development In other development news, the EAD3 exporter that Trevor Thornton of North Carolina State and Noah Huffman of Duke University worked on over the summer has now been merged into the core code, and we are expecting the arrival of the code for the assessment module that Tufts University is subsidizing (development work by Hudson Molonglo) within days. Thank so much to these community members for all their work in making these projects happen! Look for an announcement soon of options for testing these new features and a potential release date. Welcome, Sarah Morrissey! Sarah Morrissey joined us on August 21 to focus on some special projects for ArchivesSpace. Sarah is a second-year Computer Science major at Georgia Tech with a particular interest in data management. As part of a co-op program with Georgia Tech, she will be with us this Fall to upgrade the ArchivesSpace migration tools. Sarah will return next Summer 2018 and Spring 2019, with additional projects to be designated at that time. Please join us in welcoming Sarah Morrissey to the ArchivesSpace team! TAC/UAC Chairs Update We are thrilled to share that new chairs have been elected for both the Technical Advisory and User Advisory Councils. Max Eckard from the University of Michigan will chair TAC, and Suzanne Stasiulatis from the Pennsylvania Historical and Museum Commission will chair UAC. The Chair for each Council is selected by the Council and serves a one-year term. Please welcome Max and Suzanne to their new appointments! Special thanks to our former chairs Sally Vermaaten and Gordon Daines for their past years of leadership and service. Webinar on the new PUI: October 26, 1-2:30 EST Join us on October 26 as we take a close look at a variety of implementation strategies on the new ArchivesSpace PUI! Mark Custer (Archivist and Metadata Coordinator, Yale University) and Susan Pyzynski (Associate Librarian of Houghton Library for Technical Services, Harvard University) were deeply entrenched in the public interface as they led the community effort to shape this essential access point for archival collections. Now they have moved onto their next great challenge -- implementing the PUI at their own institutions. Both Mark and Susan will each share the strategies they have created to roll out the new PUI. Both aim to be using the new PUI by early next year. Grand Valley State University have been using the ArchivesSpace PUI since 2014 and have already rolled out the new public interface. Annie Benefiel (Archivist for Collection Management, GVSU) and Leigh Rupinski (Archivist for Public Services & Community Engagement, GVSU) will share valuable insight on how the PUI has affected their day-to-day responsibilities as well as public reception and adapting their instruction for students and researchers. Please join us on October 26 at 1-2:30 EST as Mark, Susan, Annie, and Leigh as they share their experiences. Please feel free to bring any questions you have on the new public interface! Details on attending the webinar will be posted soon. If you have any questions about this webinar, please contact Kim at christine.kim at lyrasis.org. We look forward to seeing you at the webinar! Highlighting User Stories - Call for Contributions! Please submit stories you would like to share in our community-centric blog series. We want to hear the details on your challenges, experiences, and problem-solving thought processes as you offer some helpful advice along the way. Some ideas include: migration mishaps, creative workarounds, favorite plugins, and more! We welcome this space as an opportunity to share professional journal articles, short anecdotes, presentation papers, how-to guides, lessons learned, and more! Our goal is to highlight our members and their work at the very center of these stories. If you would like to contribute any stories or have ideas on the type of stories you'd like to hear, please reach out to Kim at christine.kim at lyrasis.org. Annual Report ArchivesSpace is delighted to share our first annual report with you. This digital document celebrates our community's many accomplishments in the year that has just passed, and provides information on plans for the future. Thanks to all our members for all you've done to sustain and move the application and the program forward. None of this is possible without you! The document is available for download through this link: https://tinyurl.com/y7rjoeyj We encourage you to share the ArchivesSpace annual report with others at your institutions and anyone else with an interest in ArchivesSpace. We hope this report may be especially helpful in conveying the value of ArchivesSpace as an application, as well as the value of ArchivesSpace membership to resource allocators at your institutions. This report reflects a true community effort. Thanks to all whose ideas and feedback over the years prompted the creation of this new offering and strengthened our commitment to communication and transparency. We welcome feedback and ideas for future annual reports. Please feel free to email us at ArchivesSpaceHome at lyrasis.org at any point. We're hiring! DevOps Specialist supporting ArchivesSpace We are thrilled to announce a new job opening for a DevOps Specialist supporting the ArchivesSpace community and the ArchivesSpace program team. LYRASIS, the organizational home for ArchivesSpace, recently approved an additional staff position based in Technology Services to support ArchivesSpace technical needs. The position description can be found at https://www.lyrasis.org/job/Pages/LYRASIS-Positions.aspx. While the position will report to the Director of Technology Services, the person in the position will work closely with the ArchivesSpace program team to provide technical support for ArchivesSpace members as well as coding and other technical assistance for the application. Over time the person will have additional responsibilities for supporting LYRASIS hosting clients. This position is ideal for someone who is familiar with ArchivesSpace or other archival/collection management systems and likes to help people with their technical questions. Previous experience with multiple platforms (Linux, Mac, Windows), MySQL, Java, Ruby, and Apache Solr is required. We are excited about this additional support within the organizational home for ArchivesSpace technical needs. If you are interested in applying, or know someone who is, applications, including a cover letter and resume, are being accepted via email at human.resources at lyrasis.org. If you have questions about the position, feel free to reach out to Christine (christine.dibella at lyrasis.org) or Laney (laney.mcglohon at lyrasis.org). Membership Update Our new members since August 11 include: * University of Rochester * Lincoln Center Archives * Indiana University-Purdue University Indianapolis / IUPUI University Library * San Diego State University * Jesuit Archives and Research Center As of September 21, we have 328 General members, 15 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools roundtable 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. Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 20006 bytes Desc: image003.jpg URL: From Joshua.D.Shaw at dartmouth.edu Thu Sep 21 16:54:04 2017 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Thu, 21 Sep 2017 20:54:04 +0000 Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop In-Reply-To: References: , Message-ID: I'd love to know the solution as well, since I'm seeing a similar/related(?) error as I'm starting to test 2.1.2 locally. I've migrated from a 1.5.3 instance and see the following error when attempting to view an archival object. The archival object information renders in the record pane, but the tree fails to populate anything except the collection level. I checked the db and the id being referenced (14195) does exist in the archival_object table (I think that's what the id is referencing - assuming I'm reading the code right). This is running with only one plugin (our omniauthCas) plugin enabled, though the database contains some additional tables from some of our other plugins key not found: :14195 org/jruby/RubyHash.java:1189:in `fetch' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:203:in `block in node_from_root' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:193:in `block in node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:105:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:145:in `node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/resource.rb:203:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stanonik, Ronald Sent: Friday, September 15, 2017 1:44:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I notice a repeating error and stacktrace in the log about an unhandled exception. E, [2017-09-15T09:45:13.168412 #10788] ERROR -- : Thread-5342: Unhandled exception! E, [2017-09-15T09:45:13.168722 #10788] ERROR -- : key not found: : org/jruby/RubyHash.java:1189:in `fetch' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:63:in `root_record' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:22:in `block in add_ancestors' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:12:in `add_ancestors' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/archival_object.rb:69:in `sequel_to_jsonmodel' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:105:in `listing_response' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in `handle_listing' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:95:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' D, [2017-09-15T09:45:13.169154 #10788] DEBUG -- : Thread-5342: Responded with [500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"29"}, ["{\"error\":\"key not found: :\"}\n"]]... in 247ms From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 21 17:06:14 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 21 Sep 2017 21:06:14 +0000 Subject: [Archivesspace_Users_Group] Advice on Custom Theming In-Reply-To: References: Message-ID: I believe you are running into Rails defaults before the ASpace plugins come into play. As I test, I added the line 'layout "custom"' to frontend/app/controllers/application_controller.rb. It will then use layouts/custom.html.erb, and that layout appears to work if that file is in either frontend/app/views/layouts/ or plugins/local/frontend/views/layouts/ . However, If I try moving the edited copy of application_controller.rb to the plugins/local/frontend/controllers/ directory, it no longer works as the default application controller is what the base class for all other controllers. Perhaps making the plugins extensible on this level would require adding a conditional check for plugin layouts in base application_controller . Instead of deep mods, another possible way is patching it after the fact with javascript. You could try adding something like the following to plugins/local/frontend/views/layout_head.html.erb: -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chelsea Lobdell Sent: Thursday, September 21, 2017 1:04:40 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Advice on Custom Theming Hi Archivesspace, I'm looking for some advice on how to get started with custom theming. I've been reviewing this custom theming documentation: https://github.com/archivesspace/archivesspace/blob/master/CUSTOMIZING_THEMING.md [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/CUSTOMIZING_THEMING.md at master ... github.com Customizing and Theming ArchivesSpace I just want to change some of the labels and messages! All the messages and labels are stored in locales files, which is part of ... The initial change I'm trying to make is really simple. In layouts/application.html.erb I just need to change the header, navigation and maincontent from container-fluid to container to match the style of the other applications in our application suite. My first attempt was to add archivesspace/plugins/local/frontend/views/layouts/application.html.erb and to make the appropriate changes. However, after a restart I am not seeing my changes. Can anyone advise me on how to get this working? I also recognize that application.html.erb is a pretty important file to be customizing. If anybody has advice on how best to approach this, I would appreciate it. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Sep 21 17:14:58 2017 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 21 Sep 2017 21:14:58 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace In-Reply-To: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu> References: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu> Message-ID: We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs: INFO: I, [2017-09-21T15:08:03.838360 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600 [the e-mail successfully sends here; log output omitted] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-21T15:08:09.740133 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#:0x59036603>): Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] 4:

Record Requested

[5c583ccc-1669-40c4-9f90-81f09fac562b] 5: Title: <%= @request.title %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 6: <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 7: URL: <%= link_to url, app_prefix(url) %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 8: [5c583ccc-1669-40c4-9f90-81f09fac562b] 9: [5c583ccc-1669-40c4-9f90-81f09fac562b] 10:
Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request' -k -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Thursday, September 21, 2017 1:19 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace Hello, we recently upgraded from 2.1.1 from 1.5.3. With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request. Is this normal? Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI? Thanks! Lydia From mark.custer at yale.edu Thu Sep 21 17:30:33 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 21 Sep 2017 21:30:33 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace In-Reply-To: References: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu> Message-ID: All, I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case. I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time. Here's what a message would look like that's sent to a patron (as you can see, it doesn?t include ALL of the data, like what the staff would receive), and they shouldn?t see an error message when requesting after everything has been configured to allow email requesting: Thank you for your request Record Requested Title: Watercolor of Brassie fly nymph (fishing fly) URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375 Your Details Name: m Email: mark.custer at yale.edu Date: Notes for Staff: I don?t believe that the email that was sent to staff ever had a specialized template, like this one, however. It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI. Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly. I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I?m not sure why exactly that was or might be). Just so that I?m clear, though? Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received. Is that correct? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Thursday, 21 September, 2017 5:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs: INFO: I, [2017-09-21T15:08:03.838360 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600 [the e-mail successfully sends here; log output omitted] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-21T15:08:09.740133 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#:0x59036603>): Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] 4:

Record Requested

[5c583ccc-1669-40c4-9f90-81f09fac562b] 5: Title: <%= @request.title %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 6: <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 7: URL: <%= link_to url, app_prefix(url) %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 8:
[5c583ccc-1669-40c4-9f90-81f09fac562b] 9: [5c583ccc-1669-40c4-9f90-81f09fac562b] 10:
Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request' -k -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Thursday, September 21, 2017 1:19 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace Hello, we recently upgraded from 2.1.1 from 1.5.3. With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request. Is this normal? Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI? Thanks! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Sep 21 17:38:33 2017 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 21 Sep 2017 21:38:33 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace In-Reply-To: References: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu> Message-ID: We?ve been able to receive the e-mail confirmations ArchivesSpace sends, both with my personal e-mail and with LibAnswers. It?s only when it tries to render request_received_email.html that it throws the error. -k From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Thursday, September 21, 2017 3:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace All, I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case. I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time. Here's what a message would look like that's sent to a patron (as you can see, it doesn?t include ALL of the data, like what the staff would receive), and they shouldn?t see an error message when requesting after everything has been configured to allow email requesting: Thank you for your request Record Requested Title: Watercolor of Brassie fly nymph (fishing fly) URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375 Your Details Name: m Email: mark.custer at yale.edu Date: Notes for Staff: I don?t believe that the email that was sent to staff ever had a specialized template, like this one, however. It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI. Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly. I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I?m not sure why exactly that was or might be). Just so that I?m clear, though? Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received. Is that correct? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Thursday, 21 September, 2017 5:15 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs: INFO: I, [2017-09-21T15:08:03.838360 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600 [the e-mail successfully sends here; log output omitted] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-21T15:08:09.740133 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#:0x59036603>): Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] 4:

Record Requested

[5c583ccc-1669-40c4-9f90-81f09fac562b] 5: Title: <%= @request.title %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 6: <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 7: URL: <%= link_to url, app_prefix(url) %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 8:
[5c583ccc-1669-40c4-9f90-81f09fac562b] 9: [5c583ccc-1669-40c4-9f90-81f09fac562b] 10:
Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request' -k -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Thursday, September 21, 2017 1:19 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace Hello, we recently upgraded from 2.1.1 from 1.5.3. With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request. Is this normal? Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI? Thanks! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Thu Sep 21 18:13:57 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Thu, 21 Sep 2017 22:13:57 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend In-Reply-To: References: Message-ID: I saw another person got this error but for a different request. Any ideas on what can cause this is appreciated. thanks From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jones, Jeremy Sent: Wednesday, September 20, 2017 5:10 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback Sure, I think this is what the log captured: Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={q=(id:("\/repositories\/3\/resources\/243\/tree\/root"))&csv.escape=\&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_default:true&fq=publish:true&rows=1&wt=json&facet=true} hits=0 status=0 QTime=1 Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: http://localhost:8089/search?publish=true&page_size=10&q=collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%28types%3Apui+AND+types%3Apui_container%29&page=1 I simply clicked collections and then clicked on the first one. Repositories/3/resource/243. I hope this helps. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Wednesday, September 20, 2017 4:59 PM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] can't view collections on the backend Jeremy, Can you share the http requests you made to generate the error? Don On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy > wrote: Hello, I?m having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy _______________________________________________ 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 j at minorscience.com Thu Sep 21 18:57:16 2017 From: j at minorscience.com (Jason Loeffler) Date: Thu, 21 Sep 2017 18:57:16 -0400 Subject: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend In-Reply-To: References: Message-ID: Are you making an external http request to an endpoint, resulting in the log output above? Or are you somehow issuing the POST method internally? What do you mean by "I simply clicked collections and then clicked on the first one"? Can you refer us to the other user report for this error? On Thu, Sep 21, 2017 at 6:13 PM, Jones, Jeremy wrote: > I saw another person got this error but for a different request. Any > ideas on what can cause this is appreciated. > > > > thanks > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jones, > Jeremy > *Sent:* Wednesday, September 20, 2017 5:10 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] [EXT] Re: can't view > collections on the backend > > > > This sender failed our fraud detection checks and may not > be who they appear to be. Learn about spoofing > > > Feedback > > Sure, I think this is what the log captured: > > > > Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute > > INFO: [collection1] webapp= path=/select params={q=(id:("\/ > repositories\/3\/resources\/243\/tree\/root"))&csv.escape= > \&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_ > default:true&fq=publish:true&rows=1&wt=json&facet=true} hits=0 status=0 > QTime=1 > > > > Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: > http://localhost:8089/search?publish=true&page_size=10&q= > collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+% > 28types%3Apui+AND+types%3Apui_container%29&page=1 > > > > I simply clicked collections and then clicked on the first one. > Repositories/3/resource/243. I hope this helps. > > > > jeremy > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Donald > Mennerich > *Sent:* Wednesday, September 20, 2017 4:59 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* [EXT] Re: [Archivesspace_Users_Group] can't view collections > on the backend > > > > Jeremy, > > Can you share the http requests you made to generate the error? > > Don > > > > > > On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy > wrote: > > Hello, > > > I?m having a few issues with Archivesspace. First, I cannot view the > contents of a collection on the backend view (:8089). I can view them on > the front end and edit them. But the backend view says (We're sorry, but > something went wrong. > > If you are the application owner check the logs for more information. > > > > The logs say: > > > > > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server > Error in 507ms > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error > (undefined method `[]' for nil:NilClass): > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && > @result.respond_to?(:metadata) %> > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] > > > > Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context > log > > INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in > `metadata' > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in > `_app_views_shared__metadata_html_erb__1424742346_2312' > > [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in > `_app_views_layouts_application_html_erb___1292011715_2310' > > > > I cannot make much from this log entry other than there was a fatal > error. Any ideas what could be causing this? > > > > Thank you > > jeremy > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Fri Sep 22 08:48:51 2017 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Fri, 22 Sep 2017 12:48:51 +0000 Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface In-Reply-To: References: Message-ID: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> Hi Benn, This is a recurring issue I hit over both Harvard and Smith?s collections ? it?s a consequence of ASpace not really having a distinction between mixed content and plaintext content. Unfortunately, there isn?t really a good solution. The best solution as far as I?ve been able to figure is to use HTML/XML entity for ampersand (&) wherever it appears in a context that?s treated by the interface/etc as markup; title fields _definitely_ fall under that category. There?s unfortunately no reliable guide to what fields are ?mixed content? and what fields are ?plaintext content? because, well, the underlying system doesn?t track that distinction ? it?s up to how the fields are eventually displayed/used to build exports/etc. As to _how_ to fix it ? well, it depends somewhat on whether you can be ABSOLUTELY SURE you don?t have any HTML/XML entities in your title fields. If you are ABSOLUTELY SURE of this, you should be able to make the change via API or on the SQL level, but if you DO have entities, it gets a lot harder, to the point where manual review is probably appropriate. - Dave Mayo ASpace Core Committer?s Group Member From: on behalf of Benn Joseph Reply-To: Archivesspace Users Group Date: Thursday, September 21, 2017 at 4:21 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Hi all, We've encountered an issue with the v2.1.2 Print-to-PDF button in the public interface--apparently for any resource record with an ampersand that is followed immediately by another character that is not a space (e.g. "b&w" or "AT&T"), the ampersand is misinterpreted and causes the Print-to-PDF button to fail with an error. For me, that error is just "something went wrong", but the log shows this (when it gets tripped up on "b&w"): RuntimeError (Failed to clean XML: The reference to entity "w" must end with the ';' delimiter.): So we're guessing ArchivesSpace is thinking "&w" should be "&w;", and so forth for any other string of text with an ampersand. I checked this by going into a record that wouldn?t print and changing the lone suspect ampersand (?AT&T? to ?AT and T?) and the PDF generated just fine. This doesn't impact being able to just view resource records in the public interface, it's just the PDF function that isn't working. It's a problem, though, because we want to be able to use that PDF functionality but we also have a lot of ampersands in our resource records! Has anyone else experienced this issue or possibly come up with a fix? Thanks, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Sep 22 09:15:49 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 22 Sep 2017 13:15:49 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend In-Reply-To: References: Message-ID: Does this error happen in the PUI view? Based on this error: INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> My first guess would be that there?s a problem with how the JSON-LD metadata is being created in the HTML view. So, I wonder if there?s a problem happening along the lines here: https://github.com/archivesspace/archivesspace/blob/81875d98a7764f0ed94826a2b2b7a85e39778885/public/app/models/resource.rb#L37-L109 ? I know that you mentioned a problem on the backend, via port 8089, but I?m not sure why that would display the above error. Mark p.s. here?s an example of what that metadata section could look like, taken from the LYRASIS sandbox website: From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Thursday, 21 September, 2017 6:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend Are you making an external http request to an endpoint, resulting in the log output above? Or are you somehow issuing the POST method internally? What do you mean by "I simply clicked collections and then clicked on the first one"? Can you refer us to the other user report for this error? On Thu, Sep 21, 2017 at 6:13 PM, Jones, Jeremy > wrote: I saw another person got this error but for a different request. Any ideas on what can cause this is appreciated. thanks From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jones, Jeremy Sent: Wednesday, September 20, 2017 5:10 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback Sure, I think this is what the log captured: Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={q=(id:("\/repositories\/3\/resources\/243\/tree\/root"))&csv.escape=\&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_default:true&fq=publish:true&rows=1&wt=json&facet=true} hits=0 status=0 QTime=1 Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: http://localhost:8089/search?publish=true&page_size=10&q=collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%28types%3Apui+AND+types%3Apui_container%29&page=1 I simply clicked collections and then clicked on the first one. Repositories/3/resource/243. I hope this helps. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Wednesday, September 20, 2017 4:59 PM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] can't view collections on the backend Jeremy, Can you share the http requests you made to generate the error? Don On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy > wrote: Hello, I?m having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Sep 22 09:41:31 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 22 Sep 2017 13:41:31 +0000 Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface In-Reply-To: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> References: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> Message-ID: Dave, Benn: Another important point here is that the ASpace staff interface attempts to handle both ? & ? and ? & ?. Those spaces are (quite unfortunately) important here. & is a special HTML and XML entity reference for the ampersand character. A nice, short overview is provided here: https://mrcoles.com/blog/how-use-amersands-html-encode/ Benn, as you?ve discovered, when there aren?t any spaces, it looks like those attempts to handle both types of references go out the window. So, AT&T, b&w, &c., &c., &c., cause problems. The really problematic part is that the problems and the ?solutions? vary depending on whether you?re exporting data, storing it titles vs. notes, displaying it in the PUI, creating a PDF, &c. I just recently discovered another wrinkle that puts us into a real catch 22. Here it is: We?ve got a note with ?&c.? in ArchivesSpace. It would be great if that could be handled okay everywhere, whether ArchivesSpace forced us to use &c OR &c (and I don?t care which way!), but as Dave explains, there aren?t clear distinctions for ASpace to make in every situation right now. With that ?&c? in the note, here?s what I wind up with: * The PUI displays the note correctly. Yay! * The EAD exporter won?t wrap paragraph elements around the note, which results in invalid EAD. Boo. If I edit that note to instead be ?&c?, here?s what I wind up with: * The PUI displays everything in the note up until that character. Everything else in the note silently falls away into oblivion (but surely this would be an easy bug fix, I hope???). Boo. * The EAD exporter works perfectly. Yay! Dave, since you included the line about being on the Core Committer?s Group, does that mean that this issue will be discussed soon ? (I know that it wouldn?t be an easy thing to tackle, but it would make a lot of metadata folks out there pretty happy!) Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mayo, Dave Sent: Friday, 22 September, 2017 8:49 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Hi Benn, This is a recurring issue I hit over both Harvard and Smith?s collections ? it?s a consequence of ASpace not really having a distinction between mixed content and plaintext content. Unfortunately, there isn?t really a good solution. The best solution as far as I?ve been able to figure is to use HTML/XML entity for ampersand (&) wherever it appears in a context that?s treated by the interface/etc as markup; title fields _definitely_ fall under that category. There?s unfortunately no reliable guide to what fields are ?mixed content? and what fields are ?plaintext content? because, well, the underlying system doesn?t track that distinction ? it?s up to how the fields are eventually displayed/used to build exports/etc. As to _how_ to fix it ? well, it depends somewhat on whether you can be ABSOLUTELY SURE you don?t have any HTML/XML entities in your title fields. If you are ABSOLUTELY SURE of this, you should be able to make the change via API or on the SQL level, but if you DO have entities, it gets a lot harder, to the point where manual review is probably appropriate. - Dave Mayo ASpace Core Committer?s Group Member From: > on behalf of Benn Joseph > Reply-To: Archivesspace Users Group > Date: Thursday, September 21, 2017 at 4:21 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Hi all, We've encountered an issue with the v2.1.2 Print-to-PDF button in the public interface--apparently for any resource record with an ampersand that is followed immediately by another character that is not a space (e.g. "b&w" or "AT&T"), the ampersand is misinterpreted and causes the Print-to-PDF button to fail with an error. For me, that error is just "something went wrong", but the log shows this (when it gets tripped up on "b&w"): RuntimeError (Failed to clean XML: The reference to entity "w" must end with the ';' delimiter.): So we're guessing ArchivesSpace is thinking "&w" should be "&w;", and so forth for any other string of text with an ampersand. I checked this by going into a record that wouldn?t print and changing the lone suspect ampersand (?AT&T? to ?AT and T?) and the PDF generated just fine. This doesn't impact being able to just view resource records in the public interface, it's just the PDF function that isn't working. It's a problem, though, because we want to be able to use that PDF functionality but we also have a lot of ampersands in our resource records! Has anyone else experienced this issue or possibly come up with a fix? Thanks, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Fri Sep 22 09:44:42 2017 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Fri, 22 Sep 2017 09:44:42 -0400 Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface In-Reply-To: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> References: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> Message-ID: The logic for converting ampersands in the EAD exporter is to only convert them if they are immediately followed by a space, otherwise they are assumed to be an entity. This is part of the process of sanitizing mixed content, which is actually applied to most fields. However, the ampersand conversion is included in the routine that handles line breaks (converting 2 line breaks into paragraphs as appropriate), and this is only applied to fields for which the corresponding EAD tag allows

as a child, which excludes untititle, abstract, etc. There's no good reason that I can think of why the ampersand conversion should be restricted in this way, so it can probably be moved to apply more broadly. Unfortunately, since the new EAD3 exporter is based on the existing EAD exporter, this problem persists in the EAD3 exporter, because I didn't really notice it until now. I'll try to fix it in both places and do a pull request. On Fri, Sep 22, 2017 at 8:48 AM, Mayo, Dave wrote: > Hi Benn, > > This is a recurring issue I hit over both Harvard and Smith?s collections > ? it?s a consequence of ASpace not really having a distinction between > mixed content and plaintext content. > > Unfortunately, there isn?t really a good solution. The best solution as > far as I?ve been able to figure is to use HTML/XML entity for ampersand > (&) wherever it appears in a context that?s treated by the > interface/etc as markup; title fields _*definitely*_ fall under that > category. There?s unfortunately no reliable guide to what fields are > ?mixed content? and what fields are ?plaintext content? because, well, the > underlying system doesn?t track that distinction ? it?s up to how the > fields are eventually displayed/used to build exports/etc. > > > As to _*how*_ to fix it ? well, it depends somewhat on whether you can be > ABSOLUTELY SURE you don?t have any HTML/XML entities in your title fields. > If you are ABSOLUTELY SURE of this, you should be able to make the change > via API or on the SQL level, but if you DO have entities, it gets a lot > harder, to the point where manual review is probably appropriate. > > - Dave Mayo > ASpace Core Committer?s Group Member > > *From: * on > behalf of Benn Joseph > *Reply-To: *Archivesspace Users Group lyralists.lyrasis.org> > *Date: *Thursday, September 21, 2017 at 4:21 PM > *To: *Archivesspace Users Group lyralists.lyrasis.org> > *Subject: *[Archivesspace_Users_Group] ampersand issue with PDF button in > 2.1.2 public interface > > > > Hi all, > > We've encountered an issue with the v2.1.2 Print-to-PDF button in the > public interface--apparently for any resource record with an ampersand that > is followed immediately by another character that is not a space (e.g. > "b&w" or "AT&T"), the ampersand is misinterpreted and causes the > Print-to-PDF button to fail with an error. For me, that error is just > "something went wrong", but the log shows this (when it gets tripped up on > "b&w"): > > > > RuntimeError (Failed to clean XML: The reference to entity "w" must end > with the ';' delimiter.): > > > > So we're guessing ArchivesSpace is thinking "&w" should be "&w;", and so > forth for any other string of text with an ampersand. I checked this by > going into a record that wouldn?t print and changing the lone suspect > ampersand (?AT&T? to ?AT and T?) and the PDF generated just fine. > > > > This doesn't impact being able to just view resource records in the public > interface, it's just the PDF function that isn't working. It's a problem, > though, because we want to be able to use that PDF functionality but we > also have a lot of ampersands in our resource records! Has anyone else > experienced this issue or possibly come up with a fix? > > > > Thanks, > > --Benn > > > > *Benn Joseph* > > Head of Archival Processing > > Northwestern University Libraries > > Northwestern University > > www.library.northwestern.edu > > > benn.joseph at northwestern.edu > > 847.467.6581 <(847)%20467-6581> > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Sep 22 10:11:22 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 22 Sep 2017 14:11:22 +0000 Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface In-Reply-To: References: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> Message-ID: Trevor, That would be fantastic!!!!! Benn, For your PDF error, I think that might be caused by a slightly different issue. The new PUI ?Print to PDF? process converts that ArchivesSpace JSON record to HTML and then converts that HTML into a PDF file. So, it doesn?t use the same JSON --> EAD --> PDF process as the staff interface. I?m assuming that a small tweak to this file https://github.com/archivesspace/archivesspace/blob/master/public/app/lib/xml_cleaner.rb might allow it to still create the PDF successfully (assuming that ArchivesSpace would want the application to handle both ?b&w? and ?b&w?, which might not be the case). We should log this issue in JIRA at some point, regardless, just so that it?s captured there. I don?t have time to do that right now, but I did update one of the files in the sandbox to illustrate the problem. Here it is: http://public.archivesspace.org/repositories/2/resources/1008/ * Before I added the lone collection-level note to this record, the PDF printed fine. * Once I added a note of ?b&w?, it failed. * When I change the note to ?b&w?, the PDF file works.... * It also still displays fine in the PUI, which might mean that the problem that I noted in my previous message only occurs when the note is in one of those ?see more? / ?see less? sections. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Trevor Thornton Sent: Friday, 22 September, 2017 9:45 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface The logic for converting ampersands in the EAD exporter is to only convert them if they are immediately followed by a space, otherwise they are assumed to be an entity. This is part of the process of sanitizing mixed content, which is actually applied to most fields. However, the ampersand conversion is included in the routine that handles line breaks (converting 2 line breaks into paragraphs as appropriate), and this is only applied to fields for which the corresponding EAD tag allows

as a child, which excludes untititle, abstract, etc. There's no good reason that I can think of why the ampersand conversion should be restricted in this way, so it can probably be moved to apply more broadly. Unfortunately, since the new EAD3 exporter is based on the existing EAD exporter, this problem persists in the EAD3 exporter, because I didn't really notice it until now. I'll try to fix it in both places and do a pull request. On Fri, Sep 22, 2017 at 8:48 AM, Mayo, Dave > wrote: Hi Benn, This is a recurring issue I hit over both Harvard and Smith?s collections ? it?s a consequence of ASpace not really having a distinction between mixed content and plaintext content. Unfortunately, there isn?t really a good solution. The best solution as far as I?ve been able to figure is to use HTML/XML entity for ampersand (&) wherever it appears in a context that?s treated by the interface/etc as markup; title fields _definitely_ fall under that category. There?s unfortunately no reliable guide to what fields are ?mixed content? and what fields are ?plaintext content? because, well, the underlying system doesn?t track that distinction ? it?s up to how the fields are eventually displayed/used to build exports/etc. As to _how_ to fix it ? well, it depends somewhat on whether you can be ABSOLUTELY SURE you don?t have any HTML/XML entities in your title fields. If you are ABSOLUTELY SURE of this, you should be able to make the change via API or on the SQL level, but if you DO have entities, it gets a lot harder, to the point where manual review is probably appropriate. - Dave Mayo ASpace Core Committer?s Group Member From: > on behalf of Benn Joseph > Reply-To: Archivesspace Users Group > Date: Thursday, September 21, 2017 at 4:21 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Hi all, We've encountered an issue with the v2.1.2 Print-to-PDF button in the public interface--apparently for any resource record with an ampersand that is followed immediately by another character that is not a space (e.g. "b&w" or "AT&T"), the ampersand is misinterpreted and causes the Print-to-PDF button to fail with an error. For me, that error is just "something went wrong", but the log shows this (when it gets tripped up on "b&w"): RuntimeError (Failed to clean XML: The reference to entity "w" must end with the ';' delimiter.): So we're guessing ArchivesSpace is thinking "&w" should be "&w;", and so forth for any other string of text with an ampersand. I checked this by going into a record that wouldn?t print and changing the lone suspect ampersand (?AT&T? to ?AT and T?) and the PDF generated just fine. This doesn't impact being able to just view resource records in the public interface, it's just the PDF function that isn't working. It's a problem, though, because we want to be able to use that PDF functionality but we also have a lot of ampersands in our resource records! Has anyone else experienced this issue or possibly come up with a fix? Thanks, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From sustasiula at pa.gov Fri Sep 22 10:48:57 2017 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Fri, 22 Sep 2017 14:48:57 +0000 Subject: [Archivesspace_Users_Group] AS PUI Terms for Database Mapping Message-ID: <4cc130fddc5e4b7bb06b29b3ecc8ae2f@ENCTCEXCH008.PA.LCL> Does anyone have a reference for the PUI screen terms matched to Database mapping? Will you share? This would help users who don't have access to the backend better understand the system. Does anyone have interest in formalizing this for other users? Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.PAStateArchives.com sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Fri Sep 22 11:00:02 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Fri, 22 Sep 2017 15:00:02 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend In-Reply-To: References: Message-ID: Hello, I am making the request from the :8081 endpoint. What do you mean by "I simply clicked collections and then clicked on the first one"? ? For instance on the archives space sandbox if you go to url http://public.archivesspace.org/ right now there are 7 links across the top (Repositories, Collections, Digital Material, Unprocessed Material, Subjects, Names, Record Groups) If you click collections, the next screen shows a list of collections. The first one says 1313? If click that one, information about that collection is displayed. When I do that on my instance it says ?We?re sorry, but something went wrong?. I check the log and it continually runs the staff and pui indexer every 30 seconds. So my log file is very large. I cannot find the User that reached the same screen right now. I will continue looking. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Thursday, September 21, 2017 5:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend Are you making an external http request to an endpoint, resulting in the log output above? Or are you somehow issuing the POST method internally? What do you mean by "I simply clicked collections and then clicked on the first one"? Can you refer us to the other user report for this error? On Thu, Sep 21, 2017 at 6:13 PM, Jones, Jeremy > wrote: I saw another person got this error but for a different request. Any ideas on what can cause this is appreciated. thanks From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jones, Jeremy Sent: Wednesday, September 20, 2017 5:10 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback Sure, I think this is what the log captured: Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={q=(id:("\/repositories\/3\/resources\/243\/tree\/root"))&csv.escape=\&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_default:true&fq=publish:true&rows=1&wt=json&facet=true} hits=0 status=0 QTime=1 Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: http://localhost:8089/search?publish=true&page_size=10&q=collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%28types%3Apui+AND+types%3Apui_container%29&page=1 I simply clicked collections and then clicked on the first one. Repositories/3/resource/243. I hope this helps. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Wednesday, September 20, 2017 4:59 PM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] can't view collections on the backend Jeremy, Can you share the http requests you made to generate the error? Don On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy > wrote: Hello, I?m having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Fri Sep 22 11:36:02 2017 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Fri, 22 Sep 2017 15:36:02 +0000 Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop In-Reply-To: References: , , Message-ID: To add another datapoint, when I change the publish status for all items in a node's immediate tree (ie file-> parent box -> parent series) then the child node and its parents will appear in the staff interface. If the AO or *any* of its ancestors are *not* published, they do *not* appear in the staff interface. I took a quick look at the database and the publish status for *most* of our AOs is "NULL", not the 1 or 0 that large_tree.rb is looking for in published_filter (line 73). I'm currently thinking that our initial custom migration never set that column... Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Joshua D. Shaw Sent: Thursday, September 21, 2017 4:54:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback I'd love to know the solution as well, since I'm seeing a similar/related(?) error as I'm starting to test 2.1.2 locally. I've migrated from a 1.5.3 instance and see the following error when attempting to view an archival object. The archival object information renders in the record pane, but the tree fails to populate anything except the collection level. I checked the db and the id being referenced (14195) does exist in the archival_object table (I think that's what the id is referencing - assuming I'm reading the code right). This is running with only one plugin (our omniauthCas) plugin enabled, though the database contains some additional tables from some of our other plugins key not found: :14195 org/jruby/RubyHash.java:1189:in `fetch' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:203:in `block in node_from_root' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:193:in `block in node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:105:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:145:in `node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/resource.rb:203:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stanonik, Ronald Sent: Friday, September 15, 2017 1:44:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I notice a repeating error and stacktrace in the log about an unhandled exception. E, [2017-09-15T09:45:13.168412 #10788] ERROR -- : Thread-5342: Unhandled exception! E, [2017-09-15T09:45:13.168722 #10788] ERROR -- : key not found: : org/jruby/RubyHash.java:1189:in `fetch' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:63:in `root_record' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:22:in `block in add_ancestors' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:12:in `add_ancestors' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/archival_object.rb:69:in `sequel_to_jsonmodel' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:105:in `listing_response' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in `handle_listing' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:95:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' D, [2017-09-15T09:45:13.169154 #10788] DEBUG -- : Thread-5342: Responded with [500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"29"}, ["{\"error\":\"key not found: :\"}\n"]]... in 247ms From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Fri Sep 22 11:43:03 2017 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Fri, 22 Sep 2017 15:43:03 +0000 Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface In-Reply-To: References: <15ED38DD-9F82-46D6-99CC-233E2011E5C9@harvard.edu> Message-ID: <69efa5403f6448378b1cebad92036a9b@evcspmbx04.ads.northwestern.edu> Yes, Trevor that would be great! Mark, I?ll look into whether we can try tweaking that xml_cleaner.rb file. That scenario you describe below is exactly what?s happening for us?although I should mention that we can still export valid EAD. For the AT&T example (which is in a Separated Materials note), AT&T gets changed to ?AT&T? in the EAD export, but PDF generation fails. If I change the actual text in the ArchivesSpace note to ?AT&T?, it still shows up as ?AT&T? in the exported EAD, but PDF generation works! Dave, I do remember there being a lot of HTML/XML entities in our title fields when we were using Archon, but I?m not seeing them in ArchivesSpace. Maybe we?ll do some more manual review before more seriously considering making a change on the SQL level. Thanks! --Benn From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Friday, September 22, 2017 9:11 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Trevor, That would be fantastic!!!!! Benn, For your PDF error, I think that might be caused by a slightly different issue. The new PUI ?Print to PDF? process converts that ArchivesSpace JSON record to HTML and then converts that HTML into a PDF file. So, it doesn?t use the same JSON --> EAD --> PDF process as the staff interface. I?m assuming that a small tweak to this file https://github.com/archivesspace/archivesspace/blob/master/public/app/lib/xml_cleaner.rb might allow it to still create the PDF successfully (assuming that ArchivesSpace would want the application to handle both ?b&w? and ?b&w?, which might not be the case). We should log this issue in JIRA at some point, regardless, just so that it?s captured there. I don?t have time to do that right now, but I did update one of the files in the sandbox to illustrate the problem. Here it is: http://public.archivesspace.org/repositories/2/resources/1008/ * Before I added the lone collection-level note to this record, the PDF printed fine. * Once I added a note of ?b&w?, it failed. * When I change the note to ?b&w?, the PDF file works.... * It also still displays fine in the PUI, which might mean that the problem that I noted in my previous message only occurs when the note is in one of those ?see more? / ?see less? sections. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Trevor Thornton Sent: Friday, 22 September, 2017 9:45 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface The logic for converting ampersands in the EAD exporter is to only convert them if they are immediately followed by a space, otherwise they are assumed to be an entity. This is part of the process of sanitizing mixed content, which is actually applied to most fields. However, the ampersand conversion is included in the routine that handles line breaks (converting 2 line breaks into paragraphs as appropriate), and this is only applied to fields for which the corresponding EAD tag allows

as a child, which excludes untititle, abstract, etc. There's no good reason that I can think of why the ampersand conversion should be restricted in this way, so it can probably be moved to apply more broadly. Unfortunately, since the new EAD3 exporter is based on the existing EAD exporter, this problem persists in the EAD3 exporter, because I didn't really notice it until now. I'll try to fix it in both places and do a pull request. On Fri, Sep 22, 2017 at 8:48 AM, Mayo, Dave > wrote: Hi Benn, This is a recurring issue I hit over both Harvard and Smith?s collections ? it?s a consequence of ASpace not really having a distinction between mixed content and plaintext content. Unfortunately, there isn?t really a good solution. The best solution as far as I?ve been able to figure is to use HTML/XML entity for ampersand (&) wherever it appears in a context that?s treated by the interface/etc as markup; title fields _definitely_ fall under that category. There?s unfortunately no reliable guide to what fields are ?mixed content? and what fields are ?plaintext content? because, well, the underlying system doesn?t track that distinction ? it?s up to how the fields are eventually displayed/used to build exports/etc. As to _how_ to fix it ? well, it depends somewhat on whether you can be ABSOLUTELY SURE you don?t have any HTML/XML entities in your title fields. If you are ABSOLUTELY SURE of this, you should be able to make the change via API or on the SQL level, but if you DO have entities, it gets a lot harder, to the point where manual review is probably appropriate. - Dave Mayo ASpace Core Committer?s Group Member From: > on behalf of Benn Joseph > Reply-To: Archivesspace Users Group > Date: Thursday, September 21, 2017 at 4:21 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface Hi all, We've encountered an issue with the v2.1.2 Print-to-PDF button in the public interface--apparently for any resource record with an ampersand that is followed immediately by another character that is not a space (e.g. "b&w" or "AT&T"), the ampersand is misinterpreted and causes the Print-to-PDF button to fail with an error. For me, that error is just "something went wrong", but the log shows this (when it gets tripped up on "b&w"): RuntimeError (Failed to clean XML: The reference to entity "w" must end with the ';' delimiter.): So we're guessing ArchivesSpace is thinking "&w" should be "&w;", and so forth for any other string of text with an ampersand. I checked this by going into a record that wouldn?t print and changing the lone suspect ampersand (?AT&T? to ?AT and T?) and the PDF generated just fine. This doesn't impact being able to just view resource records in the public interface, it's just the PDF function that isn't working. It's a problem, though, because we want to be able to use that PDF functionality but we also have a lot of ampersands in our resource records! Has anyone else experienced this issue or possibly come up with a fix? Thanks, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Sep 22 12:16:22 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Sep 2017 16:16:22 +0000 Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop In-Reply-To: References: , , Message-ID: Hi Joshua, I think your issue may be different than Ron's. Ron's appears to have been caused by orphaned instances and archival objects in the database. Earlier versions of ArchivesSpace ignored these during indexing, but 2.1 is more finicky about that. See https://archivesspace.atlassian.net/browse/ANW-220 for some information about that issue. Ron can hopefully share more details about his resolution. I do think your issue may also be specific to your data and local deployment, so it would be worth working through this on a support ticket. You'll see another message about that directly to you in a minute. It would also be great if you'd share the solution back to the list when you get there. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joshua D. Shaw Sent: Friday, September 22, 2017 11:36 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop To add another datapoint, when I change the publish status for all items in a node's immediate tree (ie file-> parent box -> parent series) then the child node and its parents will appear in the staff interface. If the AO or *any* of its ancestors are *not* published, they do *not* appear in the staff interface. I took a quick look at the database and the publish status for *most* of our AOs is "NULL", not the 1 or 0 that large_tree.rb is looking for in published_filter (line 73). I'm currently thinking that our initial custom migration never set that column... Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Joshua D. Shaw > Sent: Thursday, September 21, 2017 4:54:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback I'd love to know the solution as well, since I'm seeing a similar/related(?) error as I'm starting to test 2.1.2 locally. I've migrated from a 1.5.3 instance and see the following error when attempting to view an archival object. The archival object information renders in the record pane, but the tree fails to populate anything except the collection level. I checked the db and the id being referenced (14195) does exist in the archival_object table (I think that's what the id is referencing - assuming I'm reading the code right). This is running with only one plugin (our omniauthCas) plugin enabled, though the database contains some additional tables from some of our other plugins key not found: :14195 org/jruby/RubyHash.java:1189:in `fetch' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:203:in `block in node_from_root' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:193:in `block in node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:105:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:145:in `node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/resource.rb:203:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stanonik, Ronald > Sent: Friday, September 15, 2017 1:44:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I notice a repeating error and stacktrace in the log about an unhandled exception. E, [2017-09-15T09:45:13.168412 #10788] ERROR -- : Thread-5342: Unhandled exception! E, [2017-09-15T09:45:13.168722 #10788] ERROR -- : key not found: : org/jruby/RubyHash.java:1189:in `fetch' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:63:in `root_record' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:22:in `block in add_ancestors' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:12:in `add_ancestors' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/archival_object.rb:69:in `sequel_to_jsonmodel' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:105:in `listing_response' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in `handle_listing' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:95:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' D, [2017-09-15T09:45:13.169154 #10788] DEBUG -- : Thread-5342: Responded with [500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"29"}, ["{\"error\":\"key not found: :\"}\n"]]... in 247ms From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- 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 christine.dibella at lyrasis.org Fri Sep 22 12:21:16 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Sep 2017 16:21:16 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend In-Reply-To: References: Message-ID: Hi Jeremy, It looks like you?ve gotten a lot of help here on the list, but if you?d like to move this over to a tech support ticket at some point, please let us know at ArchivesSpaceHome at lyrasis.org. Either way, I?m sure those on the list will be eager to hear what needed to be done to fix it once your issue is resolved. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jones, Jeremy Sent: Friday, September 22, 2017 11:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend Hello, I am making the request from the :8081 endpoint. What do you mean by "I simply clicked collections and then clicked on the first one"? ? For instance on the archives space sandbox if you go to url http://public.archivesspace.org/ right now there are 7 links across the top (Repositories, Collections, Digital Material, Unprocessed Material, Subjects, Names, Record Groups) If you click collections, the next screen shows a list of collections. The first one says 1313? If click that one, information about that collection is displayed. When I do that on my instance it says ?We?re sorry, but something went wrong?. I check the log and it continually runs the staff and pui indexer every 30 seconds. So my log file is very large. I cannot find the User that reached the same screen right now. I will continue looking. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Thursday, September 21, 2017 5:57 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend Are you making an external http request to an endpoint, resulting in the log output above? Or are you somehow issuing the POST method internally? What do you mean by "I simply clicked collections and then clicked on the first one"? Can you refer us to the other user report for this error? On Thu, Sep 21, 2017 at 6:13 PM, Jones, Jeremy > wrote: I saw another person got this error but for a different request. Any ideas on what can cause this is appreciated. thanks From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jones, Jeremy Sent: Wednesday, September 20, 2017 5:10 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback Sure, I think this is what the log captured: Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={q=(id:("\/repositories\/3\/resources\/243\/tree\/root"))&csv.escape=\&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_default:true&fq=publish:true&rows=1&wt=json&facet=true} hits=0 status=0 QTime=1 Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: http://localhost:8089/search?publish=true&page_size=10&q=collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%28types%3Apui+AND+types%3Apui_container%29&page=1 I simply clicked collections and then clicked on the first one. Repositories/3/resource/243. I hope this helps. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Wednesday, September 20, 2017 4:59 PM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] can't view collections on the backend Jeremy, Can you share the http requests you made to generate the error? Don On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy > wrote: Hello, I?m having a few issues with Archivesspace. First, I cannot view the contents of a collection on the backend view (:8089). I can view them on the front end and edit them. But the backend view says (We're sorry, but something went wrong. If you are the application owner check the logs for more information. The logs say: Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-20T16:39:38.022275 #18373] INFO -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 507ms Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && @result.respond_to?(:metadata) %> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %> Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb__1424742346_2312' [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___1292011715_2310' I cannot make much from this log entry other than there was a fatal error. Any ideas what could be causing this? Thank you jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From laney.mcglohon at lyrasis.org Fri Sep 22 12:22:28 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Fri, 22 Sep 2017 16:22:28 +0000 Subject: [Archivesspace_Users_Group] AS PUI Terms for Database Mapping Message-ID: Hey Suzanne, The reports team has been working on creating a data dictionary for the ArchivesSpace database. I think adding the corresponding PUI terms would be a great enhancement to the data dictionary. Carolyn Runyon is the head of the reports team, so you might want to touch base with her. Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: on behalf of "Stasiulatis, Suzanne" Reply-To: Archivesspace Users Group Date: Friday, September 22, 2017 at 10:48 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] AS PUI Terms for Database Mapping Does anyone have a reference for the PUI screen terms matched to Database mapping? Will you share? This would help users who don?t have access to the backend better understand the system. Does anyone have interest in formalizing this for other users? Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.PAStateArchives.com sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Fri Sep 22 12:28:59 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Fri, 22 Sep 2017 16:28:59 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: 2.1.2 re-indexing loop In-Reply-To: References: , , Message-ID: +1 on this... I am getting this index loop as well. I am also not able to view any details of my collections and I am not familiar enough with the program to know which is causing the other or if these issues are independent of each other. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Friday, September 22, 2017 11:16 AM To: Archivesspace Users Group Subject: [EXT] Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop Hi Joshua, I think your issue may be different than Ron's. Ron's appears to have been caused by orphaned instances and archival objects in the database. Earlier versions of ArchivesSpace ignored these during indexing, but 2.1 is more finicky about that. See https://archivesspace.atlassian.net/browse/ANW-220 for some information about that issue. Ron can hopefully share more details about his resolution. I do think your issue may also be specific to your data and local deployment, so it would be worth working through this on a support ticket. You'll see another message about that directly to you in a minute. It would also be great if you'd share the solution back to the list when you get there. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joshua D. Shaw Sent: Friday, September 22, 2017 11:36 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop To add another datapoint, when I change the publish status for all items in a node's immediate tree (ie file-> parent box -> parent series) then the child node and its parents will appear in the staff interface. If the AO or *any* of its ancestors are *not* published, they do *not* appear in the staff interface. I took a quick look at the database and the publish status for *most* of our AOs is "NULL", not the 1 or 0 that large_tree.rb is looking for in published_filter (line 73). I'm currently thinking that our initial custom migration never set that column... Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Joshua D. Shaw > Sent: Thursday, September 21, 2017 4:54:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback I'd love to know the solution as well, since I'm seeing a similar/related(?) error as I'm starting to test 2.1.2 locally. I've migrated from a 1.5.3 instance and see the following error when attempting to view an archival object. The archival object information renders in the record pane, but the tree fails to populate anything except the collection level. I checked the db and the id being referenced (14195) does exist in the archival_object table (I think that's what the id is referencing - assuming I'm reading the code right). This is running with only one plugin (our omniauthCas) plugin enabled, though the database contains some additional tables from some of our other plugins key not found: :14195 org/jruby/RubyHash.java:1189:in `fetch' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:203:in `block in node_from_root' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:193:in `block in node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:105:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:145:in `node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/resource.rb:203:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stanonik, Ronald > Sent: Friday, September 15, 2017 1:44:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I notice a repeating error and stacktrace in the log about an unhandled exception. E, [2017-09-15T09:45:13.168412 #10788] ERROR -- : Thread-5342: Unhandled exception! E, [2017-09-15T09:45:13.168722 #10788] ERROR -- : key not found: : org/jruby/RubyHash.java:1189:in `fetch' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:63:in `root_record' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:22:in `block in add_ancestors' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:12:in `add_ancestors' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/archival_object.rb:69:in `sequel_to_jsonmodel' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:105:in `listing_response' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in `handle_listing' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:95:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' D, [2017-09-15T09:45:13.169154 #10788] DEBUG -- : Thread-5342: Responded with [500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"29"}, ["{\"error\":\"key not found: :\"}\n"]]... in 247ms From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4009 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Fri Sep 22 12:35:06 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Sep 2017 16:35:06 +0000 Subject: [Archivesspace_Users_Group] Top container record corrupted In-Reply-To: References: Message-ID: Hi George, Which version of ArchivesSpace is this in? As I don't think I've heard of this type of situation and no one else has weighed in yet, I'm thinking this might work better as a tech support ticket to figure out the cause. I'm creating one for you and you'll see another message about that directly to you in a minute. It'd be great if you'd share the solution back to the list when you get this resolved. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of George Stanley Kozak Sent: Thursday, September 21, 2017 11:07 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Top container record corrupted Hi, Everyone: Recently, one of our Archivists created a top container record attached to an archival object in ASpace. She then changed the access restriction on the archival object but deleted a sub-note field it expected to have. This gave her the following error: "Sub Notes - translation missing: en.validation_errors.must_contain_at_least_one_subnote". We believe that this corrupted the top container record. When she tried to create a new top container record attached to the same archival object, it was created, but when trying to view the container the "We're sorry, something went wrong" error occurred. I tried to go through the logs to find what exactly happened, but I am having trouble pinpointing where the error occurred in the logs. Has anyone else experienced something similar or has any hints to give us as to what we can do to fix this problem? Thanks! George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Fri Sep 22 12:39:28 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Sep 2017 16:39:28 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: 2.1.2 re-indexing loop In-Reply-To: References: , , Message-ID: Hi Jeremy, I'm definitely going to put a support ticket in for you then. The tech folks can help troubleshoot what's going on overall. You'll see another message about that from me directly in a minute. (And it'd be great if you'd post back to the list when it's resolved.) Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jones, Jeremy Sent: Friday, September 22, 2017 12:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: 2.1.2 re-indexing loop +1 on this... I am getting this index loop as well. I am also not able to view any details of my collections and I am not familiar enough with the program to know which is causing the other or if these issues are independent of each other. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Friday, September 22, 2017 11:16 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop Hi Joshua, I think your issue may be different than Ron's. Ron's appears to have been caused by orphaned instances and archival objects in the database. Earlier versions of ArchivesSpace ignored these during indexing, but 2.1 is more finicky about that. See https://archivesspace.atlassian.net/browse/ANW-220 for some information about that issue. Ron can hopefully share more details about his resolution. I do think your issue may also be specific to your data and local deployment, so it would be worth working through this on a support ticket. You'll see another message about that directly to you in a minute. It would also be great if you'd share the solution back to the list when you get there. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joshua D. Shaw Sent: Friday, September 22, 2017 11:36 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop To add another datapoint, when I change the publish status for all items in a node's immediate tree (ie file-> parent box -> parent series) then the child node and its parents will appear in the staff interface. If the AO or *any* of its ancestors are *not* published, they do *not* appear in the staff interface. I took a quick look at the database and the publish status for *most* of our AOs is "NULL", not the 1 or 0 that large_tree.rb is looking for in published_filter (line 73). I'm currently thinking that our initial custom migration never set that column... Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Joshua D. Shaw > Sent: Thursday, September 21, 2017 4:54:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback I'd love to know the solution as well, since I'm seeing a similar/related(?) error as I'm starting to test 2.1.2 locally. I've migrated from a 1.5.3 instance and see the following error when attempting to view an archival object. The archival object information renders in the record pane, but the tree fails to populate anything except the collection level. I checked the db and the id being referenced (14195) does exist in the archival_object table (I think that's what the id is referencing - assuming I'm reading the code right). This is running with only one plugin (our omniauthCas) plugin enabled, though the database contains some additional tables from some of our other plugins key not found: :14195 org/jruby/RubyHash.java:1189:in `fetch' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:203:in `block in node_from_root' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:193:in `block in node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:105:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/large_tree.rb:145:in `node_from_root' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/resource.rb:203:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /Applications/archivesspace-2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /Applications/archivesspace-2.1.2/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /Applications/archivesspace-2.1.2/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stanonik, Ronald > Sent: Friday, September 15, 2017 1:44:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I notice a repeating error and stacktrace in the log about an unhandled exception. E, [2017-09-15T09:45:13.168412 #10788] ERROR -- : Thread-5342: Unhandled exception! E, [2017-09-15T09:45:13.168722 #10788] ERROR -- : key not found: : org/jruby/RubyHash.java:1189:in `fetch' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:63:in `root_record' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:22:in `block in add_ancestors' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/ancestor_listing.rb:12:in `add_ancestors' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/archival_object.rb:69:in `sequel_to_jsonmodel' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:105:in `listing_response' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in `handle_listing' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:95:in `block in ArchivesSpaceService' org/jruby/RubyBasicObject.java:1687:in `instance_eval' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:280:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111:in `block in open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `block in transaction' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize' /usr/local/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74:in `transaction' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110:in `block in open' org/jruby/RubyFixnum.java:305:in `times' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432:in `block in DB' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:262:in `block in returns' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:230:in `block in returns' org/jruby/RubyMethod.java:111:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block in route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!' org/jruby/RubyArray.java:1734:in `each' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke' org/jruby/RubyKernel.java:1120:in `catch' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call' /usr/local/archivesspace-v2.1.2/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:291:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call' /usr/local/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' uri:classloader:/vendor/rack-1.5.5/rack/nulllogger.rb:9:in `call' uri:classloader:/vendor/rack-1.5.5/rack/head.rb:11:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize' /usr/local/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call' uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:138:in `call' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:65:in `block in call' org/jruby/RubyArray.java:1734:in `each' uri:classloader:/vendor/rack-1.5.5/rack/urlmap.rb:50:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' D, [2017-09-15T09:45:13.169154 #10788] DEBUG -- : Thread-5342: Responded with [500, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"29"}, ["{\"error\":\"key not found: :\"}\n"]]... in 247ms From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald Sent: Friday, September 15, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] 2.1.2 re-indexing loop I recently upgraded to 2.1.2 and it seems to be in an indexing loop. I restarted the application. I removed the solr index and restarted the application. In the log I see it counting up Staff Indexer [2017-09-15 07:42:21 -0700] ~~~ Indexed 185825 of 212959 archival_object records in repository SC&A ... Staff Indexer [2017-09-15 03:50:30 -0700] ~~~ Indexed 201525 of 212959 archival_object records in repository SC&A But then Staff Indexer [2017-09-15 04:09:49 -0700] ~~~ Indexed 25 of 212959 archival_object records in repository SC&A Since yesterday it has re-indexed ten times. The resulting constant re-indexing causes a high load average and slow performance for users. Any suggestions? Thanks, Ron ps. I also posted this question to https://groups.google.com/forum/#!forum/archivesspace. Sorry if that is redundant. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 4009 bytes Desc: image004.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From laney.mcglohon at lyrasis.org Fri Sep 22 12:49:17 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Fri, 22 Sep 2017 16:49:17 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace Message-ID: <3EFE07FD-B05F-4CDD-BBED-5E477384BA2A@lyrasis.org> All, We have identified the issue with the requesting material email and have put a fix into the core code in GitHub: https://github.com/archivesspace/archivesspace/pull/971. So, it will be in the next release, that we are expecting to come out soon. Best, Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: on behalf of Kevin Clair Reply-To: Archivesspace Users Group Date: Thursday, September 21, 2017 at 5:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace We?ve been able to receive the e-mail confirmations ArchivesSpace sends, both with my personal e-mail and with LibAnswers. It?s only when it tries to render request_received_email.html that it throws the error. -k From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Thursday, September 21, 2017 3:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace All, I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case. I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time. Here's what a message would look like that's sent to a patron (as you can see, it doesn?t include ALL of the data, like what the staff would receive), and they shouldn?t see an error message when requesting after everything has been configured to allow email requesting: Thank you for your request Record Requested Title: Watercolor of Brassie fly nymph (fishing fly) URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375 Your Details Name: m Email: mark.custer at yale.edu Date: Notes for Staff: I don?t believe that the email that was sent to staff ever had a specialized template, like this one, however. It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI. Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly. I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I?m not sure why exactly that was or might be). Just so that I?m clear, though? Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received. Is that correct? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Thursday, 21 September, 2017 5:15 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs: INFO: I, [2017-09-21T15:08:03.838360 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600 [the e-mail successfully sends here; log output omitted] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-09-21T15:08:09.740133 #4548] INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#:0x59036603>): Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] 4:

Record Requested

[5c583ccc-1669-40c4-9f90-81f09fac562b] 5: Title: <%= @request.title %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 6: <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 7: URL: <%= link_to url, app_prefix(url) %> [5c583ccc-1669-40c4-9f90-81f09fac562b] 8:
[5c583ccc-1669-40c4-9f90-81f09fac562b] 9: [5c583ccc-1669-40c4-9f90-81f09fac562b] 10:
Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email' [5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request' -k -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Thursday, September 21, 2017 1:19 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace Hello, we recently upgraded from 2.1.1 from 1.5.3. With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request. Is this normal? Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI? Thanks! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From gsk5 at cornell.edu Fri Sep 22 12:53:56 2017 From: gsk5 at cornell.edu (George Stanley Kozak) Date: Fri, 22 Sep 2017 16:53:56 +0000 Subject: [Archivesspace_Users_Group] Top container record corrupted In-Reply-To: References: Message-ID: HI, Christine: Sorry, I should have put that in my original email. We are using v. 2.1.1. Thanks. George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Friday, September 22, 2017 12:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top container record corrupted Hi George, Which version of ArchivesSpace is this in? As I don't think I've heard of this type of situation and no one else has weighed in yet, I'm thinking this might work better as a tech support ticket to figure out the cause. I'm creating one for you and you'll see another message about that directly to you in a minute. It'd be great if you'd share the solution back to the list when you get this resolved. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of George Stanley Kozak Sent: Thursday, September 21, 2017 11:07 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Top container record corrupted Hi, Everyone: Recently, one of our Archivists created a top container record attached to an archival object in ASpace. She then changed the access restriction on the archival object but deleted a sub-note field it expected to have. This gave her the following error: "Sub Notes - translation missing: en.validation_errors.must_contain_at_least_one_subnote". We believe that this corrupted the top container record. When she tried to create a new top container record attached to the same archival object, it was created, but when trying to view the container the "We're sorry, something went wrong" error occurred. I tried to go through the logs to find what exactly happened, but I am having trouble pinpointing where the error occurred in the logs. Has anyone else experienced something similar or has any hints to give us as to what we can do to fix this problem? Thanks! George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4009 bytes Desc: image001.jpg URL: From HurtT at easternct.edu Mon Sep 25 09:04:59 2017 From: HurtT at easternct.edu (Hurt, Tara (Library)) Date: Mon, 25 Sep 2017 13:04:59 +0000 Subject: [Archivesspace_Users_Group] Help With PDF and EAD Export Message-ID: Good morning everyone. I sent a message out last week but my whole message sis not go out, sorry if that was confusing in a call for help. We do need some help. We upgraded to v2.1.2 and we can no longer get a clean PDF Export or a clean EAD Export. Has anyone else had this trouble. Any help you can give would be appreciated. We can add data and work with collections so that is going smoothly But the Exports we need to do are not working. I attached a sample of the very garbled PDF Finding Aid and also a copy Of the EAD that gets outputted, the start is like usual and then garbled text? Thanks so much for any help you can give. Tara Hurt Eastern Connecticut State University hurtt at easterntct.edu 860-465-5563 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Test EAD.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 13212 bytes Desc: Test EAD.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Test PDF .pdf Type: application/pdf Size: 35474 bytes Desc: Test PDF .pdf URL: From mark.custer at yale.edu Mon Sep 25 09:24:42 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 25 Sep 2017 13:24:42 +0000 Subject: [Archivesspace_Users_Group] Help With PDF and EAD Export In-Reply-To: References: Message-ID: Tara, Just a wild guess, but since the EAD file seems to fail while trying to export information about the Repository, can you edit your Repository record and make sure that everything looks okay there? You can edit your Repository in the staff interface by going to System --> Manage Repositories --> click "Edit" next to the repository that's causing an issue. Hopefully that helps, but if not, can you post back what your Repository record looks like? Seeing this, "Universe3nananeq7 iE te w Specialonnllticuons", at the bottom of the PDF file makes it look like some data is corrupted, but whether that's happened in the database or elsewhere, I couldn't say. But since the EAD file cuts off right where the exporter should be adding the URL info for the repository, that seems to be the most likely culprit. If data is there in the Repository record, what happens if you delete it and re-export? Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hurt, Tara (Library) Sent: Monday, 25 September, 2017 9:05 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Help With PDF and EAD Export Good morning everyone. I sent a message out last week but my whole message sis not go out, sorry if that was confusing in a call for help. We do need some help. We upgraded to v2.1.2 and we can no longer get a clean PDF Export or a clean EAD Export. Has anyone else had this trouble. Any help you can give would be appreciated. We can add data and work with collections so that is going smoothly But the Exports we need to do are not working. I attached a sample of the very garbled PDF Finding Aid and also a copy Of the EAD that gets outputted, the start is like usual and then garbled text? Thanks so much for any help you can give. Tara Hurt Eastern Connecticut State University hurtt at easterntct.edu 860-465-5563 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpeterson at smith.edu Mon Sep 25 11:15:19 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Mon, 25 Sep 2017 15:15:19 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> <97D928B6-DA9C-473C-8F67-25401A47C504@lyrasis.org> Message-ID: Hi Jeremy, I just did a local install of ASpace with a copy of our production data for the very first time and was getting similar errors: --- Backtrace RuntimeError: Database connection failed block in ArchivesSpaceService at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101 configure at /Applications/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411 at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78
at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 block in (root) at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/ config.ru:1 instance_eval at org/jruby/RubyBasicObject.java:1687 (root) at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/ config.ru:4
at uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 I did two things, and I'm not sure which was the one that fixed the problem (bad methodology, I know), but one of them did: - make sure that the user account you're using to connect has been granted all privileges (see the example for 'finley' at https://dev.mysql.com/doc/refman/5.7/en/adding-users.html) - make sure that when you downloaded the connector, it was the .jar file that ended up in your /lib directory, and not a directory containing the .jar file plus a bunch of other stuff If you're more patient than I was, you might try to reconnect after each of these and see which (if either) solves the issue. Good luck! Christie Peterson On Tue, Sep 19, 2017 at 4:46 PM Jones, Jeremy wrote: > Hello, > > > > Thanks for the update and suggestion. No, my database is on the same > machine. It?s the same user and permissions that it?s always been. I > commented out the bd_url declaration in the config.rb file and actually got > the thing to start so I?m thinking it has something to do with the app > talking to the database. I?ve got ssl on this machine with a force > rewrite. I didn?t think that would cause any issues but I?m running out of > ideas on this. It?s been a day and a half. Last update took less than 5 > minutes. Lol. > > > > jeremy > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Laney > McGlohon > *Sent:* Tuesday, September 19, 2017 3:31 PM > > > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to > database issue > > > > Hey Jeremy, > > > > I had the same problem on my server. To fix it I had to fix the > permissions of my AS user to the database. > > I had granted permissions for localhost but the mysql server was on a > different machine so I had to grant permissions for that machine. > > Could your mysql database be on a different machine? > > > > Laney > > > > *Laney McGlohon* > > ArchivesSpace Tech Lead > > laney.mcglohon at lyrasis.org > > 800.999.8558 x2927 <(800)%20999-8558> > > laneymcglohon Skype > > > > > > > > *From: * on > behalf of "Jones, Jeremy" > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Tuesday, September 19, 2017 at 3:40 PM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to > database issue > > > > I used 5.1.34 until today then I upgraded to 6.0.6. No luck. > > > > jeremy > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Laney > McGlohon > *Sent:* Tuesday, September 19, 2017 2:38 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to > database issue > > > > Hey Jeremy, > > > > What version of the mysql connector are you using? I have been using > mysql-connector-java-5.1.42-bin.jar. > > > > Laney > > > > > > *Laney McGlohon* > > ArchivesSpace Tech Lead > > laney.mcglohon at lyrasis.org > > 800.999.8558 x2927 <(800)%20999-8558> > > laneymcglohon Skype > > > > > > > > *From: * on > behalf of Jason Loeffler > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Tuesday, September 19, 2017 at 3:22 PM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to > database issue > > > > JRuby is a Java application that reads and runs the Ruby source code. You > don't need to install anything. If rolling back results in the same > connectivity issue, I suspect it is not an ArchivesSpace-specific problem > and is arising from something lower in your stack, likely an issue with > your database server. Re-confirm that your config.rb has the correct > credentials and that you also have the MYSQL connector installed at in your > lib directory. > > > > On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy > wrote: > > Thanks looking into this. I tried going back to version 1.52 and got the > same error. What is jruby and do I need to have it installed on the server? > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jason > Loeffler > *Sent:* Tuesday, September 19, 2017 12:44 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to > database issue > > > > The db connection error is thrown in only one place, in main.rb at lines > 96-102 > . > It's hard to say what may be impeding the connection. I can't think of any > reason the application can't connect, aside from a network issue. Feel free > to contact me offlist if you're unable to resolve the issue. > > > > On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: > > Sure, > > > > The server is centOS 6.9. > > Mysql version 14.14 Distrib 5.1.73 > > Yes I can connect to the database directly using the username and > password. It?s the same combo that I?ve used since AS version 1.2. > > > > This is very strange that this is happening. I?ve never had any problems > including the great migration to get to version 1.5.2. > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jason > Loeffler > *Sent:* Tuesday, September 19, 2017 11:33 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [EXT] Re: [Archivesspace_Users_Group] Failed to connect to > database issue > > > > Hi Jeremy, > > > > Can you include more information about your environment, e.g. server OS > and database server version? Can you connect to the database directly using > your ArchivesSpace username and password as stored in config.rb? > > > Jason Loeffler > > Technology Consultant | The American Academy in Rome > > Minor Science | Application Development & Metadata Strategy > > Brooklyn, New York > > jason at minorscience.com > > (347) 405-0826 > > minorscience (Skype) > > > > > > On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: > > Hello, > > > > I?ve been using Archives Space since version 1.2. I?ve recently upgraded > to version 2.1.2 using the directions included. Now I am getting a > ?Database connection failed? error. I?m using the same mysql connecter > that I used in my version 1.5.2 install and connecting to the same > database. The setup-database.sh script ran with no errors. Here is the > stack trace: > > > > "msg": "Database connection failed", > > "backtrace": [ > > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in > `block in ArchivesSpaceService'", > > > "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in > `configure'", > > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in > `'", > > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in > `
'", > > "org/jruby/RubyKernel.java:961:in `require'", > > > "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in > `require'", > > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in > `block in (root)'", > > "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", > > > "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in > `(root)'", > > "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", > > "launcher/launcher.rb:92:in `start_server'", > > "launcher/launcher.rb:157:in `main'", > > "launcher/launcher.rb:261:in `
'" > > > > > > Any help solving this issue or any insight is appreciated. Thanks in > advance. > > > > jeremy > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- ? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jeremy.Jones at unt.edu Mon Sep 25 11:19:00 2017 From: Jeremy.Jones at unt.edu (Jones, Jeremy) Date: Mon, 25 Sep 2017 15:19:00 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue In-Reply-To: References: <4A17F09A-349E-4D90-97BE-35E84E672C9B@lyrasis.org> <97D928B6-DA9C-473C-8F67-25401A47C504@lyrasis.org> Message-ID: Hello, Thanks for the suggestion. My issue was that I had a database table that had the wrong collation. I had to update the collection for that table and the app started up as usual. Now I?m dealing with a whole new set of problems, lol. Thanks again, jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christie Peterson Sent: Monday, September 25, 2017 10:15 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hi Jeremy, I just did a local install of ASpace with a copy of our production data for the very first time and was getting similar errors: --- Backtrace RuntimeError: Database connection failed block in ArchivesSpaceService at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101 configure at /Applications/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411 at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78
at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38 require at org/jruby/RubyKernel.java:961 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 block in (root) at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1 instance_eval at org/jruby/RubyBasicObject.java:1687 (root) at /Applications/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4
at uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 I did two things, and I'm not sure which was the one that fixed the problem (bad methodology, I know), but one of them did: * make sure that the user account you're using to connect has been granted all privileges (see the example for 'finley' at https://dev.mysql.com/doc/refman/5.7/en/adding-users.html) * make sure that when you downloaded the connector, it was the .jar file that ended up in your /lib directory, and not a directory containing the .jar file plus a bunch of other stuff If you're more patient than I was, you might try to reconnect after each of these and see which (if either) solves the issue. Good luck! Christie Peterson On Tue, Sep 19, 2017 at 4:46 PM Jones, Jeremy > wrote: Hello, Thanks for the update and suggestion. No, my database is on the same machine. It?s the same user and permissions that it?s always been. I commented out the bd_url declaration in the config.rb file and actually got the thing to start so I?m thinking it has something to do with the app talking to the database. I?ve got ssl on this machine with a force rewrite. I didn?t think that would cause any issues but I?m running out of ideas on this. It?s been a day and a half. Last update took less than 5 minutes. Lol. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Tuesday, September 19, 2017 3:31 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hey Jeremy, I had the same problem on my server. To fix it I had to fix the permissions of my AS user to the database. I had granted permissions for localhost but the mysql server was on a different machine so I had to grant permissions for that machine. Could your mysql database be on a different machine? Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: > on behalf of "Jones, Jeremy" > Reply-To: Archivesspace Users Group > Date: Tuesday, September 19, 2017 at 3:40 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue I used 5.1.34 until today then I upgraded to 6.0.6. No luck. jeremy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Tuesday, September 19, 2017 2:38 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue Hey Jeremy, What version of the mysql connector are you using? I have been using mysql-connector-java-5.1.42-bin.jar. Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: > on behalf of Jason Loeffler > Reply-To: Archivesspace Users Group > Date: Tuesday, September 19, 2017 at 3:22 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue JRuby is a Java application that reads and runs the Ruby source code. You don't need to install anything. If rolling back results in the same connectivity issue, I suspect it is not an ArchivesSpace-specific problem and is arising from something lower in your stack, likely an issue with your database server. Re-confirm that your config.rb has the correct credentials and that you also have the MYSQL connector installed at in your lib directory. On Tue, Sep 19, 2017 at 2:20 PM, Jones, Jeremy > wrote: Thanks looking into this. I tried going back to version 1.52 and got the same error. What is jruby and do I need to have it installed on the server? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Failed to connect to database issue The db connection error is thrown in only one place, in main.rb at lines 96-102. It's hard to say what may be impeding the connection. I can't think of any reason the application can't connect, aside from a network issue. Feel free to contact me offlist if you're unable to resolve the issue. On Tue, Sep 19, 2017 at 12:45 PM, Jones, Jeremy > wrote: Sure, The server is centOS 6.9. Mysql version 14.14 Distrib 5.1.73 Yes I can connect to the database directly using the username and password. It?s the same combo that I?ve used since AS version 1.2. This is very strange that this is happening. I?ve never had any problems including the great migration to get to version 1.5.2. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Tuesday, September 19, 2017 11:33 AM To: Archivesspace Users Group > Subject: [EXT] Re: [Archivesspace_Users_Group] Failed to connect to database issue Hi Jeremy, Can you include more information about your environment, e.g. server OS and database server version? Can you connect to the database directly using your ArchivesSpace username and password as stored in config.rb? Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Sep 19, 2017 at 12:20 PM, Jones, Jeremy > wrote: Hello, I?ve been using Archives Space since version 1.2. I?ve recently upgraded to version 2.1.2 using the directions included. Now I am getting a ?Database connection failed? error. I?m using the same mysql connecter that I used in my version 1.5.2 install and connecting to the same database. The setup-database.sh script ran with no errors. Here is the stack trace: "msg": "Database connection failed", "backtrace": [ "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService'", "/var/www/html/archivesspace-2.1.2/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
'", "org/jruby/RubyKernel.java:961:in `require'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)'", "org/jruby/RubyBasicObject.java:1687:in `instance_eval'", "/var/www/html/archivesspace-2.1.2/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'", "uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55:in `
'", "launcher/launcher.rb:92:in `start_server'", "launcher/launcher.rb:157:in `main'", "launcher/launcher.rb:261:in `
'" Any help solving this issue or any insight is appreciated. Thanks in advance. jeremy _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- ? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhughes at library.ucla.edu Mon Sep 25 14:06:28 2017 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Mon, 25 Sep 2017 18:06:28 +0000 Subject: [Archivesspace_Users_Group] Assistance with migrator plugin Message-ID: Hi all, I'm testing a migration from Archivists' Toolkit 2.0.0 update 16 to ArchivesSpace v1.4.2 using the Migration Plugin Version 1.4.2 (10-28-2015). The AT test database (and the production one) is on a database server managed by my IT department. The client is installed on my local PC. After running the migration plugin the error log says: RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: RECORD SAVE ERRORS ( 0 ) :: Running for: 1 min 46.77 sec Current # of Records Copied: Archives Space Data Migrator v1.4.2 (10-28-2015) Simulator True to the above log, no records appear in AS. The inclusion of the word "simulator" in the log seems odd - I've searched the listserv and AS documentation for related information and haven't found anything. Apologies if there's an obvious answer or if this has been previously documented. Any suggestions on things to try or change would be greatly appreciated. Thank you for any assistance! Maggie ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Mon Sep 25 16:56:16 2017 From: smithkr at mit.edu (Kari R Smith) Date: Mon, 25 Sep 2017 20:56:16 +0000 Subject: [Archivesspace_Users_Group] Assistance with migrator plugin In-Reply-To: References: Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01401558FD@OC11expo28.exchange.mit.edu> Hi Margaret, If you contact me off-list I can talk you through our settings for doing this migration (although we did the same last year). In our case, because the two were not on the same machine, we had to enable some extra settings in our SFX tool to bridge the data over the connections. There are others that also have likely suggestions for you too but if my offer is helpful, let me know. Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hughes, Margaret Sent: Monday, September 25, 2017 2:06 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Assistance with migrator plugin Hi all, I'm testing a migration from Archivists' Toolkit 2.0.0 update 16 to ArchivesSpace v1.4.2 using the Migration Plugin Version 1.4.2 (10-28-2015). The AT test database (and the production one) is on a database server managed by my IT department. The client is installed on my local PC. After running the migration plugin the error log says: RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: RECORD SAVE ERRORS ( 0 ) :: Running for: 1 min 46.77 sec Current # of Records Copied: Archives Space Data Migrator v1.4.2 (10-28-2015) Simulator True to the above log, no records appear in AS. The inclusion of the word "simulator" in the log seems odd - I've searched the listserv and AS documentation for related information and haven't found anything. Apologies if there's an obvious answer or if this has been previously documented. Any suggestions on things to try or change would be greatly appreciated. Thank you for any assistance! Maggie ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Sep 26 09:05:01 2017 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 26 Sep 2017 13:05:01 +0000 Subject: [Archivesspace_Users_Group] Archival Objects not showing in the tree - was 2.1.2 re-indexing issue Message-ID: Hey all- Just wanted to let everyone know what the issue was for me and the solution. It turns out that the publish column in the archival objects table allows NULL values. Most of our AOs were NULL in that column. The bit of code that is partially responsible for building the tree (backend/app/model/large_tree.rb) checks for published status (line 74). Its only checking for 0 or 1 in the publish column and so anything that is NULL gets ignored completely - hence the reason why the AOs weren't showing in the tree. I checked this by doing a quick SQL command to convert the NULL values to 0 and re-indexing and the AO's showed as expected. I'll be putting in a JIRA ticket for the bug in large_tree, since it should allow for NULL as the table definition includes that option. Joshua -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Tue Sep 26 16:46:54 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Tue, 26 Sep 2017 20:46:54 +0000 Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? Message-ID: Hi all, Maybe it?s me, but it seems like it?s too easy to scroll way too fast in the ?Collection Organization? tab of the public interface. I don?t think I do anything especially different, but I seem to fly through the inventory, making it nearly impossible to navigate through it or absorb the contents. I use a mac with a touchpad for a mouse, so that could be part of the issue. Anyone else notice this? Lydia From atummino at sunymaritime.edu Wed Sep 27 09:39:59 2017 From: atummino at sunymaritime.edu (Tummino, Annie) Date: Wed, 27 Sep 2017 13:39:59 +0000 Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? In-Reply-To: References: Message-ID: <36364fbfc0fc49e9bc5caaa4bd432a40@EX01.sunymaritime.edu> Yes! I was using a mac laptop and had the same problem!! Now I am trying it on my desktop PC and not having any problems, so it's definitely behaving different based on the device. -- Annie Tummino Stephen B. Luce Library Interim Library Director Archivist & Scholarly Communications Librarian 718-409-7236 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Tuesday, September 26, 2017 4:47 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? Hi all, Maybe it?s me, but it seems like it?s too easy to scroll way too fast in the ?Collection Organization? tab of the public interface. I don?t think I do anything especially different, but I seem to fly through the inventory, making it nearly impossible to navigate through it or absorb the contents. I use a mac with a touchpad for a mouse, so that could be part of the issue. Anyone else notice this? Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From christine.dibella at lyrasis.org Wed Sep 27 11:13:20 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 27 Sep 2017 15:13:20 +0000 Subject: [Archivesspace_Users_Group] question related to AT migration tool update - locations attached to accessions Message-ID: Hello ArchivesSpace members, As mentioned in last week's monthly update, Georgia Tech co-op student Sarah Morrissey is working closely with Laney on various projects, including an update to the Archivists' Toolkit migration tool, to be followed soon afterward by an update to the Archon tool. The aim is to make it possible to migrate data from the last version of each of these systems into the current version of ArchivesSpace. (Currently migration is only supported through ArchivesSpace 1.4.2 and then users must upgrade to later versions of ArchivesSpace from there.) We're really excited about this update but we need your insight to move forward. As you may imagine, one of the more complex pieces of the update is mapping container information from Toolkit to the ArchivesSpace container model. One discrepancy we have found is that Toolkit allowed locations to be linked directly to accessions, with no intervening instances or containers. In ArchivesSpace locations have to be linked to a top container, which is in turn linked to an instance. So locations that were attached directly to accessions in Toolkit need to be translated into instance records, and now into instances with top containers, and then attached to the top container. We're curious how people who used locations with accessions in Toolkit have translated this data into ArchivesSpace to this point. Sarah is analyzing whether there is any way to determine what top containers should be created when, due to the use of locations, there seem to be implied containers linked to accessions. One top container per location? We are thinking the indicator would be something like the accession number plus the location with a sequential "unknown container" or similar. Does anyone have a better suggestion, or want to voice support for that idea? We see there's also an optional Note/Container Information field that is part of the linking information that may be useful in some cases in determining container information, but since it's optional, it wouldn't be there in all cases, and even, if data is present, it may not always provide information that could be used to determine the appropriate top container data. If you used locations with accessions in AT, did you use this note field to record such information? Could it be parsed out into useful container type or indicator information? Thanks for any suggestions and feedback you can provide. And looking ahead to the update of the Archon migration tool, if you have any suggestions for identifying top containers from Archon data, we'd be very interested to have them. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From smithkr at mit.edu Wed Sep 27 12:32:51 2017 From: smithkr at mit.edu (Kari R Smith) Date: Wed, 27 Sep 2017 16:32:51 +0000 Subject: [Archivesspace_Users_Group] Question about Container Profile extents -- use for separate Repos Message-ID: <29F559819ACA9A4FBF208407D4B63ABB014015C869@OC11expo28.exchange.mit.edu> Hi, Is it possible to 1: limit a container profile to one Repo of an instance, or 2: set the default units of a profile to be different in each Repo Our use case: One Repo uses cubic feet and the other uses linear feet. We'd like to distinguish without having a lot of duplicate container profiles showing in our options. Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsteele at jhu.edu Wed Sep 27 12:45:07 2017 From: jsteele at jhu.edu (Jordon Steele) Date: Wed, 27 Sep 2017 16:45:07 +0000 Subject: [Archivesspace_Users_Group] Truncated searches in ASpace PUI Message-ID: <367f9ff3130f471295e8dcc64e881a07@ESGMTWEX6.win.ad.jhu.edu> Hello, We are new users to the PUI and noticed today (correct me if I?m wrong) that neither the old PUI nor the new PUI supports the ability for users to perform truncated searches without truncation operators like * and ?. For example, one must type ?histor*,? with quotes, to get search results containing the word history. One cannot merely type histor with no quotes (0 results). Is this the case? Is there an existing ticket with a request to add this feature? And if this was a conscious decision not to have this feature, may I ask why? Best, Jordon Jordon Steele Hodson Curator of the University Archives Special Collections The Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 410-516-5493 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Monday, April 11, 2016 4:32 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Reference Staff training material? I created something here for staff that addressed some of their questions about using advanced search in the staff interface. A lot of their questions were particular to our local plugins, though, so those probably wouldn?t make much sense to everyone else. However, in case it helps, here are two questions and answers from our current FAQ: 1. How do you truncate your search in ArchivesSpace? You can truncate searches by using an asterisk (*) as a wildcard operator. Using this technique, you can perform truncations on the end of your search as well as the beginning (the left-hand side). For example, you can search for pop* as well as *pop. If doing the latter search, you might wonder if you can filter out all of the results that just contain the string pop in them (e.g. you want records that have lollipop and afropop in their description, but not any with the word pop). Well, of course you can! Just throw in the not operator, and re-run this search: *pop NOT pop (upper-casing the Boolean here is required in our setup), which you can also write as *pop -pop: http://sandbox.archivesspace.org/search?utf8=?&q=*pop+-pop ArchivesSpace uses Solr, which in turn uses Lucene. So, any search operator or technique available with those technologies is likely to be supported by ArchivesSpace (depending on how Solr is configured, which can be customized by every ArchivesSpace installation). 2. Can you put a search in quotes to get results for a specific phrase? You betcha. By default, ArchivesSpace is setup to increase recall for basic searches, so you might want to use quotes to drill down to a more specific result set. Here?s an example: I?m looking for references to the play Cher Antoine. If I put those keywords into the search box without quotes, I?m going to get results that have either Cher or Antoine in them ? only one search term has to match to be considered a match ? but the relevancy ranking will bring most of the results that contain the play?s name to the top. Still, if I don?t want the other results at all, I can wrap up the query in quotes like so: http://sandbox.archivesspace.org search?utf8=?&q=%22cher+antoine%22 (in the above URL, the quote characters are the two instances of %22, which is how double quotes are encoded in URLs) I realize that this isn?t the training information that you asked about, but I just thought I?d share in case it?s of any use. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith Sent: Monday, 11 April, 2016 4:07 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Reference Staff training material? Hello, Has anyone developed local training material for reference archivists? If so, would you be willing to share it? And / or is there official ArchivesSpace community training material for reference archivists? Activities I?m thinking of are like: complex searching in both the staff and public interfaces and producing reports / output that is useful for researchers (like a limited box list, search results, etc.) Thank you! Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Wed Sep 27 13:01:04 2017 From: luftsche at usc.edu (Susan Luftschein) Date: Wed, 27 Sep 2017 17:01:04 +0000 Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? In-Reply-To: References: Message-ID: Hi Lydia, YES! It's a huge problem. It makes demonstrating the tool to patrons very difficult. Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Tuesday, September 26, 2017 1:47 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? Hi all, Maybe it?s me, but it seems like it?s too easy to scroll way too fast in the ?Collection Organization? tab of the public interface. I don?t think I do anything especially different, but I seem to fly through the inventory, making it nearly impossible to navigate through it or absorb the contents. I use a mac with a touchpad for a mouse, so that could be part of the issue. Anyone else notice this? Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=kNZmLW0Un7JxWj76kKwXWUjbE4kk7ztBOZQhZeIFkZI&s=RMmNyK8Rn3mx0Kj_T2r3Mzkm0BdJW790tN-dCxNQUAE&e= From trthorn2 at ncsu.edu Wed Sep 27 13:03:19 2017 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Wed, 27 Sep 2017 13:03:19 -0400 Subject: [Archivesspace_Users_Group] Truncated searches in ASpace PUI In-Reply-To: <367f9ff3130f471295e8dcc64e881a07@ESGMTWEX6.win.ad.jhu.edu> References: <367f9ff3130f471295e8dcc64e881a07@ESGMTWEX6.win.ad.jhu.edu> Message-ID: I think the functionality you're suggesting would have a drastically adverse effect on the precision of the search results. To take an extreme example, say you were searching for records relating to a person with the last name 'Pape' (it's a real name, I looked it up for this purpose). Using 'Pape' as your search query would also return all records that included the word 'Papers', which are likely to be numerous. Even though the exact match would likely be close to the top of the results list, the total set of results would be very large and mostly unrelated to what you were looking for. On Wed, Sep 27, 2017 at 12:45 PM, Jordon Steele wrote: > Hello, > > > > We are new users to the PUI and noticed today (correct me if I?m wrong) > that neither the old PUI nor the new PUI supports the ability for users to > perform truncated searches without truncation operators like * and ?. For > example, one must type ?histor*,? with quotes, to get search results > containing the word history. One cannot merely type histor with no quotes > (0 results). > > > > Is this the case? Is there an existing ticket with a request to add this > feature? And if this was a conscious decision not to have this feature, may > I ask why? > > > > Best, > > > > Jordon > > > > Jordon Steele > > Hodson Curator of the University Archives > > Special Collections > > The Sheridan Libraries > > Johns Hopkins University > > 3400 N Charles St > > Baltimore, MD 21218 > > 410-516-5493 <(410)%20516-5493> > > jsteele at jhu.edu > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Custer, > Mark > *Sent:* Monday, April 11, 2016 4:32 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Reference Staff training > material? > > > > I created something here for staff that addressed some of their questions > about using advanced search in the staff interface. A lot of their > questions were particular to our local plugins, though, so those probably > wouldn?t make much sense to everyone else. However, in case it helps, here > are two questions and answers from our current FAQ: > > > > 1. How do you truncate your search in ArchivesSpace? > > > > You can truncate searches by using an asterisk (*) as a wildcard > operator. Using this technique, you can perform truncations on the end of > your search as well as the beginning (the left-hand side). For example, > you can search for pop* as well as *pop. > > > > If doing the latter search, you might wonder if you can filter out all of > the results that just contain the string pop in them (e.g. you want records > that have lollipop and afropop in their description, but not any with the > word pop). Well, of course you can! Just throw in the not operator, and > re-run this search: *pop NOT pop (upper-casing the Boolean here is > required in our setup), which you can also write as *pop -pop: > > > > *http://sandbox.archivesspace.org/search?utf8= > **?**&q=*pop+-pop * > > > > ArchivesSpace uses Solr, which in turn uses Lucene. So, any search > operator or technique available with those technologies is likely to be > supported by ArchivesSpace (depending on how Solr is configured, which can > be customized by every ArchivesSpace installation). > > > > 2. Can you put a search in quotes to get results for a specific > phrase? > > > > You betcha. By default, ArchivesSpace is setup to increase recall for > basic searches, so you might want to use quotes to drill down to a more > specific result set. > > > > Here?s an example: I?m looking for references to the play Cher Antoine. > If I put those keywords into the search box without quotes, I?m going to > get results that have either Cher or Antoine in them ? only one search term > has to match to be considered a match ? but the relevancy ranking will > bring most of the results that contain the play?s name to the top. Still, > if I don?t want the other results at all, I can wrap up the query in quotes > like so: > > > > *http://sandbox.archivesspace.org search?utf8=?&q=%22cher+antoine%22 > * > > > > (in the above URL, the quote characters are the two instances of %22, > which is how double quotes are encoded in URLs) > > > > I realize that this isn?t the training information that you asked about, > but I just thought I?d share in case it?s of any use. > > > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Kari > R Smith > *Sent:* Monday, 11 April, 2016 4:07 PM > *To:* Archivesspace Users Group (archivesspace_users_group@ > lyralists.lyrasis.org) > *Subject:* [Archivesspace_Users_Group] Reference Staff training material? > > > > Hello, > > Has anyone developed local training material for reference archivists? If > so, would you be willing to share it? And / or is there official > ArchivesSpace community training material for reference archivists? > Activities I?m thinking of are like: complex searching in both the staff > and public interfaces and producing reports / output that is useful for > researchers (like a limited box list, search results, etc.) > > > > Thank you! > > > > Kari R. Smith, Digital Archivist > > MIT Libraries, Institute Archives and Special Collections > > 617-258-5568 <(617)%20258-5568> | smithkr (at) mit.edu > > http://libraries.mit.edu/archives/ > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Wed Sep 27 13:17:31 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Wed, 27 Sep 2017 17:17:31 +0000 Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? In-Reply-To: References: Message-ID: <99E3502A-D634-4ACA-A43B-7E0AB3E227D6@lib.msu.edu> Thanks, Sue and Annie! Sue, were/are you also using a Mac? I created this Jira issue, folks please feel free to edit and add to it. https://archivesspace.atlassian.net/browse/AR-1894 Thanks, Lydia On 9/27/17, 1:01 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Susan Luftschein" wrote: Hi Lydia, YES! It's a huge problem. It makes demonstrating the tool to patrons very difficult. Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Tuesday, September 26, 2017 1:47 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? Hi all, Maybe it?s me, but it seems like it?s too easy to scroll way too fast in the ?Collection Organization? tab of the public interface. I don?t think I do anything especially different, but I seem to fly through the inventory, making it nearly impossible to navigate through it or absorb the contents. I use a mac with a touchpad for a mouse, so that could be part of the issue. Anyone else notice this? Lydia From jsteele at jhu.edu Wed Sep 27 15:02:07 2017 From: jsteele at jhu.edu (Jordon Steele) Date: Wed, 27 Sep 2017 19:02:07 +0000 Subject: [Archivesspace_Users_Group] Truncated searches in ASpace PUI In-Reply-To: References: <367f9ff3130f471295e8dcc64e881a07@ESGMTWEX6.win.ad.jhu.edu> Message-ID: <6e89b2ad615548c59da391d60b89701a@ESGMTWEX6.win.ad.jhu.edu> Thanks, Trevor. Good point. I?m not necessarily recommending it, was just wondering if this had ever been discussed (and if it?s been done formally, if someone could point me to a ticket/PUI redesign documentation where it?s captured that?d be great). Best, Jordon Jordon Steele Hodson Curator of the University Archives Special Collections The Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 410-516-5493 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Trevor Thornton Sent: Wednesday, September 27, 2017 1:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Truncated searches in ASpace PUI I think the functionality you're suggesting would have a drastically adverse effect on the precision of the search results. To take an extreme example, say you were searching for records relating to a person with the last name 'Pape' (it's a real name, I looked it up for this purpose). Using 'Pape' as your search query would also return all records that included the word 'Papers', which are likely to be numerous. Even though the exact match would likely be close to the top of the results list, the total set of results would be very large and mostly unrelated to what you were looking for. On Wed, Sep 27, 2017 at 12:45 PM, Jordon Steele > wrote: Hello, We are new users to the PUI and noticed today (correct me if I?m wrong) that neither the old PUI nor the new PUI supports the ability for users to perform truncated searches without truncation operators like * and ?. For example, one must type ?histor*,? with quotes, to get search results containing the word history. One cannot merely type histor with no quotes (0 results). Is this the case? Is there an existing ticket with a request to add this feature? And if this was a conscious decision not to have this feature, may I ask why? Best, Jordon Jordon Steele Hodson Curator of the University Archives Special Collections The Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 410-516-5493 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Monday, April 11, 2016 4:32 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Reference Staff training material? I created something here for staff that addressed some of their questions about using advanced search in the staff interface. A lot of their questions were particular to our local plugins, though, so those probably wouldn?t make much sense to everyone else. However, in case it helps, here are two questions and answers from our current FAQ: 1. How do you truncate your search in ArchivesSpace? You can truncate searches by using an asterisk (*) as a wildcard operator. Using this technique, you can perform truncations on the end of your search as well as the beginning (the left-hand side). For example, you can search for pop* as well as *pop. If doing the latter search, you might wonder if you can filter out all of the results that just contain the string pop in them (e.g. you want records that have lollipop and afropop in their description, but not any with the word pop). Well, of course you can! Just throw in the not operator, and re-run this search: *pop NOT pop (upper-casing the Boolean here is required in our setup), which you can also write as *pop -pop: http://sandbox.archivesspace.org/search?utf8=?&q=*pop+-pop ArchivesSpace uses Solr, which in turn uses Lucene. So, any search operator or technique available with those technologies is likely to be supported by ArchivesSpace (depending on how Solr is configured, which can be customized by every ArchivesSpace installation). 2. Can you put a search in quotes to get results for a specific phrase? You betcha. By default, ArchivesSpace is setup to increase recall for basic searches, so you might want to use quotes to drill down to a more specific result set. Here?s an example: I?m looking for references to the play Cher Antoine. If I put those keywords into the search box without quotes, I?m going to get results that have either Cher or Antoine in them ? only one search term has to match to be considered a match ? but the relevancy ranking will bring most of the results that contain the play?s name to the top. Still, if I don?t want the other results at all, I can wrap up the query in quotes like so: http://sandbox.archivesspace.org search?utf8=?&q=%22cher+antoine%22 (in the above URL, the quote characters are the two instances of %22, which is how double quotes are encoded in URLs) I realize that this isn?t the training information that you asked about, but I just thought I?d share in case it?s of any use. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith Sent: Monday, 11 April, 2016 4:07 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Reference Staff training material? Hello, Has anyone developed local training material for reference archivists? If so, would you be willing to share it? And / or is there official ArchivesSpace community training material for reference archivists? Activities I?m thinking of are like: complex searching in both the staff and public interfaces and producing reports / output that is useful for researchers (like a limited box list, search results, etc.) Thank you! Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Wed Sep 27 16:51:51 2017 From: luftsche at usc.edu (Susan Luftschein) Date: Wed, 27 Sep 2017 20:51:51 +0000 Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? In-Reply-To: <99E3502A-D634-4ACA-A43B-7E0AB3E227D6@lib.msu.edu> References: <99E3502A-D634-4ACA-A43B-7E0AB3E227D6@lib.msu.edu> Message-ID: Nope, PC. Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Wednesday, September 27, 2017 10:18 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Scrolling too fast in the public interface? Thanks, Sue and Annie! Sue, were/are you also using a Mac? I created this Jira issue, folks please feel free to edit and add to it. https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1894&d=DwIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=Y6LNz6cbswgRpLFCwBuBWXwXKZ7oSF1CpRKzl7ZLrPw&s=NiyWhyO50aclA89LjjbrdhSsIap0QQkhz_6tOcCKXzo&e= Thanks, Lydia On 9/27/17, 1:01 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Susan Luftschein" wrote: Hi Lydia, YES! It's a huge problem. It makes demonstrating the tool to patrons very difficult. Sue Sue Luftschein, Ph.D. Head of Special Collections/Archival & Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Tuesday, September 26, 2017 1:47 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Scrolling too fast in the public interface? Hi all, Maybe it?s me, but it seems like it?s too easy to scroll way too fast in the ?Collection Organization? tab of the public interface. I don?t think I do anything especially different, but I seem to fly through the inventory, making it nearly impossible to navigate through it or absorb the contents. I use a mac with a touchpad for a mouse, so that could be part of the issue. Anyone else notice this? Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=Y6LNz6cbswgRpLFCwBuBWXwXKZ7oSF1CpRKzl7ZLrPw&s=2el_MmGW4RWY4IDWdEaG8Iq-HBXgRIizbEmE-CWSKz4&e= From j at minorscience.com Wed Sep 27 17:08:35 2017 From: j at minorscience.com (Jason Loeffler) Date: Wed, 27 Sep 2017 17:08:35 -0400 Subject: [Archivesspace_Users_Group] Looping indexer of death Message-ID: I'm again seeing what I've dubbed the looping indexer of death. Solr indexer progresses through a repository, emits an opaque error, then bails out and starts from the top of the queue. Gist of log output here . May or may not be related to: https://archivesspace.atlassian.net/browse/ANW-220 Checked the database and didn't catch any orphaned records. Ideas? -- Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Sep 28 11:01:27 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 28 Sep 2017 15:01:27 +0000 Subject: [Archivesspace_Users_Group] Looping indexer of death In-Reply-To: References: Message-ID: Since the error is coming from the indexer calling JSONModel_client, which fetches data from the backend API, you should be able to identify which record is causing the fail by accessing from the backend API with scripts/curl_as I'm guessing that the archival_objects logged in that first line of your log file extract are the ones that completed successfully. So since it's indexing in numerical order, you can try /repositories/7/archival_objects/182770 and above. If you get an error from the backend, you can at least locate the record that's the source of the problem, but if you don't get JSON output from the backend, you may have to look at that record in MySQL or using 'pry' or 'rib' in the backend. If you don't get an error, then it may be from the JSONModel trying to resolve subordinate records and you may have to try accessing children. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Jason Loeffler Sent: Wednesday, September 27, 2017 5:08:35 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Looping indexer of death I'm again seeing what I've dubbed the looping indexer of death. Solr indexer progresses through a repository, emits an opaque error, then bails out and starts from the top of the queue. Gist of log output here. May or may not be related to: https://archivesspace.atlassian.net/browse/ANW-220 Checked the database and didn't catch any orphaned records. Ideas? -- Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgd1 at williams.edu Thu Sep 28 11:12:03 2017 From: jgd1 at williams.edu (Drmacich, Jessika) Date: Thu, 28 Sep 2017 11:12:03 -0400 Subject: [Archivesspace_Users_Group] Ghost identifiers Message-ID: Dear all: A student of ours erased a record from ArchivesSpace. We were able to recover it from a backup. I exported the record from the backup and imported it to the current instance as EAD. However, the identifier is not unique anymore. We temporarily rectified this by adding an asterisk after the identifier. Of course this isn't good practice and I'd like to use the proper number. Has anyone encountered this? I've also experienced this with erased boxes and associated barcodes. Please let me know if you have suggestions. Best, Jessika Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries Special Collections 413-597-4725 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alston.Cobourn at tamucc.edu Thu Sep 28 15:37:15 2017 From: Alston.Cobourn at tamucc.edu (Cobourn, Alston) Date: Thu, 28 Sep 2017 19:37:15 +0000 Subject: [Archivesspace_Users_Group] bulk uploading of Archival Objects via Excel Spreadsheet- how large is too large? Message-ID: I have had success uploading this template in 2.1.2 while testing with just a few rows of data. I now need to upload *for real* a spreadsheet that contains 11,000 rows of data. I tried to load it and got an error message that says "Processing Stopped at Row 0". That seems like a pretty weird error given that Row 0 doesn't exist and that I am able to successfully load a test of several lines of this data, so I'm guessing it is trying to tell me the file is too large. I have now put series 1, which is about 500 rows of data, in its own spreadsheet and am going to try to upload just that. Does anyone have an idea from their own testing how many rows the system can handle processing in one spreadsheet? [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Fox, Bobbi bobbi_fox at harvard.edu Fri Jul 14 16:00:16 EDT 2017 * Previous message: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet * Next message: [Archivesspace_Users_Group] Barcodes Disappearing from Database * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] ________________________________ Hi, VivianLea, Take a look at the template, and see if it meets your needs; you do, however, have to create the Resource, however minimally, in ArchivesSpace somehow (could be interactively, of course!) Cheers, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of VivianLea.Solek at Kofc.Org Sent: Friday, July 14, 2017 3:57 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Hi Bobbi, ...so this would get our raw data from Excel into ASpace without going through an EAD transformation? I'm migrating from an ANCIENT DOS system which I've been able to get out to excel. Once I have that cleaned up, if I and my IT partner can skip the transformation step, that would be beyond fabulous! There are only 15 fields to come over, so it would be very easy to map them to your template. Looking forward to your response, which might make my whole month! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 [Inactive hide details for "Fox, Bobbi" ---07/14/2017 03:44:00 PM---Library Technology Services, which supports the Harvard Libr]"Fox, Bobbi" ---07/14/2017 03:44:00 PM---Library Technology Services, which supports the Harvard Library, is pleased to announce the availabi From: "Fox, Bobbi" >> To: "archivesspace_users_group at lyralists.lyrasis.org>" >>, Date: 07/14/2017 03:44 PM Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org> ________________________________ Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel> . Using the provided spreadsheet template, users can go to a Resource, and either add or insert the set of Archival Objects that have been defined in the spreadsheet. Please note carefully the following paragraph in the README: The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively. Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md> , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template. This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. Cheers, Bobbi Fox, Maintainer _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org> https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GXMnvtV2cyS8rDYQOUdBae-J3_5pKCeySUAi9E3PwPI&s=x7wbsF-0e7H4tdAqlZfuP-j27pCXO_i_JOAwg51LQMs&e= CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 105 bytes Desc: image001.gif URL: ________________________________ * Previous message: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet * Next message: [Archivesspace_Users_Group] Barcodes Disappearing from Database * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] ________________________________ More information about the Archivesspace_Users_Group mailing list Alston Cobourn Processing and Digital Assets Archivist Texas A&M-Corpus Christi Alston.cobourn at tamucc.edu 361-825-2300 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Thu Sep 28 15:51:19 2017 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Thu, 28 Sep 2017 19:51:19 +0000 Subject: [Archivesspace_Users_Group] bulk uploading of Archival Objects via Excel Spreadsheet- how large is too large? In-Reply-To: References: Message-ID: Hi, Someone else who successfully was able to load 12K lines in 1.* ran into the same problem on 2.*. For her, it seemed to be a timeout problem. She found that 5000 lines did work for her. Although she communicated this to me as a comment to another issue I was addressing, I've now created an issue for this: https://github.com/harvard-library/aspace-import-excel/issues/10 I have a co-worker looking into it in his (very limited) spare time, to see if there is some timeout tuning that could happen. TBH, I had no idea that people's spreadsheets were so huge, so didn't test for that. If you want to send me your spreadsheet, we can try to work with it, but I'm not promising immediate results. Cheers, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Cobourn, Alston Sent: Thursday, September 28, 2017 3:37 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] bulk uploading of Archival Objects via Excel Spreadsheet- how large is too large? I have had success uploading this template in 2.1.2 while testing with just a few rows of data. I now need to upload *for real* a spreadsheet that contains 11,000 rows of data. I tried to load it and got an error message that says "Processing Stopped at Row 0". That seems like a pretty weird error given that Row 0 doesn't exist and that I am able to successfully load a test of several lines of this data, so I'm guessing it is trying to tell me the file is too large. I have now put series 1, which is about 500 rows of data, in its own spreadsheet and am going to try to upload just that. Does anyone have an idea from their own testing how many rows the system can handle processing in one spreadsheet? [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Fox, Bobbi bobbi_fox at harvard.edu Fri Jul 14 16:00:16 EDT 2017 * Previous message: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet * Next message: [Archivesspace_Users_Group] Barcodes Disappearing from Database * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] ________________________________ Hi, VivianLea, Take a look at the template, and see if it meets your needs; you do, however, have to create the Resource, however minimally, in ArchivesSpace somehow (could be interactively, of course!) Cheers, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of VivianLea.Solek at Kofc.Org Sent: Friday, July 14, 2017 3:57 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Hi Bobbi, ...so this would get our raw data from Excel into ASpace without going through an EAD transformation? I'm migrating from an ANCIENT DOS system which I've been able to get out to excel. Once I have that cleaned up, if I and my IT partner can skip the transformation step, that would be beyond fabulous! There are only 15 fields to come over, so it would be very easy to map them to your template. Looking forward to your response, which might make my whole month! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 [Inactive hide details for "Fox, Bobbi" ---07/14/2017 03:44:00 PM---Library Technology Services, which supports the Harvard Libr]"Fox, Bobbi" ---07/14/2017 03:44:00 PM---Library Technology Services, which supports the Harvard Library, is pleased to announce the availabi From: "Fox, Bobbi" >> To: "archivesspace_users_group at lyralists.lyrasis.org>" >>, Date: 07/14/2017 03:44 PM Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org> ________________________________ Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel> . Using the provided spreadsheet template, users can go to a Resource, and either add or insert the set of Archival Objects that have been defined in the spreadsheet. Please note carefully the following paragraph in the README: The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively. Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md> , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template. This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. Cheers, Bobbi Fox, Maintainer _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org> https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GXMnvtV2cyS8rDYQOUdBae-J3_5pKCeySUAi9E3PwPI&s=x7wbsF-0e7H4tdAqlZfuP-j27pCXO_i_JOAwg51LQMs&e= CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: > -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 105 bytes Desc: image001.gif URL: > ________________________________ * Previous message: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet * Next message: [Archivesspace_Users_Group] Barcodes Disappearing from Database * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] ________________________________ More information about the Archivesspace_Users_Group mailing list Alston Cobourn Processing and Digital Assets Archivist Texas A&M-Corpus Christi Alston.cobourn at tamucc.edu 361-825-2300 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Fri Sep 29 14:14:58 2017 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Fri, 29 Sep 2017 18:14:58 +0000 Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? Message-ID: Hi, I'm working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my "product owner" is a committee made up of picky(yeah, that's redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running. Has anyone tried this? What incredible munging of the build.xml am I likely to need to do? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: From bthomas at tsl.texas.gov Fri Sep 29 15:47:35 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Fri, 29 Sep 2017 19:47:35 +0000 Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? In-Reply-To: References: Message-ID: Thanks for posting this question. We are also interested in whether this has been done and how. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Fox, Bobbi Sent: Friday, September 29, 2017 1:15 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? Hi, I'm working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my "product owner" is a committee made up of picky(yeah, that's redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running. Has anyone tried this? What incredible munging of the build.xml am I likely to need to do? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From sdm7g at virginia.edu Fri Sep 29 15:57:09 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 29 Sep 2017 19:57:09 +0000 Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? In-Reply-To: References: Message-ID: I haven't tried it (yet) but I'm guessing that you just have to set AppConfig[:enable_*] for all but :enable_public to false, and redirect all of the "http://localhost:port" default settings for AppConfig[:*_url] to point to the remote counterparts. You might also need to set AppConfig[:frontend_proxy_url] That should (in theory) get you a configuration with only public server running, talking to backend, solr and frontend on remote server. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Fox, Bobbi Sent: Friday, September 29, 2017 2:14:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? Hi, I?m working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my ?product owner? is a committee made up of picky(yeah, that?s redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running. Has anyone tried this? What incredible munging of the build.xml am I likely to need to do? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Sep 29 16:09:56 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 29 Sep 2017 20:09:56 +0000 Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? In-Reply-To: References: , Message-ID: Oops: Sorry. I wasn't thinking correctly about running dev mode. The URLs except for the ports are hardwired in build.xml. Looks like it only needs itself and backend URLs. ( No solr ? ) -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Friday, September 29, 2017 3:57:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? I haven't tried it (yet) but I'm guessing that you just have to set AppConfig[:enable_*] for all but :enable_public to false, and redirect all of the "http://localhost:port" default settings for AppConfig[:*_url] to point to the remote counterparts. You might also need to set AppConfig[:frontend_proxy_url] That should (in theory) get you a configuration with only public server running, talking to backend, solr and frontend on remote server. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Fox, Bobbi Sent: Friday, September 29, 2017 2:14:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? Hi, I?m working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my ?product owner? is a committee made up of picky(yeah, that?s redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running. Has anyone tried this? What incredible munging of the build.xml am I likely to need to do? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Sep 29 17:33:51 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 29 Sep 2017 21:33:51 +0000 Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? In-Reply-To: References: , , Message-ID: OK: This seems to work for me: In the public:devserver target of build/build.xml: change -Daspace.config.backend_url= to point to the remote backend server. Solr URL and public_user_secret are set in default_java_options property near the head of that file. It looks like those can also be set from a JAVA_OPTS environment variable. Solr URL should point to the remote solr server, and public_user_secret needs to be set to the same value for both local devserver and in AppConfig[:public_user_secret] on the remote server. Otherwise, you'll get login failures from the local public app being unable to log into the remote backend. With those settings, it appears to be working for me, but I haven't exhaustively tested it. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Friday, September 29, 2017 4:09:56 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? Oops: Sorry. I wasn't thinking correctly about running dev mode. The URLs except for the ports are hardwired in build.xml. Looks like it only needs itself and backend URLs. ( No solr ? ) -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Friday, September 29, 2017 3:57:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? I haven't tried it (yet) but I'm guessing that you just have to set AppConfig[:enable_*] for all but :enable_public to false, and redirect all of the "http://localhost:port" default settings for AppConfig[:*_url] to point to the remote counterparts. You might also need to set AppConfig[:frontend_proxy_url] That should (in theory) get you a configuration with only public server running, talking to backend, solr and frontend on remote server. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Fox, Bobbi Sent: Friday, September 29, 2017 2:14:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server? Hi, I?m working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my ?product owner? is a committee made up of picky(yeah, that?s redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running. Has anyone tried this? What incredible munging of the build.xml am I likely to need to do? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: