Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Took a step back and made the story more story-like
Title (Goal)Support for Fedora 3-style disseminations or “behaviour”.
Primary Actor

Repository architect & implementer 

Scopearchitecture and access

As a repository manager, 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)
  • 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)
  • I can do this in a declarative way in rdf, xml or json. No custom java code is required (assuming suitable external services exist)

    want to define external services to dynamically transform the (meta)data of certain types of repository resources so

    • they can be harvested by other systems
    • a richer user experience can be offered by websites using these services

    These definitions can be made and maintained by metadata specialists with knowledge of rdf and related standards, rather than developers.


    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.