No, I don't think this is valid use of reportedIn. IRIs in this field should point to VA-Spec Document objects.
We're in crunch time here, so just put these in an extension for now so we can move forward with the submission software testing.
To accomplish this in the slightly-less-immediate term, we should be packaging in the VA-Spec statements associated with each of these EIDs in the appropriate place. Those statements will each have their own reportedIn field where we can have a Document for the source (the PMID / ASCO document) and/or the curated record (the CIViC webpage document), each with their respective embedded URLs.
Originally posted by @ahwagner in #218 (comment)
No, I don't think this is valid use of reportedIn. IRIs in this field should point to VA-Spec Document objects.
We're in crunch time here, so just put these in an extension for now so we can move forward with the submission software testing.
To accomplish this in the slightly-less-immediate term, we should be packaging in the VA-Spec statements associated with each of these EIDs in the appropriate place. Those statements will each have their own reportedIn field where we can have a Document for the source (the PMID / ASCO document) and/or the curated record (the CIViC webpage document), each with their respective embedded URLs.
Originally posted by @ahwagner in #218 (comment)