Difference between revisions of "MD Store"
Jump to navigation
Jump to search
m (→URL definition) |
|||
Line 16: | Line 16: | ||
==URL definition== | ==URL definition== | ||
*For metadata records graph (NOTE: there can be several metadata records managed in the MD Store for a resource) | |||
''<base-url>''/''<resource-id>''/metadata/''<md-record-id>'' | ''<base-url>''/''<resource-id>''/metadata/''<md-record-id>'' | ||
*For properties graph (NOTE: there can be several metadata records managed in the MD Store for a resource) | |||
''<base-url>''/''<resource-id>''/properties | ''<base-url>''/''<resource-id>''/properties | ||
*Base-URL (proposal 1) | |||
''<core-service-url>''/md-store | ''<core-service-url>''/md-store | ||
*Base-URL (proposal 2) | |||
''<service-url e.g. md-store.mpdl.mpg.de>'' | ''<service-url e.g. md-store.mpdl.mpg.de>'' | ||
Revision as of 11:03, 12 July 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 be 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
URL definition[edit]
- For metadata records graph (NOTE: there can be several metadata records managed in the MD Store for a resource)
<base-url>/<resource-id>/metadata/<md-record-id>
- For properties graph (NOTE: there can be several metadata records managed in the MD Store for a resource)
<base-url>/<resource-id>/properties
- Base-URL (proposal 1)
<core-service-url>/md-store
- Base-URL (proposal 2)
<service-url e.g. md-store.mpdl.mpg.de>
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