[EP-tech] OAI2 deleted vs destroyed records

David R Newman drn at ecs.soton.ac.uk
Thu Apr 15 16:03:39 BST 2021


Hi Alan,

If previously live records have been completely removed rather than 
retired then you can expect bad things to happen.  If there is a 
specific privacy issue that means the record cannot even been retained 
in a restricted form (retired), then removing may be the only option.  
However, the need for this should be vanishingly small and therefore 
issues like you describe with Primo should be few a far between and may 
require manual intervention.

The error code idDoesNotExist is deliberately returned by EPrints OAI 
interface when a record is removed, as in effect the record never 
existed.  All I can suggest is that Primo should treat getting back 
idDoesNotExist the same as getting back an item that is marked as 
deleted.  Obviously, you may want to be a bit more careful about what to 
do when getting back idDoesNotExist, in case there is some error in the 
request that mangles the ID so it cannot be found.  I have no idea how 
Primo could be configured to do this but as far as I can tell EPrints is 
behaving as it should; reporting completely removed items as not 
existing whereas retired items are reported as 'Deleted'.

Regards

David Newman

On 15/04/2021 15:27, Alan.Stiles via Eprints-tech wrote:

> *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: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cefdfef4565d241a87b6f08d9001fa815%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637540958475749542%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SvgF0bDebCjBdWdLMNn2iRKLermBmIZS6tdgYyp4IQA%3D&reserved=0
> *** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cefdfef4565d241a87b6f08d9001fa815%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637540958475749542%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DfYcw6RwjrZnGvll%2FP77ZTyKI4f4MrMMKAENGQLBiNs%3D&reserved=0


-- 
This email has been checked for viruses by AVG.
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cefdfef4565d241a87b6f08d9001fa815%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637540958475749542%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=A5EicB31YlNV%2BVta5iPS9CwABNNE0Ekd1%2B2WGw%2BQzzw%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20210415/0a69223d/attachment-0001.html 


More information about the Eprints-tech mailing list