Unification of inst/curated and inst/extdata datasets

[lwaldron]

While looking into issue #111 I noticed that tsv files in inst/curated still follow an old schema, while there are now multiple files in inst/extdata that seem to combine metadata from all studies together using different schema.

What's the plan for unification - I assume that per-study files are still the most convenient for curators, and the inst/extdata files are just a convenience placeholder until someone updates individual files in inst/curated? Are all important edits in inst/curated also reflected in the inst/extdata files? If it's just a matter of someone with time and technical ability for cleanup, if I know what the "gold standard" data is I can update inst/curated and get rid of redundant / out-of-sync data stores.

[shbrief]

The inst/curated is legacy information that I plan to keep until the harmonized (i.e., following the new schema) metadata in the inst/harmonized are all programmatically validated (@delaney-collins is working on it now). And the inst/extdata is supposed to contain up-to-date information that is synced with the data in inst/harmonized.

I noticed that @SvetlanaUP made changes in inst/curated. I can prioritize this consolidation.

[lwaldron]

It will help to have an outline of the intended workflow in or linked to from README.md. A couple questions I have are:

1. Is inst/harmonized to be used the same or differently than inst/extdata was? In particular, is this where in-progress and completed curations will go.
2. Should the Copilot bot make pushes like this to inst/harmonized (I see only one such previous push, to inst/extdata)