OpenAIRE-EUDAT-DMP-service-pilot issueshttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues2019-07-17T11:11:52+02:00https://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/138Connect to OpenAIRE API for serving project list via EESTORE2019-07-17T11:11:52+02:00Georgios KakaletrisConnect to OpenAIRE API for serving project list via EESTOREOpenAIRE commits to provide to us a new API with all the projects it hosts.
As soon as this is available, can we expose it via EEStore ?OpenAIRE commits to provide to us a new API with all the projects it hosts.
As soon as this is available, can we expose it via EEStore ?Hanne MoaHanne Moahttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/54What to do with remote resources that disappear2019-03-15T08:31:17+01:00Hanne MoaWhat to do with remote resources that disappearI've been working on the refreshing code for the EEStore, that is: refetching data from remotes to discover changes (this updates last_fetched).
One thing is: the original spec doesn't have any notion of a "last modified"-date, so that'...I've been working on the refreshing code for the EEStore, that is: refetching data from remotes to discover changes (this updates last_fetched).
One thing is: the original spec doesn't have any notion of a "last modified"-date, so that's not supported. Understandable, some remotes have a notion of last modified but most don't.
Much worse: different remotes treat deletion of data differently, and this hasn't been considered at all (not mentioned in the original spec). Some set a flag marking that a record is deleted, others delete the record. But what EEStore should do in either case is unclear. Currently, the last_fetched date is not updated so that at least it is possible to see that the record is outdated.
When a record on a remote has been deleted, what should the EEStore pass on, and what should it do with its cache? There are basically two possibilities:
1. Mark the record as deleted and keep it in the cache (and have a filter to hide or only fetch deleted records)
2. Erase the record in the cache and stop sending it out to clients
As for 1 there are two relevant implementation methods: a) a boolean (deleted=true vs. deleted=false) or b) a date (deleted_at=date vs. deleted_at is unset/nil. I tend to prefer option b).
(I just discovered that 83 records classified as "project" has disappeared from CRISTIN since that last time I fetched data from them.)https://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/39Autocomplete lists ordering2018-10-22T12:15:33+02:00Georgios KakaletrisAutocomplete lists orderingAutocomplete lists present unordered results to the end user.
This is most probably caused by the way results are delivered by EEStore and may hide a more significant error in the way the topmost n entries are being fetched.
@dtziotzio...Autocomplete lists present unordered results to the end user.
This is most probably caused by the way results are delivered by EEStore and may hide a more significant error in the way the topmost n entries are being fetched.
@dtziotzios : please confirm that results from EEstore are handled appropriately when merged with local results, though this is not related to the issue observed.Saturn ReleaseHanne MoaHanne Moahttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/25What data should be harvested via OAI-PMH2018-06-29T13:58:42+02:00Hanne MoaWhat data should be harvested via OAI-PMHFor instance, which metadata type should be supported, just Dublin Core?
From the header, datestamp (as last_modified) and identifier I think.
If only supporting DC metadata, which fields of DC should be used? I'm guessing at minimum "...For instance, which metadata type should be supported, just Dublin Core?
From the header, datestamp (as last_modified) and identifier I think.
If only supporting DC metadata, which fields of DC should be used? I'm guessing at minimum "*title*", "*date*" (publication date, not record date), "*creator*", so that it is possible to create a dropdown looking like so: **Dushay, Naomi (2001-12-14) "Using Structural Metadata to Localize Experience of Digital Content"**. Should we aim for something looking like a full bibliographic entry? I note that doesn't mandate a format for a person's name(s) (http://dublincore.org/documents/name-representation/), and what "creator" means is ambiguous since it can also be an organization.
Should deleted records be ignored?
Should there be a new repository-type, "publication"?https://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/24Usage of ORCID2018-10-09T12:06:52+02:00Hanne MoaUsage of ORCIDIn order to use ORCID in a smart way, let's document how others are using ORCID, and what we plan/hope to be able to do.In order to use ORCID in a smart way, let's document how others are using ORCID, and what we plan/hope to be able to do.https://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/10Link external sources - 2nd Group2018-06-29T13:58:41+02:00Georgios KakaletrisLink external sources - 2nd Group1. Repository registries: OpenDOAR
1. Repository registries: fairshairing.org for databases
1. Services: EOSC-hub
1. List of licences : Zenodo
1. Data catalogues: B2FIND1. Repository registries: OpenDOAR
1. Repository registries: fairshairing.org for databases
1. Services: EOSC-hub
1. List of licences : Zenodo
1. Data catalogues: B2FINDHanne MoaHanne Moahttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/9Link to external vocabularies2019-04-04T12:05:46+02:00Georgios KakaletrisLink to external vocabulariesIdentify external vocabularies for providing tagging data for future DMP tool.Identify external vocabularies for providing tagging data for future DMP tool.Arcturus ReleaseGeorgios KakaletrisGeorgios Kakaletrishttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/8Link external sources - 1st group2018-06-22T09:45:45+02:00Georgios KakaletrisLink external sources - 1st group1. Repository registries: Re3data.org (done)
1. Metadata schemata: The URL for the Metadata Standards Catalog is: http://rdamsc.dcc.ac.uk/ Instructions for using the API are here: https://github.com/rd-alliance/metadata-catalog-dev/blob/...1. Repository registries: Re3data.org (done)
1. Metadata schemata: The URL for the Metadata Standards Catalog is: http://rdamsc.dcc.ac.uk/ Instructions for using the API are here: https://github.com/rd-alliance/metadata-catalog-dev/blob/master/README.md Also look at fairsharing.org to see what they have
1. Services: eInfraCentral
1. Funders: funder registry https://www.crossref.org/services/funder-registry/
1. Formats: Pronom file format registry (https://www.nationalarchives.gov.uk/PRONOM/Default.aspx ) (done)
1. Grants: OpenAIRE APIs (done)
1. Researcher: ORCID Apis for researchers
1. Data catalogues: DataCite
1. Data catalogues: OpenAIRE (harvests Zenodo), sizing: 1m entries
Saturn ReleaseHanne MoaHanne Moahttps://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 Releasehttps://gitlab.eudat.eu/dmp/OpenAIRE-EUDAT-DMP-service-pilot/-/issues/3Expose EE Store connected stores and APIs2018-06-22T09:13:55+02:00Georgios KakaletrisExpose EE Store connected stores and APIsThe DMP tool web UI, during the design of the DMP Dataset Profile, requires access to the configured sources in EEStore so that it can present them to the user in the admin interface.
The task involves:
- Co-design the API
- Implement:...The DMP tool web UI, during the design of the DMP Dataset Profile, requires access to the configured sources in EEStore so that it can present them to the user in the admin interface.
The task involves:
- Co-design the API
- Implement: Provide the API on EEStore, Consume the API in DMP ToolJuno ReleaseHanne MoaHanne Moa