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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Jun 15 17:19:29 CEST 2016


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

--- Comment #31 from Frédéric Demians <frederic at tamil.fr> ---
> - Fixed date handling to use UTC as specs require.
> - Added support for second precision in time stamps.
> - Added support for marc21 metadata prefix as recommended in the guidelines
> (synonym for marcxml).
> - ListIdentifiers and ListRecords always return records in timestamp order
> (faster than biblionumber order with the new index).
> - Improved performance of database queries especially for large collections.

All good. I can see the SQL improvements, and immediate response time
improvement.

> - Unified functionality of ListRecords and ListIdentifiers to a common base
> class.

Good catch. It was stupid repeating convoluted code and queries in two
places.

> - 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
interesting to include items (include_items parameter) in order to have
homebranch and call number, but availability info is not required, so
resending the whole biblio+items when a transaction is done is not desirable.
I can't see any solution without adding a new 'datemodified' field to items
table, which would only by updated when non circulation-related info are
updated. 

Have you considered this point? Have you evaluated the impact of including
items with a Koha doing a lot of circulation?

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


More information about the Koha-bugs mailing list