Author objects?

[dosumis]

User story:

• BICAN wants to support fine tracking of edits, recording authors at the level of individual annotation objects. For BICAN tooling we plan to tie this to GitHub handles, ORCIDs and author names. The current schema doesn't work well for this because it only captures additional metadata for the Primary Author. One potential solution to this is to define author objects to which this additional metadata is attached. The only downside I see to this is some extra effort is needed to maintain compatibility with CAP.

[evanbiederstedt]

FWIW, it seems like requiring GitHub handles was considered to onerous for many users. So CAP didn't do this.

[dosumis]

FWIW, it seems like requiring GitHub handles was considered to onerous for many users. So CAP didn't do this.

This is not to do with required fields, it is to do with whether we have distinct author objects vs a disparate set of author fields. Author objects are the only practical way to deal with tracking information about multiple authors.

[dosumis]

The blocker - how do we have author objects and still => all the relevant flattened fields to CAP.