Page tree
Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Current »

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

Repository architect & implementer 

Scopearchitecture and access

As a repository manager, I 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.
  • No labels