Trying this out on the ArchivesSpace test instance (test.archivesspace.org), when clicking on the Edit OAI Settings button on the Per Repository OAI-PMH Settings section of the OAI-PMH Settings page, I am getting a page not found error message. It appears that the link is pointing to http://test.archivesspace.org/repositories/2/edit#oai_settings, but at least on the test instance this is page is at http://test.archivesspace.org/staff/repositories/2/edit. Is this just a matter of configuration, or are the links incorrect?

PR submitted: https://github.com/archivesspace/archivesspace/pull/1346

I've been working through implementing this, and found that there are the three different types or levels of configuration options for OAI:

1. Sysadmin level: These options deal with server configuration need other sysadmin actions like firewall/web server changes to work, so these should stay in the config.rb file.

2. Repository level: These are options that control what is published from a given repo. These config options are set on the repository edit page.

3. General level: These are options that apply to the OAI service in general, like oai_record_prefix and oai_admin_email.

Based on this, here's how I've developed things so far:

oai_proxy_url, oai_url and enable_oai are sysadmin level and remain in the config.rb file.

oai_repository_name, oai_record_prefix and oai_admin_email are general level, so I've moved them out of the config.rb file and built out an interface under a new "Manage OAI-PMH Harvesting" item in the System menu to update them, as described in the spec.

Publishing and unpublishing sets defined by level of description was added in ANW-242, and the interface for this is on the repository edit form.

The addition of controls for records defined by LOD can be added to the repository edit form, alongside where the sets are visible.

This raises a possible UI design issue, since there are OAI controls in two places. I'm thinking the best way to move forward is adding some links to the OAI subforms on the repository edit page – mockups attached.

- this would build off of what you've already done for sets in the staff interface.