MD Store
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]
Base URL[edit]
- Base-URL (proposal 1) - base URL of the core-service is appended with the URL of the new-service
<core-service-url>/md-store
e.g.
http://coreservice.mpdl.mpg.de/md-store
- Base-URL (proposal 2) - separate URL for the new service is provided (independently of the core-service URL)
<service-url>
e.g.
http://md-store.mpdl.mpg.de
Interface Methods URL[edit]
- For retrieval of the complete resource from the MD store (properties + all metadata record graphs)
<base-url>/<resource-id>
e.g.
<base-url>/escidoc:1234
- For all metadata records graph (NOTE: there can be several metadata records managed in the MD Store for a resource)
<base-url>/<resource-id>/md-records
e.g.
<base-url>/escidoc:1234/md-records
- For single metadata record graph
<base-url>/<resource-id>/md-records/md-record/<md-record-id>
e.g.
<base-url>/escidoc:1234/md-records/md-record/escidoc
- For properties graph
<base-url>/<resource-id>/properties
e.g.
<base-url>/escidoc:1234/properties
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