Skip to content

Determine fields we need to deal with in database / interface(s) #1

@davclark

Description

@davclark

Note that different fields may be relevant to different "user stories"

From Tuan:

After much thought, I realized the only fields to, ideally, map to each other/combine are under reading level, where we have different entries to translate, see:

https://www.readinga-z.com/learninga-z-levels/level-correlation-chart/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions