OAI-PMH service - suppressed records
As a default suppressed records are not included in the harvest stream. This becomes an issue when a harvested record later becomes suppressed in Sierra as the harvester does not know to remove it from its listings as its omission from the stream does not allow for identification of its suppressed state. I would recommend that the option to include suppressed records should be configurable as a harvest stream level, giving the library the ability to configure the inclusion/exclusion dependent on their business rules.
Chris Jones
shared this idea
In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Amanda Steen
commented
Absolutely needing this. We are unable to remove our holdings from the national system due to their being suppressed in Sierra.
We'll need to band aid the process by keeping deletions unsuppressed until after the harvest, which means double handling and inefficiencies.
Please fix this!! -
Adam Hornsey
commented
100% percent in support of this enhancement request.
While it might seem logical to not send suppressed records via OAI-PMH, there needs to be a way for records that become suppressed to be fed through.
We will have to come up with a workaround until this is fixed