CAUTION: This e-mail originated outside the University of Southampton.

Hi Alan,

it's a Primo problem. This is one of the reasons why items that are in the "archive" should be moved to "deletion" and not be destroyed.
According to our experience, to sort this out, a full reharvest must be done by the Primo Harvester to remove the destroyed items in the Primo data.

Kind regards,

Martin

--
Dr. Martin Brändle
Zentrale Informatik
Universität Zürich
Stampfenbachstr. 73
CH-8006 Zürich


"Alan.Stiles via Eprints-tech" ---15/04/2021 16:57:04---CAUTION: This e-mail originated outside the University of Southampton. Hi all,

Von: "Alan.Stiles via Eprints-tech" <eprints-tech@ecs.soton.ac.uk>
An: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
Datum: 15/04/2021 16:57
Betreff: [EP-tech] OAI2 deleted vs destroyed records
Gesendet von: <eprints-tech-bounces@ecs.soton.ac.uk>

---

CAUTION: This e-mail originated outside the University of Southampton.
Hi all,
I feel like there was a discussion about this here a year or two ago but I can’t find it now.
 
Records in our repository that get flagged as deleted show up in the OAI feed as ‘Deleted’, but records that get completely removed (destroyed) show up as error code ‘idDoesNotExist’.
 
It appears that Primo (our library search product) isn’t doing anything about updating records from the feed (configured within Primo to explicitly harvest our repository), at least where it’s getting the error response.
 
Any clues as to whether this is a Primo problem or my problem to sort out?
 
Cheers,
Alan*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/