From bdysonsm at utk.edu Mon Mar 1 10:29:47 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Mon, 1 Mar 2021 15:29:47 +0000 Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section Message-ID: <78059f835620a4e6ac19b3cae56c93ea8fd08526.camel@utk.edu> Hi all - I'm trying to think about suppressing a section of our finding aids in the PUI, specifically the Finding Aid & Administrative Information. I'm not sure, though, if this should be managed through the admin UI or programmatically. I had thought that there might be 'Publish' radio box on that section in the admin UI, but maybe there isn't. Unless I'm missing something (and I probably am!) in the admin UI, then addressing this programmatically seems to be the way forward. Does this sound accurate? What else should I be looking for? We're running v2.5.1. Thoughts and suggestions would be greatly appreciated - thanks in advance for your time and trouble. Best, Bridger -- Bridger Dyson-Smith From christine.dibella at lyrasis.org Mon Mar 1 10:36:35 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 1 Mar 2021 15:36:35 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Diversity Partnership: March 15 deadline approaching Message-ID: (Please share widely and with anyone you think may be interested) The deadline to apply for the ArchivesSpace Diversity Partnership is coming up on March 15. More information about the program is below. Please reach out to us at ArchivesSpaceHome at lyrasis.org if you have any questions. -- The ArchivesSpace Diversity Partnership is a new program that offers support for implementing the ArchivesSpace application to institutions that are themselves or primarily serve communities underrepresented in the ArchivesSpace community. Participating organizations will receive, at no cost to them, ArchivesSpace membership, hosting with a Registered Service Provider, training, and user and technical support for the duration of a three-year term. Eligible organizations include: * academic Minority-Serving Institutions such as Historically Black Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and Tribal Colleges and Universities * non-profit or community archives primarily run by or serving BIPOC (Black, Indigenous, and People of Color) * tribal archives To be eligible for this new program, organizations cannot already be ArchivesSpace members or current hosting clients of any ArchivesSpace provider. This program will launch with a small cohort of institutions on July 1, 2021. The three-year term will conclude on June 30, 2024. More information about the ArchivesSpace Diversity Partnership, including information about how to apply, is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership. We also held an informational webinar outlining the program and the application process last month. The recording is available on our YouTube channel at https://youtu.be/B3SOgG4zThM. The deadline to submit an application for the program is March 15. Members of the planning group are happy to answer questions or discuss potential applicant's situations at any time. Please contact us at ArchivesSpaceHome at lyrasis.org. We really appreciate the interest in the program and look forward to receiving some great applications! Sent on behalf of the Planning Group Jessica Crouch, ArchivesSpace Community Engagement Coordinator Christine Di Bella, ArchivesSpace Program Manager Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory Council Chair Sean Quimby, University of Pennsylvania and ArchivesSpace Governance Board Vice Chair -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Mar 1 12:11:27 2021 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 1 Mar 2021 17:11:27 +0000 Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section In-Reply-To: <78059f835620a4e6ac19b3cae56c93ea8fd08526.camel@utk.edu> References: <78059f835620a4e6ac19b3cae56c93ea8fd08526.camel@utk.edu> Message-ID: Hi Bridger, Just a very quick reply, as I haven't had time to look at the newest release of ArchiveSpace, but... 1. Yes, I think you'd need to use a plugin or other mechanism to do this (lots of plugin examples out there, but if you have any questions about that, there are lots of people in the ASpace community that could help out). 2. I don't like the accordion approach overall, so maybe that will be updated at some point, but that still doesn't help you right now, of course. 3. Most importantly, if you do remove this section, I'd encourage you to think about not moving some of the data elsewhere, particularly the finding aid author, sponsor info (if applicable), etc. I also wish that the finding author info could be managed as linked agents, rather than just text, but even as text it's very useful data! Also, it provides credit as well as some visibility to archival labor (that's another reason I don't like the accordions, since it hides that info by default). I hope that helps. And I'm curious to hear more about whatever direction you wind up taking! All my best Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dyson-Smith, Bridger Sent: Monday, March 1, 2021 10:29 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section Hi all - I'm trying to think about suppressing a section of our finding aids in the PUI, specifically the Finding Aid & Administrative Information. I'm not sure, though, if this should be managed through the admin UI or programmatically. I had thought that there might be 'Publish' radio box on that section in the admin UI, but maybe there isn't. Unless I'm missing something (and I probably am!) in the admin UI, then addressing this programmatically seems to be the way forward. Does this sound accurate? What else should I be looking for? We're running v2.5.1. Thoughts and suggestions would be greatly appreciated - thanks in advance for your time and trouble. Best, Bridger -- Bridger Dyson-Smith _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=04%7C01%7Cmark.custer%40yale.edu%7C7f6e4c3f47be431e9dd308d8dcc6e758%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637502094224544177%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=PMx4OS0yPDdHFrwVS3Xn8TdtOOEb5NTxzbd6WwMvFdo%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Mar 1 15:03:39 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 1 Mar 2021 20:03:39 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace Member Match Program Informational Webinar Message-ID: ArchivesSpace is pleased to announce the ArchivesSpace Member Match program. The Member Match program is a new initiative to engage the ArchivesSpace membership community in peer-to-peer support between ArchivesSpace members. For one, year-long term, Member Match participants will be matched with a member with whom they can receive and offer professional insight, advice, and comradery. The program will also offer participants the opportunity to engage in exclusive events and enlightening discussions about ArchivesSpace and its active user community. In this webinar, members of the ArchivesSpace Member Engagement sub-team will discuss the program and answer questions from potential participants and others interested in the program. More information about the ArchivesSpace Member Match program is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program. A recording of this webinar will be made available on the ArchivesSpace YouTube channel. When: March 10, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_ZqjF2XKXTaqBFQbeITClHA In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. Who should attend: Anyone interested in the ArchivesSpace Member Match program or in becoming more involved in the ArchivesSpace Member community. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Mon Mar 1 17:18:32 2021 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Mon, 1 Mar 2021 17:18:32 -0500 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> Message-ID: Thanks, Rachel! I've now completely reindexed everything (a "hard reindex") and still no joy. I am noticing there is no "location.dat" file in our /indexer_pui_state/: -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_classification.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_resource.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_classification.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_resource.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_classification.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_resource.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 _deletes_deletes.dat -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 repositories_repositories.dat Should there be? Our two problem repositories here are 4 and 5.? The Staff interface reports "0" Resources for both.? Yet when I run the Resources List Report I do indeed get back a report with Resources.? Puzzling. It's like something in the backend DB has become disconnected, but just for these two repositories.? Not sure how. If anyone has any suggestions, I would greatly appreciate hearing them! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: > Hi Mark > > We ran into a similar issue recently, where newly created containers > were not being properly associated with the resource record, and > updates to locations or barcodes were not showing up in searches or > the Manage Top Containers view. We looked at the timestamp files for > the indexer, and noticed that there was no location.dat file. We > performed a soft re-index > , > after which our containers, barcodes, and locations resumed behaving > as expected. We also have recurring monthly system restarts (which > will now include a soft re-index going forward) built into our > schedule, which seems to help with maintaining overall performance. > > I'm not sure if this is exactly what you're experiencing, but I hope > it's helpful. Take care, > Rachel > > On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk > wrote: > > > Dear ASpace list, > > ?From one of our Archivists: > > > When I create a new container, either manually or by spreadsheet > > ingest, the container appears properly in the Instance field of the > > record. From the resource, I can open the container record and it > > appears to be associated with the resource correctly. However, > in the > > container management module, when I search for all containers > > associated with the collection, the recently created container > is not > > listed. If I search for the new container's barcode, the container > > appears in the search results but with no associated resource. I > can > > also locate the new containers by searching for unassociated > containers. > > It seems like some linkage is not happening here. > > More, this is only happening in his Repository, not our other, larger > Repository. > > Has anyone else run into this? > > Mark > > -- > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > > _______________________________________________ > 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= > > > > > > -- > Rachel Searcy > Accessioning Archivist, Archival Collections Management > New York University Libraries > 212.998.2539?| rachel.searcy at nyu.edu > My pronouns are she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Mar 1 19:07:39 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 2 Mar 2021 00:07:39 +0000 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> , Message-ID: Are there any errors in your logs? Look for ERROR and/or FATAL ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Monday, March 1, 2021 5:18 PM To: Rachel Aileen Searcy ; Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Containers not being associated with their resources Thanks, Rachel! I've now completely reindexed everything (a "hard reindex") and still no joy. I am noticing there is no "location.dat" file in our /indexer_pui_state/: -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_classification.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_resource.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_classification.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_resource.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_classification.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_resource.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 _deletes_deletes.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 repositories_repositories.dat Should there be? Our two problem repositories here are 4 and 5. The Staff interface reports "0" Resources for both. Yet when I run the Resources List Report I do indeed get back a report with Resources. Puzzling. It's like something in the backend DB has become disconnected, but just for these two repositories. Not sure how. If anyone has any suggestions, I would greatly appreciate hearing them! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: Hi Mark We ran into a similar issue recently, where newly created containers were not being properly associated with the resource record, and updates to locations or barcodes were not showing up in searches or the Manage Top Containers view. We looked at the timestamp files for the indexer, and noticed that there was no location.dat file. We performed a soft re-index, after which our containers, barcodes, and locations resumed behaving as expected. We also have recurring monthly system restarts (which will now include a soft re-index going forward) built into our schedule, which seems to help with maintaining overall performance. I'm not sure if this is exactly what you're experiencing, but I hope it's helpful. Take care, Rachel On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk > wrote: Dear ASpace list, From one of our Archivists: > When I create a new container, either manually or by spreadsheet > ingest, the container appears properly in the Instance field of the > record. From the resource, I can open the container record and it > appears to be associated with the resource correctly. However, in the > container management module, when I search for all containers > associated with the collection, the recently created container is not > listed. If I search for the new container's barcode, the container > appears in the search results but with no associated resource. I can > also locate the new containers by searching for unassociated containers. It seems like some linkage is not happening here. More, this is only happening in his Repository, not our other, larger Repository. Has anyone else run into this? Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. _______________________________________________ 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdysonsm at utk.edu Mon Mar 1 20:18:30 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Tue, 2 Mar 2021 01:18:30 +0000 Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section In-Reply-To: References: <78059f835620a4e6ac19b3cae56c93ea8fd08526.camel@utk.edu> Message-ID: <9b3b8f13d901a63aeb0f5ac5c60e82207ce172e5.camel@utk.edu> Hi Mark - On Mon, 2021-03-01 at 17:11 +0000, Custer, Mark wrote: > Hi Bridger, > > Just a very quick reply, as I haven't had time to look at the newest > release of ArchiveSpace, but... > ???1. Yes, I think you'd need to use a plugin or other mechanism to > do this (lots of plugin examples out there, but if you have any > questions about that, there are lots of people in the ASpace > community that could help out). That's great - we can integrate this change into our local plugin. > ???2. I don't like the accordion approach overall, so maybe that will > be updated at some point, but that still doesn't help you right now, > of course. > ???3. Most importantly, if you do remove this section, I'd encourage > you to think about not moving some of the data elsewhere, > particularly thefinding aid author, sponsor info (if applicable), > etc. ?I also wish that the finding author info could be managed as > linked agents, rather than just text, but even as text it's very > useful data! ?Also, it provides credit as well as some visibility to > archival labor (that's another reason I don't like the accordions, > since it hides that info by default). > I hope that helps. ?And I'm curious to hear more about whatever > direction you wind up taking! > That's an enormous help - I really appreciate your time and response! > All my best > > Mark > > Best, Bridger From andrew.morrison at bodleian.ox.ac.uk Tue Mar 2 03:24:46 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 2 Mar 2021 08:24:46 +0000 Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section In-Reply-To: <9b3b8f13d901a63aeb0f5ac5c60e82207ce172e5.camel@utk.edu> References: <78059f835620a4e6ac19b3cae56c93ea8fd08526.camel@utk.edu> <9b3b8f13d901a63aeb0f5ac5c60e82207ce172e5.camel@utk.edu> Message-ID: <9eec2b3b-3e09-4222-ea4a-5a5bd4b4b084@bodleian.ox.ac.uk> Note that not every field in the finding aid data section in the staff interface is displayed in the public user interface. There is a summary here: https://archivesspace.atlassian.net/browse/ANW-1055 Although the purpose of that ticket is to ask whether those choices should be changed in future releases. Also note the differences between the PUI, PDFs, and EAD export (including in the OAI-PMH service.) Each is controlled by separate code. Customizing what is included in PDFs and EAD is possible, but there are fewer examples out there to follow. Andrew. On 02/03/2021 01:18, Dyson-Smith, Bridger wrote: > Hi Mark - > > On Mon, 2021-03-01 at 17:11 +0000, Custer, Mark wrote: >> Hi Bridger, >> >> Just a very quick reply, as I haven't had time to look at the newest >> release of ArchiveSpace, but... >> ???1. Yes, I think you'd need to use a plugin or other mechanism to >> do this (lots of plugin examples out there, but if you have any >> questions about that, there are lots of people in the ASpace >> community that could help out). > That's great - we can integrate this change into our local plugin. > >> ???2. I don't like the accordion approach overall, so maybe that will >> be updated at some point, but that still doesn't help you right now, >> of course. >> ???3. Most importantly, if you do remove this section, I'd encourage >> you to think about not moving some of the data elsewhere, >> particularly thefinding aid author, sponsor info (if applicable), >> etc. ?I also wish that the finding author info could be managed as >> linked agents, rather than just text, but even as text it's very >> useful data! ?Also, it provides credit as well as some visibility to >> archival labor (that's another reason I don't like the accordions, >> since it hides that info by default). >> I hope that helps. ?And I'm curious to hear more about whatever >> direction you wind up taking! >> > That's an enormous help - I really appreciate your time and response! > >> All my best >> >> Mark >> >> > Best, > Bridger > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From andrew.morrison at bodleian.ox.ac.uk Tue Mar 2 04:21:08 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 2 Mar 2021 09:21:08 +0000 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> Message-ID: <43358837-7eab-b38e-f38d-154b318c367d@bodleian.ox.ac.uk> Also, if you have access to the Solr web interface, check whether there is a green tick next to "Current" in the core admin for the Solr core your ArchivesSpace system is using. If not, then you could try doubling AppConfig[:indexer_solr_timeout_seconds]) in config.rb, restarting ArchivesSpace, and running a soft re-index. We found, as we added more records, the time it took for Solr to commit in-memory changes to storage at the end of a re-index exceeded the time allowed by ArchivesSpace, so it got stuck in a loop. However, we only have one repository, so I don't what the effect might be when there are multiple. Andrew. On 02/03/2021 00:07, Blake Carver wrote: > Are there any errors in your logs? Look for ERROR and/or FATAL > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Mark Cyzyk > *Sent:* Monday, March 1, 2021 5:18 PM > *To:* Rachel Aileen Searcy ; Archivesspace > Users Group > *Subject:* Re: [Archivesspace_Users_Group] Containers not being > associated with their resources > > Thanks, Rachel! > > I've now completely reindexed everything (a "hard reindex") and still > no joy. > > I am noticing there is no "location.dat" file in our /indexer_pui_state/: > > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_archival_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_classification.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_classification_term.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_digital_object_component.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_digital_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_resource.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_archival_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_classification.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_classification_term.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_digital_object_component.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_digital_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_resource.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_archival_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_classification.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_classification_term.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_digital_object_component.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_digital_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_resource.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > _deletes_deletes.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > repositories_repositories.dat > > Should there be? > > Our two problem repositories here are 4 and 5.? The Staff interface > reports "0" Resources for both.? Yet when I run the Resources List > Report I do indeed get back a report with Resources.? Puzzling. > > It's like something in the backend DB has become disconnected, but > just for these two repositories.? Not sure how. > > If anyone has any suggestions, I would greatly appreciate hearing them! > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: >> Hi Mark >> >> We ran into a similar issue recently, where newly created containers >> were not being properly associated with the resource record, and >> updates to locations or barcodes were not showing up in searches or >> the Manage Top Containers view. We looked at the timestamp files for >> the indexer, and noticed that there was no location.dat file. We >> performed a soft re-index >> , >> after which our containers, barcodes, and locations resumed behaving >> as expected. We also have recurring monthly system restarts (which >> will now include a soft re-index going forward) built into our >> schedule, which seems to help with maintaining overall performance. >> >> I'm not sure if this is exactly what you're experiencing, but I hope >> it's helpful. Take care, >> Rachel >> >> On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk > > wrote: >> >> >> Dear ASpace list, >> >> ?From one of our Archivists: >> >> > When I create a new container, either manually or by spreadsheet >> > ingest, the container appears properly in the Instance field of >> the >> > record. From the resource, I can open the container record and it >> > appears to be associated with the resource correctly. However, >> in the >> > container management module, when I search for all containers >> > associated with the collection, the recently created container >> is not >> > listed. If I search for the new container's barcode, the container >> > appears in the search results but with no associated resource. >> I can >> > also locate the new containers by searching for unassociated >> containers. >> >> It seems like some linkage is not happening here. >> >> More, this is only happening in his Repository, not our other, >> larger >> Repository. >> >> Has anyone else run into this? >> >> Mark >> >> -- >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> >> _______________________________________________ >> 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= >> >> >> >> >> >> -- >> Rachel Searcy >> Accessioning Archivist, Archival Collections Management >> New York University Libraries >> 212.998.2539?| rachel.searcy at nyu.edu >> My pronouns are she/her/hers > > > _______________________________________________ > 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 bdysonsm at utk.edu Tue Mar 2 09:22:43 2021 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Tue, 2 Mar 2021 14:22:43 +0000 Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section In-Reply-To: <9eec2b3b-3e09-4222-ea4a-5a5bd4b4b084@bodleian.ox.ac.uk> References: <78059f835620a4e6ac19b3cae56c93ea8fd08526.camel@utk.edu> <9b3b8f13d901a63aeb0f5ac5c60e82207ce172e5.camel@utk.edu> <9eec2b3b-3e09-4222-ea4a-5a5bd4b4b084@bodleian.ox.ac.uk> Message-ID: <7f2538b08f6309726de3bd2caf63388ccac88abc.camel@utk.edu> Hi Andrew - Thank you for that link - that is very helpful! Best, Bridger On Tue, 2021-03-02 at 08:24 +0000, Andrew Morrison wrote: > Note that not every field in the finding aid data section in the > staff > interface is displayed in the public user interface. There is a > summary > here: > > https://archivesspace.atlassian.net/browse/ANW-1055 > > Although the purpose of that ticket is to ask whether those choices > should be changed in future releases. > > Also note the differences between the PUI, PDFs, and EAD export > (including in the OAI-PMH service.) Each is controlled by separate > code. > Customizing what is included in PDFs and EAD is possible, but there > are > fewer examples out there to follow. > > Andrew. > > > On 02/03/2021 01:18, Dyson-Smith, Bridger wrote: > > Hi Mark - > > > > On Mon, 2021-03-01 at 17:11 +0000, Custer, Mark wrote: > > > Hi Bridger, > > > > > > Just a very quick reply, as I haven't had time to look at the > > > newest > > > release of ArchiveSpace, but... > > > ????1. Yes, I think you'd need to use a plugin or other mechanism > > > to > > > do this (lots of plugin examples out there, but if you have any > > > questions about that, there are lots of people in the ASpace > > > community that could help out). > > That's great - we can integrate this change into our local plugin. > > ? > > > ????2. I don't like the accordion approach overall, so maybe that > > > will > > > be updated at some point, but that still doesn't help you right > > > now, > > > of course. > > > ????3. Most importantly, if you do remove this section, I'd > > > encourage > > > you to think about not moving some of the data elsewhere, > > > particularly thefinding aid author, sponsor info (if applicable), > > > etc. ?I also wish that the finding author info could be managed > > > as > > > linked agents, rather than just text, but even as text it's very > > > useful data! ?Also, it provides credit as well as some visibility > > > to > > > archival labor (that's another reason I don't like the > > > accordions, > > > since it hides that info by default). > > > I hope that helps. ?And I'm curious to hear more about whatever > > > direction you wind up taking! > > > > > That's an enormous help - I really appreciate your time and > > response! > > > > > All my best > > > > > > Mark > > > > > > > > Best, > > Bridger > > > > _______________________________________________ > > 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 From npwb2 at cam.ac.uk Tue Mar 2 10:01:15 2021 From: npwb2 at cam.ac.uk (Nick Butler) Date: Tue, 2 Mar 2021 15:01:15 +0000 Subject: [Archivesspace_Users_Group] Searches including colons Message-ID: Hi all, We're currently experimenting with creating a new index field (a StrField) for alternative forms of our resource and archival object identifiers. This field is largely working fine and behaving as expected, but over the course of testing this work out we've noticed that searches including colons don't appear to return any results, even when the exact content of the index field is used (with or without quotation marks around the whole search). Have other people experienced something similar? Is there a known workaround? Many thanks, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Mar 2 11:44:00 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 2 Mar 2021 16:44:00 +0000 Subject: [Archivesspace_Users_Group] Searches including colons In-Reply-To: References: Message-ID: How are you searching this field? If you've added it to the options in the PUI or SUI advanced search, it should be escaping the colon for you. If searching via the API, you probably need to do it yourself . Andrew. On 02/03/2021 15:01, Nick Butler wrote: > Hi all, > > We're currently experimenting with creating a new index field (a > StrField) for alternative forms of our resource and archival object > identifiers. This field is largely working fine and behaving as > expected, but over the course of testing this work out we've noticed > that searches including colons don't appear to return any results, > even when the exact content of the index field is used (with or > without quotation marks around the whole search). Have other people > experienced something similar? Is there a known workaround? > > Many thanks, > Nick > > _______________________________________________ > 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 npwb2 at cam.ac.uk Wed Mar 3 04:18:08 2021 From: npwb2 at cam.ac.uk (Nick Butler) Date: Wed, 3 Mar 2021 09:18:08 +0000 Subject: [Archivesspace_Users_Group] Searches including colons In-Reply-To: References: , Message-ID: Hi Andrew, We've added it to the PUI and SUI advanced search, in what I believe to be the standard manner (for the SUI, adding a line to search_definitions.rb, and for the PUI adding it to the :field_options arrays in the locals for the shared/search partial, in both the PUI search/search_results and welcome/show views). It's a *_u_sstr field, if that makes a difference, and we're storing multiple values in it. Exact (or wildcard) searches for any of the values being stored in the field are returning correct matches, except (as far as we can tell) when the searches contain colons, when they uniformly return no results. Many thanks, Nick ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: 02 March 2021 16:44 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Searches including colons How are you searching this field? If you've added it to the options in the PUI or SUI advanced search, it should be escaping the colon for you. If searching via the API, you probably need to do it yourself. Andrew. On 02/03/2021 15:01, Nick Butler wrote: Hi all, We're currently experimenting with creating a new index field (a StrField) for alternative forms of our resource and archival object identifiers. This field is largely working fine and behaving as expected, but over the course of testing this work out we've noticed that searches including colons don't appear to return any results, even when the exact content of the index field is used (with or without quotation marks around the whole search). Have other people experienced something similar? Is there a known workaround? Many thanks, Nick _______________________________________________ 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 MNovak at CSBSJU.EDU Wed Mar 3 09:43:57 2021 From: MNovak at CSBSJU.EDU (Novak, Miranda) Date: Wed, 3 Mar 2021 14:43:57 +0000 Subject: [Archivesspace_Users_Group] Past Perfect migration? Message-ID: Hello, My institution is brand-new to ArchivesSpace and has been using Past Perfect for 20+ years. I'm hoping to be directed to documentation to help me plan how to migrate data from Past Perfect into ArchivesSpace. Has anyone already done this and could you point me to the documents/videos that helped you? Thank you and apologies if this isn't an appropriate question for this group! Sincerely, Miranda Miranda Novak Assistant Director of Instructional Technology Clemens & Alcuin Libraries, IT Services College of Saint Benedict/Saint John's University 320-363-5923 mnovak at csbsju.edu Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Wed Mar 3 09:50:15 2021 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Wed, 3 Mar 2021 14:50:15 +0000 Subject: [Archivesspace_Users_Group] Past Perfect migration? In-Reply-To: References: Message-ID: Good morning Miranda, I do not believe that there is an existing import template for PastPerfect. That said, I know that PP will export into excel. From there, you could use the Harvard plugin to get your data into ASpace. (The plugin is part of the core code for version 2.8 (think I have the # right)). If you're using an earlier version, you can add the plugin and use it to import resource records from excel. (Your accession records can go in through the built in importer. It is doable - it will just require a bit of extra work. Good luck with the project! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Novak, Miranda Sent: Wednesday, March 3, 2021 9:44 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Past Perfect migration? Hello, My institution is brand-new to ArchivesSpace and has been using Past Perfect for 20+ years. I'm hoping to be directed to documentation to help me plan how to migrate data from Past Perfect into ArchivesSpace. Has anyone already done this and could you point me to the documents/videos that helped you? Thank you and apologies if this isn't an appropriate question for this group! Sincerely, Miranda Miranda Novak Assistant Director of Instructional Technology Clemens & Alcuin Libraries, IT Services College of Saint Benedict/Saint John's University 320-363-5923 mnovak at csbsju.edu Pronouns: she/her/hers CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From MNovak at CSBSJU.EDU Wed Mar 3 09:52:29 2021 From: MNovak at CSBSJU.EDU (Novak, Miranda) Date: Wed, 3 Mar 2021 14:52:29 +0000 Subject: [Archivesspace_Users_Group] Past Perfect migration? In-Reply-To: References: Message-ID: Hello, Thank you this is perfect! I expected I'd need to do some manipulation to my data to get it prepped for ASpace, but I was unsure of what mechanism to get data in. I will investigate this plugin. Thanks again, Miranda From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Solek, VivianLea Sent: Wednesday, March 3, 2021 8:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Past Perfect migration? Good morning Miranda, I do not believe that there is an existing import template for PastPerfect. That said, I know that PP will export into excel. From there, you could use the Harvard plugin to get your data into ASpace. (The plugin is part of the core code for version 2.8 (think I have the # right)). If you're using an earlier version, you can add the plugin and use it to import resource records from excel. (Your accession records can go in through the built in importer. It is doable - it will just require a bit of extra work. Good luck with the project! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Novak, Miranda Sent: Wednesday, March 3, 2021 9:44 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Past Perfect migration? Hello, My institution is brand-new to ArchivesSpace and has been using Past Perfect for 20+ years. I'm hoping to be directed to documentation to help me plan how to migrate data from Past Perfect into ArchivesSpace. Has anyone already done this and could you point me to the documents/videos that helped you? Thank you and apologies if this isn't an appropriate question for this group! Sincerely, Miranda Miranda Novak Assistant Director of Instructional Technology Clemens & Alcuin Libraries, IT Services College of Saint Benedict/Saint John's University 320-363-5923 mnovak at csbsju.edu Pronouns: she/her/hers CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gcoddington at mcdaniel.edu Wed Mar 3 09:54:04 2021 From: gcoddington at mcdaniel.edu (Gwenlyn Coddington) Date: Wed, 3 Mar 2021 14:54:04 +0000 Subject: [Archivesspace_Users_Group] Past Perfect migration? In-Reply-To: References: , Message-ID: Hi Miranda, I did a small-scale migration of past perfect records to ArchivesSpace over the summer (less than 1000 records). It was pretty messy, but I am happy to share some of the things I learned if you'd like to talk. My email is gcoddington at mcdaniel.edu Best regards, Gwen Coddington Gwenlyn Coddington Archivist and Special Collections Librarian, Hoover Library McDaniel College ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Solek, VivianLea Sent: Wednesday, March 3, 2021 9:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Past Perfect migration? CAUTION: This email originated from a non-McDaniel address. Do not click links or open attachments unless you recognize the sender and know the content is safe. Good morning Miranda, I do not believe that there is an existing import template for PastPerfect. That said, I know that PP will export into excel. From there, you could use the Harvard plugin to get your data into ASpace. (The plugin is part of the core code for version 2.8 (think I have the # right)). If you?re using an earlier version, you can add the plugin and use it to import resource records from excel. (Your accession records can go in through the built in importer. It is doable ? it will just require a bit of extra work. Good luck with the project! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Novak, Miranda Sent: Wednesday, March 3, 2021 9:44 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Past Perfect migration? Hello, My institution is brand-new to ArchivesSpace and has been using Past Perfect for 20+ years. I?m hoping to be directed to documentation to help me plan how to migrate data from Past Perfect into ArchivesSpace. Has anyone already done this and could you point me to the documents/videos that helped you? Thank you and apologies if this isn?t an appropriate question for this group! Sincerely, Miranda Miranda Novak Assistant Director of Instructional Technology Clemens & Alcuin Libraries, IT Services College of Saint Benedict/Saint John?s University 320-363-5923 mnovak at csbsju.edu Pronouns: she/her/hers CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Wed Mar 3 10:20:44 2021 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Wed, 3 Mar 2021 10:20:44 -0500 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> Message-ID: More: In our development environment, I configured full error logging.? I then ran one of our queries that is failing, stopped ASpace, then began scrutiny of archivesspace.out. Here are my disturbing findings: E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: DESCRIBE `agent_relationship_associative` E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1 E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1 E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: DESCRIBE `agent_relationship_earlierlater` E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: SELECT * FROM `agent_relationship_earlierlater` LIMIT 1 E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: SELECT * FROM `agent_relationship_earlierlater` LIMIT 1 E, [2021-03-03T09:47:30.000084 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: DESCRIBE `agent_relationship_parentchild` E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT * FROM `agent_relationship_parentchild` LIMIT 1 E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT * FROM `agent_relationship_parentchild` LIMIT 1 E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: DESCRIBE `agent_relationship_subordinatesuperior` E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT 1 E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT 1 E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: DESCRIBE `container_location` E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM `container_location` LIMIT 1 E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM `container_location` LIMIT 1 E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: DESCRIBE `note_bibliography` E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM `note_bibliography` LIMIT 1 E, [2021-03-03T09:47:30.606147 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM `note_bibliography` LIMIT 1 E, [2021-03-03T09:47:30.635130 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: DESCRIBE `note_digital_object` E, [2021-03-03T09:47:30.638129 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: SELECT * FROM `note_digital_object` LIMIT 1 E, [2021-03-03T09:47:30.645140 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: SELECT * FROM `note_digital_object` LIMIT 1 E, [2021-03-03T09:47:30.651197 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_index' doesn't exist: DESCRIBE `note_index`E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1 I took a look directly in the database and these tables are indeed missing. At this point, I am stumped.? I don't understand why, with these tables missing, one of our three Repositories would be working just fine -- the other two, not so much.? How could whole tables get deleted from our ASpace?? I'm guessing this happened a couple weeks ago. Any advice greatly appreciated, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 3/1/21 5:18 PM, Mark Cyzyk wrote: > > Thanks, Rachel! > > I've now completely reindexed everything (a "hard reindex") and still > no joy. > > I am noticing there is no "location.dat" file in our /indexer_pui_state/: > > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_archival_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_classification.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_classification_term.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_digital_object_component.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 3_digital_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 3_resource.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_archival_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_classification.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_classification_term.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_digital_object_component.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 4_digital_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 4_resource.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_archival_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_classification.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_classification_term.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_digital_object_component.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > 5_digital_object.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 5_resource.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > _deletes_deletes.dat > -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 > repositories_repositories.dat > > Should there be? > > Our two problem repositories here are 4 and 5.? The Staff interface > reports "0" Resources for both.? Yet when I run the Resources List > Report I do indeed get back a report with Resources.? Puzzling. > > It's like something in the backend DB has become disconnected, but > just for these two repositories.? Not sure how. > > If anyone has any suggestions, I would greatly appreciate hearing them! > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: >> Hi Mark >> >> We ran into a similar issue recently, where newly created containers >> were not being properly associated with the resource record, and >> updates to locations or barcodes were not showing up in searches or >> the Manage Top Containers view. We looked at the timestamp files for >> the indexer, and noticed that there was no location.dat file. We >> performed a soft re-index >> , >> after which our containers, barcodes, and locations resumed behaving >> as expected. We also have recurring monthly system restarts (which >> will now include a soft re-index going forward) built into our >> schedule, which seems to help with maintaining overall performance. >> >> I'm not sure if this is exactly what you're experiencing, but I hope >> it's helpful. Take care, >> Rachel >> >> On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk > > wrote: >> >> >> Dear ASpace list, >> >> ?From one of our Archivists: >> >> > When I create a new container, either manually or by spreadsheet >> > ingest, the container appears properly in the Instance field of >> the >> > record. From the resource, I can open the container record and it >> > appears to be associated with the resource correctly. However, >> in the >> > container management module, when I search for all containers >> > associated with the collection, the recently created container >> is not >> > listed. If I search for the new container's barcode, the container >> > appears in the search results but with no associated resource. >> I can >> > also locate the new containers by searching for unassociated >> containers. >> >> It seems like some linkage is not happening here. >> >> More, this is only happening in his Repository, not our other, >> larger >> Repository. >> >> Has anyone else run into this? >> >> Mark >> >> -- >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> >> _______________________________________________ >> 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= >> >> >> >> >> >> -- >> Rachel Searcy >> Accessioning Archivist, Archival Collections Management >> New York University Libraries >> 212.998.2539?| rachel.searcy at nyu.edu >> My pronouns are she/her/hers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Mar 3 10:30:00 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 3 Mar 2021 15:30:00 +0000 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> , Message-ID: Those MySQL errors look like the ones already reported and are probably not causing any problems. https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9 Turn the mysql error logging thing off and set the other loglevel errors to debug and look for any FATAL or ERROR in the logs. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Wednesday, March 3, 2021 10:20 AM To: Rachel Aileen Searcy ; Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Containers not being associated with their resources More: In our development environment, I configured full error logging. I then ran one of our queries that is failing, stopped ASpace, then began scrutiny of archivesspace.out. Here are my disturbing findings: E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: DESCRIBE `agent_relationship_associative` E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1 E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1 E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: DESCRIBE `agent_relationship_earlierlater` E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: SELECT * FROM `agent_relationship_earlierlater` LIMIT 1 E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: SELECT * FROM `agent_relationship_earlierlater` LIMIT 1 E, [2021-03-03T09:47:30.000084 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: DESCRIBE `agent_relationship_parentchild` E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT * FROM `agent_relationship_parentchild` LIMIT 1 E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT * FROM `agent_relationship_parentchild` LIMIT 1 E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: DESCRIBE `agent_relationship_subordinatesuperior` E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT 1 E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT 1 E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: DESCRIBE `container_location` E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM `container_location` LIMIT 1 E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM `container_location` LIMIT 1 E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: DESCRIBE `note_bibliography` E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM `note_bibliography` LIMIT 1 E, [2021-03-03T09:47:30.606147 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM `note_bibliography` LIMIT 1 E, [2021-03-03T09:47:30.635130 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: DESCRIBE `note_digital_object` E, [2021-03-03T09:47:30.638129 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: SELECT * FROM `note_digital_object` LIMIT 1 E, [2021-03-03T09:47:30.645140 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: SELECT * FROM `note_digital_object` LIMIT 1 E, [2021-03-03T09:47:30.651197 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_index' doesn't exist: DESCRIBE `note_index`E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1 I took a look directly in the database and these tables are indeed missing. At this point, I am stumped. I don't understand why, with these tables missing, one of our three Repositories would be working just fine -- the other two, not so much. How could whole tables get deleted from our ASpace? I'm guessing this happened a couple weeks ago. Any advice greatly appreciated, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 3/1/21 5:18 PM, Mark Cyzyk wrote: Thanks, Rachel! I've now completely reindexed everything (a "hard reindex") and still no joy. I am noticing there is no "location.dat" file in our /indexer_pui_state/: -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_classification.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_resource.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_classification.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_resource.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_archival_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_classification.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_classification_term.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_digital_object_component.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_digital_object.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_resource.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 _deletes_deletes.dat -rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 repositories_repositories.dat Should there be? Our two problem repositories here are 4 and 5. The Staff interface reports "0" Resources for both. Yet when I run the Resources List Report I do indeed get back a report with Resources. Puzzling. It's like something in the backend DB has become disconnected, but just for these two repositories. Not sure how. If anyone has any suggestions, I would greatly appreciate hearing them! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: Hi Mark We ran into a similar issue recently, where newly created containers were not being properly associated with the resource record, and updates to locations or barcodes were not showing up in searches or the Manage Top Containers view. We looked at the timestamp files for the indexer, and noticed that there was no location.dat file. We performed a soft re-index, after which our containers, barcodes, and locations resumed behaving as expected. We also have recurring monthly system restarts (which will now include a soft re-index going forward) built into our schedule, which seems to help with maintaining overall performance. I'm not sure if this is exactly what you're experiencing, but I hope it's helpful. Take care, Rachel On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk > wrote: Dear ASpace list, From one of our Archivists: > When I create a new container, either manually or by spreadsheet > ingest, the container appears properly in the Instance field of the > record. From the resource, I can open the container record and it > appears to be associated with the resource correctly. However, in the > container management module, when I search for all containers > associated with the collection, the recently created container is not > listed. If I search for the new container's barcode, the container > appears in the search results but with no associated resource. I can > also locate the new containers by searching for unassociated containers. It seems like some linkage is not happening here. More, this is only happening in his Repository, not our other, larger Repository. Has anyone else run into this? Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. _______________________________________________ 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Wed Mar 3 10:54:38 2021 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Wed, 3 Mar 2021 10:54:38 -0500 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> Message-ID: Thanks! No FATAL or ERROR now.? But there is this: INFO: [collection1] webapp= path=/select params={df=fullrecord&csv.escape=\&start=0&fq=-exclude_by_default:true&fq=publish:true&fq=types:pui&rows=1&bq=primary_type:resource^100+primary_type:accession^100+primary_type:subject^50+primary_type:agent_person^50+primary_type:agent_corporate_entity^30+primary_type:agent_family^30+&q=(uri:("\/repositories\/4\/resources\/1260"))&qf=title^25+four_part_id^50+fullrecord&pf=four_part_id^50&csv.header=true&csv.encapsulator="&wt=json&facet=true} hits=0 status=0 QTime=1 RecordNotFound: /repositories/4/resources/1260 <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 3/3/21 10:30 AM, Blake Carver wrote: > Those MySQL errors look like the ones already reported and are > probably not causing any problems. > > https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9 > > > Turn the mysql error logging thing off and set the other loglevel > errors to debug and look for any FATAL or ERROR in the logs. > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Mark Cyzyk > *Sent:* Wednesday, March 3, 2021 10:20 AM > *To:* Rachel Aileen Searcy ; Archivesspace > Users Group > *Subject:* Re: [Archivesspace_Users_Group] Containers not being > associated with their resources > > More: > > In our development environment, I configured full error logging.? I > then ran one of our queries that is failing, stopped ASpace, then > began scrutiny of archivesspace.out. > > Here are my disturbing findings: > > E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_associative' > doesn't exist: DESCRIBE `agent_relationship_associative` > E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_associative' > doesn't exist: SELECT * FROM `agent_relationship_associative` > LIMIT 1 > E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_associative' > doesn't exist: SELECT * FROM `agent_relationship_associative` > LIMIT 1 > E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_earlierlater' > doesn't exist: DESCRIBE `agent_relationship_earlierlater` > E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_earlierlater' > doesn't exist: SELECT * FROM `agent_relationship_earlierlater` > LIMIT 1 > E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_earlierlater' > doesn't exist: SELECT * FROM `agent_relationship_earlierlater` > LIMIT 1 > E, [2021-03-03T09:47:30.000084 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_parentchild' > doesn't exist: DESCRIBE `agent_relationship_parentchild` > E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_parentchild' > doesn't exist: SELECT * FROM `agent_relationship_parentchild` > LIMIT 1 > E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_parentchild' > doesn't exist: SELECT * FROM `agent_relationship_parentchild` > LIMIT 1 > E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' > doesn't exist: DESCRIBE `agent_relationship_subordinatesuperior` > E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' > doesn't exist: SELECT * FROM > `agent_relationship_subordinatesuperior` LIMIT 1 > E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' > doesn't exist: SELECT * FROM > `agent_relationship_subordinatesuperior` LIMIT 1 > > > > E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.container_location' doesn't > exist: DESCRIBE `container_location` > E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.container_location' doesn't > exist: SELECT * FROM `container_location` LIMIT 1 > E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.container_location' doesn't > exist: SELECT * FROM `container_location` LIMIT 1 > > > > E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_bibliography' doesn't > exist: DESCRIBE `note_bibliography` > E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_bibliography' doesn't > exist: SELECT * FROM `note_bibliography` LIMIT 1 > E, [2021-03-03T09:47:30.606147 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_bibliography' doesn't > exist: SELECT * FROM `note_bibliography` LIMIT 1 > E, [2021-03-03T09:47:30.635130 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_digital_object' doesn't > exist: DESCRIBE `note_digital_object` > E, [2021-03-03T09:47:30.638129 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_digital_object' doesn't > exist: SELECT * FROM `note_digital_object` LIMIT 1 > E, [2021-03-03T09:47:30.645140 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_digital_object' doesn't > exist: SELECT * FROM `note_digital_object` LIMIT 1 > E, [2021-03-03T09:47:30.651197 #27625] ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table 'archivesspaceDevelopment.note_index' doesn't exist: > DESCRIBE `note_index`E, [2021-03-03T09:47:29.960346 #27625] > ERROR -- : > Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: > Table > 'archivesspaceDevelopment.agent_relationship_associative' > doesn't exist: SELECT * FROM `agent_relationship_associative` > LIMIT 1 > > > > I took a look directly in the database and these tables are indeed > missing. > > At this point, I am stumped.? I don't understand why, with these > tables missing, one of our three Repositories would be working just > fine -- the other two, not so much.? How could whole tables get > deleted from our ASpace?? I'm guessing this happened a couple weeks ago. > > Any advice greatly appreciated, > > Mark > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 3/1/21 5:18 PM, Mark Cyzyk wrote: >> >> Thanks, Rachel! >> >> I've now completely reindexed everything (a "hard reindex") and still >> no joy. >> >> I am noticing there is no "location.dat" file in our /indexer_pui_state/: >> >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 3_archival_object.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 3_classification.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 3_classification_term.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 3_digital_object_component.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 3_digital_object.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 3_resource.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 4_archival_object.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 4_classification.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 4_classification_term.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 4_digital_object_component.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 4_digital_object.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 4_resource.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 5_archival_object.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 5_classification.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 5_classification_term.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 5_digital_object_component.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 5_digital_object.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> 5_resource.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> _deletes_deletes.dat >> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >> repositories_repositories.dat >> >> Should there be? >> >> Our two problem repositories here are 4 and 5.? The Staff interface >> reports "0" Resources for both.? Yet when I run the Resources List >> Report I do indeed get back a report with Resources.? Puzzling. >> >> It's like something in the backend DB has become disconnected, but >> just for these two repositories.? Not sure how. >> >> If anyone has any suggestions, I would greatly appreciate hearing them! >> >> Mark >> >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: >>> Hi Mark >>> >>> We ran into a similar issue recently, where newly created containers >>> were not being properly associated with the resource record, and >>> updates to locations or barcodes were not showing up in searches or >>> the Manage Top Containers view. We looked at the timestamp files for >>> the indexer, and noticed that there was no location.dat file. We >>> performed a soft re-index >>> , >>> after which our containers, barcodes, and locations resumed behaving >>> as expected. We also have recurring monthly system restarts (which >>> will now include a soft re-index going forward) built into our >>> schedule, which seems to help with maintaining overall performance. >>> >>> I'm not sure if this is exactly what you're experiencing, but I hope >>> it's helpful. Take care, >>> Rachel >>> >>> On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk >> > wrote: >>> >>> >>> Dear ASpace list, >>> >>> ?From one of our Archivists: >>> >>> > When I create a new container, either manually or by spreadsheet >>> > ingest, the container appears properly in the Instance field >>> of the >>> > record. From the resource, I can open the container record and it >>> > appears to be associated with the resource correctly. However, >>> in the >>> > container management module, when I search for all containers >>> > associated with the collection, the recently created container >>> is not >>> > listed. If I search for the new container's barcode, the >>> container >>> > appears in the search results but with no associated resource. >>> I can >>> > also locate the new containers by searching for unassociated >>> containers. >>> >>> It seems like some linkage is not happening here. >>> >>> More, this is only happening in his Repository, not our other, >>> larger >>> Repository. >>> >>> Has anyone else run into this? >>> >>> Mark >>> >>> -- >>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>> Mark Cyzyk, M.A., M.L.S. >>> Library Applications Group >>> The Sheridan Libraries >>> The Johns Hopkins University >>> mcyzyk at jhu.edu >>> >>> Verba volant, scripta manent. >>> >>> _______________________________________________ >>> 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= >>> >>> >>> >>> >>> >>> -- >>> Rachel Searcy >>> Accessioning Archivist, Archival Collections Management >>> New York University Libraries >>> 212.998.2539?| rachel.searcy at nyu.edu >>> My pronouns are she/her/hers >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Wed Mar 3 12:51:21 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 3 Mar 2021 17:51:21 +0000 Subject: [Archivesspace_Users_Group] CollectionSpace (LYRASIS) webinar announcement: Data Migrations Discussion Message-ID: <37FAB6A1-97FD-4B4B-9536-EB87E47DBAB8@lyrasis.org> [Posted on behalf of our colleague Linda Colet at LYRASIS. Please contact Linda at linda.colet at lyrasis.org for more information] Community Collections Spotlight: Data Migrations Discussion Data migrations can be intimidating for everyone, but there are ways to think about and organize them that can make them more likely to succeed. This discussion session will feature two panelists: Jeremy Katz from the Breman Museum, who recently completed a collections management system migration, and Kristina Spurgin, data migration specialist at LYRASIS. Jeremy will speak about the process from the perspective of a museum professional, including highlighting the methods and practices that worked best during the Breman?s migration. Kristina has worked with a wide variety of data and systems during her career and will speak more broadly about some of the challenges and potential pitfalls of data migrations, as well as strategies she has employed to make the process more transparent, auditable, and safe. Speakers: Kristina Spurgin, Data Migration Specialist, LYRASIS and Jeremy R Katz, Senior Director, Archives, the Breman Date & Time: March 4, 2021, 1:00 - 2:30 PM EST Register at: https://www.lyrasis.org/Content/Pages/Event-Details.aspx?Eid=4E684E81-4436-EB11-80ED-00155DE5EC03 Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Wed Mar 3 16:29:29 2021 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Wed, 3 Mar 2021 16:29:29 -0500 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> Message-ID: <995b771f-198a-59e2-353a-ecbf9df039ce@jhu.edu> More: I turned back on the DB logging, forced the same error, and here is part of what I captured: I, [2021-03-03T12:31:02.401423 #29270]? INFO -- : (0.023387s) SELECT * FROM `note` WHERE (`lang_material_id` IN (1058)) I, [2021-03-03T12:31:02.406634 #29270]? INFO -- : (0.005770s) SELECT 1 AS `one` FROM `archival_object` INNER JOIN `enumeration_value` AS `level_enum` ON (`level_enum`.`id` = `archival_object`.`level_id`) WHERE ((`archival_object`.`id` != `archival_object`.`id`) AND (`archival_object`.`component_id` IS NOT NULL) AND ((`level_enum`.`value` IN ('series')) OR ((`level_enum`.`value` = 'otherlevel') AND (lower(`other_level`) IN ('accession'))))) LIMIT 1 I, [2021-03-03T12:31:02.407401 #29270]? INFO -- : (0.007306s) SELECT * FROM `instance_do_link_rlshp` WHERE (`instance_id` IN (238583)) I, [2021-03-03T12:31:02.409280 #29270]? INFO -- : (0.005184s) SELECT * FROM `note` WHERE (`lang_material_id` IN (1059, 2127)) I, [2021-03-03T12:31:02.409613 #29270]? INFO -- : (0.002386s) SELECT * FROM `top_container_link_rlshp` WHERE (`top_container_id` = 9074) I, [2021-03-03T12:31:02.410056 #29270]? INFO -- : (0.000203s) SELECT * FROM `subnote_metadata` WHERE (`note_id` IN (205950)) I, [2021-03-03T12:31:02.410913 #29270]? INFO -- : (0.012668s) SELECT * FROM `note` WHERE (`lang_material_id` IN (1140, 2095)) RecordNotFound: /repositories/4/resources/1260 Working my way up from the error, this query is returning 0 rows: ?SELECT * FROM `instance_do_link_rlshp` WHERE (`instance_id` IN (238583)) <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 3/3/21 10:54 AM, Mark Cyzyk wrote: > > Thanks! > > No FATAL or ERROR now.? But there is this: > > INFO: [collection1] webapp= path=/select > params={df=fullrecord&csv.escape=\&start=0&fq=-exclude_by_default:true&fq=publish:true&fq=types:pui&rows=1&bq=primary_type:resource^100+primary_type:accession^100+primary_type:subject^50+primary_type:agent_person^50+primary_type:agent_corporate_entity^30+primary_type:agent_family^30+&q=(uri:("\/repositories\/4\/resources\/1260"))&qf=title^25+four_part_id^50+fullrecord&pf=four_part_id^50&csv.header=true&csv.encapsulator="&wt=json&facet=true} > hits=0 status=0 QTime=1 > RecordNotFound: /repositories/4/resources/1260 > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 3/3/21 10:30 AM, Blake Carver wrote: >> Those MySQL errors look like the ones already reported and are >> probably not causing any problems. >> >> https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9 >> >> >> Turn the mysql error logging thing off and set the other loglevel >> errors to debug and look for any FATAL or ERROR in the logs. >> ------------------------------------------------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >> on behalf >> of Mark Cyzyk >> *Sent:* Wednesday, March 3, 2021 10:20 AM >> *To:* Rachel Aileen Searcy ; Archivesspace >> Users Group >> *Subject:* Re: [Archivesspace_Users_Group] Containers not being >> associated with their resources >> >> More: >> >> In our development environment, I configured full error logging.? I >> then ran one of our queries that is failing, stopped ASpace, then >> began scrutiny of archivesspace.out. >> >> Here are my disturbing findings: >> >> E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_associative' >> doesn't exist: DESCRIBE `agent_relationship_associative` >> E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_associative' >> doesn't exist: SELECT * FROM `agent_relationship_associative` >> LIMIT 1 >> E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_associative' >> doesn't exist: SELECT * FROM `agent_relationship_associative` >> LIMIT 1 >> E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_earlierlater' >> doesn't exist: DESCRIBE `agent_relationship_earlierlater` >> E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_earlierlater' >> doesn't exist: SELECT * FROM >> `agent_relationship_earlierlater` LIMIT 1 >> E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_earlierlater' >> doesn't exist: SELECT * FROM >> `agent_relationship_earlierlater` LIMIT 1 >> E, [2021-03-03T09:47:30.000084 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_parentchild' >> doesn't exist: DESCRIBE `agent_relationship_parentchild` >> E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_parentchild' >> doesn't exist: SELECT * FROM `agent_relationship_parentchild` >> LIMIT 1 >> E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_parentchild' >> doesn't exist: SELECT * FROM `agent_relationship_parentchild` >> LIMIT 1 >> E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' >> doesn't exist: DESCRIBE `agent_relationship_subordinatesuperior` >> E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' >> doesn't exist: SELECT * FROM >> `agent_relationship_subordinatesuperior` LIMIT 1 >> E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' >> doesn't exist: SELECT * FROM >> `agent_relationship_subordinatesuperior` LIMIT 1 >> >> >> >> E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.container_location' doesn't >> exist: DESCRIBE `container_location` >> E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.container_location' doesn't >> exist: SELECT * FROM `container_location` LIMIT 1 >> E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.container_location' doesn't >> exist: SELECT * FROM `container_location` LIMIT 1 >> >> >> >> E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_bibliography' doesn't >> exist: DESCRIBE `note_bibliography` >> E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_bibliography' doesn't >> exist: SELECT * FROM `note_bibliography` LIMIT 1 >> E, [2021-03-03T09:47:30.606147 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_bibliography' doesn't >> exist: SELECT * FROM `note_bibliography` LIMIT 1 >> E, [2021-03-03T09:47:30.635130 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_digital_object' doesn't >> exist: DESCRIBE `note_digital_object` >> E, [2021-03-03T09:47:30.638129 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_digital_object' doesn't >> exist: SELECT * FROM `note_digital_object` LIMIT 1 >> E, [2021-03-03T09:47:30.645140 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_digital_object' doesn't >> exist: SELECT * FROM `note_digital_object` LIMIT 1 >> E, [2021-03-03T09:47:30.651197 #27625] ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table 'archivesspaceDevelopment.note_index' doesn't exist: >> DESCRIBE `note_index`E, [2021-03-03T09:47:29.960346 #27625] >> ERROR -- : >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >> Table >> 'archivesspaceDevelopment.agent_relationship_associative' >> doesn't exist: SELECT * FROM `agent_relationship_associative` >> LIMIT 1 >> >> >> >> I took a look directly in the database and these tables are indeed >> missing. >> >> At this point, I am stumped.? I don't understand why, with these >> tables missing, one of our three Repositories would be working just >> fine -- the other two, not so much.? How could whole tables get >> deleted from our ASpace?? I'm guessing this happened a couple weeks ago. >> >> Any advice greatly appreciated, >> >> Mark >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> On 3/1/21 5:18 PM, Mark Cyzyk wrote: >>> >>> Thanks, Rachel! >>> >>> I've now completely reindexed everything (a "hard reindex") and >>> still no joy. >>> >>> I am noticing there is no "location.dat" file in our >>> /indexer_pui_state/: >>> >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 3_archival_object.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 3_classification.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 3_classification_term.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 3_digital_object_component.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 3_digital_object.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 3_resource.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 4_archival_object.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 4_classification.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 4_classification_term.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 4_digital_object_component.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 4_digital_object.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 4_resource.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 5_archival_object.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 5_classification.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 5_classification_term.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 5_digital_object_component.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 5_digital_object.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> 5_resource.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> _deletes_deletes.dat >>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>> repositories_repositories.dat >>> >>> Should there be? >>> >>> Our two problem repositories here are 4 and 5.? The Staff interface >>> reports "0" Resources for both.? Yet when I run the Resources List >>> Report I do indeed get back a report with Resources.? Puzzling. >>> >>> It's like something in the backend DB has become disconnected, but >>> just for these two repositories.? Not sure how. >>> >>> If anyone has any suggestions, I would greatly appreciate hearing them! >>> >>> Mark >>> >>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>> Mark Cyzyk, M.A., M.L.S. >>> Library Applications Group >>> The Sheridan Libraries >>> The Johns Hopkins University >>> mcyzyk at jhu.edu >>> >>> Verba volant, scripta manent. >>> On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: >>>> Hi Mark >>>> >>>> We ran into a similar issue recently, where newly created >>>> containers were not being properly associated with the resource >>>> record, and updates to locations or barcodes were not showing up in >>>> searches or the Manage Top Containers view. We looked at the >>>> timestamp files for the indexer, and noticed that there was no >>>> location.dat file. We performed a soft re-index >>>> , >>>> after which our containers, barcodes, and locations resumed >>>> behaving as expected. We also have recurring monthly system >>>> restarts (which will now include a soft re-index going forward) >>>> built into our schedule, which seems to help with maintaining >>>> overall performance. >>>> >>>> I'm not sure if this is exactly what you're experiencing, but I >>>> hope it's helpful. Take care, >>>> Rachel >>>> >>>> On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk >>> > wrote: >>>> >>>> >>>> Dear ASpace list, >>>> >>>> ?From one of our Archivists: >>>> >>>> > When I create a new container, either manually or by spreadsheet >>>> > ingest, the container appears properly in the Instance field >>>> of the >>>> > record. From the resource, I can open the container record >>>> and it >>>> > appears to be associated with the resource correctly. >>>> However, in the >>>> > container management module, when I search for all containers >>>> > associated with the collection, the recently created >>>> container is not >>>> > listed. If I search for the new container's barcode, the >>>> container >>>> > appears in the search results but with no associated >>>> resource. I can >>>> > also locate the new containers by searching for unassociated >>>> containers. >>>> >>>> It seems like some linkage is not happening here. >>>> >>>> More, this is only happening in his Repository, not our other, >>>> larger >>>> Repository. >>>> >>>> Has anyone else run into this? >>>> >>>> Mark >>>> >>>> -- >>>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>>> Mark Cyzyk, M.A., M.L.S. >>>> Library Applications Group >>>> The Sheridan Libraries >>>> The Johns Hopkins University >>>> mcyzyk at jhu.edu >>>> >>>> Verba volant, scripta manent. >>>> >>>> _______________________________________________ >>>> 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Rachel Searcy >>>> Accessioning Archivist, Archival Collections Management >>>> New York University Libraries >>>> 212.998.2539?| rachel.searcy at nyu.edu >>>> My pronouns are she/her/hers >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Mar 4 06:21:57 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 4 Mar 2021 11:21:57 +0000 Subject: [Archivesspace_Users_Group] Searches including colons In-Reply-To: References: Message-ID: <88846bb7-816f-ecec-26b1-019366391d47@bodleian.ox.ac.uk> I think your problem is here: https://github.com/archivesspace/archivesspace/blob/4554d0b8bb47558f18bbcae2f63bea84effc9b28/backend/app/model/advanced_query_string.rb#L84-L95 The backend, when converting the "advanced_query" data structures the PUI and SUI send it into Solr queries, is stripping out colons. That might work if the index field were "text_general" but for a "string" type Solr does no tokenization, so matches have to be exact. If you look further up in the same file, it will escape colons, which is what you want, if this condition is met: https://github.com/archivesspace/archivesspace/blob/4554d0b8bb47558f18bbcae2f63bea84effc9b28/backend/app/model/advanced_query_string.rb#L54 But I don't know how you'd go about triggering that. Andrew. On 03/03/2021 09:18, Nick Butler wrote: > Hi Andrew, > > We've added it to the PUI and SUI advanced search, in what I believe > to be the standard manner (for the SUI, adding a line to > search_definitions.rb, and for the PUI adding it to the :field_options > arrays in the locals for the shared/search partial, in both the PUI > search/search_results and welcome/show views). It's a *_u_sstr field, > if that makes a difference, and we're storing multiple values in it. > Exact (or wildcard) searches for any of the values being stored in the > field are returning correct matches, except (as far as we can tell) > when the searches contain colons, when they uniformly return no results. > > Many thanks, > Nick > > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Andrew Morrison > *Sent:* 02 March 2021 16:44 > *To:* archivesspace_users_group at lyralists.lyrasis.org > > *Subject:* Re: [Archivesspace_Users_Group] Searches including colons > > How are you searching this field? If you've added it to the options in > the PUI or SUI advanced search, it should be escaping the colon for > you. If searching via the API, you probably need to do it yourself > . > > > Andrew. > > > > On 02/03/2021 15:01, Nick Butler wrote: >> Hi all, >> >> We're currently experimenting with creating a new index field (a >> StrField) for alternative forms of our resource and archival object >> identifiers. This field is largely working fine and behaving as >> expected, but over the course of testing this work out we've noticed >> that searches including colons don't appear to return any results, >> even when the exact content of the index field is used (with or >> without quotation marks around the whole search). Have other people >> experienced something similar? Is there a known workaround? >> >> Many thanks, >> Nick >> >> _______________________________________________ >> 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 andrew.morrison at bodleian.ox.ac.uk Thu Mar 4 06:44:54 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 4 Mar 2021 11:44:54 +0000 Subject: [Archivesspace_Users_Group] Searches including colons In-Reply-To: <88846bb7-816f-ecec-26b1-019366391d47@bodleian.ox.ac.uk> References: <88846bb7-816f-ecec-26b1-019366391d47@bodleian.ox.ac.uk> Message-ID: Probably the easiest fix would be to change your plug-in so that it convert colons to spaces when indexing this new field. Andrew. On 04/03/2021 11:21, Andrew Morrison wrote: > > I think your problem is here: > > > https://github.com/archivesspace/archivesspace/blob/4554d0b8bb47558f18bbcae2f63bea84effc9b28/backend/app/model/advanced_query_string.rb#L84-L95 > > > The backend, when converting the "advanced_query" data structures the > PUI and SUI send it into Solr queries, is stripping out colons. That > might work if the index field were "text_general" but for a "string" > type Solr does no tokenization, so matches have to be exact. > > > If you look further up in the same file, it will escape colons, which > is what you want, if this condition is met: > > > https://github.com/archivesspace/archivesspace/blob/4554d0b8bb47558f18bbcae2f63bea84effc9b28/backend/app/model/advanced_query_string.rb#L54 > > > But I don't know how you'd go about triggering that. > > > Andrew. > > > > On 03/03/2021 09:18, Nick Butler wrote: >> Hi Andrew, >> >> We've added it to the PUI and SUI advanced search, in what I believe >> to be the standard manner (for the SUI, adding a line to >> search_definitions.rb, and for the PUI adding it to the >> :field_options arrays in the locals for the shared/search partial, in >> both the PUI search/search_results and welcome/show views). It's a >> *_u_sstr field, if that makes a difference, and we're storing >> multiple values in it. Exact (or wildcard) searches for any of the >> values being stored in the field are returning correct matches, >> except (as far as we can tell) when the searches contain colons, when >> they uniformly return no results. >> >> Many thanks, >> Nick >> >> ------------------------------------------------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >> on behalf >> of Andrew Morrison >> *Sent:* 02 March 2021 16:44 >> *To:* archivesspace_users_group at lyralists.lyrasis.org >> >> *Subject:* Re: [Archivesspace_Users_Group] Searches including colons >> >> How are you searching this field? If you've added it to the options >> in the PUI or SUI advanced search, it should be escaping the colon >> for you. If searching via the API, you probably need to do it >> yourself >> . >> >> >> Andrew. >> >> >> >> On 02/03/2021 15:01, Nick Butler wrote: >>> Hi all, >>> >>> We're currently experimenting with creating a new index field (a >>> StrField) for alternative forms of our resource and archival object >>> identifiers. This field is largely working fine and behaving as >>> expected, but over the course of testing this work out we've noticed >>> that searches including colons don't appear to return any results, >>> even when the exact content of the index field is used (with or >>> without quotation marks around the whole search). Have other people >>> experienced something similar? Is there a known workaround? >>> >>> Many thanks, >>> Nick >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Mar 4 10:24:41 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 4 Mar 2021 15:24:41 +0000 Subject: [Archivesspace_Users_Group] OSS LYRASIS Research Survey: Participation Requested Message-ID: [Posted on behalf of our colleague Hannah Rosen at LYRASIS. Please contact Hannah at hannah.rosen at lyrasis.org for more information] Dear Colleagues, We are excited to announce the release of our 2021 LYRASIS Research survey! This year the survey focuses on challenges and opportunities in community-supported open source software (OSS). We welcome your participation in this survey. The survey will offer LYRASIS members, users and participants in the GLAM (galleries, libraries, archives and museums) community a new perspective and understanding of how our institutions interact with and support GLAM-focused OSS. The survey is divided into three sections: (1) funding/supporting OSS, (2) justifying OSS, and (3) evaluating OSS. It is intended to cover the span of an institution?s OSS activities, so please share the survey with your colleagues for questions that lie outside of your job duties. Please take approximately 25 minutes to fill out the following survey: http://bit.ly/37Tj10K The deadline for participation is April 2nd, 2021. At the beginning of the survey you will be asked for your name, institution and job title. All of this information will remain confidential and will not be included in any external publications/reports or presentations. We are merely using this information to identify duplicate entries from institutions across our distribution channels. For those participants who prefer to see all of the question in advance, a PDF copy of the survey has been attached to this email. As a reminder, the LYRASIS Research surveys are guided by member input. Leaders Circle members selected the research topic at our fall forum in October 2020, and then afterwards volunteer members participated in focus groups to determine the scope of the survey and potential questions. Volunteers also assisted LYRASIS staff with final reviews and edits. We at LYRASIS are grateful to be able to perform research developed by and for our community. Please contact Hannah Rosen, hannah.rosen at lyrasis.org with any questions. Thank you, LYRASIS Research and Innovation Team Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From npwb2 at cam.ac.uk Thu Mar 4 10:45:33 2021 From: npwb2 at cam.ac.uk (Nick Butler) Date: Thu, 4 Mar 2021 15:45:33 +0000 Subject: [Archivesspace_Users_Group] Searches including colons In-Reply-To: References: <88846bb7-816f-ecec-26b1-019366391d47@bodleian.ox.ac.uk>, Message-ID: Hi Andrew, Thank you very much, that sounds like an excellent solution. I'd tried tweaking the advanced_query_string model in a development instance without reliable success, but simply converting the colons to spaces ought to work nicely. Many thanks again, Nick ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: 04 March 2021 11:44 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Searches including colons Probably the easiest fix would be to change your plug-in so that it convert colons to spaces when indexing this new field. Andrew. On 04/03/2021 11:21, Andrew Morrison wrote: I think your problem is here: https://github.com/archivesspace/archivesspace/blob/4554d0b8bb47558f18bbcae2f63bea84effc9b28/backend/app/model/advanced_query_string.rb#L84-L95 The backend, when converting the "advanced_query" data structures the PUI and SUI send it into Solr queries, is stripping out colons. That might work if the index field were "text_general" but for a "string" type Solr does no tokenization, so matches have to be exact. If you look further up in the same file, it will escape colons, which is what you want, if this condition is met: https://github.com/archivesspace/archivesspace/blob/4554d0b8bb47558f18bbcae2f63bea84effc9b28/backend/app/model/advanced_query_string.rb#L54 But I don't know how you'd go about triggering that. Andrew. On 03/03/2021 09:18, Nick Butler wrote: Hi Andrew, We've added it to the PUI and SUI advanced search, in what I believe to be the standard manner (for the SUI, adding a line to search_definitions.rb, and for the PUI adding it to the :field_options arrays in the locals for the shared/search partial, in both the PUI search/search_results and welcome/show views). It's a *_u_sstr field, if that makes a difference, and we're storing multiple values in it. Exact (or wildcard) searches for any of the values being stored in the field are returning correct matches, except (as far as we can tell) when the searches contain colons, when they uniformly return no results. Many thanks, Nick ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: 02 March 2021 16:44 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Searches including colons How are you searching this field? If you've added it to the options in the PUI or SUI advanced search, it should be escaping the colon for you. If searching via the API, you probably need to do it yourself. Andrew. On 02/03/2021 15:01, Nick Butler wrote: Hi all, We're currently experimenting with creating a new index field (a StrField) for alternative forms of our resource and archival object identifiers. This field is largely working fine and behaving as expected, but over the course of testing this work out we've noticed that searches including colons don't appear to return any results, even when the exact content of the index field is used (with or without quotation marks around the whole search). Have other people experienced something similar? Is there a known workaround? Many thanks, Nick _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtenenho at rand.org Thu Mar 4 11:36:32 2021 From: dtenenho at rand.org (Tenenholtz, David) Date: Thu, 4 Mar 2021 16:36:32 +0000 Subject: [Archivesspace_Users_Group] Local plugin disabled and aspace_diagnostic not present Message-ID: <55DAF2A9-C900-4335-949C-2D555A47B356@rand.org> Hi James, Thanks so much for your insights on this issue and for those suggestions on where to look for possible errors. In the end, it was beneficial for me to simply eliminate some errant whitespace in the config.rb file below the AppConfig[:plugins] statement. A larger takeaway is that presence of whitespace in the config.rb file is very unforgiving. In any case, I?m happy to say this issue is now resolved. Kind regards, David -- David Tenenholtz (he/him) Digital Archivist, RAND Corporation 1776 Main Street P.O. Box 2138 Santa Monica, CA 90407-2138 (310) 393-0411 x6188 dtenenho at rand.org From: James Bullen Reply-To: Archivesspace Users Group Date: Sunday, February 21, 2021 at 3:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Local plugin disabled and aspace_diagnostic not present Hi David, Not sure what?s going on, but a few points to note: - The absence of an aspace_diagnostic file is a good sign because it only gets written if something goes wrong during start up. - There is no need to run 'initialize-plugin.sh local' unless you are using gems in your local plugin. That message is just noting that there is no plugins/local/Gemfile, so there is nothing to do. - Check that you have ?local? in AppConfig[:plugins]. - You mention ?plugin/local/??, I guess this is a typo, but make sure the directory is ?plugins/local/?' - From memory, that gear icon only appears if you have a plugin that has a config.yml that specifies a menu item. Cheers, James On Feb 20, 2021, at 4:11 AM, Tenenholtz, David > wrote: Hello! I?m standing up the v.2.8.1 release in production, and am running into a persistent issue that keeps the local plugin from being enabled. I have not been able to identify if this is related to the prior bug in older releases having to do with the gem bundler, but I suspect that a gem (or the bundler?) is being blocked here. Although I have the same content in plugin/local/frontend and plugin/local/public running happily on a test server on matching infrastructure, I?m not having any luck getting the local plugin to initialize on prod. Under /data/tmp there is also no aspace_diagnostic text file to interrogate. In the staff GUI I?m not seeing the Plug-ins list item within the dropdown under the gear icon. Tech specs (matching on test server and production server): RHEL7.9 VM openjdk 1.8.0_282 mysql Ver 15.1 distrib 5.5.68-MariaDB Apache/2.4.6 During the building of the production application, I noticed the issue, and so I ran ?initialize-plugin.sh local? from within the scripts folder, but got an error related to a Gemfile not being present within the ?local? folder. If anyone has any pointers on how to get the aspace_diagnostic to generate under /data/tmp, or any other avenues for me to pursue here with initializing the local plugin properly, I?d be so grateful! Kind regards, David -- David Tenenholtz (he/him) Digital Archivist, RAND Corporation 1776 Main Street P.O. Box 2138 Santa Monica, CA 90407-2138 (310) 393-0411 x6188 dtenenho at rand.org __________________________________________________________________________ This email message is for the sole use of the intended recipient(s) and may contain information that is sensitive, proprietary, and/or privileged. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group __________________________________________________________________________ This email message is for the sole use of the intended recipient(s) and may contain information that is sensitive, proprietary, and/or privileged. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Thu Mar 4 15:01:49 2021 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Thu, 4 Mar 2021 15:01:49 -0500 Subject: [Archivesspace_Users_Group] Containers not being associated with their resources In-Reply-To: <995b771f-198a-59e2-353a-ecbf9df039ce@jhu.edu> References: <1944c45d-be2b-8831-41f1-acbcc53f3c6f@jhu.edu> <995b771f-198a-59e2-353a-ecbf9df039ce@jhu.edu> Message-ID: <5a8e43e1-8f67-c3c1-3b17-6a13ed658c29@jhu.edu> Still more: I have attached three images. 1. Showing our Peabody Repository as having 0 Resources 2. Showing a test Resource we manually created in that repository (a image 1 above really should at least be reporting "1") 3. The output of the Resources List Report for the Peabody repository showing 140+ Resources Reindexing does nothing to reconnect these Resources in the missing places to their Repository. Is there some kind of database maintenance utility I can run to make this reconnect happen? Worried, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 3/3/21 4:29 PM, Mark Cyzyk wrote: > > More: > > I turned back on the DB logging, forced the same error, and here is > part of what I captured: > > I, [2021-03-03T12:31:02.401423 #29270]? INFO -- : (0.023387s) > SELECT * FROM `note` WHERE (`lang_material_id` IN (1058)) > I, [2021-03-03T12:31:02.406634 #29270]? INFO -- : (0.005770s) > SELECT 1 AS `one` FROM `archival_object` INNER JOIN > `enumeration_value` AS `level_enum` ON (`level_enum`.`id` = > `archival_object`.`level_id`) WHERE ((`archival_object`.`id` != > `archival_object`.`id`) AND (`archival_object`.`component_id` IS > NOT NULL) AND ((`level_enum`.`value` IN ('series')) OR > ((`level_enum`.`value` = 'otherlevel') AND (lower(`other_level`) > IN ('accession'))))) LIMIT 1 > I, [2021-03-03T12:31:02.407401 #29270]? INFO -- : (0.007306s) > SELECT * FROM `instance_do_link_rlshp` WHERE (`instance_id` IN > (238583)) > I, [2021-03-03T12:31:02.409280 #29270]? INFO -- : (0.005184s) > SELECT * FROM `note` WHERE (`lang_material_id` IN (1059, 2127)) > I, [2021-03-03T12:31:02.409613 #29270]? INFO -- : (0.002386s) > SELECT * FROM `top_container_link_rlshp` WHERE (`top_container_id` > = 9074) > I, [2021-03-03T12:31:02.410056 #29270]? INFO -- : (0.000203s) > SELECT * FROM `subnote_metadata` WHERE (`note_id` IN (205950)) > I, [2021-03-03T12:31:02.410913 #29270]? INFO -- : (0.012668s) > SELECT * FROM `note` WHERE (`lang_material_id` IN (1140, 2095)) > RecordNotFound: /repositories/4/resources/1260 > > > Working my way up from the error, this query is returning 0 rows: > > ?SELECT * FROM `instance_do_link_rlshp` WHERE (`instance_id` IN > (238583)) > > > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 3/3/21 10:54 AM, Mark Cyzyk wrote: >> >> Thanks! >> >> No FATAL or ERROR now.? But there is this: >> >> INFO: [collection1] webapp= path=/select >> params={df=fullrecord&csv.escape=\&start=0&fq=-exclude_by_default:true&fq=publish:true&fq=types:pui&rows=1&bq=primary_type:resource^100+primary_type:accession^100+primary_type:subject^50+primary_type:agent_person^50+primary_type:agent_corporate_entity^30+primary_type:agent_family^30+&q=(uri:("\/repositories\/4\/resources\/1260"))&qf=title^25+four_part_id^50+fullrecord&pf=four_part_id^50&csv.header=true&csv.encapsulator="&wt=json&facet=true} >> hits=0 status=0 QTime=1 >> RecordNotFound: /repositories/4/resources/1260 >> >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> On 3/3/21 10:30 AM, Blake Carver wrote: >>> Those MySQL errors look like the ones already reported and are >>> probably not causing any problems. >>> >>> https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9 >>> >>> >>> Turn the mysql error logging thing off and set the other loglevel >>> errors to debug and look for any FATAL or ERROR in the logs. >>> ------------------------------------------------------------------------ >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >>> on behalf >>> of Mark Cyzyk >>> *Sent:* Wednesday, March 3, 2021 10:20 AM >>> *To:* Rachel Aileen Searcy ; Archivesspace >>> Users Group >>> *Subject:* Re: [Archivesspace_Users_Group] Containers not being >>> associated with their resources >>> >>> More: >>> >>> In our development environment, I configured full error logging.? I >>> then ran one of our queries that is failing, stopped ASpace, then >>> began scrutiny of archivesspace.out. >>> >>> Here are my disturbing findings: >>> >>> E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_associative' >>> doesn't exist: DESCRIBE `agent_relationship_associative` >>> E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_associative' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_associative` LIMIT 1 >>> E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_associative' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_associative` LIMIT 1 >>> E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_earlierlater' >>> doesn't exist: DESCRIBE `agent_relationship_earlierlater` >>> E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_earlierlater' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_earlierlater` LIMIT 1 >>> E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_earlierlater' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_earlierlater` LIMIT 1 >>> E, [2021-03-03T09:47:30.000084 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_parentchild' >>> doesn't exist: DESCRIBE `agent_relationship_parentchild` >>> E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_parentchild' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_parentchild` LIMIT 1 >>> E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_parentchild' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_parentchild` LIMIT 1 >>> E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' >>> doesn't exist: DESCRIBE `agent_relationship_subordinatesuperior` >>> E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_subordinatesuperior` LIMIT 1 >>> E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_subordinatesuperior` LIMIT 1 >>> >>> >>> >>> E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.container_location' doesn't >>> exist: DESCRIBE `container_location` >>> E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.container_location' doesn't >>> exist: SELECT * FROM `container_location` LIMIT 1 >>> E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.container_location' doesn't >>> exist: SELECT * FROM `container_location` LIMIT 1 >>> >>> >>> >>> E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_bibliography' doesn't >>> exist: DESCRIBE `note_bibliography` >>> E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_bibliography' doesn't >>> exist: SELECT * FROM `note_bibliography` LIMIT 1 >>> E, [2021-03-03T09:47:30.606147 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_bibliography' doesn't >>> exist: SELECT * FROM `note_bibliography` LIMIT 1 >>> E, [2021-03-03T09:47:30.635130 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_digital_object' doesn't >>> exist: DESCRIBE `note_digital_object` >>> E, [2021-03-03T09:47:30.638129 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_digital_object' doesn't >>> exist: SELECT * FROM `note_digital_object` LIMIT 1 >>> E, [2021-03-03T09:47:30.645140 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_digital_object' doesn't >>> exist: SELECT * FROM `note_digital_object` LIMIT 1 >>> E, [2021-03-03T09:47:30.651197 #27625] ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table 'archivesspaceDevelopment.note_index' doesn't exist: >>> DESCRIBE `note_index`E, [2021-03-03T09:47:29.960346 #27625] >>> ERROR -- : >>> Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: >>> Table >>> 'archivesspaceDevelopment.agent_relationship_associative' >>> doesn't exist: SELECT * FROM >>> `agent_relationship_associative` LIMIT 1 >>> >>> >>> >>> I took a look directly in the database and these tables are indeed >>> missing. >>> >>> At this point, I am stumped.? I don't understand why, with these >>> tables missing, one of our three Repositories would be working just >>> fine -- the other two, not so much.? How could whole tables get >>> deleted from our ASpace?? I'm guessing this happened a couple weeks ago. >>> >>> Any advice greatly appreciated, >>> >>> Mark >>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>> Mark Cyzyk, M.A., M.L.S. >>> Library Applications Group >>> The Sheridan Libraries >>> The Johns Hopkins University >>> mcyzyk at jhu.edu >>> >>> Verba volant, scripta manent. >>> On 3/1/21 5:18 PM, Mark Cyzyk wrote: >>>> >>>> Thanks, Rachel! >>>> >>>> I've now completely reindexed everything (a "hard reindex") and >>>> still no joy. >>>> >>>> I am noticing there is no "location.dat" file in our >>>> /indexer_pui_state/: >>>> >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 3_archival_object.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 3_classification.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 3_classification_term.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 3_digital_object_component.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 3_digital_object.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 3_resource.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 4_archival_object.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 4_classification.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 4_classification_term.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 4_digital_object_component.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 4_digital_object.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 4_resource.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 5_archival_object.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 5_classification.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 5_classification_term.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 5_digital_object_component.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 5_digital_object.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> 5_resource.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> _deletes_deletes.dat >>>> -rw-r--r--. 1 archivesspace archivesspace?? 11 Mar? 1 17:13 >>>> repositories_repositories.dat >>>> >>>> Should there be? >>>> >>>> Our two problem repositories here are 4 and 5.? The Staff interface >>>> reports "0" Resources for both.? Yet when I run the Resources List >>>> Report I do indeed get back a report with Resources.? Puzzling. >>>> >>>> It's like something in the backend DB has become disconnected, but >>>> just for these two repositories.? Not sure how. >>>> >>>> If anyone has any suggestions, I would greatly appreciate hearing them! >>>> >>>> Mark >>>> >>>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>>> Mark Cyzyk, M.A., M.L.S. >>>> Library Applications Group >>>> The Sheridan Libraries >>>> The Johns Hopkins University >>>> mcyzyk at jhu.edu >>>> >>>> Verba volant, scripta manent. >>>> On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote: >>>>> Hi Mark >>>>> >>>>> We ran into a similar issue recently, where newly created >>>>> containers were not being properly associated with the resource >>>>> record, and updates to locations or barcodes were not showing up >>>>> in searches or the Manage Top Containers view. We looked at the >>>>> timestamp files for the indexer, and noticed that there was no >>>>> location.dat file. We performed a soft re-index >>>>> , >>>>> after which our containers, barcodes, and locations resumed >>>>> behaving as expected. We also have recurring monthly system >>>>> restarts (which will now include a soft re-index going forward) >>>>> built into our schedule, which seems to help with maintaining >>>>> overall performance. >>>>> >>>>> I'm not sure if this is exactly what you're experiencing, but I >>>>> hope it's helpful. Take care, >>>>> Rachel >>>>> >>>>> On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk >>>> > wrote: >>>>> >>>>> >>>>> Dear ASpace list, >>>>> >>>>> ?From one of our Archivists: >>>>> >>>>> > When I create a new container, either manually or by >>>>> spreadsheet >>>>> > ingest, the container appears properly in the Instance field >>>>> of the >>>>> > record. From the resource, I can open the container record >>>>> and it >>>>> > appears to be associated with the resource correctly. >>>>> However, in the >>>>> > container management module, when I search for all containers >>>>> > associated with the collection, the recently created >>>>> container is not >>>>> > listed. If I search for the new container's barcode, the >>>>> container >>>>> > appears in the search results but with no associated >>>>> resource. I can >>>>> > also locate the new containers by searching for unassociated >>>>> containers. >>>>> >>>>> It seems like some linkage is not happening here. >>>>> >>>>> More, this is only happening in his Repository, not our other, >>>>> larger >>>>> Repository. >>>>> >>>>> Has anyone else run into this? >>>>> >>>>> Mark >>>>> >>>>> -- >>>>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>>>> Mark Cyzyk, M.A., M.L.S. >>>>> Library Applications Group >>>>> The Sheridan Libraries >>>>> The Johns Hopkins University >>>>> mcyzyk at jhu.edu >>>>> >>>>> Verba volant, scripta manent. >>>>> >>>>> _______________________________________________ >>>>> 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e= >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Rachel Searcy >>>>> Accessioning Archivist, Archival Collections Management >>>>> New York University Libraries >>>>> 212.998.2539?| rachel.searcy at nyu.edu >>>>> My pronouns are she/her/hers >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: aspace1.png Type: image/png Size: 113098 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: aspace2.png Type: image/png Size: 141304 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: aspace3.png Type: image/png Size: 750306 bytes Desc: not available URL: From cory_nimer at byu.edu Thu Mar 4 15:02:25 2021 From: cory_nimer at byu.edu (Cory Nimer) Date: Thu, 4 Mar 2021 20:02:25 +0000 Subject: [Archivesspace_Users_Group] Request for input on visibility of digital content Message-ID: Colleagues, Working with representatives from Yale University and the Smithsonian Institution, we have been working to develop a draft specification for improving the visibility of linked digital content in the ArchivesSpace staff interface and public front-end. This has been added to JIRA as ANW-1209 (https://archivesspace.atlassian.net/browse/ANW-1209), and the specification is available at https://docs.google.com/document/d/1-fi-1jpE7GqWc0zWxWsRO9zgRmR1vFFygp6jGnKh23k/edit?usp=sharing. We are very interested in getting feedback from the community about recommended features. The specification document linked above is open for comments, or notes may be added to the JIRA ticket. We would ask that interested parties submit their comments by March 19, 2021. Sincerely, Cory Nimer University Archivist Brigham Young University 801-422-6091 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasmine.soliman at nyu.edu Sun Mar 7 02:22:36 2021 From: jasmine.soliman at nyu.edu (Jasmine Soliman) Date: Sun, 7 Mar 2021 11:22:36 +0400 Subject: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts in AS title field Message-ID: Hello, I'd like to connect with anyone who is currently using, or experimenting with, Arabic or r-t-l script in the title field of AS. We've had mixed results with punctuation/typographical symbols when trying to include both English and Arabic in the title, so I'd like to connect with anyone working on this. Best regards, Jasmine jasmine.soliman at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdb3 at nyu.edu Mon Mar 8 00:41:08 2021 From: bdb3 at nyu.edu (Bradley Bauer) Date: Mon, 8 Mar 2021 00:41:08 -0500 Subject: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts in AS title field In-Reply-To: References: Message-ID: Hello all, I am interested in this as well, as I have wanted to enter Arabic titles of documents or printed items (such as ephemera or printed material) in their own script, and not just as transliterated text, where possible. Over the months, I have experienced a couple of things when doing so, either in the title field, or in notes. On one level, having both the Arabic and Latin script in the same field won't work, left-to-right and right-to-left texts don't share fields very well. That led me to start using the "notes" field at the file level, so I could put an alternate form of the title below, and see whether it displays. I tried this initially using English in the title field, and Arabic in the note (although one could do the reverse as well). The first time I tried that, when I created a preview copy, it gave me just hash-tag symbols instead of Arabic text. Recently when I tried again, I got Arabic letters, but separated, and only in their initial form, not the medial or final forms of the letters (using the correct form is critical in Arabic text, which has three forms based on the placement of a given letter within a word). So the display in Arabic would read something like this: A-R-A-B-I-C_T-E-X-T. If there are some well-proven work-arounds for that, it would be really helpful to know. Best regards, Brad Bauer NYU Abu Dhabi Library On Sun, Mar 7, 2021 at 2:23 AM Jasmine Soliman wrote: > Hello, > > I'd like to connect with anyone who is currently using, or experimenting > with, Arabic or r-t-l script in the title field of AS. We've had mixed > results with punctuation/typographical symbols when trying to include both > English and Arabic in the title, so I'd like to connect with anyone working > on this. > > Best regards, > Jasmine > jasmine.soliman at nyu.edu > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Brad Bauer Librarian for Archives and Special Collections New York University Abu Dhabi PO Box 129188 Saadiyat Island Abu Dhabi, UAE e-mail: bdb3 at nyu.edu phone: +971 2 628 7335 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Mar 8 08:33:59 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 8 Mar 2021 13:33:59 +0000 Subject: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts in AS title field In-Reply-To: References: , Message-ID: There is a JIRA here about providing better support for right-to-left (RTL) scripts, ideally bi-directional text https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1144 And another about Hebrew characters printed left-to-right in staff-side PDFs https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1195 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bradley Bauer Sent: Monday, March 8, 2021 12:41 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts in AS title field Hello all, I am interested in this as well, as I have wanted to enter Arabic titles of documents or printed items (such as ephemera or printed material) in their own script, and not just as transliterated text, where possible. Over the months, I have experienced a couple of things when doing so, either in the title field, or in notes. On one level, having both the Arabic and Latin script in the same field won't work, left-to-right and right-to-left texts don't share fields very well. That led me to start using the "notes" field at the file level, so I could put an alternate form of the title below, and see whether it displays. I tried this initially using English in the title field, and Arabic in the note (although one could do the reverse as well). The first time I tried that, when I created a preview copy, it gave me just hash-tag symbols instead of Arabic text. Recently when I tried again, I got Arabic letters, but separated, and only in their initial form, not the medial or final forms of the letters (using the correct form is critical in Arabic text, which has three forms based on the placement of a given letter within a word). So the display in Arabic would read something like this: A-R-A-B-I-C_T-E-X-T. If there are some well-proven work-arounds for that, it would be really helpful to know. Best regards, Brad Bauer NYU Abu Dhabi Library On Sun, Mar 7, 2021 at 2:23 AM Jasmine Soliman > wrote: Hello, I'd like to connect with anyone who is currently using, or experimenting with, Arabic or r-t-l script in the title field of AS. We've had mixed results with punctuation/typographical symbols when trying to include both English and Arabic in the title, so I'd like to connect with anyone working on this. Best regards, Jasmine jasmine.soliman at nyu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Brad Bauer Librarian for Archives and Special Collections New York University Abu Dhabi PO Box 129188 Saadiyat Island Abu Dhabi, UAE e-mail: bdb3 at nyu.edu phone: +971 2 628 7335 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdb3 at nyu.edu Mon Mar 8 08:40:53 2021 From: bdb3 at nyu.edu (Bradley Bauer) Date: Mon, 8 Mar 2021 17:40:53 +0400 Subject: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts in AS title field In-Reply-To: References: Message-ID: Thanks very much, Blake. So at this point, should we just sit tight, knowing that the issue is under review? Best, Brad On Mon, Mar 8, 2021 at 5:34 PM Blake Carver wrote: > There is a JIRA here about providing better support for right-to-left > (RTL) scripts, ideally bi-directional text > > > https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1144 > > And another about Hebrew characters printed left-to-right in staff-side > PDFs > > > https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1195 > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Bradley Bauer > *Sent:* Monday, March 8, 2021 12:41 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Using Arabic or right-to-left > scripts in AS title field > > Hello all, > > I am interested in this as well, as I have wanted to enter Arabic titles > of documents or printed items (such as ephemera or printed material) in > their own script, and not just as transliterated text, where possible. > > Over the months, I have experienced a couple of things when doing so, > either in the title field, or in notes. > > On one level, having both the Arabic and Latin script in the same field > won't work, left-to-right and right-to-left texts don't share fields very > well. That led me to start using the "notes" field at the file level, so I > could put an alternate form of the title below, and see whether it > displays. I tried this initially using English in the title field, and > Arabic in the note (although one could do the reverse as well). The first > time I tried that, when I created a preview copy, it gave me just hash-tag > symbols instead of Arabic text. Recently when I tried again, I got Arabic > letters, but separated, and only in their initial form, not the medial or > final forms of the letters (using the correct form is critical in Arabic > text, which has three forms based on the placement of a given letter within > a word). So the display in Arabic would read something like this: > A-R-A-B-I-C_T-E-X-T. > > If there are some well-proven work-arounds for that, it would be really > helpful to know. > > Best regards, > > Brad Bauer > NYU Abu Dhabi Library > > > On Sun, Mar 7, 2021 at 2:23 AM Jasmine Soliman > wrote: > > Hello, > > I'd like to connect with anyone who is currently using, or experimenting > with, Arabic or r-t-l script in the title field of AS. We've had mixed > results with punctuation/typographical symbols when trying to include both > English and Arabic in the title, so I'd like to connect with anyone working > on this. > > Best regards, > Jasmine > jasmine.soliman at nyu.edu > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > -- > Brad Bauer > Librarian for Archives and Special Collections > New York University Abu Dhabi > PO Box 129188 > Saadiyat Island > Abu Dhabi, UAE > e-mail: bdb3 at nyu.edu > phone: +971 2 628 7335 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Brad Bauer Librarian for Archives and Special Collections New York University Abu Dhabi PO Box 129188 Saadiyat Island Abu Dhabi, UAE e-mail: bdb3 at nyu.edu phone: +971 2 628 7335 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Mar 8 09:46:31 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 8 Mar 2021 14:46:31 +0000 Subject: [Archivesspace_Users_Group] Reminder - Webinar this Wednesday: ArchivesSpace Member Match Program Informational Webinar Message-ID: <4CD4121F-9BAA-496F-BBA0-6C559E602EF8@lyrasis.org> ArchivesSpace is pleased to announce the ArchivesSpace Member Match program. The Member Match program is a new initiative to engage the ArchivesSpace membership community in peer-to-peer support between ArchivesSpace members. For one, year-long term, Member Match participants will be matched with a member with whom they can receive and offer professional insight, advice, and comradery. The program will also offer participants the opportunity to engage in exclusive events and enlightening discussions about ArchivesSpace and its active user community. In this webinar, members of the ArchivesSpace Member Engagement sub-team will discuss the program and answer questions from potential participants and others interested in the program. More information about the ArchivesSpace Member Match program is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program. A recording of this webinar will be made available on the ArchivesSpace YouTube channel. When: March 10, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_ZqjF2XKXTaqBFQbeITClHA In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. Who should attend: Anyone interested in the ArchivesSpace Member Match program or in becoming more involved in the ArchivesSpace Member community. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From Scott.Renton at ed.ac.uk Mon Mar 8 10:39:53 2021 From: Scott.Renton at ed.ac.uk (RENTON Scott) Date: Mon, 8 Mar 2021 15:39:53 +0000 Subject: [Archivesspace_Users_Group] Line Breaks (Windows/UNIX) Message-ID: Hi folks, Sorry to have two tickets in at once. I tried this one out on the Google Group- thought I'd hit paydirt, but then discovered the advice was helpful but didn't solve the issue. We're just trying to get our heads round line breaks assignation. We have an archivist who is cataloguing content, and we notice through the API that they are being recorded with Windows (CR-LF) line endings. "subnotes": [ { "jsonmodel_type": "note_text", "content": "Recorded by E. Sinclair on Vatersay in 1962, (eg. SA1962.05)\r\n\r\nRecorded by James Ross on Vatersay in 1956, (eg.SA1956.069.1, SA1956.087)\r\n\r\nThis lady is great (SA1960.124 proverbs)! JB 9/6/09\r\n\r\nThere is a duplicate 5810 - use this one. EmM 9/6/09\r\n\r\nbiog info on SA1958.157 track 3. \"Brief history of contributor.\r\n\r\nNan MacKinnon was born in Kentangaval in 1903, and moved to Vatersay at age four. She spent several years working on the mainland, then came home and worked at the herring. She learned most of her songs when she came home, from her mother.\" more detail on tape, mentions other place names.", "publish": false } It appears that these line breaks do not appear in 'View' mode in the frontend as being respected, but while we can see them in 'Edit' mode, the cataloguers do need to see the line breaks in 'View' mode. If we were seeing UNIX LF endings (\n), it does seem to work. We thought it was just that the users had been cutting and pasting from a Word Doc, and if we changed manually in the interface they'd be fixed, but apparently not. Even copying in the content in the attached file- which I've converted to UNIX file endings results in Windows ones. Is it possible there's a hidden character I'm not converting that's governing all of this? Cheers Scott ========== Scott Renton Digital Library Development & Systems Floor F East Argyle House 515219 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th' ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Wed Mar 10 21:07:35 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Wed, 10 Mar 2021 21:07:35 -0500 Subject: [Archivesspace_Users_Group] Indexing and search issues Message-ID: I'm very new to ArchivesSpace and so my issues may be early configuration problems. But I'm hoping some out there can assist. We are moving from hosted to local, so I have a large database full of data that I'm working with. Indexing Right now, I'm running into two primary problems: - Twice now, I've hit issues where the indexing fails due to the Java heap space being exhausted. Do others run into this? What do others use for Java settings? - I've broken out my PUI indexing log into a separate log and see FATAL errors in the log: ------ I, [2021-03-10T15:32:03.747156 #2919] INFO -- : [1b34df32-d3b7-49c3-b205-01a59daf03e5] Started GET "/system_api.php" for 206.189.134.38 at 2021-03-10 15:32:03 -0500 F, [2021-03-10T15:32:03.881297 #2919] FATAL -- : [1b34df32-d3b7-49c3-b205-01a59daf03e5] F, [2021-03-10T15:32:03.881658 #2919] FATAL -- : [1b34df32-d3b7-49c3-b205-01a59daf03e5] ActionController::RoutingErro r (No route matches [GET] "/system_api.php"): F, [2021-03-10T15:32:03.881866 #2919] FATAL -- : [1b34df32-d3b7-49c3-b205-01a59daf03e5] F, [2021-03-10T15:32:03.882085 #2919] FATAL -- : [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) lib/acti on_dispatch/middleware/debug_exceptions.rb:65:in `call' [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) lib/action_dispatch/middleware/show_exceptions.rb:33:in ` call' ------ Is this something to be concerned about? Why is it showing up in the PUI log? Search issues - Supposedly, I did get one round of indexing completed without a heap error. But the resulting searches yielded numbers which were incorrect compared to our hosted version. This is why I've been trying reindexing. Is it usual to have indexing *look* like it is complete but really be incomplete? - When I do a search, the response is really slow. I've got nginx set up as a proxy in front of ArchivesSpace and it is showing that the slowness is in ArchivesSpace itself somewhere. I don't see anything in the logs to show what is taking so long. Where should I be checking for issues? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Mar 11 07:31:06 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 11 Mar 2021 12:31:06 +0000 Subject: [Archivesspace_Users_Group] Indexing and search issues In-Reply-To: References: Message-ID: You can allocate more memory to ArchivesSpace by setting the ASPACE_JAVA_XMX environment variable it runs under. Setting that to "-Xmx4g" should be sufficient. Those FATAL lines in the log snippet are caused by a bot probing for known vulnerabilities in common web platforms and applications, hoping to find a web site running an out-of-date copy (of Drupal in this case) which it can exploit. It has nothing to do with ArchivesSpace, which has no PHP code. It is merely logging that it doesn't know what to do with that request. How did you know your one successful re-indexing completed? There are two indexers, Staff and PUI, with the latter usually taking much longer to finish. So if the PUI indexer fails after the staff indexer finishes, you will see more records in the staff interface than the public interface, even if they're all set to be public. Also both indexers log messages that could be interpreted as meaning they've finished, but they then run additional indexing to build trees, to enable navigation within collections to work. A finally they instruct Solr to commit changes, which can be slow depending on the performance of your storage. You could try doubling AppConfig[:indexer_solr_timeout_seconds] to allow more time for each operation. Or it could've re-indexed one repository but failed on the next. And it is possible for entire repositories to be set as non-public, which could be another explanation for fewer records. Are you running an external Solr? If so, is the AppConfig[:solr_url] in config.rb pointing to the correct server? There are many possible reasons for search slowness, including not enough memory. Are there any differences in the speed of doing the same search in the staff and public interfaces? Or between two ways of getting the same results in the PUI. For example, does the link in the header to list all collections (/repositories/resources) return results faster than searching everything then filtering to just collections (/search?q[]=*&op[]=&field[]=keyword&filter_fields[]=primary_type&filter_values[]=resource). There's a fix coming in 3.0.0 for the latter. Andrew. On 11/03/2021 02:07, Tom Hanstra wrote: > I'm very new to ArchivesSpace and so my issues may be early > configuration problems. But I'm hoping some out there can assist. We > are moving from hosted to local, so I have a large database full of > data that I'm working with. > > Indexing > Right now, I'm running into two primary problems: > > - Twice now, I've hit issues where the indexing fails due to the Java > heap space being exhausted. Do others run into this? What do others > use for Java settings? > - I've broken out my PUI indexing log into a separate log and see > FATAL errors in the log: > ------ > I, [2021-03-10T15:32:03.747156 #2919] ?INFO -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] Started GET "/system_api.php" > ?for 206.189.134.38 at 2021-03-10 15:32:03 -0500 > F, [2021-03-10T15:32:03.881297 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] > F, [2021-03-10T15:32:03.881658 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] ActionController::RoutingErro > r (No route matches [GET] "/system_api.php"): > F, [2021-03-10T15:32:03.881866 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] > F, [2021-03-10T15:32:03.882085 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) lib/acti > on_dispatch/middleware/debug_exceptions.rb:65:in `call' > [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) > lib/action_dispatch/middleware/show_exceptions.rb:33:in ` > call' > ------ > Is this something to be concerned about? Why is it showing up in the > PUI log? > > Search issues > - Supposedly, I did get one round of indexing completed without a heap > error. But the resulting searches yielded numbers which were incorrect > compared to our hosted version. This is why I've been trying > reindexing. Is it usual to have indexing *look* like it is complete > but really be incomplete? > - When I do a search, the response is really slow. I've got nginx set > up as a proxy in front of ArchivesSpace and it is showing that the > slowness is in ArchivesSpace itself somewhere. I don't see anything in > the logs to show what is taking so long. Where should I be checking > for issues? > > Thanks, > Tom > > -- > *Tom Hanstra* > /Sr. Systems Administrator/ > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.barrutia-wood at sheffield.ac.uk Thu Mar 11 07:43:00 2021 From: a.barrutia-wood at sheffield.ac.uk (Arantza Barrutia Ezenarro) Date: Thu, 11 Mar 2021 12:43:00 +0000 Subject: [Archivesspace_Users_Group] AS Agent Search Functionality Message-ID: Hi Any users experiencing issues with the agent search functionality? I'm finding that the agent I'm typing in the box is not coming up but instead a list of other agents appear, sometimes even when I use title:* I have to search through several agents and when I browse the agent template I still have to look through several pages, even when I type the entire agent name. I'm surprised that AS is not giving me the agent I'm typing as the first choice and I'm worried that as the agent database increases there is a risk of users starting to duplicate entries because of this. I believe something similar is happening with containers. Has anyone got a solution to this problem? Thanks -- Arantza Barrutia National Fairground and Circus Archive Collections Manager Western Bank Library University of Sheffield Western Bank Sheffield S10 2TN a.barrutia-wood at sheffield.ac.uk 01142227266 *Follow the National Fairground and Circus Archive *.*on Twitter and Facebook * *Follow the University Library on Instagram , Twitter and on Facebook * -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Thu Mar 11 10:32:20 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Thu, 11 Mar 2021 10:32:20 -0500 Subject: [Archivesspace_Users_Group] Indexing and search issues In-Reply-To: References: Message-ID: Thanks, Andrew. Some responses intertwined below, italicized: On Thu, Mar 11, 2021 at 7:31 AM Andrew Morrison < andrew.morrison at bodleian.ox.ac.uk> wrote: > You can allocate more memory to ArchivesSpace by setting the > ASPACE_JAVA_XMX environment variable it runs under. Setting that to > "-Xmx4g" should be sufficient. > *I did bump that and the ASPACE_JAVA_XSS up a bit for this round, which looks like it will finally complete. Just a few more PUI records need to be added. * > Those FATAL lines in the log snippet are caused by a bot probing for known > vulnerabilities in common web platforms and applications, hoping to find a > web site running an out-of-date copy (of Drupal in this case) which it can > exploit. It has nothing to do with ArchivesSpace, which has no PHP code. It > is merely logging that it doesn't know what to do with that request. > *Thanks. I was hoping this was just extraneous. * > How did you know your one successful re-indexing completed? There are two > indexers, Staff and PUI, with the latter usually taking much longer to > finish. So if the PUI indexer fails after the staff indexer finishes, you > will see more records in the staff interface than the public interface, > even if they're all set to be public. Also both indexers log messages that > could be interpreted as meaning they've finished, but they then run > additional indexing to build trees, to enable navigation within collections > to work. A finally they instruct Solr to commit changes, which can be slow > depending on the performance of your storage. You could try doubling > AppConfig[:indexer_solr_timeout_seconds] to allow more time for each > operation. > *At least one set of logs, when I earlier gave the server more resources, showed that the indexing had completed. But, because the second repository was showing nothing, I decided to indexing again. This time around, we do have the second repository found so that, too, indicates that things have gone better. I guess I have to wait for things to complete but there are still some questions outstanding. For instance, one search I did for "football" (something dear to the Notre Dame experience) within the repository which is supposed to be pretty much indexed, showed over 32K results on our hosted site but only 17K locally. That seems wildly off with only a few PUI records to be completed (log shows 736500 of 763368). Could the incomplete index really be that far off?* *I also notice that indexing overall slows down as it gets farther into our records. Is that probably because there is just more to be done with the records that might not have gotten done in earlier attempts while the first records buzz by rapidly because of earlier indexing attempts? Or could it be that resources are taken up early in the processing and no longer available for processing the later records? Is resource tuning just a trial/error prospect? I don't see a lot of information in the documentation.* Or it could've re-indexed one repository but failed on the next. And it is possible for entire repositories to be set as non-public, which could be another explanation for fewer records. Are you running an external Solr? If so, is the AppConfig[:solr_url] in config.rb pointing to the correct server? *I'm running a local Solr as part of the application. Is an external Solr a good idea for a site like ours? I will also do some tweaking with the Solr settings to see if that might help...after I get through at least one complete index. * > There are many possible reasons for search slowness, including not enough > memory. Are there any differences in the speed of doing the same search in > the staff and public interfaces? Or between two ways of getting the same > results in the PUI. For example, does the link in the header to list all > collections (/repositories/resources) return results faster than searching > everything then filtering to just collections > (/search?q[]=*&op[]=&field[]=keyword&filter_fields[]=primary_type&filter_values[]=resource). > There's a fix coming in 3.0.0 for the latter. > *I had not tried comparing staff to public. I will do that (though I first have to get some access to the staff side!). And I'll really not try to do much comparison until we get indexing complete, in case the indexing itself is slowing things down. * *More questions to come, I'm sure. But thanks for your input and ideas of places to look further. Much appreciated.* > Andrew. > > > On 11/03/2021 02:07, Tom Hanstra wrote: > > I'm very new to ArchivesSpace and so my issues may be early configuration > problems. But I'm hoping some out there can assist. We are moving from > hosted to local, so I have a large database full of data that I'm working > with. > > Indexing > Right now, I'm running into two primary problems: > > - Twice now, I've hit issues where the indexing fails due to the Java heap > space being exhausted. Do others run into this? What do others use for Java > settings? > - I've broken out my PUI indexing log into a separate log and see FATAL > errors in the log: > ------ > I, [2021-03-10T15:32:03.747156 #2919] INFO -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] Started GET "/system_api.php" > for 206.189.134.38 at 2021-03-10 15:32:03 -0500 > F, [2021-03-10T15:32:03.881297 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] > F, [2021-03-10T15:32:03.881658 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] ActionController::RoutingErro > r (No route matches [GET] "/system_api.php"): > F, [2021-03-10T15:32:03.881866 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] > F, [2021-03-10T15:32:03.882085 #2919] FATAL -- : > [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) lib/acti > on_dispatch/middleware/debug_exceptions.rb:65:in `call' > [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) > lib/action_dispatch/middleware/show_exceptions.rb:33:in ` > call' > ------ > Is this something to be concerned about? Why is it showing up in the PUI > log? > > Search issues > - Supposedly, I did get one round of indexing completed without a heap > error. But the resulting searches yielded numbers which were incorrect > compared to our hosted version. This is why I've been trying reindexing. Is > it usual to have indexing *look* like it is complete but really be > incomplete? > - When I do a search, the response is really slow. I've got nginx set up > as a proxy in front of ArchivesSpace and it is showing that the slowness is > in ArchivesSpace itself somewhere. I don't see anything in the logs to show > what is taking so long. Where should I be checking for issues? > > Thanks, > Tom > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing listArchivesspace_Users_Group at lyralists.lyrasis.orghttp://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 > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Thu Mar 11 11:09:21 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Thu, 11 Mar 2021 11:09:21 -0500 Subject: [Archivesspace_Users_Group] AS Agent Search Functionality In-Reply-To: References: Message-ID: I think this might be related to the search and browse preferences that were added recently (maybe not that recent, but in one of the last few releases). If you look in the preferences (we set ours in the ?repository preferences?, but you might do it at the global or user level), look for ?Agent Browse Columns?, then look for the Default Sort Column and Default Sort Direction settings. These are what determine the order of the results that appear when you start typing in the agent box. Try setting Default Sort Column to Relevance, and set Default Sort Direction to 'descending', and see if that makes a difference. On Thu, Mar 11, 2021 at 7:43 AM Arantza Barrutia Ezenarro < a.barrutia-wood at sheffield.ac.uk> wrote: > Hi > > Any users experiencing issues with the agent search functionality? > > I'm finding that the agent I'm typing in the box is not coming up but > instead a list of other agents appear, sometimes even when I use title:* I > have to search through several agents and when I browse the agent template > I still have to look through several pages, even when I type the entire > agent name. I'm surprised that AS is not giving me the agent I'm typing as > the first choice and I'm worried that as the agent database increases there > is a risk of users starting to duplicate entries because of this. I believe > something similar is happening with containers. > > Has anyone got a solution to this problem? > > Thanks > > -- > Arantza Barrutia > National Fairground and Circus Archive Collections Manager > Western Bank Library > University of Sheffield > Western Bank > Sheffield > S10 2TN > a.barrutia-wood at sheffield.ac.uk > > 01142227266 > > *Follow the National Fairground and Circus Archive *.*on Twitter > and Facebook > * > > > > *Follow the University Library on Instagram > , Twitter > and on Facebook > * > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Mar 11 13:25:33 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 11 Mar 2021 18:25:33 +0000 Subject: [Archivesspace_Users_Group] Indexing and search issues In-Reply-To: References: Message-ID: <1d4a4ab6-d2f4-43f0-8bab-cc9a32c4a85c@bodleian.ox.ac.uk> //> I also notice that indexing overall slows down as it gets farther into our records.// I haven't observed a slow-down in indexing. At least not noticeably enough to cause me to want to measure it. As I mentioned, there are some latter stages of the indexing process (building trees, committing changes) that can run for a long time without logging anything. But for the main indexing of archival objects, the last 1000 doesn't seem to take longer than the first 1000. /> Is an external Solr a good idea for a site like ours?/ Hard to say. There was a discussion on the performance benefits of running external Solr on here last month: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2021-February/thread.html#8168 And documentation here: https://archivesspace.github.io/tech-docs/provisioning/solr.html Whether it affects indexing speed for large numbers of records I cannot say. We made the decision to use it before all our data was migrated into ArchivesSpace. Andrew. On 11/03/2021 15:32, Tom Hanstra wrote: > Thanks, Andrew. Some responses intertwined below, italicized: > > On Thu, Mar 11, 2021 at 7:31 AM Andrew Morrison > > wrote: > > You can allocate more memory to ArchivesSpace by setting the > ASPACE_JAVA_XMX environment variable it runs under. Setting that > to "-Xmx4g" should be sufficient. > > /I did bump that and the?ASPACE_JAVA_XSS up a?bit for this round, > which looks like it will finally complete. Just a few more PUI records > need to be added. / > > Those FATAL lines in the log snippet are caused by a bot probing > for known vulnerabilities in common web platforms and > applications, hoping to find a web site running an out-of-date > copy (of Drupal in this case) which it can exploit. It has nothing > to do with ArchivesSpace, which has no PHP code. It is merely > logging that it doesn't know what to do with that request. > > /Thanks. I was hoping this was just extraneous. / > > How did you know your one successful re-indexing completed? There > are two indexers, Staff and PUI, with the latter usually taking > much longer to finish. So if the PUI indexer fails after the staff > indexer finishes, you will see more records in the staff interface > than the public interface, even if they're all set to be public. > Also both indexers log messages that could be interpreted as > meaning they've finished, but they then run additional indexing to > build trees, to enable navigation within collections to work. A > finally they instruct Solr to commit changes, which can be slow > depending on the performance of your storage. You could try > doubling AppConfig[:indexer_solr_timeout_seconds] to allow more > time for each operation. > > /At least one set of logs, when I earlier gave the server more > resources, showed that the indexing had completed. But, because the > second repository was showing nothing, I decided to indexing again. > > This time around, we do have the second repository found so that, too, > indicates that things have gone better. I guess I have to wait for > things to complete but there are still some questions outstanding. For > instance, one search I did for "football" (something dear to the Notre > Dame experience) within the repository which is supposed to be pretty > much indexed, showed over 32K results on our hosted site but only 17K > locally. That seems wildly off with only a few PUI records to be > completed (log shows?736500 of 763368). Could the incomplete index > really be that far off?/ > / > / > /I also notice that indexing overall slows down as it gets farther > into our records. Is that probably because there is just more to be > done with the records that might not have gotten done in earlier > attempts while the first records buzz by rapidly because of earlier > indexing attempts?? Or could it be that resources are taken up early > in the processing and no longer available for processing the later > records? Is resource tuning just a trial/error prospect?? I don't see > a lot of information in the documentation./ > > Or it could've re-indexed one repository but failed on the next. And > it is possible for entire repositories to be set as non-public, which > could be another explanation for fewer records. > > Are you running an external Solr? If so, is the AppConfig[:solr_url] > in config.rb pointing to the correct server? > > /I'm running a local Solr as part of the application. Is an external > Solr a good idea for a site like ours? I will also do some tweaking > with the Solr settings to see if that might help...after I get through > at least one complete index. / > > There are many possible reasons for search slowness, including not > enough memory. Are there any differences in the speed of doing the > same search in the staff and public interfaces? Or between two > ways of getting the same results in the PUI. For example, does the > link in the header to list all collections > (/repositories/resources) return results faster than searching > everything then filtering to just collections > (/search?q[]=*&op[]=&field[]=keyword&filter_fields[]=primary_type&filter_values[]=resource). > There's a fix coming in 3.0.0 for the latter. > > /I had not tried comparing staff to public. I will do that (though I > first have to get some access to the staff side!). And I'll really not > try to do much comparison until we get indexing complete, in case the > indexing itself is slowing things down. / > / > / > /More questions to come, I'm sure. But thanks for your input and ideas > of places to look further. Much appreciated./ > > Andrew. > > > On 11/03/2021 02:07, Tom Hanstra wrote: >> I'm very new to ArchivesSpace and so my issues may be early >> configuration problems. But I'm hoping some out there can assist. >> We are moving from hosted to local, so I have a large database >> full of data that I'm working with. >> >> Indexing >> Right now, I'm running into two primary problems: >> >> - Twice now, I've hit issues where the indexing fails due to the >> Java heap space being exhausted. Do others run into this? What do >> others use for Java settings? >> - I've broken out my PUI indexing log into a separate log and see >> FATAL errors in the log: >> ------ >> I, [2021-03-10T15:32:03.747156 #2919] ?INFO -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] Started GET "/system_api.php" >> ?for 206.189.134.38 at 2021-03-10 15:32:03 -0500 >> F, [2021-03-10T15:32:03.881297 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] >> F, [2021-03-10T15:32:03.881658 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] ActionController::RoutingErro >> r (No route matches [GET] "/system_api.php"): >> F, [2021-03-10T15:32:03.881866 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] >> F, [2021-03-10T15:32:03.882085 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) lib/acti >> on_dispatch/middleware/debug_exceptions.rb:65:in `call' >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) >> lib/action_dispatch/middleware/show_exceptions.rb:33:in ` >> call' >> ------ >> Is this something to be concerned about? Why is it showing up in >> the PUI log? >> >> Search issues >> - Supposedly, I did get one round of indexing completed without a >> heap error. But the resulting searches yielded numbers which were >> incorrect compared to our hosted version. This is why I've been >> trying reindexing. Is it usual to have indexing *look* like it is >> complete but really be incomplete? >> - When I do a search, the response is really slow. I've got nginx >> set up as a proxy in front of ArchivesSpace and it is showing >> that the slowness is in ArchivesSpace itself somewhere. I don't >> see anything in the logs to show what is taking so long. Where >> should I be checking for issues? >> >> Thanks, >> Tom >> >> -- >> *Tom Hanstra* >> /Sr. Systems Administrator/ >> hanstra at nd.edu >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > *Tom Hanstra* > /Sr. Systems Administrator/ > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Thu Mar 11 15:53:35 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Thu, 11 Mar 2021 15:53:35 -0500 Subject: [Archivesspace_Users_Group] Indexing and search issues In-Reply-To: <1d4a4ab6-d2f4-43f0-8bab-cc9a32c4a85c@bodleian.ox.ac.uk> References: <1d4a4ab6-d2f4-43f0-8bab-cc9a32c4a85c@bodleian.ox.ac.uk> Message-ID: On Thu, Mar 11, 2021 at 1:25 PM Andrew Morrison < andrew.morrison at bodleian.ox.ac.uk> wrote: > *> I also notice that indexing overall slows down as it gets farther into > our records.* > > I haven't observed a slow-down in indexing. At least not noticeably enough > to cause me to want to measure it. As I mentioned, there are some latter > stages of the indexing process (building trees, committing changes) that > can run for a long time without logging anything. But for the main indexing > of archival objects, the last 1000 doesn't seem to take longer than the > first 1000. > *I really only have one set of data to work from, but I've been tracking times for PUI indexing especially. During the first hour, it was able to complete193300 records. I'm assuming it was able to do that because it was covering ground it had passed before the Java Heap error caused the previous attempt to stop. But looking later in the processing, hour 3 it indexed 41500 records, hour 12 it was down to 22250 records, and now in the last hour (hour 23) it has only completed 950 records. That is why I was asking about the slow down.* > *> Is an external Solr a good idea for a site like ours?* > > Hard to say. There was a discussion on the performance benefits of running > external Solr on here last month: > > > http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2021-February/thread.html#8168 > > And documentation here: > > https://archivesspace.github.io/tech-docs/provisioning/solr.html > Whether it affects indexing speed for large numbers of records I cannot > say. We made the decision to use it before all our data was migrated into > ArchivesSpace. > > *Looks as if separating Solr out is a good idea, based upon feedback. I'll work on that (assuming indexing finally finishes at some point) * > Andrew. > > > On 11/03/2021 15:32, Tom Hanstra wrote: > > Thanks, Andrew. Some responses intertwined below, italicized: > > On Thu, Mar 11, 2021 at 7:31 AM Andrew Morrison < > andrew.morrison at bodleian.ox.ac.uk> wrote: > >> You can allocate more memory to ArchivesSpace by setting the >> ASPACE_JAVA_XMX environment variable it runs under. Setting that to >> "-Xmx4g" should be sufficient. >> > *I did bump that and the ASPACE_JAVA_XSS up a bit for this round, which > looks like it will finally complete. Just a few more PUI records need to be > added. * > >> Those FATAL lines in the log snippet are caused by a bot probing for >> known vulnerabilities in common web platforms and applications, hoping to >> find a web site running an out-of-date copy (of Drupal in this case) which >> it can exploit. It has nothing to do with ArchivesSpace, which has no PHP >> code. It is merely logging that it doesn't know what to do with that >> request. >> > *Thanks. I was hoping this was just extraneous. * > >> How did you know your one successful re-indexing completed? There are two >> indexers, Staff and PUI, with the latter usually taking much longer to >> finish. So if the PUI indexer fails after the staff indexer finishes, you >> will see more records in the staff interface than the public interface, >> even if they're all set to be public. Also both indexers log messages that >> could be interpreted as meaning they've finished, but they then run >> additional indexing to build trees, to enable navigation within collections >> to work. A finally they instruct Solr to commit changes, which can be slow >> depending on the performance of your storage. You could try doubling >> AppConfig[:indexer_solr_timeout_seconds] to allow more time for each >> operation. >> > > > *At least one set of logs, when I earlier gave the server more resources, > showed that the indexing had completed. But, because the second repository > was showing nothing, I decided to indexing again. This time around, we do > have the second repository found so that, too, indicates that things have > gone better. I guess I have to wait for things to complete but there are > still some questions outstanding. For instance, one search I did for > "football" (something dear to the Notre Dame experience) within the > repository which is supposed to be pretty much indexed, showed over 32K > results on our hosted site but only 17K locally. That seems wildly off with > only a few PUI records to be completed (log shows 736500 of 763368). Could > the incomplete index really be that far off?* > > *I also notice that indexing overall slows down as it gets farther into > our records. Is that probably because there is just more to be done with > the records that might not have gotten done in earlier attempts while the > first records buzz by rapidly because of earlier indexing attempts? Or > could it be that resources are taken up early in the processing and no > longer available for processing the later records? Is resource tuning just > a trial/error prospect? I don't see a lot of information in the > documentation.* > > Or it could've re-indexed one repository but failed on the next. And it is > possible for entire repositories to be set as non-public, which could be > another explanation for fewer records. > > Are you running an external Solr? If so, is the AppConfig[:solr_url] in > config.rb pointing to the correct server? > *I'm running a local Solr as part of the application. Is an external Solr > a good idea for a site like ours? I will also do some tweaking with the > Solr settings to see if that might help...after I get through at least one > complete index. * > >> There are many possible reasons for search slowness, including not enough >> memory. Are there any differences in the speed of doing the same search in >> the staff and public interfaces? Or between two ways of getting the same >> results in the PUI. For example, does the link in the header to list all >> collections (/repositories/resources) return results faster than searching >> everything then filtering to just collections >> (/search?q[]=*&op[]=&field[]=keyword&filter_fields[]=primary_type&filter_values[]=resource). >> There's a fix coming in 3.0.0 for the latter. >> > *I had not tried comparing staff to public. I will do that (though I first > have to get some access to the staff side!). And I'll really not try to do > much comparison until we get indexing complete, in case the indexing itself > is slowing things down. * > > *More questions to come, I'm sure. But thanks for your input and ideas of > places to look further. Much appreciated.* > >> Andrew. >> >> >> On 11/03/2021 02:07, Tom Hanstra wrote: >> >> I'm very new to ArchivesSpace and so my issues may be early configuration >> problems. But I'm hoping some out there can assist. We are moving from >> hosted to local, so I have a large database full of data that I'm working >> with. >> >> Indexing >> Right now, I'm running into two primary problems: >> >> - Twice now, I've hit issues where the indexing fails due to the Java >> heap space being exhausted. Do others run into this? What do others use for >> Java settings? >> - I've broken out my PUI indexing log into a separate log and see FATAL >> errors in the log: >> ------ >> I, [2021-03-10T15:32:03.747156 #2919] INFO -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] Started GET "/system_api.php" >> for 206.189.134.38 at 2021-03-10 15:32:03 -0500 >> F, [2021-03-10T15:32:03.881297 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] >> F, [2021-03-10T15:32:03.881658 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] ActionController::RoutingErro >> r (No route matches [GET] "/system_api.php"): >> F, [2021-03-10T15:32:03.881866 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] >> F, [2021-03-10T15:32:03.882085 #2919] FATAL -- : >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) lib/acti >> on_dispatch/middleware/debug_exceptions.rb:65:in `call' >> [1b34df32-d3b7-49c3-b205-01a59daf03e5] actionpack (5.2.4.4) >> lib/action_dispatch/middleware/show_exceptions.rb:33:in ` >> call' >> ------ >> Is this something to be concerned about? Why is it showing up in the PUI >> log? >> >> Search issues >> - Supposedly, I did get one round of indexing completed without a heap >> error. But the resulting searches yielded numbers which were incorrect >> compared to our hosted version. This is why I've been trying reindexing. Is >> it usual to have indexing *look* like it is complete but really be >> incomplete? >> - When I do a search, the response is really slow. I've got nginx set up >> as a proxy in front of ArchivesSpace and it is showing that the slowness is >> in ArchivesSpace itself somewhere. I don't see anything in the logs to show >> what is taking so long. Where should I be checking for issues? >> >> Thanks, >> Tom >> >> -- >> *Tom Hanstra* >> *Sr. Systems Administrator* >> hanstra at nd.edu >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing listArchivesspace_Users_Group at lyralists.lyrasis.orghttp://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 >> > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing listArchivesspace_Users_Group at lyralists.lyrasis.orghttp://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 > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Mar 12 11:25:29 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 12 Mar 2021 16:25:29 +0000 Subject: [Archivesspace_Users_Group] reminder: March 15 is last day to apply for ArchivesSpace Diversity Partnership Message-ID: (Please share widely and with anyone you think may be interested) A reminder that the last day to apply for the ArchivesSpace Diversity Partnership is Monday, March 15. More information about the program is below. Please reach out to us at ArchivesSpaceHome at lyrasis.org if you have any questions. Thanks to those who have applied already! -- The ArchivesSpace Diversity Partnership is a new program that offers support for implementing the ArchivesSpace application to institutions that are themselves or primarily serve communities underrepresented in the ArchivesSpace community. Participating organizations will receive, at no cost to them, ArchivesSpace membership, hosting with a Registered Service Provider, training, and user and technical support for the duration of a three-year term. Eligible organizations include: * academic Minority-Serving Institutions such as Historically Black Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and Tribal Colleges and Universities * non-profit or community archives primarily run by or serving BIPOC (Black, Indigenous, and People of Color) * tribal archives To be eligible for this new program, organizations cannot already be ArchivesSpace members or current hosting clients of any ArchivesSpace provider. This program will launch with a small cohort of institutions on July 1, 2021. The three-year term will conclude on June 30, 2024. More information about the ArchivesSpace Diversity Partnership, including information about how to apply, is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership. We also held an informational webinar outlining the program and the application process last month. The recording is available on our YouTube channel at https://youtu.be/B3SOgG4zThM. The deadline to submit an application for the program is March 15. Members of the planning group are happy to answer questions or discuss potential applicant's situations at any time. Please contact us at ArchivesSpaceHome at lyrasis.org. We really appreciate the interest in the program and look forward to receiving some great applications! Sent on behalf of the Planning Group Jessica Crouch, ArchivesSpace Community Engagement Coordinator Christine Di Bella, ArchivesSpace Program Manager Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory Council Chair Sean Quimby, University of Pennsylvania and ArchivesSpace Governance Board Vice Chair -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Fri Mar 12 14:27:55 2021 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Fri, 12 Mar 2021 19:27:55 +0000 Subject: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? Message-ID: Good afternoon all, I'm forwarding this message that a colleague of mine sent to the Google Group, hoping to catch more bites here. Any advice/info would be appreciated. Thanks! We're using ArchivesSpace 2.7.1 and have been using the local plugin overrides to customize. I've been successful in suppressing items through the config file and relabeling using the localizations, but I can't figure out how to change the order that the links in the nav bar appear in. Anybody know how to do this? I can't seem to find the relevant file. Currently we've got a local copy of plugins\local\public\views\shared\_navigation.html.erb that we are working with, and I see where it looks like it's constructing the nav bar and links, but I'm not sure what the underlying file is that I need to target to change it. My colleague suspects that control of the order of the links in the nav bar exists outside of the local plugins architecture because it's under the config folder filepath (/public/config/initializers/public_new_defaults.rb?), which the documentation on the local plugin says isn't one that LP includes. Thanks, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Henry.Steele at tufts.edu Fri Mar 12 14:38:17 2021 From: Henry.Steele at tufts.edu (Steele, Henry) Date: Fri, 12 Mar 2021 19:38:17 +0000 Subject: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? In-Reply-To: References: Message-ID: I saw this message earlier and meant to reply. The way we have reordered various links, and elements of the content, is through a JS file, which I used jquery for. Here's how I moved the search bar e.g. $("
  • Search:
    • ").insertAfter($(".navbar-nav li:nth-child(2)")); What you would do is put a .js file in /plugins/local/public/assets, with the appropriate jquery to reorder elements. And then place a file in /plugins/local/public/views called layout_head.html.erb with the following line <%= javascript_include_tag "#{@base_url}/assets/.js" %> Incidentally, I also used the same method for our local css From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Corey Schmidt Sent: Friday, March 12, 2021 2:28 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? Good afternoon all, I'm forwarding this message that a colleague of mine sent to the Google Group, hoping to catch more bites here. Any advice/info would be appreciated. Thanks! We're using ArchivesSpace 2.7.1 and have been using the local plugin overrides to customize. I've been successful in suppressing items through the config file and relabeling using the localizations, but I can't figure out how to change the order that the links in the nav bar appear in. Anybody know how to do this? I can't seem to find the relevant file. Currently we've got a local copy of plugins\local\public\views\shared\_navigation.html.erb that we are working with, and I see where it looks like it's constructing the nav bar and links, but I'm not sure what the underlying file is that I need to target to change it. My colleague suspects that control of the order of the links in the nav bar exists outside of the local plugins architecture because it's under the config folder filepath (/public/config/initializers/public_new_defaults.rb?), which the documentation on the local plugin says isn't one that LP includes. Thanks, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Fri Mar 12 15:25:42 2021 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Fri, 12 Mar 2021 20:25:42 +0000 Subject: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? In-Reply-To: References: , Message-ID: Awesome! Thank you for the info! I'll forward it to my colleague. Corey ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steele, Henry Sent: Friday, March 12, 2021 2:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? [EXTERNAL SENDER - PROCEED CAUTIOUSLY] I saw this message earlier and meant to reply. The way we have reordered various links, and elements of the content, is through a JS file, which I used jquery for. Here?s how I moved the search bar e.g. $("
  • Search:
    • ").insertAfter($(".navbar-nav li:nth-child(2)")); What you would do is put a .js file in /plugins/local/public/assets, with the appropriate jquery to reorder elements. And then place a file in /plugins/local/public/views called layout_head.html.erb with the following line <%= javascript_include_tag "#{@base_url}/assets/.js" %> Incidentally, I also used the same method for our local css From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Corey Schmidt Sent: Friday, March 12, 2021 2:28 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? Good afternoon all, I'm forwarding this message that a colleague of mine sent to the Google Group, hoping to catch more bites here. Any advice/info would be appreciated. Thanks! We're using ArchivesSpace 2.7.1 and have been using the local plugin overrides to customize. I've been successful in suppressing items through the config file and relabeling using the localizations, but I can't figure out how to change the order that the links in the nav bar appear in. Anybody know how to do this? I can't seem to find the relevant file. Currently we've got a local copy of plugins\local\public\views\shared\_navigation.html.erb that we are working with, and I see where it looks like it's constructing the nav bar and links, but I'm not sure what the underlying file is that I need to target to change it. My colleague suspects that control of the order of the links in the nav bar exists outside of the local plugins architecture because it's under the config folder filepath (/public/config/initializers/public_new_defaults.rb?), which the documentation on the local plugin says isn't one that LP includes. Thanks, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Fri Mar 12 17:23:00 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Fri, 12 Mar 2021 17:23:00 -0500 Subject: [Archivesspace_Users_Group] Understanding why ArchivesSpace seems to have died Message-ID: I never was able to complete my indexing of PUI and now it looks as if ArchivesSpace has simply stopped working for me. I'm trying to understand what happened. I have tried to break out the various logs, though doing so has not worked as expected. All PUI activity was going to the indexer log and the end of that log shows the staff log only: I, [2021-03-12T16:46:07.137484 #2919] INFO -- : Thread-2868: Staff Indexer [2021-03-12 16:46:07 -0500] Index round complete I, [2021-03-12T16:46:40.315017 #2919] INFO -- : Thread-2868: Staff Indexer [2021-03-12 16:46:40 -0500] Running index round I have to go back farther to see the last PUI update: I, [2021-03-12T15:37:18.971100 #2919] INFO -- : Thread-2932: PUI Indexer [2021-03-12 15:37:18 -0500] ~~~ Indexed 760150 of 763368 archival_object records in repository UNDA I, [2021-03-12T15:41:27.314764 #2919] INFO -- : Thread-2932: PUI Indexer [2021-03-12 15:41:27 -0500] ~~~ Indexed 760200 of 763368 archival_object records in repository UNDA At the end, that index had gone to a crawl, only indexing about 400 records/hour. While the indexer log continued through the 16:46 time stamp, the pui and archivespace.out logs both stop at 16:10. Here is the last thing in the PUI log: I, [2021-03-12T16:10:06.564227 #2919] INFO -- : [06eac683-aff7-4afe-9046-97e5551b94a9] Rendered shared/_header.html.erb (14.3ms) I, [2021-03-12T16:10:06.570258 #2919] INFO -- : [06eac683-aff7-4afe-9046-97e5551b94a9] Rendered shared/_navigation.html.erb (4.6ms) I, [2021-03-12T16:10:06.572299 #2919] INFO -- : [06eac683-aff7-4afe-9046-97e5551b94a9] Rendered shared/_footer.html.erb (0.4ms) I, [2021-03-12T16:10:06.573882 #2919] INFO -- : [06eac683-aff7-4afe-9046-97e5551b94a9] Completed 404 Not Found in 2930ms (Views: 79.4ms) and in the archivesspace.out log: INFO: [collection1] webapp= path=/update params={} {add=[/repositories/2/archival_objects/1484673#pui, /repositories/2/archival_objects/1484674#pui, /repositories/2/archival_objects/1484675#pui, /repositories/2/archival_objects/1484676#pui, /repositories/2/archival_objects/1484677#pui, /repositories/2/archival_objects/1484678#pui, /repositories/2/archival_objects/1484679#pui, /repositories/2/archival_objects/1484680#pui, /repositories/2/archival_objects/1484681#pui, /repositories/2/archival_objects/1484682#pui, ... (50 adds)]} 0 48 Mar 12, 2021 3:42:27 PM org.apache.solr.update.DirectUpdateHandler2 commit INFO: start commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false} Mar 12, 2021 3:42:27 PM org.apache.solr.core.SolrDeletionPolicy onCommit INFO: SolrDeletionPolicy.onCommit: commits: num=2 commit{dir=NRTCachingDirectory(MMapDirectory@/home/app/archivesspace/data/solr_index/index lockFactory=NativeFSLockFactory@/home/app/archivesspace/data/solr_index/index; maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_bx5,generation=15449} commit{dir=NRTCachingDirectory(MMapDirectory@/home/app/archivesspace/data/solr_index/index lockFactory=NativeFSLockFactory@/home/app/archivesspace/data/solr_index/index; maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_bx6,generation=15450} Mar 12, 2021 3:42:27 PM org.apache.solr.core.SolrDeletionPolicy updateCommits INFO: newest commit generation = 15450 Mar 12, 2021 3:42:27 PM org.apache.solr.search.SolrIndexSearcher INFO: Opening Searcher at 20bc5398[collection1] realtime Mar 12, 2021 3:42:27 PM org.apache.solr.update.DirectUpdateHandler2 commit INFO: end_commit_flush Mar 12, 2021 4:10:06 PM org.apache.solr.core.SolrCore execute INFO: [collection1] webapp= path=/select params={mm=100%25&q=(uri:("\/repositories\/\-1\/actuator\/\-1"))&csv.escape=\&csv.header=true&start=0&csv.encapsulator="&fq=-exclude_by_default:true&fq=publish:true&fq=types:pui&rows=1&wt=json&facet=true} hits=0 status=0 QTime=140 Neither the Staff nor Public interface are currently responding right now. How can I tell if this fully died and, if it did, why it died? Should I restart? Thanks for any help anyone might have. This is rather frustrating! Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Sun Mar 14 22:59:08 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Sun, 14 Mar 2021 22:59:08 -0400 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Message-ID: I don't seem to be able to win with ArchivesSpace. After having indexing again finally give up because of another Java heap error, I restarted archivesspace again with some different java settings. I believe it actually got through the indexing, at least of the first repository. But tonight, looking at the logs, there is another error that seems to have something to do with, perhaps, daylight savings time? I'm seeing this Java error in the logs, even after a restart: -------- INFO: An exception happened during JRuby-Rack startup Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] Time: 2021-03-14 22:46:48 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 -------- Did something get corrupted in the database? What might be happening to result in this error? How do I fix it? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Sun Mar 14 23:04:25 2021 From: james at hudmol.com (James Bullen) Date: Mon, 15 Mar 2021 14:04:25 +1100 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: References: Message-ID: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> Oh gee, I?ve seen that horror. And, yes, it is caused by records having times in that non-existent hour. From memory the only fix I could find was to delete the offending rows, or update their times. Cheers, James > On Mar 15, 2021, at 1:59 PM, Tom Hanstra wrote: > > I don't seem to be able to win with ArchivesSpace. > > After having indexing again finally give up because of another Java heap error, I restarted archivesspace again with some different java settings. I believe it actually got through the indexing, at least of the first repository. > > But tonight, looking at the logs, there is another error that seems to have something to do with, perhaps, daylight savings time? I'm seeing this Java error in the logs, even after a restart: > > -------- > INFO: An exception happened during JRuby-Rack startup > Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > --- System > jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] > Time: 2021-03-14 22:46:48 -0400 > Server: jetty/8.1.5.v20120716 > jruby.home: uri:classloader://META-INF/jruby.home > > --- Context Init Parameters: > jruby.max.runtimes = 1 > jruby.min.runtimes = 1 > public.root = / > rack.env = production > > --- Backtrace > Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > -------- > > Did something get corrupted in the database? What might be happening to result in this error? > How do I fix it? > > Thanks, > Tom > > -- > Tom Hanstra > Sr. Systems Administrator > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Mon Mar 15 07:03:08 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 15 Mar 2021 11:03:08 +0000 Subject: [Archivesspace_Users_Group] Change order of items on PUI navigation bar using local plug-in override? In-Reply-To: References: Message-ID: The links in the navigation bar are defined an array called /$MAIN_MENU/ which is populated during start-up, using /AppConfig[:pui_hide]/ options to determine which of the standard links to include. You can make adjustments to it in your plug-in's /public/plugin_init.rb/ file (if that doesn't exist yet create it as a blank file.) To add a new link on the end, use this: /Plugins::add_menu_item("path_on_server_or_full_url", "Label")/ To add one at the start use: /Plugins::add_menu_item("//path_on_server_or_full_url//", "Label", 0)/ There is no ready-made method for re-ordering existing links, but you could do it with something like the following, for example to swap the 2nd and 4th links: /ArchivesSpacePublic::Application.config.after_initialize do// //? $MAIN_MENU[1],$MAIN_MENU[3]=$MAIN_MENU[3],$MAIN_MENU[1]/ /end/ Directly modifying a global variable like that would be a bad thing for a third-party plug-in to do. But for your local plug-in, customizing your implementation, it should be OK. Just remember that if you change your config.rb in the future, you might have to modify your plug-in too, otherwise it could break the public user interface. But this method runs on the server, during start-up, so is the most efficient option. Andrew. On 12/03/2021 19:27, Corey Schmidt wrote: > Good afternoon all, > > I'm forwarding this message that a colleague of mine sent to the > Google Group, hoping to catch more bites here. Any advice/info would > be appreciated. Thanks! > > We're using ArchivesSpace 2.7.1 and have been using the local > plugin overrides to customize. I've been successful in suppressing > items through the config file and relabeling using the > localizations, but I can't figure out how to change the order that > the links in the nav bar appear in. Anybody know how to do this? I > can't seem to find the relevant file. Currently we've got a local > copy of plugins\local\public\views\shared\_navigation.html.erb > that we are working with, and I see where it looks like it's > constructing the nav bar and links, but I'm not sure what the > underlying file is that I need to target to change it. > > > My colleague suspects that control of the order of the links in the > nav bar exists outside of the local plugins architecture because it's > under the config folder filepath > (/public/config/initializers/public_new_defaults.rb?), which the > documentation on the local plugin says isn't one that LP includes. > > Thanks, > > Corey > > Corey Schmidt > ArchivesSpace Project Manager > University of Georgia Special Collections Libraries > /Email:/Corey.Schmidt at uga.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Mon Mar 15 07:08:15 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 15 Mar 2021 11:08:15 +0000 Subject: [Archivesspace_Users_Group] Line Breaks (Windows/UNIX) In-Reply-To: References: Message-ID: <0956d496-d566-d12c-afdf-1286d73246d6@bodleian.ox.ac.uk> How have you managed to get the UNIX LF-only line breaks to work in the staff interface view mode? Normally, web browsers don't render them. Have you used CSS? Or are you searching and replacing them with HTML br tags? Andrew. On 08/03/2021 15:39, RENTON Scott wrote: > Hi folks, > > Sorry to have two tickets in at once. I tried this one out on the > Google Group- thought I'd hit paydirt, but then discovered the advice > was helpful but didn't solve the issue. > > We're just trying to get our heads round line breaks assignation. We > have an archivist who is cataloguing content, and we notice through > the API that they are being recorded with Windows (CR-LF) line endings. > > ?"subnotes": [ > ? ? ? ? { > "jsonmodel_type": "note_text", > "content": "Recorded by E. Sinclair on Vatersay in 1962, (eg. > SA1962.05)*\r\n\r\n*Recorded by James Ross on Vatersay in 1956, > (eg.SA1956.069.1, SA1956.087)*\r\n\r\n*This lady is great (SA1960.124 > proverbs)! JB 9/6/09*\r\n\r\n*There is a duplicate 5810 - use this > one. EmM 9/6/09*\r\n\r\n*biog info on SA1958.157 track 3. \"Brief > history of contributor.*\r\n\r\n*Nan MacKinnon was born in Kentangaval > in 1903, and moved to Vatersay at age four. She spent several years > working on the mainland, then came home and worked at the herring. She > learned most of her songs when she came home, from her mother.\" more > detail on tape, mentions other place names.", > "publish": false > ? ? ? ? } > > It appears that these line breaks do not appear in 'View' mode in the > frontend as being respected, but while we can see them in 'Edit' mode, > the cataloguers do need to see the line breaks in 'View' mode. If we > were seeing UNIX LF endings (\n), it does seem to work. > > We thought it was just that the users had been cutting and pasting > from a Word Doc, and if we changed manually in the interface they'd be > fixed, but apparently not. Even copying in the content in the attached > file- which I've converted to UNIX file endings results in Windows > ones. Is it possible there's a hidden character I'm not converting > that's governing all of this? > > Cheers > Scott > > > > ========== > > Scott Renton > > Digital Library Development & Systems > > Floor F East > > Argyle House > > 515219 > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. Is e buidheann > carthannais a th? ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, > ?ireamh cl?raidh SC005336. > > _______________________________________________ > 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 Mon Mar 15 09:03:44 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 15 Mar 2021 13:03:44 +0000 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> References: , <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> Message-ID: https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 You'll want to find the date more like '2021-03-14 02:00%' or would it be 03-13? Whatever the date was this year. Find any date with a time between 2-3am and just change it to any real hour. ArchivesSpace did "something" (probably restarted?) at a bad time on Sunday morning and wrote a time that never happened. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James Bullen Sent: Sunday, March 14, 2021 11:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Oh gee, I?ve seen that horror. And, yes, it is caused by records having times in that non-existent hour. From memory the only fix I could find was to delete the offending rows, or update their times. Cheers, James On Mar 15, 2021, at 1:59 PM, Tom Hanstra > wrote: I don't seem to be able to win with ArchivesSpace. After having indexing again finally give up because of another Java heap error, I restarted archivesspace again with some different java settings. I believe it actually got through the indexing, at least of the first repository. But tonight, looking at the logs, there is another error that seems to have something to do with, perhaps, daylight savings time? I'm seeing this Java error in the logs, even after a restart: -------- INFO: An exception happened during JRuby-Rack startup Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] Time: 2021-03-14 22:46:48 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 -------- Did something get corrupted in the database? What might be happening to result in this error? How do I fix it? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] _______________________________________________ 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 hanstra at nd.edu Mon Mar 15 09:10:19 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Mon, 15 Mar 2021 09:10:19 -0400 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: References: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> Message-ID: Any suggestion on what ArchivesSpace might have changed? I had the server running but indexing was complete. What might it have been changing and in what database table would I look for that change? Alternately, since this is still test data, should I just overlay a backup copy of the database from earlier than the EDT cutover time? I don't know what affect that might have on other portions of ArchivesSpace. Finally, what is the overall fix for this issue. If others have seen it, what can be done to make sure to avoid it in the future? Thanks, Tom On Mon, Mar 15, 2021 at 9:03 AM Blake Carver wrote: > https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 > > You'll want to find the date more like '2021-03-14 02:00%' or would it be 03-13? > Whatever the date was this year. > Find any date with a time between 2-3am and just change it to any real > hour. > ArchivesSpace did "something" (probably restarted?) at a bad time on > Sunday morning and wrote a time that never happened. > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > James Bullen > *Sent:* Sunday, March 14, 2021 11:04 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Java error - > Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > > Oh gee, I?ve seen that horror. And, yes, it is caused by records having > times in that non-existent hour. From memory the only fix I could find was > to delete the offending rows, or update their times. > > > Cheers, > James > > > > On Mar 15, 2021, at 1:59 PM, Tom Hanstra wrote: > > I don't seem to be able to win with ArchivesSpace. > > After having indexing again finally give up because of another Java heap > error, I restarted archivesspace again with some different java settings. I > believe it actually got through the indexing, at least of the first > repository. > > But tonight, looking at the logs, there is another error that seems to > have something to do with, perhaps, daylight savings time? I'm seeing this > Java error in the logs, even after a restart: > > -------- > INFO: An exception happened during JRuby-Rack startup > Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > --- System > jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM > 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] > Time: 2021-03-14 22:46:48 -0400 > Server: jetty/8.1.5.v20120716 > jruby.home: uri:classloader://META-INF/jruby.home > > --- Context Init Parameters: > jruby.max.runtimes = 1 > jruby.min.runtimes = 1 > public.root = / > rack.env = production > > --- Backtrace > Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > -------- > > Did something get corrupted in the database? What might be happening to > result in this error? > How do I fix it? > > Thanks, > Tom > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From schanzme at msu.edu Mon Mar 15 10:12:01 2021 From: schanzme at msu.edu (Schanz, Megan) Date: Mon, 15 Mar 2021 14:12:01 +0000 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: References: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> , Message-ID: I run across this every March for daylight savings. This is what I have in my notes to do each time if the indexer is running. Luckily it seems like I didn't have this scenario this year. java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException: This error will appear in the logs when trying to start ArchivesSpace after daylight savings time. Reference: http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-March/006652.html Basically, the indexer user is being updated in the database with a time that does not exist due to daylight savings time. To verify: SELECT * FROM user WHERE (user_mtime >= '2021-03-14 02:00:00' and user_mtime <= '2021-03-14 03:00:00') OR (system_mtime >= '2021-03-04 02:00:00' and system_mtime <= '2021-03-14 03:00:00'); The record that should come back is the search_indexer user. To resolve: UPDATE user set user_mtime = NOW(), system_mtime=NOW() where username='search_indexer'; ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Monday, March 15, 2021 9:10 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Any suggestion on what ArchivesSpace might have changed? I had the server running but indexing was complete. What might it have been changing and in what database table would I look for that change? Alternately, since this is still test data, should I just overlay a backup copy of the database from earlier than the EDT cutover time? I don't know what affect that might have on other portions of ArchivesSpace. Finally, what is the overall fix for this issue. If others have seen it, what can be done to make sure to avoid it in the future? Thanks, Tom On Mon, Mar 15, 2021 at 9:03 AM Blake Carver > wrote: https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 You'll want to find the date more like '2021-03-14 02:00%' or would it be 03-13? Whatever the date was this year. Find any date with a time between 2-3am and just change it to any real hour. ArchivesSpace did "something" (probably restarted?) at a bad time on Sunday morning and wrote a time that never happened. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of James Bullen > Sent: Sunday, March 14, 2021 11:04 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Oh gee, I?ve seen that horror. And, yes, it is caused by records having times in that non-existent hour. From memory the only fix I could find was to delete the offending rows, or update their times. Cheers, James On Mar 15, 2021, at 1:59 PM, Tom Hanstra > wrote: I don't seem to be able to win with ArchivesSpace. After having indexing again finally give up because of another Java heap error, I restarted archivesspace again with some different java settings. I believe it actually got through the indexing, at least of the first repository. But tonight, looking at the logs, there is another error that seems to have something to do with, perhaps, daylight savings time? I'm seeing this Java error in the logs, even after a restart: -------- INFO: An exception happened during JRuby-Rack startup Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] Time: 2021-03-14 22:46:48 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 -------- Did something get corrupted in the database? What might be happening to result in this error? How do I fix it? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] _______________________________________________ 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 -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Mon Mar 15 10:24:07 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Mon, 15 Mar 2021 10:24:07 -0400 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: References: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> Message-ID: Thanks, Megan. That update did fix things. So, is this not something that can be addressed at the software fix level? Do other sites simply stop indexing or turn something else off when we hit DST in March? Tom On Mon, Mar 15, 2021 at 10:12 AM Schanz, Megan wrote: > I run across this every March for daylight savings. This is what I have in > my notes to do each time if the indexer is running. Luckily it seems like I > didn't have this scenario this year. > > java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> > 3:Java::JavaLang::IllegalArgumentException: > > This error will appear in the logs when trying to start ArchivesSpace > after daylight savings time. Reference: > http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-March/006652.html > > Basically, the indexer user is being updated in the database with a time > that does not exist due to daylight savings time. > > To verify: > > SELECT * FROM user WHERE (user_mtime >= '2021-03-14 02:00:00' and user_mtime <= '2021-03-14 03:00:00') OR (system_mtime >= '2021-03-04 02:00:00' and system_mtime <= '2021-03-14 03:00:00'); > > The record that should come back is the search_indexer user. > > To resolve: > > UPDATE user set user_mtime = NOW(), system_mtime=NOW() where username='search_indexer'; > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom > Hanstra > *Sent:* Monday, March 15, 2021 9:10 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Java error - > Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > Any suggestion on what ArchivesSpace might have changed? I had the server > running but indexing was complete. What might it have been changing and in > what database table would I look for that change? > > Alternately, since this is still test data, should I just overlay a backup > copy of the database from earlier than the EDT cutover time? I don't know > what affect that might have on other portions of ArchivesSpace. > > Finally, what is the overall fix for this issue. If others have seen it, > what can be done to make sure to avoid it in the future? > > Thanks, > Tom > > On Mon, Mar 15, 2021 at 9:03 AM Blake Carver > wrote: > > https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 > > > You'll want to find the date more like '2021-03-14 02:00%' or would it be 03-13? > Whatever the date was this year. > Find any date with a time between 2-3am and just change it to any real > hour. > ArchivesSpace did "something" (probably restarted?) at a bad time on > Sunday morning and wrote a time that never happened. > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > James Bullen > *Sent:* Sunday, March 14, 2021 11:04 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Java error - > Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > > Oh gee, I?ve seen that horror. And, yes, it is caused by records having > times in that non-existent hour. From memory the only fix I could find was > to delete the offending rows, or update their times. > > > Cheers, > James > > > > On Mar 15, 2021, at 1:59 PM, Tom Hanstra wrote: > > I don't seem to be able to win with ArchivesSpace. > > After having indexing again finally give up because of another Java heap > error, I restarted archivesspace again with some different java settings. I > believe it actually got through the indexing, at least of the first > repository. > > But tonight, looking at the logs, there is another error that seems to > have something to do with, perhaps, daylight savings time? I'm seeing this > Java error in the logs, even after a restart: > > -------- > INFO: An exception happened during JRuby-Rack startup > Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > --- System > jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM > 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] > Time: 2021-03-14 22:46:48 -0400 > Server: jetty/8.1.5.v20120716 > jruby.home: uri:classloader://META-INF/jruby.home > > --- Context Init Parameters: > jruby.max.runtimes = 1 > jruby.min.runtimes = 1 > public.root = / > rack.env = production > > --- Backtrace > Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > -------- > > Did something get corrupted in the database? What might be happening to > result in this error? > How do I fix it? > > Thanks, > Tom > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Mon Mar 15 10:33:28 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Mon, 15 Mar 2021 10:33:28 -0400 Subject: [Archivesspace_Users_Group] PUI indexing Message-ID: Is it typical for PUI indexing to run through all records each time ArchivesSpace restarts? Or is my indexing just never fully completed? The staff indexer seems to understand that there are no new records and does not run through everything: I, [2021-03-15T10:25:16.599063 #6928] INFO -- : Thread-2868: Staff Indexer [2021-03-15 10:25:16 -0400] Running index round I, [2021-03-15T10:25:18.785671 #6928] INFO -- : Thread-2868: Staff Indexer [2021-03-15 10:25:18 -0400] Index round complete But the PUI, so far in my experience, restarts from 0 each time. Just trying to understand if this is normal behavior. I don't have anything in the directory: archivesspace/data/indexer_pui_state besides the repositories_repositories.dat. Will there be more files there when PUI indexing really completes? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From schanzme at msu.edu Mon Mar 15 10:36:34 2021 From: schanzme at msu.edu (Schanz, Megan) Date: Mon, 15 Mar 2021 14:36:34 +0000 Subject: [Archivesspace_Users_Group] PUI indexing In-Reply-To: References: Message-ID: The files don't get written to the state directory until indexing has fully completed. So if ArchivesSpace restarts before then, it will try to re-index from the start again. - Megan Megan Schanz Michigan State University Libraries ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Monday, March 15, 2021 10:33 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] PUI indexing Is it typical for PUI indexing to run through all records each time ArchivesSpace restarts? Or is my indexing just never fully completed? The staff indexer seems to understand that there are no new records and does not run through everything: I, [2021-03-15T10:25:16.599063 #6928] INFO -- : Thread-2868: Staff Indexer [2021-03-15 10:25:16 -0400] Running index round I, [2021-03-15T10:25:18.785671 #6928] INFO -- : Thread-2868: Staff Indexer [2021-03-15 10:25:18 -0400] Index round complete But the PUI, so far in my experience, restarts from 0 each time. Just trying to understand if this is normal behavior. I don't have anything in the directory: archivesspace/data/indexer_pui_state besides the repositories_repositories.dat. Will there be more files there when PUI indexing really completes? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Mar 15 11:20:11 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 15 Mar 2021 15:20:11 +0000 Subject: [Archivesspace_Users_Group] Register now for the 2021 ArchivesSpace Online Forum Message-ID: [A picture containing diagram Description automatically generated] There?s still time to register for the 3rd Annual ArchivesSpace Online Forum! Taking place March 29-31, 2021, our online forum will be a three-day event spanning a variety of time zones and ArchivesSpace experience levels. Anyone who uses ArchivesSpace or is interested in ArchivesSpace is welcome to attend. As in years past, this free event will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace. When: Presentations and breakout discussions will be held on March 29-30, 2021, from 4pm-8pm UTC, and all individuals using or interested in ArchivesSpace are welcome to attend some or all of the sessions on these days. Small workshops covering specific elements of the ArchivesSpace application will be offered at different times on March 30-31, 2021. These workshops are currently full. Where: All online via Zoom, with opportunities to join via computer or phone. Who Can Attend: Anyone using or interested in using ArchivesSpace. This is a free event but registration is required. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2146992129/ArchivesSpace+Online+Forum+2021 Registrations for each day of the Forum are separate. You will need to register for each day you are interested in attending to guarantee your spot. Registration for each activity is linked above the session in the agenda. Workshop attendance is limited and workshops are currently full. We anticipate recording many parts of the forum, but for it to be a success we will also need as many live participants as possible. We encourage you to dip in and out of the live program as much as you can. You will no doubt ?meet? a different set of colleagues each time. A special thanks to our Online Forum planning group for the tremendous work they?re doing to plan this forum. We?re looking forward to a great event, with your help! Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing many of you there! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 254329 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29063 bytes Desc: image002.jpg URL: From robinsa1 at newschool.edu Mon Mar 15 16:26:09 2021 From: robinsa1 at newschool.edu (Anna Robinson-Sweet) Date: Mon, 15 Mar 2021 16:26:09 -0400 Subject: [Archivesspace_Users_Group] Plugin for publishing Rights Statements Message-ID: Hello, We just came to the realization that Right Statements are not published to the PUI--despite the existence of a "Publish?" checkbox in the Additional Information section. Searching the listserv I found an exchange from 2019 regarding this issue. Someone mentioned it would be easy to develop a plugin to surface the rights statement on the PUI. I'm wondering if anyone has developed such a plugin in the two years since? All the best, Anna -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [image: THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Mon Mar 15 19:48:57 2021 From: james at hudmol.com (James Bullen) Date: Tue, 16 Mar 2021 10:48:57 +1100 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: References: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> Message-ID: Many thanks Megan for the lead. I just poked around and found a few things out. It turns out to be interesting in at least three bad ways. 1. User records are updated every time they authenticate. This is unnecessary because it is just updating their authentication source, which usually never changes. So this line could be made conditional on the source being different: https://github.com/archivesspace/archivesspace/blob/master/backend/app/model/authentication_manager.rb#L40 2. The search_indexer user is being re-authenticated a lot. This shouldn?t happen because it should be a non-expiring session. I haven?t looked into this one, but I did check the lock_version on the search_inxdexer user on a large-ish AS db I have lying around, that has been in production for less than a year and it is over 100,000. That?s nuts. Actually I just took a quick look and saw this: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/periodic_indexer.rb#L285 The session is reset if there is an error during an indexing round. So that could be the culprit. 3. There is clearly a bug somewhere in the stack, probably in the Sequel layer, because it shouldn?t crash the system just because you have a whacky datetime somewhere. This bug may well have been fixed in a more recent version of that component. Dealing with 1 will likely fix the problem, but 2 and 3 should also be investigated. Cheers, James > On Mar 16, 2021, at 1:24 AM, Tom Hanstra wrote: > > Thanks, Megan. That update did fix things. > > So, is this not something that can be addressed at the software fix level? Do other sites simply stop indexing or turn something else off when we hit DST in March? > > Tom > > On Mon, Mar 15, 2021 at 10:12 AM Schanz, Megan > wrote: > I run across this every March for daylight savings. This is what I have in my notes to do each time if the indexer is running. Luckily it seems like I didn't have this scenario this year. > > java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException: > > This error will appear in the logs when trying to start ArchivesSpace after daylight savings time. Reference:http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-March/006652.html > Basically, the indexer user is being updated in the database with a time that does not exist due to daylight savings time. > > To verify: > > SELECT * FROM user WHERE (user_mtime >= '2021-03-14 02:00:00' and user_mtime <= '2021-03-14 03:00:00') OR (system_mtime >= '2021-03-04 02:00:00' and system_mtime <= '2021-03-14 03:00:00'); > The record that should come back is the search_indexer user. > > To resolve: > > UPDATE user set user_mtime = NOW(), system_mtime=NOW() where username='search_indexer'; > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tom Hanstra > > Sent: Monday, March 15, 2021 9:10 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > Any suggestion on what ArchivesSpace might have changed? I had the server running but indexing was complete. What might it have been changing and in what database table would I look for that change? > > Alternately, since this is still test data, should I just overlay a backup copy of the database from earlier than the EDT cutover time? I don't know what affect that might have on other portions of ArchivesSpace. > > Finally, what is the overall fix for this issue. If others have seen it, what can be done to make sure to avoid it in the future? > > Thanks, > Tom > > On Mon, Mar 15, 2021 at 9:03 AM Blake Carver > wrote: > https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 > > You'll want to find the date more like '2021-03-14 02:00%' or would it be 03-13? Whatever the date was this year. > Find any date with a time between 2-3am and just change it to any real hour. > ArchivesSpace did "something" (probably restarted?) at a bad time on Sunday morning and wrote a time that never happened. > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of James Bullen > > Sent: Sunday, March 14, 2021 11:04 PM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 > > > Oh gee, I?ve seen that horror. And, yes, it is caused by records having times in that non-existent hour. From memory the only fix I could find was to delete the offending rows, or update their times. > > > Cheers, > James > > > >> On Mar 15, 2021, at 1:59 PM, Tom Hanstra > wrote: >> >> I don't seem to be able to win with ArchivesSpace. >> >> After having indexing again finally give up because of another Java heap error, I restarted archivesspace again with some different java settings. I believe it actually got through the indexing, at least of the first repository. >> >> But tonight, looking at the logs, there is another error that seems to have something to do with, perhaps, daylight savings time? I'm seeing this Java error in the logs, even after a restart: >> >> -------- >> INFO: An exception happened during JRuby-Rack startup >> Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 >> --- System >> jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] >> Time: 2021-03-14 22:46:48 -0400 >> Server: jetty/8.1.5.v20120716 >> jruby.home: uri:classloader://META-INF/jruby.home <> >> >> --- Context Init Parameters: >> jruby.max.runtimes = 1 >> jruby.min.runtimes = 1 >> public.root = / >> rack.env = production >> >> --- Backtrace >> Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 >> >> -------- >> >> Did something get corrupted in the database? What might be happening to result in this error? >> How do I fix it? >> >> Thanks, >> Tom >> >> -- >> Tom Hanstra >> Sr. Systems Administrator >> hanstra at nd.edu >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > -- > Tom Hanstra > Sr. Systems Administrator > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > -- > Tom Hanstra > Sr. Systems Administrator > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.hoffman at lyrasis.org Tue Mar 16 08:50:42 2021 From: brian.hoffman at lyrasis.org (Brian Hoffman) Date: Tue, 16 Mar 2021 12:50:42 +0000 Subject: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 In-Reply-To: References: <6E518CD9-EDFB-4785-845A-D8F2979CF7FE@hudmol.com> Message-ID: I created an issue for this in JIRA with references to the information shared by Megan and James. https://archivesspace.atlassian.net/browse/ANW-1229 Brian From: on behalf of James Bullen Reply-To: Archivesspace Users Group Date: Monday, March 15, 2021 at 7:49 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Many thanks Megan for the lead. I just poked around and found a few things out. It turns out to be interesting in at least three bad ways. 1. User records are updated every time they authenticate. This is unnecessary because it is just updating their authentication source, which usually never changes. So this line could be made conditional on the source being different: https://github.com/archivesspace/archivesspace/blob/master/backend/app/model/authentication_manager.rb#L40 2. The search_indexer user is being re-authenticated a lot. This shouldn?t happen because it should be a non-expiring session. I haven?t looked into this one, but I did check the lock_version on the search_inxdexer user on a large-ish AS db I have lying around, that has been in production for less than a year and it is over 100,000. That?s nuts. Actually I just took a quick look and saw this: https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/periodic_indexer.rb#L285 The session is reset if there is an error during an indexing round. So that could be the culprit. 3. There is clearly a bug somewhere in the stack, probably in the Sequel layer, because it shouldn?t crash the system just because you have a whacky datetime somewhere. This bug may well have been fixed in a more recent version of that component. Dealing with 1 will likely fix the problem, but 2 and 3 should also be investigated. Cheers, James On Mar 16, 2021, at 1:24 AM, Tom Hanstra > wrote: Thanks, Megan. That update did fix things. So, is this not something that can be addressed at the software fix level? Do other sites simply stop indexing or turn something else off when we hit DST in March? Tom On Mon, Mar 15, 2021 at 10:12 AM Schanz, Megan > wrote: I run across this every March for daylight savings. This is what I have in my notes to do each time if the indexer is running. Luckily it seems like I didn't have this scenario this year. java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException: This error will appear in the logs when trying to start ArchivesSpace after daylight savings time. Reference: http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-March/006652.html Basically, the indexer user is being updated in the database with a time that does not exist due to daylight savings time. To verify: SELECT * FROM user WHERE (user_mtime >= '2021-03-14 02:00:00' and user_mtime <= '2021-03-14 03:00:00') OR (system_mtime >= '2021-03-04 02:00:00' and system_mtime <= '2021-03-14 03:00:00'); The record that should come back is the search_indexer user. To resolve: UPDATE user set user_mtime = NOW(), system_mtime=NOW() where username='search_indexer'; ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tom Hanstra > Sent: Monday, March 15, 2021 9:10 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Any suggestion on what ArchivesSpace might have changed? I had the server running but indexing was complete. What might it have been changing and in what database table would I look for that change? Alternately, since this is still test data, should I just overlay a backup copy of the database from earlier than the EDT cutover time? I don't know what affect that might have on other portions of ArchivesSpace. Finally, what is the overall fix for this issue. If others have seen it, what can be done to make sure to avoid it in the future? Thanks, Tom On Mon, Mar 15, 2021 at 9:03 AM Blake Carver > wrote: https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 You'll want to find the date more like '2021-03-14 02:00%' or would it be 03-13? Whatever the date was this year. Find any date with a time between 2-3am and just change it to any real hour. ArchivesSpace did "something" (probably restarted?) at a bad time on Sunday morning and wrote a time that never happened. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of James Bullen > Sent: Sunday, March 14, 2021 11:04 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 Oh gee, I?ve seen that horror. And, yes, it is caused by records having times in that non-existent hour. From memory the only fix I could find was to delete the offending rows, or update their times. Cheers, James On Mar 15, 2021, at 1:59 PM, Tom Hanstra > wrote: I don't seem to be able to win with ArchivesSpace. After having indexing again finally give up because of another Java heap error, I restarted archivesspace again with some different java settings. I believe it actually got through the indexing, at least of the first repository. But tonight, looking at the logs, there is another error that seems to have something to do with, perhaps, daylight savings time? I'm seeing this Java error in the logs, even after a restart: -------- INFO: An exception happened during JRuby-Rack startup Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64] Time: 2021-03-14 22:46:48 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 -------- Did something get corrupted in the database? What might be happening to result in this error? How do I fix it? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [Image removed by sender.] _______________________________________________ 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 -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [Image removed by sender.] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [Image removed by sender.] _______________________________________________ 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 christine.dibella at lyrasis.org Tue Mar 16 10:57:13 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 16 Mar 2021 14:57:13 +0000 Subject: [Archivesspace_Users_Group] FW: Introducing the LYRASIS DataCite US Community Message-ID: Forwarded on behalf of our colleague Sheila Rabun at LYRASIS. Please contact Sheila (sheila.rabun at lyrasis.org) if you have questions. ------- Greetings all, We are pleased to announce the official launch of the LYRASIS DataCite US Community, a national consortium/community of practice for non-profit organizations in the US dedicated to creating and maintaining DOIs (Digital Object Identifiers) for special collections, unique cultural heritage materials, research data, and other scholarly content via the DataCite DOI registration agency. This new program provides membership cost sharing, dedicated support, and a shared pathway for organizations to support open research infrastructure by using DOIs to make scholarly content and research materials more FAIR: Findable, Accessible, Interoperable, and Reusable. Please join us for a free informational webinar "Introducing the LYRASIS DataCite US Community" to learn more about the benefits of DOIs, participation, and program details: * When: Thurs. April 22, 12-1pm Pacific/ 1-2pm Mountain/ 2-3pm Central/ 3-4pm Eastern * Registration and details: https://www.lyrasis.org/Content/Pages/Event-Details.aspx?Eid=E0361D0F-F281-EB11-80EF-00155D0A2721 * Note: All registrants will receive a link to the webinar recording. This program is designed to serve any non-profit institution in the US that is not already a DataCite member, and your organization does not need to be a LYRASIS member to participate. Additional information can be found online at https://www.lyrasis.org/programs/Pages/DataCite-US-Community-Membership.aspx. Feel free to contact me directly with any questions: sheila.rabun at lyrasis.org Many thanks, Sheila Sheila Rabun, MA, MLIS [cid:image001.gif at 01D7199F.34670460] https://orcid.org/0000-0002-1196-6279 Program Leader, Persistent Identifier Communities Web: http://orcid-us.org Twitter: https://twitter.com/USconsortium Phone: 1-800-999-8558 x4809 Pronouns: she/her/hers Recognize me: https://rescognito.com/0000-0002-1196-6279 [cid:image002.jpg at 01D7199F.34670460] [cid:image003.png at 01D7199F.34670460] I live, work, and learn on Kalapuya Ilihi, the traditional indigenous homeland of the Kalapuya people. Learn more about the Kalapuya people, their history, and the history of this land. Learn about land acknowledgments and ways to be in solidarity with Native nations beyond land acknowledgments. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1221 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 2350 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 16743 bytes Desc: image003.png URL: From ccauste1 at swarthmore.edu Tue Mar 16 12:00:39 2021 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Tue, 16 Mar 2021 12:00:39 -0400 Subject: [Archivesspace_Users_Group] Past Perfect migration? In-Reply-To: References: Message-ID: I would recommend checking out the work that Lindsey Loeper did at UMBC to convert PastPerfect XML to EAD, presuming you could easily import the EAD into ASpace but I haven't tried it myself. See https://www2.archivists.org/sites/all/files/Module_18_CaseStudy_LindseyLoeper.pdf , https://github.com/UMBC-Library/EAD-XML, etc. On Wed, Mar 3, 2021 at 9:44 AM Novak, Miranda wrote: > Hello, > > > > My institution is brand-new to ArchivesSpace and has been using Past > Perfect for 20+ years. I?m hoping to be directed to documentation to help > me plan how to migrate data from Past Perfect into ArchivesSpace. Has > anyone already done this and could you point me to the documents/videos > that helped you? > > > > Thank you and apologies if this isn?t an appropriate question for this > group! > > > > Sincerely, > > Miranda > > > > Miranda Novak > > Assistant Director of Instructional Technology > > Clemens & Alcuin Libraries, IT Services > > College of Saint Benedict/Saint John?s University > > 320-363-5923 > > mnovak at csbsju.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 > -- Celia Caust-Ellenbogen (she/her/hers ) Friends Historical Library of Swarthmore College ccauste1 at swarthmore.edu Please be aware that Swarthmore College is currently closed to visitors and all but essential staff due to coronavirus precautions. I am primarily working from home and spending only limited time in the office. Email is the best way to reach me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Tue Mar 16 12:04:38 2021 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Tue, 16 Mar 2021 16:04:38 +0000 Subject: [Archivesspace_Users_Group] Past Perfect migration? In-Reply-To: References: Message-ID: If you have questions about importing your data (not XML), I know you can export out of PastPerfect into a CSV excel file. With version 2.8, you can import that directly into ASpace, after you have migrated the data to the import template. Thanks to the work of Bobbi Fox and others, what used to be a plug-in for importing excel spreadsheets, is part of the core code with version 2.8. Good luck with your migration. Best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Celia Caust-Ellenbogen Sent: Tuesday, March 16, 2021 12:01 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Past Perfect migration? I would recommend checking out the work that Lindsey Loeper did at UMBC to convert PastPerfect XML to EAD, presuming you could easily import the EAD into ASpace but I haven't tried it myself. See https://www2.archivists.org/sites/all/files/Module_18_CaseStudy_LindseyLoeper.pdf, https://github.com/UMBC-Library/EAD-XML, etc. On Wed, Mar 3, 2021 at 9:44 AM Novak, Miranda > wrote: Hello, My institution is brand-new to ArchivesSpace and has been using Past Perfect for 20+ years. I'm hoping to be directed to documentation to help me plan how to migrate data from Past Perfect into ArchivesSpace. Has anyone already done this and could you point me to the documents/videos that helped you? Thank you and apologies if this isn't an appropriate question for this group! Sincerely, Miranda Miranda Novak Assistant Director of Instructional Technology Clemens & Alcuin Libraries, IT Services College of Saint Benedict/Saint John's University 320-363-5923 mnovak at csbsju.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 -- Celia Caust-Ellenbogen (she/her/hers) Friends Historical Library of Swarthmore College ccauste1 at swarthmore.edu Please be aware that Swarthmore College is currently closed to visitors and all but essential staff due to coronavirus precautions. I am primarily working from home and spending only limited time in the office. Email is the best way to reach me. CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Mar 16 12:31:51 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 16 Mar 2021 16:31:51 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Implementing the Protocols for Native American Archival Materials at Northern Arizona University Message-ID: <0CFFE2A8-BA6F-46FA-9F3F-306AA60BC3D6@lyrasis.org> Dear ArchivesSpace users, ArchivesSpace will be offering a webinar on Implementing the Protocols for Native American Archival Materials at Northern Arizona University. In this webinar, Sam Meier, Cindy Summers, and Liz Garcia will discuss the ongoing efforts of Northern Arizona University?s Cline Library Special Collections and Archives to implement the Protocols for Native American Archival Materials; their vision for applying the Protocols to archival arrangement and description as well as rearrangement and redescription; logistical, technological, and resource issues with regards to updating legacy archival description in ArchivesSpace; and the design, implementation, and progress to date of the Archival Description Internship developed to help make this work possible. When: April 14, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_THgc9aVTSDK4y0GygvSLeQ This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Background information: In April 2006, Northern Arizona University (NAU) in Flagstaff, Arizona hosted a gathering of Native American and non-Native American cultural heritage professionals who together drafted the Protocols for Native American Archival Materials, a professional best practices document which outlined guidelines for culturally responsive care of Native American archival materials held by non-tribal institutions. NAU?s Cline Library and Special Collections and Archives formally endorsed the Protocols in 2006. Since then, the staff members of Cline Library Special Collections and Archives (SCA) have sought to integrate the guidance put forth by the Protocols into all aspects of their work, including collection development, collections management, and archival arrangement and description. In 2019, SCA?s newly hired Archivist for Discovery, Sam(antha) Meier, began revising the department?s draft Arrangement and Description Policy to address issues common to academic archives and special collections, such as an extensive and growing backlog of unprocessed materials and outdated and inaccurate legacy description. Supported by colleagues at Arizona State University, she began to explore the possibility of using ArchivesSpace to more rapidly gain collection-level control over new acquisitions, update existing legacy finding aids, and transition the department?s EAD finding aids hosted in Arizona Archives Online from EAD 2002 to EAD3. During the COVID-19 pandemic, Meier collaborated with Library Assistant Manager Cindy Summers to begin a holistic review of SCA?s legacy finding aids to prepare for their eventual ingest into ArchivesSpace for revision and correction. Meier and Summers found ways to continue this critical work remotely, as neither were initially working in Cline Library. Cognizant of the need to implement the Protocols at every step in archival processing, including re-description, re-arrangement, and re-processing, in the winter of 2020 Meier and Summers developed a fully remote paid graduate internship, the Archival Description Internship, intended to support an MLIS student at the University of Arizona in Tucson, Arizona. The internship was designed to function as a "pilot project" for the department, allowing Meier and Summers to explore how to apply the Protocols to their legacy finding aids along with intern Liz Garcia. Presenter Information: Elizabeth (Liz) Garcia is an MLIS student and Knowledge River Scholar at the University of Arizona?s School of Information with a concentration in archival studies. In addition to her work as the Archival Description Intern at Cline Library Special Collections and Archives, she is also the Graduate Assistant Archives Specialist at the University of Arizona Libraries Special Collections. Her research interests include archival theory, social justice in libraries and archives, and digital curation. Cindy Summers is an Assistant Manager at Cline Library Special Collections and Archives where she supervises volunteers, student employees, and interns. Cindy works closely with the Archivist for Discovery (Samantha Meier) to oversee collections processing, which has led to the ambitious project of updating all of SCA?s legacy finding aids and ingesting them in ArchivesSpace. Despite her employment history in many different units of Cline Library over 23 years, she feels fortunate to have become a staff member of Special Collections and Archives where she is surrounded by fascinating history, inspired by incredible coworkers, and encouraged by the aspirations of future archivists. Sam(antha) Meier is the Archivist for Discovery at Cline Library Special Collections and Archives, where she oversees arrangement and description of the department?s archival collections. Prior to coming to Cline Library, Sam worked as an archival technician with the Veterans History Project of the Library of Congress and as a contract archivist with the Union of B.C. Indian Chiefs Library & Archives. She received her Masters in Archival Studies, First Nations Curriculum Concentration, from the University of British Columbia in 2018. Who should attend: Anyone interested in implementing the Protocols for Native American Archival Materials, using ArchivesSpace to facilitate redescription of legacy finding aids or assessing archival backlog, or anyone managing graduate students and interns performing core functions in ArchivesSpace. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From hanstra at nd.edu Tue Mar 16 12:51:30 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Tue, 16 Mar 2021 12:51:30 -0400 Subject: [Archivesspace_Users_Group] PUI indexing issues Message-ID: Hello again. I'm still trying to understand some indexing issues. I've now left my PUI indexing threads and count at the default (which I believe is 1 thread and 25 records/thread). And I have given 4GB to Java processes. I've tried other values as well, but with similar results. No matter what values I use, I cannot seem to fully index PUI. Each time, it will start well but continuously slow down. I've kept a spreadsheet of the number of records/hr I'm indexing and have several attempts which start in the 50-60K/hr range and then continuously slow down to the 1800-1500/hr speed until finally dying with a Java Heap error. I think I'm headed to that again this round. Why might this be happening? Could my data have been corrupted during the transfer from Lyrasis? (I'm working with a database export of our production data). Is the database too far away (our database is in an AWS RDS being accessed from our AWS EC2). I do have one log which gave this error: E, [2021-03-12T18:14:53.886243 #2919] ERROR -- : Thread-9472: Failed fetching archival_object id=1484623: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on 3150, last used 1615590893.870297 seconds ago prior to the Java Heap error. In that log, there were a number of connections for the staff indexer after the PUI indexer stopped reporting, then an 88 minute gap prior to the above connection error and then finally a Java Heap error in the archivesspace.out log. Does the indexer reauthenticate each time it connects to get more information? The earlier question about authentication has me wondering if my database server might be balking at the number of reconnections or something. I'm trying to index 760K records. Bottom line is that I'm still not getting my PUI index creation to complete. Each run can take several days before it finally fails and I have to start all over again. I'm looking for any help to track down why this slowdown is occurring and what I can do to address it. Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Tue Mar 16 13:15:03 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 16 Mar 2021 17:15:03 +0000 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: Message-ID: > I've now left my PUI indexing threads and count at the default (which I believe is 1 thread and 25 records/thread). Try dropping both indexer_records_per_thread and indexer_thread_count for both PUI and Staff indexers. Maybe in half or so. Sometimes with larger records it just needs to be slowed down. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Tuesday, March 16, 2021 12:51 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] PUI indexing issues Hello again. I'm still trying to understand some indexing issues. I've now left my PUI indexing threads and count at the default (which I believe is 1 thread and 25 records/thread). And I have given 4GB to Java processes. I've tried other values as well, but with similar results. No matter what values I use, I cannot seem to fully index PUI. Each time, it will start well but continuously slow down. I've kept a spreadsheet of the number of records/hr I'm indexing and have several attempts which start in the 50-60K/hr range and then continuously slow down to the 1800-1500/hr speed until finally dying with a Java Heap error. I think I'm headed to that again this round. Why might this be happening? Could my data have been corrupted during the transfer from Lyrasis? (I'm working with a database export of our production data). Is the database too far away (our database is in an AWS RDS being accessed from our AWS EC2). I do have one log which gave this error: E, [2021-03-12T18:14:53.886243 #2919] ERROR -- : Thread-9472: Failed fetching archival_object id=1484623: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on 3150, last used 1615590893.870297 seconds ago prior to the Java Heap error. In that log, there were a number of connections for the staff indexer after the PUI indexer stopped reporting, then an 88 minute gap prior to the above connection error and then finally a Java Heap error in the archivesspace.out log. Does the indexer reauthenticate each time it connects to get more information? The earlier question about authentication has me wondering if my database server might be balking at the number of reconnections or something. I'm trying to index 760K records. Bottom line is that I'm still not getting my PUI index creation to complete. Each run can take several days before it finally fails and I have to start all over again. I'm looking for any help to track down why this slowdown is occurring and what I can do to address it. Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Tue Mar 16 13:52:11 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Tue, 16 Mar 2021 13:52:11 -0400 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: Message-ID: Thanks for the suggestion, Blake. A couple additional questions: - Staff indexing is done and has its files written. So does the number of threads given to that make a difference? Is it still taking up resources? - Does there happen to be any way to stop the staff indexing and just let PUI have full access to the server for indexing? - What really bothers me is the slowdown. That indicates to me that some resource is being lost along the way. Anyone have thoughts on what that might be? - Should our repositories be broken up into smaller groupings? I'm beginning to wonder if we have things set up incorrectly, since it sounds like we have a very large data set compared to others. And a comment.... It is really frustrating to have to start over on the indexing each time. It seems that there should be some way to document progress along the way so that the indexing can pick up where it left off. Is that something that might also be looked at? Thanks all. Appreciate your help. Tom On Tue, Mar 16, 2021 at 1:15 PM Blake Carver wrote: > > I've now left my PUI indexing threads and count at the default (which I > believe is 1 thread and 25 records/thread). > > Try dropping both indexer_records_per_thread and indexer_thread_count for > both PUI and Staff indexers. Maybe in half or so. Sometimes with larger > records it just needs to be slowed down. > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom > Hanstra > *Sent:* Tuesday, March 16, 2021 12:51 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] PUI indexing issues > > Hello again. > > I'm still trying to understand some indexing issues. I've now left my PUI > indexing threads and count at the default (which I believe is 1 thread and > 25 records/thread). And I have given 4GB to Java processes. I've tried > other values as well, but with similar results. > > No matter what values I use, I cannot seem to fully index PUI. Each time, > it will start well but continuously slow down. I've kept a spreadsheet of > the number of records/hr I'm indexing and have several attempts which start > in the 50-60K/hr range and then continuously slow down to the 1800-1500/hr > speed until finally dying with a Java Heap error. I think I'm headed to > that again this round. > > Why might this be happening? Could my data have been corrupted during the > transfer from Lyrasis? (I'm working with a database export of our > production data). Is the database too far away (our database is in an AWS > RDS being accessed from our AWS EC2). > > I do have one log which gave this error: > > E, [2021-03-12T18:14:53.886243 #2919] ERROR -- : Thread-9472: Failed > fetching archival_object id=1484623: too many connection resets (due to > Net::ReadTimeout - Net::ReadTimeout) after 0 requests on 3150, last used > 1615590893.870297 seconds > ago > > prior to the Java Heap error. In that log, there were a number of > connections for the staff indexer after the PUI indexer stopped reporting, > then an 88 minute gap prior to the above connection error and then finally > a Java Heap error in the archivesspace.out log. > > Does the indexer reauthenticate each time it connects to get more > information? The earlier question about authentication has me wondering if > my database server might be balking at the number of reconnections or > something. I'm trying to index 760K records. > > Bottom line is that I'm still not getting my PUI index creation to > complete. Each run can take several days before it finally fails and I have > to start all over again. I'm looking for any help to track down why this > slowdown is occurring and what I can do to address it. > > Thanks, > Tom > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Tue Mar 16 14:03:00 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 16 Mar 2021 18:03:00 +0000 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: , Message-ID: I can only answer some of those. - Staff indexing is done and has its files written. So does the number of threads given to that make a difference? Is it still taking up resources? Not so much if it's not doing anything. - Does there happen to be any way to stop the staff indexing and just let PUI have full access to the server for indexing? You can disable either indexer, but that requires a restart. There's a setting in the config. The PUI is just slower than the Staff. - Should our repositories be broken up into smaller groupings? I'm beginning to wonder if we have things set up incorrectly, since it sounds like we have a very large data set compared to others. It's probably not the total number of resources in a repo, just that the resources are quite large. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Tuesday, March 16, 2021 1:52 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] PUI indexing issues Thanks for the suggestion, Blake. A couple additional questions: - Staff indexing is done and has its files written. So does the number of threads given to that make a difference? Is it still taking up resources? - Does there happen to be any way to stop the staff indexing and just let PUI have full access to the server for indexing? - What really bothers me is the slowdown. That indicates to me that some resource is being lost along the way. Anyone have thoughts on what that might be? - Should our repositories be broken up into smaller groupings? I'm beginning to wonder if we have things set up incorrectly, since it sounds like we have a very large data set compared to others. And a comment.... It is really frustrating to have to start over on the indexing each time. It seems that there should be some way to document progress along the way so that the indexing can pick up where it left off. Is that something that might also be looked at? Thanks all. Appreciate your help. Tom On Tue, Mar 16, 2021 at 1:15 PM Blake Carver > wrote: > I've now left my PUI indexing threads and count at the default (which I believe is 1 thread and 25 records/thread). Try dropping both indexer_records_per_thread and indexer_thread_count for both PUI and Staff indexers. Maybe in half or so. Sometimes with larger records it just needs to be slowed down. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tom Hanstra > Sent: Tuesday, March 16, 2021 12:51 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] PUI indexing issues Hello again. I'm still trying to understand some indexing issues. I've now left my PUI indexing threads and count at the default (which I believe is 1 thread and 25 records/thread). And I have given 4GB to Java processes. I've tried other values as well, but with similar results. No matter what values I use, I cannot seem to fully index PUI. Each time, it will start well but continuously slow down. I've kept a spreadsheet of the number of records/hr I'm indexing and have several attempts which start in the 50-60K/hr range and then continuously slow down to the 1800-1500/hr speed until finally dying with a Java Heap error. I think I'm headed to that again this round. Why might this be happening? Could my data have been corrupted during the transfer from Lyrasis? (I'm working with a database export of our production data). Is the database too far away (our database is in an AWS RDS being accessed from our AWS EC2). I do have one log which gave this error: E, [2021-03-12T18:14:53.886243 #2919] ERROR -- : Thread-9472: Failed fetching archival_object id=1484623: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on 3150, last used 1615590893.870297 seconds ago prior to the Java Heap error. In that log, there were a number of connections for the staff indexer after the PUI indexer stopped reporting, then an 88 minute gap prior to the above connection error and then finally a Java Heap error in the archivesspace.out log. Does the indexer reauthenticate each time it connects to get more information? The earlier question about authentication has me wondering if my database server might be balking at the number of reconnections or something. I'm trying to index 760K records. Bottom line is that I'm still not getting my PUI index creation to complete. Each run can take several days before it finally fails and I have to start all over again. I'm looking for any help to track down why this slowdown is occurring and what I can do to address it. Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Tue Mar 16 15:20:47 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Tue, 16 Mar 2021 19:20:47 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board Message-ID: As chair of the 2021 ArchivesSpace Nominating Committee, I seek your nominations of candidates to stand for election for the ArchivesSpace Governance Board representing the Small and Very Large membership levels. The Governance Board is charged with providing oversight for the ArchivesSpace application and community, including fiscal oversight, the approval of development priorities, and oversight of the Technical and User Advisory councils. We are seeking two candidates for the Small level and one candidate for the Very Large level. (The current incumbent at the Very Large membership level is running for re-election as representative.) The terms for all successful candidates will be July 1, 2021-June 30, 2024. Each newly elected member representative will be eligible to run for a second term, July 1, 2024-June 30, 2027. Governance Board nominees must be currently employed by an ArchivesSpace member organization in either the Small or Very Large member levels (see the member lists at: http://archivesspace.org/community/whos-using-archivesspace/). A variety of skills, interests, and experience can be useful in furthering the Board's mission, but nominees should ideally have administrative and fiscal oversight experience. As the community for a software application used in many different settings, we seek diverse voices in working to improve ArchivesSpace and support those who use or may benefit from using it. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in these important leadership roles. To submit nominations, including self-nominations, please submit this form at https://forms.gle/m2nN49M34CPgnvci9. Nominees who confirm their interest in standing for election will be requested to supply a formal candidate statement outlining their qualifications for serving on the ArchivesSpace Governance Board (see: http://archivesspace.org/about/governance-board-and-councils/). The Nominating Committee will review all nominations and confirm a slate of nominees with the current Governance Board. An election ballot will be circulated to member institutions in mid-May. Nominations must be received by 9:00 p.m. EDT on Friday April 23rd. Please contact Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org or any member of the Nominating Committee with questions. 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, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: Brittany Newberry, Robert W. Woodruff Library, Atlanta University Center, Chair of User Advisory Council Trevor Thornton, North Carolina State University, Chair of Technical Advisory Council Zach Johnson, Vanderbilt University, representing very large membership level Jacky Johnson, Miami University, representing large membership level Heidi Buchanan, West Carolina University, representing medium membership level Patricia Burdick, Colby College, representing small membership level Yue Ma, Museum of Chinese in America, representing very small membership level Christine Di Bella (ArchivesSpace Program Manager), ex officio _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Tue Mar 16 15:20:52 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Tue, 16 Mar 2021 19:20:52 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: The ArchivesSpace Governance Board is seeking nominations to fill up to three (3) vacancies on the ArchivesSpace Technical Advisory Council (TAC). The Technical Advisory Council (https://archivesspace.org/governance-board-and-councils#TAC) 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: * 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 in formats such as EAD, MARCXML, and CSV. * Documenting the metadata standards used by ArchivesSpace and monitoring the standards landscape. * 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. * Maintaining and updating technical documentation, including documentation of the API. * Providing support and resources to help develop a community of code committers. Nominees should preferably be presently employed at an ArchivesSpace member institution (please refer to the member list at: http://archivesspace.org/community/whos-using-archivesspace/) or employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations from non-member institutions will be considered based on their expertise and ability to contribute to the TAC. As the community for a software application used in many different settings, we seek diverse voices in working to improve ArchivesSpace and support those who use or may benefit from using it. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in these important leadership roles. 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, 2021-June 30, 2023. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2023-June 30, 2025. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please submit this form at https://forms.gle/m2nN49M34CPgnvci9. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. Nominations must be received by 9:00 p.m. EDT on Friday April 23rd. Please contact Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org or any member of the Nominating Committee with questions. 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, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: Brittany Newberry, Robert W. Woodruff Library, Atlanta University Center, Chair of User Advisory Council Trevor Thornton, North Carolina State University, Chair of Technical Advisory Council Zach Johnson, Vanderbilt University, representing very large membership level Jacky Johnson, Miami University, representing large membership level Heidi Buchanan, West Carolina University, representing medium membership level Patricia Burdick, Colby College, representing small membership level Yue Ma, Museum of Chinese in America, representing very small membership level Christine Di Bella (ArchivesSpace Program Manager), ex officio _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Tue Mar 16 15:21:00 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Tue, 16 Mar 2021 19:21:00 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council Message-ID: The ArchivesSpace Governance Board is seeking nominations to fill up to three (3) vacancies on the ArchivesSpace User Advisory Council (UAC). The User Advisory Council (https://archivesspace.org/governance-board-and-councils#UAC) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. Some of the activities UAC is currently engaged in are: * Advising the ArchivesSpace Governance Board and the ArchivesSpace Organizational Home on the design and delivery of services, such as community engagement and support services, technical support, and training. * As a joint representative of the Development Prioritization subteam, discussing and voting on ideas for software enhancements and improvements. * As a joint representative of the Testing subteam, conducting user-centered testing of the application prior to releases and conduct ongoing usability studies as needed. * Liaising with national and regional archives organizations. * Maintaining and updating user documentation. * Advocating on the usability and functionality of the software program to facilitate adoption of the program. Nominees should be presently employed at an ArchivesSpace member institution (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). As the community for a software application used in many different settings, we seek diverse voices in working to improve ArchivesSpace and support those who use or may benefit from using it. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in these important leadership roles. 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, 2021-June 30, 2023. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2023-June 30, 2025. To nominate a candidate for the ArchivesSpace User Advisory Council, please submit this form at https://forms.gle/m2nN49M34CPgnvci9. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. Nominations must be received by 9:00 p.m. EDT on Friday April 23rd. Please contact Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org or any member of the Nominating Committee with questions. 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, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: Brittany Newberry, Robert W. Woodruff Library, Atlanta University Center, Chair of User Advisory Council Trevor Thornton, North Carolina State University, Chair of Technical Advisory Council Zach Johnson, Vanderbilt University, representing very large membership level Jacky Johnson, Miami University, representing large membership level Heidi Buchanan, West Carolina University, representing medium membership level Patricia Burdick, Colby College, representing small membership level Yue Ma, Museum of Chinese in America, representing very small membership level Christine Di Bella (ArchivesSpace Program Manager), ex officio _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Wed Mar 17 11:42:56 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Wed, 17 Mar 2021 11:42:56 -0400 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: Message-ID: > > > - What really bothers me is the slowdown. That indicates to me that some > resource is being lost along the way. Anyone have thoughts on what that > might be? > > > Just to follow up on my earlier post, I did get even lower numbers from Blake to try based upon what he used for our hosted account. But I'm seeing the same pattern in terms of slowdowns regarding the number of records that get processed/hour. Is this typical? Is it just hitting records that have more work to be done? Or do I still have a resource issue. I note that the number of docs in Solr has not changed at all throughout the last couple of attempts, which again leads me to believe it has already handled these records (at least once) before and thus there is no more indexing to really be done with the records which it is running through the PUI indexer again. Which leads back to the "why does PUI indexing restart each time from 0" question. How does one add an enhancement request to have this reviewed and (perhaps) changed? Thanks, Tom > >> -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Wed Mar 17 12:01:56 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 17 Mar 2021 16:01:56 +0000 Subject: [Archivesspace_Users_Group] Apply now for the ArchivesSpace Member Match program Message-ID: <2AE1C0E2-B181-42B6-82B2-1EEEB9ECF98C@lyrasis.org> Dear ArchivesSpace Members, Applications are now open for the ArchivesSpace Member Match program. The Member Match program is an initiative to engage the ArchivesSpace membership community, created and organized by the Member Engagement sub-team of the ArchivesSpace User Advisory Council, with support from the ArchivesSpace Community Engagement Coordinator. The program is intended to be a resource and venue for peer-to-peer support between ArchivesSpace members. For one, year-long term, participants will be matched with a member with whom they can receive and offer professional insight, advice, and comradery. The program will also offer participants the opportunity to engage in exclusive events and enlightening discussions about ArchivesSpace and its active user community. Eligibility Any individual affiliated with an ArchivesSpace member organization is eligible to participate in the ArchivesSpace Member Match program and there is no limit to the number of individuals from a member organization that may participate. If you are unsure of your organization?s ArchivesSpace membership status, visit https://archivesspace.org/community/whos-using-archivesspace or email ArchivesSpaceHome at lyrasis.org. To Apply There is a short application to complete at https://airtable.com/shr1nE3RWpR7Y78En. Applications should be submitted by April 30. Applicants will be notified of their matches no later than June 30. To Learn More Visit the Member Match wiki: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program The ArchivesSpace Member Engagement Sub-team conducted an informational webinar on March 10th. You can find a link to the recording of this webinar on the Member Match wiki. Please feel free to direct any questions to ArchivesSpaceHome at lyrasis.org -Sent on behalf of the ArchivesSpace Member Engagement sub-team Kate Blalack, American Song Archive Regina Carra, American Folk Art Museum Bailey Hoffner, University of Oklahoma Ashley Knox, University of North Carolina Wilmington Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory Council Chair Jessica Crouch, ArchivesSpace Community Engagement Coordinator -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Wed Mar 17 13:12:36 2021 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 17 Mar 2021 17:12:36 +0000 Subject: [Archivesspace_Users_Group] Manage Top Containers endpoints Message-ID: Hey everyone, Does anyone have experience getting search results from the Manage Top Containers functionality through the API? I?m looking to do some response testing and was wondering how to structure requests against this page. Are the endpoints documented somewhere? Thanks, Patrick Galligan -------------- next part -------------- An HTML attachment was scrubbed... URL: From na207 at cam.ac.uk Thu Mar 18 05:55:34 2021 From: na207 at cam.ac.uk (Natalie Adams) Date: Thu, 18 Mar 2021 09:55:34 +0000 Subject: [Archivesspace_Users_Group] Fw: Error message In-Reply-To: References: <17ad8635965b25d9390c1c3a7c58644c@cam.ac.uk>, Message-ID: Natalie Adams Systems Archivist Cambridge University Library Information about using Cambridge University Libraries is available online here: https://www.lib.cam.ac.uk/using-library ________________________________ From: CUL Archive Management System Sent: 18 March 2021 09:53 To: Natalie Adams Subject: FW: Error message ________________________________________ From: E. A. Ennion-Smith Sent: Thursday, March 18, 2021 9:53:50 AM (UTC+00:00) Monrovia, Reykjavik To: CUL Archive Management System Subject: Error message Good morning, I have been unable to save my changes made to one of my collections, see attached screenshot. I wanted to update the covering dates and for some reason it has put the date, extent and languages all twice and I cannot save my changes to delete the second set of information. This is my very largest collection and I don't know if that has something to do with it? I would appreciate your advice. Many thanks, Lizzy -- Elizabeth Ennion-Smith Archivist Pembroke College Cambridge CB2 1RF Telephone: 01223 764151 Email: eae31 at cam.ac.uk Please note I am currently working from home so there may sometimes be a delay in responding to enquiries. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: AMS error.JPG Type: image/jpeg Size: 59209 bytes Desc: AMS error.JPG URL: From na207 at cam.ac.uk Thu Mar 18 06:06:08 2021 From: na207 at cam.ac.uk (Natalie Adams) Date: Thu, 18 Mar 2021 10:06:08 +0000 Subject: [Archivesspace_Users_Group] Error message In-Reply-To: References: <17ad8635965b25d9390c1c3a7c58644c@cam.ac.uk>, , Message-ID: I'm so sorry please ignore my last message- a few too many 'archivesspace' email addresses come up when I start typing. I'll check more carefully next time! Natalie Natalie Adams Systems Archivist Cambridge University Library Information about using Cambridge University Libraries is available online here: https://www.lib.cam.ac.uk/using-library ________________________________ From: Natalie Adams Sent: 18 March 2021 09:55 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Fw: Error message Natalie Adams Systems Archivist Cambridge University Library Information about using Cambridge University Libraries is available online here: https://www.lib.cam.ac.uk/using-library ________________________________ From: CUL Archive Management System Sent: 18 March 2021 09:53 To: Natalie Adams Subject: FW: Error message ________________________________________ From: E. A. Ennion-Smith Sent: Thursday, March 18, 2021 9:53:50 AM (UTC+00:00) Monrovia, Reykjavik To: CUL Archive Management System Subject: Error message Good morning, I have been unable to save my changes made to one of my collections, see attached screenshot. I wanted to update the covering dates and for some reason it has put the date, extent and languages all twice and I cannot save my changes to delete the second set of information. This is my very largest collection and I don't know if that has something to do with it? I would appreciate your advice. Many thanks, Lizzy -- Elizabeth Ennion-Smith Archivist Pembroke College Cambridge CB2 1RF Telephone: 01223 764151 Email: eae31 at cam.ac.uk Please note I am currently working from home so there may sometimes be a delay in responding to enquiries. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Thu Mar 18 10:50:58 2021 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Thu, 18 Mar 2021 14:50:58 +0000 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: Message-ID: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu> This is a little bit of a shot in the dark, but have you looked at disk space on whatever host Solr is resident on? (the ASpace server if you?re not running an external one)? A thing we?ve hit a couple times is that Solr, at least in some configurations, needs substantial headroom on disk to perform well ? I think it?s related to how it builds and maintains the index? So it might be worth looking to see if Solr is filling up the disk enough that it can?t efficiently handle itself. -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: on behalf of Tom Hanstra Reply-To: Archivesspace Users Group Date: Wednesday, March 17, 2021 at 11:43 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] PUI indexing issues - What really bothers me is the slowdown. That indicates to me that some resource is being lost along the way. Anyone have thoughts on what that might be? Just to follow up on my earlier post, I did get even lower numbers from Blake to try based upon what he used for our hosted account. But I'm seeing the same pattern in terms of slowdowns regarding the number of records that get processed/hour. Is this typical? Is it just hitting records that have more work to be done? Or do I still have a resource issue. I note that the number of docs in Solr has not changed at all throughout the last couple of attempts, which again leads me to believe it has already handled these records (at least once) before and thus there is no more indexing to really be done with the records which it is running through the PUI indexer again. Which leads back to the "why does PUI indexing restart each time from 0" question. How does one add an enhancement request to have this reviewed and (perhaps) changed? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Thu Mar 18 11:24:22 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Thu, 18 Mar 2021 11:24:22 -0400 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu> References: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu> Message-ID: Dave, Thanks for the suggestion, but unless there is some direct limitation within Solr, that should not be an issue. My disk is at only about 50% of capacity and Solr should be able to expand as needed. In my case, I don't think there has been much addition to Solr because I'm reindexing records which have been indexed already. So the deleted records are growing, but not the overall number of records. My index is currently at about 6GB. Any other thoughts out there? Thanks, Tom On Thu, Mar 18, 2021 at 10:51 AM Mayo, Dave wrote: > This is a little bit of a shot in the dark, but have you looked at disk > space on whatever host Solr is resident on? (the ASpace server if you?re > not running an external one)? > > A thing we?ve hit a couple times is that Solr, at least in some > configurations, needs substantial headroom on disk to perform well ? I > think it?s related to how it builds and maintains the index? So it might > be worth looking to see if Solr is filling up the disk enough that it can?t > efficiently handle itself. > > > > -- > > Dave Mayo (he/him) > > Senior Digital Library Software Engineer > Harvard University > HUIT > LTS > > > > *From: * on > behalf of Tom Hanstra > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Wednesday, March 17, 2021 at 11:43 AM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] PUI indexing issues > > > > > > > > - What really bothers me is the slowdown. That indicates to me that some > resource is being lost along the way. Anyone have thoughts on what that > might be? > > > > > > Just to follow up on my earlier post, I did get even lower numbers from > Blake to try based upon what he used for our hosted account. But I'm seeing > the same pattern in terms of slowdowns regarding the number of records that > get processed/hour. Is this typical? Is it just hitting records that have > more work to be done? Or do I still have a resource issue. > > > > I note that the number of docs in Solr has not changed at all throughout > the last couple of attempts, which again leads me to believe it has already > handled these records (at least once) before and thus there is no more > indexing to really be done with the records which it is running through > the PUI indexer again. Which leads back to the "why does PUI indexing > restart each time from 0" question. How does one add an enhancement request > to have this reviewed and (perhaps) changed? > > > > Thanks, > > Tom > > > > -- > > *Tom Hanstra* > > *Sr. Systems Administrator* > > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Thu Mar 18 12:08:32 2021 From: npwb2 at cam.ac.uk (Nick Butler) Date: Thu, 18 Mar 2021 16:08:32 +0000 Subject: [Archivesspace_Users_Group] Exporting very large collections (OAI, EAD, PDF) Message-ID: Hi all, We're exploring sharing our archival data with a few partners via OAI, and have been coming up against timeouts when attempting to export some of our larger collections (with, say, over 10,000 published descendant records), even when increasing the timeout threshold to ten minutes. We appreciate that 10,000 archival object records on one resource is fairly large (our largest has more like 90,000), but I can't imagine that there aren't other institutions with individual collections as large or larger (perhaps substantially so). Are others in this same boat able to export these larger collections via OAI? We've implemented a change in our local plugin which stops processing and adding child records to the oai_ead output, which allows all of the resource-level records to be generated without timing out, but does mean we miss out on being able to share multi-level descriptions. In a similar vein we're unable to generate PDFs on our PUI for some of these larger records, or export their EAD in the staff interface. We've worked around these latter issues by adding functionality to export portions of a record tree rather than the whole thing, but it would be nice to know if this is a problem that others are facing too (or if, say, it's caused by our local setup, infrastructure, etc). Many thanks, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Fri Mar 19 09:45:55 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Fri, 19 Mar 2021 09:45:55 -0400 Subject: [Archivesspace_Users_Group] Logs and database connections Message-ID: Back again... I have yet another wrinkle to things which I'm trying to track down. I've started working with another instance of ArchivesSpace just to try to move things forward a bit faster and now have some different issues going on, this time with my database connections. In the logs, things were humming along when, for reasons unknown, they no longer were humming: I, [2021-03-19T05:09:13.304429 #13392] INFO -- : Thread-2868: Staff Indexer [2021-03-19 05:09:13 -0400] ~~~ Indexed 595 420 of 763368 archival_object records in repository UNDA I, [2021-03-19T05:09:14.625595 #13392] INFO -- : Thread-2906: PUI Indexer [2021-03-19 05:09:14 -0400] ~~~ Indexed 43278 0 of 763368 archival_object records in repository UNDA E, [2021-03-19T05:09:14.768619 #13392] ERROR -- : Thread-5364: Failed fetching archival_object id=809925: {"error":{"db_ error":["Database integrity constraint conflict: Java::JavaSql::SQLNonTransientConnectionException: No operations allowe d after connection closed."]}} It *looks* like something got lost, but after some digging, I'm beginning to wonder what is actually going on. Note that the PUI and Staff indexing threads are 2906 and 2868 respectively. Throughout the log, this is the case. Then, the thread which complains about connections is 5364...a completely different thread. I see no other references to that thread in any logs. So, what, exactly, timed out here? The thing that has me scratching my head is that Solr is continuing to see increased numbers of records added (I started that from scratch along with everything else). So, how can records be being added to the Solr index without showing up in the logs? Or could it be that it is just the log writer which is timed out but indexing is still going on in the background? Is there any way, besides the logs, to know where indexing stands? I note that this database was dedicated only to this instance of ArchivesSpace and continues to see activity. So if things have truly failed, what is it doing? I have a feeling that indexing is still going on but the logging just stopped working properly. But is there any way to tell? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneal at richmond.edu Mon Mar 22 10:33:16 2021 From: rneal at richmond.edu (Neal, Rick) Date: Mon, 22 Mar 2021 14:33:16 +0000 Subject: [Archivesspace_Users_Group] SOLR error explanation needed Message-ID: Good morning, While running down an error, I found that my solr_backups directory has over 20,000 directories in it that look like this. Note that these are ALL for March 21st and that each of these directories have subdirectories. Though it is not using a log of space, how many subdirectories does solr_backups need? Should I have something in place to delete based on date? Thanks! Rick Neal 4096 Mar 21 00:00 solr.1616299200 4096 Mar 21 00:00 solr.1616299201 4096 Mar 21 00:00 solr.1616299202 4096 Mar 21 00:00 solr.1616299203 4096 Mar 21 00:00 solr.1616299208 4096 Mar 21 01:00 solr.1616302800 4096 Mar 21 01:00 solr.1616302801 4096 Mar 21 01:00 solr.1616302806 4096 Mar 21 01:00 solr.1616302807 4096 Mar 21 01:00 solr.1616302808 4096 Mar 21 02:00 solr.1616306400 4096 Mar 21 02:00 solr.1616306405 4096 Mar 21 02:00 solr.1616306406 4096 Mar 21 02:00 solr.1616306407 4096 Mar 21 02:00 solr.1616306408 4096 Mar 21 03:00 solr.1616310000 4096 Mar 21 03:00 solr.1616310001 4096 Mar 21 03:00 solr.1616310002 4096 Mar 21 03:00 solr.1616310007 4096 Mar 21 03:00 solr.1616310008 4096 Mar 21 04:00 solr.1616313600 4096 Mar 21 04:00 solr.1616313601 4096 Mar 21 04:00 solr.1616313606 4096 Mar 21 04:00 solr.1616313607 4096 Mar 21 04:00 solr.1616313608 4096 Mar 21 05:00 solr.1616317200 4096 Mar 21 05:00 solr.1616317201 4096 Mar 21 05:00 solr.1616317206 4096 Mar 21 05:00 solr.1616317211 4096 Mar 21 05:00 solr.1616317212 4096 Mar 21 06:00 solr.1616320800 4096 Mar 21 06:00 solr.1616320805 4096 Mar 21 06:00 solr.1616320806 4096 Mar 21 06:00 solr.1616320811 4096 Mar 21 06:00 solr.1616320812 4096 Mar 21 07:00 solr.1616324400 4096 Mar 21 07:00 solr.1616324405 4096 Mar 21 07:00 solr.1616324410 4096 Mar 21 07:00 solr.1616324411 4096 Mar 21 07:00 solr.1616324412 4096 Mar 21 08:00 solr.1616328000 4096 Mar 21 08:00 solr.1616328001 4096 Mar 21 08:00 solr.1616328006 4096 Mar 21 08:00 solr.1616328011 4096 Mar 21 08:00 solr.1616328016 4096 Mar 21 09:00 solr.1616331600 4096 Mar 21 09:00 solr.1616331601 4096 Mar 21 09:00 solr.1616331606 4096 Mar 21 09:00 solr.1616331607 4096 Mar 21 09:00 solr.1616331612 4096 Mar 21 10:00 solr.1616335200 4096 Mar 21 10:00 solr.1616335205 4096 Mar 21 10:00 solr.1616335206 4096 Mar 21 10:00 solr.1616335207 4096 Mar 21 10:00 solr.1616335208 4096 Mar 21 11:00 solr.1616338800 4096 Mar 21 11:00 solr.1616338801 4096 Mar 21 11:00 solr.1616338806 4096 Mar 21 11:00 solr.1616338807 4096 Mar 21 11:00 solr.1616338812 4096 Mar 21 12:00 solr.1616342400 4096 Mar 21 12:00 solr.1616342401 4096 Mar 21 12:00 solr.1616342406 4096 Mar 21 12:00 solr.1616342407 4096 Mar 21 12:00 solr.1616342412 4096 Mar 21 13:00 solr.1616346000 4096 Mar 21 13:00 solr.1616346001 4096 Mar 21 13:00 solr.1616346002 4096 Mar 21 13:00 solr.1616346007 4096 Mar 21 13:00 solr.1616346008 4096 Mar 21 14:00 solr.1616349600 4096 Mar 21 14:00 solr.1616349605 4096 Mar 21 14:00 solr.1616349610 4096 Mar 21 14:00 solr.1616349615 4096 Mar 21 14:00 solr.1616349616 4096 Mar 21 15:00 solr.1616353200 4096 Mar 21 15:00 solr.1616353201 4096 Mar 21 15:00 solr.1616353202 4096 Mar 21 15:00 solr.1616353203 4096 Mar 21 15:00 solr.1616353204 4096 Mar 21 16:00 solr.1616356800 4096 Mar 21 16:00 solr.1616356801 4096 Mar 21 16:00 solr.1616356806 4096 Mar 21 17:00 solr.1616360400 4096 Mar 21 17:00 solr.1616360405 4096 Mar 21 17:00 solr.1616360410 4096 Mar 21 17:00 solr.1616360415 4096 Mar 21 17:00 solr.1616360416 4096 Mar 21 18:00 solr.1616364000 4096 Mar 21 18:00 solr.1616364005 4096 Mar 21 18:00 solr.1616364006 4096 Mar 21 18:00 solr.1616364007 4096 Mar 21 18:00 solr.1616364012 4096 Mar 21 19:00 solr.1616367600 4096 Mar 21 19:00 solr.1616367601 4096 Mar 21 19:00 solr.1616367606 4096 Mar 21 19:00 solr.1616367611 4096 Mar 21 19:00 solr.1616367612 4096 Mar 21 20:00 solr.1616371200 4096 Mar 21 20:00 solr.1616371201 4096 Mar 21 20:00 solr.1616371206 4096 Mar 21 20:00 solr.1616371211 4096 Mar 21 20:00 solr.1616371212 4096 Mar 21 21:00 solr.1616374800 4096 Mar 21 21:00 solr.1616374801 4096 Mar 21 21:00 solr.1616374806 4096 Mar 21 21:00 solr.1616374807 4096 Mar 21 21:00 solr.1616374812 4096 Mar 21 22:00 solr.1616378400 4096 Mar 21 22:00 solr.1616378401 4096 Mar 21 22:00 solr.1616378402 4096 Mar 21 22:00 solr.1616378407 4096 Mar 21 22:00 solr.1616378412 4096 Mar 21 23:00 solr.1616382000 4096 Mar 21 23:00 solr.1616382001 4096 Mar 21 23:00 solr.1616382006 4096 Mar 21 23:00 solr.1616382007 4096 Mar 21 23:00 solr.1616382008 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Mar 22 10:52:14 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 22 Mar 2021 14:52:14 +0000 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu>, Message-ID: I did some experimenting this weekend, messing around with indexer speeds, and found I could get it to succeed with the right indexer settings. I think the answer is going to be "it depends" and you'll need to experiment with what works on your set up with your data. I started with the defaults, then dropped it to reallllly slow (1 thread 1 per), then just tried to dial it up and down. The last one I tried worked fine, it was fast enough to finish in a reasonable amount of time and didn't slow down or crash. Your settings may not look like this, but here's something to try. AppConfig[:pui_indexer_records_per_thread] = 50 AppConfig[:pui_indexer_thread_count] = 1 So some extra detail for the mailing list archives... if your site keeps crashing before the indexers finish and you're not seeing any particular errors in the logs that make you think you have a problem with your data, try turning the knobs on your indexer speed and see if that helps. It looks like maybe the indexer just eats up too much memory on BIG records and having too many (too many being 15ish) threads running causes it to crash. I know BIG is pretty subjective, if you have a bunch of resources (maybe a few thousand) AND those resources all have ALLOTA (maybe a few thousand) children with ALLOTA subjects/agents/notes/stuff, then you might hit this problem. Seems like it's not the total number of resources, it's probably because those resources are big/complex/deep. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Thursday, March 18, 2021 11:24 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] PUI indexing issues Dave, Thanks for the suggestion, but unless there is some direct limitation within Solr, that should not be an issue. My disk is at only about 50% of capacity and Solr should be able to expand as needed. In my case, I don't think there has been much addition to Solr because I'm reindexing records which have been indexed already. So the deleted records are growing, but not the overall number of records. My index is currently at about 6GB. Any other thoughts out there? Thanks, Tom On Thu, Mar 18, 2021 at 10:51 AM Mayo, Dave > wrote: This is a little bit of a shot in the dark, but have you looked at disk space on whatever host Solr is resident on? (the ASpace server if you?re not running an external one)? A thing we?ve hit a couple times is that Solr, at least in some configurations, needs substantial headroom on disk to perform well ? I think it?s related to how it builds and maintains the index? So it might be worth looking to see if Solr is filling up the disk enough that it can?t efficiently handle itself. -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: > on behalf of Tom Hanstra > Reply-To: Archivesspace Users Group > Date: Wednesday, March 17, 2021 at 11:43 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] PUI indexing issues - What really bothers me is the slowdown. That indicates to me that some resource is being lost along the way. Anyone have thoughts on what that might be? Just to follow up on my earlier post, I did get even lower numbers from Blake to try based upon what he used for our hosted account. But I'm seeing the same pattern in terms of slowdowns regarding the number of records that get processed/hour. Is this typical? Is it just hitting records that have more work to be done? Or do I still have a resource issue. I note that the number of docs in Solr has not changed at all throughout the last couple of attempts, which again leads me to believe it has already handled these records (at least once) before and thus there is no more indexing to really be done with the records which it is running through the PUI indexer again. Which leads back to the "why does PUI indexing restart each time from 0" question. How does one add an enhancement request to have this reviewed and (perhaps) changed? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Mon Mar 22 11:21:13 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Mon, 22 Mar 2021 11:21:13 -0400 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu> Message-ID: Thanks, Blake. In your testing, how big was the repository that you were testing against. Mine has "763368 archival_object records" and I consistently get into the 670K range for staff and 575 range for PUI before things really slow down. I'm now trying to really increase the Java settings to see if that will help. So far, the problem is similar: real slow downs after zipping through the first records. I'll also try some of the settings you have there to see if fewer but larger threads work better than multiple smaller threads. Tom On Mon, Mar 22, 2021 at 10:52 AM Blake Carver wrote: > I did some experimenting this weekend, messing around with indexer speeds, > and found I could get it to succeed with the right indexer settings. I > think the answer is going to be "it depends" and you'll need to experiment > with what works on your set up with your data. I started with the defaults, > then dropped it to reallllly slow (1 thread 1 per), then just tried to dial > it up and down. The last one I tried worked fine, it was fast enough to > finish in a reasonable amount of time and didn't slow down or crash. Your > settings may not look like this, but here's something to try. > > AppConfig[:pui_indexer_records_per_thread] = 50 > AppConfig[:pui_indexer_thread_count] = 1 > > > So some extra detail for the mailing list archives... if your site keeps > crashing before the indexers finish and you're not seeing any particular > errors in the logs that make you think you have a problem with your data, > try turning the knobs on your indexer speed and see if that helps. > > It looks like maybe the indexer just eats up too much memory on BIG > records and having too many (too many being 15ish) threads running causes > it to crash. I know BIG is pretty subjective, if you have a bunch of > resources (maybe a few thousand) AND those resources all have ALLOTA (maybe > a few thousand) children with ALLOTA subjects/agents/notes/stuff, then you > might hit this problem. Seems like it's not the total number of resources, > it's probably because those resources are big/complex/deep. > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom > Hanstra > *Sent:* Thursday, March 18, 2021 11:24 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] PUI indexing issues > > Dave, > > Thanks for the suggestion, but unless there is some direct limitation > within Solr, that should not be an issue. My disk is at only about 50% of > capacity and Solr should be able to expand as needed. In my case, I don't > think there has been much addition to Solr because I'm reindexing records > which have been indexed already. So the deleted records are growing, but > not the overall number of records. My index is currently at about 6GB. > > Any other thoughts out there? > > Thanks, > Tom > > On Thu, Mar 18, 2021 at 10:51 AM Mayo, Dave wrote: > > This is a little bit of a shot in the dark, but have you looked at disk > space on whatever host Solr is resident on? (the ASpace server if you?re > not running an external one)? > > A thing we?ve hit a couple times is that Solr, at least in some > configurations, needs substantial headroom on disk to perform well ? I > think it?s related to how it builds and maintains the index? So it might > be worth looking to see if Solr is filling up the disk enough that it can?t > efficiently handle itself. > > > > -- > > Dave Mayo (he/him) > > Senior Digital Library Software Engineer > Harvard University > HUIT > LTS > > > > *From: * on > behalf of Tom Hanstra > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Wednesday, March 17, 2021 at 11:43 AM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] PUI indexing issues > > > > > > > > - What really bothers me is the slowdown. That indicates to me that some > resource is being lost along the way. Anyone have thoughts on what that > might be? > > > > > > Just to follow up on my earlier post, I did get even lower numbers from > Blake to try based upon what he used for our hosted account. But I'm seeing > the same pattern in terms of slowdowns regarding the number of records that > get processed/hour. Is this typical? Is it just hitting records that have > more work to be done? Or do I still have a resource issue. > > > > I note that the number of docs in Solr has not changed at all throughout > the last couple of attempts, which again leads me to believe it has already > handled these records (at least once) before and thus there is no more > indexing to really be done with the records which it is running through > the PUI indexer again. Which leads back to the "why does PUI indexing > restart each time from 0" question. How does one add an enhancement request > to have this reviewed and (perhaps) changed? > > > > Thanks, > > Tom > > > > -- > > *Tom Hanstra* > > *Sr. Systems Administrator* > > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Mar 22 12:05:35 2021 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 22 Mar 2021 16:05:35 +0000 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu> , Message-ID: Tom, Not sure if it will help (and not sure if you shared your config.rb file in a previous message), but have you tried: * turning off the Solr backups during the re-indexing (https://github.com/archivesspace/archivesspace/blob/d207e8a7bb01c2b7b6f42ee5c0025d95f35ee7ae/common/config/config-defaults.rb#L76). Just going back to Dave's suggestion about keeping an eye out on disk space. * updating the record inheritance settings and removing the bit about inheriting scope and contents notes, which really bloats the index since most finding aids won't have lower-level descriptive notes (https://github.com/archivesspace/archivesspace/blob/d207e8a7bb01c2b7b6f42ee5c0025d95f35ee7ae/common/config/config-defaults.rb#L411-L413). For our record inheritance settings , https://github.com/YaleArchivesSpace/aspace-deployment/blob/master/prod/config.rb#L204-L244), we only inherit two notes currently: access notes and preferred citation notes. * Turning off the PUI indexer until the staff indexing is done, and then turning the PUI indexer back on? When testing re-indexing locally, I usually bump up the two values that Blake listed below, at least until I start getting Java heapspace errors and don't' have any more RAM to allot to ASpace ?. But even just waiting for the archival objects can take a while, depending on the settings in your config.rb file. While waiting for a full re-index once when things were re-indexing on a server that I didn't have access to, I'd periodically look at the last archival object ID that was indexed, and then run a database query to see how many more archival objects were left in that repo, since a full re-index seems to go in order of the primary keys. e.g. select count(*) from archival_object where id > {archival_object id} and repo_id = {repo id}; That would at least give me a sense of how much longer it might be for all the archival objects were left in one of our repos. As for the slowdown, after all the archival objects are indexed in a repository, the next thing that happens (although it can take quite a while) will be for all the tree indexes to be created and finally committed to Solr. See https://github.com/archivesspace/archivesspace/blob/82c4603fe22bf0fd06043974478d4caf26e1c646/indexer/app/lib/pui_indexer.rb#L136. If i recall correctly, there won't be any specific mentions in the logs about that, but after you get a message about all of the archival objects being indexed in a specfic repository, you'll get another message about the archival objects being indexed again sometime later, at which point the full trees have been reindexed again, and then the indexer will be off to the next repo (or record type, like classification records, etc.) Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Monday, March 22, 2021 11:21 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] PUI indexing issues Thanks, Blake. In your testing, how big was the repository that you were testing against. Mine has "763368 archival_object records" and I consistently get into the 670K range for staff and 575 range for PUI before things really slow down. I'm now trying to really increase the Java settings to see if that will help. So far, the problem is similar: real slow downs after zipping through the first records. I'll also try some of the settings you have there to see if fewer but larger threads work better than multiple smaller threads. Tom On Mon, Mar 22, 2021 at 10:52 AM Blake Carver > wrote: I did some experimenting this weekend, messing around with indexer speeds, and found I could get it to succeed with the right indexer settings. I think the answer is going to be "it depends" and you'll need to experiment with what works on your set up with your data. I started with the defaults, then dropped it to reallllly slow (1 thread 1 per), then just tried to dial it up and down. The last one I tried worked fine, it was fast enough to finish in a reasonable amount of time and didn't slow down or crash. Your settings may not look like this, but here's something to try. AppConfig[:pui_indexer_records_per_thread] = 50 AppConfig[:pui_indexer_thread_count] = 1 So some extra detail for the mailing list archives... if your site keeps crashing before the indexers finish and you're not seeing any particular errors in the logs that make you think you have a problem with your data, try turning the knobs on your indexer speed and see if that helps. It looks like maybe the indexer just eats up too much memory on BIG records and having too many (too many being 15ish) threads running causes it to crash. I know BIG is pretty subjective, if you have a bunch of resources (maybe a few thousand) AND those resources all have ALLOTA (maybe a few thousand) children with ALLOTA subjects/agents/notes/stuff, then you might hit this problem. Seems like it's not the total number of resources, it's probably because those resources are big/complex/deep. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tom Hanstra > Sent: Thursday, March 18, 2021 11:24 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] PUI indexing issues Dave, Thanks for the suggestion, but unless there is some direct limitation within Solr, that should not be an issue. My disk is at only about 50% of capacity and Solr should be able to expand as needed. In my case, I don't think there has been much addition to Solr because I'm reindexing records which have been indexed already. So the deleted records are growing, but not the overall number of records. My index is currently at about 6GB. Any other thoughts out there? Thanks, Tom On Thu, Mar 18, 2021 at 10:51 AM Mayo, Dave > wrote: This is a little bit of a shot in the dark, but have you looked at disk space on whatever host Solr is resident on? (the ASpace server if you?re not running an external one)? A thing we?ve hit a couple times is that Solr, at least in some configurations, needs substantial headroom on disk to perform well ? I think it?s related to how it builds and maintains the index? So it might be worth looking to see if Solr is filling up the disk enough that it can?t efficiently handle itself. -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: > on behalf of Tom Hanstra > Reply-To: Archivesspace Users Group > Date: Wednesday, March 17, 2021 at 11:43 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] PUI indexing issues - What really bothers me is the slowdown. That indicates to me that some resource is being lost along the way. Anyone have thoughts on what that might be? Just to follow up on my earlier post, I did get even lower numbers from Blake to try based upon what he used for our hosted account. But I'm seeing the same pattern in terms of slowdowns regarding the number of records that get processed/hour. Is this typical? Is it just hitting records that have more work to be done? Or do I still have a resource issue. I note that the number of docs in Solr has not changed at all throughout the last couple of attempts, which again leads me to believe it has already handled these records (at least once) before and thus there is no more indexing to really be done with the records which it is running through the PUI indexer again. Which leads back to the "why does PUI indexing restart each time from 0" question. How does one add an enhancement request to have this reviewed and (perhaps) changed? Thanks, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://docs.google.com/uc?export=download&id=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0&revid=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Mon Mar 22 12:33:22 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Mon, 22 Mar 2021 12:33:22 -0400 Subject: [Archivesspace_Users_Group] PUI indexing issues In-Reply-To: References: <70A1CD16-C8BC-4899-935C-ECC8B784BD79@harvard.edu> Message-ID: Mark, Thanks. Some new information and ideas in there. I have our record_inheritance settings directly out of the box, which I assume are: # { # :property => 'notes', # :inherit_if => proc {|json| json.select {|j| j['type'] == 'accessrestrict'} }, # :inherit_directly => true # }, # { # :property => 'notes', # :inherit_if => proc {|json| json.select {|j| j['type'] == 'scopecontent'} }, # :inherit_directly => false # }, # { # :property => 'notes', # :inherit_if => proc {|json| json.select {|j| j['type'] == 'langmaterial'} }, # :inherit_directly => false # }, Setting the restricted notes to *false* might help. Is that a normal setting for others? I don't know what is appropriate or desired in terms of regular usage. As far as watching what is happening, I'd be rather happy to see any of the indexing complete to the point where I have to look at the database for further info. So far, the only thing that has *ever* completed was the Staff index once and then everything died when the database had the 'savings time' error. That data set *thought* that staff indexing was complete and only did PUI after that and never completed just PUI, so whether running one before the other would work for our data is a question mark. But that is worth a try as well. I've been keeping an eye on disk space and have not hit any limits there. I do see where backups could take up a lot of space over time. So will keep watching that going forward (assuming I ever get a completed solr index). Tom On Mon, Mar 22, 2021 at 12:05 PM Custer, Mark wrote: > Tom, > > Not sure if it will help (and not sure if you shared your config.rb file > in a previous message), but have you tried: > > - turning off the Solr backups during the re-indexing ( > https://github.com/archivesspace/archivesspace/blob/d207e8a7bb01c2b7b6f42ee5c0025d95f35ee7ae/common/config/config-defaults.rb#L76). > Just going back to Dave's suggestion about keeping an eye out on disk > space. > - updating the record inheritance settings and removing the bit about > inheriting scope and contents notes, which really bloats the index since > most finding aids won't have lower-level descriptive notes ( > https://github.com/archivesspace/archivesspace/blob/d207e8a7bb01c2b7b6f42ee5c0025d95f35ee7ae/common/config/config-defaults.rb#L411-L413). > For our record inheritance settings , > https://github.com/YaleArchivesSpace/aspace-deployment/blob/master/prod/config.rb#L204-L244), > we only inherit two notes currently: access notes and preferred citation > notes. > - Turning off the PUI indexer until the staff indexing is done, and > then turning the PUI indexer back on? > > When testing re-indexing locally, I usually bump up the two values that > Blake listed below, at least until I start getting Java heapspace errors > and don't' have any more RAM to allot to ASpace ?. But even just > waiting for the archival objects can take a while, depending on the > settings in your config.rb file. While waiting for a full re-index once > when things were re-indexing on a server that I didn't have access to, I'd > periodically look at the last archival object ID that was indexed, and then > run a database query to see how many more archival objects were left in > that repo, since a full re-index seems to go in order of the primary keys. > e.g. > > select count(*) from archival_object > where id > {archival_object id} > and repo_id = {repo id}; > > > That would at least give me a sense of how much longer it might be for all > the archival objects were left in one of our repos. > > As for the slowdown, after all the archival objects are indexed in a > repository, the next thing that happens (although it can take quite a > while) will be for all the tree indexes to be created and finally committed > to Solr. See > https://github.com/archivesspace/archivesspace/blob/82c4603fe22bf0fd06043974478d4caf26e1c646/indexer/app/lib/pui_indexer.rb#L136. > If i recall correctly, there won't be any specific mentions in the logs > about that, but after you get a message about all of the archival objects > being indexed in a specfic repository, you'll get another message about the > archival objects being indexed again sometime later, at which point the > full trees have been reindexed again, and then the indexer will be off to > the next repo (or record type, like classification records, etc.) > > > Mark > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom > Hanstra > *Sent:* Monday, March 22, 2021 11:21 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] PUI indexing issues > > Thanks, Blake. > > In your testing, how big was the repository that you were testing against. > Mine has "763368 archival_object records" and I consistently get into the > 670K range for staff and 575 range for PUI before things really slow down. > I'm now trying to really increase the Java settings to see if that will > help. So far, the problem is similar: real slow downs after zipping through > the first records. I'll also try some of the settings you have there to see > if fewer but larger threads work better than multiple smaller threads. > > Tom > > On Mon, Mar 22, 2021 at 10:52 AM Blake Carver > wrote: > > I did some experimenting this weekend, messing around with indexer speeds, > and found I could get it to succeed with the right indexer settings. I > think the answer is going to be "it depends" and you'll need to experiment > with what works on your set up with your data. I started with the defaults, > then dropped it to reallllly slow (1 thread 1 per), then just tried to dial > it up and down. The last one I tried worked fine, it was fast enough to > finish in a reasonable amount of time and didn't slow down or crash. Your > settings may not look like this, but here's something to try. > > AppConfig[:pui_indexer_records_per_thread] = 50 > AppConfig[:pui_indexer_thread_count] = 1 > > > So some extra detail for the mailing list archives... if your site keeps > crashing before the indexers finish and you're not seeing any particular > errors in the logs that make you think you have a problem with your data, > try turning the knobs on your indexer speed and see if that helps. > > It looks like maybe the indexer just eats up too much memory on BIG > records and having too many (too many being 15ish) threads running causes > it to crash. I know BIG is pretty subjective, if you have a bunch of > resources (maybe a few thousand) AND those resources all have ALLOTA (maybe > a few thousand) children with ALLOTA subjects/agents/notes/stuff, then you > might hit this problem. Seems like it's not the total number of resources, > it's probably because those resources are big/complex/deep. > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom > Hanstra > *Sent:* Thursday, March 18, 2021 11:24 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] PUI indexing issues > > Dave, > > Thanks for the suggestion, but unless there is some direct limitation > within Solr, that should not be an issue. My disk is at only about 50% of > capacity and Solr should be able to expand as needed. In my case, I don't > think there has been much addition to Solr because I'm reindexing records > which have been indexed already. So the deleted records are growing, but > not the overall number of records. My index is currently at about 6GB. > > Any other thoughts out there? > > Thanks, > Tom > > On Thu, Mar 18, 2021 at 10:51 AM Mayo, Dave wrote: > > This is a little bit of a shot in the dark, but have you looked at disk > space on whatever host Solr is resident on? (the ASpace server if you?re > not running an external one)? > > A thing we?ve hit a couple times is that Solr, at least in some > configurations, needs substantial headroom on disk to perform well ? I > think it?s related to how it builds and maintains the index? So it might > be worth looking to see if Solr is filling up the disk enough that it can?t > efficiently handle itself. > > > > -- > > Dave Mayo (he/him) > > Senior Digital Library Software Engineer > Harvard University > HUIT > LTS > > > > *From: * on > behalf of Tom Hanstra > *Reply-To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Wednesday, March 17, 2021 at 11:43 AM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] PUI indexing issues > > > > > > > > - What really bothers me is the slowdown. That indicates to me that some > resource is being lost along the way. Anyone have thoughts on what that > might be? > > > > > > Just to follow up on my earlier post, I did get even lower numbers from > Blake to try based upon what he used for our hosted account. But I'm seeing > the same pattern in terms of slowdowns regarding the number of records that > get processed/hour. Is this typical? Is it just hitting records that have > more work to be done? Or do I still have a resource issue. > > > > I note that the number of docs in Solr has not changed at all throughout > the last couple of attempts, which again leads me to believe it has already > handled these records (at least once) before and thus there is no more > indexing to really be done with the records which it is running through > the PUI indexer again. Which leads back to the "why does PUI indexing > restart each time from 0" question. How does one add an enhancement request > to have this reviewed and (perhaps) changed? > > > > Thanks, > > Tom > > > > -- > > *Tom Hanstra* > > *Sr. Systems Administrator* > > hanstra at nd.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From katie.nash at wisc.edu Mon Mar 22 16:51:46 2021 From: katie.nash at wisc.edu (Katie Nash) Date: Mon, 22 Mar 2021 20:51:46 +0000 Subject: [Archivesspace_Users_Group] Disappeared Accession Record Message-ID: Hello colleagues, We've been creating accession records for several years now, and had the strangest thing happen recently. We created an accession record, added an instance, and saved it. When we went to search for it using the identifier, we received a message that "No Records Found", and the same thing happened when we searched the barcode for the top container. When we tried to create a new accession record using the same identifier, the system said the identifier is already in use. We've been unable to locate this accession record! Any idea where it could be hiding? I've been using ASpace for several years and never had this happen, so I'm at a loss. Thanks for any guidance! Worst case scenario we simply create a new accession record (for this one box collection!) with a new identifier. Best wishes, Katie Katie Nash | University Archivist and Head of UW Archives University of Wisconsin-Madison Libraries 425 Steenbock Library | 550 Babcock Dr. Madison, WI 53706 1-608-265-1988 Pronouns: she/her/hers Tell us your COVID-19 story! -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Mon Mar 22 17:00:06 2021 From: buschedw at msu.edu (Busch, Ed) Date: Mon, 22 Mar 2021 21:00:06 +0000 Subject: [Archivesspace_Users_Group] Disappeared Accession Record Message-ID: I would bet you need to do a re-index. We?ve seen things like that in the past occasionally. Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his From: on behalf of Katie Nash Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Monday, March 22, 2021 at 4:51 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Disappeared Accession Record Hello colleagues, We've been creating accession records for several years now, and had the strangest thing happen recently. We created an accession record, added an instance, and saved it. When we went to search for it using the identifier, we received a message that "No Records Found", and the same thing happened when we searched the barcode for the top container. When we tried to create a new accession record using the same identifier, the system said the identifier is already in use. We've been unable to locate this accession record! Any idea where it could be hiding? I've been using ASpace for several years and never had this happen, so I'm at a loss. Thanks for any guidance! Worst case scenario we simply create a new accession record (for this one box collection!) with a new identifier. Best wishes, Katie Katie Nash | University Archivist and Head of UW Archives University of Wisconsin-Madison Libraries 425 Steenbock Library | 550 Babcock Dr. Madison, WI 53706 1-608-265-1988 Pronouns: she/her/hers Tell us your COVID-19 story! -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Mon Mar 22 19:20:51 2021 From: james at hudmol.com (James Bullen) Date: Tue, 23 Mar 2021 10:20:51 +1100 Subject: [Archivesspace_Users_Group] Disappeared Accession Record In-Reply-To: References: Message-ID: <24319A4B-8C64-45D2-A6EF-236FA711298F@hudmol.com> Hi Katie, That looks suspiciously like a bug I?ve seen on v2.8.1 - not sure if it afflicts any earlier versions. I assume it has been noted elsewhere and documented because it?s pretty nasty. If an accession has an instance with a linked top container, its json looks like this: "top_container": { "ref": [ "SubContainer", "TopContainer" ] } That ref value should be the uri of the top container (not an array of strings - classnames?). When the indexer retrieves such an accession it tries to resolve the top container and blows up because it is not expecting an array. The test would be to remove the instance and see if it re-appears in search results. I assume this will be fixed in the next release. Cheers, James > On Mar 23, 2021, at 7:51 AM, Katie Nash wrote: > > Hello colleagues, > > We've been creating accession records for several years now, and had the strangest thing happen recently. We created an accession record, added an instance, and saved it. When we went to search for it using the identifier, we received a message that "No Records Found", and the same thing happened when we searched the barcode for the top container. When we tried to create a new accession record using the same identifier, the system said the identifier is already in use. We've been unable to locate this accession record! Any idea where it could be hiding? I've been using ASpace for several years and never had this happen, so I'm at a loss. > > Thanks for any guidance! Worst case scenario we simply create a new accession record (for this one box collection!) with a new identifier. > > Best wishes, > Katie > > Katie Nash | University Archivist and Head of UW Archives > University of Wisconsin-Madison Libraries > 425 Steenbock Library | 550 Babcock Dr. > Madison, WI 53706 > 1-608-265-1988 > Pronouns: she/her/hers > Tell us your COVID-19 story! > _______________________________________________ > 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 trthorn2 at ncsu.edu Tue Mar 23 09:50:04 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Tue, 23 Mar 2021 09:50:04 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace Technical Documentation Discussion at Online Forum Message-ID: As part of the ArchivesSpace Online Forum on March 30, members from the ArchivesSpace Technical Advisory Council will be hosting a discussion session on the various technical documentation sources available to implementers and developers. Please join us with any questions you have about the existing technical documentation, or ideas for how to improve it. The time slot for this session is on *Tuesday March 30 from 2:45 - 3:15 PM EDT (6:45 - 7:15pm UTC)*. A full agenda and more info can be found here: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2146992129/ArchivesSpace+Online+Forum+2021 Registration for the discussion sessions is already full, but there is a waitlist . Hope to see you there! -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Wed Mar 24 09:25:24 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Wed, 24 Mar 2021 09:25:24 -0400 Subject: [Archivesspace_Users_Group] Indexed - but still some issues Message-ID: Whew! Ok, my logs now say that both Staff and PUI have been indexed. So I got that far finally. Thanks to both Blake and Mark for suggestions. The combination of staggering Staff and then PUI indexing as well as moving to 1 thread seems to have helped. So, I am now further than I've been yet, at least based upon the logs. But I still have something not working properly, because when I do a search and find output, nothing is coming up when I try to look at the found record. I get the error: *We're sorry, but something went wrong.* When I've seen that in other applications, it has been a rails issue. Not sure if that is what is happening here as well. Also, the "Found In" links for the records come back with: *The record you've tried to access does not exist or may have been removed.The record you've tried to access does not exist or may have been removed.* The logs are prolific, but I don't see anything right off to tell me what is missing/broken. What should I be looking for? Once I get indexing to the point where they are both showing: I, [2021-03-24T09:17:08.655860 #10795] INFO -- : Thread-2868: Staff Indexer [2021-03-24 09:17:08 -0400] Index round complete I, [2021-03-24T09:17:18.314866 #10795] INFO -- : Thread-3200: PUI Indexer [2021-03-24 09:17:18 -0400] Index round complete Is there more to be done behind the scenes? Do I need to restart something? Are there log entries that I should be looking for to show what is going on? Another possible red flag is that when I do searches, the results are different than what I see on our hosted site. Not sure why that might be either. Thanks to those who have helped me get this far. Hopefully it is not going to be overly difficult to get the rest of the way... Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Wed Mar 24 09:55:24 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Wed, 24 Mar 2021 13:55:24 +0000 Subject: [Archivesspace_Users_Group] Indexed - but still some issues In-Reply-To: References: Message-ID: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> Tom Hanstra wrote on 2021-03-24 09:25:24: > So, I am now further than I've been yet, at least based upon the logs. But > I still have something not working properly, because when I do a search and > find output, nothing is coming up when I try to look at the found record. I > get the error: > > *We're sorry, but something went wrong.* > > When I've seen that in other applications, it has been a rails issue. Not > sure if that is what is happening here as well. This error should have a corresponding event with at least WARNING level in the frontend/public log (depending on which gave you the error) that you can correlate by event time. > Also, the "Found In" links for the records come back with: > > *The record you've tried to access does not exist or may have been > removed.The record you've tried to access does not exist or may have been > removed.* This would point to the fact that your database and index are not in sync. Given your struggles with indexing I'm starting to wonder if you're reading from the Solr instance you're writing to. p From hanstra at nd.edu Wed Mar 24 11:42:58 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Wed, 24 Mar 2021 11:42:58 -0400 Subject: [Archivesspace_Users_Group] Indexed - but still some issues In-Reply-To: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> References: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> Message-ID: Hmmm. So I finally tracked the issue down to my Java settings. For some reason, before/during indexing, Java settings of: ASPACE_JAVA_XMX="-Xmx8192m" ASPACE_JAVA_XSS="-Xss4g" worked fine. But, once indexing was complete, those settings were somehow unusable. Staff connection would not work, searches failed, etc. But when I crank down the thread size to: ASPACE_JAVA_XMX="-Xmx8192m" ASPACE_JAVA_XSS="-Xss1g" everything goes back to working. There was a server reboot in there as well as numerous restarts with config.rb changes and that was the only change that I found could address the issues. Through a number of restarts, there was nothing in the logs to indicate the issue. Finally got an error that suggested Java space issues and tried the lower value and things now work (as far as I've tested at least). Quite a journey so far... Tom On Wed, Mar 24, 2021 at 9:54 AM Peter Heiner wrote: > Tom Hanstra wrote on 2021-03-24 09:25:24: > > So, I am now further than I've been yet, at least based upon the logs. > But > > I still have something not working properly, because when I do a search > and > > find output, nothing is coming up when I try to look at the found > record. I > > get the error: > > > > *We're sorry, but something went wrong.* > > > > When I've seen that in other applications, it has been a rails issue. Not > > sure if that is what is happening here as well. > > This error should have a corresponding event with at least WARNING level in > the frontend/public log (depending on which gave you the error) that you > can > correlate by event time. > > > Also, the "Found In" links for the records come back with: > > > > *The record you've tried to access does not exist or may have been > > removed.The record you've tried to access does not exist or may have been > > removed.* > > This would point to the fact that your database and index are not in sync. > Given your struggles with indexing I'm starting to wonder if you're reading > from the Solr instance you're writing to. > > p > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomsonl at tulane.edu Wed Mar 24 11:49:14 2021 From: thomsonl at tulane.edu (Thomson, Laura J) Date: Wed, 24 Mar 2021 15:49:14 +0000 Subject: [Archivesspace_Users_Group] Spam coming through the Request Button Message-ID: Hello all, We are experiencing an increase in spam coming through the request button in ArchivesSpace's public interface. Has anyone found a solution? I did a search of the listserv archives and really didn't come up with a solution beyond disabling the request button. Best, LAURA THOMSON, MLS, MA Director of Archives Division (504) 862-3224 (504) 862-3226 thomsonl at tulane.edu Amistad Research Center Tulane University Tilton Hall 6823 St. Charles Avenue New Orleans, LA 70118 [cid:433ee468-2827-42da-991b-4bc6f33d5b00] [cid:69dd2e39-5371-49db-8da6-530be9a335b9] [cid:f8631bdf-2f31-48e4-ad5f-d64b25b48f6a] [cid:f2b3eddc-7ffa-433b-b8f9-c958d33b9e48] Amistad is here to serve you. Let?s Connect! [cid:031b00a9-f85b-407f-8b97-61f605892ec9] [cid:cb20c308-70f1-4cdf-bd28-8bec8907ad5b] [cid:81f1e89b-41fc-4b0b-a760-9f0cf11937d1] [cid:a068a797-8c59-4be9-8624-d8ffc435b64e] [cid:c57b2c8e-407d-4379-9235-98a036bea8e3] [cid:93d11d11-5379-4896-9512-434fa7fbdf27] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-twrrx3u1.png Type: image/png Size: 316 bytes Desc: Outlook-twrrx3u1.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yx00kpph.png Type: image/png Size: 431 bytes Desc: Outlook-yx00kpph.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-4rjgwgzo.png Type: image/png Size: 360 bytes Desc: Outlook-4rjgwgzo.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-ecufwdqv.png Type: image/png Size: 469 bytes Desc: Outlook-ecufwdqv.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-cxumir41.png Type: image/png Size: 3038 bytes Desc: Outlook-cxumir41.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-hxck2m2e.png Type: image/png Size: 4477 bytes Desc: Outlook-hxck2m2e.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-ls5z2uve.png Type: image/png Size: 4056 bytes Desc: Outlook-ls5z2uve.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dnnasbzo.png Type: image/png Size: 44879 bytes Desc: Outlook-dnnasbzo.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yws2izst.png Type: image/png Size: 46334 bytes Desc: Outlook-yws2izst.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-sua0kgiz.png Type: image/png Size: 44524 bytes Desc: Outlook-sua0kgiz.png URL: From jgd1 at williams.edu Wed Mar 24 11:58:21 2021 From: jgd1 at williams.edu (Jessika Drmacich) Date: Wed, 24 Mar 2021 11:58:21 -0400 Subject: [Archivesspace_Users_Group] Spam bombed Message-ID: Hi all, Our ArchivesSpace request form is getting spam bombed. Does anyone have a way to cease this? *Example below Thanks, everyone! My very best, Jessika Request for Civil War papers of Samuel E. Pittman, Lt. Col. New Request Request received: 2021-03-18 16:23:46 -0400 Requester*Name: *iwtuwovixuwac *Email: *vigezi at asfuy.jonjamail.com *Date:* *Notes for Staff:* [url=http://slkjfdf.net/]Amoxicillin[/url] Buy Amoxicillin woe.abev.archivesspace.williams.edu.eck.wf http://slkjfdf.net/ Record Requesteduser_name: iwtuwovixuwac user_email: vigezi at asfuy.jonjamail.com date: note: [url=http://slkjfdf.net/]Amoxicillin[/url] Buy Amoxicillin woe.abev.archivesspace.williams.edu.eck.wf http://slkjfdf.net/ title: Civil War papers of Samuel E. Pittman, Lt. Col. identifier: Am-Mss-Pittman cite: Civil War Papers of Samuel E. Pittman, Lt. Col. Chapin Library, Williams College. https://archivesspace.williams.edu/repositories/4/resources/312 Accessed March 18, 2021. request_uri: /repositories/4/resources/312 resource_name: resource_id: repo_name: Chapin Library hierarchy: restrict: The Civil War Papers of Samuel E. Pittman, Lt. Col., are open for research. Researchers are encouraged to contact Special Collections staff prior to a visit. machine: container: top_container_url: barcode: location_title: location_url: ["user_name: iwtuwovixuwac", "user_email: vigezi at asfuy.jonjamail.com", "date: ", "note: [url=http://slkjfdf.net/]Amoxicillin[/url] Buy Amoxicillin woe.abev.archivesspace.williams.edu.eck.wf http://slkjfdf.net/", "title: Civil War papers of Samuel E. Pittman, Lt. Col.", "identifier: Am-Mss-Pittman", "cite: Civil War Papers of Samuel E. Pittman, Lt. Col. Chapin Library, Williams College. https://archivesspace.williams.edu/repositories/4/resources/312 Accessed March 18, 2021.", "request_uri: /repositories/4/resources/312", "resource_name: ", "resource_id: ", "repo_name: Chapin Library", "hierarchy: ", "restrict: The Civil War Papers of Samuel E. Pittman, Lt. Col., are open for research. Researchers are encouraged to contact Special Collections staff prior to a visit.", "machine: ", "container:", "top_container_url:", "barcode:", "location_title:", "location_url:"] *Jessika Drmacich * *Records Manager & Digital Resources Archivist * *Williams College * *Libraries/ **Special Collections* *413-597-4725 (o)* *she/her/hers* *Please Note: Due to COVID-19 library services have changed. See **the library?s webpage for information on how to access collections and services. I am working both from home and my office in special collections and I will be checking email regularly. I?m also available for in-person appointments and virtual consultations via GoogleMeet.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgd1 at williams.edu Wed Mar 24 12:02:30 2021 From: jgd1 at williams.edu (Jessika Drmacich) Date: Wed, 24 Mar 2021 12:02:30 -0400 Subject: [Archivesspace_Users_Group] Spam coming through the Request Button In-Reply-To: References: Message-ID: I will be following this! Same here. *Jessika Drmacich * *Records Manager & Digital Resources Archivist * *Williams College * *Libraries/ **Special Collections* *413-597-4725 (o)* *she/her/hers* *Please Note: Due to COVID-19 library services have changed. See **the library?s webpage for information on how to access collections and services. I am working both from home and my office in special collections and I will be checking email regularly. I?m also available for in-person appointments and virtual consultations via GoogleMeet.* On Wed, Mar 24, 2021 at 11:49 AM Thomson, Laura J wrote: > Hello all, > > We are experiencing an increase in spam coming through the request button > in ArchivesSpace's public interface. Has anyone found a solution? > > I did a search of the listserv archives and really didn't come up with a > solution beyond disabling the request button. > > Best, > > > *LAURA THOMSON, MLS, MA* > > > > *Director of Archives Division* > > > > (504) 862-3224 > > (504) 862-3226 > > > > thomsonl at tulane.edu > > > > > *Amistad Research Center *Tulane University > > Tilton Hall > > 6823 St. Charles Avenue > > New Orleans, LA 70118 > > > > > > > > > > > *Amistad is here to serve you. Let?s Connect!* > > > > > > > > > > > > > > _______________________________________________ > 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: Outlook-twrrx3u1.png Type: image/png Size: 316 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yx00kpph.png Type: image/png Size: 431 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-4rjgwgzo.png Type: image/png Size: 360 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-ecufwdqv.png Type: image/png Size: 469 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-cxumir41.png Type: image/png Size: 3038 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-hxck2m2e.png Type: image/png Size: 4477 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-ls5z2uve.png Type: image/png Size: 4056 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-dnnasbzo.png Type: image/png Size: 44879 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yws2izst.png Type: image/png Size: 46334 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-sua0kgiz.png Type: image/png Size: 44524 bytes Desc: not available URL: From mark.cooper at lyrasis.org Wed Mar 24 12:15:24 2021 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Wed, 24 Mar 2021 16:15:24 +0000 Subject: [Archivesspace_Users_Group] Spam coming through the Request Button In-Reply-To: References: , Message-ID: You can try the reCAPTCHA plugin: https://github.com/archivesspace-plugins/aspace-recaptcha Best, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Jessika Drmacich Date: Wednesday, March 24, 2021 at 9:03 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Spam coming through the Request Button I will be following this! Same here. Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries/ Special Collections 413-597-4725 (o) she/her/hers Please Note: Due to COVID-19 library services have changed. See the library?s webpage for information on how to access collections and services. I am working both from home and my office in special collections and I will be checking email regularly. I?m also available for in-person appointments and virtual consultations via GoogleMeet. On Wed, Mar 24, 2021 at 11:49 AM Thomson, Laura J > wrote: Hello all, We are experiencing an increase in spam coming through the request button in ArchivesSpace's public interface. Has anyone found a solution? I did a search of the listserv archives and really didn't come up with a solution beyond disabling the request button. Best, LAURA THOMSON, MLS, MA Director of Archives Division (504) 862-3224 (504) 862-3226 thomsonl at tulane.edu Amistad Research Center Tulane University Tilton Hall 6823 St. Charles Avenue New Orleans, LA 70118 [cid:image001.png at 01D7208E.33992B80] [cid:image002.png at 01D7208E.33992B80] [cid:image003.png at 01D7208E.33992B80] [cid:image004.png at 01D7208E.33992B80] Amistad is here to serve you. Let?s Connect! [cid:image005.png at 01D7208E.33992B80] [cid:image006.png at 01D7208E.33992B80] [cid:image007.png at 01D7208E.33992B80] [cid:image008.png at 01D7208E.33992B80] [cid:image009.png at 01D7208E.33992B80] [cid:image010.png at 01D7208E.33992B80] _______________________________________________ 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: 317 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 432 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 361 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 470 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 3039 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 4478 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 4057 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 44880 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 46335 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 44525 bytes Desc: image010.png URL: From bnewberry at auctr.edu Wed Mar 24 12:16:57 2021 From: bnewberry at auctr.edu (Brittany Newberry) Date: Wed, 24 Mar 2021 16:16:57 +0000 Subject: [Archivesspace_Users_Group] Spam coming through the Request Button In-Reply-To: References: , Message-ID: <59AE3EF1920BD744B9A471EB4854C3510497CA47@RWWLEXCHSRV01.RWWL-MAIN.AUCTR.EDU> We installed the reCAPTCHA plugin and it has worked to stop spam for us. Brittany Brittany Newberry Processing Archivist Archives Research Center Atlanta University Center Robert W. Woodruff Library 111 James P. Brawley Drive, SW Atlanta, GA 30314 (404)978-2019 bnewberry at auctr.edu "We will always provide service that exceeds the customer's expectation...Because we care!" From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mark Cooper Sent: Wednesday, March 24, 2021 12:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Spam coming through the Request Button You can try the reCAPTCHA plugin: https://github.com/archivesspace-plugins/aspace-recaptcha Best, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Jessika Drmacich > Date: Wednesday, March 24, 2021 at 9:03 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Spam coming through the Request Button I will be following this! Same here. Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries/ Special Collections 413-597-4725 (o) she/her/hers Please Note: Due to COVID-19 library services have changed. See the library's webpage for information on how to access collections and services. I am working both from home and my office in special collections and I will be checking email regularly. I'm also available for in-person appointments and virtual consultations via GoogleMeet. On Wed, Mar 24, 2021 at 11:49 AM Thomson, Laura J > wrote: Hello all, We are experiencing an increase in spam coming through the request button in ArchivesSpace's public interface. Has anyone found a solution? I did a search of the listserv archives and really didn't come up with a solution beyond disabling the request button. Best, LAURA THOMSON, MLS, MA Director of Archives Division (504) 862-3224 (504) 862-3226 thomsonl at tulane.edu Amistad Research Center Tulane University Tilton Hall 6823 St. Charles Avenue New Orleans, LA 70118 [cid:image001.png at 01D720A7.94DD3030] [cid:image002.png at 01D720A7.94DD3030] [cid:image003.png at 01D720A7.94DD3030] [cid:image004.png at 01D720A7.94DD3030] Amistad is here to serve you. Let's Connect! [cid:image005.png at 01D720A7.94DD3030] [cid:image006.png at 01D720A7.94DD3030] [cid:image007.png at 01D720A7.94DD3030] [cid:image008.png at 01D720A7.94DD3030] [cid:image009.png at 01D720A7.94DD3030] [cid:image010.png at 01D720A7.94DD3030] _______________________________________________ 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: 317 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 432 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 361 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 470 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 3039 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 4478 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 4057 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 44880 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 46335 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 44525 bytes Desc: image010.png URL: From mcallahan at smith.edu Wed Mar 24 12:38:17 2021 From: mcallahan at smith.edu (Maureen Cresci Callahan) Date: Wed, 24 Mar 2021 12:38:17 -0400 Subject: [Archivesspace_Users_Group] Spam coming through the Request Button In-Reply-To: <59AE3EF1920BD744B9A471EB4854C3510497CA47@RWWLEXCHSRV01.RWWL-MAIN.AUCTR.EDU> References: <59AE3EF1920BD744B9A471EB4854C3510497CA47@RWWLEXCHSRV01.RWWL-MAIN.AUCTR.EDU> Message-ID: Spam is super annoying and I'm so happy to see that there are good solutions. But, for folks looking at implementing a captcha option, I want to recommend this website which discusses 1. the ways that the reCaptcha service helps Google violate privacy and leverage our users to make their products better so that they can sell them back to us 2. alternative captcha approaches https://switching.software/replace/google-recaptcha/ Just something to consider! MCC On Wed, Mar 24, 2021 at 12:17 PM Brittany Newberry wrote: > We installed the reCAPTCHA plugin and it has worked to stop spam for us. > > > > Brittany > > > > *Brittany Newberry* > > Processing Archivist > > Archives Research Center > > Atlanta University Center Robert W. Woodruff Library > > 111 James P. Brawley Drive, SW > > Atlanta, GA 30314 > > (404)978-2019 > > bnewberry at auctr.edu > > > > ?*We will always provide service that exceeds the customer?s > expectation?Because we care!?* > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Mark > Cooper > *Sent:* Wednesday, March 24, 2021 12:15 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Spam coming through the > Request Button > > > > You can try the reCAPTCHA plugin: > > > > https://github.com/archivesspace-plugins/aspace-recaptcha > > > > Best, > > Mark > > > > *From: *archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Jessika Drmacich > *Date: *Wednesday, March 24, 2021 at 9:03 AM > *To: *Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Spam coming through the > Request Button > > I will be following this! Same here. > > > > > > *Jessika Drmacich * > > *Records Manager & Digital Resources Archivist * > > *Williams College * > > *Libraries/ Special Collections* > > *413-597-4725 (o)* > > *she/her/hers* > > > > *Please Note: Due to COVID-19 library services have changed. See the > library?s webpage > for > information on how to access collections and services. I am working both > from home and my office in special collections and I will be checking email > regularly. I?m also available for in-person appointments and virtual > consultations via GoogleMeet.* > > > > > > On Wed, Mar 24, 2021 at 11:49 AM Thomson, Laura J > wrote: > > Hello all, > > > > We are experiencing an increase in spam coming through the request button > in ArchivesSpace's public interface. Has anyone found a solution? > > > > I did a search of the listserv archives and really didn't come up with a > solution beyond disabling the request button. > > > > Best, > > > > > > *LAURA THOMSON, MLS, MA* > > > > *Director of Archives Division* > > > > (504) 862-3224 > > (504) 862-3226 > > > > thomsonl at tulane.edu > > > > > *Amistad Research Center *Tulane University > > Tilton Hall > > 6823 St. Charles Avenue > > New Orleans, LA 70118 > > > > > > > > > > > *Amistad is here to serve you. Let?s Connect!* > > > > > > > > > > > > > > > > _______________________________________________ > 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 > -- *Maureen Cresci Callahan* Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 voicemail: 413 585 2981 email: mcallahan at smith.edu videoconference: https://smith.zoom.us/my/maureen.callahan pronouns : she/her/hers Information about the Sophia Smith Collection of Women's history *Please note:* In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website . -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 317 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 432 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 361 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 470 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 3039 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 4478 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 4057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 44880 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 46335 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 44525 bytes Desc: not available URL: From trthorn2 at ncsu.edu Wed Mar 24 12:55:26 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Wed, 24 Mar 2021 12:55:26 -0400 Subject: [Archivesspace_Users_Group] Indexed - but still some issues In-Reply-To: References: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> Message-ID: I'm doing this exact thing right now and I wanted to confirm that the 'g' here shouldn't be an 'm': ASPACE_JAVA_XSS="-Xss1g" The default looks to be: ASPACE_JAVA_XSS="-Xss2m" https://github.com/archivesspace/archivesspace/blob/master/launcher/archivesspace.sh#L105 On Wed, Mar 24, 2021 at 11:43 AM Tom Hanstra wrote: > Hmmm. So I finally tracked the issue down to my Java settings. For some > reason, before/during indexing, Java settings of: > > ASPACE_JAVA_XMX="-Xmx8192m" > ASPACE_JAVA_XSS="-Xss4g" > > worked fine. But, once indexing was complete, those settings were somehow > unusable. Staff connection would not work, searches failed, etc. > > But when I crank down the thread size to: > > ASPACE_JAVA_XMX="-Xmx8192m" > ASPACE_JAVA_XSS="-Xss1g" > > everything goes back to working. There was a server reboot in there as > well as numerous restarts with config.rb changes and that was the only > change that I found could address the issues. Through a number of restarts, > there was nothing in the logs to indicate the issue. Finally got an error > that suggested Java space issues and tried the lower value and things now > work (as far as I've tested at least). > > Quite a journey so far... > > Tom > > > On Wed, Mar 24, 2021 at 9:54 AM Peter Heiner wrote: > >> Tom Hanstra wrote on 2021-03-24 09:25:24: >> > So, I am now further than I've been yet, at least based upon the logs. >> But >> > I still have something not working properly, because when I do a search >> and >> > find output, nothing is coming up when I try to look at the found >> record. I >> > get the error: >> > >> > *We're sorry, but something went wrong.* >> > >> > When I've seen that in other applications, it has been a rails issue. >> Not >> > sure if that is what is happening here as well. >> >> This error should have a corresponding event with at least WARNING level >> in >> the frontend/public log (depending on which gave you the error) that you >> can >> correlate by event time. >> >> > Also, the "Found In" links for the records come back with: >> > >> > *The record you've tried to access does not exist or may have been >> > removed.The record you've tried to access does not exist or may have >> been >> > removed.* >> >> This would point to the fact that your database and index are not in sync. >> Given your struggles with indexing I'm starting to wonder if you're >> reading >> from the Solr instance you're writing to. >> >> p >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Wed Mar 24 14:45:29 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Wed, 24 Mar 2021 14:45:29 -0400 Subject: [Archivesspace_Users_Group] More indexing woes? Message-ID: I have two instances which have successfully completed indexing. And with the lowering of the Jave thread size, searches and other access is now working. But... When I choose the "Repositories" button at the top of the Public interface, I get an error message: E, [2021-03-24T13:41:12.798448 #3141] ERROR -- : [d9a19e62-859c-4ddb-b73f-7985974b1f4c] No repository records found! and get nothing in terms of repositories. Also, I'm not getting nearly enough Collections. Our hosted version has 1539 collections. My server has only 295. >From the Staff side, I'm getting nothing when doing any "Browse" options. Each of the pulldowns results in: "No records found". Searches in the Staff interface do return values. Do I possibly have some other configuration settings not set properly? Or did my indexing not *really* work and I need to restart indexing yet again? Again, my lack of experience may be an issue, but things still don't seem to work. Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanstra at nd.edu Wed Mar 24 15:06:30 2021 From: hanstra at nd.edu (Tom Hanstra) Date: Wed, 24 Mar 2021 15:06:30 -0400 Subject: [Archivesspace_Users_Group] Indexed - but still some issues In-Reply-To: References: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> Message-ID: My understand/reading regarding this setting is that it is the thread size for Java, and has to be big enough to handle the work but cannot be too big either. The default of 2m seems very low. I have been working with the 1g size lately but am not sure that is optimal either. I'd be curious to know if there are optimal numbers that people have found useful. Tom On Wed, Mar 24, 2021 at 12:55 PM Trevor Thornton wrote: > I'm doing this exact thing right now and I wanted to confirm that the 'g' > here shouldn't be an 'm': > ASPACE_JAVA_XSS="-Xss1g" > > The default looks to be: > ASPACE_JAVA_XSS="-Xss2m" > > https://github.com/archivesspace/archivesspace/blob/master/launcher/archivesspace.sh#L105 > > On Wed, Mar 24, 2021 at 11:43 AM Tom Hanstra wrote: > >> Hmmm. So I finally tracked the issue down to my Java settings. For some >> reason, before/during indexing, Java settings of: >> >> ASPACE_JAVA_XMX="-Xmx8192m" >> ASPACE_JAVA_XSS="-Xss4g" >> >> worked fine. But, once indexing was complete, those settings were somehow >> unusable. Staff connection would not work, searches failed, etc. >> >> But when I crank down the thread size to: >> >> ASPACE_JAVA_XMX="-Xmx8192m" >> ASPACE_JAVA_XSS="-Xss1g" >> >> everything goes back to working. There was a server reboot in there as >> well as numerous restarts with config.rb changes and that was the only >> change that I found could address the issues. Through a number of restarts, >> there was nothing in the logs to indicate the issue. Finally got an error >> that suggested Java space issues and tried the lower value and things now >> work (as far as I've tested at least). >> >> Quite a journey so far... >> >> Tom >> >> >> On Wed, Mar 24, 2021 at 9:54 AM Peter Heiner wrote: >> >>> Tom Hanstra wrote on 2021-03-24 09:25:24: >>> > So, I am now further than I've been yet, at least based upon the logs. >>> But >>> > I still have something not working properly, because when I do a >>> search and >>> > find output, nothing is coming up when I try to look at the found >>> record. I >>> > get the error: >>> > >>> > *We're sorry, but something went wrong.* >>> > >>> > When I've seen that in other applications, it has been a rails issue. >>> Not >>> > sure if that is what is happening here as well. >>> >>> This error should have a corresponding event with at least WARNING level >>> in >>> the frontend/public log (depending on which gave you the error) that you >>> can >>> correlate by event time. >>> >>> > Also, the "Found In" links for the records come back with: >>> > >>> > *The record you've tried to access does not exist or may have been >>> > removed.The record you've tried to access does not exist or may have >>> been >>> > removed.* >>> >>> This would point to the fact that your database and index are not in >>> sync. >>> Given your struggles with indexing I'm starting to wonder if you're >>> reading >>> from the Solr instance you're writing to. >>> >>> p >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> >> >> -- >> *Tom Hanstra* >> *Sr. Systems Administrator* >> hanstra at nd.edu >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Trevor Thornton > Applications Developer, Digital Library Initiatives > North Carolina State University Libraries > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From robinsa1 at newschool.edu Wed Mar 24 15:40:31 2021 From: robinsa1 at newschool.edu (Anna Robinson-Sweet) Date: Wed, 24 Mar 2021 15:40:31 -0400 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? Message-ID: Hello, We just noticed what appears to be a bug in applying filters to search results in the PUI. When we run a search on a phrase that is more than one word, and then apply a filter to those results, we get more results in the "filtered" search than in the initial one. When we remove the filter, there are even more results than either the initial or filtered search.This only happens when the initial search phrase is more than one word and is not in quotes, suggesting that the filter turns the initial search from an "and" query to an "or" query, or something along these lines. Here is an example of the problem: First search for the phrase fashion designers (without quotes) returns 113 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search When I add a date filer 1950-1960 I get 393 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search And when I remove the filter I get 5,998 results: https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= Has anyone else encountered this or have any ideas what may be causing the problem? Thanks, Anna -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [image: THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpaquette at smith.edu Wed Mar 24 15:56:28 2021 From: mpaquette at smith.edu (Michelle Paquette) Date: Wed, 24 Mar 2021 15:56:28 -0400 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? In-Reply-To: References: Message-ID: Hi Anna, I'm wondering if something is happening to the default AND boolean - if you search fashion OR designers in the first place you're getting 5998 results, so it seems when you remove the date filter it switches from an AND to an OR search. Michelle On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet wrote: > Hello, > > We just noticed what appears to be a bug in applying filters to search > results in the PUI. When we run a search on a phrase that is more than one > word, and then apply a filter to those results, we get more results in the > "filtered" search than in the initial one. When we remove the filter, there > are even more results than either the initial or filtered search.This only > happens when the initial search phrase is more than one word and is not in > quotes, suggesting that the filter turns the initial search from an "and" > query to an "or" query, or something along these lines. > > Here is an example of the problem: > First search for the phrase fashion designers (without quotes) returns 113 > results: > https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search > > When I add a date filer 1950-1960 I get 393 results: > https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search > > And when I remove the filter I get 5,998 results: > https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= > > Has anyone else encountered this or have any ideas what may be causing the > problem? > > Thanks, > Anna > > -- > > ANNA ROBINSON-SWEET (she/her) > > ASSOCIATE ARCHIVIST > THE NEW SCHOOL > ARCHIVES & SPECIAL COLLECTIONS > > 66 FIFTH AVENUE, NEW YORK, NY 10011 > robinsa1 at newschool.edu > > T 212-229-2942 3375 > > archives.newschool.edu > > [image: THE NEW SCHOOL] > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Michelle Paquette (she/her) Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu Please note: In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website . -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpaquette at smith.edu Wed Mar 24 16:00:17 2021 From: mpaquette at smith.edu (Michelle Paquette) Date: Wed, 24 Mar 2021 16:00:17 -0400 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? In-Reply-To: References: Message-ID: Ha, and actually now I've tested it in my own system and this seems to be the case that when adding the date filter it switches to OR. Doesn't seem to be happening with any other filters though. Blake, any insight? On Wed, Mar 24, 2021 at 3:56 PM Michelle Paquette wrote: > Hi Anna, > > I'm wondering if something is happening to the default AND boolean - if > you search fashion OR designers in the first place you're getting 5998 > results, so it seems when you remove the date filter it switches from an > AND to an OR search. > > Michelle > > On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet < > robinsa1 at newschool.edu> wrote: > >> Hello, >> >> We just noticed what appears to be a bug in applying filters to search >> results in the PUI. When we run a search on a phrase that is more than one >> word, and then apply a filter to those results, we get more results in the >> "filtered" search than in the initial one. When we remove the filter, there >> are even more results than either the initial or filtered search.This only >> happens when the initial search phrase is more than one word and is not in >> quotes, suggesting that the filter turns the initial search from an "and" >> query to an "or" query, or something along these lines. >> >> Here is an example of the problem: >> First search for the phrase fashion designers (without quotes) returns >> 113 results: >> https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search >> >> When I add a date filer 1950-1960 I get 393 results: >> https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search >> >> And when I remove the filter I get 5,998 results: >> https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= >> >> Has anyone else encountered this or have any ideas what may be causing >> the problem? >> >> Thanks, >> Anna >> >> -- >> >> ANNA ROBINSON-SWEET (she/her) >> >> ASSOCIATE ARCHIVIST >> THE NEW SCHOOL >> ARCHIVES & SPECIAL COLLECTIONS >> >> 66 FIFTH AVENUE, NEW YORK, NY 10011 >> robinsa1 at newschool.edu >> >> T 212-229-2942 3375 >> >> archives.newschool.edu >> >> [image: THE NEW SCHOOL] >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Michelle Paquette > (she/her) > Metadata & Technical Services Archivist > Special Collections > Smith College > 413-585-7029 > mpaquette at smith.edu > > Please note: In light of COVID-19, the Libraries are offering contactless > pickup, and all other services will continue to be offered remotely. Visit > bit.ly/SCLcovid-19 for full details. > > Please send any questions you may have to libraryhelp at smith.edu and they > will be answered as soon as possible. Special Collections reference > service is active, but limited. For > information about Smith College?s response to Covid-19, please visit the college?s > official website > . > -- Michelle Paquette (she/her) Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu Please note: In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website . -------------- next part -------------- An HTML attachment was scrubbed... URL: From robinsa1 at newschool.edu Wed Mar 24 16:03:43 2021 From: robinsa1 at newschool.edu (Anna Robinson-Sweet) Date: Wed, 24 Mar 2021 16:03:43 -0400 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? In-Reply-To: References: Message-ID: That is indeed what seems to be happening. For us it's not only with the date filter, but also the free text filter. Search for fashion designers (113 results): https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search When I type critics into the filter search bar, 136 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=critics&filter_from_year=&filter_to_year=&commit=Search On Wed, Mar 24, 2021 at 4:00 PM Michelle Paquette wrote: > Ha, and actually now I've tested it in my own system and this seems to be > the case that when adding the date filter it switches to OR. Doesn't seem > to be happening with any other filters though. Blake, any insight? > > On Wed, Mar 24, 2021 at 3:56 PM Michelle Paquette > wrote: > >> Hi Anna, >> >> I'm wondering if something is happening to the default AND boolean - if >> you search fashion OR designers in the first place you're getting 5998 >> results, so it seems when you remove the date filter it switches from an >> AND to an OR search. >> >> Michelle >> >> On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet < >> robinsa1 at newschool.edu> wrote: >> >>> Hello, >>> >>> We just noticed what appears to be a bug in applying filters to search >>> results in the PUI. When we run a search on a phrase that is more than one >>> word, and then apply a filter to those results, we get more results in the >>> "filtered" search than in the initial one. When we remove the filter, there >>> are even more results than either the initial or filtered search.This only >>> happens when the initial search phrase is more than one word and is not in >>> quotes, suggesting that the filter turns the initial search from an "and" >>> query to an "or" query, or something along these lines. >>> >>> Here is an example of the problem: >>> First search for the phrase fashion designers (without quotes) returns >>> 113 results: >>> https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search >>> >>> When I add a date filer 1950-1960 I get 393 results: >>> https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search >>> >>> And when I remove the filter I get 5,998 results: >>> https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= >>> >>> Has anyone else encountered this or have any ideas what may be causing >>> the problem? >>> >>> Thanks, >>> Anna >>> >>> -- >>> >>> ANNA ROBINSON-SWEET (she/her) >>> >>> ASSOCIATE ARCHIVIST >>> THE NEW SCHOOL >>> ARCHIVES & SPECIAL COLLECTIONS >>> >>> 66 FIFTH AVENUE, NEW YORK, NY 10011 >>> robinsa1 at newschool.edu >>> >>> T 212-229-2942 3375 >>> >>> archives.newschool.edu >>> >>> [image: THE NEW SCHOOL] >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> >> >> -- >> Michelle Paquette >> (she/her) >> Metadata & Technical Services Archivist >> Special Collections >> Smith College >> 413-585-7029 >> mpaquette at smith.edu >> >> Please note: In light of COVID-19, the Libraries are offering contactless >> pickup, and all other services will continue to be offered remotely. Visit >> bit.ly/SCLcovid-19 for full details. >> >> Please send any questions you may have to libraryhelp at smith.edu and they >> will be answered as soon as possible. Special Collections reference >> service is active, but limited. For >> information about Smith College?s response to Covid-19, please visit the college?s >> official website >> . >> > > > -- > Michelle Paquette > (she/her) > Metadata & Technical Services Archivist > Special Collections > Smith College > 413-585-7029 > mpaquette at smith.edu > > Please note: In light of COVID-19, the Libraries are offering contactless > pickup, and all other services will continue to be offered remotely. Visit > bit.ly/SCLcovid-19 for full details. > > Please send any questions you may have to libraryhelp at smith.edu and they > will be answered as soon as possible. Special Collections reference > service is active, but limited. For > information about Smith College?s response to Covid-19, please visit the college?s > official website > . > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [image: THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Mar 24 16:39:43 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 24 Mar 2021 20:39:43 +0000 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? In-Reply-To: References: , Message-ID: > Blake, any insight? Nope, it does look like a bug to me, but I'm not sure on that. I'll look into it, and get a JIRA in if that's the case. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Anna Robinson-Sweet Sent: Wednesday, March 24, 2021 4:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Bug in PUI search filtering? That is indeed what seems to be happening. For us it's not only with the date filter, but also the free text filter. Search for fashion designers (113 results): https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search When I type critics into the filter search bar, 136 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=critics&filter_from_year=&filter_to_year=&commit=Search On Wed, Mar 24, 2021 at 4:00 PM Michelle Paquette > wrote: Ha, and actually now I've tested it in my own system and this seems to be the case that when adding the date filter it switches to OR. Doesn't seem to be happening with any other filters though. Blake, any insight? On Wed, Mar 24, 2021 at 3:56 PM Michelle Paquette > wrote: Hi Anna, I'm wondering if something is happening to the default AND boolean - if you search fashion OR designers in the first place you're getting 5998 results, so it seems when you remove the date filter it switches from an AND to an OR search. Michelle On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet > wrote: Hello, We just noticed what appears to be a bug in applying filters to search results in the PUI. When we run a search on a phrase that is more than one word, and then apply a filter to those results, we get more results in the "filtered" search than in the initial one. When we remove the filter, there are even more results than either the initial or filtered search.This only happens when the initial search phrase is more than one word and is not in quotes, suggesting that the filter turns the initial search from an "and" query to an "or" query, or something along these lines. Here is an example of the problem: First search for the phrase fashion designers (without quotes) returns 113 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search When I add a date filer 1950-1960 I get 393 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search And when I remove the filter I get 5,998 results: https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= Has anyone else encountered this or have any ideas what may be causing the problem? Thanks, Anna -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [THE NEW SCHOOL] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Michelle Paquette (she/her) Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu Please note: In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website. -- Michelle Paquette (she/her) Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu Please note: In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.hoffman at lyrasis.org Wed Mar 24 21:13:08 2021 From: brian.hoffman at lyrasis.org (Brian Hoffman) Date: Thu, 25 Mar 2021 01:13:08 +0000 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? In-Reply-To: References: Message-ID: <4AFA12E6-B786-40C9-A5BF-87C61EC8BCE5@lyrasis.org> Responding to Anna?s original message, I think this issue in JIRA captures what is probably going on when a two-word search yields more (rather than fewer) results after filtering by another word: https://archivesspace.atlassian.net/browse/ANW-1240 From: on behalf of Blake Carver Reply-To: Archivesspace Users Group Date: Wednesday, March 24, 2021 at 4:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Bug in PUI search filtering? > Blake, any insight? Nope, it does look like a bug to me, but I'm not sure on that. I'll look into it, and get a JIRA in if that's the case. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Anna Robinson-Sweet Sent: Wednesday, March 24, 2021 4:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Bug in PUI search filtering? That is indeed what seems to be happening. For us it's not only with the date filter, but also the free text filter. Search for fashion designers (113 results): https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search When I type critics into the filter search bar, 136 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=critics&filter_from_year=&filter_to_year=&commit=Search On Wed, Mar 24, 2021 at 4:00 PM Michelle Paquette > wrote: Ha, and actually now I've tested it in my own system and this seems to be the case that when adding the date filter it switches to OR. Doesn't seem to be happening with any other filters though. Blake, any insight? On Wed, Mar 24, 2021 at 3:56 PM Michelle Paquette > wrote: Hi Anna, I'm wondering if something is happening to the default AND boolean - if you search fashion OR designers in the first place you're getting 5998 results, so it seems when you remove the date filter it switches from an AND to an OR search. Michelle On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet > wrote: Hello, We just noticed what appears to be a bug in applying filters to search results in the PUI. When we run a search on a phrase that is more than one word, and then apply a filter to those results, we get more results in the "filtered" search than in the initial one. When we remove the filter, there are even more results than either the initial or filtered search.This only happens when the initial search phrase is more than one word and is not in quotes, suggesting that the filter turns the initial search from an "and" query to an "or" query, or something along these lines. Here is an example of the problem: First search for the phrase fashion designers (without quotes) returns 113 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search When I add a date filer 1950-1960 I get 393 results: https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search And when I remove the filter I get 5,998 results: https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= Has anyone else encountered this or have any ideas what may be causing the problem? Thanks, Anna -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [Image removed by sender. THE NEW SCHOOL] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Michelle Paquette (she/her) Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu Please note: In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website. -- Michelle Paquette (she/her) Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu Please note: In light of COVID-19, the Libraries are offering contactless pickup, and all other services will continue to be offered remotely. Visit bit.ly/SCLcovid-19 for full details. Please send any questions you may have to libraryhelp at smith.edu and they will be answered as soon as possible. Special Collections reference service is active, but limited. For information about Smith College?s response to Covid-19, please visit the college?s official website. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- ANNA ROBINSON-SWEET (she/her) ASSOCIATE ARCHIVIST THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212-229-2942 3375 archives.newschool.edu [Image removed by sender. THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Mar 25 04:04:20 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 25 Mar 2021 08:04:20 +0000 Subject: [Archivesspace_Users_Group] Bug in PUI search filtering? In-Reply-To: <4AFA12E6-B786-40C9-A5BF-87C61EC8BCE5@lyrasis.org> References: <4AFA12E6-B786-40C9-A5BF-87C61EC8BCE5@lyrasis.org> Message-ID: <670956ba-749a-24ea-fd2c-ec144987a7cf@bodleian.ox.ac.uk> This sounds similar to some observations I made last year in a comment on the fix that made defaulting to AND between multiple search terms work in the PUI: https://github.com/archivesspace/archivesspace/pull/1861#issuecomment-620676731 Basically, what I believe is happening is that old versions of Solr, including the one packaged with ArchivesSpace, ignore the choice of implicit-AND between two or more search terms (as set by q.op or mm in AppConfig[:solr_params]) when it receives a query that includes explicit Boolean logic. That is the case when you add date filters, because the ArchivesSpace backend builds a query to send to Solr in which whatever you enter as a user is AND'ed with the date range. The number of hits goes up even further when you remove the date filter because &filter_q[]= in the URL means it is AND'ing the user's query with a search for *. Newer versions of Solr allow q.op or mm parameters to apply within subqueries, which removes this issue. To confirm, are the people who see this effect running ArchivesSpace 2.8.0 or higher with internal Solr (i.e. is AppConfig[:enable_solr] set to true in config.rb)? Or, if using external Solr, is the version lower than 5.5? I'm afraid I never got round to raising a JIRA ticket for this, partly because it doesn't actually affect us (we run external Solr and also have opted for implicit-OR) and partly because there is probably nothing that can be done to fix it (except by upgrading the version of Solr that comes with ArchivesSpace, but as I understand it another change made in Solr after 4.10 makes that difficult.) Andrew. On 25/03/2021 01:13, Brian Hoffman wrote: > > Responding to Anna?s original message, I think this issue in JIRA > captures what is probably going on when a two-word search yields more > (rather than fewer) results after filtering by another word: > > https://archivesspace.atlassian.net/browse/ANW-1240 > > > *From: * on > behalf of Blake Carver > *Reply-To: *Archivesspace Users Group > > *Date: *Wednesday, March 24, 2021 at 4:39 PM > *To: *Archivesspace Users Group > > *Subject: *Re: [Archivesspace_Users_Group] Bug in PUI search filtering? > > > Blake, any insight? > > Nope, it does look?like a bug to me, but I'm not?sure on that. I'll > look into it, and get a JIRA in if that's the case. > > ------------------------------------------------------------------------ > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Anna Robinson-Sweet > *Sent:* Wednesday, March 24, 2021 4:03 PM > *To:* Archivesspace Users Group > > *Subject:* Re: [Archivesspace_Users_Group] Bug in PUI search filtering? > > That is indeed what seems to be happening. For us it's not only with > the date filter, but also the free text filter. > > Search for fashion designers (113 results): > https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search > > > When I type critics into the filter search bar, 136 results: > https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=critics&filter_from_year=&filter_to_year=&commit=Search > > > On Wed, Mar 24, 2021 at 4:00 PM Michelle Paquette > wrote: > > Ha, and actually now I've tested it in my own system and this > seems to be the case that when adding the date filter it switches > to OR. Doesn't seem to be happening with any other filters though. > Blake, any insight? > > On Wed, Mar 24, 2021 at 3:56 PM Michelle Paquette > > wrote: > > Hi Anna, > > I'm wondering if something is happening to the default AND > boolean - if you search fashion OR designers in the first > place you're getting 5998 results, so it seems when you remove > the date filter it switches from an AND to an OR search. > > Michelle > > On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet > > wrote: > > Hello, > > We just noticed what appears to be a bug in applying > filters to search results in the PUI. When we run a search > on a phrase that is more than one word, and then apply a > filter to those results, we get more results in the > "filtered" search than in the initial one. When we remove > the filter, there are even more results than either the > initial or filtered search.This only happens when the > initial search phrase is more than one word and is not in > quotes, suggesting that the filter turns the initial > search from an "and" query to an "or" query, or something > along these lines. > > Here is an example of the problem: > > First search for the phrase fashion designers (without > quotes) returns 113 results: > https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&commit=Search > > > When I add a date filer 1950-1960 I get 393 results: > https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93&op%5B%5D=&q%5B%5D=fashion+designers&limit=&field%5B%5D=&from_year%5B%5D=&to_year%5B%5D=&action=search&sort=&filter_q%5B%5D=&filter_from_year=1950&filter_to_year=1960&commit=Search > > > And when I remove the filter I get 5,998 results: > https://findingaids.archives.newschool.edu/search?q[]=fashion+designers&op[]=&field[]=keyword&from_year[]=&to_year[]=&filter_q[]=&sort= > > > Has anyone else encountered this or have any ideas what > may be causing the problem? > > Thanks, > > Anna > > -- > > *ANNA ROBINSON-SWEET (she/her)* > > ASSOCIATE ARCHIVIST > THE NEW SCHOOL > ARCHIVES & SPECIAL COLLECTIONS > > 66 FIFTH AVENUE, NEW YORK, NY 10011 > robinsa1 at newschool.edu > > *T*?212-229-2942 3375 > > archives.newschool.edu > > > Image removed by sender. THE NEW SCHOOL > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > -- > > Michelle Paquette > > (she/her) > > Metadata & Technical Services Archivist > > Special Collections > > Smith College > > 413-585-7029 > > mpaquette at smith.edu > > Please note: In light of COVID-19, the Libraries are offering > contactless pickup, and all other services will continue to be > offered remotely. Visit bit.ly/SCLcovid-19 > for full details. > > > Please send any questions you may have to > libraryhelp at smith.edu and they > will be answered as soon as possible. Special > Collectionsreference service > is active, but limited. > For information about Smith College?s response to Covid-19, > please visit thecollege?s official website > . > > > -- > > Michelle Paquette > > (she/her) > > Metadata & Technical Services Archivist > > Special Collections > > Smith College > > 413-585-7029 > > mpaquette at smith.edu > > Please note: In light of COVID-19, the Libraries are offering > contactless pickup, and all other services will continue to be > offered remotely. Visit bit.ly/SCLcovid-19 > for full details. > > > Please send any questions you may have to libraryhelp at smith.edu > and they will be answered as soon as > possible. Special Collectionsreference service > is active, but limited. For > information about Smith College?s response to Covid-19, please > visit thecollege?s official website > . > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > -- > > *ANNA ROBINSON-SWEET (she/her)* > > ASSOCIATE ARCHIVIST > THE NEW SCHOOL > ARCHIVES & SPECIAL COLLECTIONS > > 66 FIFTH AVENUE, NEW YORK, NY 10011 > robinsa1 at newschool.edu > > *T*?212-229-2942 3375 > > archives.newschool.edu > > > Image removed by sender. THE NEW SCHOOL > > > _______________________________________________ > 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 christine.dibella at lyrasis.org Thu Mar 25 10:22:33 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 25 Mar 2021 14:22:33 +0000 Subject: [Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.0.0-RC1 Message-ID: Hello ArchivesSpace members, The ArchivesSpace team is pleased to announce a release candidate, v3.0.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v3.0.0-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This release candidate centers around changes to the agents module of ArchivesSpace to make it more standards-compliant with EAC-CPF and the MARCXML format for authority data, enabling deeper and richer description of people, families, and corporate entities, their relationships to each other and their relationships to materials held outside ArchivesSpace. This work is the result of a community specification written through the participation of many users across the ArchivesSpace community, mostly notably Cory Nimer, Sue Luftschein, and Brad Westbrook. Through this work new fields and sub-records have been added to the agents schema, and staff and public interface views, imports, exports, and auxiliary functionality like agent merging have all been updated. There is also a new Light mode for agents, which provides the option for users to continue to work with agent records in the staff interface in a pared down view that is similar to that of ArchivesSpace versions prior to this one. While the bulk of the changes in this release candidate relate to the agents module, the release candidate also contains improvements in some other areas of the application contributed by community developers and program team developers and contractors. Included among these are additional performance, backend and staff interface improvements courtesy of work Hudson Molonglo developers James Bullen, Mark Triggs, and Payten Giles did for Queensland State Archives as part of a larger project. Every bit of testing and feedback helps us improves the release. We encourage you to test these improvements with your own data if you can. Some resources you may find helpful when testing include: * Information from the webinar highlighting changes in v3.0.0: https://archivesspace.org/archives/6660 * Some new or updated user manual sections on the agents module (access requires your usual user manual login): https://archivesspace.atlassian.net/wiki/label/ArchivesSpaceUserManual/3agents Thanks to the many community members who made contributions as we worked on bringing this expanded functionality to ArchivesSpace, including both individual archives staff and developers and our Testing and User Documentation sub-teams. Please try this release candidate out and let us know at ArchivesSpaceHome at lyrasis.org by April 7 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. The results of community testing will help us determine a release date. Please get in touch if you have any questions. Thanks as always for your feedback and support. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6609 bytes Desc: image003.jpg URL: From pcollopy at caltech.edu Thu Mar 25 12:00:30 2021 From: pcollopy at caltech.edu (Collopy, Peter S.) Date: Thu, 25 Mar 2021 16:00:30 +0000 Subject: [Archivesspace_Users_Group] Announcing the ARK (Archival Resource Key) Alliance (arks.org) Message-ID: Dear colleagues, [https://lh6.googleusercontent.com/lwniYti6F-oPMreWgw7uJVx5ETdR5-CRxKKdoG68uPnRZtmG2KkSqOPnfopD6Y7-Wio6Ru8rY2pBQ3OMB8IxJWhPprfUbtsG1jJ2Dfq1oVyiJntiYvcGjUg8arOWgScT3hRaNbVB] We are pleased to announce the formation of the ARK Alliance, an open global community supporting Archival Resource Keys (ARKs). The ARK Alliance succeeds the ARKs-in-the-Open initiative, begun in 2018. We invite you to visit us at our new website, which contains guidance on how to get started with ARKs, resources, news, the community, and links to email forums for users in English and French. ARK users can receive news and updates from the ARK community by subscribing to the ARK Alliance newsletter and following the ARK Alliance on Twitter. The ARK Alliance has three working groups and welcomes your participation, which can take many forms. Please visit the community page to learn about ways to become involved. About ARKs: ARKs are used as ?persistent identifiers?, which are stable, trusted references (names) for information objects. Among other things, they aim to be web addresses (URLs) that don?t return 404 Page Not Found errors. ARKs are similar to DOIs, URNs, and Handles. All of them * were introduced over 20 years ago, * exist in large numbers (8.2 billion ARKs, 240 million DOIs, etc.), * start with a string to identify the name assigning authority, * require the active updating of URL redirects, and * support research and scholarship, appearing in the Data Citation Index, Wikipedia, ORCiD.org profiles, etc. In contrast, ARKs are cheaper, more flexible, and less centralized, letting you * create unlimited identifiers without paying for the right to do so, * add any kind of metadata, including no metadata, * append extensions and query strings during resolution, * link directly to an article, image, or spreadsheet that is immediately usable by people and software without making them first stop at a landing page, and * make millions of ARKs resolvable by managing just one ARK, via a mechanism called suffix passthrough. Who uses ARKs: End users, especially researchers, rely on ARKs for long term access to the global scientific and cultural record, where by design they identify anything digital, physical, or abstract. [https://lh3.googleusercontent.com/lP0IT9ZtBOOQocpPECJ4oTXAEeEwiNGqB7357S-ekVMKjNn55C_aFII6_-V-6S3bNqap2yw_pEwTBVXSovU61FInyITcZee3svapvWCHmns8tNn2pcqv8UdUNLd0NubAPQdXVxQV] Some things that have ARKs ? an article, violin, genealogy, storybook, sports photo, and plant specimen ? assigned by the Smithsonian Institution, Internet Archive, California Digital Library, and FamilySearch. Over 725 organizations are registered to create ARKs, including libraries, data centers, archives, museums, publishers, government agencies, and vendors. Additional organizations are signing on rapidly. [chart of growth of ARK-assigning organizations since 2001] Peter Sachs Collopy, PhD (he/him) University Archivist and Head of Archives and Special Collections Caltech Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Thu Mar 25 16:59:00 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Thu, 25 Mar 2021 16:59:00 -0400 Subject: [Archivesspace_Users_Group] Indexed - but still some issues In-Reply-To: References: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> Message-ID: I may not be understanding it completely, but from what I've read 256k is typical for a 64-bit JVM. Given that, 2m is comparatively big. 1g is 500 times the default, which seems excessively big. On Wed, Mar 24, 2021 at 3:06 PM Tom Hanstra wrote: > My understand/reading regarding this setting is that it is the thread size > for Java, and has to be big enough to handle the work but cannot be too big > either. The default of 2m seems very low. I have been working with the 1g > size lately but am not sure that is optimal either. I'd be curious to know > if there are optimal numbers that people have found useful. > > Tom > > On Wed, Mar 24, 2021 at 12:55 PM Trevor Thornton > wrote: > >> I'm doing this exact thing right now and I wanted to confirm that the 'g' >> here shouldn't be an 'm': >> ASPACE_JAVA_XSS="-Xss1g" >> >> The default looks to be: >> ASPACE_JAVA_XSS="-Xss2m" >> >> https://github.com/archivesspace/archivesspace/blob/master/launcher/archivesspace.sh#L105 >> >> On Wed, Mar 24, 2021 at 11:43 AM Tom Hanstra wrote: >> >>> Hmmm. So I finally tracked the issue down to my Java settings. For some >>> reason, before/during indexing, Java settings of: >>> >>> ASPACE_JAVA_XMX="-Xmx8192m" >>> ASPACE_JAVA_XSS="-Xss4g" >>> >>> worked fine. But, once indexing was complete, those settings were >>> somehow unusable. Staff connection would not work, searches failed, etc. >>> >>> But when I crank down the thread size to: >>> >>> ASPACE_JAVA_XMX="-Xmx8192m" >>> ASPACE_JAVA_XSS="-Xss1g" >>> >>> everything goes back to working. There was a server reboot in there as >>> well as numerous restarts with config.rb changes and that was the only >>> change that I found could address the issues. Through a number of restarts, >>> there was nothing in the logs to indicate the issue. Finally got an error >>> that suggested Java space issues and tried the lower value and things now >>> work (as far as I've tested at least). >>> >>> Quite a journey so far... >>> >>> Tom >>> >>> >>> On Wed, Mar 24, 2021 at 9:54 AM Peter Heiner wrote: >>> >>>> Tom Hanstra wrote on 2021-03-24 09:25:24: >>>> > So, I am now further than I've been yet, at least based upon the >>>> logs. But >>>> > I still have something not working properly, because when I do a >>>> search and >>>> > find output, nothing is coming up when I try to look at the found >>>> record. I >>>> > get the error: >>>> > >>>> > *We're sorry, but something went wrong.* >>>> > >>>> > When I've seen that in other applications, it has been a rails issue. >>>> Not >>>> > sure if that is what is happening here as well. >>>> >>>> This error should have a corresponding event with at least WARNING >>>> level in >>>> the frontend/public log (depending on which gave you the error) that >>>> you can >>>> correlate by event time. >>>> >>>> > Also, the "Found In" links for the records come back with: >>>> > >>>> > *The record you've tried to access does not exist or may have been >>>> > removed.The record you've tried to access does not exist or may have >>>> been >>>> > removed.* >>>> >>>> This would point to the fact that your database and index are not in >>>> sync. >>>> Given your struggles with indexing I'm starting to wonder if you're >>>> reading >>>> from the Solr instance you're writing to. >>>> >>>> p >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>> >>> >>> -- >>> *Tom Hanstra* >>> *Sr. Systems Administrator* >>> hanstra at nd.edu >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> >> >> -- >> Trevor Thornton >> Applications Developer, Digital Library Initiatives >> North Carolina State University Libraries >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From ph448 at cam.ac.uk Thu Mar 25 17:41:04 2021 From: ph448 at cam.ac.uk (Peter Heiner) Date: Thu, 25 Mar 2021 21:41:04 +0000 Subject: [Archivesspace_Users_Group] Indexed - but still some issues In-Reply-To: References: <20210324135524.ijjckpgww6tubbif@sparkly.localdomain> Message-ID: <20210325214104.5hqtl6h3wwogpzhj@sparkly.localdomain> Indeed, -Xss is the stack size, this amount gets allocated for each thread created. I believe the default is 1MB. A general rule of thumb is to increase it conservatively if you get a stack overflow error in the app. p Trevor Thornton wrote on 2021-03-25 16:59:00: > I may not be understanding it completely, but from what I've read 256k is > typical for a 64-bit JVM. Given that, 2m is comparatively big. 1g is 500 > times the default, which seems excessively big. > > On Wed, Mar 24, 2021 at 3:06 PM Tom Hanstra wrote: > > > My understand/reading regarding this setting is that it is the thread size > > for Java, and has to be big enough to handle the work but cannot be too big > > either. The default of 2m seems very low. I have been working with the 1g > > size lately but am not sure that is optimal either. I'd be curious to know > > if there are optimal numbers that people have found useful. > > > > Tom > > > > On Wed, Mar 24, 2021 at 12:55 PM Trevor Thornton > > wrote: > > > >> I'm doing this exact thing right now and I wanted to confirm that the 'g' > >> here shouldn't be an 'm': > >> ASPACE_JAVA_XSS="-Xss1g" > >> > >> The default looks to be: > >> ASPACE_JAVA_XSS="-Xss2m" > >> > >> https://github.com/archivesspace/archivesspace/blob/master/launcher/archivesspace.sh#L105 > >> > >> On Wed, Mar 24, 2021 at 11:43 AM Tom Hanstra wrote: > >> > >>> Hmmm. So I finally tracked the issue down to my Java settings. For some > >>> reason, before/during indexing, Java settings of: > >>> > >>> ASPACE_JAVA_XMX="-Xmx8192m" > >>> ASPACE_JAVA_XSS="-Xss4g" > >>> > >>> worked fine. But, once indexing was complete, those settings were > >>> somehow unusable. Staff connection would not work, searches failed, etc. > >>> > >>> But when I crank down the thread size to: > >>> > >>> ASPACE_JAVA_XMX="-Xmx8192m" > >>> ASPACE_JAVA_XSS="-Xss1g" > >>> > >>> everything goes back to working. There was a server reboot in there as > >>> well as numerous restarts with config.rb changes and that was the only > >>> change that I found could address the issues. Through a number of restarts, > >>> there was nothing in the logs to indicate the issue. Finally got an error > >>> that suggested Java space issues and tried the lower value and things now > >>> work (as far as I've tested at least). > >>> > >>> Quite a journey so far... > >>> > >>> Tom > >>> > >>> > >>> On Wed, Mar 24, 2021 at 9:54 AM Peter Heiner wrote: > >>> > >>>> Tom Hanstra wrote on 2021-03-24 09:25:24: > >>>> > So, I am now further than I've been yet, at least based upon the > >>>> logs. But > >>>> > I still have something not working properly, because when I do a > >>>> search and > >>>> > find output, nothing is coming up when I try to look at the found > >>>> record. I > >>>> > get the error: > >>>> > > >>>> > *We're sorry, but something went wrong.* > >>>> > > >>>> > When I've seen that in other applications, it has been a rails issue. > >>>> Not > >>>> > sure if that is what is happening here as well. > >>>> > >>>> This error should have a corresponding event with at least WARNING > >>>> level in > >>>> the frontend/public log (depending on which gave you the error) that > >>>> you can > >>>> correlate by event time. > >>>> > >>>> > Also, the "Found In" links for the records come back with: > >>>> > > >>>> > *The record you've tried to access does not exist or may have been > >>>> > removed.The record you've tried to access does not exist or may have > >>>> been > >>>> > removed.* > >>>> > >>>> This would point to the fact that your database and index are not in > >>>> sync. > >>>> Given your struggles with indexing I'm starting to wonder if you're > >>>> reading > >>>> from the Solr instance you're writing to. > >>>> > >>>> p > >>>> > >>>> _______________________________________________ > >>>> Archivesspace_Users_Group mailing list > >>>> Archivesspace_Users_Group at lyralists.lyrasis.org > >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >>>> > >>> > >>> > >>> -- > >>> *Tom Hanstra* > >>> *Sr. Systems Administrator* > >>> hanstra at nd.edu > >>> > >>> > >>> _______________________________________________ > >>> Archivesspace_Users_Group mailing list > >>> Archivesspace_Users_Group at lyralists.lyrasis.org > >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >>> > >> > >> > >> -- > >> Trevor Thornton > >> Applications Developer, Digital Library Initiatives > >> North Carolina State University Libraries > >> _______________________________________________ > >> Archivesspace_Users_Group mailing list > >> Archivesspace_Users_Group at lyralists.lyrasis.org > >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >> > > > > > > -- > > *Tom Hanstra* > > *Sr. Systems Administrator* > > hanstra at nd.edu > > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Trevor Thornton > Applications Developer, Digital Library Initiatives > North Carolina State University Libraries > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From dsprouse at tsl.texas.gov Fri Mar 26 11:24:36 2021 From: dsprouse at tsl.texas.gov (Daniel Sprouse) Date: Fri, 26 Mar 2021 15:24:36 +0000 Subject: [Archivesspace_Users_Group] merge agent/subject records operation not working Message-ID: merge agent/subject records operation not working We created a group to allow an individual to 'merge agent/subject records' and while the button shows up, the behavior is not what we expected: "I do have the Merge button now and I get to the Merge Preview to compare the two. However, when I click on the Merge button in the Merge Preview it just spins. When it stops I am still in the Merge Preview. The two agent names have not been merged." This is the only group the user is a member of, and we have restarted the archivesspace application and retested her ability to perform the merge operation. Anyone have any ideas on how to make this work? Daniel Sprouse TSLAC Linux Admin dsprouse at tsl.texas.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Fri Mar 26 16:51:23 2021 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Fri, 26 Mar 2021 20:51:23 +0000 Subject: [Archivesspace_Users_Group] merge agent/subject records operation not working In-Reply-To: References: Message-ID: Can the user edit agent records without a problem? Can the user delete agent records? Can other users merge agent records? If the answer to the final question is Yes, I'd compare the user's group's permissions to the permissions of the other groups and see what the differences are. Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Daniel Sprouse Sent: Friday, March 26, 2021 11:24 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge agent/subject records operation not working merge agent/subject records operation not working We created a group to allow an individual to 'merge agent/subject records' and while the button shows up, the behavior is not what we expected: "I do have the Merge button now and I get to the Merge Preview to compare the two. However, when I click on the Merge button in the Merge Preview it just spins. When it stops I am still in the Merge Preview. The two agent names have not been merged." This is the only group the user is a member of, and we have restarted the archivesspace application and retested her ability to perform the merge operation. Anyone have any ideas on how to make this work? Daniel Sprouse TSLAC Linux Admin dsprouse at tsl.texas.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 29 13:40:23 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 29 Mar 2021 17:40:23 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board In-Reply-To: References: Message-ID: This is a gentle reminder to consider participating in ArchivesSpace governance-nominate yourself or a colleague.. The deadline for nominations is Friday April 23rd. From: Gordon Daines Sent: Tuesday, March 16, 2021 1:21 PM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' ; Archivesspace_member_reps at lyralists.lyrasis.org; archivesspace_tac at lyralists.lyrasis.org; archivesspace_uac at lyralists.lyrasis.org; archivesspace_small_archives_users_group at lyralists.lyrasis.org; ArchivesSpace Board of Trustees mail list Subject: Nominations Requested for ArchivesSpace Governance Board As chair of the 2021 ArchivesSpace Nominating Committee, I seek your nominations of candidates to stand for election for the ArchivesSpace Governance Board representing the Small and Very Large membership levels. The Governance Board is charged with providing oversight for the ArchivesSpace application and community, including fiscal oversight, the approval of development priorities, and oversight of the Technical and User Advisory councils. We are seeking two candidates for the Small level and one candidate for the Very Large level. (The current incumbent at the Very Large membership level is running for re-election as representative.) The terms for all successful candidates will be July 1, 2021-June 30, 2024. Each newly elected member representative will be eligible to run for a second term, July 1, 2024-June 30, 2027. Governance Board nominees must be currently employed by an ArchivesSpace member organization in either the Small or Very Large member levels (see the member lists at: http://archivesspace.org/community/whos-using-archivesspace/). A variety of skills, interests, and experience can be useful in furthering the Board's mission, but nominees should ideally have administrative and fiscal oversight experience. As the community for a software application used in many different settings, we seek diverse voices in working to improve ArchivesSpace and support those who use or may benefit from using it. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in these important leadership roles. To submit nominations, including self-nominations, please submit this form at https://forms.gle/m2nN49M34CPgnvci9. Nominees who confirm their interest in standing for election will be requested to supply a formal candidate statement outlining their qualifications for serving on the ArchivesSpace Governance Board (see: http://archivesspace.org/about/governance-board-and-councils/). The Nominating Committee will review all nominations and confirm a slate of nominees with the current Governance Board. An election ballot will be circulated to member institutions in mid-May. Nominations must be received by 9:00 p.m. EDT on Friday April 23rd. Please contact Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org or any member of the Nominating Committee with questions. 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, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: Brittany Newberry, Robert W. Woodruff Library, Atlanta University Center, Chair of User Advisory Council Trevor Thornton, North Carolina State University, Chair of Technical Advisory Council Zach Johnson, Vanderbilt University, representing very large membership level Jacky Johnson, Miami University, representing large membership level Heidi Buchanan, West Carolina University, representing medium membership level Patricia Burdick, Colby College, representing small membership level Yue Ma, Museum of Chinese in America, representing very small membership level Christine Di Bella (ArchivesSpace Program Manager), ex officio _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 29 13:41:08 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 29 Mar 2021 17:41:08 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council In-Reply-To: References: Message-ID: This is a gentle reminder to consider participating in ArchivesSpace governance-nominate yourself or a colleague. The deadline for nominations is Friday April 23rd. From: Gordon Daines Sent: Tuesday, March 16, 2021 1:21 PM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' ; Archivesspace_member_reps at lyralists.lyrasis.org; archivesspace_tac at lyralists.lyrasis.org; archivesspace_uac at lyralists.lyrasis.org; archivesspace_small_archives_users_group at lyralists.lyrasis.org; ArchivesSpace Board of Trustees mail list Subject: Nominations Requested for ArchivesSpace Technical Advisory Council The ArchivesSpace Governance Board is seeking nominations to fill up to three (3) vacancies on the ArchivesSpace Technical Advisory Council (TAC). The Technical Advisory Council (https://archivesspace.org/governance-board-and-councils#TAC) 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: * 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 in formats such as EAD, MARCXML, and CSV. * Documenting the metadata standards used by ArchivesSpace and monitoring the standards landscape. * 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. * Maintaining and updating technical documentation, including documentation of the API. * Providing support and resources to help develop a community of code committers. Nominees should preferably be presently employed at an ArchivesSpace member institution (please refer to the member list at: http://archivesspace.org/community/whos-using-archivesspace/) or employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations from non-member institutions will be considered based on their expertise and ability to contribute to the TAC. As the community for a software application used in many different settings, we seek diverse voices in working to improve ArchivesSpace and support those who use or may benefit from using it. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in these important leadership roles. 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, 2021-June 30, 2023. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2023-June 30, 2025. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please submit this form at https://forms.gle/m2nN49M34CPgnvci9. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. Nominations must be received by 9:00 p.m. EDT on Friday April 23rd. Please contact Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org or any member of the Nominating Committee with questions. 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, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: Brittany Newberry, Robert W. Woodruff Library, Atlanta University Center, Chair of User Advisory Council Trevor Thornton, North Carolina State University, Chair of Technical Advisory Council Zach Johnson, Vanderbilt University, representing very large membership level Jacky Johnson, Miami University, representing large membership level Heidi Buchanan, West Carolina University, representing medium membership level Patricia Burdick, Colby College, representing small membership level Yue Ma, Museum of Chinese in America, representing very small membership level Christine Di Bella (ArchivesSpace Program Manager), ex officio _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 29 13:41:47 2021 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 29 Mar 2021 17:41:47 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council In-Reply-To: References: Message-ID: This is a gentle reminder to consider participating in ArchivesSpace governance-nominate yourself or a colleague. The deadline for nominations is Friday April 23rd. From: Gordon Daines Sent: Tuesday, March 16, 2021 1:21 PM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' ; Archivesspace_member_reps at lyralists.lyrasis.org; archivesspace_tac at lyralists.lyrasis.org; archivesspace_uac at lyralists.lyrasis.org; archivesspace_small_archives_users_group at lyralists.lyrasis.org; ArchivesSpace Board of Trustees mail list Subject: Nominations Requested for ArchivesSpace User Advisory Council The ArchivesSpace Governance Board is seeking nominations to fill up to three (3) vacancies on the ArchivesSpace User Advisory Council (UAC). The User Advisory Council (https://archivesspace.org/governance-board-and-councils#UAC) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. Some of the activities UAC is currently engaged in are: * Advising the ArchivesSpace Governance Board and the ArchivesSpace Organizational Home on the design and delivery of services, such as community engagement and support services, technical support, and training. * As a joint representative of the Development Prioritization subteam, discussing and voting on ideas for software enhancements and improvements. * As a joint representative of the Testing subteam, conducting user-centered testing of the application prior to releases and conduct ongoing usability studies as needed. * Liaising with national and regional archives organizations. * Maintaining and updating user documentation. * Advocating on the usability and functionality of the software program to facilitate adoption of the program. Nominees should be presently employed at an ArchivesSpace member institution (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). As the community for a software application used in many different settings, we seek diverse voices in working to improve ArchivesSpace and support those who use or may benefit from using it. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in these important leadership roles. 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, 2021-June 30, 2023. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2023-June 30, 2025. To nominate a candidate for the ArchivesSpace User Advisory Council, please submit this form at https://forms.gle/m2nN49M34CPgnvci9. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. Nominations must be received by 9:00 p.m. EDT on Friday April 23rd. Please contact Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org or any member of the Nominating Committee with questions. 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, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: Brittany Newberry, Robert W. Woodruff Library, Atlanta University Center, Chair of User Advisory Council Trevor Thornton, North Carolina State University, Chair of Technical Advisory Council Zach Johnson, Vanderbilt University, representing very large membership level Jacky Johnson, Miami University, representing large membership level Heidi Buchanan, West Carolina University, representing medium membership level Patricia Burdick, Colby College, representing small membership level Yue Ma, Museum of Chinese in America, representing very small membership level Christine Di Bella (ArchivesSpace Program Manager), ex officio _______________________________________ J. Gordon Daines III Curator of Research and Instruction Services Curator of the Yellowstone National Park collection 1130 HBLL Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Tue Mar 30 16:15:08 2021 From: scheirw at newschool.edu (Wendy Scheir) Date: Tue, 30 Mar 2021 16:15:08 -0400 Subject: [Archivesspace_Users_Group] Issues with MySQL v8 Message-ID: Hi, When we installed ArchivesSpace last summer, we used MySQL v8 for our database. The documentation has instructions that read, "if using for MySQL 8+..." leading us to believe that MySQL 8 was a supported version. However, we've been having issues running Accession and Shelflist reports that the Lyrasis team has told us is caused by running MySQL 8 instead of MySQL 5. In the interim, Lyrasis has updated the documentation to say that "ArchivesSpace is currently able to run on MySQL version 5.x." Has anyone else installed ArchivesSpace with MySQL 8? We are concerned about downgrading to 5 versus waiting for a future version that works with 8, but in the meantime we are unable to run a number of desired reports. Many thanks, Wendy ____________________________________ WENDY SCHEIR *DIRECTOR* 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From aabney at mailbox.sc.edu Wed Mar 31 08:43:08 2021 From: aabney at mailbox.sc.edu (ABNEY, ANN C) Date: Wed, 31 Mar 2021 12:43:08 +0000 Subject: [Archivesspace_Users_Group] Locations List Providing Not-Even Close Results? Message-ID: Morning all - We're using 2.8.1 and recently I've been having trouble adding locations. Our numbering convention is Row: #, Compartment: #, Shelf: #. In the manage top containers tab for a specific resource, usually I'll search to add a location with that format. But lately, even if I put the full name of the location (with repository, floor, etc.) I'm getting lots of extraneous results. For example, I was searching for "Row: 61, Compartment: 6, Shelf: 1" I got results including from Row 2, Compartment 1, Shelf 6, and then a whole list of every shelf in Row 61 from Compartments 1-4 until the list cut off. If I search via browse, I get the same results and usually have to click through to the second page. As I said before, this even happens if I copy word for word a previous location already linked. Am I searching wrong? Is it a bug? I haven't had this problem in past iterations so I have no idea what's going on. Thanks! Ann Ann Abney, CA She/her/hers Special Projects Archivist South Carolina Political Collections University of South Carolina Libraries https://sc.edu/libraries/scpc aabney at mailbox.sc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Wed Mar 31 09:41:27 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Wed, 31 Mar 2021 09:41:27 -0400 Subject: [Archivesspace_Users_Group] Locations List Providing Not-Even Close Results? In-Reply-To: References: Message-ID: This issue keeps coming up and the solution usually involves adjusting the "default sort column" and "default sort direction" in the appropriate section in the settings (in this case it would be "Location Profile Browse Columns" I think). We had this same problem and adjusting these values worked for us, but other people have reported that it didn't. There are 3 levels of settings (Global, Repository and User) that should override one another. Here's what it says in the User Guide: > Global Preferences ? Edit these values to set your system-wide > preferences. These values can be overridden by repository default or by > your own preferences for a repository. > Repository Preferences ? Edit these values to set your user preferences > for this repository. These values can be overridden by user preferences. > User Preferences ? Edit these values to set user preference defaults for > the current repository. These values cannot be overridden. In my experience, this doesn't work as smoothly as advertised, but in theory this is how it should work. Given how frequently this problem has been reported, and the impact it has on people's workflows, I think this issue (using preference settings to adjust sort order in lists) is in desperate need of documentation. On Wed, Mar 31, 2021 at 8:43 AM ABNEY, ANN C wrote: > Morning all - > > > > We?re using 2.8.1 and recently I?ve been having trouble adding locations. > Our numbering convention is Row: #, Compartment: #, Shelf: #. In the manage > top containers tab for a specific resource, usually I?ll search to add a > location with that format. But lately, even if I put the full name of the > location (with repository, floor, etc.) I?m getting lots of extraneous > results. > > > > For example, I was searching for ?Row: 61, Compartment: 6, Shelf: 1? I got > results including from Row 2, Compartment 1, Shelf 6, and then a whole list > of every shelf in Row 61 from Compartments 1-4 until the list cut off. If I > search via browse, I get the same results and usually have to click through > to the second page. As I said before, this even happens if I copy word for > word a previous location already linked. > > > > Am I searching wrong? Is it a bug? I haven?t had this problem in past > iterations so I have no idea what?s going on. > > > > Thanks! > > Ann > > > > *Ann Abney, CA* > > She/her/hers > > Special Projects Archivist > > South Carolina Political Collections > > University of South Carolina Libraries > > https://sc.edu/libraries/scpc > > aabney at mailbox.sc.edu > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsprouse at tsl.texas.gov Wed Mar 31 12:09:02 2021 From: dsprouse at tsl.texas.gov (Daniel Sprouse) Date: Wed, 31 Mar 2021 16:09:02 +0000 Subject: [Archivesspace_Users_Group] merge agent/subject records operation not working Message-ID: merge agent/subject records operation not working We created a group to allow an individual to 'merge agent/subject records' and while the button shows up, the behavior is not what we expected: "I do have the Merge button now and I get to the Merge Preview to compare the two. However, when I click on the Merge button in the Merge Preview it just spins. When it stops I am still in the Merge Preview. The two agent names have not been merged." This is the only group the user is a member of, and we have restarted the archivesspace application and retested her ability to perform the merge operation. Anyone have any ideas on how to make this work? Thanks, Daniel Sprouse Linux Admin Texas State Library and Archives Commission -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Wed Mar 31 13:49:00 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 31 Mar 2021 17:49:00 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - March 2021 Message-ID: <1586509E-09EC-4D0A-9F63-08D318A0FF24@lyrasis.org> [cid:image001.jpg at 01D72634.9A26ADE0] ArchivesSpace Update ? March 2021 Development The ArchivesSpace team is pleased to announce a release candidate, v3.0.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v3.0.0-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This release candidate centers around changes to the agents module of ArchivesSpace to make it more standards-compliant with EAC-CPF and the MARCXML format for authority data, enabling deeper and richer description of people, families, and corporate entities, their relationships to each other and their relationships to materials held outside ArchivesSpace. This work is the result of a community specification written through the participation of many users across the ArchivesSpace community, mostly notably Cory Nimer, Sue Luftschein, and Brad Westbrook. Through this work new fields and sub-records have been added to the agents schema, and staff and public interface views, imports, exports, and auxiliary functionality like agent merging have all been updated. There is also a new Light mode for agents, which provides the option for users to continue to work with agent records in the staff interface in a pared down view that is similar to that of ArchivesSpace versions prior to this one. While the bulk of the changes in this release candidate relate to the agents module, the release candidate also contains improvements in some other areas of the application contributed by community developers and program team developers and contractors. Included among these are additional performance, backend and staff interface improvements courtesy of work Hudson Molonglo developers James Bullen, Mark Triggs, and Payten Giles did for Queensland State Archives as part of a larger project. Every bit of testing and feedback helps us improve the release. We encourage you to test these improvements with your own data if you can. Our recent webinar previewing the changes in v3.0.0 may serve as a helpful guide: https://archivesspace.org/archives/6660. Thanks to the many community members who made contributions as we worked on bringing this expanded functionality to ArchivesSpace, including both individual archives staff and developers and our Testing and User Documentation sub-teams. Please try this release candidate out and let us know at ArchivesSpaceHome at lyrasis.org by April 7 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. The results of community testing will help us determine a release date. Training Announcement: ArchivesSpace Community-wide Training Program Beginning in April of 2021, the ArchivesSpace Trainers Corps will offer regularly scheduled virtual, community-wide trainings and office hours open to anyone using or interested in using ArchivesSpace. These training opportunities will be part of a 12-month pilot project by the Trainers Corps to assess community interest and training needs. All will be free to attendees during this pilot period. Information about this training program is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2331148319/ArchivesSpace+Community-Wide+Virtual+Training. Registration for each training will be separate and registration will open closer to each training date. ArchivesSpace Trainers Corps Office Hour Registration is currently open for the first ArchivesSpace Office Hour on April 19th at 2pm ET/11am PT. This office hour will offer a demonstration of how to create a thumbnail image of a digital object in the ArchivesSpace Public User Interface. Following the brief presentation, you will have the opportunity to ask questions about the topic. Once those run out we will answer questions submitted via the submission form and if time allows, questions on the fly. If you would like to suggest a topic for a future Office Hour, you can do so at https://forms.gle/unz3GmAbWwvpHjSr7. When: April 19, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Topic: How to create a thumbnail image of a digital object in the ArchivesSpace Public User Interface Question submission form: https://forms.gle/4kx1bntG7HUkMXdRA Registration: https://lyrasis.zoom.us/webinar/register/WN_5XgnGX1vTlqixabZwGKIVA <%20https:/lyrasis.zoom.us/webinar/register/WN_5XgnGX1vTlqixabZwGKIVA%0b> Webinar Announcement: Implementing the Protocols for Native American Archival Materials at Northern Arizona University ArchivesSpace will be offering a webinar on Implementing the Protocols for Native American Archival Materials at Northern Arizona University. In this webinar, Sam Meier, Cindy Summers, and Liz Garcia will discuss the ongoing efforts of Northern Arizona University?s Cline Library Special Collections and Archives to implement the Protocols for Native American Archival Materials; their vision for applying the Protocols to archival arrangement and description as well as rearrangement and redescription; logistical, technological, and resource issues with regards to updating legacy archival description in ArchivesSpace; and the design, implementation, and progress to date of the Archival Description Internship developed to help make this work possible. When: April 14, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_THgc9aVTSDK4y0GygvSLeQ This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Background information: In April 2006, Northern Arizona University (NAU) in Flagstaff, Arizona hosted a gathering of Native American and non-Native American cultural heritage professionals who together drafted the Protocols for Native American Archival Materials, a professional best practices document which outlined guidelines for culturally responsive care of Native American archival materials held by non-tribal institutions. NAU?s Cline Library and Special Collections and Archives formally endorsed the Protocols in 2006. Since then, the staff members of Cline Library Special Collections and Archives (SCA) have sought to integrate the guidance put forth by the Protocols into all aspects of their work, including collection development, collections management, and archival arrangement and description. In 2019, SCA?s newly hired Archivist for Discovery, Sam(antha) Meier, began revising the department?s draft Arrangement and Description Policy to address issues common to academic archives and special collections, such as an extensive and growing backlog of unprocessed materials and outdated and inaccurate legacy description. Supported by colleagues at Arizona State University, she began to explore the possibility of using ArchivesSpace to more rapidly gain collection-level control over new acquisitions, update existing legacy finding aids, and transition the department?s EAD finding aids hosted in Arizona Archives Online from EAD 2002 to EAD3. During the COVID-19 pandemic, Meier collaborated with Library Assistant Manager Cindy Summers to begin a holistic review of SCA?s legacy finding aids to prepare for their eventual ingest into ArchivesSpace for revision and correction. Meier and Summers found ways to continue this critical work remotely, as neither were initially working in Cline Library. Cognizant of the need to implement the Protocols at every step in archival processing, including re-description, re-arrangement, and re-processing, in the winter of 2020 Meier and Summers developed a fully remote paid graduate internship, the Archival Description Internship, intended to support an MLIS student at the University of Arizona in Tucson, Arizona. The internship was designed to function as a "pilot project" for the department, allowing Meier and Summers to explore how to apply the Protocols to their legacy finding aids along with intern Liz Garcia. Presenter Information: Elizabeth (Liz) Garcia is an MLIS student and Knowledge River Scholar at the University of Arizona?s School of Information with a concentration in archival studies. In addition to her work as the Archival Description Intern at Cline Library Special Collections and Archives, she is also the Graduate Assistant Archives Specialist at the University of Arizona Libraries Special Collections. Her research interests include archival theory, social justice in libraries and archives, and digital curation. Cindy Summers is an Assistant Manager at Cline Library Special Collections and Archives where she supervises volunteers, student employees, and interns. Cindy works closely with the Archivist for Discovery (Samantha Meier) to oversee collections processing, which has led to the ambitious project of updating all of SCA?s legacy finding aids and ingesting them in ArchivesSpace. Despite her employment history in many different units of Cline Library over 23 years, she feels fortunate to have become a staff member of Special Collections and Archives where she is surrounded by fascinating history, inspired by incredible coworkers, and encouraged by the aspirations of future archivists. Sam(antha) Meier is the Archivist for Discovery at Cline Library Special Collections and Archives, where she oversees arrangement and description of the department?s archival collections. Prior to coming to Cline Library, Sam worked as an archival technician with the Veterans History Project of the Library of Congress and as a contract archivist with the Union of B.C. Indian Chiefs Library & Archives. She received her Masters in Archival Studies, First Nations Curriculum Concentration, from the University of British Columbia in 2018. Who should attend: Anyone interested in implementing the Protocols for Native American Archival Materials, using ArchivesSpace to facilitate redescription of legacy finding aids or assessing archival backlog, or anyone managing graduate students and interns performing core functions in ArchivesSpace. Applications now open - ArchivesSpace Member Match Program Applications are now open for the ArchivesSpace Member Match program. The Member Match program is an initiative to engage the ArchivesSpace membership community, created and organized by the Member Engagement sub-team of the ArchivesSpace User Advisory Council, with support from the ArchivesSpace Community Engagement Coordinator. The program is intended to be a resource and venue for peer-to-peer support between ArchivesSpace members. For one, year-long term, participants will be matched with a member with whom they can receive and offer professional insight, advice, and comradery. The program will also offer participants the opportunity to engage in exclusive events and enlightening discussions about ArchivesSpace and its active user community. Eligibility Any individual affiliated with an ArchivesSpace member organization is eligible to participate in the ArchivesSpace MemberMatch program and there is no limit to the number of individuals from a member organization that may participate. If you are unsure of your organization?s ArchivesSpace membership status, visit https://archivesspace.org/community/whos-using-archivesspace or email ArchivesSpaceHome at lyrasis.org. To Apply There is a short application to complete at https://airtable.com/shr1nE3RWpR7Y78En. Applications should be submitted by April 30. Applicants will be notified of their matches no later than June 30. To Learn More Visit the Member Match wiki: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program The ArchivesSpace Member Engagement Sub-team conducted an informational webinar on March 10th. You can find a link to the recording of this webinar on the Member Match wiki. Please feel free to direct any questions to ArchivesSpaceHome at lyrasis.org -Sent on behalf of the ArchivesSpace Member Engagement sub-team Kate Blalack, American Song Archive Regina Carra, American Folk Art Museum Bailey Hoffner, University of Oklahoma Ashley Knox, University of North Carolina Wilmington Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory Council Chair Jessica Crouch, ArchivesSpace Community Engagement Coordinator Thank You for a Successful 3rd Annual ArchivesSpace Online Forum! Thank you to everyone who presented, led a discussion, taught a workshop or attended the 3rd Annual ArchivesSpace Online Forum this week! Recordings, presentation slides and other resources will be added to the forum wiki in the coming days at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2146992129/ArchivesSpace+Online+Forum+2021. In the meantime, please take a moment to complete the Online Forum evaluation at https://www.surveymonkey.com/r/FRW83SL to let us know what you liked about the forum and what we can do differently to improve future ArchivesSpace events. And a special congratulations to the winners of Monday?s first ever game of ArchivesSpace themed trivia! The winners of the fabulous ArchivesSpace prizes and bragging rights are Noah Huffman of Duke University and Miloche Kottman of University of Kansas! Congratulations to you both! Call for Nominations for ArchivesSpace Governance Groups The ArchivesSpace Governance Board is seeking nominations to fill vacancies on three ArchivesSpace Governance Groups: the Governance Board, the Technical Advisory Council (TAC), and the User Advisory Council (UAC). Self-nominations and nominations by others are welcome. Please submit nominations via the form at https://forms.gle/m2nN49M34CPgnvci9. Nominations must be received by 9:00 p.m. EDT on Friday, April 23, 2021. The Nominating Committee will review all nominations and recommend candidates and appointments to the Governance Board for their approval. Please feel free to reach out Nominating Committee Chair Gordon Daines (gordon_daines at byu.edu) or Christine Di Bella, ArchivesSpace Program Manager, at christine.dibella at lyrasis.org with any questions. Membership Update We are excited to welcome our newest members to our community! Our new members since February 28 include: * College of Saint Benedict/Saint John?s University (Collegeville, MN) * Public Library of Brookline (Brookline, MA) * Wyoming State Archives (Cheyenne, WY) As of March 31, we have 421 General members, 21 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22469 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29061 bytes Desc: image002.jpg URL: From buschedw at msu.edu Wed Mar 31 13:51:35 2021 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 31 Mar 2021 17:51:35 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Message-ID: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> When I do Generate PDF for a particular Resource, the job fails. This resource has added Preservica content in External Documents, Notes and added DOs. I?m suspecting something in one of those fields is causing the problem. I?ve attached the EAD export. Here?s the error list: Generating PDF for College of Arts and Letters records Internal error evaluating template rule at line 123 in module file:/archivesspace/stylesheets/as-ead-pdf.xsl net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371) net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533) net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746) net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293) org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514) org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755) org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200) org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen) RUBY.invocation_lambda(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270) org.jruby.RubyProc.call(org/jruby/RubyProc.java:291) org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen) RUBY.to_destination(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73) RUBY.to_fo(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44) RUBY.to_pdf(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8 Any suggestions? Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: UA.15.9_20210331_175003_UTC__ead.xml Type: application/xml Size: 153910 bytes Desc: UA.15.9_20210331_175003_UTC__ead.xml URL: From barbara.benedett at curtis.edu Wed Mar 31 13:59:39 2021 From: barbara.benedett at curtis.edu (Benedett, Barbara) Date: Wed, 31 Mar 2021 17:59:39 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? In-Reply-To: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> References: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> Message-ID: Hi Ed, I just tested one of ours that has the Preservica-generated External document note and it was successful. I'll try a few others and see if I can recreate your issue. Barbara J. Benedett, CA, DAS Digital Archivist | Rock Resource Center 1720 Locust Street, Philadelphia, PA 19103 (215) 717-3139 Phone | (215) 893-9065 Fax | barbara.benedett at curtis.edu [1485183964799_Signature] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed Sent: Wednesday, March 31, 2021 1:51 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? When I do Generate PDF for a particular Resource, the job fails. This resource has added Preservica content in External Documents, Notes and added DOs. I?m suspecting something in one of those fields is causing the problem. I?ve attached the EAD export. Here?s the error list: Generating PDF for College of Arts and Letters records Internal error evaluating template rule at line 123 in module file:/archivesspace/stylesheets/as-ead-pdf.xsl net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371) net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533) net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746) net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293) org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514) org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755) org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200) org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen) RUBY.invocation_lambda(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270) org.jruby.RubyProc.call(org/jruby/RubyProc.java:291) org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen) RUBY.to_destination(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73) RUBY.to_fo(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44) RUBY.to_pdf(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8 Any suggestions? Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-1485183964.jpg Type: image/jpeg Size: 3608 bytes Desc: Outlook-1485183964.jpg URL: From buschedw at msu.edu Wed Mar 31 14:24:04 2021 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 31 Mar 2021 18:24:04 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? In-Reply-To: References: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> Message-ID: <6B2DA6D4-08A4-4E19-BC24-593A74FC0A11@msu.edu> Just curious, in the Preservica added Notes in their Subnote Text content do you have them begin with he/him/his From: on behalf of "Benedett, Barbara" Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Wednesday, March 31, 2021 at 1:59 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Hi Ed, I just tested one of ours that has the Preservica-generated External document note and it was successful. I'll try a few others and see if I can recreate your issue. Barbara J. Benedett, CA, DAS Digital Archivist | Rock Resource Center 1720 Locust Street, Philadelphia, PA 19103 (215) 717-3139 Phone | (215) 893-9065 Fax | barbara.benedett at curtis.edu [1485183964799_Signature] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed Sent: Wednesday, March 31, 2021 1:51 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? When I do Generate PDF for a particular Resource, the job fails. This resource has added Preservica content in External Documents, Notes and added DOs. I?m suspecting something in one of those fields is causing the problem. I?ve attached the EAD export. Here?s the error list: Generating PDF for College of Arts and Letters records Internal error evaluating template rule at line 123 in module file:/archivesspace/stylesheets/as-ead-pdf.xsl net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371) net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533) net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746) net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293) org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514) org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755) org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200) org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen) RUBY.invocation_lambda(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270) org.jruby.RubyProc.call(org/jruby/RubyProc.java:291) org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen) RUBY.to_destination(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73) RUBY.to_fo(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44) RUBY.to_pdf(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8 Any suggestions? Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3609 bytes Desc: image001.jpg URL: From blake.carver at lyrasis.org Wed Mar 31 14:33:44 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 31 Mar 2021 18:33:44 +0000 Subject: [Archivesspace_Users_Group] Issues with MySQL v8 In-Reply-To: References: Message-ID: There are others running on 8, so far the only trouble seems to be reports. Here's a JIRA https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200 You're seeing it fail on two reports? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Wendy Scheir Sent: Tuesday, March 30, 2021 4:15 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Issues with MySQL v8 Hi, When we installed ArchivesSpace last summer, we used MySQL v8 for our database. The documentation has instructions that read, "if using for MySQL 8+..." leading us to believe that MySQL 8 was a supported version. However, we've been having issues running Accession and Shelflist reports that the Lyrasis team has told us is caused by running MySQL 8 instead of MySQL 5. In the interim, Lyrasis has updated the documentation to say that "ArchivesSpace is currently able to run on MySQL version 5.x." Has anyone else installed ArchivesSpace with MySQL 8? We are concerned about downgrading to 5 versus waiting for a future version that works with 8, but in the meantime we are unable to run a number of desired reports. Many thanks, Wendy ____________________________________ WENDY SCHEIR DIRECTOR [https://docs.google.com/uc?export=download&id=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o&revid=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ] 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From barbara.benedett at curtis.edu Wed Mar 31 14:37:33 2021 From: barbara.benedett at curtis.edu (Benedett, Barbara) Date: Wed, 31 Mar 2021 18:37:33 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? In-Reply-To: <6B2DA6D4-08A4-4E19-BC24-593A74FC0A11@msu.edu> References: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> , <6B2DA6D4-08A4-4E19-BC24-593A74FC0A11@msu.edu> Message-ID: Hi Ed, Mine begin with [1485183964799_Signature] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed Sent: Wednesday, March 31, 2021 2:24 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Just curious, in the Preservica added Notes in their Subnote Text content do you have them begin with &fb978c72-bce5-4d04-b69b-762891c683b4 Just wild guessing right now. Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his From: on behalf of "Benedett, Barbara" Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Wednesday, March 31, 2021 at 1:59 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Hi Ed, I just tested one of ours that has the Preservica-generated External document note and it was successful. I'll try a few others and see if I can recreate your issue. Barbara J. Benedett, CA, DAS Digital Archivist | Rock Resource Center 1720 Locust Street, Philadelphia, PA 19103 (215) 717-3139 Phone | (215) 893-9065 Fax | barbara.benedett at curtis.edu [1485183964799_Signature] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed Sent: Wednesday, March 31, 2021 1:51 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? When I do Generate PDF for a particular Resource, the job fails. This resource has added Preservica content in External Documents, Notes and added DOs. I?m suspecting something in one of those fields is causing the problem. I?ve attached the EAD export. Here?s the error list: Generating PDF for College of Arts and Letters records Internal error evaluating template rule at line 123 in module file:/archivesspace/stylesheets/as-ead-pdf.xsl net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371) net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533) net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746) net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293) org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514) org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755) org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200) org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen) RUBY.invocation_lambda(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270) org.jruby.RubyProc.call(org/jruby/RubyProc.java:291) org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen) RUBY.to_destination(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73) RUBY.to_fo(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44) RUBY.to_pdf(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8 Any suggestions? Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3609 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-1485183964.jpg Type: image/jpeg Size: 3608 bytes Desc: Outlook-1485183964.jpg URL: From mkottman at ku.edu Wed Mar 31 14:47:35 2021 From: mkottman at ku.edu (Kottman, Miloche) Date: Wed, 31 Mar 2021 18:47:35 +0000 Subject: [Archivesspace_Users_Group] merge agent/subject records operation not working In-Reply-To: References: Message-ID: It's probably a matter of permissions. Besides the merge agent/subject records permission you will definitely need the ability to create/update/deleted agent and subject records. I wouldn't be surprised if you'll also need the ability to create/updated accessions, resources and digital objects in the repository too (since ASpace is relinking these records behind the scenes). You also might need the ability to create and run background jobs. You can add permissions and then tweak after you get it working. --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Daniel Sprouse Sent: Wednesday, March 31, 2021 11:09 AM To: Archivesspace Users Group Cc: Brian Thomas Subject: [Archivesspace_Users_Group] merge agent/subject records operation not working merge agent/subject records operation not working We created a group to allow an individual to 'merge agent/subject records' and while the button shows up, the behavior is not what we expected: "I do have the Merge button now and I get to the Merge Preview to compare the two. However, when I click on the Merge button in the Merge Preview it just spins. When it stops I am still in the Merge Preview. The two agent names have not been merged." This is the only group the user is a member of, and we have restarted the archivesspace application and retested her ability to perform the merge operation. Anyone have any ideas on how to make this work? Thanks, Daniel Sprouse Linux Admin Texas State Library and Archives Commission -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Wed Mar 31 14:49:22 2021 From: scheirw at newschool.edu (Wendy Scheir) Date: Wed, 31 Mar 2021 14:49:22 -0400 Subject: [Archivesspace_Users_Group] Issues with MySQL v8 In-Reply-To: References: Message-ID: Hi Blake, Thanks so much for following up. So far, we've gotten report errors for the following 3 accessions reports: - Accession Report - Accession Receipt Report - Accessions and Linked Subjects, Names and Classifications I'm not sure if we've tested all of them, but definitely these 3 are erroring out. If you'd like to look at the error logs, I'd be glad to send them to you. All best, Wendy ____________________________________ WENDY SCHEIR *DIRECTOR* 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives On Wed, Mar 31, 2021 at 2:33 PM Blake Carver wrote: > There are others running on 8, so far the only trouble seems to be > reports. Here's a JIRA > > https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200 > You're seeing it fail on two reports? > > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Wendy Scheir > *Sent:* Tuesday, March 30, 2021 4:15 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Issues with MySQL v8 > > Hi, > > When we installed ArchivesSpace last summer, we used MySQL v8 for our > database. The documentation has instructions that read, "if using for MySQL > 8+..." leading us to believe that MySQL 8 was a supported version. However, > we've been having issues running Accession and Shelflist reports that the > Lyrasis team has told us is caused by running MySQL 8 instead of MySQL 5. > In the interim, Lyrasis has updated the documentation to say that > "ArchivesSpace is currently able to run on MySQL version 5.x." > > Has anyone else installed ArchivesSpace with MySQL 8? We are concerned > about downgrading to 5 versus waiting for a future version that works with > 8, but in the meantime we are unable to run a number of desired reports. > > Many thanks, > Wendy > > ____________________________________ > > WENDY SCHEIR > *DIRECTOR* > > 66 5TH AVENUE, NEW YORK, NY 10011 > scheirw at newschool.edu > > T 212.229.5942 x2888 > > Explore the Archives | Digital > Collections from the Archives > | New School Histories > | @tnsarchives > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Mar 31 14:57:17 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 31 Mar 2021 18:57:17 +0000 Subject: [Archivesspace_Users_Group] Issues with MySQL v8 In-Reply-To: References: , Message-ID: You can send them to me or attach them to that JIRA. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Wendy Scheir Sent: Wednesday, March 31, 2021 2:49 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Issues with MySQL v8 Hi Blake, Thanks so much for following up. So far, we've gotten report errors for the following 3 accessions reports: * Accession Report * Accession Receipt Report * Accessions and Linked Subjects, Names and Classifications I'm not sure if we've tested all of them, but definitely these 3 are erroring out. If you'd like to look at the error logs, I'd be glad to send them to you. All best, Wendy ____________________________________ WENDY SCHEIR DIRECTOR [https://docs.google.com/uc?export=download&id=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o&revid=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ] 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives On Wed, Mar 31, 2021 at 2:33 PM Blake Carver > wrote: There are others running on 8, so far the only trouble seems to be reports. Here's a JIRA https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200 You're seeing it fail on two reports? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Wendy Scheir > Sent: Tuesday, March 30, 2021 4:15 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Issues with MySQL v8 Hi, When we installed ArchivesSpace last summer, we used MySQL v8 for our database. The documentation has instructions that read, "if using for MySQL 8+..." leading us to believe that MySQL 8 was a supported version. However, we've been having issues running Accession and Shelflist reports that the Lyrasis team has told us is caused by running MySQL 8 instead of MySQL 5. In the interim, Lyrasis has updated the documentation to say that "ArchivesSpace is currently able to run on MySQL version 5.x." Has anyone else installed ArchivesSpace with MySQL 8? We are concerned about downgrading to 5 versus waiting for a future version that works with 8, but in the meantime we are unable to run a number of desired reports. Many thanks, Wendy ____________________________________ WENDY SCHEIR DIRECTOR [https://docs.google.com/uc?export=download&id=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o&revid=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ] 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives _______________________________________________ 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 buschedw at msu.edu Wed Mar 31 16:05:10 2021 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 31 Mar 2021 20:05:10 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? In-Reply-To: References: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> <6B2DA6D4-08A4-4E19-BC24-593A74FC0A11@msu.edu> Message-ID: <24C24651-F242-4CF1-81DF-9345B183D803@msu.edu> It could be also related to other content that was added for analog media (not Preservica). It looks like this one has been printed in a long time. Does anyone know if there is a correspondence between the PDF report error line and the line in an EAD export? Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his From: on behalf of "Benedett, Barbara" Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Wednesday, March 31, 2021 at 2:37 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Hi Ed, Mine begin with [1485183964799_Signature] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed Sent: Wednesday, March 31, 2021 2:24 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Just curious, in the Preservica added Notes in their Subnote Text content do you have them begin with &fb978c72-bce5-4d04-b69b-762891c683b4 Just wild guessing right now. Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his From: on behalf of "Benedett, Barbara" Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Wednesday, March 31, 2021 at 1:59 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? Hi Ed, I just tested one of ours that has the Preservica-generated External document note and it was successful. I'll try a few others and see if I can recreate your issue. Barbara J. Benedett, CA, DAS Digital Archivist | Rock Resource Center 1720 Locust Street, Philadelphia, PA 19103 (215) 717-3139 Phone | (215) 893-9065 Fax | barbara.benedett at curtis.edu [1485183964799_Signature] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed Sent: Wednesday, March 31, 2021 1:51 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? When I do Generate PDF for a particular Resource, the job fails. This resource has added Preservica content in External Documents, Notes and added DOs. I?m suspecting something in one of those fields is causing the problem. I?ve attached the EAD export. Here?s the error list: Generating PDF for College of Arts and Letters records Internal error evaluating template rule at line 123 in module file:/archivesspace/stylesheets/as-ead-pdf.xsl net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371) net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533) net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746) net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293) org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514) org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755) org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200) org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen) RUBY.invocation_lambda(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270) org.jruby.RubyProc.call(org/jruby/RubyProc.java:291) org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen) RUBY.to_destination(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73) RUBY.to_fo(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44) RUBY.to_pdf(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) RUBY.run(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8 Any suggestions? Ed Busch, MLIS Interim Head of University Archives and Historical Collections Electronic Records Archivist Conrad Hall, 943 Conrad Road, Room 101 East Lansing, MI 48824 517-884-6438 buschedw at msu.edu he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3609 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 3610 bytes Desc: image002.jpg URL: From sdm7g at virginia.edu Wed Mar 31 16:06:15 2021 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 31 Mar 2021 20:06:15 +0000 Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? In-Reply-To: <6B2DA6D4-08A4-4E19-BC24-593A74FC0A11@msu.edu> References: <6F37B284-C1AC-4608-9D57-6D51369EB47F@msu.edu> <6B2DA6D4-08A4-4E19-BC24-593A74FC0A11@msu.edu> Message-ID: <92560AD7-2500-4146-B440-757CA8B586CC@virginia.edu> It definitely doesn?t like those Preservica URLs. The staff PDF production goes thru 3 steps, and you can do them separately and manually to debug. [1] export EAD XML [2] Run XSLT processor on EAD with /stylesheets/as-ead-pdf.xsl xsl-fo stylesheet $ saxon -xsl:archivesspace/stylesheets/as-ead-pdf.xsl -s:UA.15.9_20210331_175003_UTC__ead.xml -o:fop.fo [3] Run FOP processor on output of xsl-fo stylesheet. $ fop fop.fo -pdf fop.pdf After an error on logo image (because I?m not in the right directory and didn?t pass a param so it can find it) And a bunch of warning in info messages that can be ignored, I get a whole series of errors like this: SEVERE: Error while rendering page 19 java.lang.IllegalStateException: java.net.URISyntaxException: Illegal character in scheme name at index 0: %3Ca%20href=%22https://us.preservica.com/explorer/explorer.html%23prop:7&de6cbfd3-5bdf-41d1-a313-e323698859f2%22%3EPreservica%20Internal%3C/a%3E at org.apache.fop.pdf.PDFFactory.getFileUri(PDFFactory.java:688) at org.apache.fop.pdf.PDFFactory.getTargetUri(PDFFactory.java:646) at org.apache.fop.pdf.PDFFactory.getExternalAction(PDFFactory.java:585) at org.apache.fop.render.pdf.PDFDocumentNavigationHandler.getAction(PDFDocumentNavigationHandler.java:173) at org.apache.fop.render.pdf.PDFDocumentNavigationHandler.renderLink(PDFDocumentNavigationHandler.java:107) at org.apache.fop.render.intermediate.IFRenderer.renderPage(IFRenderer.java:597) at org.apache.fop.area.RenderPagesModel.addPage(RenderPagesModel.java:123) at org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.finishPage(AbstractPageSequenceLayoutManager.java:316) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.finishPage(PageSequenceLayoutManager.java:243) at org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.makeNewPage(AbstractPageSequenceLayoutManager.java:287) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.makeNewPage(PageSequenceLayoutManager.java:192) at org.apache.fop.layoutmgr.PageBreaker.handleBreakTrait(PageBreaker.java:634) at org.apache.fop.layoutmgr.PageBreaker.startPart(PageBreaker.java:512) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.java:564) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.java:509) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.java:504) at org.apache.fop.layoutmgr.PageBreaker.doPhase3(PageBreaker.java:339) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:458) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:113) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:143) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:139) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:362) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:293) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116) at org.apache.fop.cli.Main.startFOP(Main.java:183) at org.apache.fop.cli.Main.main(Main.java:214) Caused by: java.net.URISyntaxException: Illegal character in scheme name at index 0: %3Ca%20href=%22https://us.preservica.com/explorer/explorer.html%23prop:7&de6cbfd3-5bdf-41d1-a313-e323698859f2%22%3EPreservica%20Internal%3C/a%3E at java.base/java.net.URI$Parser.fail(URI.java:2963) at java.base/java.net.URI$Parser.checkChars(URI.java:3134) at java.base/java.net.URI$Parser.checkChar(URI.java:3144) at java.base/java.net.URI$Parser.parse(URI.java:3159) at java.base/java.net.URI.(URI.java:855) at org.apache.fop.pdf.PDFFactory.getFileUri(PDFFactory.java:686) ... 39 more And searching for ?Preservica Internal? in the EAD, I see that some of those URLs are text strings: --

    These are photographs taken at the College of Arts and Letters Alumni Homecoming Tailgate tent.These are part of a larger group of College of Arts and Letters photographs that have an identifier beginning with A.2013.0031.

    Preservica Internal URL

    https://us.preservica.com/explorer/explorer.html#prop:4&0a205486-db11-445e-a49f-7c0c55ef8c63

     -- And others (which are the source of the problem) are DAO href attribute values that are character escaped     tags. Not sure how you?ve got this encoded in ArchivesSpace for it to export like this, but those are the values that need to be fixed. --

    ArtPrize Submissions: 2020-12-07

     -- ? Steve Majewski > On Mar 31, 2021, at 2:24 PM, Busch, Ed wrote: > > Just curious, in the Preservica added Notes in their Subnote Text content do you have them begin with     Content > https://us.preservica.com/explorer/explorer.html#prop:4 &fb978c72-bce5-4d04-b69b-762891c683b4 > > Just wild guessing right now. > > Ed Busch, MLIS > Interim Head of University Archives and Historical Collections > Electronic Records Archivist > Conrad Hall, 943 Conrad Road, Room 101 > East Lansing, MI 48824 > 517-884-6438 > buschedw at msu.edu > he/him/his > > > From: > on behalf of "Benedett, Barbara" > > Reply-To: "archivesspace_users_group at lyralists.lyrasis.org " > > Date: Wednesday, March 31, 2021 at 1:59 PM > To: "archivesspace_users_group at lyralists.lyrasis.org " > > Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? > > Hi Ed, > I just tested one of ours that has the Preservica-generated External document note and it was successful. I'll try a few others and see if I can recreate your issue. > > Barbara J. Benedett, CA, DAS > Digital Archivist | Rock Resource Center > 1720 Locust Street, Philadelphia, PA 19103 > (215) 717-3139 Phone | (215) 893-9065 Fax | barbara.benedett at curtis.edu > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Busch, Ed > > Sent: Wednesday, March 31, 2021 1:51 PM > To: archivesspace_users_group at lyralists.lyrasis.org > > Subject: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content? > > When I do Generate PDF for a particular Resource, the job fails. This resource has added Preservica content in External Documents, Notes and added DOs. I?m suspecting something in one of those fields is causing the problem. I?ve attached the EAD export. Here?s the error list: > > Generating PDF for College of Arts and Letters records > > Internal error evaluating template rule at line 123 in module file:/archivesspace/stylesheets/as-ead-pdf.xsl > > net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371 ) > > net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533 ) > > net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746 ) > > net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441 ) > > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498 ) > > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426 ) > > org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293 ) > > org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514 ) > > org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755 ) > > org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200 ) > > org.jruby.RubyKernel$INVOKER$s$send.call (org/jruby/RubyKernel$INVOKER$s$send.gen) > > RUBY.invocation_lambda(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270) > > org.jruby.RubyProc.call (org/jruby/RubyProc.java:291 ) > > org.jruby.RubyProc$INVOKER$i$call.call (org/jruby/RubyProc$INVOKER$i$call.gen) > > RUBY.to_destination(/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73) > > RUBY.to_fo(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44) > > RUBY.to_pdf(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58) > > RUBY.run (/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51) > > archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open (/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24) > > RUBY.run (/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14) > > archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8 > > Any suggestions? > > Ed Busch, MLIS > Interim Head of University Archives and Historical Collections > Electronic Records Archivist > Conrad Hall, 943 Conrad Road, Room 101 > East Lansing, MI 48824 > 517-884-6438 > buschedw at msu.edu > he/him/his > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3342 bytes Desc: not available URL: From sdm7g at virginia.edu Wed Mar 31 16:55:47 2021 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 31 Mar 2021 20:55:47 +0000 Subject: [Archivesspace_Users_Group] Issues with MySQL v8 In-Reply-To: References: Message-ID: <4C9A50A3-0872-484A-A3BB-5BEDD02676A0@virginia.edu> I?m running ArchivesSpace 2.8.1 under current MariaDB 10.5.9 and I?m not getting any errors on any of those reports. It?s our intention to support current versions of both MySQL and MariaDB, but not everything can be tested against every version, especially those reports. Wendy: are you getting the same error message reported in that JIRA issue? > https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200 Wendy and/or Blake: (I have a hunch) Can you try editing: archivesspace/reports/accessions/accession_names_subreport/accession_names_subreport.rb And in the line: role_id as function, quote the word function: 12c12 < role_id as function, --- > role_id as 'function', class AccessionNamesSubreport < AbstractSubreport def initialize(parent_report, accession_id) super(parent_report) @accession_id = accession_id end def query_string "select ifnull(ifnull(ifnull(name_person.sort_name, name_family.sort_name), name_corporate_entity.sort_name), 'Unknown') as name, role_id as function, relator_id as role from linked_agents_rlshp left outer join name_person on name_person.agent_person_id = linked_agents_rlshp.agent_person_id left outer join name_family on name_family.agent_family_id = linked_agents_rlshp.agent_family_id left outer join name_corporate_entity on name_corporate_entity.agent_corporate_entity_id = linked_agents_rlshp.agent_corporate_entity_id where accession_id = #{db.literal(@accession_id)}" end def fix_row(row) ReportUtils.get_enum_values(row, [:function, :role]) end end Or else replace it with this edited version: And then restart ArchivesSpace and try Accession reports again? Actually, more than a hunch now that I googled for this doc: https://dev.mysql.com/doc/refman/8.0/en/keywords.html#keywords-8-0-detailed-F And see: FUNCTION (R); became reserved in 8.0.1 Pretty sure that is the problem! ? Steve Majewski > On Mar 31, 2021, at 2:49 PM, Wendy Scheir wrote: > > Hi Blake, > > Thanks so much for following up. So far, we've gotten report errors for the following 3 accessions reports: > Accession Report > Accession Receipt Report > Accessions and Linked Subjects, Names and Classifications > > I'm not sure if we've tested all of them, but definitely these 3 are erroring out. If you'd like to look at the error logs, I'd be glad to send them to you. > > All best, > Wendy > ____________________________________ > WENDY SCHEIR > DIRECTOR > > 66 5TH AVENUE, NEW YORK, NY 10011 > scheirw at newschool.edu > T 212.229.5942 x2888 > Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives > > > On Wed, Mar 31, 2021 at 2:33 PM Blake Carver > wrote: > There are others running on 8, so far the only trouble seems to be reports. Here's a JIRA > https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200 > You're seeing it fail on two reports? > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Wendy Scheir > > Sent: Tuesday, March 30, 2021 4:15 PM > To: Archivesspace Users Group > > Subject: [Archivesspace_Users_Group] Issues with MySQL v8 > > Hi, > > When we installed ArchivesSpace last summer, we used MySQL v8 for our database. The documentation has instructions that read, "if using for MySQL 8+..." leading us to believe that MySQL 8 was a supported version. However, we've been having issues running Accession and Shelflist reports that the Lyrasis team has told us is caused by running MySQL 8 instead of MySQL 5. In the interim, Lyrasis has updated the documentation to say that "ArchivesSpace is currently able to run on MySQL version 5.x." > > Has anyone else installed ArchivesSpace with MySQL 8? We are concerned about downgrading to 5 versus waiting for a future version that works with 8, but in the meantime we are unable to run a number of desired reports. > > Many thanks, > Wendy > ____________________________________ > WENDY SCHEIR > DIRECTOR > > 66 5TH AVENUE, NEW YORK, NY 10011 > scheirw at newschool.edu > T 212.229.5942 x2888 > Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ > 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: accession_names_subreport.rb Type: text/x-ruby-script Size: 943 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3342 bytes Desc: not available URL: