Skip to content

Data storage formats and conventions #7

@jamiefolsom

Description

@jamiefolsom

We should prefer CSV for data storage files, if feasible, since that will allow data to continue to be edited by scholars (provided they don't change columns).

It would be good if one developer were to provide (written documentation of) conventions for the scholars to follow, so that their data can be easily edited re-exported and imported into the framework site.

For each column,

  • What values are valid (dates, strings, ints, etc)
  • What they should contain/not
  • What conventions if any should they follow re: length, punctuation, accents, spelling, abbreviations, consistency of reused values, etc.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions