<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
Thanks, Rachel!<br>
<br>
I've now completely reindexed everything (a "hard reindex") and
still no joy. <br>
<br>
I am noticing there is no "location.dat" file in our
/indexer_pui_state/:<br>
<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
3_archival_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
3_classification.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
3_classification_term.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
3_digital_object_component.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
3_digital_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
3_resource.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
4_archival_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
4_classification.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
4_classification_term.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
4_digital_object_component.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
4_digital_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
4_resource.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
5_archival_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
5_classification.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
5_classification_term.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
5_digital_object_component.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
5_digital_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
5_resource.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
_deletes_deletes.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13
repositories_repositories.dat<br>
<br>
Should there be?<br>
<br>
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.<br>
<br>
It's like something in the backend DB has become disconnected, but
just for these two repositories. Not sure how.<br>
<br>
If anyone has any suggestions, I would greatly appreciate hearing
them!<br>
<br>
Mark<br>
<br>
<pre class="moz-signature" cols="72"><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
<a class="moz-txt-link-abbreviated" href="mailto:mcyzyk@jhu.edu">mcyzyk@jhu.edu</a>
Verba volant, scripta manent.
</pre>
<div class="moz-cite-prefix">On 2/24/21 11:11 AM, Rachel Aileen
Searcy wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGFAsrNkx4tGoKbMWOvxi+OQYY79E-nsHNUZumpEcjHd7X3PCw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Mark</div>
<div><br>
</div>
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 <a
href="https://github.com/archivesspace/tech-docs/blob/master/administration/indexes.md"
moz-do-not-send="true">soft re-index</a>, 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.<br>
<div><br>
</div>
<div>I'm not sure if this is exactly what you're experiencing,
but I hope it's helpful. Take care,</div>
<div>Rachel</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Feb 22, 2021 at 5:45
PM Mark Cyzyk <<a href="mailto:mcyzyk@jhu.edu"
moz-do-not-send="true">mcyzyk@jhu.edu</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Dear ASpace list,<br>
<br>
From one of our Archivists:<br>
<br>
> When I create a new container, either manually or by
spreadsheet <br>
> ingest, the container appears properly in the Instance
field of the <br>
> record. From the resource, I can open the container
record and it <br>
> appears to be associated with the resource correctly.
However, in the <br>
> container management module, when I search for all
containers <br>
> associated with the collection, the recently created
container is not <br>
> listed. If I search for the new container's barcode, the
container <br>
> appears in the search results but with no associated
resource. I can <br>
> also locate the new containers by searching for
unassociated containers.<br>
<br>
It seems like some linkage is not happening here.<br>
<br>
More, this is only happening in his Repository, not our other,
larger <br>
Repository.<br>
<br>
Has anyone else run into this?<br>
<br>
Mark<br>
<br>
-- <br>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><br>
Mark Cyzyk, M.A., M.L.S.<br>
Library Applications Group<br>
The Sheridan Libraries<br>
The Johns Hopkins University<br>
<a href="mailto:mcyzyk@jhu.edu" target="_blank"
moz-do-not-send="true">mcyzyk@jhu.edu</a><br>
<br>
Verba volant, scripta manent.<br>
<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a
href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org"
target="_blank" moz-do-not-send="true">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a
href="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="
rel="noreferrer" target="_blank" moz-do-not-send="true">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=</a>
<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Rachel Searcy<br>
Accessioning Archivist, Archival Collections
Management<br>
<div><span style="font-size:12.8px">New York
University Libraries</span><br>
</div>
<div><a value="+12129982631"
moz-do-not-send="true">212.998.2539</a> |
<a href="mailto:rachel.searcy@nyu.edu"
target="_blank" moz-do-not-send="true">rachel.searcy@nyu.edu</a>
<br>
</div>
</div>
<div>My pronouns are she/her/hers</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>