|Title (Goal)||Support for Fedora 3-style disseminations or “behaviour”.|
Repository architect & implementer
|Scope||architecture and access|
As a repository manager, Iwill 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)
want to define external services to dynamically transform the (meta)data of certain types of repository resources so
These definitions can be made and maintained by metadata specialists with knowledge of rdf and related standards, rather than developers.
- 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.