Title (Goal) | Support for Fedora 3-style disseminations or “behaviour”. |
---|---|
Primary Actor | Repository architect & implementer |
Scope | architecture and access |
Level | High |
Story | As a repository manager,
|
Examples:
- Dynamic transformation of metadata formats, e.g MODS to Datacite
- 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.”
- 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.