Title (goal) | Repository-level metadata transformations/mapping |
|---|---|
| Primary Actor | user |
| Scope | |
| Level | |
| Story | A user requests metadata in a certain form. The repository (based on RDF assertions, metadata characteristics, or any other mechanism) provides metadata in that form. In the three-series fedora, this can be accomplished by exposing a method in a service definition for dissemination of metadata in that form. The repository need not maintain metadata in multiple forms, it just needs to maintain mappings. For the benefits of preservation, having this transformation be embedded in the repository is important. (this may further the goal of TRAC B2.8 in cases where the metadata format of record is application-specific) One of the strengths of fedora 3.* was the ease with which one could add a new service to a content model. Updating every object to change their behaviors in the repository is an unacceptable regression to the functionality of fedora 2*. |
| Comments | AWoods: There are two issues at play here:
There are several ways that both #1 and #2 can be achieved. We should establish a group of institutions with the same use case and discuss/design. |
Overview
Content Tools
All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license
, unless otherwise noted.