Record Requested

Title

URL

Aug 23, 2017 12:42:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T12:42:10.766101 #20482] FATAL -- : [c90e77e0-4387-4281-b38e-a533031ca293] Aug 23, 2017 12:42:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T12:42:10.774380 #20482] FATAL -- : [c90e77e0-4387-4281-b38e-a533031ca293] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb__2099221818_2268' [c90e77e0-4387-4281-b38e-a533031ca293] app/mailers/request_mailer.rb:7:in `request_received_email' [c90e77e0-4387-4281-b38e-a533031ca293] app/controllers/requests_controller.rb:11:in `make_request' Has anyone else encountered anything like this? I tried to fix it using a plugin to replace "app_prefix(url)" with some other link but I couldn't get the plugin to override the original page. Thanks in advance for any help provided! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Aug 23 15:29:39 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 23 Aug 2017 19:29:39 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 In-Reply-To: References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl>, Message-ID: It looks like adding a default arg to the fetch method is also a quick fix: diff --git a/public/app/views/shared/_result.html.erb b/public/app/views/shared/_result.html.erb index 01bfc6c..3434f05 100644 --- a/public/app/views/shared/_result.html.erb +++ b/public/app/views/shared/_result.html.erb @@ -50,7 +50,7 @@ <% result.ancestors.each do |ancestor| %> / - <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> + <%= link_to process_mixed_content(ancestor.fetch('title', '[untitled]')).html_safe, app_prefix(ancestor.fetch('uri')) %> <% end %> <% else %> -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Wednesday, August 23, 2017 1:52:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Neal, Lance: thanks for diagnosing this issue! The PUI search results should definitely still work in this case. We had archival objects in our test corpus with missing titles, so I?m pretty sure that this worked at some point, but it?s definitely not working now, as you?ve noticed. I think the simple fix would be to fall back to the display title if a title doesn?t exist (the display title in ASpace concatenates the title and the first date subrecord together, so in the cases of a missing title, you might wind up with something like ?1880-1889? as the search result link, or the breadcrumb link in the ?Found In? section of the search results). I?ve just added a JIRA ticket to capture this bug: https://archivesspace.atlassian.net/browse/AR-1869 Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Wednesday, 23 August, 2017 1:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi Lance, We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date subrecord but no title. For these records, a search in the new public interface spawns the ?something went wrong? message?from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility. In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a title, any search for terms in that series will also generate the ?something went wrong? search result. We?ve been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the titles gives the broken search result but once the title is entered and saved, the search works. I?ve attached an EAD export of that test resource record (we used unique terms for us, ?AEIOU? and ?fuzzy? so we could pinpoint the test). You?ll see that the series in the EAD export does not have a field. We?ve made the local decision to require title fields for all archival objects. I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles?or the archival object title field made required? Neal -- Neal Harmeyer Digital Archivist Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Wednesday, August 23, 2017 11:55 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hello, We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and possibly others) and other words return results fine. The * wildcard also returns results. Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search. I have attached the logs I think are relevant to the search. Any help would be appreciated. Thanks, , [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #"search_indexer", :login_time=>2017-08-23 10:57:40 -0400, :expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821, :repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title): D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %> [11861f8d-4ed2-494e-93d5-bde230321aec] 51: / [11861f8d-4ed2-494e-93d5-bde230321aec] 52: [11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> [11861f8d-4ed2-494e-93d5-bde230321aec] 54: [11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %> [11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %> Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: as-search.png Type: image/png Size: 482885 bytes Desc: as-search.png URL: From sdm7g at virginia.edu Wed Aug 23 15:56:41 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 23 Aug 2017 19:56:41 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 In-Reply-To: References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl>, , Message-ID: PS to previous note: I initially tried using ancestor display_string as the default, but that failed. Although the ancestor resource has a display_string attribute containing the date, that does not appear to be indexed into the PUI index results returned by search results. So getting that probably requires changes to the indexer as well. ancestor.fetch( 'level' ) did work as alternative default: <%= link_to process_mixed_content(ancestor.fetch('title', ancestor.fetch('level'))).html_safe, app_prefix(ancestor.fetch('uri')) %> -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Wednesday, August 23, 2017 3:29:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 It looks like adding a default arg to the fetch method is also a quick fix: diff --git a/public/app/views/shared/_result.html.erb b/public/app/views/shared/_result.html.erb index 01bfc6c..3434f05 100644 --- a/public/app/views/shared/_result.html.erb +++ b/public/app/views/shared/_result.html.erb @@ -50,7 +50,7 @@ <% result.ancestors.each do |ancestor| %> / - <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> + <%= link_to process_mixed_content(ancestor.fetch('title', '[untitled]')).html_safe, app_prefix(ancestor.fetch('uri')) %> <% end %> <% else %> -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Wednesday, August 23, 2017 1:52:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Neal, Lance: thanks for diagnosing this issue! The PUI search results should definitely still work in this case. We had archival objects in our test corpus with missing titles, so I?m pretty sure that this worked at some point, but it?s definitely not working now, as you?ve noticed. I think the simple fix would be to fall back to the display title if a title doesn?t exist (the display title in ASpace concatenates the title and the first date subrecord together, so in the cases of a missing title, you might wind up with something like ?1880-1889? as the search result link, or the breadcrumb link in the ?Found In? section of the search results). I?ve just added a JIRA ticket to capture this bug: https://archivesspace.atlassian.net/browse/AR-1869 Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Wednesday, 23 August, 2017 1:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi Lance, We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date subrecord but no title. For these records, a search in the new public interface spawns the ?something went wrong? message?from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility. In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a title, any search for terms in that series will also generate the ?something went wrong? search result. We?ve been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the titles gives the broken search result but once the title is entered and saved, the search works. I?ve attached an EAD export of that test resource record (we used unique terms for us, ?AEIOU? and ?fuzzy? so we could pinpoint the test). You?ll see that the series in the EAD export does not have a field. We?ve made the local decision to require title fields for all archival objects. I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles?or the archival object title field made required? Neal -- Neal Harmeyer Digital Archivist Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Wednesday, August 23, 2017 11:55 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hello, We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and possibly others) and other words return results fine. The * wildcard also returns results. Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search. I have attached the logs I think are relevant to the search. Any help would be appreciated. Thanks, , [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #"search_indexer", :login_time=>2017-08-23 10:57:40 -0400, :expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821, :repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title): D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %> [11861f8d-4ed2-494e-93d5-bde230321aec] 51: / [11861f8d-4ed2-494e-93d5-bde230321aec] 52: [11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> [11861f8d-4ed2-494e-93d5-bde230321aec] 54: [11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %> [11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %> Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Aug 23 16:02:45 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 23 Aug 2017 20:02:45 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 In-Reply-To: References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl>, , Message-ID: Ahhh, thanks for figuring that out Steve!!! I'll update the JIRA ticket with this info. 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: Wednesday, 23 August, 2017 3:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 PS to previous note: I initially tried using ancestor display_string as the default, but that failed. Although the ancestor resource has a display_string attribute containing the date, that does not appear to be indexed into the PUI index results returned by search results. So getting that probably requires changes to the indexer as well. ancestor.fetch( 'level' ) did work as alternative default: <%= link_to process_mixed_content(ancestor.fetch('title', ancestor.fetch('level'))).html_safe, app_prefix(ancestor.fetch('uri')) %> -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Wednesday, August 23, 2017 3:29:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 It looks like adding a default arg to the fetch method is also a quick fix: diff --git a/public/app/views/shared/_result.html.erb b/public/app/views/shared/_result.html.erb index 01bfc6c..3434f05 100644 --- a/public/app/views/shared/_result.html.erb +++ b/public/app/views/shared/_result.html.erb @@ -50,7 +50,7 @@ <% result.ancestors.each do |ancestor| %> / - <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> + <%= link_to process_mixed_content(ancestor.fetch('title', '[untitled]')).html_safe, app_prefix(ancestor.fetch('uri')) %> <% end %> <% else %> -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Custer, Mark > Sent: Wednesday, August 23, 2017 1:52:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Neal, Lance: thanks for diagnosing this issue! The PUI search results should definitely still work in this case. We had archival objects in our test corpus with missing titles, so I'm pretty sure that this worked at some point, but it's definitely not working now, as you've noticed. I think the simple fix would be to fall back to the display title if a title doesn't exist (the display title in ASpace concatenates the title and the first date subrecord together, so in the cases of a missing title, you might wind up with something like "1880-1889" as the search result link, or the breadcrumb link in the "Found In" section of the search results). I've just added a JIRA ticket to capture this bug: https://archivesspace.atlassian.net/browse/AR-1869 Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Wednesday, 23 August, 2017 1:18 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi Lance, We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date subrecord but no title. For these records, a search in the new public interface spawns the 'something went wrong' message-from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility. In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a title, any search for terms in that series will also generate the 'something went wrong' search result. We've been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the titles gives the broken search result but once the title is entered and saved, the search works. I've attached an EAD export of that test resource record (we used unique terms for us, 'AEIOU' and 'fuzzy' so we could pinpoint the test). You'll see that the series in the EAD export does not have a field. We've made the local decision to require title fields for all archival objects. I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles-or the archival object title field made required? Neal -- Neal Harmeyer Digital Archivist Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Wednesday, August 23, 2017 11:55 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hello, We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and possibly others) and other words return results fine. The * wildcard also returns results. Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search. I have attached the logs I think are relevant to the search. Any help would be appreciated. Thanks, , [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #"search_indexer", :login_time=>2017-08-23 10:57:40 -0400, :expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821, :repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title): D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %> [11861f8d-4ed2-494e-93d5-bde230321aec] 51: / [11861f8d-4ed2-494e-93d5-bde230321aec] 52: [11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> [11861f8d-4ed2-494e-93d5-bde230321aec] 54: [11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %> [11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %> Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Thu Aug 24 12:08:04 2017 From: smithkr at mit.edu (Kari R Smith) Date: Thu, 24 Aug 2017 16:08:04 +0000 Subject: [Archivesspace_Users_Group] help requested with an error message - missing attribute In-Reply-To: References: <29F559819ACA9A4FBF208407D4B63ABB01344DCE07@OC11expo28.exchange.mit.edu>, Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01344F0E29@OC11expo28.exchange.mit.edu> Thanks Steve and Seth - I did validate the EAD in Oxygen, so that's not the problem. It's a huge file, so I'm going to send you two a link (off list) to it and really appreciate anything you can do to uncover where the error is. 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 Majewski, Steven Dennis (sdm7g) Sent: Thursday, August 17, 2017 12:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Also do a validation of the EAD in oxygen. ASpace will sometimes produce invalid EAD, often caused by glitches handling mixed content / markup in notes, or by mixed published/unpublished content producing empty or missing elements. Most of the errors exporting PDF that I've seen are caused by invalid EAD. ( Although your's is one I haven't seen: If you're still at a loss, please post the EAD and we'll investigate. ) -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Kari R Smith > Sent: Thursday, August 24, 2017 12:08:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Thanks Steve and Seth - I did validate the EAD in Oxygen, so that's not the problem. It's a huge file, so I'm going to send you two a link (off list) to it and really appreciate anything you can do to uncover where the error is. 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 Majewski, Steven Dennis (sdm7g) Sent: Thursday, August 17, 2017 12:36 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Also do a validation of the EAD in oxygen. ASpace will sometimes produce invalid EAD, often caused by glitches handling mixed content / markup in notes, or by mixed published/unpublished content producing empty or missing elements. Most of the errors exporting PDF that I've seen are caused by invalid EAD. ( Although your's is one I haven't seen: If you're still at a loss, please post the EAD and we'll investigate. ) -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Seth Shaw > Sent: Thursday, August 17, 2017 11:33:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Note that the print to PDF process runs the EAD through an XSLT to create an XSL Formatting Objects (XSL-FO) document which is then converted into a PDF. This error may refer to line 3255 your as-ead-pdf.xsl (which lives in the stylesheets subdirectory of the archivesspace home directory), but that seems unlikely if the print to PDF works for other documents, OR the error could be the result of a bad transformation. I would first check the as-ead-pdf.xsl and, if that doesn't seem to be the source, run the EAD through the stylesheet using oXygen and check the output. If none of that turns anything up send along the original EAD and your as-ead-pdf.xsl to see if we can help debug. Good luck! On Thu, Aug 17, 2017 at 6:58 AM, Kari R Smith > wrote: > Hello, > > We are unable to print to PDF a finding aid and I'm having trouble locating > where this error is so I can correct it: > > > > org.apache.fop.fo.ValidationException: null:3255:124: Missing attribute on > fo:basic-link: Either external-destination or internal-destination must be > specified. (See position 3255:124) > > > > I've exported the EAD and at line 3255 there is a name entry. > > I'm looking at the XML in Oxygen and have searched on "fo:basic-link" to no > success. > > > > Thanks in advance! > > > > > > 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 > > > > > _______________________________________________ > 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: image001.jpg Type: image/jpeg Size: 29229 bytes Desc: image001.jpg URL: From livsolis at utexas.edu Thu Aug 24 16:04:44 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Thu, 24 Aug 2017 15:04:44 -0500 Subject: [Archivesspace_Users_Group] location profiles + container profiles Message-ID: Hi all, We at the Briscoe are in the thick of/near the end of migrating legacy data and at long last adopting ArchivesSpace. It appears I had a misunderstanding of how container profiles + location profiles could work together. I had assumed that when you assign all of your boxes/containers container profiles and plot them to a location with a particular location profile (i.e. dimensions) you would be able to identify shelves with free space. After getting some of our data in the system/more monkeying with the sandbox, I see this is not the case. You can identify shelves with no containers (few and far between in our case). But you cannot see how much space is available on a shelf with one or more containers. You can see that the shelf has a number of top containers, but not how many inches remain on a shelf given the range of sizes a top container can have. Our institution is crammed to near maximum capacity. Currently for us, processors can either spend time in the stacks scanning for minimal onsite space to put their recently processed materials, some of which might be a just couple of Hollingers, or just sent them to offsite storage. This being the case I have some questions: 1) Am I just missing something obvious and ASpace can be used to identify shelves with top containers with available space? Based on all documentation I've read, I don't think so, but want a sanity check. 2) Are there any plans to implement location/container management functionality so that container profiles can be used to calculate the space remaining on a shelf with a location profile? 3) This brings up another issue for us. Sometimes, e.g., a bankers box is oriented on the shelf with the long side of the box running parallel with the shelf edge, and other rarer cases the long side is perpendicular to it. If container profile dimensions are used to calculate available shelf space, it would seem I need two separate container profiles for the same box, one for each orientation, each with inverse widths and depths. If not, though, the box would get one profile. I looked at Yale's lovely documentation , which for container profiles states, "Width is the edge of the container that faces out on the shelf." Without the application of container profiles being used to calculate available shelf space, just extents, why would this matter? (Again, the issue might be that I am missing something. See point 1). Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpeterson at smith.edu Fri Aug 25 10:03:08 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Fri, 25 Aug 2017 14:03:08 +0000 Subject: [Archivesspace_Users_Group] Spawning resources Message-ID: Hello everyone, Here at Smith we're currently diving head-first into using ASpace for our accessioning and description workflows, and we're going to be making healthy use of the spawn resource feature. There are some things that do not happen in the spawning process that we would like -- carrying over things like provenance information, machine-actionable restrictions, etc. I searched Jira and didn't see these as open issues. It feels to me like rather than reporting issues one-at-a-time, it might be worthwhile to consider a re-examination of the mapping and spawning, and maybe funding some work to improve this process. Is anyone else already treading this path? Would any organizations like to start thinking and possibly working on this as a community? Thanks all, Christie Peterson Head of Technical Services for Special Collections Smith College -------------- next part -------------- An HTML attachment was scrubbed... URL: From michelsd at union.edu Fri Aug 25 10:19:42 2017 From: michelsd at union.edu (Michelson, Daniel) Date: Fri, 25 Aug 2017 10:19:42 -0400 Subject: [Archivesspace_Users_Group] Spawning resources In-Reply-To: References: Message-ID: Hi Christie, We've run into some of the same issues here at Union College. Another example is that resource records spawned from accessions ignore defaults for new resource records. Presumably some of these have to do with the difficulty of predicting user desires. To use one of your examples, should the Provenance field in the Accessions Module map to the Custodial History Note or the Immediate Source of Acquisition Note? I'm wondering if this type of issue is something within the purview of the new Staff Interface Working Group. Regards, Dan Michelson Historical Records Project Archivist Union College On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson wrote: > Hello everyone, > > Here at Smith we're currently diving head-first into using ASpace for our > accessioning and description workflows, and we're going to be making > healthy use of the spawn resource feature. > > There are some things that do not happen in the spawning process that we > would like -- carrying over things like provenance information, > machine-actionable restrictions, etc. > > I searched Jira and didn't see these as open issues. It feels to me like > rather than reporting issues one-at-a-time, it might be worthwhile to > consider a re-examination of the mapping and spawning, and maybe funding > some work to improve this process. > > Is anyone else already treading this path? Would any organizations like to > start thinking and possibly working on this as a community? > > Thanks all, > > Christie Peterson > Head of Technical Services for Special Collections > Smith College > > _______________________________________________ > 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 adrien_hilton at harvard.edu Fri Aug 25 11:05:02 2017 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Fri, 25 Aug 2017 15:05:02 +0000 Subject: [Archivesspace_Users_Group] Spawning resources In-Reply-To: References: Message-ID: Hi Christie/Dan, I noticed the same thing with spawning accession records, our default resource record template with pre-populated fields was ignored. Given the relatively little amount of data that transfers over, it?s more efficient for us to create a new resource record (from said template) and then link to the accession record. Agreed, a thorough analysis would be nice! Best, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Michelson, Daniel Sent: Friday, August 25, 2017 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Spawning resources Hi Christie, We've run into some of the same issues here at Union College. Another example is that resource records spawned from accessions ignore defaults for new resource records. Presumably some of these have to do with the difficulty of predicting user desires. To use one of your examples, should the Provenance field in the Accessions Module map to the Custodial History Note or the Immediate Source of Acquisition Note? I'm wondering if this type of issue is something within the purview of the new Staff Interface Working Group. Regards, Dan Michelson Historical Records Project Archivist Union College On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson > wrote: Hello everyone, Here at Smith we're currently diving head-first into using ASpace for our accessioning and description workflows, and we're going to be making healthy use of the spawn resource feature. There are some things that do not happen in the spawning process that we would like -- carrying over things like provenance information, machine-actionable restrictions, etc. I searched Jira and didn't see these as open issues. It feels to me like rather than reporting issues one-at-a-time, it might be worthwhile to consider a re-examination of the mapping and spawning, and maybe funding some work to improve this process. Is anyone else already treading this path? Would any organizations like to start thinking and possibly working on this as a community? Thanks all, Christie Peterson Head of Technical Services for Special Collections Smith College _______________________________________________ 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 ltang5 at lib.msu.edu Fri Aug 25 10:49:15 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 25 Aug 2017 14:49:15 +0000 Subject: [Archivesspace_Users_Group] Spawning resources In-Reply-To: References: Message-ID: Hi all, Yes, it would be something for the Staff Interface Enhancement Working Group! Currently, we are still in the early stages of the group, but would be very interested in working with you both (and anyone else), in identifying what can be improved and making recommendations on how it can be improved. This is currently a brainstorm document on new capabilities we?d like to see in the Staff Interface. In there is currently in a very basic form some ideas about treating the default presets for Resources/Accessions as selectable/merge-able templates. You all are welcome to add your ideas or create a JIRA ticket. If you go with the JIRA route, please be sure to tag it with ?staff_interface? Thanks! https://docs.google.com/document/d/1NLTIBOwRrHdztQli2QvcRgr-JAIOXy_5TUXAAR-DRvg/edit?usp=sharing Lydia -- Dr. Lydia Tang, CA, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries From: on behalf of "Michelson, Daniel" Reply-To: Archivesspace Users Group Date: Friday, August 25, 2017 at 10:19 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Spawning resources Hi Christie, We've run into some of the same issues here at Union College. Another example is that resource records spawned from accessions ignore defaults for new resource records. Presumably some of these have to do with the difficulty of predicting user desires. To use one of your examples, should the Provenance field in the Accessions Module map to the Custodial History Note or the Immediate Source of Acquisition Note? I'm wondering if this type of issue is something within the purview of the new Staff Interface Working Group. Regards, Dan Michelson Historical Records Project Archivist Union College On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson > wrote: Hello everyone, Here at Smith we're currently diving head-first into using ASpace for our accessioning and description workflows, and we're going to be making healthy use of the spawn resource feature. There are some things that do not happen in the spawning process that we would like -- carrying over things like provenance information, machine-actionable restrictions, etc. I searched Jira and didn't see these as open issues. It feels to me like rather than reporting issues one-at-a-time, it might be worthwhile to consider a re-examination of the mapping and spawning, and maybe funding some work to improve this process. Is anyone else already treading this path? Would any organizations like to start thinking and possibly working on this as a community? Thanks all, Christie Peterson Head of Technical Services for Special Collections Smith College _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From k-miller3 at northwestern.edu Fri Aug 25 11:20:15 2017 From: k-miller3 at northwestern.edu (Karen Miller) Date: Fri, 25 Aug 2017 15:20:15 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 In-Reply-To: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl> References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl> Message-ID: <0ca3a4566d46473da3fbd0e850f6c07f@evcspmbx05.ads.northwestern.edu> Hi, all. We're having a different problem with archival objects that lack a Title (but include a Date sub-record) not showing up at all in the staff interface. In addition, any siblings (and in some cases cousins as well) do not show up. For example, on our public v1.5 site, the Gwendolen M. Carter papers finding aid has three sub-series (General Correspondence, Letters of Recommendation, and Subject Files) under the second series (Administrative Files): https://findingaids.library.northwestern.edu/repositories/6/resources/18#components If you open the sub-series, you can see that the first two have archival object children that have Dates, but no Titles. The third sub-series (Subject Files) has archival objects with both Titles and Dates. In the v2.1.1 Staff interface, the Administrative Files series shows up, but it has no children. They are present in the MySQL tables and their contents show up in the Container Inventory on the public interface. I added several components under the Administrative Files series in the staff interface and they saved, but they did not show up. I found that any archival object that is added with a Date but no Title will save but not show up in a Resource component tree. In addition, if I save an archival object without a Title and use the +1 button to create a sibling, neither of them display in the component tree. I have not tried RDE to see if that functions differently, but this seems like a pretty big issue as it is. It's not a data issue, it's a display issue - so maybe it will be straightforward to fix? Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Wednesday, August 23, 2017 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi Lance, We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date subrecord but no title. For these records, a search in the new public interface spawns the 'something went wrong' message-from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility. In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a title, any search for terms in that series will also generate the 'something went wrong' search result. We've been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the titles gives the broken search result but once the title is entered and saved, the search works. I've attached an EAD export of that test resource record (we used unique terms for us, 'AEIOU' and 'fuzzy' so we could pinpoint the test). You'll see that the series in the EAD export does not have a field. We've made the local decision to require title fields for all archival objects. I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles-or the archival object title field made required? Neal -- Neal Harmeyer Digital Archivist Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Wednesday, August 23, 2017 11:55 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hello, We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and possibly others) and other words return results fine. The * wildcard also returns results. Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search. I have attached the logs I think are relevant to the search. Any help would be appreciated. Thanks, , [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #"search_indexer", :login_time=>2017-08-23 10:57:40 -0400, :expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821, :repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title): D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %> [11861f8d-4ed2-494e-93d5-bde230321aec] 51: / [11861f8d-4ed2-494e-93d5-bde230321aec] 52: [11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> [11861f8d-4ed2-494e-93d5-bde230321aec] 54: [11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %> [11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %> Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Fri Aug 25 11:51:27 2017 From: k-miller3 at northwestern.edu (Karen Miller) Date: Fri, 25 Aug 2017 15:51:27 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl> Message-ID: <2869dc51ee5f4bc4a47b17ab69b00814@evcspmbx05.ads.northwestern.edu> One more detail about this issue - in the public interface, the untitled archival objects don't display in the component tree along the right side of the page, just like they don't in the staff interface. But if I click on their parent, they do display in the full display that appears in the center of the page, directly under the "Collection Organization" tab. So in the example below, the sub-series "962-1966 Thunderclaps (programs, music)" is clicked open in the component structure on the right hand side, but no archival objects are shown beneath it. However, if the detailed view in the middle of the page, there are 5 archival objects displayed as children of the sub-series, including the culprit at the very bottom, which has no title, but is dated 1966. [cid:image001.jpg at 01D31D90.16C4D1D0] Karen From: Karen Miller Sent: Friday, August 25, 2017 10:19 AM To: Archivesspace Users Group Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi, all. We're having a different problem with archival objects that lack a Title (but include a Date sub-record) not showing up at all in the staff interface. In addition, any siblings (and in some cases cousins as well) do not show up. For example, on our public v1.5 site, the Gwendolen M. Carter papers finding aid has three sub-series (General Correspondence, Letters of Recommendation, and Subject Files) under the second series (Administrative Files): https://findingaids.library.northwestern.edu/repositories/6/resources/18#components If you open the sub-series, you can see that the first two have archival object children that have Dates, but no Titles. The third sub-series (Subject Files) has archival objects with both Titles and Dates. In the v2.1.1 Staff interface, the Administrative Files series shows up, but it has no children. They are present in the MySQL tables and their contents show up in the Container Inventory on the public interface. I added several components under the Administrative Files series in the staff interface and they saved, but they did not show up. I found that any archival object that is added with a Date but no Title will save but not show up in a Resource component tree. In addition, if I save an archival object without a Title and use the +1 button to create a sibling, neither of them display in the component tree. I have not tried RDE to see if that functions differently, but this seems like a pretty big issue as it is. It's not a data issue, it's a display issue - so maybe it will be straightforward to fix? Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Wednesday, August 23, 2017 12:18 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi Lance, We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date subrecord but no title. For these records, a search in the new public interface spawns the 'something went wrong' message-from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility. In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a title, any search for terms in that series will also generate the 'something went wrong' search result. We've been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the titles gives the broken search result but once the title is entered and saved, the search works. I've attached an EAD export of that test resource record (we used unique terms for us, 'AEIOU' and 'fuzzy' so we could pinpoint the test). You'll see that the series in the EAD export does not have a field. We've made the local decision to require title fields for all archival objects. I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles-or the archival object title field made required? Neal -- Neal Harmeyer Digital Archivist Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Wednesday, August 23, 2017 11:55 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hello, We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and possibly others) and other words return results fine. The * wildcard also returns results. Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search. I have attached the logs I think are relevant to the search. Any help would be appreciated. Thanks, , [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #"search_indexer", :login_time=>2017-08-23 10:57:40 -0400, :expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821, :repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title): D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %> [11861f8d-4ed2-494e-93d5-bde230321aec] 51: / [11861f8d-4ed2-494e-93d5-bde230321aec] 52: [11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> [11861f8d-4ed2-494e-93d5-bde230321aec] 54: [11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %> [11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %> Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_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: 120552 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Mon Aug 28 14:27:32 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 28 Aug 2017 18:27:32 +0000 Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 In-Reply-To: <2869dc51ee5f4bc4a47b17ab69b00814@evcspmbx05.ads.northwestern.edu> References: <8560fbdb47134cad93bb0ca5b3a9ce05@wppexc09.purdue.lcl> <2869dc51ee5f4bc4a47b17ab69b00814@evcspmbx05.ads.northwestern.edu> Message-ID: To Karen - Would you mind sending me the EAD for this one for testing purposes? Steve Majewski of UVA has put in a fix that's available now on http://test.archivesspace.org (thanks, Steve!), and Laney is going to look at it a little more to see if we can improve it further. Real examples like yours will definitely help us with that. (And Neal and Lance, I'd be glad for examples from you too, if you have them to share.) To everyone - people have reported a few bugs, including this one and an issue with Windows installs that use a blank MySQL database, that we're hoping to resolve with another small release, possibly later this week. We're still aiming for a bigger release in September that adds new functionality, but for those that need these kinds of fixes sooner, we wanted to let you know that we expect to have something for you soon. Thanks to all who have been working through the recent release and reporting issues. It helps us both with resolving the specific issues and identifying further areas for testing in the future. 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 Karen Miller Sent: Friday, August 25, 2017 11:51 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 One more detail about this issue - in the public interface, the untitled archival objects don't display in the component tree along the right side of the page, just like they don't in the staff interface. But if I click on their parent, they do display in the full display that appears in the center of the page, directly under the "Collection Organization" tab. So in the example below, the sub-series "962-1966 Thunderclaps (programs, music)" is clicked open in the component structure on the right hand side, but no archival objects are shown beneath it. However, if the detailed view in the middle of the page, there are 5 archival objects displayed as children of the sub-series, including the culprit at the very bottom, which has no title, but is dated 1966. [cid:image006.jpg at 01D32009.C3DB73D0] Karen From: Karen Miller Sent: Friday, August 25, 2017 10:19 AM To: Archivesspace Users Group > Subject: RE: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi, all. We're having a different problem with archival objects that lack a Title (but include a Date sub-record) not showing up at all in the staff interface. In addition, any siblings (and in some cases cousins as well) do not show up. For example, on our public v1.5 site, the Gwendolen M. Carter papers finding aid has three sub-series (General Correspondence, Letters of Recommendation, and Subject Files) under the second series (Administrative Files): https://findingaids.library.northwestern.edu/repositories/6/resources/18#components If you open the sub-series, you can see that the first two have archival object children that have Dates, but no Titles. The third sub-series (Subject Files) has archival objects with both Titles and Dates. In the v2.1.1 Staff interface, the Administrative Files series shows up, but it has no children. They are present in the MySQL tables and their contents show up in the Container Inventory on the public interface. I added several components under the Administrative Files series in the staff interface and they saved, but they did not show up. I found that any archival object that is added with a Date but no Title will save but not show up in a Resource component tree. In addition, if I save an archival object without a Title and use the +1 button to create a sibling, neither of them display in the component tree. I have not tried RDE to see if that functions differently, but this seems like a pretty big issue as it is. It's not a data issue, it's a display issue - so maybe it will be straightforward to fix? Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Wednesday, August 23, 2017 12:18 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hi Lance, We've experienced this issue as well, in search results after the move to 2.1. We recently finished some testing on it. Our findings suggest this is directly related to archival objects that possess a date subrecord but no title. For these records, a search in the new public interface spawns the 'something went wrong' message-from our error logs and yours, it looks like the search parameters are looking for titles and when those do not exist, and it breaks the search. Although an archival object title in ASpace is conditionally required when a date subrecord is present, the search does not seem to recognize that flexibility. In addition, it appears when a keyword search is conducted across all record types, and any one of the related archival objects (for example, a sibling or child archival object in a series) does not have a title, any search for terms in that series will also generate the 'something went wrong' search result. We've been able to reproduce this result and repair it. Adding the titles resolved the search error. I also created a simple test record with archival objects that do not possess titles; a search within the titles gives the broken search result but once the title is entered and saved, the search works. I've attached an EAD export of that test resource record (we used unique terms for us, 'AEIOU' and 'fuzzy' so we could pinpoint the test). You'll see that the series in the EAD export does not have a field. We've made the local decision to require title fields for all archival objects. I hope this helps identity trouble areas. Perhaps the public interface search could be updated to work with archival objects lacking titles-or the archival object title field made required? Neal -- Neal Harmeyer Digital Archivist Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Wednesday, August 23, 2017 11:55 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Error when searching in archivesspace v2.1.1 Hello, We have a test instance of archivespace 2.1.1 that is throwing the "Something went wrong" error when a search is performed searching all record types and for a keyword. It is only throwing the error for certain words (ex tree, navy and possibly others) and other words return results fine. The * wildcard also returns results. Our production instance, on archivesspace 1.5.4 does not throw these errors when I do the same search. I have attached the logs I think are relevant to the search. Any help would be appreciated. Thanks, , [2017-08-23T11:48:57.060531 #11297] DEBUG -- : Thread-2022: GET /repositories/9/accessions?all_ids=true&modified_since=1503433821 [session: #"search_indexer", :login_time=>2017-08-23 10:57:40 -0400, :expirable=>false}, @id="35ccdf0821cbc8065adf7f1576eb02e254564cd1484d6cc5dec6c673ae3ba709", @system_mtime=2017-08-23 15:48:27 UTC>] D, [2017-08-23T11:48:57.061902 #11297] DEBUG -- : Thread-2022: Post-processed params: {"all_ids"=>true, "modified_since"=>1503433821, :repo_id=>9} Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.063591 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.064606 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] ActionView::Template::Error (key not found: :title): D, [2017-08-23T11:48:57.066191 #11297] DEBUG -- : Thread-2022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 6ms Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.065756 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] 50: <% result.ancestors.each do |ancestor| %> [11861f8d-4ed2-494e-93d5-bde230321aec] 51: / [11861f8d-4ed2-494e-93d5-bde230321aec] 52: [11861f8d-4ed2-494e-93d5-bde230321aec] 53: <%= link_to process_mixed_content(ancestor.fetch('title')).html_safe, app_prefix(ancestor.fetch('uri')) %> [11861f8d-4ed2-494e-93d5-bde230321aec] 54: [11861f8d-4ed2-494e-93d5-bde230321aec] 55: <% end %> [11861f8d-4ed2-494e-93d5-bde230321aec] 56: <% else %> Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.066453 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] Aug 23, 2017 11:48:57 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-23T11:48:57.067003 #11297] FATAL -- : [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:53:in `block in _app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/shared/_result.html.erb:50:in `_app_views_shared__result_html_erb___496965727_2290' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:72:in `block in _app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/views/search/search_results.html.erb:71:in `_app_views_search_search_results_html_erb___490211956_2278' [11861f8d-4ed2-494e-93d5-bde230321aec] app/controllers/search_controller.rb:59:in `search' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://secure-web.cisco.com/15lWK5VFuWNYU8-dysqpky6CV0tBt-4GGXX7vXdSyYU9KRzp-CuiExj7UOi6znSgQuoHzU_bugQWuB2AhpAoyjk-8HZ_7zXWkpvTrrtiKG9VSeG2Z4UtkxEkMafDFKKmdLWkVH7PocSqfwIt6DzC4FMFo5uN9X1_vHDu_Pcd36-BPZHVDrRxYibxSD5OgpCEOvauD51TSX2pgrdDEdUKOcxDsX1XtcmTkpJ2P28WEorUKVG5yLWdx2gF_MekYRyTJZoUBiDtGJdOm2p8LLuRBCStt4PVbjoBt5SwPrkYWO1B3xEaBMP1dw3P0_QhDbEv8lbuuhadbsK4cp5EKBqAZNiJ4sJFSEEYPQiHaUYCGLCU/http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 141544 bytes Desc: image006.jpg URL: From Henry.Steele at tufts.edu Tue Aug 29 16:12:45 2017 From: Henry.Steele at tufts.edu (Steele, Henry) Date: Tue, 29 Aug 2017 20:12:45 +0000 Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete Message-ID: Good afternoon, I recently updated our dev instance of ArchivesSpace to 2.1.1 for Tufts University Digital Collections & Archives. This patch was in part to address issues with the amount of time it took to re-index. The question we have is how do we know when re-indexing is complete? I look every day in our archivesspace.out log, and I keep seeing entries for "Running index round." I assumed this meant re-indexing was still happening, but I don't know. Is this visible in the solr interface? Any advice on this would be much appreciated. Henry Steele Tufts University Henry.steele at tufts.edu (617)627-5239 -------------- next part -------------- An HTML attachment was scrubbed... URL: From KUTZUBA at hws.edu Tue Aug 29 16:23:00 2017 From: KUTZUBA at hws.edu (Kutzuba, Jamie) Date: Tue, 29 Aug 2017 20:23:00 +0000 Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete In-Reply-To: References: Message-ID: 1+ Thanks- Jamie 315.781.4355 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steele, Henry Sent: Tuesday, August 29, 2017 4:13 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete Good afternoon, I recently updated our dev instance of ArchivesSpace to 2.1.1 for Tufts University Digital Collections & Archives. This patch was in part to address issues with the amount of time it took to re-index. The question we have is how do we know when re-indexing is complete? I look every day in our archivesspace.out log, and I keep seeing entries for "Running index round." I assumed this meant re-indexing was still happening, but I don't know. Is this visible in the solr interface? Any advice on this would be much appreciated. Henry Steele Tufts University Henry.steele at tufts.edu (617)627-5239 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue Aug 29 16:34:08 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 29 Aug 2017 20:34:08 +0000 Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete In-Reply-To: References: Message-ID: You will see the "Running index round" line whenever the indexer checks for any updates to index. When there is nothing new, you'll see an "Index round complete" immediately after, if there is little or no other activity on the server. If there is no other activity, you'll see those lines repeated in the log: Staff Indexer [2017-08-22 16:25:52 -0400] Running index round Staff Indexer [2017-08-22 16:25:53 -0400] Index round complete PUI Indexer [2017-08-22 16:26:08 -0400] Running index round PUI Indexer [2017-08-22 16:26:09 -0400] Index round complete Staff Indexer [2017-08-22 16:26:23 -0400] Running index round Staff Indexer [2017-08-22 16:26:24 -0400] Index round complete PUI Indexer [2017-08-22 16:26:39 -0400] Running index round PUI Indexer [2017-08-22 16:26:40 -0400] Index round complete Staff Indexer [2017-08-22 16:26:54 -0400] Running index round Staff Indexer [2017-08-22 16:26:55 -0400] Index round complete PUI Indexer [2017-08-22 16:27:10 -0400] Running index round PUI Indexer [2017-08-22 16:27:10 -0400] Index round complete When the indexer finds updates to be indexed, you will see additional status lines following the "Running index round" line before "Index round complete" . Staff Indexer [2017-08-22 16:24:50 -0400] Running index round Staff Indexer [2017-08-22 16:24:50 -0400] ~~~ Indexed 2 of 2 digital_object records in repository uva-hs [...] Indexed 2 records in 0 seconds Staff Indexer [2017-08-22 16:24:50 -0400] ~~~ Indexed 25 of 43 top_container records in repository uva-hs Staff Indexer [2017-08-22 16:24:50 -0400] ~~~ Indexed 43 of 43 top_container records in repository uva-hs And depending on your log level, you may have other INFO level lines reporting on update progress. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steele, Henry Sent: Tuesday, August 29, 2017 4:12:45 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete Good afternoon, I recently updated our dev instance of ArchivesSpace to 2.1.1 for Tufts University Digital Collections & Archives. This patch was in part to address issues with the amount of time it took to re-index. The question we have is how do we know when re-indexing is complete? I look every day in our archivesspace.out log, and I keep seeing entries for ?Running index round.? I assumed this meant re-indexing was still happening, but I don?t know. Is this visible in the solr interface? Any advice on this would be much appreciated. Henry Steele Tufts University Henry.steele at tufts.edu (617)627-5239 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jteitelbaum at pabmc.net Wed Aug 30 09:46:55 2017 From: jteitelbaum at pabmc.net (Teitelbaum, Jesse) Date: Wed, 30 Aug 2017 09:46:55 -0400 Subject: [Archivesspace_Users_Group] Finding Aids not showing contents in 2.1.1 Message-ID: We upgraded from 1.5.4 to 2.1.1. In the public interface, I clicked on a collection and when COLLECTION INVENTORY is selected, only the number of boxes appear. No contents. When I click on BOX 1, nothing shows up. Is there something I need to correct in the staff interface in order for the public site to show everything? [cid:image005.jpg at 01D32174.EA903A80] [cid:image006.jpg at 01D32174.EA903A80] Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives [cid:image007.jpg at 01D32174.EA903A80] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 27532 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 21067 bytes Desc: image006.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 1066 bytes Desc: image007.jpg URL: From mark.custer at yale.edu Wed Aug 30 10:01:00 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 30 Aug 2017 14:01:00 +0000 Subject: [Archivesspace_Users_Group] Finding Aids not showing contents in 2.1.1 In-Reply-To: References: Message-ID: Jesse, Could you send me a copy of the EAD file? On the "Container Inventory" page, there may or may not be facets depending on the data. On the actual top-container page in the PUI (i.e. the second screenshot), though, there should be listing of every archival object, resource, and/or accession record that is linked to that top container as long as those link records are published and not suppressed. But if the linked records aren't published or if they are suppressed, then you shouldn't see those archival objects, resources, or accessions anywhere else in the PUI -- do you see them on the "Collection Organization" tab? My first guess would be that the linked components in your second screenshot aren't published, but first guesses don't often grasp all of the important details. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse Sent: Wednesday, 30 August, 2017 9:47 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Finding Aids not showing contents in 2.1.1 We upgraded from 1.5.4 to 2.1.1. In the public interface, I clicked on a collection and when COLLECTION INVENTORY is selected, only the number of boxes appear. No contents. When I click on BOX 1, nothing shows up. Is there something I need to correct in the staff interface in order for the public site to show everything? [cid:image001.jpg at 01D32176.E05990A0] [cid:image002.jpg at 01D32176.E05990A0] Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives [logo-from-http-techmarketingbuffalo-com-facebook-logo-1024_1017] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 27532 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 21067 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1066 bytes Desc: image003.jpg URL: From jteitelbaum at pabmc.net Wed Aug 30 10:31:52 2017 From: jteitelbaum at pabmc.net (Teitelbaum, Jesse) Date: Wed, 30 Aug 2017 10:31:52 -0400 Subject: [Archivesspace_Users_Group] Finding Aids not showing contents in 2.1.1 In-Reply-To: References: Message-ID: Mark, Thanks for the input. Although the records were published in the previous version, they became unpublished in the upgrade. Easy fix. Jesse From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Wednesday, August 30, 2017 10:01 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding Aids not showing contents in 2.1.1 Jesse, Could you send me a copy of the EAD file? On the "Container Inventory" page, there may or may not be facets depending on the data. On the actual top-container page in the PUI (i.e. the second screenshot), though, there should be listing of every archival object, resource, and/or accession record that is linked to that top container as long as those link records are published and not suppressed. But if the linked records aren't published or if they are suppressed, then you shouldn't see those archival objects, resources, or accessions anywhere else in the PUI -- do you see them on the "Collection Organization" tab? My first guess would be that the linked components in your second screenshot aren't published, but first guesses don't often grasp all of the important details. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse Sent: Wednesday, 30 August, 2017 9:47 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Finding Aids not showing contents in 2.1.1 We upgraded from 1.5.4 to 2.1.1. In the public interface, I clicked on a collection and when COLLECTION INVENTORY is selected, only the number of boxes appear. No contents. When I click on BOX 1, nothing shows up. Is there something I need to correct in the staff interface in order for the public site to show everything? [cid:image001.jpg at 01D3217B.31CE6420] [cid:image002.jpg at 01D3217B.31CE6420] Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives [cid:image003.jpg at 01D3217B.31CE6420] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 27532 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 21067 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1066 bytes Desc: image003.jpg URL: From jteitelbaum at pabmc.net Wed Aug 30 10:38:45 2017 From: jteitelbaum at pabmc.net (Teitelbaum, Jesse) Date: Wed, 30 Aug 2017 10:38:45 -0400 Subject: [Archivesspace_Users_Group] Personalize public interface Message-ID: Another question: How do I personalize the main title, "AchivesSpace Public Interface," i.e. change it to the name of my organization? [cid:image001.jpg at 01D3217C.283CA240] Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives [cid:image002.jpg at 01D3217C.283CA240] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 27532 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1069 bytes Desc: image002.jpg URL: From mark.custer at yale.edu Wed Aug 30 10:59:41 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 30 Aug 2017 14:59:41 +0000 Subject: [Archivesspace_Users_Group] Personalize public interface In-Reply-To: References: Message-ID: Jesse, Eventually, I?d love to have all of these options documented with examples on this site: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/66355303/Release+Phase Right now, though, a lot of these common configuration options haven?t been added there yet. Here?s how to make that change with a version of 2.1.x, though: * Open your locales/public/en.yml file * Edit the text there as needed * (not necessary, but a great next step: validate the YML file! Here?s an easy tool online to use, http://www.yamllint.com/ ; if the file isn?t valid (and YML files are picky about spacing), then ASpace won?t start up with the next step) * Restart your ASpace app to see the changes. So, for example, you might have something like this: en: brand: title: Your new title There's a bit more information about how ArchivesSpace uses YML files that you can read online here, https://github.com/archivesspace/archivesspace/blob/master/common/locales/LOCALES_README.md, but that's focused on the staff interface. Still, the idea is the same. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse Sent: Wednesday, 30 August, 2017 10:39 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Personalize public interface Another question: How do I personalize the main title, ?AchivesSpace Public Interface,? i.e. change it to the name of my organization? [cid:image001.jpg at 01D3217B.31CE6420] Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives [logo-from-http-techmarketingbuffalo-com-facebook-logo-1024_1017] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 27532 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1069 bytes Desc: image002.jpg URL: From jteitelbaum at pabmc.net Wed Aug 30 11:26:47 2017 From: jteitelbaum at pabmc.net (Teitelbaum, Jesse) Date: Wed, 30 Aug 2017 11:26:47 -0400 Subject: [Archivesspace_Users_Group] Personalize public interface In-Reply-To: References: Message-ID: Success. Thanks again. Jesse From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Wednesday, August 30, 2017 11:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Personalize public interface Jesse, Eventually, I'd love to have all of these options documented with examples on this site: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/66355303/Release+Phase Right now, though, a lot of these common configuration options haven't been added there yet. Here's how to make that change with a version of 2.1.x, though: * Open your locales/public/en.yml file * Edit the text there as needed * (not necessary, but a great next step: validate the YML file! Here's an easy tool online to use, http://www.yamllint.com/ ; if the file isn't valid (and YML files are picky about spacing), then ASpace won't start up with the next step) * Restart your ASpace app to see the changes. So, for example, you might have something like this: en: brand: title: Your new title There's a bit more information about how ArchivesSpace uses YML files that you can read online here, https://github.com/archivesspace/archivesspace/blob/master/common/locales/LOCALES_README.md, but that's focused on the staff interface. Still, the idea is the same. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Teitelbaum, Jesse Sent: Wednesday, 30 August, 2017 10:39 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Personalize public interface Another question: How do I personalize the main title, "AchivesSpace Public Interface," i.e. change it to the name of my organization? [cid:image001.jpg at 01D32182.DD8803A0] Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives [cid:image002.jpg at 01D32182.DD8803A0] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 27532 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1069 bytes Desc: image002.jpg URL: From a-tippit at northwestern.edu Wed Aug 30 11:40:41 2017 From: a-tippit at northwestern.edu (Alice Elizabeth Tippit) Date: Wed, 30 Aug 2017 15:40:41 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Message-ID: Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the "Print" button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I'd hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else... For interested folks, I've attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice-thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: STAFFjob_136_file_130.pdf.pdf Type: application/pdf Size: 90947 bytes Desc: STAFFjob_136_file_130.pdf.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PUBLICBennett-2.pdf Type: application/pdf Size: 122160 bytes Desc: PUBLICBennett-2.pdf URL: From andrew-holland at uiowa.edu Wed Aug 30 12:00:36 2017 From: andrew-holland at uiowa.edu (Holland, Andrew S) Date: Wed, 30 Aug 2017 16:00:36 +0000 Subject: [Archivesspace_Users_Group] Public View; AS 2.1.1 Message-ID: I'm having a difficult time figuring out why none of our repository content or their resources can be displayed in V 2.1.1. I'm trying to upgrade from 1.5+. Our list of collections will show up but when one is selected, all I see is a screen that says something went wrong and to check the logs. Digital objects, names, subjects and record groups all display fine but the actual collections can't be viewed. I believe this should be a couple of relevant pulls from the logs: Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-08-24T08:26:03.211805 #11229] INFO -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] Rendered shared/_metadata.html.erb (8.2ms) Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-08-24T08:26:03.213361 #11229] INFO -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] Completed 500 Internal Server Error in 151ms Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-24T08:26:03.217166 #11229] FATAL -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-24T08:26:03.217588 #11229] FATAL -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] ActionView::Template::Error (undefined method `[]' for nil:NilClass): Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-24T08:26:03.218187 #11229] FATAL -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] 1: <% if @result && @result.respond_to?(:metadata) %> [5da13b63-2cae-49e1-b001-4e762cc851ec] 2: [5da13b63-2cae-49e1-b001-4e762cc851ec] 3: [5da13b63-2cae-49e1-b001-4e762cc851ec] 6: <% end %> Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-24T08:26:03.218589 #11229] FATAL -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] Aug 24, 2017 8:26:03 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-24T08:26:03.218996 #11229] FATAL -- : [5da13b63-2cae-49e1-b001-4e762cc851ec] app/models/resource.rb:101:in `metadata' [5da13b63-2cae-49e1-b001-4e762cc851ec] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb___2117630061_2294' [5da13b63-2cae-49e1-b001-4e762cc851ec] app/views/layouts/application.html.erb:19:in `_app_views_layouts_application_html_erb___856163347_2292' Aug 30, 2017 10:50:51 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: I, [2017-08-30T10:50:51.877149 #5131] INFO -- : [d1c3c9a7-61eb-446c-a4e9-2ac88390b40b] Completed 500 Internal Server Error in 274ms Aug 30, 2017 10:50:51 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-30T10:50:51.884464 #5131] FATAL -- : [d1c3c9a7-61eb-446c-a4e9-2ac88390b40b] Aug 30, 2017 10:50:51 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-30T10:50:51.885209 #5131] FATAL -- : [d1c3c9a7-61eb-446c-a4e9-2ac88390b40b] NoMethodError (undefined method `[]' for nil:NilClass): Aug 30, 2017 10:50:51 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-30T10:50:51.885610 #5131] FATAL -- : [d1c3c9a7-61eb-446c-a4e9-2ac88390b40b] Aug 30, 2017 10:50:51 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: F, [2017-08-30T10:50:51.886012 #5131] FATAL -- : [d1c3c9a7-61eb-446c-a4e9-2ac88390b40b] app/controllers/repositories_controller.rb:90:in `show' Any help would be appreciated. -Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Wed Aug 30 13:03:07 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 30 Aug 2017 17:03:07 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Annual Report is out! Message-ID: ArchivesSpace is delighted to share our first annual report with you. This digital document (attached) 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! 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. 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: ArchivesSpace-2017-Report-8-29-2017-FINAL.PDF Type: application/pdf Size: 5145666 bytes Desc: ArchivesSpace-2017-Report-8-29-2017-FINAL.PDF URL: From sdm7g at virginia.edu Wed Aug 30 13:09:30 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 30 Aug 2017 17:09:30 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF In-Reply-To: References: Message-ID: The public interface PDF generation appears to be a completely different method from the FOP/xsl based PDF generator in the staff interface. Staff PDF generation: EAD.xml + FOP.xsl -> FOP.xml + [fop-processor] -> PDF The public interface PDF generator is using Java libraries common/lib/core-renderer.jar and common/lib/itext-2.1.7.js2.jar which is generating PDF from XHTML + CSS . So I believe you would want to customize the ERB html templates in: https://github.com/archivesspace/archivesspace/tree/master/public/app/views/pdf I haven't attempted this myself yet, but I would imagine you could override those templates by putting customized copies in plugins/local/public/views/ [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool See also: https://github.com/archivesspace/archivesspace/blob/master/public/app/controllers/pdf_controller.rb [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool https://github.com/archivesspace/archivesspace/blob/master/public/app/models/finding_aid_pdf.rb [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool And: https://flyingsaucerproject.github.io/flyingsaucer/r8/guide/users-guide-R8.html#pdf The Flying Saucer User's Guide - GitHub Pages flyingsaucerproject.github.io The parser is loaded and configured on first use. Normally, we find the default JDK XML parser to work just fine. You may want to alter the XMLReader instance used if ... -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alice Elizabeth Tippit Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I?d hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else? For interested folks, I?ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice?thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Henry.Steele at tufts.edu Wed Aug 30 13:18:55 2017 From: Henry.Steele at tufts.edu (Steele, Henry) Date: Wed, 30 Aug 2017 17:18:55 +0000 Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete In-Reply-To: References: Message-ID: Thank you very much for your response. Looking for the "Indexed # of ##" helped me find where re-indexing stopped, and helped us check on how quickly re-indexing happens. 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: Tuesday, August 29, 2017 4:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] how to know when re-indexing is complete You will see the "Running index round" line whenever the indexer checks for any updates to index. When there is nothing new, you'll see an "Index round complete" immediately after, if there is little or no other activity on the server. If there is no other activity, you'll see those lines repeated in the log: Staff Indexer [2017-08-22 16:25:52 -0400] Running index round Staff Indexer [2017-08-22 16:25:53 -0400] Index round complete PUI Indexer [2017-08-22 16:26:08 -0400] Running index round PUI Indexer [2017-08-22 16:26:09 -0400] Index round complete Staff Indexer [2017-08-22 16:26:23 -0400] Running index round Staff Indexer [2017-08-22 16:26:24 -0400] Index round complete PUI Indexer [2017-08-22 16:26:39 -0400] Running index round PUI Indexer [2017-08-22 16:26:40 -0400] Index round complete Staff Indexer [2017-08-22 16:26:54 -0400] Running index round Staff Indexer [2017-08-22 16:26:55 -0400] Index round complete PUI Indexer [2017-08-22 16:27:10 -0400] Running index round PUI Indexer [2017-08-22 16:27:10 -0400] Index round complete When the indexer finds updates to be indexed, you will see additional status lines following the "Running index round" line before "Index round complete" . Staff Indexer [2017-08-22 16:24:50 -0400] Running index round Staff Indexer [2017-08-22 16:24:50 -0400] ~~~ Indexed 2 of 2 digital_object records in repository uva-hs [...] Indexed 2 records in 0 seconds Staff Indexer [2017-08-22 16:24:50 -0400] ~~~ Indexed 25 of 43 top_container records in repository uva-hs Staff Indexer [2017-08-22 16:24:50 -0400] ~~~ Indexed 43 of 43 top_container records in repository uva-hs And depending on your log level, you may have other INFO level lines reporting on update progress. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Steele, Henry > Sent: Tuesday, August 29, 2017 4:12:45 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] how to know when re-indexing is complete Good afternoon, I recently updated our dev instance of ArchivesSpace to 2.1.1 for Tufts University Digital Collections & Archives. This patch was in part to address issues with the amount of time it took to re-index. The question we have is how do we know when re-indexing is complete? I look every day in our archivesspace.out log, and I keep seeing entries for "Running index round." I assumed this meant re-indexing was still happening, but I don't know. Is this visible in the solr interface? Any advice on this would be much appreciated. Henry Steele Tufts University Henry.steele at tufts.edu (617)627-5239 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Aug 30 13:30:26 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 30 Aug 2017 17:30:26 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF In-Reply-To: References: Message-ID: Alice, all: The new PUI PDF process does *not* use EAD or any XSL that's still used on the staff side. Instead, it takes the data directly from ArchivesSpace, converts it to HTML, and then converts that HTML to PDF. For the ASpace PUI workshop I created a small plugin to illustrate how you can change the image that's added to the front page of the PDF. I haven't had a chance to provide other examples yet (or even to delve too deeply into how the new PDF creation process works), but here is where some of those files live in the ArchivesSpace core code: https://github.com/archivesspace/archivesspace/tree/master/public/app/views/pdf If you follow the model of the "local" plugin that's already provided with ArchivesSpace, here's how you'd change the image on the front page of the PDF: * Add a "public" directory to the local plugin, and add an "assets" subdirectory (for your new image) and a "views" subdirectory (which can be used to override the default behaviors of the PDF process). * In the "assets" directory, add something like "images/logo.png" * In the "view" directory, I added the following: pdf/_header.html.erb. * In that _header.html.erb file, I kept everything the same as what's in the default, aside from this last bit:

As long as you then have the "local" plugin turned on, you can then use this technique to change the default image as well as anything else in the PDF. I hope that helps, and I hope to have this more fully documented soon once it's been explored a bit more. I was actually hoping to re-use the pre-exisitng XSL transformations (primarily since that's what I know!), but I believe that this approach results in PDFs much more quickly, since the EAD file also doesn't have to be generated. The other benefit, which may take a while to show its usefulness, is that you don't need to know EAD or XSLT to update the PDFs. Instead, you need to know a bit about ArchivesSpace and HTML. Please let us know if you're able to change the PDF using this plugin approach or not, and if you have any feedback about it. So far, all that I've done was test that I could change the logo that's used, but it would be great to develop other types of customizations so that those can be shared with the rest of the community. mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alice Elizabeth Tippit Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I?d hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else? For interested folks, I?ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice?thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Aug 30 13:36:49 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 30 Aug 2017 17:36:49 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF In-Reply-To: References: , Message-ID: Steve, Thanks so much for including information about the Java libraries that this new process that the PUI uses, as well as that link to that flying saucer user's guide (it looks like that could be helpful in figuring out how much of CSS3, etc., is supported for creating the PDFs!). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Wednesday, August 30, 2017 1:09:30 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF The public interface PDF generation appears to be a completely different method from the FOP/xsl based PDF generator in the staff interface. Staff PDF generation: EAD.xml + FOP.xsl -> FOP.xml + [fop-processor] -> PDF The public interface PDF generator is using Java libraries common/lib/core-renderer.jar and common/lib/itext-2.1.7.js2.jar which is generating PDF from XHTML + CSS . So I believe you would want to customize the ERB html templates in: https://github.com/archivesspace/archivesspace/tree/master/public/app/views/pdf I haven't attempted this myself yet, but I would imagine you could override those templates by putting customized copies in plugins/local/public/views/ [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool See also: https://github.com/archivesspace/archivesspace/blob/master/public/app/controllers/pdf_controller.rb [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool https://github.com/archivesspace/archivesspace/blob/master/public/app/models/finding_aid_pdf.rb [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool And: https://flyingsaucerproject.github.io/flyingsaucer/r8/guide/users-guide-R8.html#pdf The Flying Saucer User's Guide - GitHub Pages flyingsaucerproject.github.io The parser is loaded and configured on first use. Normally, we find the default JDK XML parser to work just fine. You may want to alter the XMLReader instance used if ... -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alice Elizabeth Tippit Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I?d hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else? For interested folks, I?ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice?thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From a-tippit at northwestern.edu Wed Aug 30 13:40:02 2017 From: a-tippit at northwestern.edu (Alice Elizabeth Tippit) Date: Wed, 30 Aug 2017 17:40:02 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF In-Reply-To: References: , Message-ID: <9d4f60c461c04cd8959f9b15b7ce821f@evcspmbx05.ads.northwestern.edu> Thank you Mark and Steve! Tremendously helpful! I have not had time to try any of your recommendations yet, but based on my previous experience with local plugins it should work. Fingers crossed! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.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: Wednesday, August 30, 2017 12:37 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF Steve, Thanks so much for including information about the Java libraries that this new process that the PUI uses, as well as that link to that flying saucer user's guide (it looks like that could be helpful in figuring out how much of CSS3, etc., is supported for creating the PDFs!). Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Wednesday, August 30, 2017 1:09:30 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF The public interface PDF generation appears to be a completely different method from the FOP/xsl based PDF generator in the staff interface. Staff PDF generation: EAD.xml + FOP.xsl -> FOP.xml + [fop-processor] -> PDF The public interface PDF generator is using Java libraries common/lib/core-renderer.jar and common/lib/itext-2.1.7.js2.jar which is generating PDF from XHTML + CSS . So I believe you would want to customize the ERB html templates in: https://github.com/archivesspace/archivesspace/tree/master/public/app/views/pdf I haven't attempted this myself yet, but I would imagine you could override those templates by putting customized copies in plugins/local/public/views/ [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool See also: https://github.com/archivesspace/archivesspace/blob/master/public/app/controllers/pdf_controller.rb [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool https://github.com/archivesspace/archivesspace/blob/master/public/app/models/finding_aid_pdf.rb [https://avatars0.githubusercontent.com/u/1311559?v=4&s=400] archivesspace/archivesspace github.com archivesspace - The ArchivesSpace archives management tool And: https://flyingsaucerproject.github.io/flyingsaucer/r8/guide/users-guide-R8.html#pdf The Flying Saucer User's Guide - GitHub Pages flyingsaucerproject.github.io The parser is loaded and configured on first use. Normally, we find the default JDK XML parser to work just fine. You may want to alter the XMLReader instance used if ... -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org

> on behalf of Alice Elizabeth Tippit > Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the "Print" button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I'd hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else... For interested folks, I've attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice-thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Aug 30 13:51:42 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 30 Aug 2017 17:51:42 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Message-ID: Alice, all: The new PUI PDF process does *not* use EAD or the as-ead.html.xsl file. Instead, it takes the data directly from ArchivesSpace, converts it to HTML, and then converts that HTML to PDF. For the ASpace PUI workshop I created a small plugin to illustrate how you can change the image that's added to the front page of the PDF. I haven't had a chance to provide other examples yet (or even to delve too deeply into how the new PDF creation process works), but here is where some of those files live in the ArchivesSpace core code: https://github.com/archivesspace/archivesspace/tree/master/public/app/views/pdf If you follow the model of the "local" plugin that's already provided with ArchivesSpace, here's how you'd change the image on the front page of the PDF: * Add a "public" directory to the local plugin, and add an "assets" subdirectory (for your new image) and a "views" subdirectory (which can be used to override the default behaviors of the PDF process). * In the "assets" directory, add something like "images/logo.png" * In the "view" directory, I added the following: pdf/_header.html.erb. * In that _header.html.erb file, I kept everything the same as what's in the default file, aside from this last bit:

<%= image_tag( record.resolved_repository['image_url'] || asset_url("Aspace-logo.png") ) %>

-- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Wednesday, August 30, 2017 1:51:42 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF Alice, all: The new PUI PDF process does *not* use EAD or the as-ead.html.xsl file. Instead, it takes the data directly from ArchivesSpace, converts it to HTML, and then converts that HTML to PDF. For the ASpace PUI workshop I created a small plugin to illustrate how you can change the image that's added to the front page of the PDF. I haven't had a chance to provide other examples yet (or even to delve too deeply into how the new PDF creation process works), but here is where some of those files live in the ArchivesSpace core code: https://github.com/archivesspace/archivesspace/tree/master/public/app/views/pdf If you follow the model of the "local" plugin that's already provided with ArchivesSpace, here's how you'd change the image on the front page of the PDF: * Add a "public" directory to the local plugin, and add an "assets" subdirectory (for your new image) and a "views" subdirectory (which can be used to override the default behaviors of the PDF process). * In the "assets" directory, add something like "images/logo.png" * In the "view" directory, I added the following: pdf/_header.html.erb. * In that _header.html.erb file, I kept everything the same as what's in the default file, aside from this last bit:

<%= image_tag( record.resolved_repository['image_url'] || asset_url("Aspace-logo.png") ) %>

As long as you then have the "local" plugin turned on, you can then use this technique to change the default image as well as anything else in the PDF. I hope that helps, and I hope to have this more fully documented soon once it's been explored a bit more. I was actually hoping to re-use the pre-exisitng XSL transformations (primarily since that's what I know!), but I believe that this approach results in PDFs much more quickly, since the EAD file also doesn't have to be generated. The other benefit, which may take a while to show its usefulness, is that you don't need to know EAD or XSLT to update the PUI PDFs. Instead, you need to know a bit about ArchivesSpace and HTML (and lots more people know about HTML than know about EAD or XSLT). Please let us know if you're able to change the PDF using this plugin approach or not, and if you have any feedback about it. So far, all that I've done was test that I could change the logo that's used, but it would be great to develop other types of customizations so that those can be shared with the rest of the community. mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alice Elizabeth Tippit Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I?d hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else? For interested folks, I?ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice?thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Aug 30 15:15:00 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 30 Aug 2017 19:15:00 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF In-Reply-To: References: Message-ID: It looks like most of the difference in number of pages is just due to whitespace and font size used and not to any more information in the document. It would be nice to tweak these and get back to a more compact format. I think 'preferred citation' was also missing from public PDF. > When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alice Elizabeth Tippit Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I?d hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else? For interested folks, I?ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice?thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Wed Aug 30 16:24:51 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Wed, 30 Aug 2017 20:24:51 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Message-ID: <2DEF4293-81C4-40F2-AB8D-668CFCDE3D09@lib.msu.edu> Hear, hear! ? Many of our finding aids dramatically expanded in printing length and it would be wonderful to see the PDFs become more compact. Lydia From: on behalf of "Majewski, Steven Dennis (sdm7g)" Reply-To: Archivesspace Users Group Date: Wednesday, August 30, 2017 at 3:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF It looks like most of the difference in number of pages is just due to whitespace and font size used and not to any more information in the document. It would be nice to tweak these and get back to a more compact format. I think 'preferred citation' was also missing from public PDF. > When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alice Elizabeth Tippit Sent: Wednesday, August 30, 2017 11:40:41 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF Greetings all, We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files. When the ?Print? button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful table of contents and has formatting that produces a document that is twice the number of pages. Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin: >PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL< Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I?d hope for something better than the PDF that currently generates on the public site. Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect. Are we chasing the wrong file, or placing it in the wrong location? Or something else? For interested folks, I?ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface. Any advice?thank you! Alice Tippit Developer-Metadata & Discovery Services Northwestern University Library Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu a-tippit at northwestern.edu From sdm7g at virginia.edu Wed Aug 30 16:48:27 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 30 Aug 2017 20:48:27 +0000 Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF In-Reply-To: References: , , Message-ID: Looks like some CSS mods are also required to adjust for logo size. First repo logo I tried looked good, but the 2nd one I tried caused the repo information at the bottom of titlepage to push down to the next page. But yes, If we can make that a bit more robust, it would make a better default. -- Steve Majewski / UVA Alderman Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Wednesday, August 30, 2017 2:59:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF Steve, that's excellent. In fact, that should probably just get added to the core code, I'd think! ? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Wednesday, August 30, 2017 2:17:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizing the Public Interface PDF Thanks, Mark. I gave this a try and verified that it worked added to plugins/local/public/views/pdf/_header.html.erb We have different logos for different repositories. If you add the logos to the repository branding image url, this pulls that image url:

<%= image_tag( record.resolved_repository['image_url'] || asset_url("Aspace-logo.png") ) %>

Message-ID: I'm a little bit late to the party here - typical - but this is something I've thought about too. Our accessioning workflow involves the creation of both an accession and resource record for new collections. We still use the spawning feature because of the information it does automatically carry over (Title, extent, dates, scope and content note, agents and subjects) but I'd be keen to see some of the specifics you mention, Christie. I think the spawning functionality provides a concrete application for iterative and extensible workflows, and a way to show how we can create archival description at many different points along the way, so I'd like to make the most of that. I'd be happy to talk further about this as well - thanks for raising the issue. Best, Rachel On Fri, Aug 25, 2017 at 10:49 AM, Tang, Lydia wrote: > Hi all, > Yes, it would be something for the Staff Interface Enhancement Working > Group! Currently, we are still in the early stages of the group, but would > be very interested in working with you both (and anyone else), in > identifying what can be improved and making recommendations on how it can > be improved. > This is currently a brainstorm document on new capabilities we?d like to > see in the Staff Interface. In there is currently in a very basic form > some ideas about treating the default presets for Resources/Accessions as > selectable/merge-able templates. You all are welcome to add your ideas or > create a JIRA ticket. If you go with the JIRA route, please be sure to tag > it with ?staff_interface? Thanks! > https://docs.google.com/document/d/1NLTIBOwRrHdztQli2QvcRgr- > JAIOXy_5TUXAAR-DRvg/edit?usp=sharing > Lydia > -- > Dr. Lydia Tang, CA, DMA, MLIS > Special Collections Archivist-Librarian > Philosophy, Aesthetics, and Ethics Bibliographer > Michigan State University Libraries > > From: on behalf > of "Michelson, Daniel" > Reply-To: Archivesspace Users Group lyralists.lyrasis.org> > Date: Friday, August 25, 2017 at 10:19 AM > To: Archivesspace Users Group lyralists.lyrasis.org> > Subject: Re: [Archivesspace_Users_Group] Spawning resources > > Hi Christie, > We've run into some of the same issues here at Union College. Another > example is that resource records spawned from accessions ignore defaults > for new resource records. > Presumably some of these have to do with the difficulty of predicting user > desires. To use one of your examples, should the Provenance field in the > Accessions Module map to the Custodial History Note or the Immediate Source > of Acquisition Note? > > I'm wondering if this type of issue is something within the purview of the > new Staff Interface Working Group. > Regards, > > Dan Michelson > Historical Records Project Archivist > Union College > > On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson > wrote: > Hello everyone, > > Here at Smith we're currently diving head-first into using ASpace for our > accessioning and description workflows, and we're going to be making > healthy use of the spawn resource feature. > > There are some things that do not happen in the spawning process that we > would like -- carrying over things like provenance information, > machine-actionable restrictions, etc. > > I searched Jira and didn't see these as open issues. It feels to me like > rather than reporting issues one-at-a-time, it might be worthwhile to > consider a re-examination of the mapping and spawning, and maybe funding > some work to improve this process. > > Is anyone else already treading this path? Would any organizations like to > start thinking and possibly working on this as a community? > > Thanks all, > > Christie Peterson > Head of Technical Services for Special Collections > Smith College > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org rchivesspace_Users_Group at lyralists.lyrasis.org> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group< > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists. > lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup& > d=DwMFaQ&c=nE__W8dFE-shTxStwXtp0A&r=M5PgloWvPMrr8ldOateLlQ&m= > IikwWiUDD0nHvGEphQIA-2XSNnaM5GSjFxg8YhAEdnE&s=Ub7nh7aL3qsx32xz1MBX3_bIH7_ > 1P2CsvD4cG434924&e=> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: