[TAVERNA-1046] ORCID not picked up when parsing manifest

• Type: Bug
• Status: Done
• Priority: Major
• Resolution: Done
• Affects Version/s: language 0.15.1
• Fix Version/s: language 0.16.0
• Component/s: Taverna Language
• Assignee: Stian Soiland-Reyes
• Reporter: Stian Soiland-Reyes
• Created: 10/May/18 17:20
• Updated: 11/May/18 10:45
• Resolved: 11/May/18 10:45

Description

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