From christine.dibella at lyrasis.org Mon Apr 1 08:00:14 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 1 Apr 2019 12:00:14 +0000 Subject: [Archivesspace_Users_Group] open call on ArchivesSpace reports - Wednesday, April 3 at 1:00 p.m. EDT / 10 a.m. PDT Message-ID: Please join the Reports sub-team of the ArchivesSpace User Advisory Council this Wednesday, April 3, at 1:00 EDT / 10 a.m. PDT for an open call on reports. The Reports sub-team is interested in learning about the community's use of the existing reports, use cases, and pain points. The sub-team will use this feedback to inform their next steps. Some questions and discussion items are posted on the wiki page for the call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call. Feel free to add more by using the comments section on the page. Connection information is provided below. If you have any questions, please contact Alston Cobourn, Reports sub-team leader (cobourna18 at ecu.edu), or me. We hope to see a number of you there! Connection information: https://zoom.us/j/926134522 Dial by your location (if you cannot connect to the audio with your computer) +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) Meeting ID: 926 134 522 Find your local number: https://zoom.us/u/abY0PUiwRs -------------- next part -------------- An HTML attachment was scrubbed... URL: From racheltrent at gwu.edu Mon Apr 1 09:35:17 2019 From: racheltrent at gwu.edu (Rachel Trent) Date: Mon, 1 Apr 2019 09:35:17 -0400 Subject: [Archivesspace_Users_Group] Digitization Work Order plugin + ASpace v 2.5.2 Message-ID: Good morning, I was wondering if anyone might have had any luck installing the Digitization Work Order plugin ( https://github.com/hudmol/digitization_work_order) on ArchivesSpace version 2.5.2. We saw that Tufts, NYU, and perhaps some others have had success with installing on version 2.5.1 (thanks Henry and Rachel for your thread back in January!). We've tried installing the plugin on our 2.5.2 instance, but ASpace won't restart afterwards. Looking at the logs, I see it loads the configuration file, attempts a thread dump, and then hits a server error. It keeps retrying and re-hitting the error. Anyone else have luck (or not have luck) on 2.5.2? Thanks! Rachel Rachel Trent Digital Services Manager Special Collections Research Center Gelman Library, George Washington University 2130 H Street NW Washington DC 20052 202.994.4824 racheltrent at gwu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Apr 3 17:18:35 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 3 Apr 2019 21:18:35 +0000 Subject: [Archivesspace_Users_Group] FYI: Custom reports Message-ID: Followup to my comments on todays Reports call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom , but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) I found it was quite easy to add one of these custom sub reports to existing reports. We wanted to add the collections_management_subreport to the resources_list_report and the accession_report. This was a pretty trivial set of changes to implement: https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports.patch And if some of the proper defaults like additions to the locales files were added to the distribution, it would have been only two one-line additions. Adds these fields to the reports if a collection management record exists: collection_management_subreport: processing_funding_source: Funding Source processing_hours_total: Total Hours processing_plan: Processing Plan processing_priority: Processing Priority processing_status: Processing Status processors: Processors rights_determined: Rights Determined? Reports, like plugins, do not require a new build: you can just drop modified reports into archivesspace/reports/ directories and restart to take effect. We have also added a custom report on users and permission groups, which is very handy due to the limited staff web app view of users. I?ve submitted a pull request to add this to the next release. https://github.com/archivesspace/archivesspace/pull/1502 https://github.com/archivesspace/archivesspace/pull/1502/files ? Steve Majewski -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From Hilary.Clifford at aidshealth.org Thu Apr 4 13:06:15 2019 From: Hilary.Clifford at aidshealth.org (Hilary Clifford) Date: Thu, 4 Apr 2019 17:06:15 +0000 Subject: [Archivesspace_Users_Group] Video Length Metadata Message-ID: <6E036E39-29C5-41E5-B119-E56BD390EE97@aidshealth.org> Good morning (or afternoon, depending on where you are), I was wondering if anyone else came across this issue: In our collection we have many videos where the length of time of the video is important information. However, there is no field to add the length of the videos in ArchivesSpace. Extent wouldn?t work, as it is the physical size of the collection (in boxes or gigabytes etc) whereas I?m looking to have the length of time for the individual videos. How are other archives handling this type of metadata? Thanks so much! Hilary Clifford AIDS Healthcare Foundation Senior Program Manager of Archives Public Health Division 1710 N La Brea Ave Los Angeles, CA 90046 323-436-8900 ext. 5844 Cell: 323-219-8613 [/Users/archive/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1607367186] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 293391 bytes Desc: image001.png URL: From Kevin.Clair at du.edu Thu Apr 4 13:19:33 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 4 Apr 2019 17:19:33 +0000 Subject: [Archivesspace_Users_Group] Video Length Metadata Message-ID: Hello, When we?ve recorded it, it?s been in the Dimensions field of the Extent section of the record, like here: https://duarchives.coalliance.org/repositories/2/archival_objects/29427 Here?s how it looks in the staff interface: [cid:image001.png at 01D4EAD8.46FA47B0] cheers, -k From: on behalf of Hilary Clifford Reply-To: Archivesspace Group Date: Thursday, April 4, 2019 at 11:06 AM To: Archivesspace Group , LYRASIS Subject: [Archivesspace_Users_Group] Video Length Metadata Good morning (or afternoon, depending on where you are), I was wondering if anyone else came across this issue: In our collection we have many videos where the length of time of the video is important information. However, there is no field to add the length of the videos in ArchivesSpace. Extent wouldn?t work, as it is the physical size of the collection (in boxes or gigabytes etc) whereas I?m looking to have the length of time for the individual videos. How are other archives handling this type of metadata? Thanks so much! Hilary Clifford AIDS Healthcare Foundation Senior Program Manager of Archives Public Health Division 1710 N La Brea Ave Los Angeles, CA 90046 323-436-8900 ext. 5844 Cell: 323-219-8613 [/Users/archive/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1607367186] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 78313 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 293392 bytes Desc: image002.png URL: From cap166 at georgetown.edu Thu Apr 4 13:20:25 2019 From: cap166 at georgetown.edu (Carole Prietto) Date: Thu, 4 Apr 2019 13:20:25 -0400 Subject: [Archivesspace_Users_Group] Video Length Metadata In-Reply-To: <6E036E39-29C5-41E5-B119-E56BD390EE97@aidshealth.org> References: <6E036E39-29C5-41E5-B119-E56BD390EE97@aidshealth.org> Message-ID: When I look at the dropdown menu for Extent, audiocassette and reel are among the choices. Is is possible to add options for the different audio/video formats you have? "Reel" seems much too generic for all the different audio and video formats that are out there. I would prefer to specify the exact format: Audio CD or VHS or 3/4" U-Matic or Mini-DV cassette or what have you. Very interested in others' take on this, as we are planning for a finding aid for a very large AV collection with many formats represented. Carole Prietto, MLIS, CA | Law Center Archivist GEORGETOWN LAW | cap166 at georgetown.edu Edward Bennett Williams Law Library 111 G. St. NW | Washington, D.C. 20001-2015 Office: 202.662.9149 | Fax: 202.662.9911 On Thu, Apr 4, 2019 at 1:06 PM Hilary Clifford < Hilary.Clifford at aidshealth.org> wrote: > Good morning (or afternoon, depending on where you are), > > > > I was wondering if anyone else came across this issue: > > > > In our collection we have many videos where the length of time of the > video is important information. However, there is no field to add the > length of the videos in ArchivesSpace. Extent wouldn?t work, as it is the > physical size of the collection (in boxes or gigabytes etc) whereas I?m > looking to have the length of time for the individual videos. > > > > How are other archives handling this type of metadata? > > > > Thanks so much! > > > > Hilary Clifford > > AIDS Healthcare Foundation > > Senior Program Manager of Archives > > Public Health Division > > 1710 N La Brea Ave > > Los Angeles, CA 90046 > > 323-436-8900 ext. 5844 > > Cell: 323-219-8613 > > [image: > /Users/archive/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1607367186] > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 293391 bytes Desc: not available URL: From mark.custer at yale.edu Thu Apr 4 13:25:28 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 4 Apr 2019 17:25:28 +0000 Subject: [Archivesspace_Users_Group] Video Length Metadata In-Reply-To: <6E036E39-29C5-41E5-B119-E56BD390EE97@aidshealth.org> References: <6E036E39-29C5-41E5-B119-E56BD390EE97@aidshealth.org> Message-ID: Hi Hilary, You can apply extent subrecords at any level of description in ArchivesSpace. Although we still need to add some translation values (as you?ll no doubt notice if you click on the following link), I?ll point you to an example of a single U-matic tape that?s in one of the Beinecke finding aids: https://archives.yale.edu/repositories/11/archival_objects/610224 * Although we could store this information in a dimensions note or elsewhere, we?ve gone with the option of putting it into an extent statement since it was desired to keep this information as structured (and machine-actionable) as possible. And to do that, we added the following extent type to the extent type controlled value list, which you can do directly in the staff interface: duration_HH:MM:SS.mmm For a lot of use cases, though, I?d assume that separating out the duration into its own field would not be needed. I?m also curious how others are handling this type of information in ArchivesSpace. Mark * the display looks a bit better in our PDF: Rules of the Game, Act 1 Call Number: YCALMSS421_0001 1 Videocassette (U-matic) duration: 01:02:45 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hilary Clifford Sent: Thursday, 04 April, 2019 1:06 PM To: Archivesspace Users Group ; LYRASIS Subject: [Archivesspace_Users_Group] Video Length Metadata Good morning (or afternoon, depending on where you are), I was wondering if anyone else came across this issue: In our collection we have many videos where the length of time of the video is important information. However, there is no field to add the length of the videos in ArchivesSpace. Extent wouldn?t work, as it is the physical size of the collection (in boxes or gigabytes etc) whereas I?m looking to have the length of time for the individual videos. How are other archives handling this type of metadata? Thanks so much! Hilary Clifford AIDS Healthcare Foundation Senior Program Manager of Archives Public Health Division 1710 N La Brea Ave Los Angeles, CA 90046 323-436-8900 ext. 5844 Cell: 323-219-8613 [/Users/archive/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1607367186] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 28964 bytes Desc: image001.png URL: From akroeger at unomaha.edu Thu Apr 4 14:57:04 2019 From: akroeger at unomaha.edu (Angela Kroeger) Date: Thu, 4 Apr 2019 18:57:04 +0000 Subject: [Archivesspace_Users_Group] Video Length Metadata In-Reply-To: References: <6E036E39-29C5-41E5-B119-E56BD390EE97@aidshealth.org> Message-ID: We've put the runtime in various note fields over the last couple of years (including it as part of the scope and contents note or as a general note), most recently settling on the material specific details note. (Example: https://archives.nebraska.edu/repositories/4/archival_objects/36138) I like the suggestions others have made about putting it in the dimensions field of the extent subrecord, or creating a new extent type for duration. But I think we went with a note because that was the option that worked with our metadata batchloads. --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [Media:UniversityCommunications:Graphic Design:Brand tools:Logos- UNO:Vector files:Lock-up:Lockup-color on white backgrnd.eps] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 5540 bytes Desc: image002.png URL: From Hilary.Clifford at aidshealth.org Thu Apr 4 16:30:52 2019 From: Hilary.Clifford at aidshealth.org (Hilary Clifford) Date: Thu, 4 Apr 2019 20:30:52 +0000 Subject: [Archivesspace_Users_Group] Video Length Metadata Message-ID: Thank you all for these suggestions, they have been very helpful! Hilary Clifford AIDS Healthcare Foundation Senior Program Manager of Archives Public Health Division 1710 N La Brea Ave Los Angeles, CA 90046 323-436-8900 ext. 5844 Cell: 323-219-8613 [/Users/archive/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_809055832] From: on behalf of Angela Kroeger Reply-To: Archivesspace Users Group Date: Thursday, April 4, 2019 at 11:57 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Video Length Metadata We've put the runtime in various note fields over the last couple of years (including it as part of the scope and contents note or as a general note), most recently settling on the material specific details note. (Example: https://archives.nebraska.edu/repositories/4/archival_objects/36138) I like the suggestions others have made about putting it in the dimensions field of the extent subrecord, or creating a new extent type for duration. But I think we went with a note because that was the option that worked with our metadata batchloads. --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [Media:UniversityCommunications:Graphic Design:Brand tools:Logos- UNO:Vector files:Lock-up:Lockup-color on white backgrnd.eps] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 293391 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 5541 bytes Desc: image002.png URL: From maura.carbone at yale.edu Fri Apr 5 11:41:00 2019 From: maura.carbone at yale.edu (Carbone, Maura) Date: Fri, 5 Apr 2019 15:41:00 +0000 Subject: [Archivesspace_Users_Group] FYI: Custom reports Message-ID: <0FFB72A8-C693-46D7-AA6F-6A677E66E8D2@yale.edu> Hi Steven, ?A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom, but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) ? Sadly, I wasn?t able to make the call and I didn?t see this information in the community notes. What were the resons? Thanks! Maura From: on behalf of "Majewski, Steven Dennis (sdm7g)" Reply-To: Archivesspace Users Group Date: Wednesday, April 3, 2019 at 5:18 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] FYI: Custom reports Followup to my comments on todays Reports call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom, but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) I found it was quite easy to add one of these custom sub reports to existing reports. We wanted to add the collections_management_subreport to the resources_list_report and the accession_report. This was a pretty trivial set of changes to implement: https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports.patch And if some of the proper defaults like additions to the locales files were added to the distribution, it would have been only two one-line additions. Adds these fields to the reports if a collection management record exists: collection_management_subreport: processing_funding_source: Funding Source processing_hours_total: Total Hours processing_plan: Processing Plan processing_priority: Processing Priority processing_status: Processing Status processors: Processors rights_determined: Rights Determined? Reports, like plugins, do not require a new build: you can just drop modified reports into archivesspace/reports/ directories and restart to take effect. We have also added a custom report on users and permission groups, which is very handy due to the limited staff web app view of users. I?ve submitted a pull request to add this to the next release. https://github.com/archivesspace/archivesspace/pull/1502 https://github.com/archivesspace/archivesspace/pull/1502/files ? Steve Majewski -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Apr 5 11:55:53 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 5 Apr 2019 15:55:53 +0000 Subject: [Archivesspace_Users_Group] FYI: Custom reports In-Reply-To: <0FFB72A8-C693-46D7-AA6F-6A677E66E8D2@yale.edu> References: <0FFB72A8-C693-46D7-AA6F-6A677E66E8D2@yale.edu> Message-ID: My understanding is that the intention was that you could arbitrarily combine or add sub reports by selecting them in the web app custom report generator, however in testing it was discovered that some combinations were a real resource hog and could crash. I?m not sure if that meant that just the reports crashed or the whole web app crashed, or if the rest of the system was unresponsive until the report finished. But it required at least more investigation to discover the scope of the problem. ? Steve. > On Apr 5, 2019, at 11:41 AM, Carbone, Maura wrote: > > Hi Steven, > > ?A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom , but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) ? > > Sadly, I wasn?t able to make the call and I didn?t see this information in the community notes. What were the resons? > > Thanks! > Maura > > From: on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Wednesday, April 3, 2019 at 5:18 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] FYI: Custom reports > > Followup to my comments on todays Reports call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call > > A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom , but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) > > I found it was quite easy to add one of these custom sub reports to existing reports. > We wanted to add the collections_management_subreport to the resources_list_report and the accession_report. > > This was a pretty trivial set of changes to implement: > > https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports > > https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports.patch > > And if some of the proper defaults like additions to the locales files were added to the distribution, it would have been only two one-line additions. > > Adds these fields to the reports if a collection management record exists: > > collection_management_subreport: > processing_funding_source: Funding Source > processing_hours_total: Total Hours > processing_plan: Processing Plan > processing_priority: Processing Priority > processing_status: Processing Status > processors: Processors > rights_determined: Rights Determined? > > > Reports, like plugins, do not require a new build: you can just drop modified reports into archivesspace/reports/ directories and restart to take effect. > > > We have also added a custom report on users and permission groups, which is very handy due to the limited staff web app view of users. I?ve submitted a pull request to add this to the next release. > > https://github.com/archivesspace/archivesspace/pull/1502 > > https://github.com/archivesspace/archivesspace/pull/1502/files > > > > ? Steve Majewski > > > > > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From maura.carbone at yale.edu Fri Apr 5 12:00:41 2019 From: maura.carbone at yale.edu (Carbone, Maura) Date: Fri, 5 Apr 2019 16:00:41 +0000 Subject: [Archivesspace_Users_Group] FYI: Custom reports In-Reply-To: References: <0FFB72A8-C693-46D7-AA6F-6A677E66E8D2@yale.edu> Message-ID: <58CF1CEC-A0F9-4AAA-B2FF-05C22D9EECD0@yale.edu> Oh, interesting, is that the ?proof of concept? UI thing we saw awhile back? Where you could build a report in the UI? -Maura From: on behalf of "Majewski, Steven Dennis (sdm7g)" Reply-To: Archivesspace Users Group Date: Friday, April 5, 2019 at 11:56 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FYI: Custom reports My understanding is that the intention was that you could arbitrarily combine or add sub reports by selecting them in the web app custom report generator, however in testing it was discovered that some combinations were a real resource hog and could crash. I?m not sure if that meant that just the reports crashed or the whole web app crashed, or if the rest of the system was unresponsive until the report finished. But it required at least more investigation to discover the scope of the problem. ? Steve. On Apr 5, 2019, at 11:41 AM, Carbone, Maura > wrote: Hi Steven, ?A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom, but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) ? Sadly, I wasn?t able to make the call and I didn?t see this information in the community notes. What were the resons? Thanks! Maura From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Wednesday, April 3, 2019 at 5:18 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] FYI: Custom reports Followup to my comments on todays Reports call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom, but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) I found it was quite easy to add one of these custom sub reports to existing reports. We wanted to add the collections_management_subreport to the resources_list_report and the accession_report. This was a pretty trivial set of changes to implement: https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports.patch And if some of the proper defaults like additions to the locales files were added to the distribution, it would have been only two one-line additions. Adds these fields to the reports if a collection management record exists: collection_management_subreport: processing_funding_source: Funding Source processing_hours_total: Total Hours processing_plan: Processing Plan processing_priority: Processing Priority processing_status: Processing Status processors: Processors rights_determined: Rights Determined? Reports, like plugins, do not require a new build: you can just drop modified reports into archivesspace/reports/ directories and restart to take effect. We have also added a custom report on users and permission groups, which is very handy due to the limited staff web app view of users. I?ve submitted a pull request to add this to the next release. https://github.com/archivesspace/archivesspace/pull/1502 https://github.com/archivesspace/archivesspace/pull/1502/files ? Steve Majewski _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Apr 5 12:14:31 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 5 Apr 2019 16:14:31 +0000 Subject: [Archivesspace_Users_Group] FYI: Custom reports In-Reply-To: <58CF1CEC-A0F9-4AAA-B2FF-05C22D9EECD0@yale.edu> References: <0FFB72A8-C693-46D7-AA6F-6A677E66E8D2@yale.edu> <58CF1CEC-A0F9-4AAA-B2FF-05C22D9EECD0@yale.edu> Message-ID: <2EDD3238-4477-4A3C-82B1-6AA9FC876128@virginia.edu> Yes. So the sub reports that are the building blocks exist in current releases in reports/custom/ , but the ?build a custom report? templates and facility has not been released, pending figuring out that resource problem. But if you can?t wait for this to be solved and you really need a custom report, my example was to show that it?s fairly easy to extend the existing reports using those existing custom sub-report modules. (Testing can then be done on a non production server before copying changes to production and restarting.) ? Steve. > On Apr 5, 2019, at 12:00 PM, Carbone, Maura wrote: > > Oh, interesting, is that the ?proof of concept? UI thing we saw awhile back? Where you could build a report in the UI? > > -Maura > > From: on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Friday, April 5, 2019 at 11:56 AM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] FYI: Custom reports > > My understanding is that the intention was that you could arbitrarily combine or add sub reports by selecting them in the web app custom report generator, however in testing it was discovered that some combinations were a real resource hog and could crash. > I?m not sure if that meant that just the reports crashed or the whole web app crashed, or if the rest of the system was unresponsive until the report finished. > But it required at least more investigation to discover the scope of the problem. > > ? Steve. > > >> On Apr 5, 2019, at 11:41 AM, Carbone, Maura > wrote: >> >> Hi Steven, >> >> ?A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom , but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) ? >> >> Sadly, I wasn?t able to make the call and I didn?t see this information in the community notes. What were the resons? >> >> Thanks! >> Maura >> >> From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > >> Reply-To: Archivesspace Users Group > >> Date: Wednesday, April 3, 2019 at 5:18 PM >> To: Archivesspace Users Group > >> Subject: [Archivesspace_Users_Group] FYI: Custom reports >> >> Followup to my comments on todays Reports call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call >> >> A number of custom sub reports are available in https://github.com/archivesspace/archivesspace/tree/master/reports/custom , but the facility to create custom reports has not yet been released. ( Reasons for this was discussed on the call. ) >> >> I found it was quite easy to add one of these custom sub reports to existing reports. >> We wanted to add the collections_management_subreport to the resources_list_report and the accession_report. >> >> This was a pretty trivial set of changes to implement: >> >> https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports >> >> https://github.com/archivesspace/archivesspace/compare/master...uvalib:collmgmt_subreports.patch >> >> And if some of the proper defaults like additions to the locales files were added to the distribution, it would have been only two one-line additions. >> >> Adds these fields to the reports if a collection management record exists: >> >> collection_management_subreport: >> processing_funding_source: Funding Source >> processing_hours_total: Total Hours >> processing_plan: Processing Plan >> processing_priority: Processing Priority >> processing_status: Processing Status >> processors: Processors >> rights_determined: Rights Determined? >> >> >> Reports, like plugins, do not require a new build: you can just drop modified reports into archivesspace/reports/ directories and restart to take effect. >> >> >> We have also added a custom report on users and permission groups, which is very handy due to the limited staff web app view of users. I?ve submitted a pull request to add this to the next release. >> >> https://github.com/archivesspace/archivesspace/pull/1502 >> >> https://github.com/archivesspace/archivesspace/pull/1502/files >> >> >> >> ? Steve Majewski >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From suzanna.calev at wilkes.edu Mon Apr 8 13:41:54 2019 From: suzanna.calev at wilkes.edu (Calev, Suzanna) Date: Mon, 8 Apr 2019 13:41:54 -0400 Subject: [Archivesspace_Users_Group] Trying to import data but keep getting error message Message-ID: Hello all, Has anyone else encountered this error with importing data for digital objects : "Error: #<ArgumentError: invalid byte sequence in UTF-8>" I keep getting this error message in the log. If anyone has any insight into fixing this, please let me know. Thank you, Suzanna -- Suzanna Calev, MLIS & MA Archivist/Public Services Librarian Farley Library 187 South Franklin Street Wilkes-Barre, PA 18766 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christy.tomecek at yale.edu Mon Apr 8 14:31:09 2019 From: christy.tomecek at yale.edu (Tomecek, Christy) Date: Mon, 8 Apr 2019 18:31:09 +0000 Subject: [Archivesspace_Users_Group] Trying to import data but keep getting error message In-Reply-To: References: Message-ID: Hi Suzanna, I?ve seen this error when I?ve tried to import something with improperly encoded diacritics (i.e. not done in UTF-8). Perhaps run the data through a UTF-8 validator to check? Best wishes, Christy -- Christy Tomecek Project Archivist Fortunoff Video Archive for Holocaust Testimonies Yale University Library (203) 432-0367 christy.tomecek at yale.edu https://fortunoff.library.yale.edu/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Calev, Suzanna Sent: Monday, April 8, 2019 1:42 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Trying to import data but keep getting error message Hello all, Has anyone else encountered this error with importing data for digital objects : "Error: #<ArgumentError: invalid byte sequence in UTF-8>" I keep getting this error message in the log. If anyone has any insight into fixing this, please let me know. Thank you, Suzanna -- Suzanna Calev, MLIS & MA Archivist/Public Services Librarian Farley Library 187 South Franklin Street Wilkes-Barre, PA 18766 -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Wed Apr 10 10:28:04 2019 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 10 Apr 2019 14:28:04 +0000 Subject: [Archivesspace_Users_Group] External identifiers in agents Message-ID: <7BC585A7-FBF9-41BF-85C4-C1441939C460@rockarch.org> Hey all, We were just looking at the models in AS and noticed that the backend models for Terms, Resources, Objects, etc. supported external identifiers (even if the GUI doesn?t), and we found it kind of weird that the Agents module doesn?t. We?d love to have the ability to link out to a DBPedia or Wikidata entry for an agent without having to add an extraneous Name Form and Source just for that information. It doesn?t feel like a good way to go about doing that. Can anyone foresee any issues with something like this? Would you be in support of this being added to the Agents model? It appears to be a fairly easy change, even if it is a database change. Thoughts? -Patrick -- Patrick Galligan Digital Archivist Rockefeller Archive Center (914) 366-6386 He/Him/His -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Wed Apr 10 14:42:50 2019 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 10 Apr 2019 18:42:50 +0000 Subject: [Archivesspace_Users_Group] this PM Message-ID: I'll be leaving at 430 today. Ed Busch, MLIS Acting Director Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Wed Apr 10 14:43:20 2019 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 10 Apr 2019 18:43:20 +0000 Subject: [Archivesspace_Users_Group] this PM In-Reply-To: References: Message-ID: Sorry, wrong list. :) From: Busch, Ed Sent: Wednesday, April 10, 2019 2:43 PM To: 'Archivesspace Users Group' Subject: this PM I'll be leaving at 430 today. Ed Busch, MLIS Acting Director Electronic Records Archivist Michigan State University Archives Conrad Hall 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Wed Apr 10 15:15:20 2019 From: cory_nimer at byu.edu (Cory Nimer) Date: Wed, 10 Apr 2019 19:15:20 +0000 Subject: [Archivesspace_Users_Group] External identifiers in agents In-Reply-To: <7BC585A7-FBF9-41BF-85C4-C1441939C460@rockarch.org> References: <7BC585A7-FBF9-41BF-85C4-C1441939C460@rockarch.org> Message-ID: <1554923721699.50555@byu.edu> Patrick, The upcoming Agents module revision (https://archivesspace.atlassian.net/browse/ANW-429) includes an Alternative Set section that allow links to other authority records, which might be useful when it is finished. If you are just interested in a simple link, though, the External Documents section does allow recording a link that is currently available in the PUI display. Do either of these approaches meet your need, or what else might be needed? When you mentioned that there is a place for recording external identifiers for terms, was this in the Subjects module? There is a pending ticket to allow URIs to be recorded for controlled terms (https://archivesspace.atlassian.net/browse/ANW-355?), but I hadn't heard that there had been any progress in this area. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Wednesday, April 10, 2019 8:28 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] External identifiers in agents Hey all, We were just looking at the models in AS and noticed that the backend models for Terms, Resources, Objects, etc. supported external identifiers (even if the GUI doesn't), and we found it kind of weird that the Agents module doesn't. We'd love to have the ability to link out to a DBPedia or Wikidata entry for an agent without having to add an extraneous Name Form and Source just for that information. It doesn't feel like a good way to go about doing that. Can anyone foresee any issues with something like this? Would you be in support of this being added to the Agents model? It appears to be a fairly easy change, even if it is a database change. Thoughts? -Patrick -- Patrick Galligan Digital Archivist Rockefeller Archive Center (914) 366-6386 He/Him/His -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Wed Apr 10 15:29:36 2019 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 10 Apr 2019 19:29:36 +0000 Subject: [Archivesspace_Users_Group] External identifiers in agents Message-ID: <8303A34A-DE1F-47F0-9C18-1D2EA9DAD394@rockarch.org> Corey, Looks like the record ids in the model have basically the same model as external ids. Do you know if there?s a timeline for this development? -Patrick From: on behalf of Cory Nimer Reply-To: Archivesspace Users Group Date: Wednesday, April 10, 2019 at 3:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] External identifiers in agents Patrick, The upcoming Agents module revision (https://archivesspace.atlassian.net/browse/ANW-429) includes an Alternative Set section that allow links to other authority records, which might be useful when it is finished. If you are just interested in a simple link, though, the External Documents section does allow recording a link that is currently available in the PUI display. Do either of these approaches meet your need, or what else might be needed? When you mentioned that there is a place for recording external identifiers for terms, was this in the Subjects module? There is a pending ticket to allow URIs to be recorded for controlled terms (https://archivesspace.atlassian.net/browse/ANW-355?), but I hadn't heard that there had been any progress in this area. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Wednesday, April 10, 2019 8:28 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] External identifiers in agents Hey all, We were just looking at the models in AS and noticed that the backend models for Terms, Resources, Objects, etc. supported external identifiers (even if the GUI doesn?t), and we found it kind of weird that the Agents module doesn?t. We?d love to have the ability to link out to a DBPedia or Wikidata entry for an agent without having to add an extraneous Name Form and Source just for that information. It doesn?t feel like a good way to go about doing that. Can anyone foresee any issues with something like this? Would you be in support of this being added to the Agents model? It appears to be a fairly easy change, even if it is a database change. Thoughts? -Patrick -- Patrick Galligan Digital Archivist Rockefeller Archive Center (914) 366-6386 He/Him/His -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Wed Apr 10 15:37:08 2019 From: cory_nimer at byu.edu (Cory Nimer) Date: Wed, 10 Apr 2019 19:37:08 +0000 Subject: [Archivesspace_Users_Group] External identifiers in agents In-Reply-To: <8303A34A-DE1F-47F0-9C18-1D2EA9DAD394@rockarch.org> References: <8303A34A-DE1F-47F0-9C18-1D2EA9DAD394@rockarch.org> Message-ID: <1554925030413.93535@byu.edu> ?Patrick, According to the development roadmap published last month, the Agents updates are scheduled to be completed by June--though perhaps someone from the program staff could say where that work is at currently. As for ANW-355, I don't think it has been prioritized yet. Cory ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Wednesday, April 10, 2019 1:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] External identifiers in agents Corey, Looks like the record ids in the model have basically the same model as external ids. Do you know if there's a timeline for this development? -Patrick From: on behalf of Cory Nimer Reply-To: Archivesspace Users Group Date: Wednesday, April 10, 2019 at 3:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] External identifiers in agents Patrick, The upcoming Agents module revision (https://archivesspace.atlassian.net/browse/ANW-429) includes an Alternative Set section that allow links to other authority records, which might be useful when it is finished. If you are just interested in a simple link, though, the External Documents section does allow recording a link that is currently available in the PUI display. Do either of these approaches meet your need, or what else might be needed? When you mentioned that there is a place for recording external identifiers for terms, was this in the Subjects module? There is a pending ticket to allow URIs to be recorded for controlled terms (https://archivesspace.atlassian.net/browse/ANW-355?), but I hadn't heard that there had been any progress in this area. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Wednesday, April 10, 2019 8:28 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] External identifiers in agents Hey all, We were just looking at the models in AS and noticed that the backend models for Terms, Resources, Objects, etc. supported external identifiers (even if the GUI doesn't), and we found it kind of weird that the Agents module doesn't. We'd love to have the ability to link out to a DBPedia or Wikidata entry for an agent without having to add an extraneous Name Form and Source just for that information. It doesn't feel like a good way to go about doing that. Can anyone foresee any issues with something like this? Would you be in support of this being added to the Agents model? It appears to be a fairly easy change, even if it is a database change. Thoughts? -Patrick -- Patrick Galligan Digital Archivist Rockefeller Archive Center (914) 366-6386 He/Him/His -------------- next part -------------- An HTML attachment was scrubbed... URL: From alicia.detelich at yale.edu Thu Apr 11 10:34:21 2019 From: alicia.detelich at yale.edu (Detelich, Alicia) Date: Thu, 11 Apr 2019 14:34:21 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Technical Documentation Update Message-ID: Dear ArchivesSpace Community, I am writing on behalf of the Technical Documentation sub-team of the ArchivesSpace Technical Advisory Council (TAC) to remind users that, as noted by Christine DiBella in the January 2019 ArchivesSpace Update, technical documentation for the ArchivesSpace application is now maintained in a separate Github repository: https://github.com/archivesspace/tech-docs. The static documentation page remains the same - http://archivesspace.github.io/archivesspace/ - though it has been substantially reorganized. The sub-team encourages ArchivesSpace users to submit suggestions for technical documentation enhancements as issues to the tech-docs repository. Users are also welcome to contact Tech Docs members directly or reply to this email with ideas or comments. We are also seeking feedback from the community regarding other ways of supplementing existing technical documentation. Would users be interested in blog posts or videos about the application architecture, similar to the developer screencasts created several years ago? What other types of programming would you find beneficial that are currently lacking? Feel free to reply to this email or contact Tech Docs members with your suggestions. Thank you! Alicia Detelich, on behalf of: Bobbi Fox Jason Loeffler Dave Mayo Dallas Pillen Trevor Thornton -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Thu Apr 11 13:20:14 2019 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 11 Apr 2019 17:20:14 +0000 Subject: [Archivesspace_Users_Group] adding controlled value to multipart note Message-ID: <4c24a4095fda432d911873a8f4ea2e60@lib.msu.edu> Hi all, I'm trying to unravel a mystery... I'm interested in adding a Conservation note (DACS 7.1.3) to the list of controlled value multi-part notes but it seems like Multi-part notes are non-configurable, even though other categories are. I believe I have the permissions, but creating a new value for this particular section doesn't seem possible. I just wanted to check if others experience this and if other also miss having a Conservation (different than Processing) note? Thanks! Lydia -- Dr. Lydia Tang, CA, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Thu Apr 11 14:23:12 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 11 Apr 2019 18:23:12 +0000 Subject: [Archivesspace_Users_Group] adding controlled value to multipart note In-Reply-To: <4c24a4095fda432d911873a8f4ea2e60@lib.msu.edu> References: <4c24a4095fda432d911873a8f4ea2e60@lib.msu.edu> Message-ID: Lydia, ArchivesSpace has a variety of "uneditable" controlled value lists that not even administrators can edit in the application (the ability to suppress unused values from uneditable lists was added after the initial release of ArchivesSpace, which is a great feature, but that won't help out for this use case). I believe that there are 30 enumeration lists in total that fit the bill. Since I don't know where this documented (aside from the code), here's the full list: * accession_parts_relator * accession_sibling_relator * agent_relationship_associative_relator * agent_relationship_earlierlater_relator * agent_relationship_parentchild_relator * agent_relationship_subordinatesuperior_relator * archival_record_level * container_location_status * country_iso_3166 * date_certainty * date_type * deaccession_scope * extent_portion * file_version_xlink_actuate_attribute * file_version_xlink_show_attribute * job_type * language_iso639_2 * linked_agent_role * linked_event_archival_record_roles * name_person_name_order * note_bibliography_type * note_digital_object_type * note_index_type * note_index_item_type * note_multipart_type * note_orderedlist_enumeration * note_singlepart_type * rights_statement_ip_status * rights_statement_rights_type * subject_term_type Given that ArchivesSpace generally adheres to DACS for the rest of the "note_multipart_type", "note_singlepart_type", and other "note" lists, I think that it would make sense to add a feature request for this in JIRA. Doing that would have an impact on imports/exports, etc., but I think that harmonizing with the current version of DACS is good goal. I have to admit that I wasn't even aware of the conservation note in DACS, so thanks for bringing this up. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Thursday, 11 April, 2019 1:20 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] adding controlled value to multipart note Hi all, I'm trying to unravel a mystery... I'm interested in adding a Conservation note (DACS 7.1.3) to the list of controlled value multi-part notes but it seems like Multi-part notes are non-configurable, even though other categories are. I believe I have the permissions, but creating a new value for this particular section doesn't seem possible. I just wanted to check if others experience this and if other also miss having a Conservation (different than Processing) note? Thanks! Lydia -- Dr. Lydia Tang, CA, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pprestinary at fullerton.edu Thu Apr 11 15:01:05 2019 From: pprestinary at fullerton.edu (Prestinary, Patricia) Date: Thu, 11 Apr 2019 19:01:05 +0000 Subject: [Archivesspace_Users_Group] Subject headings Message-ID: Dear AS community, It appears that since the latest update, that we are experiencing difficulties with subject headings. We have created one, but cannot find it in a subsequent search in Edit record or Browse subjects. When we try to create it again, we receive the attached error message. Has anyone else experienced this problem recently? Best, Patrisia Patrisia Prestinary, M.L.I.S., C.A. University Archives & Special Collections Archivist & Special Collections Librarian Digitization Studio Coordinator CSU, Fullerton | Pollak Library | PLS-352 Ph. (657) 278-4751 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Subject capture error.pdf Type: application/pdf Size: 56666 bytes Desc: Subject capture error.pdf URL: From dmichelson at smith.edu Thu Apr 11 15:04:33 2019 From: dmichelson at smith.edu (Daniel Michelson) Date: Thu, 11 Apr 2019 15:04:33 -0400 Subject: [Archivesspace_Users_Group] adding controlled value to multipart note In-Reply-To: References: <4c24a4095fda432d911873a8f4ea2e60@lib.msu.edu> Message-ID: At the risk of being pedantic, ArchivesSpace is really following EAD, not DACS. The somewhat rough matching between EAD and DACS elements is more clear when comparing the numerous different notes EAD uses for physical access with the single element in DACS 4.2. Dan Michelson (wearing my TS-DACS Co-Chair hat) On Thu, Apr 11, 2019 at 2:23 PM Custer, Mark wrote: > Lydia, > > > > ArchivesSpace has a variety of ?uneditable? controlled value lists that > not even administrators can edit in the application (the ability to > suppress unused values from uneditable lists was added after the initial > release of ArchivesSpace, which is a great feature, but that won?t help out > for this use case). > > > > I believe that there are 30 enumeration lists in total that fit the bill. > Since I don?t know where this documented (aside from the code), here?s the > full list: > > > > - accession_parts_relator > - accession_sibling_relator > - agent_relationship_associative_relator > - agent_relationship_earlierlater_relator > - agent_relationship_parentchild_relator > - agent_relationship_subordinatesuperior_relator > - archival_record_level > - container_location_status > - country_iso_3166 > - date_certainty > - date_type > - deaccession_scope > - extent_portion > - file_version_xlink_actuate_attribute > - file_version_xlink_show_attribute > - job_type > - language_iso639_2 > - linked_agent_role > - linked_event_archival_record_roles > - name_person_name_order > - note_bibliography_type > - note_digital_object_type > - note_index_type > - note_index_item_type > - note_multipart_type > - note_orderedlist_enumeration > - note_singlepart_type > - rights_statement_ip_status > - rights_statement_rights_type > - subject_term_type > > > > Given that ArchivesSpace generally adheres to DACS for the rest of the > ?note_multipart_type?, ?note_singlepart_type?, and other ?note? lists, I > think that it would make sense to add a feature request for this in JIRA. > Doing that would have an impact on imports/exports, etc., but I think > that harmonizing with the current version of DACS is good goal. I have to > admit that I wasn?t even aware of the conservation note in DACS, so thanks > for bringing this up. > > > > Mark > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Tang, > Lydia > *Sent:* Thursday, 11 April, 2019 1:20 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] adding controlled value to > multipart note > > > > Hi all, > > I?m trying to unravel a mystery? I?m interested in adding a Conservation > note (DACS 7.1.3) to the list of controlled value multi-part notes but it > seems like Multi-part notes are non-configurable, even though other > categories are. I believe I have the permissions, but creating a new value > for this particular section doesn?t seem possible. I just wanted to check > if others experience this and if other also miss having a Conservation > (different than Processing) note? Thanks! > > > > Lydia > > -- > > Dr. Lydia Tang, CA, DMA, MLIS > Special Collections Archivist-Librarian > > Philosophy, Aesthetics, and Ethics Bibliographer > Michigan State University Libraries > 366 W. Circle Drive (DB 6) > East Lansing, MI 48824-1048 > Email: ltang5 at msu.edu > Phone: 517-884-8984 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Dan Michelson Project Manager Archivist Smith College Special Collections -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Fri Apr 12 09:23:43 2019 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 12 Apr 2019 13:23:43 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, but something went wrong..." Message-ID: <7749A95C-3413-4FF9-AD32-75B947270102@lib.msu.edu> Hi again, helpful people! We have been plagued by a PDF generating issue and would appreciate your help! We?re on 2.5.1 and when we try to generate a PDF from the PUI, we regularly get the "We're sorry, but something went wrong? message. We can generate it from the staff side, but obviously this doesn?t help our researchers. Sample collection: https://as.lib.msu.edu/repositories/2/resources/1983 Sample PDF: https://as.lib.msu.edu/repositories/2/resources/1983/pdf Apparently this is a 404 error and doesn?t appear in our Apache error logs. My IT person thinks it?s an error with the way the ?print? URL is being generated. Does anyone else have this issue? Any advice? Thanks! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Librarian Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 From jazairi at bc.edu Fri Apr 12 09:25:25 2019 From: jazairi at bc.edu (Adam Jazairi) Date: Fri, 12 Apr 2019 09:25:25 -0400 Subject: [Archivesspace_Users_Group] Subject headings In-Reply-To: References: Message-ID: Hi Patrisia, These error messages suggest that the first attempt to create the subject record was successful, since the ArchivesSpace database does not allow duplicate authority IDs or subject records. Are you able to access the subject record directly in your staff interface at /subjects/1933? If so, there might be a problem with the indexer. Adam On Thu, Apr 11, 2019 at 3:01 PM Prestinary, Patricia < pprestinary at fullerton.edu> wrote: > Dear AS community, > > > > It appears that since the latest update, that we are experiencing > difficulties with subject headings. We have created one, but cannot find it > in a subsequent search in Edit record or Browse subjects. When we try to > create it again, we receive the attached error message. > > > > Has anyone else experienced this problem recently? > > > > Best, > > Patrisia > > > > Patrisia Prestinary, M.L.I.S., C.A. > > University Archives & Special Collections > > Archivist & Special Collections Librarian > > Digitization Studio Coordinator > > CSU, Fullerton | Pollak Library | PLS-352 > > Ph. (657) 278-4751 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Adam Jazairi Digital Repository Services Boston College Libraries (617) 552-1404 adam.jazairi at bc.edu He/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Apr 12 09:43:31 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 12 Apr 2019 13:43:31 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, but something went wrong..." In-Reply-To: <7749A95C-3413-4FF9-AD32-75B947270102@lib.msu.edu> References: <7749A95C-3413-4FF9-AD32-75B947270102@lib.msu.edu> Message-ID: If I was a betting man I'd bet you're trying to print something with an AMPERSAND in it someplace? What's in the logs? BUT That 404 is to be expected, you can't link directly to the print page like that, it needs to be a POST from the other page. I can't tell if you're just hitting the 404 thing, or both the 404 thing and the ampersand thing. There's a bunch of JIRAs about the darn ampersands. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Friday, April 12, 2019 9:23 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] "We're sorry, but something went wrong..." Hi again, helpful people! We have been plagued by a PDF generating issue and would appreciate your help! We?re on 2.5.1 and when we try to generate a PDF from the PUI, we regularly get the "We're sorry, but something went wrong? message. We can generate it from the staff side, but obviously this doesn?t help our researchers. Sample collection: https://as.lib.msu.edu/repositories/2/resources/1983 Sample PDF: https://as.lib.msu.edu/repositories/2/resources/1983/pdf Apparently this is a 404 error and doesn?t appear in our Apache error logs. My IT person thinks it?s an error with the way the ?print? URL is being generated. Does anyone else have this issue? Any advice? Thanks! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Librarian Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Apr 12 09:44:49 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 12 Apr 2019 13:44:49 +0000 Subject: [Archivesspace_Users_Group] Subject headings In-Reply-To: References: , Message-ID: I think Adam is correct, I'd suggest forcing a full reindex and see how things look. That MIGHT clear up the problem. It will at least narrow it down. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Adam Jazairi Sent: Friday, April 12, 2019 9:25 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Subject headings Hi Patrisia, These error messages suggest that the first attempt to create the subject record was successful, since the ArchivesSpace database does not allow duplicate authority IDs or subject records. Are you able to access the subject record directly in your staff interface at /subjects/1933? If so, there might be a problem with the indexer. Adam On Thu, Apr 11, 2019 at 3:01 PM Prestinary, Patricia > wrote: Dear AS community, It appears that since the latest update, that we are experiencing difficulties with subject headings. We have created one, but cannot find it in a subsequent search in Edit record or Browse subjects. When we try to create it again, we receive the attached error message. Has anyone else experienced this problem recently? Best, Patrisia Patrisia Prestinary, M.L.I.S., C.A. University Archives & Special Collections Archivist & Special Collections Librarian Digitization Studio Coordinator CSU, Fullerton | Pollak Library | PLS-352 Ph. (657) 278-4751 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Adam Jazairi Digital Repository Services Boston College Libraries (617) 552-1404 adam.jazairi at bc.edu He/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Fri Apr 12 09:56:55 2019 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Fri, 12 Apr 2019 13:56:55 +0000 Subject: [Archivesspace_Users_Group] "We're sorry, but something went wrong..." In-Reply-To: References: <7749A95C-3413-4FF9-AD32-75B947270102@lib.msu.edu> Message-ID: Yes, it's very likely an ampersand issue! We just completed a project to hunt down and eliminate ampersands (more specifically anything that isn't &) from all our resource records, which took forever. Actually what turned out to be the most problematic were ampersands without spaces on either side, for whatever reason. So for instance, "Johnson & Johnson" would typically get through whatever scrubbing process happened when generating a PDF from the public interface, at least in v2.4.1, but "AT&T" would cause the "something went wrong" error. It's probably easier to export EAD for that record and search for the offending ampersand, then fix it in ASpace. --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Friday, April 12, 2019 8:44 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "We're sorry, but something went wrong..." If I was a betting man I'd bet you're trying to print something with an AMPERSAND in it someplace? What's in the logs? BUT That 404 is to be expected, you can't link directly to the print page like that, it needs to be a POST from the other page. I can't tell if you're just hitting the 404 thing, or both the 404 thing and the ampersand thing. There's a bunch of JIRAs about the darn ampersands. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tang, Lydia > Sent: Friday, April 12, 2019 9:23 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] "We're sorry, but something went wrong..." Hi again, helpful people! We have been plagued by a PDF generating issue and would appreciate your help! We're on 2.5.1 and when we try to generate a PDF from the PUI, we regularly get the "We're sorry, but something went wrong" message. We can generate it from the staff side, but obviously this doesn't help our researchers. Sample collection: https://as.lib.msu.edu/repositories/2/resources/1983 Sample PDF: https://as.lib.msu.edu/repositories/2/resources/1983/pdf Apparently this is a 404 error and doesn't appear in our Apache error logs. My IT person thinks it's an error with the way the "print" URL is being generated. Does anyone else have this issue? Any advice? Thanks! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Librarian Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristao at clemson.edu Mon Apr 15 10:31:40 2019 From: kristao at clemson.edu (Krista Oldham) Date: Mon, 15 Apr 2019 14:31:40 +0000 Subject: [Archivesspace_Users_Group] Reports-time out Message-ID: Hello all, I have recently moved from one institutions that had ASpace to a new institutions that has ASpace and I am currently in the process of getting familiar with its set up here. One of the things that I have noticed is that our reports do not work at all. If a report run successfully, I get a ridiculously large spreadsheet that only has one row filled out sporadically. Most of the time the reports do not run successful and basically crashes the system. Can anyone tell me what we are doing wrong or what we might think about doing differently? KRISTA OLDHAM CLEMSON UNIVERSITY University Archivist Special Collections and Archives Clemson University Libraries kristao at clemson.edu 864-656-4751 Pronouns: She, her, hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Apr 15 10:38:26 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 15 Apr 2019 14:38:26 +0000 Subject: [Archivesspace_Users_Group] Reports-time out In-Reply-To: References: Message-ID: What version are you running? If it's not 2.5.2 reports were pretty rough and it's not surprising that you're seeing that. Reports were redone in version 2.5.1, that fixed a bunch of troubles. It's generally a good idea to run the latest version if possible. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Krista Oldham Sent: Monday, April 15, 2019 10:31 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Reports-time out Hello all, I have recently moved from one institutions that had ASpace to a new institutions that has ASpace and I am currently in the process of getting familiar with its set up here. One of the things that I have noticed is that our reports do not work at all. If a report run successfully, I get a ridiculously large spreadsheet that only has one row filled out sporadically. Most of the time the reports do not run successful and basically crashes the system. Can anyone tell me what we are doing wrong or what we might think about doing differently? KRISTA OLDHAM CLEMSON UNIVERSITY University Archivist Special Collections and Archives Clemson University Libraries kristao at clemson.edu 864-656-4751 Pronouns: She, her, hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Apr 15 10:51:30 2019 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 15 Apr 2019 14:51:30 +0000 Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Nominations Requested for ArchivesSpace Technical Advisory Council In-Reply-To: <278df88fda074bde8ed6e2dfcc4ee23b@MB7.byu.local> References: <278df88fda074bde8ed6e2dfcc4ee23b@MB7.byu.local> Message-ID: <4e57fdf591a04a40b823bca01c8d0da7@MB7.byu.local> This is a gentle reminder that nominations (and self-nominations) for the Technical Advisory Council are due by 9:00 p.m. EDT Friday, April 19, 2019. Nominations should be sent to Christine DiBella at christine.dibella at lyrasis.org. We hope that you will consider submitting your name. Gordon Daines Chair, Nominating Committee From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, January 24, 2019 8:36 AM To: archivesspace_users_group at lyralists.lyrasis.org; Archivesspace Member Reps Subject: [Archivesspace_member_reps] Nominations Requested for ArchivesSpace Technical Advisory Council Colleagues, The ArchivesSpace Governance Board is seeking nominations to fill three (3) vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution in any membership level (the vacancies being filled are from the very large and very small levels). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 19, 2019. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://www.archivesspace.org/technicaladvisory) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service for these appointments will be July 1, 2019-June 30, 2021. We expect making up to three (3) appointments, and each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2021-June 30, 2023. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine DiBella at christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 19, 2019. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Gordon Daines Brigham Young University Chair, Nominating Committee On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair, and Governance Board member Ashley Knox, University of North Carolina Wilmington,Chair of User Advisory Council Max Eckard, University of Michigan, Chair of Technical Advisory Council Caitlin Wells, University of Michigan, representing very large membership level Jay Trask, University of Northern Colorado, representing large membership level Carolyn Runyon, University of Tennessee Chattanooga, representing medium membership level Suzanne Stasiulitis, Pennsylvania State Archives, representing small membership level Jonathan Lawler, Southeastern Baptist Theological Seminary, representing very small membership level Christine DiBella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Bug fixes ___Technical documentation ___Program architecture and integrations with other software ___Migration issues, including import/exports and API design and implementation ___Application testing _________________________ J. Gordon Daines III Supervisor of Reference Services Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From gordon_daines at byu.edu Mon Apr 15 10:52:02 2019 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 15 Apr 2019 14:52:02 +0000 Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Nominations Requested for ArchivesSpace User Advisory Council Message-ID: <2a433027691648f89781b1799fcda248@MB7.byu.local> This is a gentle reminder that nominations (and self-nominations) for the User Advisory Council are due by 9:00 p.m. EDT Friday, April 19, 2019. Nominations should be sent to Christine DiBella at christine.dibella at lyrasis.org. We hope that you will consider submitting your name. Gordon Daines Chair, Nominating Committee From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, January 24, 2019 8:40 AM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' ; Archivesspace Member Reps Subject: [Archivesspace_member_reps] Nominations Requested for ArchivesSpace User Advisory Council Colleagues, The ArchivesSpace Governance Board is seeking nominations to fill three (3) vacancies on the ArchivesSpace User Advisory Council (UAC). Nominees should be presently employed at an ArchivesSpace member institution in any membership category (the vacancies being filled were represented by the very large and medium levels) (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities projected for UAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 19th, 2019. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. UAC (http://www.archivesspace.org/usersadvisory) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. It is also the group that implements and contributes to ArchivesSpace user services. Some of the activities UAC is currently engaged in are: * liaising with national and regional archives organizations; * soliciting, suggesting, gathering requirements for, and prioritizing enhancements to the ArchivesSpace application; * maintaining and updating user documentation, as needed, of the ArchivesSpace application; * developing and providing training to users; and * advising the Governance Board and LYRASIS on the design and delivery of user services, including but not limited to help desk support, training, and presentation of documentation. Sub-groups will be established within UAC to address the areas identified above, as well as other activities identified subsequently. Nominees will be appointed to UAC according to their ability to participate in and lead some of the activities mentioned above. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2019-June 30, 2021. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2021-June 30, 2023. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine DiBella at christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 19th, 2019. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Gordon Daines Brigham Young University Chair, Nominating Committee On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair, and Governance Board member Ashley Knox, University of North Carolina Wilmington,Chair of User Advisory Council Max Eckard, University of Michigan, Chair of Technical Advisory Council Caitlin Wells, University of Michigan, representing very large membership level Jay Trask, University of Northern Colorado, representing large membership level Carolyn Runyon, University of Tennessee Chattanooga, representing medium membership level Suzanne Stasiulitis, Pennsylvania State Archives, representing small membership level Jonathan Lawler, Southeastern Baptist Theological Seminary, representing very small membership level Christine DiBella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Documentation ___Liaising with archives organizations. Please indicate the organizations: _____________________ ___New features, functional or technical specifications ___Training, design ___Training, provision ___ Usability testing ___User/Help support _________________________ J. Gordon Daines III Supervisor of Reference Services Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sdm7g at virginia.edu Mon Apr 15 13:03:33 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 15 Apr 2019 17:03:33 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace/OAI/EAD exports in the wild. Message-ID: <9CDC4E22-056B-45C1-A753-E5AC88057135@virginia.edu> Forwarding the results of this test to the list, as it may be useful in determining where to devote attention to fixing EAD export errors. Test was harvesting 2500+ resources from 5 sites using their ArchivesSpace OAI feeds. ( As part of setting up automatic harvesting of records for Virginia Heritage. ) I?ve been using modified version Python oai-harvest. The standard version you get from ?pip install? will stop harvesting when it encounters an error in the feed. I am in the process of trying to push patches to fix this upstream to both oai-harvest and pyoai python modules. ( Ask me for more info, if you don?t want to wait and want to patch these yourself locally. ) ? After making some modifications to the OAI-harvester to recover from XML parsing errors, I was able to harvest 2500+ EAD files from UVA, VT, JMU, VCU & VMFA ArchivesSpace OAI feeds. Below are the sorts of errors encountered, preceded by the number of occurrences of that error. I don?t have a count on how many resources produced errors, but there are frequently multiple errors in a file. ( All of the TAG_NAME_MISMATCH errors are from the same file, and likely produced by the same malformed element tag. And I suspect all of those UNDECLARE_ENTITY errors are from the same file as well. ) The good news is that the vast majority of errors are produced by unescaped ampersands, and I have seen commits that appear to address this issue in the next release. ( Currently, using the recover=True option on the XML parser in the OAI harvester, has the effect of just dropping the ?&? in the output EAD. And typically, in the other cases, some offending or undefined element or entity is being dropped on output to produce valid XML output. ) And it would appear that all of the errors originate from mixed content note fields. Perhaps this can be fixed by having ArchivesSpace attempt to parse mixed content fields as XML fragments before accepting them. Then bad mixed content fields can be manually fixed before resource can be saved or updated. This does not address EAD validation errors ? just XML parser errors from malformed XML. I haven?t done a massive validation test on this sample yet, but from previous test, the majority of validation errors I?ve seen produced from ASpace EAD exports ( when well formed ) have been attribute name errors. Typically container attributes are being translated thru the locales and have embedded spaces. I would probably be better to export attributes using the internal names rather than locales. 2 NAMESPACE:NS_ERR_UNDEFINED_NAMESPACE: Namespace prefix ns2 for actuate on extref is not defined 3 NAMESPACE:NS_ERR_UNDEFINED_NAMESPACE: Namespace prefix ns2 for href on extref is not defined 2 NAMESPACE:NS_ERR_UNDEFINED_NAMESPACE: Namespace prefix ns2 for show on extref is not defined 1 PARSER:ERR_DOCUMENT_END: Extra content at the end of the document 58 PARSER:ERR_ENTITYREF_SEMICOL_MISSING: EntityRef: expecting ';' 1 PARSER:ERR_GT_REQUIRED: Couldn't find end of Start Tag span line 20 1 PARSER:ERR_NAME_REQUIRED: error parsing attribute name 33 PARSER:ERR_NAME_REQUIRED: xmlParseEntityRef: no name 1 PARSER:ERR_SPACE_REQUIRED: attributes construct error 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: ListRecords line 1 and record 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: OAI-PMH line 1 and ListRecords 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: abstract line 20 and span 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: archdesc line 2 and did 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: did line 3 and abstract 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: ead line 2 and archdesc 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: metadata line 1 and ead 1 PARSER:ERR_TAG_NAME_MISMATCH: Opening and ending tag mismatch: record line 1 and metadata 1 PARSER:ERR_UNDECLARED_ENTITY: Entity 'aacute' not defined 1 PARSER:ERR_UNDECLARED_ENTITY: Entity 'ecircne' not defined 2 PARSER:ERR_UNDECLARED_ENTITY: Entity 'uuml' not defined -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From PJFlanagan at ship.edu Mon Apr 15 13:57:36 2019 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Mon, 15 Apr 2019 17:57:36 +0000 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 Message-ID: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then 2.1.0, to see if some aspect of the migration was responsible; but the issue remains regardless. The staff interface is not impacted to the best of my knowledge. Upon clicking any collection in thew new public interface I'm greeted with the We're sorry, but something went wrong error message. The log file indicates the following error at the same time: Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} hits=6 status=0 QTime=2 F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && @result.respond_to?(:metadata) %> [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] app/models/resource.rb:104:in `metadata' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb___128582640_2336' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/layouts/application.html.erb:24:in `_app_views_layouts_application_html_erb___683597418_2334' I investigated a little bit and found a reference to authority ID around that line. It's worth noting that this particular institution seems to have authority ID blank for every agent, which makes the record look like this in the staff interface: [cid:9cb69a6e-a056-46ca-bddb-34bc600b5cab] This aspect of the problem might be unrelated, but it was the only lead I had. Any advice would be welcome! I thought I would ask here before heading to Jira with it. Thanks, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-15-134634_791x377_scrot.png Type: image/png Size: 39697 bytes Desc: 2019-04-15-134634_791x377_scrot.png URL: From kristao at clemson.edu Mon Apr 15 14:17:27 2019 From: kristao at clemson.edu (Krista Oldham) Date: Mon, 15 Apr 2019 18:17:27 +0000 Subject: [Archivesspace_Users_Group] Reports-time out In-Reply-To: References: Message-ID: We are running 2.3.1. It seems that we need to upgrade for sure. KRISTA OLDHAM CLEMSON UNIVERSITY University Archivist Special Collections and Archives Clemson University Libraries kristao at clemson.edu 864-656-4751 Pronouns: She, her, hers From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Monday, April 15, 2019 10:38 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Reports-time out What version are you running? If it's not 2.5.2 reports were pretty rough and it's not surprising that you're seeing that. Reports were redone in version 2.5.1, that fixed a bunch of troubles. It's generally a good idea to run the latest version if possible. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Krista Oldham > Sent: Monday, April 15, 2019 10:31 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Reports-time out Hello all, I have recently moved from one institutions that had ASpace to a new institutions that has ASpace and I am currently in the process of getting familiar with its set up here. One of the things that I have noticed is that our reports do not work at all. If a report run successfully, I get a ridiculously large spreadsheet that only has one row filled out sporadically. Most of the time the reports do not run successful and basically crashes the system. Can anyone tell me what we are doing wrong or what we might think about doing differently? KRISTA OLDHAM CLEMSON UNIVERSITY University Archivist Special Collections and Archives Clemson University Libraries kristao at clemson.edu 864-656-4751 Pronouns: She, her, hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Apr 15 14:18:38 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 15 Apr 2019 18:18:38 +0000 Subject: [Archivesspace_Users_Group] Reports-time out In-Reply-To: References: , Message-ID: Yeah, if I was a betting man, I'd bet that'll fix it. Blake Carver Systems Administrator blake.carver at lyrasis.org 800.999.8558 x 2912 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Krista Oldham Sent: Monday, April 15, 2019 2:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Reports-time out We are running 2.3.1. It seems that we need to upgrade for sure. KRISTA OLDHAM CLEMSON UNIVERSITY University Archivist Special Collections and Archives Clemson University Libraries kristao at clemson.edu 864-656-4751 Pronouns: She, her, hers From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Blake Carver Sent: Monday, April 15, 2019 10:38 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Reports-time out What version are you running? If it's not 2.5.2 reports were pretty rough and it's not surprising that you're seeing that. Reports were redone in version 2.5.1, that fixed a bunch of troubles. It's generally a good idea to run the latest version if possible. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Krista Oldham > Sent: Monday, April 15, 2019 10:31 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Reports-time out Hello all, I have recently moved from one institutions that had ASpace to a new institutions that has ASpace and I am currently in the process of getting familiar with its set up here. One of the things that I have noticed is that our reports do not work at all. If a report run successfully, I get a ridiculously large spreadsheet that only has one row filled out sporadically. Most of the time the reports do not run successful and basically crashes the system. Can anyone tell me what we are doing wrong or what we might think about doing differently? KRISTA OLDHAM CLEMSON UNIVERSITY University Archivist Special Collections and Archives Clemson University Libraries kristao at clemson.edu 864-656-4751 Pronouns: She, her, hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Apr 15 14:22:32 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 15 Apr 2019 18:22:32 +0000 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 In-Reply-To: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> References: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> Message-ID: Patrick, Just taking a quick look at this, I wonder if the issue might have something to do with the relationship between the repository record and its corresponding corporate agent record? Do both of those records (the repository record and the corporate agent record associated with the repo that owns any affected resource records) show up fine in the staff interface? I've heard of similar issues happening, but as it's not happened in our system, I've never seen exactly what causes that problem. Do you have the ability to run SQL queries? If so, then this query should provide the URL suffix that you could use to check out the agent records that are linked to each repository record (since I don't think that the staff interface surfaces how the two records are connected): SELECT CONCAT('/agents/agent_corporate_entity/', id) AS 'url_stub' FROM agent_corporate_entity WHERE id IN (SELECT agent_representation_id FROM repository) ; I don't *think* that those corporate agent records should need to be published not to cause an error, although if that's the case then that might be a bug. I'm just curious if the agent records show up at all in the staff interface, or if editing those records (even just a meaningless edit) will solve the issue in the public interface after the indexer picks those up again. Ditto that the repository record itself might need to be re-indexed, but again, I'm just guessing since I haven't encountered this issue first hand, although I know it has impacted other folks. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Flanagan, Patrick Sent: Monday, 15 April, 2019 1:58 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then 2.1.0, to see if some aspect of the migration was responsible; but the issue remains regardless. The staff interface is not impacted to the best of my knowledge. Upon clicking any collection in thew new public interface I'm greeted with the We're sorry, but something went wrong error message. The log file indicates the following error at the same time: Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} hits=6 status=0 QTime=2 F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && @result.respond_to?(:metadata) %> [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] app/models/resource.rb:104:in `metadata' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb___128582640_2336' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/layouts/application.html.erb:24:in `_app_views_layouts_application_html_erb___683597418_2334' I investigated a little bit and found a reference to authority ID around that line. It's worth noting that this particular institution seems to have authority ID blank for every agent, which makes the record look like this in the staff interface: [cid:image001.png at 01D4F395.78816690] This aspect of the problem might be unrelated, but it was the only lead I had. Any advice would be welcome! I thought I would ask here before heading to Jira with it. Thanks, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 39697 bytes Desc: image001.png URL: From blake.carver at lyrasis.org Mon Apr 15 14:24:37 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 15 Apr 2019 18:24:37 +0000 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 In-Reply-To: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> References: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> Message-ID: We've seen this (infrequently) with upgrades from 1.5.x to 2.x: If I was a betting man, I'd bet a/the repository has lost its agent representation (which needs to be a reference to a corporate entity). If you try to view the repository in the admin "/repositories" page (that is under SYSTEM "manage repositories"), does it show everything it should? Could also be a plugin. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Flanagan, Patrick Sent: Monday, April 15, 2019 1:57 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then 2.1.0, to see if some aspect of the migration was responsible; but the issue remains regardless. The staff interface is not impacted to the best of my knowledge. Upon clicking any collection in thew new public interface I'm greeted with the We're sorry, but something went wrong error message. The log file indicates the following error at the same time: Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} hits=6 status=0 QTime=2 F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && @result.respond_to?(:metadata) %> [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] app/models/resource.rb:104:in `metadata' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb___128582640_2336' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/layouts/application.html.erb:24:in `_app_views_layouts_application_html_erb___683597418_2334' I investigated a little bit and found a reference to authority ID around that line. It's worth noting that this particular institution seems to have authority ID blank for every agent, which makes the record look like this in the staff interface: [cid:9cb69a6e-a056-46ca-bddb-34bc600b5cab] This aspect of the problem might be unrelated, but it was the only lead I had. Any advice would be welcome! I thought I would ask here before heading to Jira with it. Thanks, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-15-134634_791x377_scrot.png Type: image/png Size: 39697 bytes Desc: 2019-04-15-134634_791x377_scrot.png URL: From PJFlanagan at ship.edu Wed Apr 17 10:14:05 2019 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Wed, 17 Apr 2019 14:14:05 +0000 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 In-Reply-To: References: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu>, Message-ID: <4edffae12650430fb30d23ce9dd29d4e@ship.edu> Thanks for the information! I should have added that this repository was originally migrated from Archon, so it's possible some strangeness carried over from the migration. I ran SELECT CONCAT('/agents/agent_corporate_entity/', id) AS 'url_stub' FROM agent_corporate_entity WHERE id IN (SELECT agent_representation_id FROM repository); but received an empty set. Doing select agent_representation_id from repository; comes up with two rows of NULL. I tried editing each of the agents and saving them again, as well as the resource itself, but that didn't seem to correct it, unfortunately. If this is the issue, is there a way I can correct them in SQL en masse? As for everything showing under /repositories - I think so, but I'm not sure. It looks fine to me, unless 2.5.2 would have added more data. It looks like this: [cid:34181aac-e517-4c8a-802f-e4a857a6bbd1] It's considered repository 2 in the URLs, but that's normal for our instances. Thanks again, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver Sent: Monday, April 15, 2019 2:24:37 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 We've seen this (infrequently) with upgrades from 1.5.x to 2.x: If I was a betting man, I'd bet a/the repository has lost its agent representation (which needs to be a reference to a corporate entity). If you try to view the repository in the admin "/repositories" page (that is under SYSTEM "manage repositories"), does it show everything it should? Could also be a plugin. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Flanagan, Patrick Sent: Monday, April 15, 2019 1:57 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then 2.1.0, to see if some aspect of the migration was responsible; but the issue remains regardless. The staff interface is not impacted to the best of my knowledge. Upon clicking any collection in thew new public interface I'm greeted with the We're sorry, but something went wrong error message. The log file indicates the following error at the same time: Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} hits=6 status=0 QTime=2 F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && @result.respond_to?(:metadata) %> [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] app/models/resource.rb:104:in `metadata' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb___128582640_2336' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/layouts/application.html.erb:24:in `_app_views_layouts_application_html_erb___683597418_2334' I investigated a little bit and found a reference to authority ID around that line. It's worth noting that this particular institution seems to have authority ID blank for every agent, which makes the record look like this in the staff interface: [cid:9cb69a6e-a056-46ca-bddb-34bc600b5cab] This aspect of the problem might be unrelated, but it was the only lead I had. Any advice would be welcome! I thought I would ask here before heading to Jira with it. Thanks, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-15-134634_791x377_scrot.png Type: image/png Size: 39697 bytes Desc: 2019-04-15-134634_791x377_scrot.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-17-100245_921x414_scrot.png Type: image/png Size: 36541 bytes Desc: 2019-04-17-100245_921x414_scrot.png URL: From bdmeuse at brandeis.edu Wed Apr 17 10:34:41 2019 From: bdmeuse at brandeis.edu (Brian Meuse) Date: Wed, 17 Apr 2019 10:34:41 -0400 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 In-Reply-To: <4edffae12650430fb30d23ce9dd29d4e@ship.edu> References: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> <4edffae12650430fb30d23ce9dd29d4e@ship.edu> Message-ID: Hi, We had the same issue going from 1.5.x to 2.x. The agent_representation_id value in the repository table was null. I 'fixed' it by making a small edit to the Repository and saving it. The column then got populated. We migrated from Archon as well. I have sql dumps from each upgrade and it appears that the column was never populated to begin with. On Wed, Apr 17, 2019 at 10:14 AM Flanagan, Patrick wrote: > Thanks for the information! I should have added that this repository was > originally migrated from Archon, so it's possible some strangeness carried > over from the migration. > > > I ran *SELECT CONCAT('/agents/agent_corporate_entity/', id) AS 'url_stub' > FROM agent_corporate_entity WHERE id IN (SELECT agent_representation_id > FROM repository); *but received an empty set. Doing *select > agent_representation_id from repository;* comes up with two rows of NULL. > I tried editing each of the agents and saving them again, as well as the > resource itself, but that didn't seem to correct it, unfortunately. If this > is the issue, is there a way I can correct them in SQL en masse? > > > As for everything showing under /repositories - I think so, but I'm not > sure. It looks fine to me, unless 2.5.2 would have added more data. It > looks like this: > > > > > It's considered repository 2 in the URLs, but that's normal for our > instances. > > > Thanks again, > > > ~Patrick Flanagan > > *KLN Applications Administrator* > > *Keystone Library Network Hub* > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Blake Carver > *Sent:* Monday, April 15, 2019 2:24:37 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Unable to view collections > (public interface) after upgrading from 1.5.1 to 2.5.2 > > We've seen this (infrequently) with upgrades from 1.5.x to 2.x: If I was a > betting man, I'd bet a/the repository has lost its agent representation > (which needs to be a reference to a corporate entity). If you try to view > the repository in the admin "/repositories" page (that is under SYSTEM > "manage repositories"), does it show everything it should? > > Could also be a plugin. > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Flanagan, Patrick > *Sent:* Monday, April 15, 2019 1:57 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Unable to view collections (public > interface) after upgrading from 1.5.1 to 2.5.2 > > > I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then 2.1.0, > to see if some aspect of the migration was responsible; but the issue > remains regardless. The staff interface is not impacted to the best of my > knowledge. > > > Upon clicking any collection in thew new public interface I'm greeted with > the *We're sorry, but something went wrong* error message. The log file > indicates the following error at the same time: > > > Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute > INFO: [collection1] webapp= path=/select > params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} > hits=6 status=0 QTime=2 > F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : > [15f88748-5b17-4145-97f9-9fef25df3ba0] > F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : > [15f88748-5b17-4145-97f9-9fef25df3ba0] *ActionView::Template::Error > (undefined method `[]' for nil:NilClass):* > F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : > [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && > @result.respond_to?(:metadata) %> > [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: > [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: > [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> > F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : > [15f88748-5b17-4145-97f9-9fef25df3ba0] > F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : > [15f88748-5b17-4145-97f9-9fef25df3ba0] *app/models/resource.rb:104*:in > `metadata' > [15f88748-5b17-4145-97f9-9fef25df3ba0] > app/views/shared/_metadata.html.erb:4:in > `_app_views_shared__metadata_html_erb___128582640_2336' > [15f88748-5b17-4145-97f9-9fef25df3ba0] > app/views/layouts/application.html.erb:24:in > `_app_views_layouts_application_html_erb___683597418_2334' > > > I investigated a little bit and found a reference to authority ID around > that line. It's worth noting that this particular institution seems to have > authority ID blank for every agent, which makes the record look like this > in the staff interface: > > > > > This aspect of the problem might be unrelated, but it was the only lead I > had. > > > Any advice would be welcome! I thought I would ask here before heading to > Jira with it. > > > Thanks, > > > ~Patrick Flanagan > > *KLN Applications Administrator* > > *Keystone Library Network Hub* > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Brian Meuse, MSLIS he/him/his Digital Initiatives Librarian Brandeis University Library *Proud member of SEIU Local 888* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-15-134634_791x377_scrot.png Type: image/png Size: 39697 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-17-100245_921x414_scrot.png Type: image/png Size: 36541 bytes Desc: not available URL: From PJFlanagan at ship.edu Wed Apr 17 10:38:57 2019 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Wed, 17 Apr 2019 14:38:57 +0000 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 In-Reply-To: References: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> <4edffae12650430fb30d23ce9dd29d4e@ship.edu>, Message-ID: <2d4c26fd86eb4123bf046b50c6032eb4@ship.edu> Hi Brian, Did you make the edit in 2.x? I just tried that here in 2.5.2 and saving the repository causes the following error to fall into the log: F, [2019-04-17T10:37:57.490160 #54513] FATAL -- : F, [2019-04-17T10:37:57.492053 #54513] FATAL -- : NoMethodError (undefined method `[]=' for nil:NilClass): F, [2019-04-17T10:37:57.492728 #54513] FATAL -- : F, [2019-04-17T10:37:57.493614 #54513] FATAL -- : app/controllers/repositories_controller.rb:31:in `generate_names' app/controllers/repositories_controller.rb:70:in `update' Thanks, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Brian Meuse Sent: Wednesday, April 17, 2019 10:34:41 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 Hi, We had the same issue going from 1.5.x to 2.x. The agent_representation_id value in the repository table was null. I 'fixed' it by making a small edit to the Repository and saving it. The column then got populated. We migrated from Archon as well. I have sql dumps from each upgrade and it appears that the column was never populated to begin with. On Wed, Apr 17, 2019 at 10:14 AM Flanagan, Patrick > wrote: Thanks for the information! I should have added that this repository was originally migrated from Archon, so it's possible some strangeness carried over from the migration. I ran SELECT CONCAT('/agents/agent_corporate_entity/', id) AS 'url_stub' FROM agent_corporate_entity WHERE id IN (SELECT agent_representation_id FROM repository); but received an empty set. Doing select agent_representation_id from repository; comes up with two rows of NULL. I tried editing each of the agents and saving them again, as well as the resource itself, but that didn't seem to correct it, unfortunately. If this is the issue, is there a way I can correct them in SQL en masse? As for everything showing under /repositories - I think so, but I'm not sure. It looks fine to me, unless 2.5.2 would have added more data. It looks like this: [cid:16a2bb5605f7ff380022] It's considered repository 2 in the URLs, but that's normal for our instances. Thanks again, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Blake Carver > Sent: Monday, April 15, 2019 2:24:37 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 We've seen this (infrequently) with upgrades from 1.5.x to 2.x: If I was a betting man, I'd bet a/the repository has lost its agent representation (which needs to be a reference to a corporate entity). If you try to view the repository in the admin "/repositories" page (that is under SYSTEM "manage repositories"), does it show everything it should? Could also be a plugin. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Flanagan, Patrick > Sent: Monday, April 15, 2019 1:57 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then 2.1.0, to see if some aspect of the migration was responsible; but the issue remains regardless. The staff interface is not impacted to the best of my knowledge. Upon clicking any collection in thew new public interface I'm greeted with the We're sorry, but something went wrong error message. The log file indicates the following error at the same time: Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} hits=6 status=0 QTime=2 F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && @result.respond_to?(:metadata) %> [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : [15f88748-5b17-4145-97f9-9fef25df3ba0] app/models/resource.rb:104:in `metadata' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/shared/_metadata.html.erb:4:in `_app_views_shared__metadata_html_erb___128582640_2336' [15f88748-5b17-4145-97f9-9fef25df3ba0] app/views/layouts/application.html.erb:24:in `_app_views_layouts_application_html_erb___683597418_2334' I investigated a little bit and found a reference to authority ID around that line. It's worth noting that this particular institution seems to have authority ID blank for every agent, which makes the record look like this in the staff interface: [cid:16a2bb5605f7a0274fa1] This aspect of the problem might be unrelated, but it was the only lead I had. Any advice would be welcome! I thought I would ask here before heading to Jira with it. Thanks, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Brian Meuse, MSLIS he/him/his Digital Initiatives Librarian Brandeis University Library Proud member of SEIU Local 888 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-15-134634_791x377_scrot.png Type: image/png Size: 39697 bytes Desc: 2019-04-15-134634_791x377_scrot.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-17-100245_921x414_scrot.png Type: image/png Size: 36541 bytes Desc: 2019-04-17-100245_921x414_scrot.png URL: From Kevin.Clair at du.edu Wed Apr 17 18:12:00 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 17 Apr 2019 22:12:00 +0000 Subject: [Archivesspace_Users_Group] more punctuation issues with MARC exports In-Reply-To: References: Message-ID: Hello, We?re still encountering this MARC export error in 2.5.2; since today I had circled back to trying to figure out why it was happening, I thought I?d ping the list again to see if anyone else has encountered it. I did a little bit more testing today and it seems like we only encounter the erratic punctuation if an agent is linked more than once in a resource, and if one of the links has the role of Subject. Multiple links punctuate normally in the MARC export if their roles are Creator and Source. This continues to be the case even with all of our plugins deactivated. Happy to submit this as a bug report if others have encountered the issue. thanks! -k From: on behalf of Kevin Clair Reply-To: Archivesspace Group Date: Tuesday, December 4, 2018 at 3:58 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] more punctuation issues with MARC exports Hello, We?re testing 2.5.1 here at DU because it fixes some bugs our archivists have encountered, and in so doing I?ve found some strangeness with 110s and 610s in the MARC export. When we have resources where the same agent is a creator and a subject of the resource, the exporter will always append a comma to the name even if it?s a 610 and there?s no subfield E present, and will always append a period after the comma even if it?s a 110 and there is a subfield E present. We have some MARC export customizations in our local plugins, but this error persists even if I turn the local plugins off in our configuration. The error moves from agent to agent, e.g. if I change the creator from ?Central City Opera House Association (Central City, Colo.)? to ?Central City Opera Festival (Central City, Colo.),? the erratic punctuation in subfield A will move to the latter corporate name from the former. Attached is example output (this is from our 2.5.1 instance with no active MARC customizations). I wanted to send a note to the list to see if anyone else has seen anything similar before I submit a JIRA ticket for it. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Thu Apr 18 12:52:23 2019 From: mkottman at ku.edu (Kottman, Miloche) Date: Thu, 18 Apr 2019 16:52:23 +0000 Subject: [Archivesspace_Users_Group] Speaking of MARCXML punctuation Message-ID: <59378da8e1f1460b8f2711b46ebf9f7d@ex13-ell-cr-15.home.ku.edu> Since the PCC is starting their two phase implementation of the new policy regarding limited use of ISBD punctuation in bibliographic records, which option for ISBD punctuation will ArchivesSpace follow? Is it possible to have a configuration setting so that we can choose to determine our preference? For those who are unfamiliar with the decision regarding ISBD punctuation, I?ve copied the announcement(s) below. --Miloche ?????????????????????????????? Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 Xiaoli Li xlli at ucdavis.edu via kansas.onmicrosoft.com Apr 2, 2019, 11:04 AM to PCCLIST PCC colleagues, Last December, I announced the new policy regarding limited use of ISBD punctuation in bibliographic records. Since then, we have been working on the implementation plan. The complexity of implementing all three options outlined in that email (dated 12/12/2018 and included below) at the same time presents more challenges than we anticipated. In addition, there are issues pertinent to access point fields that require more discussion. We believe we should move forward but need to do so in a way that is manageable and will allow us to achieve some consistency. After considering all the possibilities, we have revised the policy which to address punctuation in descriptive fields only. The revised policy will be implemented in phases: Phase 1: Beginning April 8, 2019, PCC libraries will have two options regarding inclusion of terminal periods when newly authenticating bibliographic records: a. Continue current practice (fully punctuated); code Leader/18=i b. Omit terminal period in any descriptive field*; code Leader/18=i *Exception: terminal periods integral to the data (e.g., recorded as part of abbreviations, initials, etc.) should not be omitted. Special Note: when updating an existing PCC record, catalogers should follow the punctuation pattern already established in that record. The guidelines for Phase 1 and a spreadsheet containing all MARC fields that are affected by the new policy are attached to this email. Both documents have also been posted on the PCC website: * Guidelines: http://www.loc.gov/aba/pcc/documents/guidelines-terminal-periods.pdf * Spreadsheet: http://www.loc.gov/aba/pcc/documents/final_punctuation_all_MARC_field.xlsx Phase 2: [Implementation date to be determined.] PCC libraries may begin to omit ISBD punctuation between subfields and terminal period of any descriptive field as long as Leader/18 is coded as ?c?. The implementation date for Phase 2 will depend on the following: a. Completion of style guidelines containing instructions and examples b. Completion of specifications for and availability of tools for automatically removing or adding punctuation (e.g., macros for OCLC Connexion Client, etc.) Following these two phases, the Policy Committee will review the pros and cons of omitting final punctuation in access point fields. The work on the limited use of the ISBD punctuation in PCC records began in March 2011. It took many groups? work to get us to where we are now. I want to take this opportunity to express my sincere appreciation to anyone who has helped to make this happen. Please let me know if you have any questions. Xiaoli Li PCC Chair Head of Content Support Services UC Davis Library (530) 752-6735 Xiaoli Li xlli at ucdavis.edu via kansas.onmicrosoft.com Dec 12, 2018, 2:20 PM to PCCLIST PCC colleagues, At its recent meeting, the PCC Policy Committee reaffirmed its decision to allow bibliographic records with limited ISBD punctuation to be treated as full-level PCC copy. This decision comes after reviewing feedback from test participants who evaluated three test sets of records provided by Library of Congress, the National Library of Medicine, and OCLC. For more information about the test, please read the message below or click here. Beginning in spring 2019, PCC libraries will have three options to handle ISBD punctuation when authenticating new records: 1. Continue current practice 2. Omit terminal period in any field*; code Leader/18 (Descriptive cataloging form) ?i? 3. Omit ISBD punctuation between subfields of descriptive fields and omit terminal period in any field*; code Leader/18 (Descriptive cataloging form) ?c? * Exception: Terminal periods integral to the data (e.g., recorded as part of abbreviations, initials, etc.) should not be omitted. Options 2 and 3 are optional, not mandatory. However, creating records with limited punctuation is expected to save time for catalogers, simplify training of new catalogers, make it easier to map data to and from other formats, and allow for an easier transition to linked data or vice versa (e.g., mapping BIBFRAME to MARC). To facilitate the implementation, PCC will: 1. Develop and maintain style guidelines for records with limited punctuation; 2. Provide adequate training resources for catalogers and revise PCC documentation to update policies and include examples with limited punctuation; 3. Request that LC Network Development and MARC Standards Office and bibliographic utilities revise MARC 21 documentation to include examples with limited punctuation; 4. Work with bibliographic utilities and other interested parties to develop tools and specifications to automate the process of removal or reinsertion of punctuation; 5. Encourage vendors, bibliographic utilities, etc., to explore functionality to index and display records with limited punctuation as defined by the PCC; 6. Encourage vendors, bibliographic utilities, etc., to explore functionality to allow their users to easily add or remove punctuation as needed. The Policy Committee is in the process of developing a detailed implementation plan which will include the aforementioned style guidelines. I will share more information with you as it becomes available. In the meantime, if you have questions, suggestions, or comments, please feel free to contact me. Sincerely, Xiaoli Li PCC Chair Head of Content Support Services UC Davis Library (530) 752-6735 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 43 bytes Desc: image001.gif URL: From bdmeuse at brandeis.edu Thu Apr 18 13:21:44 2019 From: bdmeuse at brandeis.edu (Brian Meuse) Date: Thu, 18 Apr 2019 13:21:44 -0400 Subject: [Archivesspace_Users_Group] Unable to view collections (public interface) after upgrading from 1.5.1 to 2.5.2 In-Reply-To: <2d4c26fd86eb4123bf046b50c6032eb4@ship.edu> References: <5299cf2cd45d40feb5bf77fa958dabb6@ship.edu> <4edffae12650430fb30d23ce9dd29d4e@ship.edu> <2d4c26fd86eb4123bf046b50c6032eb4@ship.edu> Message-ID: After. I reverted my test server to 1.5.4 and re-did the upgrade to 2.5.2 and I wasn't able to recreate the problem/fix. I'm going to try stepping though releases to see if I can.... On Wed, Apr 17, 2019 at 10:39 AM Flanagan, Patrick wrote: > Hi Brian, > > > Did you make the edit in 2.x? I just tried that here in 2.5.2 and saving > the repository causes the following error to fall into the log: > > > F, [2019-04-17T10:37:57.490160 #54513] FATAL -- : > F, [2019-04-17T10:37:57.492053 #54513] FATAL -- : NoMethodError (undefined > method `[]=' for nil:NilClass): > F, [2019-04-17T10:37:57.492728 #54513] FATAL -- : > F, [2019-04-17T10:37:57.493614 #54513] FATAL -- : > app/controllers/repositories_controller.rb:31:in `generate_names' > app/controllers/repositories_controller.rb:70:in `update' > > Thanks, > > > ~Patrick Flanagan > > *KLN Applications Administrator* > > *Keystone Library Network Hub* > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Brian Meuse > *Sent:* Wednesday, April 17, 2019 10:34:41 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Unable to view collections > (public interface) after upgrading from 1.5.1 to 2.5.2 > > Hi, > > We had the same issue going from 1.5.x to 2.x. The agent_representation_id > value in the repository table was null. I 'fixed' it by making a small edit > to the Repository and saving it. The column then got populated. > > We migrated from Archon as well. I have sql dumps from each upgrade and it > appears that the column was never populated to begin with. > > On Wed, Apr 17, 2019 at 10:14 AM Flanagan, Patrick > wrote: > >> Thanks for the information! I should have added that this repository was >> originally migrated from Archon, so it's possible some strangeness carried >> over from the migration. >> >> >> I ran *SELECT CONCAT('/agents/agent_corporate_entity/', id) AS >> 'url_stub' FROM agent_corporate_entity WHERE id IN (SELECT >> agent_representation_id FROM repository); *but received an empty set. >> Doing *select agent_representation_id from repository;* comes up with >> two rows of NULL. I tried editing each of the agents and saving them again, >> as well as the resource itself, but that didn't seem to correct it, >> unfortunately. If this is the issue, is there a way I can correct them in >> SQL en masse? >> >> >> As for everything showing under /repositories - I think so, but I'm not >> sure. It looks fine to me, unless 2.5.2 would have added more data. It >> looks like this: >> >> >> >> >> It's considered repository 2 in the URLs, but that's normal for our >> instances. >> >> >> Thanks again, >> >> >> ~Patrick Flanagan >> >> *KLN Applications Administrator* >> >> *Keystone Library Network Hub* >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Blake Carver >> *Sent:* Monday, April 15, 2019 2:24:37 PM >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] Unable to view collections >> (public interface) after upgrading from 1.5.1 to 2.5.2 >> >> We've seen this (infrequently) with upgrades from 1.5.x to 2.x: If I was >> a betting man, I'd bet a/the repository has lost its agent representation >> (which needs to be a reference to a corporate entity). If you try to view >> the repository in the admin "/repositories" page (that is under SYSTEM >> "manage repositories"), does it show everything it should? >> >> Could also be a plugin. >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Flanagan, Patrick >> *Sent:* Monday, April 15, 2019 1:57 PM >> *To:* archivesspace_users_group at lyralists.lyrasis.org >> *Subject:* [Archivesspace_Users_Group] Unable to view collections >> (public interface) after upgrading from 1.5.1 to 2.5.2 >> >> >> I've also attempted to step the upgrades down to 2.5.1, 2.4.0, then >> 2.1.0, to see if some aspect of the migration was responsible; but the >> issue remains regardless. The staff interface is not impacted to the best >> of my knowledge. >> >> >> Upon clicking any collection in thew new public interface I'm greeted >> with the *We're sorry, but something went wrong* error message. The log >> file indicates the following error at the same time: >> >> >> Apr 15, 2019 11:28:16 AM org.apache.solr.core.SolrCore execute >> INFO: [collection1] webapp= path=/select >> params={facet=true&start=0&csv.encapsulator="&q=(id:("\/repositories\/2\/top_containers\/1143")+OR+id:("\/repositories\/2\/top_containers\/1144")+OR+id:("\/repositories\/2\/top_containers\/1145")+OR+id:("\/repositories\/2\/top_containers\/1146")+OR+id:("\/repositories\/2\/top_containers\/1147")+OR+id:("\/repositories\/2\/top_containers\/1149"))&q.op=AND&csv.header=true&csv.escape=\&wt=json&fq=-exclude_by_default:true&fq=suppressed:false&rows=500} >> hits=6 status=0 QTime=2 >> F, [2019-04-15T11:28:16.525748 #54143] FATAL -- : >> [15f88748-5b17-4145-97f9-9fef25df3ba0] >> F, [2019-04-15T11:28:16.526196 #54143] FATAL -- : >> [15f88748-5b17-4145-97f9-9fef25df3ba0] *ActionView::Template::Error >> (undefined method `[]' for nil:NilClass):* >> F, [2019-04-15T11:28:16.527030 #54143] FATAL -- : >> [15f88748-5b17-4145-97f9-9fef25df3ba0] 1: <% if @result && >> @result.respond_to?(:metadata) %> >> [15f88748-5b17-4145-97f9-9fef25df3ba0] 2: >> [15f88748-5b17-4145-97f9-9fef25df3ba0] 3: >> [15f88748-5b17-4145-97f9-9fef25df3ba0] 6: <% end %> >> F, [2019-04-15T11:28:16.527849 #54143] FATAL -- : >> [15f88748-5b17-4145-97f9-9fef25df3ba0] >> F, [2019-04-15T11:28:16.528196 #54143] FATAL -- : >> [15f88748-5b17-4145-97f9-9fef25df3ba0] *app/models/resource.rb:104*:in >> `metadata' >> [15f88748-5b17-4145-97f9-9fef25df3ba0] >> app/views/shared/_metadata.html.erb:4:in >> `_app_views_shared__metadata_html_erb___128582640_2336' >> [15f88748-5b17-4145-97f9-9fef25df3ba0] >> app/views/layouts/application.html.erb:24:in >> `_app_views_layouts_application_html_erb___683597418_2334' >> >> >> I investigated a little bit and found a reference to authority ID around >> that line. It's worth noting that this particular institution seems to have >> authority ID blank for every agent, which makes the record look like this >> in the staff interface: >> >> >> >> >> This aspect of the problem might be unrelated, but it was the only lead I >> had. >> >> >> Any advice would be welcome! I thought I would ask here before heading to >> Jira with it. >> >> >> Thanks, >> >> >> ~Patrick Flanagan >> >> *KLN Applications Administrator* >> >> *Keystone Library Network Hub* >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Brian Meuse, MSLIS > he/him/his > > Digital Initiatives Librarian > Brandeis University Library > > *Proud member of SEIU Local 888* > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Brian Meuse, MSLIS he/him/his Digital Initiatives Librarian Brandeis University Library *Proud member of SEIU Local 888* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-15-134634_791x377_scrot.png Type: image/png Size: 39697 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-04-17-100245_921x414_scrot.png Type: image/png Size: 36541 bytes Desc: not available URL: From mmcderm2 at bowdoin.edu Fri Apr 19 11:37:20 2019 From: mmcderm2 at bowdoin.edu (mmcderm2 at bowdoin.edu) Date: Fri, 19 Apr 2019 15:37:20 +0000 Subject: [Archivesspace_Users_Group] Importing from AT to AS - File Versions left unpublished Message-ID: Greetings all We are in the process of moving from Archivists Toolkit to ArchiveSpace. I've been experimenting with using the AT migration plugin and everything seems to be working fine, but... When we export an EAD file from ArchivesSpace and convert it to an html web page, the EAD file contains limited information about the DAOs attached to a resource. It seems that when the resources are imported from AT the digital objects are set to 'published', but the individual File Versions in the DAOs are not set to 'published' - that field seems to be null instead of 'true' or 'false' I tried just running an SQL query to set all of those file version 'published' fields to true... and that value shows up in the staff interface, but when I export the EAD I am still getting the DAO information as if the file versions are unpublished. I need to go into each digital object individually and re-save it for the change in the file version status to take effect. I tried the 'Publish All' option for the resource but that didn't seem to make the export function see the file versions as published. If I check the 'include unpublished' option in the EAD export function, I get the right DAO information, but I also get a bunch of other unpublished information in the EAD that displays in odd places in the converted HTML page. We've tried creating digital objects in ArchiveSpace and the file versions are set to published there - so this would be a one time solution to fix the resources exported from Archivists Toolkit. Is there something I can do in the export plugin that would set this value by default? Or is there a way I can force ArchivesSpace to batch publish the file versions? Or to notice the externally set published status? Thank you for any thoughts on this... Mike McDermott Bowdoin College Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Apr 19 12:22:09 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 19 Apr 2019 16:22:09 +0000 Subject: [Archivesspace_Users_Group] Importing from AT to AS - File Versions left unpublished In-Reply-To: References: Message-ID: > On Apr 19, 2019, at 11:37 AM, mmcderm2 at bowdoin.edu wrote: > > Greetings all > We are in the process of moving from Archivists Toolkit to ArchiveSpace. I?ve been experimenting with using the AT migration plugin and everything seems to be working fine, but? > When we export an EAD file from ArchivesSpace and convert it to an html web page, the EAD file contains limited information about the DAOs attached to a resource. > It seems that when the resources are imported from AT the digital objects are set to ?published?, but the individual File Versions in the DAOs are not set to ?published? ? that field seems to be null instead of ?true? or ?false? > I tried just running an SQL query to set all of those file version ?published? fields to true? and that value shows up in the staff interface, but when I export the EAD I am still getting the DAO information as if the file versions are unpublished. I need to go into each digital object individually and re-save it for the change in the file version status to take effect. > I tried the ?Publish All? option for the resource but that didn?t seem to make the export function see the file versions as published. Changing values directly in SQL bypasses the step where a reindex of that resource is triggered after editing and saving it, So there is a mismatch between the values in MySQL DB and the PUI SOLR index. Manually re-saving it triggers the reindex. Instead of manually saving each one, you can trigger a complete reindex by deleting the files in archivesspace/data/indexer_pui_state and archivesspace/data/indexer_state and restarting the server. This is something that should always(*) be done if you are going behind the usual system checks by making changes directly in MySQL DB. [ (*) I?m sure there are a few cases where it doesn?t matter, but safer to reindex if you?re not sure. ] > If I check the ?include unpublished? option in the EAD export function, I get the right DAO information, but I also get a bunch of other unpublished information in the EAD that displays in odd places in the converted HTML page. > > We?ve tried creating digital objects in ArchiveSpace and the file versions are set to published there ? so this would be a one time solution to fix the resources exported from Archivists Toolkit. > Is there something I can do in the export plugin that would set this value by default? > Or is there a way I can force ArchivesSpace to batch publish the file versions? Or to notice the externally set published status? > Thank you for any thoughts on this? > > Mike McDermott > Bowdoin College Library > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From freya.anderson at alaska.gov Fri Apr 19 14:12:27 2019 From: freya.anderson at alaska.gov (Anderson, Freya N (EED)) Date: Fri, 19 Apr 2019 18:12:27 +0000 Subject: [Archivesspace_Users_Group] default rights statement Message-ID: Hello all, We're in the process of starting up with ArchivesSpace, using a hosted instance. We'd like to set a default rights statement, that can be overridden in those few cases where we have something different, but while I'm pretty sure I found where each staff person can set a field default for their own work, I've not been able to find how to do this for the whole repository. We're moving over from PDF finding aids and have minimal tech support in house, so I'm really hoping this is doable without coding! Thanks for any suggestions or guidance! Freya [cid:image001.png at 01D422A1.1644BE70] Freya Anderson Head, Information Services Acting Head, Historical Collections Regional Librarian, Talking Book Center phone: 907.465.1315 Andrew P. Kashevaroff Building Mail: PO Box 110571, Juneau, AK 99811 Visit: 395 Whittier St., Juneau, AK 99801 email | web | sign up for event notifications -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT15888 1.jpg Type: image/jpeg Size: 7536 bytes Desc: ATT15888 1.jpg URL: From sdm7g at virginia.edu Fri Apr 19 19:17:24 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 19 Apr 2019 23:17:24 +0000 Subject: [Archivesspace_Users_Group] A more forgiving version of oai-harvest & public OAI feeds Message-ID: <7F66E65C-C224-446B-9E2F-452484187538@virginia.edu> I have a fork of python oai-harvest program that is more forgiving of XML parser errors which are typically coming from unescaped ampersands in ArchivesSpace notes text or in query strings embedded in URLs. It will also recover from other XML errors I?ve seen in the wild from ArchivesSpace exports, like undeclared namespaces or undefined character entities. Typically, how it handles and recovers from errors is to drop the node ( text, attribute, element ) that doesn?t parse correctly, so for example ?Jones & Smith? will become ?Jones Smith? , or ?AT&T? may be output as ?AT? , so the data will be incorrect, however you will get well formed EAD output, and what?s more important, the harvester will continue harvesting to completion instead of raising an XMLParser exception and quiting. The program will log recoverable errors in case you want to notify the upstream feed so they can fix their resources. ( Although I believe a fix for the unescaped ampersand issue may be in the next ArchivesSpace release. ) I have submitted a pull request upstream, but in the mean time you can install it will pip or pip3 with this command: pip3 install git+https://github.com/sdm7g/oai-harvest.git at fix-pyoai ( fix-pyoai branch is required. ) This version of the program has added another optional argument: ?recover that enables that parser option. For example ( where $URL= url of public OAI endpoint ): oai-harvest -p oai_ead -s collection --subdirs-on ':' ?recover $URL Or what is better, use the oai-reg program to create a registry database of feeds so you can use ?all? instead of a specific URL and also do incremental harvesting. ( The registry database stores the date and time of last harvest. ) The ?subdirs-on ?:? option in not required, but it will split the OAI identifiers on both ?:? and ?/? , and result in a directory tree starting at $PWD/oai/ instead of a flat collection of files. My current collection of feeds is: export VT=https://aspace.lib.vt.edu:8082/ export VMFA=https://archives.vmfa.museum/oai export JMU=https://aspace.lib.jmu.edu/oai export VCU=https://archives.library.vcu.edu/oai export UVA=https://archives-oai.lib.virginia.edu If you submit your public ArchivesSpace OAI endpoint URLs as reply to this thread, I will collect them to put on the Wiki somewhere. ? Steve Majewski -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From freya.anderson at alaska.gov Sat Apr 20 14:36:32 2019 From: freya.anderson at alaska.gov (Anderson, Freya N (EED)) Date: Sat, 20 Apr 2019 18:36:32 +0000 Subject: [Archivesspace_Users_Group] default rights statement In-Reply-To: References: Message-ID: Don?t you hate it when you ask a question, and then the next day you figure out the answer? I had been looking at the instructions for doing this, and they didn?t seem to work, but today, I figured out the one step I was missing. In other words, never mind. ? Freya From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Anderson, Freya N (EED) Sent: Friday, April 19, 2019 10:12 AM To: 'Archivesspace Users Group' Subject: [Archivesspace_Users_Group] default rights statement Hello all, We're in the process of starting up with ArchivesSpace, using a hosted instance. We'd like to set a default rights statement, that can be overridden in those few cases where we have something different, but while I'm pretty sure I found where each staff person can set a field default for their own work, I've not been able to find how to do this for the whole repository. We're moving over from PDF finding aids and have minimal tech support in house, so I'm really hoping this is doable without coding! Thanks for any suggestions or guidance! Freya [cid:image001.png at 01D422A1.1644BE70][cid:image001.jpg at 01D4F764.EB316460] Freya Anderson Head, Information Services Acting Head, Historical Collections Regional Librarian, Talking Book Center phone: 907.465.1315 Andrew P. Kashevaroff Building Mail: PO Box 110571, Juneau, AK 99811 Visit: 395 Whittier St., Juneau, AK 99801 email | web | sign up for event notifications -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 7536 bytes Desc: image001.jpg URL: From duprel at email.sc.edu Mon Apr 22 09:38:37 2019 From: duprel at email.sc.edu (DUPRE, LANCE) Date: Mon, 22 Apr 2019 13:38:37 +0000 Subject: [Archivesspace_Users_Group] Spam through the Request button Message-ID: <0C8A4014-8A51-4456-AF63-7488146EC745@email.sc.edu> Forgive is this is a reposting, I have reason to believe my original post didn?t go through? I remember there was a post about spam being sent through the request feature in Archivesspace a few months back. Does anyone have a solution to this they are willing to share? From harmeyna at purdue.edu Mon Apr 22 13:28:22 2019 From: harmeyna at purdue.edu (Harmeyer, Neal A) Date: Mon, 22 Apr 2019 17:28:22 +0000 Subject: [Archivesspace_Users_Group] Spam through the Request button In-Reply-To: <0C8A4014-8A51-4456-AF63-7488146EC745@email.sc.edu> References: <0C8A4014-8A51-4456-AF63-7488146EC745@email.sc.edu> Message-ID: Hi all, I initiated a previous message regarding spam via the request button. We do not have the IT resources locally to tackle the issue, which persists. I would very much welcome any ideas or solutions to this problem as well. Thank you, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of DUPRE, LANCE Sent: Monday, April 22, 2019 9:39 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Spam through the Request button Forgive is this is a reposting, I have reason to believe my original post didn?t go through? I remember there was a post about spam being sent through the request feature in Archivesspace a few months back. Does anyone have a solution to this they are willing to share? _______________________________________________ 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 Mon Apr 22 14:17:22 2019 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Mon, 22 Apr 2019 18:17:22 +0000 Subject: [Archivesspace_Users_Group] Spam through the Request button In-Reply-To: References: <0C8A4014-8A51-4456-AF63-7488146EC745@email.sc.edu> Message-ID: <1EBB2DED-0B9A-47EA-BB89-01F9C17224F9@lib.msu.edu> We ended up disabling the request button also because of this (and we are hoping to get the Aeon plug in to work? one of these days) at MSU Special Collections. I wonder if a reCAPTCHA feature would help with scenarios like these? Lydia From larry.weimer at nyhistory.org Mon Apr 22 14:33:38 2019 From: larry.weimer at nyhistory.org (Larry Weimer) Date: Mon, 22 Apr 2019 14:33:38 -0400 Subject: [Archivesspace_Users_Group] Spam through the Request button In-Reply-To: References: <0C8A4014-8A51-4456-AF63-7488146EC745@email.sc.edu> Message-ID: Hi Neal New-York Historical also disabled the request feature. Unfortunately I can't tell you how that is done because it was done by Atlas Systems, our systems host. . Larry Larry Weimer Head of Archival Processing New-York Historical Society On Mon, Apr 22, 2019 at 1:28 PM Harmeyer, Neal A wrote: > Hi all, > > > > I initiated a previous message regarding spam via the request button. We > do not have the IT resources locally to tackle the issue, which persists. I > would very much welcome any ideas or solutions to this problem as well. > > > > Thank you, > > Neal > > -- > > Neal Harmeyer > > Digital Archivist > > Purdue University Archives and Special Collections > > harmeyna at purdue.edu > > > > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of > DUPRE, LANCE > Sent: Monday, April 22, 2019 9:39 AM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Spam through the Request button > > > > Forgive is this is a reposting, I have reason to believe my original post > didn?t go through? > > > > I remember there was a post about spam being sent through the request > feature in Archivesspace a few months back. Does anyone have a solution to > this they are willing to share? > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmcderm2 at bowdoin.edu Tue Apr 23 09:27:51 2019 From: mmcderm2 at bowdoin.edu (mmcderm2 at bowdoin.edu) Date: Tue, 23 Apr 2019 13:27:51 +0000 Subject: [Archivesspace_Users_Group] Importing from AT to AS - File Versions left unpublished In-Reply-To: References: Message-ID: <76641fe1db2e4fd09860639cc7e7e81b@p-exch2013-c.bowdoincollege.edu> Thank you very much ? forcing a complete re-index did the trick. I?ll keep it in mind if we need to change things from outside the interface. Mike McDermott Bowdoin College Library From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Friday, April 19, 2019 12:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Importing from AT to AS - File Versions left unpublished On Apr 19, 2019, at 11:37 AM, mmcderm2 at bowdoin.edu wrote: Greetings all We are in the process of moving from Archivists Toolkit to ArchiveSpace. I?ve been experimenting with using the AT migration plugin and everything seems to be working fine, but? When we export an EAD file from ArchivesSpace and convert it to an html web page, the EAD file contains limited information about the DAOs attached to a resource. It seems that when the resources are imported from AT the digital objects are set to ?published?, but the individual File Versions in the DAOs are not set to ?published? ? that field seems to be null instead of ?true? or ?false? I tried just running an SQL query to set all of those file version ?published? fields to true? and that value shows up in the staff interface, but when I export the EAD I am still getting the DAO information as if the file versions are unpublished. I need to go into each digital object individually and re-save it for the change in the file version status to take effect. I tried the ?Publish All? option for the resource but that didn?t seem to make the export function see the file versions as published. Changing values directly in SQL bypasses the step where a reindex of that resource is triggered after editing and saving it, So there is a mismatch between the values in MySQL DB and the PUI SOLR index. Manually re-saving it triggers the reindex. Instead of manually saving each one, you can trigger a complete reindex by deleting the files in archivesspace/data/indexer_pui_state and archivesspace/data/indexer_state and restarting the server. This is something that should always(*) be done if you are going behind the usual system checks by making changes directly in MySQL DB. [ (*) I?m sure there are a few cases where it doesn?t matter, but safer to reindex if you?re not sure. ] If I check the ?include unpublished? option in the EAD export function, I get the right DAO information, but I also get a bunch of other unpublished information in the EAD that displays in odd places in the converted HTML page. We?ve tried creating digital objects in ArchiveSpace and the file versions are set to published there ? so this would be a one time solution to fix the resources exported from Archivists Toolkit. Is there something I can do in the export plugin that would set this value by default? Or is there a way I can force ArchivesSpace to batch publish the file versions? Or to notice the externally set published status? Thank you for any thoughts on this? Mike McDermott Bowdoin College Library _______________________________________________ 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 kbatyuk at whoi.edu Tue Apr 23 10:37:21 2019 From: kbatyuk at whoi.edu (Kirill Batyuk) Date: Tue, 23 Apr 2019 10:37:21 -0400 Subject: [Archivesspace_Users_Group] ead_export.sh question Message-ID: <00b801d4f9e2$0f2ed6c0$2d8c8440$@whoi.edu> Hello everyone, I have a question about ead_export script. When I try to run it I get an error message (See below). Have anyone encountered it before and if so, have you been able to solve it? ./ead_export.sh USR PW 3 Loading ArchivesSpace configuration file from path: /data/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /data/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /data/archivesspace/config/config.rb Net::ReadTimeout: Net::ReadTimeout rbuf_fill at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/protocol.rb:158 readuntil at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/protocol.rb:136 readline at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/protocol.rb:146 read_status_line at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http/response.rb:40 read_new at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http/response.rb:29 block in transport_request at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1448 catch at org/jruby/RubyKernel.java:1138 transport_request at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1445 request at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1418 block in request at /data/archivesspace/launcher/request_handler.rb:32 block in start_uri at uri:classloader:/ashttp.rb:11 start at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:858 start at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:585 start_uri at uri:classloader:/ashttp.rb:10 request at /data/archivesspace/launcher/request_handler.rb:31 post at /data/archivesspace/launcher/request_handler.rb:26 login at /data/archivesspace/launcher/request_handler.rb:11 main at ../launcher/ead_export/lib/ead_export.rb:38
at ../launcher/ead_export/lib/ead_export.rb:68 Thank you, Kirill Batyuk Systems Librarian MBLWHOI Library Data Library and Archives Woods Hole Oceanographic Institution 508-289-2850 kbatyuk at whoi.edu mblwhoilibrary.org --- whoi.edu ORCID -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5508 bytes Desc: not available URL: From Kevin.Clair at du.edu Thu Apr 25 12:00:10 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 25 Apr 2019 16:00:10 +0000 Subject: [Archivesspace_Users_Group] Suppressed record search bug Message-ID: Hello, We recently discovered an issue with searching for records that are suppressed in the staff interface. In our instance, administrative users are able to do known-item searches for suppressed records without incident; if a user without administrative permissions performs the same search, they get thrown an error with the following stack trace: I, [2019-04-25T09:47:26.038804 #18125] INFO -- : Completed 500 Internal Server Error in 1163ms F, [2019-04-25T09:47:26.041948 #18125] FATAL -- : F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = context_ancestor(result) %> 2: <% if ancestors != nil && ancestors != [''] %> 3: <% ancestors.reverse.each_with_index do |ancestor, i| %> 4: <%= resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %> 5: <% if i < ancestors.length - 1 %> 6: <%= context_separator(result) %> 7: <% end %> F, [2019-04-25T09:47:26.042340 #18125] FATAL -- : F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : app/helpers/search_helper.rb:198:in `get_ancestor_title' app/views/search/_context.html.erb:4:in `block in _app_views_search__context_html_erb___234296763_2752' app/views/search/_context.html.erb:3:in `_app_views_search__context_html_erb___234296763_2752' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_listing.html.erb:90:in `block in _app_views_search__listing_html_erb___1981573825_2748' app/views/search/_listing.html.erb:52:in `_app_views_search__listing_html_erb___1981573825_2748' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_results.html.erb:23:in `_app_views_search__results_html_erb___1135689531_2744' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/do_search.html.erb:16:in `_app_views_search_do_search_html_erb__585907251_2742' Checking in to see if anyone else has noticed similar behavior and if there?s a bug report for this in Jira already. I did a quick search just now but couldn?t find anything that looked similar to this. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Apr 25 12:08:28 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 25 Apr 2019 16:08:28 +0000 Subject: [Archivesspace_Users_Group] Suppressed record search bug Message-ID: I should also say that the search that prompted this also returns a component_transfer event of records that were moved from the suppressed Resource to another Resource. So it may be that it?s an issue with suppressed records appearing in the ?Found In? column of another record?s result summary, rather than with the suppressed record itself? -k From: on behalf of Kevin Clair Reply-To: Archivesspace Group Date: Thursday, April 25, 2019 at 10:00 AM To: Archivesspace Group Subject: [Archivesspace_Users_Group] Suppressed record search bug Hello, We recently discovered an issue with searching for records that are suppressed in the staff interface. In our instance, administrative users are able to do known-item searches for suppressed records without incident; if a user without administrative permissions performs the same search, they get thrown an error with the following stack trace: I, [2019-04-25T09:47:26.038804 #18125] INFO -- : Completed 500 Internal Server Error in 1163ms F, [2019-04-25T09:47:26.041948 #18125] FATAL -- : F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = context_ancestor(result) %> 2: <% if ancestors != nil && ancestors != [''] %> 3: <% ancestors.reverse.each_with_index do |ancestor, i| %> 4: <%= resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %> 5: <% if i < ancestors.length - 1 %> 6: <%= context_separator(result) %> 7: <% end %> F, [2019-04-25T09:47:26.042340 #18125] FATAL -- : F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : app/helpers/search_helper.rb:198:in `get_ancestor_title' app/views/search/_context.html.erb:4:in `block in _app_views_search__context_html_erb___234296763_2752' app/views/search/_context.html.erb:3:in `_app_views_search__context_html_erb___234296763_2752' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_listing.html.erb:90:in `block in _app_views_search__listing_html_erb___1981573825_2748' app/views/search/_listing.html.erb:52:in `_app_views_search__listing_html_erb___1981573825_2748' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_results.html.erb:23:in `_app_views_search__results_html_erb___1135689531_2744' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/do_search.html.erb:16:in `_app_views_search_do_search_html_erb__585907251_2742' Checking in to see if anyone else has noticed similar behavior and if there?s a bug report for this in Jira already. I did a quick search just now but couldn?t find anything that looked similar to this. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Thu Apr 25 12:28:07 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 25 Apr 2019 16:28:07 +0000 Subject: [Archivesspace_Users_Group] Suppressed record search bug In-Reply-To: References: Message-ID: What version are you on? That looks similar to a bug that should've been fixed in 2.5.2. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin Clair Sent: Thursday, April 25, 2019 12:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug I should also say that the search that prompted this also returns a component_transfer event of records that were moved from the suppressed Resource to another Resource. So it may be that it?s an issue with suppressed records appearing in the ?Found In? column of another record?s result summary, rather than with the suppressed record itself? -k From: on behalf of Kevin Clair Reply-To: Archivesspace Group Date: Thursday, April 25, 2019 at 10:00 AM To: Archivesspace Group Subject: [Archivesspace_Users_Group] Suppressed record search bug Hello, We recently discovered an issue with searching for records that are suppressed in the staff interface. In our instance, administrative users are able to do known-item searches for suppressed records without incident; if a user without administrative permissions performs the same search, they get thrown an error with the following stack trace: I, [2019-04-25T09:47:26.038804 #18125] INFO -- : Completed 500 Internal Server Error in 1163ms F, [2019-04-25T09:47:26.041948 #18125] FATAL -- : F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = context_ancestor(result) %> 2: <% if ancestors != nil && ancestors != [''] %> 3: <% ancestors.reverse.each_with_index do |ancestor, i| %> 4: <%= resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %> 5: <% if i < ancestors.length - 1 %> 6: <%= context_separator(result) %> 7: <% end %> F, [2019-04-25T09:47:26.042340 #18125] FATAL -- : F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : app/helpers/search_helper.rb:198:in `get_ancestor_title' app/views/search/_context.html.erb:4:in `block in _app_views_search__context_html_erb___234296763_2752' app/views/search/_context.html.erb:3:in `_app_views_search__context_html_erb___234296763_2752' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_listing.html.erb:90:in `block in _app_views_search__listing_html_erb___1981573825_2748' app/views/search/_listing.html.erb:52:in `_app_views_search__listing_html_erb___1981573825_2748' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_results.html.erb:23:in `_app_views_search__results_html_erb___1135689531_2744' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/do_search.html.erb:16:in `_app_views_search_do_search_html_erb__585907251_2742' Checking in to see if anyone else has noticed similar behavior and if there?s a bug report for this in Jira already. I did a quick search just now but couldn?t find anything that looked similar to this. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Apr 25 12:37:33 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 25 Apr 2019 16:37:33 +0000 Subject: [Archivesspace_Users_Group] Suppressed record search bug In-Reply-To: References: Message-ID: <048AC982-DD2B-4807-92BB-D5940A9946B5@du.edu> We?re on 2.5.2 now. We upgraded because of that bug; that?s why I thought the problem could be with the event record instead of the resource. -k From: on behalf of Blake Carver Reply-To: Archivesspace Group Date: Thursday, April 25, 2019 at 10:28 AM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug What version are you on? That looks similar to a bug that should've been fixed in 2.5.2. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin Clair Sent: Thursday, April 25, 2019 12:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug I should also say that the search that prompted this also returns a component_transfer event of records that were moved from the suppressed Resource to another Resource. So it may be that it?s an issue with suppressed records appearing in the ?Found In? column of another record?s result summary, rather than with the suppressed record itself? -k From: on behalf of Kevin Clair Reply-To: Archivesspace Group Date: Thursday, April 25, 2019 at 10:00 AM To: Archivesspace Group Subject: [Archivesspace_Users_Group] Suppressed record search bug Hello, We recently discovered an issue with searching for records that are suppressed in the staff interface. In our instance, administrative users are able to do known-item searches for suppressed records without incident; if a user without administrative permissions performs the same search, they get thrown an error with the following stack trace: I, [2019-04-25T09:47:26.038804 #18125] INFO -- : Completed 500 Internal Server Error in 1163ms F, [2019-04-25T09:47:26.041948 #18125] FATAL -- : F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = context_ancestor(result) %> 2: <% if ancestors != nil && ancestors != [''] %> 3: <% ancestors.reverse.each_with_index do |ancestor, i| %> 4: <%= resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %> 5: <% if i < ancestors.length - 1 %> 6: <%= context_separator(result) %> 7: <% end %> F, [2019-04-25T09:47:26.042340 #18125] FATAL -- : F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : app/helpers/search_helper.rb:198:in `get_ancestor_title' app/views/search/_context.html.erb:4:in `block in _app_views_search__context_html_erb___234296763_2752' app/views/search/_context.html.erb:3:in `_app_views_search__context_html_erb___234296763_2752' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_listing.html.erb:90:in `block in _app_views_search__listing_html_erb___1981573825_2748' app/views/search/_listing.html.erb:52:in `_app_views_search__listing_html_erb___1981573825_2748' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_results.html.erb:23:in `_app_views_search__results_html_erb___1135689531_2744' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/do_search.html.erb:16:in `_app_views_search_do_search_html_erb__585907251_2742' Checking in to see if anyone else has noticed similar behavior and if there?s a bug report for this in Jira already. I did a quick search just now but couldn?t find anything that looked similar to this. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneal at richmond.edu Fri Apr 26 08:50:27 2019 From: rneal at richmond.edu (Neal, Rick) Date: Fri, 26 Apr 2019 12:50:27 +0000 Subject: [Archivesspace_Users_Group] Issue after patching server Message-ID: Good morning, I patched my AS test server yesterday and rebooted. Afterward, ArchivesSpace is experiencing issues without being able to list its repositories in the Public interface. I also cannot log in to my user account in the Staff interface. I am running version 2.5.0. The log output is at the bottom of this email. Any help will be greatly appreciated as I need to patch the production server and won?t even try that until I figure this out. Have a great day and a wonderful weekend! Rick Neal [cid:image003.jpg at 01D4FC0D.17530C40] It ?feels? like some kind of database issue but I don?t see it in the log. [cid:image005.jpg at 01D4FC0D.17530C40] ArchivesSpace.out output: Apr 26, 2019 8:36:30 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={csv.escape=\&start=0&q.op=AND&sort=repo_sort+asc&fq=-exclude_by_default:true&fq=publish:true&rows=100&q=primary_type:repository&defType=edismax&qf=four_part_id^3+title^2+finding_aid_filing_title^2+fullrecord&pf=four_part_id^4&csv.header=true&csv.encapsulator="&wt=json&facet=true} hits=3 status=0 QTime=69 Apr 26, 2019 8:38:03 AM org.apache.solr.request.UnInvertedField INFO: UnInverted multi-valued field {field=subjects,memSize=13067,tindexSize=54,time=3,phase1=3,nTerms=34,bigTerms=0,termInstances=50,uses=0} Apr 26, 2019 8:38:03 AM org.apache.solr.request.UnInvertedField INFO: UnInverted multi-valued field {field=published_agents,memSize=4288,tindexSize=0,time=0,phase1=0,nTerms=0,bigTerms=0,termInstances=0,uses=0} Apr 26, 2019 8:38:03 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={facet.field=repository&facet.field=primary_type&facet.field=subjects&facet.field=published_agents&csv.escape=\&start=0&q.op=AND&fq=((types:("subject")+OR+(types:("classification")+OR+(types:("accession")+OR+(types:("repository")+OR+(types:("resource")+OR+(types:("agent")+OR+(types:("digital_object")+OR+(types:("archival_object"))))))))))&fq=-exclude_by_default:true&fq=publish:true&sort=&rows=10&q=(publish:(true)+AND+(types:(pui)+AND+((fullrecord:(the)))))&facet.limit=100&csv.header=true&csv.encapsulator="&facet.mincount=0&wt=json&facet=true} hits=0 status=0 QTime=80 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rick Neal Library Applications and Systems Administrator Boatwright Memorial Library University of Richmond, VA 23173 rneal at richmond.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 5975 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 11943 bytes Desc: image005.jpg URL: From sdm7g at virginia.edu Fri Apr 26 10:42:09 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 26 Apr 2019 14:42:09 +0000 Subject: [Archivesspace_Users_Group] Issue after patching server In-Reply-To: References: Message-ID: Any problems in the earliest part of the log file, when ArchivesSpace is staring up ? For the PUI problem, I would usually think deleting the files in archivesspace/data/indexer_pui_state/ to trigger a reindex might be what is needed, but if you?re locked out of Staff login, something else is clearly wrong. Can you access the backend api ? ? Steve Majewski > On Apr 26, 2019, at 8:50 AM, Neal, Rick wrote: > > Good morning, > > I patched my AS test server yesterday and rebooted. Afterward, ArchivesSpace is experiencing issues without being able to list its repositories in the Public interface. I also cannot log in to my user account in the Staff interface. > > I am running version 2.5.0. The log output is at the bottom of this email. > > Any help will be greatly appreciated as I need to patch the production server and won?t even try that until I figure this out. > > Have a great day and a wonderful weekend! > > Rick Neal > > > > > > > It ?feels? like some kind of database issue but I don?t see it in the log. > > > > > ArchivesSpace.out output: > > Apr 26, 2019 8:36:30 AM org.apache.solr.core.SolrCore execute > INFO: [collection1] webapp= path=/select params={csv.escape=\&start=0&q.op=AND&sort=repo_sort+asc&fq=-exclude_by_default:true&fq=publish:true&rows=100&q=primary_type:repository&defType=edismax&qf=four_part_id^3+title^2+finding_aid_filing_title^2+fullrecord&pf=four_part_id^4&csv.header=true&csv.encapsulator="&wt=json&facet=true} hits=3 status=0 QTime=69 > Apr 26, 2019 8:38:03 AM org.apache.solr.request.UnInvertedField > INFO: UnInverted multi-valued field {field=subjects,memSize=13067,tindexSize=54,time=3,phase1=3,nTerms=34,bigTerms=0,termInstances=50,uses=0} > Apr 26, 2019 8:38:03 AM org.apache.solr.request.UnInvertedField > INFO: UnInverted multi-valued field {field=published_agents,memSize=4288,tindexSize=0,time=0,phase1=0,nTerms=0,bigTerms=0,termInstances=0,uses=0} > Apr 26, 2019 8:38:03 AM org.apache.solr.core.SolrCore execute > INFO: [collection1] webapp= path=/select params={facet.field=repository&facet.field=primary_type&facet.field=subjects&facet.field=published_agents&csv.escape=\&start=0&q.op=AND&fq=((types:("subject")+OR+(types:("classification")+OR+(types:("accession")+OR+(types:("repository")+OR+(types:("resource")+OR+(types:("agent")+OR+(types:("digital_object")+OR+(types:("archival_object"))))))))))&fq=-exclude_by_default:true&fq=publish:true&sort=&rows=10&q=(publish:(true)+AND+(types:(pui)+AND+((fullrecord:(the)))))&facet.limit=100&csv.header=true&csv.encapsulator="&facet.mincount=0&wt=json&facet=true} hits=0 status=0 QTime=80 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Rick Neal > Library Applications and Systems Administrator > Boatwright Memorial Library > University of Richmond, VA 23173 > > rneal at richmond.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From rneal at richmond.edu Fri Apr 26 11:16:34 2019 From: rneal at richmond.edu (Neal, Rick) Date: Fri, 26 Apr 2019 15:16:34 +0000 Subject: [Archivesspace_Users_Group] Issue after patching server In-Reply-To: References: Message-ID: Hi Steve, I will paste the log file from today at the bottom. I stopped and started ArchivesSpace so it isn?t too long. I can get to the backend api. Thanks for looking at this: Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rick Neal Library Applications and Systems Administrator Boatwright Memorial Library University of Richmond, VA 23173 rneal at richmond.edu OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:15 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/backend.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp Apr 26, 2019 11:07:15 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},/usr/local/archivesspace/wars/backend.war Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},/usr/local/archivesspace/wars/backend.war Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb Running database migrations for demo database All done. ************************************************************************ *** *** WARNING: Running against the demo database, which is not intended *** for production use. *** *** Please see the README.md file for instructions on configuring MySQL. *** ************************************************************************ ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_backend.txt' to trigger a thread dump Apr 26, 2019 11:07:28 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},/usr/local/archivesspace/wars/backend.war Apr 26, 2019 11:07:28 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8089 Apr 26, 2019 11:07:28 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:28 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/solr.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8090-solr.war-_-any-/webapp Apr 26, 2019 11:07:29 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:29 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8090-solr.war-_-any-/webapp/},/usr/local/archivesspace/wars/solr.war Apr 26, 2019 11:07:29 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8090-solr.war-_-any-/webapp/},/usr/local/archivesspace/wars/solr.war Apr 26, 2019 11:07:29 AM org.apache.solr.servlet.SolrDispatchFilter init INFO: SolrDispatchFilter.init() Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader locateSolrHome INFO: No /solr/home in JNDI Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader locateSolrHome INFO: using system property solr.solr.home: /root/ArchivesSpace/solr_home Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader INFO: new SolrResourceLoader for directory: '/root/ArchivesSpace/solr_home/' Apr 26, 2019 11:07:29 AM org.apache.solr.core.ConfigSolr fromFile INFO: Loading container configuration from /root/ArchivesSpace/solr_home/solr.xml Apr 26, 2019 11:07:29 AM org.apache.solr.core.ConfigSolr fromFile INFO: /root/ArchivesSpace/solr_home/solr.xml does not exist, using default configuration Apr 26, 2019 11:07:29 AM org.apache.solr.core.CoreContainer INFO: New CoreContainer 1310719572 Apr 26, 2019 11:07:29 AM org.apache.solr.core.CoreContainer load INFO: Loading cores into CoreContainer [instanceDir=/root/ArchivesSpace/solr_home/] Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting socketTimeout to: 0 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting urlScheme to: null Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting connTimeout to: 0 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting maxConnectionsPerHost to: 20 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting corePoolSize to: 0 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting maximumPoolSize to: 2147483647 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting maxThreadIdleTime to: 5 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting sizeOfQueue to: -1 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting fairnessPolicy to: false Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting useRetries to: false Apr 26, 2019 11:07:29 AM org.apache.solr.update.UpdateShardHandler INFO: Creating UpdateShardHandler HTTP client with params: socketTimeout=0&connTimeout=0&retry=true Apr 26, 2019 11:07:29 AM org.apache.solr.logging.LogWatcher createWatcher INFO: SLF4J impl is org.slf4j.impl.JDK14LoggerFactory Apr 26, 2019 11:07:29 AM org.apache.solr.logging.LogWatcher newRegisteredLogWatcher INFO: Registering Log Listener [JUL (org.slf4j.impl.JDK14LoggerFactory)] Apr 26, 2019 11:07:29 AM org.apache.solr.core.CoreContainer load INFO: Host Name: Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader INFO: new SolrResourceLoader for directory: '/root/ArchivesSpace/solr_home/collection1/' Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrConfig INFO: Using Lucene MatchVersion: 4.10.4 Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrConfig INFO: Loaded SolrConfig: solrconfig.xml Apr 26, 2019 11:07:29 AM org.apache.solr.schema.IndexSchema readSchema INFO: Reading Solr Schema from /root/ArchivesSpace/solr_home/collection1/conf/schema.xml Apr 26, 2019 11:07:29 AM org.apache.solr.schema.IndexSchema readSchema INFO: [collection1] Schema name=example Apr 26, 2019 11:07:30 AM org.apache.solr.schema.IndexSchema readSchema INFO: unique key field: id Apr 26, 2019 11:07:30 AM org.apache.solr.core.CoreContainer create INFO: Creating SolrCore 'collection1' using configuration from instancedir /root/ArchivesSpace/solr_home/collection1/ Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore initDirectoryFactory INFO: solr.NRTCachingDirectoryFactory Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore INFO: [collection1] Opening new SolrCore at /root/ArchivesSpace/solr_home/collection1/, dataDir=/root/ArchivesSpace/solr_index/ Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore INFO: JMX monitoring not detected for core: collection1 Apr 26, 2019 11:07:30 AM org.apache.solr.core.CachingDirectoryFactory get INFO: return new directory for /root/ArchivesSpace/solr_index Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore getNewIndexDir INFO: New index directory detected: old=null new=/root/ArchivesSpace/solr_index/index/ Apr 26, 2019 11:07:30 AM org.apache.solr.core.CachingDirectoryFactory get INFO: return new directory for /root/ArchivesSpace/solr_index/index Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore initWriters INFO: created json: solr.JSONResponseWriter Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore loadUpdateProcessorChains INFO: no updateRequestProcessorChain defined as default, creating implicit default Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update/json: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update/csv: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update/json/docs: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /select: solr.SearchHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig WARNING: Multiple requestHandler registered to the same name: /update ignoring: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update: solr.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: adding lazy requestHandler: solr.DocumentAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /analysis/document: solr.DocumentAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: adding lazy requestHandler: solr.FieldAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /analysis/field: solr.FieldAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: adding lazy requestHandler: solr.ReplicationHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /replication: solr.ReplicationHandler Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.update.CommitTracker INFO: Hard AutoCommit: if uncommited for 60000ms; if 1000 uncommited docs Apr 26, 2019 11:07:30 AM org.apache.solr.update.CommitTracker INFO: Soft AutoCommit: disabled Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrDeletionPolicy onInit INFO: SolrDeletionPolicy.onInit: commits: num=1 commit{dir=NRTCachingDirectory(MMapDirectory@/root/ArchivesSpace/solr_index/index lockFactory=NativeFSLockFactory@/root/ArchivesSpace/solr_index/index; maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_9z,generation=359} Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrDeletionPolicy updateCommits INFO: newest commit generation = 359 Apr 26, 2019 11:07:30 AM org.apache.solr.search.SolrIndexSearcher INFO: Opening Searcher at 7174af71[collection1] main Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResourceStorage$FileStorageIO configure INFO: File-based storage initialized to use dir: /root/ArchivesSpace/solr_home/collection1/conf Apr 26, 2019 11:07:30 AM org.apache.solr.rest.RestManager init INFO: Initializing RestManager with initArgs: {storageDir=/root/ArchivesSpace/solr_home/collection1/conf} Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResourceStorage load INFO: Reading _rest_managed.json using file:dir=/root/ArchivesSpace/solr_home/collection1/conf Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResourceStorage load INFO: Loaded LinkedHashMap at path _rest_managed.json using file:dir=/root/ArchivesSpace/solr_home/collection1/conf Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResource reloadFromStorage INFO: Loaded initArgs {} for /rest/managed Apr 26, 2019 11:07:30 AM org.apache.solr.rest.RestManager init INFO: Initializing 0 registered ManagedResources Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore registerSearcher INFO: [collection1] Registered new searcher Searcher at 7174af71[collection1] main{StandardDirectoryReader(segments_9z:1767:nrt _eu(4.0.0.2):C1504/338:delGen=3 _ex(4.0.0.2):C331/330:delGen=1 _ez(4.0.0.2):C330 _f4(4.0.0.2):C2/1:delGen=1 _f5(4.0.0.2):C1 _f7(4.0.0.2):C2)} Apr 26, 2019 11:07:30 AM org.apache.solr.core.CoreContainer registerCore INFO: registering core: collection1 Apr 26, 2019 11:07:30 AM org.apache.solr.servlet.SolrDispatchFilter init INFO: user.dir=/usr/local/archivesspace Apr 26, 2019 11:07:30 AM org.apache.solr.servlet.SolrDispatchFilter init INFO: SolrDispatchFilter.init() done Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8090 Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:30 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/indexer.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp Apr 26, 2019 11:07:30 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /aspace-indexer, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/},/usr/local/archivesspace/wars/indexer.war Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/},/usr/local/archivesspace/wars/indexer.war Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_indexer.txt' to trigger a thread dump Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/},/usr/local/archivesspace/wars/indexer.war Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8091 Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:42 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/frontend.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp Apr 26, 2019 11:07:42 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/},/usr/local/archivesspace/wars/frontend.war Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/},/usr/local/archivesspace/wars/frontend.war Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb DEPRECATION WARNING: Sprockets method `register_engine` is deprecated. Please register a mime type using `register_mime_type` then use `register_compressor` or `register_transformer`. https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors (called from block in Railtie at /usr/local/archivesspace/gems/gems/less-rails-2.8.0/lib/less/rails/railtie.rb:16) DEPRECATION WARNING: You are using the a deprecated processor interface Less::Rails::ImportProcessor. Please update your processor interface: https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors (called from block in Railtie at /usr/local/archivesspace/gems/gems/less-rails-2.8.0/lib/less/rails/railtie.rb:21) ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_frontend.txt' to trigger a thread dump Apr 26, 2019 11:07:51 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/},/usr/local/archivesspace/wars/frontend.war Apr 26, 2019 11:07:51 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8080 Apr 26, 2019 11:07:51 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:52 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/public.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp Apr 26, 2019 11:07:52 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp/},/usr/local/archivesspace/wars/public.war Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp/},/usr/local/archivesspace/wars/public.war Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_pui.txt' to trigger a thread dump Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp/},/usr/local/archivesspace/wars/public.war Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8081 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8888 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/oai.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp Apr 26, 2019 11:07:59 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_oai.txt' to trigger a thread dump Apr 26, 2019 11:08:00 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Apr 26, 2019 11:08:00 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8082 ************************************************************ Welcome to ArchivesSpace! You can now point your browser to http://localhost:8080 ************************************************************ Apr 26, 2019 11:08:01 AM org.apache.solr.update.DirectUpdateHandler2 commit INFO: start commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=true,prepareCommit=false} Apr 26, 2019 11:08:01 AM org.apache.solr.core.SolrCore openNewSearcher INFO: SolrIndexSearcher has not changed - not re-opening: org.apache.solr.search.SolrIndexSearcher Apr 26, 2019 11:08:01 AM org.apache.solr.update.DirectUpdateHandler2 commit INFO: end_commit_flush Apr 26, 2019 11:08:01 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {commit=} 0 86 Apr 26, 2019 11:08:19 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={csv.escape=\&start=0&q.op=AND&sort=repo_sort+asc&fq=-exclude_by_default:true&fq=publish:true&rows=100&q=primary_type:repository&defType=edismax&qf=four_part_id^3+title^2+finding_aid_filing_title^2+fullrecord&pf=four_part_id^4&csv.header=true&csv.encapsulator="&wt=json&facet=true} hits=3 status=0 QTime=131 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lora.Woodford at lyrasis.org Fri Apr 26 11:54:59 2019 From: Lora.Woodford at lyrasis.org (Lora Woodford) Date: Fri, 26 Apr 2019 15:54:59 +0000 Subject: [Archivesspace_Users_Group] Suppressed record search bug In-Reply-To: <048AC982-DD2B-4807-92BB-D5940A9946B5@du.edu> References: <048AC982-DD2B-4807-92BB-D5940A9946B5@du.edu> Message-ID: <6026AA2E-6B9E-453F-90B6-519929BA7292@lyrasis.org> Heya Kevin, Thanks for bringing this up. I took a quick look at the code, and I see what?s going on here. I?m going to put in a pull request later today to hopefully patch this in the upcoming release. That ?found in? column was one of the first feature enhancements I tackled, so I?m afraid there are some edge cases (such as what to do in instances of suppressed records) that I just didn?t consider/test out, and our pre-release testing didn?t catch it either. If you have the ability/are able to test this out before it makes it to an official release, I?m happy to send you a build with this fix in it to test out locally. Feel free to reach out off-list if you?d like. Best, Lora From: on behalf of Kevin Clair Reply-To: Archivesspace Users Group Date: Thursday, April 25, 2019 at 12:37 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug We?re on 2.5.2 now. We upgraded because of that bug; that?s why I thought the problem could be with the event record instead of the resource. -k From: on behalf of Blake Carver Reply-To: Archivesspace Group Date: Thursday, April 25, 2019 at 10:28 AM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug What version are you on? That looks similar to a bug that should've been fixed in 2.5.2. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin Clair Sent: Thursday, April 25, 2019 12:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug I should also say that the search that prompted this also returns a component_transfer event of records that were moved from the suppressed Resource to another Resource. So it may be that it?s an issue with suppressed records appearing in the ?Found In? column of another record?s result summary, rather than with the suppressed record itself? -k From: on behalf of Kevin Clair Reply-To: Archivesspace Group Date: Thursday, April 25, 2019 at 10:00 AM To: Archivesspace Group Subject: [Archivesspace_Users_Group] Suppressed record search bug Hello, We recently discovered an issue with searching for records that are suppressed in the staff interface. In our instance, administrative users are able to do known-item searches for suppressed records without incident; if a user without administrative permissions performs the same search, they get thrown an error with the following stack trace: I, [2019-04-25T09:47:26.038804 #18125] INFO -- : Completed 500 Internal Server Error in 1163ms F, [2019-04-25T09:47:26.041948 #18125] FATAL -- : F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error (undefined method `[]' for nil:NilClass): F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = context_ancestor(result) %> 2: <% if ancestors != nil && ancestors != [''] %> 3: <% ancestors.reverse.each_with_index do |ancestor, i| %> 4: <%= resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %> 5: <% if i < ancestors.length - 1 %> 6: <%= context_separator(result) %> 7: <% end %> F, [2019-04-25T09:47:26.042340 #18125] FATAL -- : F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : app/helpers/search_helper.rb:198:in `get_ancestor_title' app/views/search/_context.html.erb:4:in `block in _app_views_search__context_html_erb___234296763_2752' app/views/search/_context.html.erb:3:in `_app_views_search__context_html_erb___234296763_2752' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_listing.html.erb:90:in `block in _app_views_search__listing_html_erb___1981573825_2748' app/views/search/_listing.html.erb:52:in `_app_views_search__listing_html_erb___1981573825_2748' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/_results.html.erb:23:in `_app_views_search__results_html_erb___1135689531_2744' app/helpers/application_helper.rb:289:in `render_aspace_partial' app/views/search/do_search.html.erb:16:in `_app_views_search_do_search_html_erb__585907251_2742' Checking in to see if anyone else has noticed similar behavior and if there?s a bug report for this in Jira already. I did a quick search just now but couldn?t find anything that looked similar to this. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneal at richmond.edu Fri Apr 26 11:57:49 2019 From: rneal at richmond.edu (Neal, Rick) Date: Fri, 26 Apr 2019 15:57:49 +0000 Subject: [Archivesspace_Users_Group] Issue after patching server Message-ID: Steve, Please stop troubleshooting. I think I know the issue now. It has to do with an older server snapshot. Thanks Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rick Neal Library Applications and Systems Administrator Boatwright Memorial Library University of Richmond, VA 23173 rneal at richmond.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Neal, Rick Sent: Friday, April 26, 2019 11:17 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issue after patching server Hi Steve, I will paste the log file from today at the bottom. I stopped and started ArchivesSpace so it isn?t too long. I can get to the backend api. Thanks for looking at this: Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rick Neal Library Applications and Systems Administrator Boatwright Memorial Library University of Richmond, VA 23173 rneal at richmond.edu OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:15 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/backend.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp Apr 26, 2019 11:07:15 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},/usr/local/archivesspace/wars/backend.war Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},/usr/local/archivesspace/wars/backend.war Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:15 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb Running database migrations for demo database All done. ************************************************************************ *** *** WARNING: Running against the demo database, which is not intended *** for production use. *** *** Please see the README.md file for instructions on configuring MySQL. *** ************************************************************************ ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_backend.txt' to trigger a thread dump Apr 26, 2019 11:07:28 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},/usr/local/archivesspace/wars/backend.war Apr 26, 2019 11:07:28 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8089 Apr 26, 2019 11:07:28 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:28 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/solr.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8090-solr.war-_-any-/webapp Apr 26, 2019 11:07:29 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:29 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8090-solr.war-_-any-/webapp/},/usr/local/archivesspace/wars/solr.war Apr 26, 2019 11:07:29 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8090-solr.war-_-any-/webapp/},/usr/local/archivesspace/wars/solr.war Apr 26, 2019 11:07:29 AM org.apache.solr.servlet.SolrDispatchFilter init INFO: SolrDispatchFilter.init() Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader locateSolrHome INFO: No /solr/home in JNDI Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader locateSolrHome INFO: using system property solr.solr.home: /root/ArchivesSpace/solr_home Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader INFO: new SolrResourceLoader for directory: '/root/ArchivesSpace/solr_home/' Apr 26, 2019 11:07:29 AM org.apache.solr.core.ConfigSolr fromFile INFO: Loading container configuration from /root/ArchivesSpace/solr_home/solr.xml Apr 26, 2019 11:07:29 AM org.apache.solr.core.ConfigSolr fromFile INFO: /root/ArchivesSpace/solr_home/solr.xml does not exist, using default configuration Apr 26, 2019 11:07:29 AM org.apache.solr.core.CoreContainer INFO: New CoreContainer 1310719572 Apr 26, 2019 11:07:29 AM org.apache.solr.core.CoreContainer load INFO: Loading cores into CoreContainer [instanceDir=/root/ArchivesSpace/solr_home/] Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting socketTimeout to: 0 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting urlScheme to: null Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting connTimeout to: 0 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting maxConnectionsPerHost to: 20 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting corePoolSize to: 0 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting maximumPoolSize to: 2147483647 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting maxThreadIdleTime to: 5 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting sizeOfQueue to: -1 Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting fairnessPolicy to: false Apr 26, 2019 11:07:29 AM org.apache.solr.handler.component.HttpShardHandlerFactory getParameter INFO: Setting useRetries to: false Apr 26, 2019 11:07:29 AM org.apache.solr.update.UpdateShardHandler INFO: Creating UpdateShardHandler HTTP client with params: socketTimeout=0&connTimeout=0&retry=true Apr 26, 2019 11:07:29 AM org.apache.solr.logging.LogWatcher createWatcher INFO: SLF4J impl is org.slf4j.impl.JDK14LoggerFactory Apr 26, 2019 11:07:29 AM org.apache.solr.logging.LogWatcher newRegisteredLogWatcher INFO: Registering Log Listener [JUL (org.slf4j.impl.JDK14LoggerFactory)] Apr 26, 2019 11:07:29 AM org.apache.solr.core.CoreContainer load INFO: Host Name: Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrResourceLoader INFO: new SolrResourceLoader for directory: '/root/ArchivesSpace/solr_home/collection1/' Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrConfig INFO: Using Lucene MatchVersion: 4.10.4 Apr 26, 2019 11:07:29 AM org.apache.solr.core.SolrConfig INFO: Loaded SolrConfig: solrconfig.xml Apr 26, 2019 11:07:29 AM org.apache.solr.schema.IndexSchema readSchema INFO: Reading Solr Schema from /root/ArchivesSpace/solr_home/collection1/conf/schema.xml Apr 26, 2019 11:07:29 AM org.apache.solr.schema.IndexSchema readSchema INFO: [collection1] Schema name=example Apr 26, 2019 11:07:30 AM org.apache.solr.schema.IndexSchema readSchema INFO: unique key field: id Apr 26, 2019 11:07:30 AM org.apache.solr.core.CoreContainer create INFO: Creating SolrCore 'collection1' using configuration from instancedir /root/ArchivesSpace/solr_home/collection1/ Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore initDirectoryFactory INFO: solr.NRTCachingDirectoryFactory Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore INFO: [collection1] Opening new SolrCore at /root/ArchivesSpace/solr_home/collection1/, dataDir=/root/ArchivesSpace/solr_index/ Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore INFO: JMX monitoring not detected for core: collection1 Apr 26, 2019 11:07:30 AM org.apache.solr.core.CachingDirectoryFactory get INFO: return new directory for /root/ArchivesSpace/solr_index Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore getNewIndexDir INFO: New index directory detected: old=null new=/root/ArchivesSpace/solr_index/index/ Apr 26, 2019 11:07:30 AM org.apache.solr.core.CachingDirectoryFactory get INFO: return new directory for /root/ArchivesSpace/solr_index/index Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore initWriters INFO: created json: solr.JSONResponseWriter Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore loadUpdateProcessorChains INFO: no updateRequestProcessorChain defined as default, creating implicit default Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update/json: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update/csv: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update/json/docs: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /select: solr.SearchHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig WARNING: Multiple requestHandler registered to the same name: /update ignoring: org.apache.solr.handler.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /update: solr.UpdateRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: adding lazy requestHandler: solr.DocumentAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /analysis/document: solr.DocumentAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: adding lazy requestHandler: solr.FieldAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /analysis/field: solr.FieldAnalysisRequestHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: adding lazy requestHandler: solr.ReplicationHandler Apr 26, 2019 11:07:30 AM org.apache.solr.core.RequestHandlers initHandlersFromConfig INFO: created /replication: solr.ReplicationHandler Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.handler.loader.XMLLoader init INFO: xsltCacheLifetimeSeconds=60 Apr 26, 2019 11:07:30 AM org.apache.solr.update.CommitTracker INFO: Hard AutoCommit: if uncommited for 60000ms; if 1000 uncommited docs Apr 26, 2019 11:07:30 AM org.apache.solr.update.CommitTracker INFO: Soft AutoCommit: disabled Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrDeletionPolicy onInit INFO: SolrDeletionPolicy.onInit: commits: num=1 commit{dir=NRTCachingDirectory(MMapDirectory@/root/ArchivesSpace/solr_index/index lockFactory=NativeFSLockFactory@/root/ArchivesSpace/solr_index/index; maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_9z,generation=359} Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrDeletionPolicy updateCommits INFO: newest commit generation = 359 Apr 26, 2019 11:07:30 AM org.apache.solr.search.SolrIndexSearcher INFO: Opening Searcher at 7174af71[collection1] main Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResourceStorage$FileStorageIO configure INFO: File-based storage initialized to use dir: /root/ArchivesSpace/solr_home/collection1/conf Apr 26, 2019 11:07:30 AM org.apache.solr.rest.RestManager init INFO: Initializing RestManager with initArgs: {storageDir=/root/ArchivesSpace/solr_home/collection1/conf} Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResourceStorage load INFO: Reading _rest_managed.json using file:dir=/root/ArchivesSpace/solr_home/collection1/conf Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResourceStorage load INFO: Loaded LinkedHashMap at path _rest_managed.json using file:dir=/root/ArchivesSpace/solr_home/collection1/conf Apr 26, 2019 11:07:30 AM org.apache.solr.rest.ManagedResource reloadFromStorage INFO: Loaded initArgs {} for /rest/managed Apr 26, 2019 11:07:30 AM org.apache.solr.rest.RestManager init INFO: Initializing 0 registered ManagedResources Apr 26, 2019 11:07:30 AM org.apache.solr.core.SolrCore registerSearcher INFO: [collection1] Registered new searcher Searcher at 7174af71[collection1] main{StandardDirectoryReader(segments_9z:1767:nrt _eu(4.0.0.2):C1504/338:delGen=3 _ex(4.0.0.2):C331/330:delGen=1 _ez(4.0.0.2):C330 _f4(4.0.0.2):C2/1:delGen=1 _f5(4.0.0.2):C1 _f7(4.0.0.2):C2)} Apr 26, 2019 11:07:30 AM org.apache.solr.core.CoreContainer registerCore INFO: registering core: collection1 Apr 26, 2019 11:07:30 AM org.apache.solr.servlet.SolrDispatchFilter init INFO: user.dir=/usr/local/archivesspace Apr 26, 2019 11:07:30 AM org.apache.solr.servlet.SolrDispatchFilter init INFO: SolrDispatchFilter.init() done Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8090 Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:30 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/indexer.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp Apr 26, 2019 11:07:30 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /aspace-indexer, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/},/usr/local/archivesspace/wars/indexer.war Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/},/usr/local/archivesspace/wars/indexer.war Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:30 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_indexer.txt' to trigger a thread dump Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/aspace-indexer,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/},/usr/local/archivesspace/wars/indexer.war Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8091 Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:42 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/frontend.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp Apr 26, 2019 11:07:42 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/},/usr/local/archivesspace/wars/frontend.war Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/},/usr/local/archivesspace/wars/frontend.war Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:42 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb DEPRECATION WARNING: Sprockets method `register_engine` is deprecated. Please register a mime type using `register_mime_type` then use `register_compressor` or `register_transformer`. https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors (called from block in Railtie at /usr/local/archivesspace/gems/gems/less-rails-2.8.0/lib/less/rails/railtie.rb:16) DEPRECATION WARNING: You are using the a deprecated processor interface Less::Rails::ImportProcessor. Please update your processor interface: https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors (called from block in Railtie at /usr/local/archivesspace/gems/gems/less-rails-2.8.0/lib/less/rails/railtie.rb:21) ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_frontend.txt' to trigger a thread dump Apr 26, 2019 11:07:51 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/},/usr/local/archivesspace/wars/frontend.war Apr 26, 2019 11:07:51 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8080 Apr 26, 2019 11:07:51 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:52 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/public.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp Apr 26, 2019 11:07:52 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp/},/usr/local/archivesspace/wars/public.war Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp/},/usr/local/archivesspace/wars/public.war Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:52 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_pui.txt' to trigger a thread dump Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8081-public.war-_-any-/webapp/},/usr/local/archivesspace/wars/public.war Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8081 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8888 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.server.Server doStart INFO: jetty-8.1.5.v20120716 Apr 26, 2019 11:07:58 AM org.eclipse.jetty.webapp.WebInfConfiguration unpack INFO: Extract jar:file:/usr/local/archivesspace/wars/oai.war!/ to /root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp Apr 26, 2019 11:07:59 AM org.eclipse.jetty.webapp.StandardDescriptorProcessor visitServlet INFO: NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server VM 25.212-b04 on 1.8.0_212-b04 +jit [linux-x86_64] Apr 26, 2019 11:07:59 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /usr/local/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/local/archivesspace/thread_dump_oai.txt' to trigger a thread dump Apr 26, 2019 11:08:00 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/root/ArchivesSpace/tmp/jetty-0.0.0.0-8082-oai.war-_-any-/webapp/},/usr/local/archivesspace/wars/oai.war Apr 26, 2019 11:08:00 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8082 ************************************************************ Welcome to ArchivesSpace! You can now point your browser to http://localhost:8080 ************************************************************ Apr 26, 2019 11:08:01 AM org.apache.solr.update.DirectUpdateHandler2 commit INFO: start commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=true,prepareCommit=false} Apr 26, 2019 11:08:01 AM org.apache.solr.core.SolrCore openNewSearcher INFO: SolrIndexSearcher has not changed - not re-opening: org.apache.solr.search.SolrIndexSearcher Apr 26, 2019 11:08:01 AM org.apache.solr.update.DirectUpdateHandler2 commit INFO: end_commit_flush Apr 26, 2019 11:08:01 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {commit=} 0 86 Apr 26, 2019 11:08:19 AM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={csv.escape=\&start=0&q.op=AND&sort=repo_sort+asc&fq=-exclude_by_default:true&fq=publish:true&rows=100&q=primary_type:repository&defType=edismax&qf=four_part_id^3+title^2+finding_aid_filing_title^2+fullrecord&pf=four_part_id^4&csv.header=true&csv.encapsulator="&wt=json&facet=true} hits=3 status=0 QTime=131 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Apr 29 10:43:09 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 29 Apr 2019 14:43:09 +0000 Subject: [Archivesspace_Users_Group] Fifth Annual Member Forum - Save the Date and Volunteer Message-ID: ArchivesSpace will hold its 5th annual Member Forum on August 2nd at the Thompson Conference Center at our member institution the University of Texas - Austin. As in previous years, this will be a free opportunity for staff of ArchivesSpace member institutions to meet and share information with each other and the program team. More information about the program and logistics later in the spring. We are looking for volunteers from member institutions of all sizes to form a working group to plan the agenda for our largest member event of the year! Contact Jessica at jessica.crouch at lyrasis.org to volunteer by May 15th. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29058 bytes Desc: image001.jpg URL: From Lisa.Crane at claremont.edu Mon Apr 29 22:11:02 2019 From: Lisa.Crane at claremont.edu (Lisa Crane) Date: Tue, 30 Apr 2019 02:11:02 +0000 Subject: [Archivesspace_Users_Group] Export container list? Message-ID: Hello all! Has anyone been successful in exporting a container list in CSV or Excel from a Resource in ASpace? I am looking for a list of box numbers (one column); file folder numbers (another column); file folder titles (another column); and date expressions (another column). Does anyone know how to do this? Can it even be done? All the best, Lisa Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont Colleges Library 800 North Dartmouth Ave. | Claremont, CA 91711-5053 Phone (909) 607-0862 | lisa.crane at claremont.edu Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpaquette at smith.edu Tue Apr 30 08:48:04 2019 From: mpaquette at smith.edu (Michelle Paquette) Date: Tue, 30 Apr 2019 08:48:04 -0400 Subject: [Archivesspace_Users_Group] Export container list? In-Reply-To: References: Message-ID: Hi Lisa, I'm not sure if you have a connection to query your MySQL database (presuming that's what you're using behind ASpace), but this is the kind of thing I tend to pull out of ASpace using SQL queries. If you are able to run queries like that, let me know and I'd be happy to share a version of a query that would get you the desired output. Michelle On Mon, Apr 29, 2019 at 10:11 PM Lisa Crane wrote: > Hello all! > > > > Has anyone been successful in exporting a container list in CSV or Excel > from a Resource in ASpace? I am looking for a list of box numbers (one > column); file folder numbers (another column); file folder titles (another > column); and date expressions (another column). > > > > Does anyone know how to do this? Can it even be done? > > > > All the best, > > > > Lisa > > > > *Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont > Colleges Library* > > 800 North Dartmouth Ave. | Claremont, CA 91711-5053 > > Phone (909) 607-0862 | *lisa.crane at claremont.edu > * > > > > Pronouns: she/her/hers > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Michelle Paquette Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Tue Apr 30 09:36:16 2019 From: noah.huffman at duke.edu (Noah Huffman) Date: Tue, 30 Apr 2019 13:36:16 +0000 Subject: [Archivesspace_Users_Group] Export container list? In-Reply-To: References: Message-ID: Hi Lisa, If you have the ability to install plugins in your ASpace instance, this plugin should meet your requirements and allow you to download CSVs directly from the staff interface: https://github.com/hudmol/digitization_work_order Alternatively, you can export EAD for the resource record and then process it with XSLT to generate a CSV file with rows for every file or item level component. Here is an example of an XSLT script that we use for this purpose: https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/xslt/aspaceEAD_to_SteadyCSV.xsl -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Lisa Crane Sent: Monday, April 29, 2019 10:11 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Export container list? Hello all! Has anyone been successful in exporting a container list in CSV or Excel from a Resource in ASpace? I am looking for a list of box numbers (one column); file folder numbers (another column); file folder titles (another column); and date expressions (another column). Does anyone know how to do this? Can it even be done? All the best, Lisa Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont Colleges Library 800 North Dartmouth Ave. | Claremont, CA 91711-5053 Phone (909) 607-0862 | lisa.crane at claremont.edu Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Tue Apr 30 11:31:23 2019 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Tue, 30 Apr 2019 11:31:23 -0400 Subject: [Archivesspace_Users_Group] Export container list? In-Reply-To: References: Message-ID: You can also get a list of containers from the API provided you are on 2.5.1 or higher: https://archivesspace.github.io/archivesspace/api/#get-top-containers-linked-to-a-published-resource-and-published-archival-ojbects-contained-within Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Tue, Apr 30, 2019 at 9:36 AM Noah Huffman wrote: > Hi Lisa, > > > > If you have the ability to install plugins in your ASpace instance, this > plugin should meet your requirements and allow you to download CSVs > directly from the staff interface: > https://github.com/hudmol/digitization_work_order > > > > > Alternatively, you can export EAD for the resource record and then process > it with XSLT to generate a CSV file with rows for every file or item level > component. Here is an example of an XSLT script that we use for this > purpose: > https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/xslt/aspaceEAD_to_SteadyCSV.xsl > > > > > -Noah > > > > ================ > > Noah Huffman > > Archivist for Metadata, Systems, and Digital Records > > David M. Rubenstein Rare Book & Manuscript Library > > Duke University | 919-660-5982 > > http://library.duke.edu/rubenstein/ > > > > > > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Lisa > Crane > *Sent:* Monday, April 29, 2019 10:11 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Export container list? > > > > Hello all! > > > > Has anyone been successful in exporting a container list in CSV or Excel > from a Resource in ASpace? I am looking for a list of box numbers (one > column); file folder numbers (another column); file folder titles (another > column); and date expressions (another column). > > > > Does anyone know how to do this? Can it even be done? > > > > All the best, > > > > Lisa > > > > *Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont > Colleges Library* > > 800 North Dartmouth Ave. | Claremont, CA 91711-5053 > > Phone (909) 607-0862 | lisa.crane at claremont.edu > > > > Pronouns: she/her/hers > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=_DsNVvE0MidyDzdUOYchWsIErjGtgLba7OOoi6MzJhM&m=oUr73kqMPBfQUe6OdpL30oisAtPYfk9snDk0XfbWT84&s=c5-3m92twJ8z58it-JTNk3LUBWcCZiTkw1tdR0RXvY8&e= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Apr 30 13:06:01 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 30 Apr 2019 17:06:01 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - April 2019 Message-ID: [ASpaceOrgHome.jpg] April 2019 Update Development We?re aiming to put out a release candidate for v2.6.0 within the next two weeks. This release candidate will include a number of improvements to the staff and public interfaces, as well as a redesigned reports page. This release candidate will also introduce our newest optional feature, human-readable URLs. Using human-readable URLs will allow you to specify a particular URL in the public user interface for records based on the title, identifier, or text you provide. Once the release candidate is out, we?ll be asking for as much testing as possible on this new feature. These testing results will determine the date for the actual release. Look for more information about the release candidate soon. Get Involved: We have several upcoming opportunities for involvement in the ArchivesSpace community and are looking for volunteers from all membership levels within the ArchivesSpace community. Call for Participation: ArchivesSpace Code of Conduct Working Group We?re looking for volunteers to serve on the ArchivesSpace Code of Conduct working group. The Working Group?s mission is to draft a code of conduct that addresses both online and in person interaction and appropriate responses to violations. The working group will draft a Code of Conduct to present to the ArchivesSpace community for comment before implementation. Contact Jessica at jessica.crouch at lyrasis.org to volunteer. Call for Participation: Annual Forum Working Group ArchivesSpace will hold its 5th annual Member Forum on August 2nd at the Thompson Conference Center at our member institution the University of Texas - Austin. As in previous years, this will be a free opportunity for staff of ArchivesSpace member institutions to meet and share information with each other and the program team. More information about the program and logistics later in the spring. We are looking for volunteers from member institutions of all sizes to form a working group to plan the agenda for our largest member event of the year! Contact Jessica at jessica.crouch at lyrasis.org to volunteer by May 15th. Call for Participation: Upcoming Webinar: From Archon to ArchivesSpace Is your institution a former user of Archon now using ArchivesSpace? Have you adapted workflows, workarounds or tricks for your implementation of ArchivesSpace to account for what you miss in Archon? We will be hosting an upcoming webinar geared specifically for former Archon users who are looking to adapt workflows for ArchivesSpace. If you would like to present at this webinar, contact Jessica at jessica.crouch at lyrasis.org. More information on the webinar itself will be available later in the spring. Connect with ArchivesSpace in Person Jessica Crouch, our new Community Engagement Coordinator, will be at the Conference of Inter-Mountain Archivists and Society of Southwest Archivists Joint Annual Meeting in Tucson, Arizona, May 15-18. Come find her in the exhibit hall to talk about the ArchivesSpace application, our community activities, membership, and more. Upcoming Trainings The Mike Kelley Foundation for the Arts will be hosting a two day ArchivesSpace Basics Workshop in Los Angeles from May 9-10. The Metropolitan New York Library Council (METRO) will be hosting a one day Introduction to ArchivesSpace workshop on May 19. Registration is open via METRO at https://www.eventbrite.com/e/introduction-to-archivesspace-tickets-55729897624. Membership Update We are excited to welcome our newest members to our community! Our new members since March 31 include: * Central Texas Conference of the United Methodist Church (Fort Worth, TX) * Fairfield University (Fairfield, CT) * University of Sheffield (Sheffield, UK) As a reminder, we will soon be sending out membership renewals for 2019-2020. If you need to update your billing contact information or if you would like to receive your invoice early, email ArchivesSpaceHome at lyrasis.org. As of April 29, we have 382 General members, 19 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Tools Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 19859 bytes Desc: image001.jpg URL: