You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Title (Goal)Support for Fedora 3-style disseminations or “behaviour”.
Primary Actor

Repository architect & implementer 

Scopearchitecture and access
LevelHigh
Story

As a repository manager,

  1. I will be able to associate content models to “service definitions” which define methods that can be performed on objects that are associated to the content model by a relation like  (in F3) fmodel:hasModel or maybe rdf:type (compare F3 Service Definitions)
  2. I will be able to implement these methods by defining which external services wil be invoked and what their parameters will be. (compare F3 Service Deployments)
  3. I can do this in a declarative way in rdf, xml or json. No custom java code is required (assuming suitable external services exist)

Examples:

  1. Dynamic transformation of metadata formats, e.g MODS to Datacite
  2. Imagine a hierarchy of objects with model “geographical object”, each with point coordinates in rdf (wsg84) or maybe a kml datastream. A "geo" service for this object model has a method "kml representation of this object and all its child objects, recursively.”
  3. Imagine a setup where datasets, instuments, places etc. are stored as separate Fedora objects to facilitate reuse. A service for datasets can give a representation of the dataset within its context of instruments and places in xml or html. The latter can function as the dataset’s landing page.
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.