[Koha-bugs] [Bug 15108] OAI-PMH provider improvements

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

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

--- Comment #34 from Ere Maijala <ere.maijala at helsinki.fi> ---
(In reply to Frédéric Demians from comment #31)
> > - If items are included in the records, their timestamps are taken into
> > account everywhere so that whichever is the most recent (timestamp of
> > biblioitem or any of its items) is considered the record's timestamp.
> 
> I approve this. It can be interesting to send back to the harvester items
> info
> when items are modified in Koha. But it could also have a huge impact on the
> quantity of records returned by incremental harvesting. Any circulation
> transaction modify items.timestamp. So for libraries doing a lot of
> circulation, harvester will have to harvest a lot of records just for the
> 'due
> date' field or other circulation related fields. In some scenario, it may be

I did consider it but I left it out for now since from our point of view any
change in the data that's included in a harvested record should make the record
be reharvested since you can't know what data the harvester finds important.

That said, if you think there should be an option to control whether item
timestamps are taken into account, I can add that. But you're right in that if
you'd like to only ignore status changes caused by circulation actions, that's
not possible without changes deeper in the system.

Additionally we need to take into account floating collections that would cause
item's location to change on checkin. I'm really an outsider to Koha (mainly a
VuFind developer), so I'm not sure how everything works in practice, so I
apologize if what I say doesn't make sense or use the correct terminology.

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