https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31161 --- Comment #18 from Ere Maijala <ere.maijala@helsinki.fi> --- (In reply to David Cook from comment #14)
(In reply to Ere Maijala from comment #13)
I think it's the only solution that would work without forementioned side-effects. It's important to report the records as deleted particularly since they might not have been suppressed before. And that'd be the case for practically every vanilla Koha instance harvested with OAI-PMH up until this change.
I'm glad to hear that you agree!
That said, there are use cases where OAI-PMH is used for non-opac functionality and suppressed records should be included just like before.
Do you have some use cases in mind?
Anything non-OPAC could qualify, e.g. a union catalog based on OAI-PMH. Or even an OPAC instance for staff use only.
For flexibility it should be possible to configure suppression per OAI-PMH set in addition to a default setting.
GetRecord isn't affected by sets, so are you thinking of a flag in the "oai_sets" data that would disable the suppression/hiding of records?
GetRecord response has header/setSpec to indicate which sets the record belongs to. It should reflect suppression by excluding a set where the record would be marked deleted. So if we have sets "all" and "opac", a suppressed record would only have <header><setSpec>all</setSpec></header>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.