Skip to content
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

<fn fn-type="COI-statement"> #49

Open
Melissa37 opened this issue Sep 27, 2016 · 3 comments
Open

<fn fn-type="COI-statement"> #49

Melissa37 opened this issue Sep 27, 2016 · 3 comments

Comments

@Melissa37
Copy link

26208cb

See: https://www.ncbi.nlm.nih.gov/pmc/pmcdoc/tagging-guidelines/article/dobs.html#dob-coi

@gnott
Copy link
Member

gnott commented Sep 27, 2016

A couple implications

  • our parser is based on fn-type = conflict
  • PoA generation also sets fn-type = conflict

It's possible these both can be adapted.

@Melissa37
Copy link
Author

Thanks for the heads up on this. I think while we're updating we should update this, how much work will it be to adapt? I'd forgotten PoA side of things.

@gnott
Copy link
Member

gnott commented Sep 30, 2016

My guess is it should be clear and simple. We should open a JIRA ticket to summarise all the parts that must be aware of the change so they're not forgotten.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants