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

elifesciences / XML-mapping

Mapping the XML to new Continuum requirements and build of a new Kitchen sink

3 stars 9 forks source link

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

Open Melissa37 opened 8 years ago

Melissa37 commented 8 years ago

https://github.com/elifesciences/XML-mapping/commit/26208cbe3ccd392a8752208e288c30f43ec0d919

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

gnott commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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.