First of all, sorry if this has been asked before, but I could not find it when searching the issue-tracker.
Issue:
A repository I am currently maintaining had a pair of academic papers published coupled with its 1.0 release. Therefor, their preferred citation is done by citing both. This does not seem to be supported (for example, having multiple doi fields breaks the validation)
For now I am using a citations.md, as I could not figure out how to do this within a cff schema.
Which leaves me with 2 questions:
- Did I miss some way of doing this?
- If not, is there any intention of supporting this edge-case?
I can understand completely if this edge-case is not intended to be covered or supported, (I can easily imagine forcing non-duplicate keys is favored), but I could not find any documentation/issue stating explicitly that the schema is supposed to be a single citation.
cc: @dwhswenson
First of all, sorry if this has been asked before, but I could not find it when searching the issue-tracker.
Issue:
A repository I am currently maintaining had a pair of academic papers published coupled with its 1.0 release. Therefor, their preferred citation is done by citing both. This does not seem to be supported (for example, having multiple
doifields breaks the validation)For now I am using a citations.md, as I could not figure out how to do this within a cff schema.
Which leaves me with 2 questions:
I can understand completely if this edge-case is not intended to be covered or supported, (I can easily imagine forcing non-duplicate keys is favored), but I could not find any documentation/issue stating explicitly that the schema is supposed to be a single citation.
cc: @dwhswenson