There are a number of fields included in the core tables that are not :actually: part of the US core spec as must require fields, but are very useful for the kinds of research questions we're typically asking.
The scope of this spike is to design an approach for handling these as part of the library and the core tables. Questions to answer:
How do we inform users about these fields?
How do we handle cases where the data in these fields is not available?
Do we need to programmatically encode the status of these fields in the database?
If so, can this mechanism be shared with derived fields in some way?
Can a study detect if fields are present and determine if it can be run? :Should: it do this, or is it just a matter of documentation?
There are a number of fields included in the core tables that are not :actually: part of the US core spec as must require fields, but are very useful for the kinds of research questions we're typically asking.
The scope of this spike is to design an approach for handling these as part of the library and the core tables. Questions to answer: