Closed GoogleCodeExporter closed 9 years ago
The following note from Chris Delis.
There are good reasons to keep "deleted" data around, such as for use by cached
IndexedReaders. They may need to access this content while serving "old"
(which is a very relative term meaning "older than when the repo changed")
harvests.
Original comment by rc...@library.rochester.edu
on 8 Aug 2011 at 4:30
Not sure i understand the cached IndexReaders piece. No matter, the concern I
wish to raise is that if a library removes a record from their ILS (which they
might do for any number of reasons), the OAI Toolkit should remove the records
payload from it's repository as well. Deleted records in the OAI toolkit can
include "suppressed" records, and it might be the case that the library does
not want that content to be hiding in another program somewhere.
My second question is, when you harvest a set of records from the OAI toolkit,
and some of them are marked deleted, do those records have the previous records
content? This could be an issue since any harvester can come along and grab
those records, and have access to the content (that a library might not want
shared). I thought we wanted to create EMPTY records for the marked deleted
ones.
Original comment by DavidLin...@gmail.com
on 24 Aug 2011 at 4:06
No, the deleted records do not reveal the payload of the record, e.g.,
<?xml version="1.0" encoding="UTF-8" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
<responseDate>2011-08-24T16:18:32Z</responseDate>
<request verb="ListRecords" from="2011-08-24T11:10:30-0500" metadataPrefix="marc21">http://localhost:8080/OAIToolkit/oai-request.do</request>
<ListRecords><record><header
status="deleted"><identifier>oai:carli.illinois.edu:CARLIVoyager1/250951</identi
fier><datestamp>2011-08-24T16:15:41Z</datestamp><setSpec>bib</setSpec></header><
/record></ListRecords>
</OAI-PMH>
Original comment by cede...@uillinois.edu
on 24 Aug 2011 at 4:19
Original issue reported on code.google.com by
rc...@library.rochester.edu
on 3 Mar 2010 at 9:27