[
https://jira.duraspace.org/browse/DS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24422#comment-24422 ]
Tim Donohue commented on DS-1142:
---------------------------------
Mark Diggory mentioned the following on 'dspace-devel':
"I'd actually rather see some documentation exposed at those points so that folks could actually get the access details for the service. For instance, parse the service document and offer examples neccessary for accessing the service."
This got me thinking that maybe all we need here is a custom 404 error page for each webapp? (I wouldn't go as far as parsing the service document or anything -- I'm talking very simple)
For example, for the 'SWORD' webapp, we could create a custom 404 error page (flat HTML or simple JSP/Servlet, no styling or anything) that just says something like:
"Sorry, the DSpace SWORD web application does not understand this request. If you are looking for the SWORD 'servicedocument' please access the path: '/servicedocument'. For more information on SWORD requests and the protocol in general, please visit:
http://www.swordapp.org"
You could do something similar for OAI & LNI. Essentially we just tweak the 404 error page so that it provides the user with useful information & gives very basic information on the correct URL, etc.
> add redirects to SWORD/OAI/LNI interfaces