Story #8371
Updated by Monica Ihli almost 7 years ago
**Problem Statement:**
For some business models, a single organization may host and otherwise manage content for multiple source repositories or producers of science data. Examples might include a consortial or aggregator arrangement. In such cases it may be most appropriate for each of the source data providers to maintain their respective identities, while still having their participation in DataONE managed by the central entity. This means that a single entity should be able to host and manage multiple DataONE member nodes. The problem is that GMN presently only supports hosting a single Member Node per installation of the web app. The only way to meet the above stated needs is for the one entity to setup multiple web servers, creating a situation of additional costs and barriers.
**Proposed Solution:**
The solution is to modify GMN so that multiple member nodes can be hosted from a single installation of the web application.
Notes on the basic strategy is as follows:
* The CN recognize and interact with MN through the node's baseURL.
* A BaseURL and all of the content on the node is tied to the a Node doc. GMN needs to be able to serve up different content for Node docs from different baseURLs. base URLs.
* This would be facilitated through Apache's ability to serve content for multiple hosts from a single web server.
* WRT application itself, would be implemented with vendor specific extension that allows the create() call to add a field specifying which Node doc goes with the particular object.
* Also adds a layer of abstraction to the database.
For some business models, a single organization may host and otherwise manage content for multiple source repositories or producers of science data. Examples might include a consortial or aggregator arrangement. In such cases it may be most appropriate for each of the source data providers to maintain their respective identities, while still having their participation in DataONE managed by the central entity. This means that a single entity should be able to host and manage multiple DataONE member nodes. The problem is that GMN presently only supports hosting a single Member Node per installation of the web app. The only way to meet the above stated needs is for the one entity to setup multiple web servers, creating a situation of additional costs and barriers.
**Proposed Solution:**
The solution is to modify GMN so that multiple member nodes can be hosted from a single installation of the web application.
Notes on the basic strategy is as follows:
* The CN recognize and interact with MN through the node's baseURL.
* A BaseURL and all of the content on the node is tied to the a Node doc. GMN needs to be able to serve up different content for Node docs from different baseURLs. base URLs.
* This would be facilitated through Apache's ability to serve content for multiple hosts from a single web server.
* WRT application itself, would be implemented with vendor specific extension that allows the create() call to add a field specifying which Node doc goes with the particular object.
* Also adds a layer of abstraction to the database.
