Task #144
Define the prototype MN Service
Status:
Closed
Priority:
High
Assignee:
Category:
d1_common_java
Target version:
Start date:
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
The prototype MN service operates as a independent process (perhaps even on it's own VM) and implements the MN APIs as specified in the architecture documentation.
Several issues to be addressed:
- Identify technology to be used
- Identify the mechanism for communication with the various MN repositories (i.e. Dryad, Metacat, DAAC)
- Implement mechanism to retrieve list of objects from repository
- Implement mechanism to generate system metadata for each object in the repository
- Implement the MN APIs
- Test the MN APIs
History
#1 Updated by Dave Vieglais almost 15 years ago
- Status changed from New to Closed
Split into several items that will appear under the "CCI.MN_Software".
Using Django (python) for initial MN implementation (standalone system)
Initial comms will be through existing client APIs for Metacat, DAAC and Dryad
