Dear Marianne, It is possible to create a top container that is not linked to an accession or resource, or is linked to multiple accessions or resources. So the first thing to check is that you are not inadvertently doing this. The key is if you create the top container with an accession or resource, link it, but then do not save the accession record or resource record to preserve the link, the top container will be created but it won't have the association you're intending. To see this, in the sandbox (http://sandbox.archivesspace.org - user name is admin and password is admin) right now there's an example of a top container I did this with (its indicator is example 1). It is findable if I do an Unassociated containers search, but not otherwise. It's possible to rectify this by adding another instance to the accession or resource, selecting the Browse option in the top container field, and locating the top container you created before (doing an unassociated containers search). Once you save it to the record the link you're expecting will be there.
(Also in the sandbox is an example of a top container that is properly linked and saved to a resource (see http://sandbox.archivesspace.org/resources/12#tree::resource_12). Its indicator is example 2. As you can see by the blue representation (blue means a linked record in ArchivesSpace) of it in the instances area, it is linked.) If your top containers are showing the links you expect in the associated accessions or resources, the other culprit might be an indexing lag. Indexing can be dependent on a number of factors, both locally and within the application. Which version of ArchivesSpace are you using, and are you having problems locating any other types of records? Christine Christine Di Bella ArchivesSpace Program Manager [email protected] 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Marianne Swierenga Sent: Thursday, March 2, 2017 2:39 PM To: [email protected] Subject: [Archivesspace_Users_Group] Top containers are not being assigned to collection When adding a new top container instance to a collection, they are not assigned to the collection somehow, unlike the ones I created in the exact same way before. So when I search for them by resource in Manage Top Container, they do not come up. When I located them in Manage Top Container, they do not have a Resource/Accession listed. I feel like there is a quick fix out there but I don't understand why they are not linking in the first place. Thanks, Marianne -- Marianne Swierenga, MFA, MLIS Metadata and Digital Resources Specialist University Libraries (Waldo Library) Western Michigan University 1903 W. Michigan Ave. Kalamazoo MI 49008-5353 USA (269) 387-4112 _______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
