[Koha-bugs] [Bug 19555] Some changes to records are not reflected in OAI-PMH

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19555

--- Comment #7 from Magnus Enger <magnus at libriotech.no> ---
My patch just adds timestamp columns to biblio_metadata and
deletedbiblio_metadata. This means the timestamps in those columns will be
0000-00-00 00:00:00. 

Possible things to do:

1. One thing we could do is copy over data from biblioitems.timestamp to
biblio_metadata.timestamp. That would give us non-zero values, but those values
would still be as wrong as the values in biblioitems.timestamp are. 

2. One step further, at least for MARC21, would be to extract the date from 005
and put that in biblio_metadata.timestamp. That should give pretty accurate
timestamps, as long as the value in 005 makes sense. 

3. The problem with both 1 and 2 is that some biblio_metadata.timestamps will
be way back in time. If a client does a harvest like
verb=ListRecords&metadataPrefix=marcxchange&from=2017-10-26&until=2017-11-02 to
pick up the most recent changes, those records with old timestamps will still
not be picked up. So the best solution is perhaps to set
biblio_metadata.timestamp to the value of 005, BUT when that timestamp is more
recent than biblioitems.timestamp, set biblio_metadata.timestamp to NOW(), so
that a harvest of "recent updates" will catch all these old changes. 

Should we put this in the databaseupdate, or is it too complex? Is it better to
have a note in the databaseupdate pointing to a page on the wiki that details
these options and lets the user/admin choose which one they want?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.