Difference between revisions of "Metadata Retriever Plugins"
(→First Phase) |
|||
| Line 6: | Line 6: | ||
A plugin implements IMetadataImporter, which provides a single method, loadMetadata. loadMetadata takes a Resource, and is responsible for adding any fields to it. loadMetadata is not responsible for persisting the Resource. | A plugin implements IMetadataImporter, which provides a single method, loadMetadata. loadMetadata takes a Resource, and is responsible for adding any fields to it. loadMetadata is not responsible for persisting the Resource. | ||
| + | |||
| + | To accomplish this... | ||
| + | *enable resources to allow dynamic metadata to be attached (by plug-ins) | ||
| + | *associate each custom metadata field with a URI-namespace to avoid cardinality | ||
| + | *Create plug-in; call from aggregate step | ||
==Deferred until later== | ==Deferred until later== | ||
Revision as of 18:15, 15 June 2010
| Contact | Contact:: |
|---|---|
| Project | ,|project_name|Project Driver::project_name}} |
| Status | Status::In Development |
First Phase
Operators may wish to include metadata about Resources from other sources, including web services (ie, Semantic Analysis), databases, or something else. This describes how to implement a plugin to import this information.
A plugin implements IMetadataImporter, which provides a single method, loadMetadata. loadMetadata takes a Resource, and is responsible for adding any fields to it. loadMetadata is not responsible for persisting the Resource.
To accomplish this...
- enable resources to allow dynamic metadata to be attached (by plug-ins)
- associate each custom metadata field with a URI-namespace to avoid cardinality
- Create plug-in; call from aggregate step
Deferred until later
Allow configuration of plug-ins
- enable/disable individual plug-ins
- add additional or custom plug-ins
- alter order in which plug-ins run (to determine which are authoritative)
