Create Transcription Project Interface
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- html, javascript
- Domain
- frontend
Research direction
The issue names no files, tests, or entry points. Begin by tracing the authorized-user project-creation entry point and existing manifest and TPEN Project configuration handling. Done means the interface supports the listed manifest sources, project label, and automatic project metadata while producing the proposed configuration object.
Written by the indexing model from the issue text.
Description
Interface for authorized user to create a new transcription project. The meat of the form is modules to describe project and create a TPEN Project configuration object:
- Manifest from string - canvases or images URI, creates URI and loads into Manifest by URI
- Manifest from resources - load a manifest or sequence or canvas and add it to the working manifest
- Manifest by URI - load remote or RERUM URI with preview
- Project Label - May be different from Manifest label
- Automatic project info - creator, modification, references to Manifests
Proposed config object:
{ "@context" : "http://rerum.io/api/context.json",
"@type" : "tpen:Project",
"label" : <String>,
"manifest" : <URI>,
"configuration" : {
"ui" : { // preferences for interface
"tools" : [ <String> ], // splitscreen tool keywords and URIs
"layout" : { <Map> }, // toggles for buttons and interface modules
"interface" : <String> // override for default transcription interface
},
"permissions" : [ { "agent" : <Agent>, "access" : <Map> } ]
},
"creator" : <RERUM User>,
"version" : [<Int>],
"createdAt" : <timestamp>,
"modifiedAt" : <timestamp>
}
- Dominant language
- HTML
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CenterForDigitalHumanities/TPEN3
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Complete Core Workflow InterfacesMay be free again @cubap claimed this 515 days ago, and no pull request is open. Open
CenterForDigitalHumanities/TPEN3#53 · 1 assignee ·
-
Users: Auth0 User management and toolsMay be free again @thehabes claimed this 948 days ago, and no pull request is open. OpenUser Administration user module
CenterForDigitalHumanities/TPEN3#38 · 2 comments · 1 assignee ·
-
Start a Project on the TPEN websiteMay be free again @cubap claimed this 949 days ago, and no pull request is open. Openstory
CenterForDigitalHumanities/TPEN3#37 · 1 assignee ·
-
enhancement OSS
Difficulty 3/5 1-2 days Newbie friendliness 35/100
CenterForDigitalHumanities/TPEN3#32 · 1 comment ·
All issues in CenterForDigitalHumanities/TPEN3
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Spomky-Labs/pwa-bundle#476 ·
-
[可靠性] 在 WebSocket 上行积压时拒绝继续排队输入Possibly taken @myot233 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
os:linux
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mpv-player/mpv#18649 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ccch1mneyyy/dsh-TUI#1631 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day