Not using the PUI? Not using OAI, or Docs? If so, consider turning these services off in your configuration file. (e.g. AppConfig[:enable_docs] = false)
You are going to use the new PUI? Here are some things to consider before you launch this service:
...
- Do you want to suppress any of the seven links that are included in the primary navigation bar of the site?
- Do you have more than one repository? If not, consider removing the repositories option from your primary navigation row of links (e.g. AppConfig[:pui_hide][:repositories] = true)
- Do you have any digital object records ready to go? If not, suppress that link.
- Same for classification records, which are labelled "Record Groups" in the new public interface by default.
...
- If you're not going to configure the Request action button to work with an email client, or replace it with another plugin, like the Aeon plugin, then you should turn off this action button before going live. (e.g. AppConfig[:pui_page_actions_request] = false)
- .
- Want your site indexed by search engines? Of course you do! Once you're done testing your local configurations, be sure to update your robots.txt file so that the site can be crawled (and consider blocking craws on "/search?" pages and anything else you don't want to show up as a search result).
...
After you've launched, let the ArchivesSpace community know what works well in the interface and what doesn't. The public interface should evolve over time based on feedback from the community and your researchers. And please share any tips, tricks, or custom plugins that you decide to use with the community. Here's an example: https://github.com/hudmol/aspace_yale_pui
...