EPrints Technical Mailing List Archive

Message: #08572


< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Antwort: OAI2 deleted vs destroyed records


CAUTION: This e-mail originated outside the University of Southampton.
This is exactly what we had to do at my previous institution; periodically we would run a full harvest from ePrints into Primo to clean up anything that had been deleted.


On Thu, 15 Apr 2021 at 16:12, Martin Braendle via Eprints-tech <eprints-tech@ecs.soton.ac.uk> wrote:
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


Inactive hide details for "Alan.Stiles via Eprints-tech" ---15/04/2021 16:57:04---CAUTION: This e-mail originated outside the U"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/


--

Iain Gray

Information Systems Manager

Library
Royal College of Art
Kensington Gore, London
SW7 2EU
E: iain.gray@rca.ac.uk
T: +44 (0)20 7590 4111
www.rca.ac.uk
twitter.com/rca
facebook.com/rca.london

logo