[Koha-bugs] [Bug 27463] OAI-PMH date handling in ListBase.pm

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

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

--- Comment #2 from Rudolf Byker <rudolfbyker at gmail.com> ---
Good point, David. I did not notice that, since our library only operates in
one time zone.

Please also note that I forgot to join on the deleteditems table in the "select
... greatest( ... from ..." example query above. It should probably be
something like this (untested):

SELECT bm.biblionumber, GREATEST(bm.timestamp, i.timestamp, di.timestamp) AS t
FROM biblio_metadata bm INNER JOIN items i ON bm.biblionumber=i.biblionumber
INNER JOIN deleteditems di ON bm.biblionumber=di.biblionumber HAVING t >=
'2020-07-14' AND t <= '2020-07-15' LIMIT 10;

One more thing I would like to mention: There was some Koha update in July 2020
(See discussion http://irc.koha-community.org/koha/2021-01-18#i_2324154 ) which
modified thousands of items to have the exact same timestamp. This is
problematic for users with the "include_items" option set in OAI-PMH. This is
not something we can fix for people who already applied that update, but it's
tangentially relevant to this bug. We should be careful when mass-updating
items or records, because when all of them have the same date, not matter how
small your OAI-PMH resolution, you will have to harvest all of them at once at
some point.

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