generated from john/python-template
UI updates, changes sync'd to UI docs
This commit is contained in:
@@ -18,7 +18,7 @@ Managing a Job is run-first:
|
||||
4. The user links a Document and uploads one or more source files.
|
||||
5. The user submits for transcription.
|
||||
6. The system creates and processes the Job.
|
||||
7. The user reviews per-source output and saves revisions.
|
||||
7. The user reviews job metadata and follows document-scoped links for Sources and Jobs.
|
||||
|
||||
## 2. User Goal
|
||||
|
||||
@@ -54,9 +54,9 @@ Create mode should include:
|
||||
|
||||
Detail mode should include:
|
||||
1. job metadata and status
|
||||
2. per-source processing state
|
||||
3. original transcription output
|
||||
4. revision editor and save actions
|
||||
2. document-scoped navigation links for the current Document
|
||||
3. provider/model/prompt visibility when known
|
||||
4. no delete action in first release
|
||||
|
||||
## 4. Entry Points
|
||||
|
||||
@@ -67,6 +67,7 @@ Primary entry points:
|
||||
Current implementation note:
|
||||
1. current code path is upload-first and auto-creates Job records
|
||||
2. intended UX is explicit Create job from the Jobs page
|
||||
3. current detail view is link-oriented and does not show per-source transcription or revision editing controls
|
||||
|
||||
## 5. Create Job Flow
|
||||
|
||||
|
||||
Reference in New Issue
Block a user