Hi everyone, our issue persists with our PUI not connecting components to collection-level records. Our sys admin attempted to identify where the data/indexing issue might lie, using the ASpace data checker plugin: https://github.com/hudmol/asck , and he asked me to query the list to ask what type of log entries we should be looking for in logs/archivesspace.out since he didn't see that in the documentation. I'm the go-between here, so I hope this query makes sense, and thank you for considering it.
Lisa +++++++++++++++++++++ Lisa Conathan Head of Special Collections Williams College Libraries 413-597-2930 On Mon, Nov 6, 2017 at 1:11 PM, Conathan, Lisa <[email protected]> wrote: > Hi everyone, > > Williams College is running 2.2.0 and we have two repositories publishing > to the PUI <http://archivesspace.williams.edu:8081/>. One repository is > displaying resource records correctly, and the other > <http://archivesspace.williams.edu:8081/repositories/4/resources?> is > displaying only collection-level information (no collection organization, > no container list on the right side of the screen). Components also do not > display in the container inventory. We've double checked that everything is > published, reindexed, and rebooted. We experienced this previously, and > then the problem resolved with one of the patches, and now has re-appeared. > Anyone know why we might be having this problem with just one of our > repositories and what we might try to address it? > > Lisa > > +++++++++++++++++++++ > Lisa Conathan > Head of Special Collections > Williams College Libraries > 413-597-2930 <(413)%20597-2930> >
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
