Users should be able to get information on a Synapse entity given its DOI in R and Python clients
Resolved for lengthy time (at least six months), closing in bulk
Resolving as a "Won't Do" based on earlier comments.
Notes from meeting with and :
Robert and Kenny are interested in answering the question: given a synapse entity, how should anyone cite it? This question has been asked many times in the past. We have control on telling people what to do.
Ideally, users do not need to know about DOI or have to handle it. They only care about getting the citation from a given entityId.
This functionality is useful in programmatically creating a wiki/ documents that includes citations.
Kenny has examples on how he has cite entity manually in the past and raised concerns about how the DOI services work. Questions to answer:
Who can mint DOI?
Who are the authors of the DOI?
Can we update DOI after minting it?
While it could be helpful to be able to mint DOI from the client, Robert is not interested in using the functionality in the client. Since we hope to have more control on filling out the metadata in the DOI, and it can be a permanent record (no update service from our rest API), Robert refers to do this on the web client.
would you like to be able to mint DOI from the R/ Python client? If so, how do you expect this function to work?
Adding to the conversation. He joined us on the second half of the discussion.
I bet if we implemented a generic DOI lookup feature, then it would return the relevant Synapse info automatically. That's what it is supposed to do! Would that be simpler? E.g. given ANY DOI (not just one in Synapse) return the relevant metadata? Perhaps something using this? https://support.datacite.org/docs/datacite-content-resolver
Anyway, this does seem cool and useful, but would make more sense if done in the generic sense; would also allow folks to pull in data from elsewhere if needed?
This issue was created by Mike and since then has no public interests (0 votes). I haven't heard any Python user asking for this. So I don't think it's necessary.