We treated this as an ArchivesSpace bug. According tp openarchives.org,
"If a record is no longer available then it is said to be deleted."
ArchivesSpace only indicates that a record is deleted when it is
actually deleted from the database, not when it becomes suppressed
(contrary to what we believe it should).
We use Primo BackOffice, so I'm not familiar with VE. For our harvest,
we do a regular harvest twice daily, then once a week we run a Cleanup
(Delete DS and ReLoad) pipe, which effectively removes records that are
no longer in the ASpace OAI data stream, even without having an explicit
"delete" record.
Andy
On 8/2/2022 6:42 AM, Andrew Morrison wrote:
From my experience with Primo in a previous job, despite its many
flaws, it is unlikely to be the cause here.
There is an open issue with ArchivesSpace which may be relevant:
https://archivesspace.atlassian.net/browse/ANW-1301
Especially the comment I've just added.
I have no experience with Archive-It, but it declares only "transient"
(i.e. partial or inconsistent) support for deletions:
https://archive-it.org/oai?verb=Identify
Whereas ArchivesSpace declares "persistent" (i.e. full) support:
https://test.archivesspace.org/oai?verb=Identify
As suppressing/unpublishing records is distinct from deletion,
technically it is correct. But it is probably contrary to your
expectations, hence the solution (delete from Primo or get Ex Libris to
do it if you cannot) may be the same.
Andrew.
On 01/08/2022 19:14, Angela Kroeger wrote:
Thank you for the information, Sarah. Narrowing the issue down to the
Primo side is very helpful.
I'll ask on the Alma-L list to see if anyone has found a way to handle
this themselves, and if not, I'll open a support ticket with Ex Libris.
--Angela
*Angela Kroeger*
Metadata Coordinator
Archives and Special Collections
UNO Libraries | Criss Library 107
University of Nebraska at Omaha | unomaha.edu
402.554.4159
akroe...@unomaha.edu <mailto:akroe...@unomaha.edu>
They | Them | Their
------------------------------------------------------------------------
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org
<archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
Newhouse, Sarah <snewho...@sciencehistory.org>
*Sent:* Monday, August 1, 2022 9:19 AM
*To:* Archivesspace Users Group
<archivesspace_users_group@lyralists.lyrasis.org>
*Subject:* Re: [Archivesspace_Users_Group] Suppressed ArchivesSpace
records in OAI-PMH
Non-NU Email
------------------------------------------------------------------------
Hi Angela,
At my previous job we had a similar problem with Archive-It OAI
imports into PrimoVE. We had to go ask ExLibris to remove the records
from Primo as this was something we couldn’t do ourselves (!). I don’t
remember the details, as our cataloging librarian handled it, but I
think you should start with the assumption that this is a PrimoVE issue.
__________________________________
Sarah Newhouse /(she, her, hers)/
Digital Preservation Archivist
Othmer Library of Chemical History
t. +1.215.873.8249
*Science History Institute *
Chemistry • Engineering • Life Sciences
315 Chestnut Street • Philadelphia, PA 19106 • U.S.A.
Learn about the scientific discoveries that changed our world at
sciencehistory.org/learn
<https://urldefense.com/v3/__https://www.sciencehistory.org/learn__;!!PvXuogZ4sRB2p-tU!GryIw5n34sdnf-cdQaXeNgPCDvJAJJLlYcrEz2_MydtV65TnCNqxg2ShAvyM_zDUtqzUfG6dippIRXRUZPcNxHWCSCE$>
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org
<archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf
Of *Angela Kroeger
*Sent:* Monday, August 1, 2022 10:09 AM
*To:* ArchivesSpace Users Group
<archivesspace_users_group@lyralists.lyrasis.org>
*Subject:* [Archivesspace_Users_Group] Suppressed ArchivesSpace
records in OAI-PMH
I'm not sure if this is an ArchivesSpace issue or an Alma/Primo issue.
I'm starting with ArchivesSpace.
We have a hosted ArchivesSpace instance, with one repository set up to
expose resource records via OAI-PMH. On the other end, we have an Alma
discovery import profile set up to load these records into Primo VE.
(The records are only being loaded and displayed in the Primo VE
discovery layer; they are not being loaded into the Alma catalog.)
This has been running smoothly for many months.
Our new problem (or more likely an old problem that we never had the
opportunity to notice before) is that resource records that have been
unpublished and suppressed in ArchivesSpace are still showing up in
Primo VE.
I've looked at both the OAI-PMH settings in ArchivesSpace and the
discovery import profile in Alma/Primo, and I can't see any setting to
toggle inclusion/exclusion of suppressed records.
How can I prevent suppressed ArchivesSpace records from being exposed
for OAI-PMH harvesting?
Or is the problem on the Primo VE side, with it failing to remove
suppressed records?
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
akroe...@unomaha.edu <mailto:akroe...@unomaha.edu>
They | Them | Their
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
