Skip to content

UI/UX Path Forward When Data Cannot Be Obtained #430

@thehabes

Description

@thehabes

In some cases, no matter how hard we try, a component or interface may not be able to ascertain the Manifest or Canvas data. Interfaces often need this data for the interface to be useful at all. In interfaces like this, users see an error and a dead page.

We want to improve that experience, especially when it pertains the Manifest, Canvas, or Image data that may be changed outside of out purview and control. We desire a graceful UI/UX so users have a path forward even without this data.

We should also consider what should happen when critical page URL are missing, such as projectID= and pageID=. In most instances users only see a header, footer, and blank blue background where a page should be.

Interfaces to Consider

  • /
  • /project
  • /project/manage
  • /project/manage/layers
  • /project/manage/collaborators
  • /project/metadata
  • /project/view-transcription
  • /transcribe
  • /annotator

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions