https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25246 --- Comment #13 from David Roberts <david.roberts@ptfs-europe.com> --- (In reply to David Cook from comment #11)
(In reply to David Roberts from comment #10)
We could have used OAI but there is at least one limitation, the main one being that EBSCO can't handle the deletions. Although we tag records as "deleted" in the OAI xml, EBSCO don't/can't use that. They asked us to set position 5 of the leader (000) to "d". However, Koha doesn't do this automatically so it would mean manually editing the record each time which is impractical. I guess the other option would be to write another patch to set position 5 on deletion. So, unless you know another way of handling the deletions, the export script is still our preferred method.
That's an interesting point! We've certainly encountered that obstacle with EBSCO.
However, how are deletions handled with your export script? It looks to me like you're just exporting the full set of bib records on each export, which would be functionally equivalent to them re-harvesting the whole collection using OAI-PMH. That said, it would be much less intensive to generate 1 export to FTP than requiring EBSCO to do X number of HTTP requests to get the same result.
We send the full export each month, and EBSCO are happy to delete the current data that they have and replace it with the new export. -- You are receiving this mail because: You are watching all bug changes.