As a repository manager, I want to control which sets are available for harvest via OAI-PMH
Description
Complexity
Attachments
Activity
Manny RodriguezJune 5, 2018 at 11:02 PM
PR submitted: https://github.com/archivesspace/archivesspace/pull/1265
Carolyn RunyonMarch 27, 2018 at 7:30 PM
Sure. Whatever you think is best.
Cory NimerMarch 27, 2018 at 7:25 PM
Providing broader configuration options for OAI-PMH would be great. During prioritization, there was some concern about conflating the set functionality adjustments with the staff interface changes. , would it be alright to break this into two tickets to cover each of these separately?
Carolyn RunyonMarch 14, 2018 at 2:41 PM
I'm attaching a crude mock up of my intention. In my repository's case, we're harvested by LYRASIS, and making backend adjustments is a little more difficult. By creating a mechanism on the staff user interface, I hope that other hosted repositories can easily control access to their OAI feeds. In our case, many of our file and item level components are just clutter in an OAI feed, and I'd like to remove them so that we focus our collections that include the fields required by DACS, for example. Since child components inherit the properties of their parents, this makes the OAI feed even more confusing, unless you are the rare repository that includes scope notes at every level of description.
Jason LoefflerNovember 9, 2017 at 8:04 PM
This needs to be evaluated more closely.
Staff interface configuration is unfortunately part of the original specification.
Not all levels of description are appropriate for harvest via OAI-PMH. Repository managers should be able to indicate, on an ArchivesSpace repository basis, which sets are made available for harvest via OAI-PMH. They should be able to do this via staff interface.