OpenAIRE-EUDAT-DMP-service-pilot issueshttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues2019-04-04T12:45:26+02:00https://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/16Extension of dataset fixed metadata2019-04-04T12:45:26+02:00Georgios KakaletrisExtension of dataset fixed metadataMore semantic info could be considered for moving to fixed dataset metadata such as external datasets, repositories, services e.g. license, usage, role of repository (primary, replica, access etc), service usage actions.
Example:
- Role...More semantic info could be considered for moving to fixed dataset metadata such as external datasets, repositories, services e.g. license, usage, role of repository (primary, replica, access etc), service usage actions.
Example:
- Role of repositoryDiana ReleaseGeorgios KakaletrisGeorgios Kakaletrishttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/6Formalize EEStore API2018-06-22T09:45:57+02:00Georgios KakaletrisFormalize EEStore APIThe group shall collectively formalize the EEStore API in order to:
a) promote EEStore as a source for acquiring related DMP reference data
b) enforce the adoption of adoption specification by external vocabulary/reference data provider...The group shall collectively formalize the EEStore API in order to:
a) promote EEStore as a source for acquiring related DMP reference data
b) enforce the adoption of adoption specification by external vocabulary/reference data providers to conform with, for easy integration within EEStore
More than one specs may be suggested for adoption, some being the following: OpenSearch (linked sources), OAI-PMH (harvested sources), or a basic JSON returning REST APIs for either case.
Following this specification EEStore should provide administrative tools (e.g. UI) that would allow DMP Managers to configure new sources at will, assuming that those sources would be compliant with the specification.Diana Release