Difference between revisions of "MD Store"
Jump to navigation
Jump to search
Haarlaender (talk | contribs) m (→Technologies) |
|||
| Line 18: | Line 18: | ||
* The MD Store defines 2 rdf graphs: | * The MD Store defines 2 rdf graphs: | ||
** Metadata graphs, where metadada triple are stored | ** Metadata graphs, where metadada triple are stored | ||
** Property graphs with: context-id, public status, lock-status | ** Property graphs with: context-id, public status, lock-status, content-model-id | ||
= Architecture = | = Architecture = | ||
Revision as of 08:35, 25 June 2010
Introduction[edit]
The MD Store is a triple store for medatada storage and management. It is part of the process for massive batch metadata update for eSciDoc objects.
Technologies[edit]
- The triple store technology is Jena SDB (TDB doesn't support transactions)
- eSciDoc: The MD Store uses eSciDoc security management (AA)
- It should generic to enable other services to log in into MDstore
Interface[edit]
- The MD Store has a REST interface:
- GET: returns metadata triple
- POST: create a new metadata triple
- PUT: Update a metadata triple
- DELETE: Delete a metadata triple
Data Model[edit]
- The MD Store defines 2 rdf graphs:
- Metadata graphs, where metadada triple are stored
- Property graphs with: context-id, public status, lock-status, content-model-id