-
-
Notifications
You must be signed in to change notification settings - Fork 145
Open
Labels
UIfrontendFrontend developmentFrontend developmentgood first issueGood for newcomersGood for newcomersneeds scopeIssues that need estimations/requirements/scopingIssues that need estimations/requirements/scoping
Description
Problem
There are several potential states for a Hearing to be in that we care about, and the current Hearing Detail page only handles one of them (the happy path) perfectly.
The states are:
- The Hearing does not exist (e.g. a mistyped hearing id)
- The Hearing has not yet occurred (e.g. a hearing scheduled to occur in the future)
- The Hearing has occurred and has no video
- Some hearings will never have a video posted, but we believe most will have a video posted within 24 hours of the hearing's end)
- The Hearing has occurred and has a video but no transcription
- This is a temporary state, likely to last an hour or two at most.
- The Hearing exists, has occurred, and has both a video and a transcription
- This is the happy path and most common use case.
For the unhappy paths, we want to provide more appropriate user experiences to set expectations around what data is available and what data will be available in the near future.
Success Criteria
- Empty State for Non-Existent Hearing (Can just be 404)
- Empty State for Hearing that has occurred but has no video
- Can determine this based on current time and hearing's scheduled date
- Should have a message like "This hearing has completed - it is currently being processed"
- Empty State for Hearing that has occurred and has a video, but no transcription
- Very similar to the previous state, but has a video - can likely be rolled into one case that handles missing video and missing transcriptions separately in their respective UI components.
- Only display the "This Transcription uses AI" box when we actually have a transcription - this applies for all states.
Additional Links
- Figma: N/A (Waiting on Design)
Metadata
Metadata
Assignees
Labels
UIfrontendFrontend developmentFrontend developmentgood first issueGood for newcomersGood for newcomersneeds scopeIssues that need estimations/requirements/scopingIssues that need estimations/requirements/scoping