Ticket #851 (new task)
[WG] Links to MOLES documents in other repositories.
Reported by: | lawrence | Owned by: | lawrence |
---|---|---|---|
Priority: | required | Milestone: | NDG2 Cleanup |
Component: | community | Version: | |
Keywords: | Cc: |
Description
It is highly likely that we will have cross links between moles documents in various respositories ... we knew that from the beginning. When I built browse, the assumption was that we would pass from one repository (and interface) to another as needed ... but this rather breaks in the concept of the current stack.
The obvious way of dealing with this is to modify the retrieve controller to parse a uri, check it's local, and if not, issue a retrieve on the remote repository for the native XML, and if there are no security problems use it as if it were local. However, if there is security, we could simply handle that with a local login, and pass the security context back to the remote repository just as if we were the login handler ourself ... Job done.
This should allow a considerable amount of flexibility in inter-repository metadata handling for no loss of security and/or visibility.
We need to get this working for RAPID, but not for Prod