[Archivesspace_Users_Group] Containers not being associated with their resources

Tue Mar 2 04:21:08 EST 2021

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 
> <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of 
> Mark Cyzyk <mcyzyk at jhu.edu>
> *Sent:* Monday, March 1, 2021 5:18 PM
> *To:* Rachel Aileen Searcy <rachel.searcy at nyu.edu>; Archivesspace 
> Users Group <archivesspace_users_group at lyralists.lyrasis.org>
> *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  <mailto: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 
>> <https://github.com/archivesspace/tech-docs/blob/master/administration/indexes.md>, 
>> 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 <mcyzyk at jhu.edu 
>> <mailto:mcyzyk at jhu.edu>> 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 <mailto:mcyzyk at jhu.edu>
>>
>>     Verba volant, scripta manent.
>>
>>     _______________________________________________
>>     Archivesspace_Users_Group mailing list
>>     Archivesspace_Users_Group at lyralists.lyrasis.org
>>     <mailto: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=
>>     <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 <mailto: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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210302/9b1f3d11/attachment.html>