Contribution to Registries, CAP, ... #7
No reviewers
Labels
No Label
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: D-Net/openaire-graph-docs#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "(deleted):main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Contribution to aggregation
@ -10,2 +10,3 @@
OpenAIRE aggregates metadata records describing objects of the research life-cycle from content providers compliant to the [OpenAIRE guidelines](https://guidelines.openaire.eu/) and from entity registries (i.e. data sources offering authoritative lists of entities, like [OpenDOAR](https://v2.sherpa.ac.uk/opendoar/), [re3data](https://www.re3data.org/), [DOAJ](https://doaj.org/), and various funder databases). After collection, metadata are transformed according to the OpenAIRE internal metadata model, which is used to generate the final OpenAIRE Research Graph, accessible from the [OpenAIRE EXPLORE portal](https://explore.openaire.eu) and the [APIs](https://graph.openaire.eu/develop/).
OpenAIRE aggregates metadata records describing objects of the research life-cycle from content providers
compliant to the [OpenAIRE guidelines](https://guidelines.openaire.eu/) base on the [OpenAIRE Content Acquisition Policies](https://doi.org/10.5281/zenodo.1446408)
"base on" => "based on"
Can you please fix this typo?
@ -11,1 +11,3 @@
OpenAIRE aggregates metadata records describing objects of the research life-cycle from content providers compliant to the [OpenAIRE guidelines](https://guidelines.openaire.eu/) and from entity registries (i.e. data sources offering authoritative lists of entities, like [OpenDOAR](https://v2.sherpa.ac.uk/opendoar/), [re3data](https://www.re3data.org/), [DOAJ](https://doaj.org/), and various funder databases). After collection, metadata are transformed according to the OpenAIRE internal metadata model, which is used to generate the final OpenAIRE Research Graph, accessible from the [OpenAIRE EXPLORE portal](https://explore.openaire.eu) and the [APIs](https://graph.openaire.eu/develop/).
OpenAIRE aggregates metadata records describing objects of the research life-cycle from content providers
compliant to the [OpenAIRE guidelines](https://guidelines.openaire.eu/) base on the [OpenAIRE Content Acquisition Policies](https://doi.org/10.5281/zenodo.1446408)
from 2018. And from entity registries (i.e. data sources offering authoritative lists of entities,
"from 2018. And from entity registries" => "from 2018 onward, and from entity registries"
Can you please make the change?
@ -12,0 +15,4 @@
[DOAJ](https://doaj.org/), [DRIS](https://dspacecris.eurocris.org/cris/explore/dris) from [euroCRIS](https://www.openaire.eu/openaire-and-eurocris-sign-a-memorandum-of-understanding), and
various funder databases).
After collection, metadata are transformed according to the OpenAIRE internal metadata model, which is used to generate the final OpenAIRE Research Graph, accessible from the [OpenAIRE EXPLORE portal](https://explore.openaire.eu) and the [APIs](https://graph.openaire.eu/develop/).
"which is used to generate the final OpenAIRE Research Graph, accessible from the OpenAIRE EXPLORE portal and the APIs."
=>
"which is used to generate the final version of OpenAIRE Research Graph."
The last part of the sentence should be omited.
Can you please make the change?
@ -12,3 +18,4 @@
After collection, metadata are transformed according to the OpenAIRE internal metadata model, which is used to generate the final OpenAIRE Research Graph, accessible from the [OpenAIRE EXPLORE portal](https://explore.openaire.eu) and the [APIs](https://graph.openaire.eu/develop/).
The transformation process includes the application of cleaning functions whose goal is to ensure that values are harmonised according to a common format (e.g. dates as YYYY-MM-dd) and, whenever applicable, to a common controlled vocabulary. The controlled vocabularies used for cleansing are accessible at [api.openaire.eu/vocabularies](https://api.openaire.eu/vocabularies/). Each vocabulary features a set of controlled terms, each with one code, one label, and a set of synonyms. If a synonym is found as field value, the value is updated with the corresponding term.
Also, the OpenAIRE Research Graph is extended with other relevant scholarly communication sources that do not follow the OpenAIRE Guidelines and/or are too large to be integrated via the “normal” aggregation mechanism: DOIBoost (which merges Crossref, ORCID, Microsoft Academic Graph, and Unpaywall).
I would remove the part that mentions that they are "too large"... Should we describe this case in another, nicer way? @claudio.atzori ???
Also the next part is weird... I would have it as a separate section titled "Aggregation process" and its heading should be formated in the same way as the rest of the headings on this page...
There is also some overlap with the previous section... Can you please revise it accordingly?
Hm... Reading it again... Is that an old version of the text? I can see that part of the information is also present in the next section. Could you please clean this part?
@ -48,3 +55,4 @@
The OpenAIRE aggregator collects metadata records in the majority of cases via [OAI-PMH](https://www.openarchives.org/pmh/), but also supports other standard exchange protocols like FTP(S), SFTP, and some RESTful API.
The whole list of available and used collectors could be found in the [RedMine Wiki - API Protocols](https://support.openaire.eu/projects/openaire/wiki/API_protocols)
For additional details about the aggregation workflows, please refer to [2].
what is the [2] reference??? we only have [1]
I'm wondering, that you don't see [2] at the bottom.
You are right... I do not know why I did not see. Mea culpa.
@andreas.czerniak please take a look at the changes and the comments. let us know when you have a new version so that me and @claudio.atzori can take a second look.
@andreas.czerniak please consider to syncronise your fork with the main project, recently the main branch received many contributions as we are finalising the different pull requests.
@andreas.czerniak can you either look into the requested changes above or allow us access to your fork ? Currently, I am not able to contribute on your forked version of this repo. Thanks
Issues raised are addressed here: #23
Pull request closed