Difference between revisions of "ESciDoc Logical Data Model/SurrogateItem"
| Line 10: | Line 10: | ||
**zero or more '''Component''' - the actual (or externally referenced) content and at least one metadata description | **zero or more '''Component''' - the actual (or externally referenced) content and at least one metadata description | ||
Surrogate items are useful mechanism for allowing users to enrich the information around existing resources e.g. for particular purpose of the research, aggregating data from various sources into a container, bridging authorization policies etc. A surrogate item | Surrogate items are useful mechanism for allowing users to enrich the information around existing resources e.g. for particular purpose of the research, aggregating data from various sources into a container, bridging authorization policies etc. A surrogate item guarantees that the reference to the origin is not lost. | ||
==UML Diagram== | ==UML Diagram== | ||
Revision as of 17:06, 28 October 2009
Introduction[edit]
This page provides general overview on the SurrogateItem resources within the eSciDoc repository. General introduction available at eSciDoc Logical Data Model page.
Model description[edit]
A surrogate item is an Item resource that references another eSciDoc content resource (e.g. another Item or Container) or an external resource (that is resolvable via the identifier used for reference). Referenced resource is thus "origin" of the surrogate item resource.
As being an Item, surrogate item has the same data model as the Item i.e.
- at least one MetadataRecord i.e. one or more metadata descriptions of the overall content of the item
- zero or more Component - the actual (or externally referenced) content and at least one metadata description
Surrogate items are useful mechanism for allowing users to enrich the information around existing resources e.g. for particular purpose of the research, aggregating data from various sources into a container, bridging authorization policies etc. A surrogate item guarantees that the reference to the origin is not lost.
UML Diagram[edit]
- For simplicity reasons properties of the objects are not represented on the diagram. Properties are managed by the escidoc repository itself and may change during time. For more information on the properties and ther usage please check the documentation available at eSciDoc Item Service.