Open Panos512 opened 7 years ago
The related invenio-orcid
pull request is inveniosoftware/invenio-orcid#20.
@Panos512:
Since the data-sets have their own DOI's they could be sent to orcid as work type documents (just like literature records do now). We need to investigate if the current mapper from our schema to orcid's schema supports out of the box the conversion of data records ( the conversion method is https://github.com/inspirehep/inspire-next/blob/master/inspirehep/modules/orcid/utils.py#L28 ). If not we should make a new converter for the data collection records and plug it to the conversion method.
Note that at the moment we don't have a schema at all for Data.
Indeed, and that's why I haven't started implementing anything yet. My point is that since ORCiD at minimum needs a title, an identifier, and a data-type (they support 'DATA-SETS') and the data records seem to have those (e.g. https://inspirehep.net/record/1409185) they will be pushable when they get a schema and become part of labs.
In order to be able to push data-sets to orcid we need to:
data collection
.data collection
to be pushed. ( changing https://github.com/inveniosoftware/invenio-orcid/blob/master/invenio_orcid/tasks.py#L101 )DOI's
they could be sent to orcid aswork type
documents (just likeliterature records
do now). We need to investigate if the current mapper from our schema to orcid's schema supports out of the box the conversion ofdata records
( the conversion method is https://github.com/inspirehep/inspire-next/blob/master/inspirehep/modules/orcid/utils.py#L28 ). If not we should make a new converter for thedata collection records
and plug it to the conversion method.After those two things, the
data-records
should automatically be pushed to orcid upon addition or update on our system ( see https://github.com/inspirehep/inspire-next/blob/master/inspirehep/modules/orcid/receivers.py#L33 )This is related to #915.
cc: @suenjedt @robk5uj @jmartinm