user's data page

[TanyaStere42]

Context

Users are not currently able to look their all of their data without leveraging the search function. As the majority of users leverage bulk import, this blocks users from accessing their most recent uploaded data and can stop users from tracking their place in their processed data.

User Story

• As a Codex user in the platform, I can access my home data view from the header menu
• As a codex user on my data page, I can select between several preset data views
  • my sightings (includes pending and sightings)
  • my unapproved sightings (includes pending and sightings, filtered to exclude approved and unidentifiable sightings)
• As a Codex user on any view, I can access the full list of my data through paginated tables

Technical Notes

Sighting and Pending sighting tables: state, location, date, number of annotations, number of animals, and link to sighting

Design

Note: typo in design on second frame. It is "Unapproved sightings" not "approved"

[TanyaStere42]

Emergent requirement for backend: need API for number of annotations and number of animals on AGS (pending sightings) Assigned to @naknomum for backend work

[TanyaStere42]

cutting "my individuals" table for now. requires a direct API call which will need to be addressed separately.

[naknomum]

Emergent requirement for backend: need API for number of annotations and number of animals on AGS (pending sightings) Assigned to @naknomum for backend work

also needed: match_state to be returned from search results.

[TanyaStere42]

Reopened - QA discovered designs did not match feature spec. Page structure needs to be updated