MD Store

From MPDLMediaWiki
Jump to navigation Jump to search
eSciDoc Solutions

Overview · Functionalities
Interfaces · Support

Overview · Functionalities
Scope · Support

Overview · Functionalities
Scope · Support

Digitization Lifecycle



The MD Store is a triple store for metadata storage and management. The MD Store manages resources which are items or containers in an eSciDoc Repository. The MDStore is designed to be used independently from eSciDoc Repository (in case such a need arises) or in relation with another, non-eSciDoc repository. The following scenarios are covered with the MD Store:


  • The triple store technology is planned to be Jena SDB (TDB doesn't support transactions)
    • note: current imeji demonstrator implements Jena TDB
  • be aware of Concurrency issues in Jena

Data model[edit]

This data model refers only to the MDStore internal data model. As the MDStore will be used in Faces, more information for Faces data model can be found here.

Draft visualization of how resources would be stored in the MDStore is given in the mage below:

Draft MDstore data model visualization

  • The MD Store defines 2 rdf graphs:
    • Metadata graphs, where metadata triples are stored
    • Property graphs with following properties:
      • context-id
      • public-status
      • lock-status
      • content-model-id
      • last-modification-date
      • created-by
      • modified-by
      • version-status
      • collection-id

Mapping to eSciDoc resources[edit]

  • Resource can be any eSciDoc resource of type Item or Container.
  • Metadata Record is the full content of a metadata record that is stored externally from eSciDoc Items and Containers. The eSciDoc items/containers would only reference the metadata record stored in the MDStore. For this purpose for each metadata record of an Item or a Container there is a special (RDF/XML) metadata profile that links further to the metadata record stored in the MDStore.
    • Note: the names of the properties are same as in eSciDoc core. However, in case when eSciDoc Core is not used, these may be set-up by the external system
  • Searching from eSciDoc - the eSciDoc indexing component is extended with the possibility to fetch external XML content and index it


For now we assume that the MD Store will implement 3 interfaces:

  • MDStore Basic interface - to manage the resource updates and synchronize with metadata from the origin repository
  • MDStore search interface - SPARQL endpoint
  • MDStore linked data publishing interface

During implementation this may possibly change, e.g. make linked data interface as a separate service. At present we see no need for it.

MDStore basic interface[edit]

The MD Store implements a REST interface. The REST interface methods are:

    • GET: retrieves the requested resource
    • POST: create a new resource
    • PUT: Updates a resource
    • DELETE: Deletes a resource

MDStore search interface[edit]

MDStore linked data publishing interface[edit]

  • TBD

URL definition[edit]

Base URL[edit]

  • Base URL of the core-service instance is appended with the URL of the new-service


  • Note: at present MDStore requires Java 1.6 which is not available at dev-coreservice-url

MDStore Basic Interface Methods URL[edit]

  • For retrieval of the complete resource from the MD store (properties + all metadata record graphs)


  • For all metadata records graph (NOTE: there can be several metadata records managed in the MD Store for a resource)


  • For single metadata record graph



  • For properties graph




  • eSciDoc: The MD Store uses eSciDoc security management (AA)
    • It should be generic to enable other services to log in into MDstore


  • shall the interface methods understand the resource version-id?
  • three alternatives could be implemented:
    • content-stream
      • is indeed for binary content only (together with the item object, must be base-64 encoded, most probably not applicable)
    • md-record - good as in this case we could deal with items, containers ... even originally considered as cumbersome, may be good approach e.g.
      • create new MD-Profile (Externally-reference
    • externally-referenced component
  • the Model itself-> when things come from CoNE -> we treat them as CoNE resources or not?
    • MDStore would not contain any descriptive metadata from CoNE in addition, only a link to CoNE resource? (cleaner)
      • CoNE changes?
    • MDStpore would contain additional descriptive metadata of a CoNE Resource (provided by the end user) and a link to CoNE Resource?