Difference between revisions of "MD Store"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 20: Line 20:
*Base-URL (proposal 1) - base URL of the core-service is appended with the URL of the new-service
*Base-URL (proposal 1) - base URL of the core-service is appended with the URL of the new-service


     ''<core-service-url>''/md-store
     ''<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)
*Base-URL (proposal 2) - separate URL for the new service is provided (independently of the core-service URL)


     ''<service-url e.g. md-store.mpdl.mpg.de>''
     ''<service-url>''
 
e.g.  
 
    http://md-store.mpdl.mpg.de


===Interface Methods URL===
===Interface Methods URL===

Revision as of 11:13, 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]

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>
  • 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 
  • For single metadata record graph
    <base-url>/<resource-id>/md-records/md-record/<md-record-id> 
  • For properties graph
    <base-url>/<resource-id>/properties

Examples[edit]

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

Architecture[edit]