[Koha-bugs] [Bug 19555] New: Some changes to records are not reflected in OAI-PMH
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Oct 31 17:20:29 CET 2017
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19555
Bug ID: 19555
Summary: Some changes to records are not reflected in OAI-PMH
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5 - low
Component: Web services
Assignee: koha-bugs at lists.koha-community.org
Reporter: magnus at libriotech.no
QA Contact: testopia at bugs.koha-community.org
The OAI-PMH server can take "from" and "until" dates, in which case it should
return records that were added or changed in the given date range:
/koha/oai.pl?verb=ListRecords&metadataPrefix=marcxchange&from=2017-10-26&until=2017-10-28
In current master, Koha uses biblioitems.timestamp to figure out which records
should be returned for a given timeframe:
http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=Koha/OAI/Server/ListBase.pm;h=0c7c56a13d7fcc977e5de5ff471059c9e32d7cfb;hb=HEAD#l63
This worked fine when the marcxml column was still in the biblioitems table.
Any change to the record would update the timestamp and it would be reflected
in OAI-PMH.
But then we yanked marcxml out of the biblioitems table, and moved it to
biblio_metadata.metadata. This means that biblioitems.timestamp only gets
updated when one of the MARC-fields that has its own column in biblioitems gets
updated. And this means that some changes are not reflected in OAI-PMH.
To verify:
- Open a record for editing in Koha
- Look at the row in biblioitems that corresponds to the record
- Change e.g. one of the subjects -> the timestamp is not updated
- Change e.g. the ISBN -> the timestamp IS updated
The solution that comes to my mind first is to:
- add a timestamp to the biblio_metadata table, and
- consider both biblioitems.timestamp and biblio_metadata.timestamp when
OAI-PMH decides what records to return
Opinions?
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list