Skip to content

Data representation object #2

Description

@gregmedlock

This issue will be for brainstorming implementation details for the object that will store the data type. The general needs/wants for this object are:

  • Representing each desired data type in a standardized way
  • Function for creating the data object using input data from a project (w/ or w/out peppy)
  • Convenience functions for filtering data

Feel free to add design wants/needs and constraints in the comments for this issue.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions