...
Available API endpoints:
POST | /api/contexts | @api.ContextLD.addContext() | |
GET | /api/contexts/:id | @api.ContextLD.getContextById(id: UUID) | |
GET | /api/contexts/:name/context.json | @api.ContextLD.getContextByName(name: String) | |
DELETE | /api/contexts/:id | @api.ContextLD.removeById(id: UUID) | |
POST | /api/datasets/:id/metadataJsonLD | @api.Datasets.addMetadataJsonLD(id: UUID) | |
GET | /api/datasets/:id/metadataJsonLD | @api.Datasets.getMetadataJsonLD(id: UUID) | |
POST | /api/files/:id/metadataJsonLD | @api.Files.addMetadataJsonLD(id: UUID) | |
GET | /api/files/:id/metadataJsonLD | @api.Files.getMetadataJsonLD(id: UUID) |
Comments:
- Extractor context definitions are similar to user specified metadata, they both provide what kind of metadata will be added
- How much flexibility do extractors get when adding metadata?
...
Code Block |
---|
case class ExtractorInfo (
id: UUID,
name: String,
description: String,
creator: User,
version: String,
contexts: List[UUID],
external_services: List[URL],
libraries: List[String],
bibtex: List[String]
) |