You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@taverna.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2018/05/10 17:21:01 UTC

[jira] [Created] (TAVERNA-1046) ORCID not picked up when parsing manifest

Stian Soiland-Reyes created TAVERNA-1046:
--------------------------------------------

             Summary: ORCID not picked up when parsing manifest
                 Key: TAVERNA-1046
                 URL: https://issues.apache.org/jira/browse/TAVERNA-1046
             Project: Apache Taverna
          Issue Type: Bug
          Components: Taverna Language
    Affects Versions: language 0.15.1
            Reporter: Stian Soiland-Reyes
            Assignee: Stian Soiland-Reyes
             Fix For: language 0.16.0


The "orcid" property is not picked up when parsing manifest.json of an opened bundle, meaning agent.getOrcid() is always blank afterwards.

This may be because the JSON-LD @context https://w3id.org/bundle/context wrongly maps "orcid" property to http://purl.org/wf4ever/roterms#orcid - but that property is not defined in that ontology. (And neither is this property recognized by our RDFToManifest code).

Suggested workaround is to map instead to prov:alternateOf and pick up ORCID if the hostname starts with orcid.org -- ideally that it conforms to https://support.orcid.org/knowledgebase/articles/116780-structure-of-the-orcid-identifier



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)