[Koha-bugs] [Bug 31161] OAI-PMH - Add ability to exclude suppressed records in output

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

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

--- Comment #27 from Ere Maijala <ere.maijala at helsinki.fi> ---
The thing is that an OAI-PMH provider should really have a publishing process
that handles everything needed to publish a set of records for harvesting and
keep it up to date. This would make it possible to:

1. Publish a set once in a format that makes harvesting blazing fast.
2. Update the set incrementally with changes in bibs and items.
3. Re-publish all if suppression rules change.
4. Take care of deletions when they affect the records that have been published
in the set. If a record has never been a part of a set, it doesn't need to be
returned even as deleted.
5. Ensure that a set doesn't change while harvesting (requires set versioning).

The obvious downside is that a publishing process is relatively heavy, and
keeping sets up to date in a near-real-time manner is more difficult. Also sets
published this way would require more database space.


--- 
Now to more practical stuff. The multiple endpoints idea works for me. I don't
think there's any other interoperable way if you need to have different rules.
You could also have several endpoints like 'internal/oai.pl', 'opac/oai.pl' and
'test/oai.pl', no problem. From the protocol point of view they'd just be
separate providers. However, they should also have separate OAI identifiers.
Things could go really bad if a harvester receives the same record from
multiple endpoints.

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