You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

As of June 8th the following need to be implemented
  1. When adding metadata check if context already exists and create new if it doesnt
  2. Ability to edit context
  3. Ability edit metadata
  4. Create GUI to manipulate this new metadata
  5. Store extractor metadata (on top of context metadata)
    1. store external services and libraries used
  6. Create example extractor using this new representation
Example json-ld document:

https://opensource.ncsa.illinois.edu/stash/projects/CATS/repos/clowder/browse/doc/src/json/metadata.js?at=refs%2Fheads%2Ffeature%2Fjsonld

Comments:
  1. Extractor context definitions are similar to user specified metadata, they both provide what kind of metadata will be added
    1. How much flexibility do extractors get when adding metadata?
Open questions:
  1. Should ContextLD and Metadata services be combined into one?
Extractor info tentative model:
case class ExtractorInfo (
  id: UUID,
  name: String,
  description: String,
  creator: User,
  version: String,
  contexts: List[UUID],
  external_services: List[URL],
  libraries: List[String]
)
  • No labels