-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding contributor roles to the metadata #5
Comments
I like the idea of showing the roles in the manuscript, thanks for doing that! |
I will add the roles to the yaml file |
Okay I'll touch base with our frontend dev @vincerubinetti on what might be some nice ways to display these roles in the manuscript frontmatter. |
awesome, thanks! |
Agree - this is awesome! Thanks! |
Please have a look at : https://jats4r.org/credit-taxonomy: We should all discuss how to include CRO information. |
@jcolomb the credit-taxonomy was incorporated into CRO; we were part of the original workshops that defined the taxonomy. CRO is a computational representation and a much more extensive set of concepts, however the original credit taxonomy can still be used as a subset. |
the question is how to implement the CRO vocabulary into the paper metadata, see the link: there is a recommendation when using credit, but not for CRO. |
An additional thought: any way to add contributors who are not authors something like:
(PS: I moved question about contributor role in #8) |
Do you want the translators to show up on the manuscript, like we did for translators at https://greenelab.github.io/scihub-manuscript-es/#traductores? For now we could just create another field in the YAML for |
I like the URLs for their human-readability and the ability to be resolved in a web browser, but the URLs like https://dictionary.casrai.org/Contributor_Roles/Visualization return "Oops! That page can’t be found." I was thinking we could just put |
This is why we created this resolvable version in OWL: https://github.com/data2health/credit-ontology (note that some of the original terms are a bit conflated, so this is a bit of a problem) |
I think I tweeted in the past that I would love to see author contributions on mouseover (or similar) in author lists. |
concerning contributor role description, I would take these actions :
Make sense ? |
this is what I can get out of my program fetching orcid info:
|
I agree with those steps, I think. For now, I think we should continue adding authors roles to
BTW, I noticed CRO wasn't on https://registry.identifiers.org/registry. This service is a great way to get a PID that can be interpreted by as many applications as possible. @jcolomb I am treating this issue as "let's add contributor roles to this specific manuscript", and not necessarily, "let's solve the problem forever". I would like a good implementation, but I view this as more proof of concept. Happy to work on more general / permanent solutions & standards for Manubot. I wasn't clear whether you were making suggestions for this manuscript specifically or for what we should do with more time going forward, especially if it depends on third-party changes.
An XML export of what? This manuscript using Pandoc to create JATS?
This looks cool. I want to mention manubot/manubot#187 where we're discussing what fields metadata.yaml should have generally. What is your program, and is this relevant to this specific manuscript, or something you'd like to integrate in the future? |
Hi @dhimmel We also like to ensure multiple resolvers in all cases, and use https://n2t.net/ In the https://github.com/prefixcommons project we aimed to coordinate prefixes across the two, but it doesn't have funding at present and perhaps not everyone is synched at present. |
Since a part of the paper is about how to implement contributor roles annotation in the literature, the two (this paper and long term solutions) are linked to some extend.
Should we move that discussion to slack? |
@jcolomb makes sense. I'm happy to work together to do as much as possible for this paper and beyond.
I prefer github issues for being public and integrated with the source code. Feel free to make new issues anywhere and tag me. Just saw your This is what I'm thinking for the general implementation:
Does this make sense @jcolomb ? |
Discussion moved to manubot repository: manubot/manubot#202 |
@nicolevasilevsky wrote:
Yes, we can put extra fields for authors in
metadata.yaml
. For example we could do:Currently we don't do anything with that information, but we could. @nicolevasilevsky should we show the roles in the manuscript?
The text was updated successfully, but these errors were encountered: