[Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH

[Angela Kroeger]

Andrew asked, "do you have different rulesets in Primo for each repository in ArchivesSpace?"

No. Is that actually possible?

As your open ticket with ArchivesSpace notes, you can only create a single OAI-PMH set in ArchivesSpace, so we can't have separate sets for reach repository. If we could, then we probably would have separate import profiles for each repository.

Is there another way in Primo VE to latch onto a single repository from an ArchivesSpace instance, without using the repository set from ArchivesSpace?

--Angela

Angela Kroeger
Metadata Coordinator
Archives and Special Collections
UNO Libraries | Criss Library 107
University of Nebraska at Omaha | unomaha.edu

402.554.4159
akroeger at unomaha.edu<mailto:akroeger at unomaha.edu>
They | Them | Their

[cid:b9f96028-fe49-46b9-bb8b-6ddb1d02f2ab]

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk>
Sent: Thursday, August 4, 2022 6:29 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH

Non-NU Email
________________________________
There is an open issue for this:


https://archivesspace.atlassian.net/browse/ANW-1339<https://urldefense.com/v3/__https://archivesspace.atlassian.net/browse/ANW-1339__;!!PvXuogZ4sRB2p-tU!FzaE2g4uCAarnB6KcYTRFCCZ39jItD56BwX7OfLMGqupoOVVaBg3o3wDTwKdHOFIHORO3WL2gTpk9rrgB01H1P4f0SqweJwrHwaWiQ$>


It would probably be helpful to detail your use-case there (e.g. do you have different rulesets in Primo for each repository in ArchivesSpace?)


Andrew.




On 03/08/2022 16:51, Angela Kroeger wrote:
Thank you, Andrew and Andy, for the additional information about how ArchivesSpace presents suppressed and deleted records. It seems that part of the issue is on the ArchivesSpace side and part of it is on the Primo VE side.

Based on advice I got on the Alma-L list, I deleted all ArchivesSpace records from Primo VE, then reloaded from scratch. The new load didn't include the suppressed records, so that resolved that particular issue. (This is a manual process that I will need to do periodically.)

However, the process of discovering this solution led me to a much bigger problem.

A colleague at another institution in my consortium was told they couldn't load their ArchivesSpace records into Primo VE because they don't have their own ArchivesSpace instance. I went into our shared ArchivesSpace instance and changed repositories to see this other institution's OAI-PMH settings, and was surprised/horrified to see that the settings I had believed were specific to our repository are in fact global settings. So the repository set I created for my institution blocks other members of the consortium from loading their ArchivesSpace repositories into Primo VE, and if anyone changes the repository set to work with their records, it will break my institution's loads.

I'm afraid the answer will be no, but I'll ask anyway:

Is there any way to create more than one repository set in the ArchivesSpace OAI-PMH settings? Looking at it, all I can see is "Update OAI-PMH Settings" which would wipe out the previous set.

Why is "repository set" a global setting and not down in the "per repository" settings?

Thank you!

--Angela

Angela Kroeger
Metadata Coordinator
Archives and Special Collections
UNO Libraries | Criss Library 107
University of Nebraska at Omaha | unomaha.edu

402.554.4159
akroeger at unomaha.edu<mailto:akroeger at unomaha.edu>
They | Them | Their


[cid:part1.JqRw517S.hvsVdJ7d at bodleian.ox.ac.uk]



_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!PvXuogZ4sRB2p-tU!FzaE2g4uCAarnB6KcYTRFCCZ39jItD56BwX7OfLMGqupoOVVaBg3o3wDTwKdHOFIHORO3WL2gTpk9rrgB01H1P4f0SqweJym4PoIUw$>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220804/fa7b282e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-3mejvx3t.png
Type: image/png
Size: 5582 bytes
Desc: Outlook-3mejvx3t.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220804/fa7b282e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-erv2qa2s.png
Type: image/png
Size: 5582 bytes
Desc: Outlook-erv2qa2s.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220804/fa7b282e/attachment-0001.png>