Open JGilbert-eLife opened 5 years ago
Would make sense to exclude the footnote from TextureJATS and only have the deceased flag set. If needed the translation could provide both the flag + a generated footnote with the content. This would make sense to avoid redundancy, but only works if the content of the deceased footnote is fixed (you can't enter custom text). Is that the case?
Does JATS4R specify how authors should be marked as deceased? Did not find a sample.
Would make sense to exclude the footnote from TextureJATS and only have the deceased flag set. If needed the translation could provide both the flag + a generated footnote with the content. This would make sense to avoid redundancy, but only works if the content of the deceased footnote is fixed (you can't enter custom text). Is that the case?
Yes agreed, we'd need to agree on text!
Does JATS4R specify how authors should be marked as deceased? Did not find a sample.
Nope
Ok, then please specify the text and we can provide a proposal for this.
Ok, then please specify the text and we can provide a proposal for this.
Maybe a tick box for Texture could work for this feature? It's a status. For eLife we just need the attribute in the XML to appear for us somehow, no need for a footnote of text to appear This is one we can discuss on the call if it's confusing.
@NickDuf
Well then this is already implemented. :)
Description
An indicator that an author is deceased.
User stories
Author
Production staff
But what if . . . ?
Consideration
XML requirements
Deceased status is captured with a
deceased="yes"
attribute on thecontrib
element. This is currently linked to a footnote containing the content which will be pulled out and displayed against that author, but we would prefer just to have the attribute:Mock ups
Proposal