Grant interface promise: Chart, ledger and tabular transcription interface
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 20/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Stack tecnologico
- javascript
Direzione di ricerca
Read components/transcription-block/index.js and components/simple-transcription/ARCHITECTURE.md to understand the current line based interfaces, then inspect interfaces/manage-columns/index.js and the referenced Annotorious line parser. The issue leaves the grid model, persistence contract, drawing mode, and host interface undecided, so implementation needs design decisions and coordination with TPEN-services; no completion criteria or test is specified.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
This was generated by AI during triage.
Grant promise: Chart, ledger and tabular transcription interface (Workstream 2 — "More and better interfaces")
The NEH grant narrative promises interfaces for tables, ledgers and charters — documents whose structure is cells and rows-with-columns, not a sequence of text lines. Today every transcription surface in TPEN-interfaces is line-oriented.
What exists today (verified on main, 2026-11)
- The atomic editing unit is one line = one single-line text input:
components/transcription-block/index.js:647(<input type="text" class="transcription-input">with Prev/Next stepper); the same line model drivescomponents/simple-transcription/(seecomponents/simple-transcription/ARCHITECTURE.md:56— "Active project graph (layers/pages/columns)"). - The closest structural analogue is column management — grouping lines into vertical columns of a manuscript page:
interfaces/manage-columns/index.js:9–10("create, merge, and extend columns for organizing line annotations"). Columns organize lines; they are not a grid, and there is no notion of a cell. - No table/grid/spreadsheet component exists anywhere in
components/orinterfaces/(full-backlog triage scan, 2026-07).
What's missing
- A cell-addressed editing surface: rows × columns with stable cell identity, keyboard tab-order, per-cell transcription content.
- Region model for grids: drawing/editing a table structure on the canvas (header row, column separators) so cells map to image regions — likely built on the Annotorious rectangle/polygon tooling (
components/annotorious-annotator/line-parser.js:762–763) but with grid semantics instead of line semantics. - Persistence mapping: how a grid serializes through RERUM/Web Annotation (one Annotation per cell? one per row with a structured body?) — a TPEN-services/RERUM contract question (phase issues TPEN-services#509–#511, #512).
- Ledger/chart-specific behaviors: running totals, date columns, struck-through rows — evaluate whether these are data or just display.
Not yet decided
- Grid vs keyed-record model: should a ledger row be one annotation with fields (closer to transcription search in workstream 3) or a matrix of cell annotations?
- Reuse of the line-parser zone tools vs a dedicated table-shape drawing mode.
- Which existing interface hosts it: new tool inside
interfaces/transcription/family vs standalone/project/tablesurface.
Related
- No TPEN-interfaces backlog issue anticipates tabular editing; nearest relatives are #287 (interface-tool taxonomy) and #160 (tool design musings).
- CenterForDigitalHumanities/TPEN-interfaces#579 ("Organize Grouping Structures within a Canvas") is a partial historical anticipation, misfiled in the TPEN3 docs repo; migration is a separate maintainer decision.
- Lingua principale
- JavaScript
- Stelle
- 2
- Fork
- 3
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di CenterForDigitalHumanities/TPEN-interfaces
-
enhancement ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
CenterForDigitalHumanities/TPEN-interfaces#569 · 1 commento ·
-
enhancement ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
CenterForDigitalHumanities/TPEN-interfaces#566 · 1 commento ·
-
bug ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
CenterForDigitalHumanities/TPEN-interfaces#562 · 1 commento ·
-
enhancement ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
CenterForDigitalHumanities/TPEN-interfaces#526 · 1 commento ·
-
License link borkedApertabug ready-for-agent
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 68/100
CenterForDigitalHumanities/TPEN-interfaces#516 · 1 commento ·
Tutte le issue di CenterForDigitalHumanities/TPEN-interfaces
Issue simili
-
enhancement frontend good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 2 giorni
-
marketing
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
[bug]: Maximizing the Windows dashboard covers the taskbarForse già presa @xiufengsun l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
xiufengsun/TokenTracker#1152 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
parity: scripting.net's net-http row fails on macOS with errno 61 where the BDS golden has 111ApertaBug Tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
JSPrismarine/JSPrismarine#3384 ·
I maintainer di solito rispondono entro 1 giorno
-
cat:test dx effort:xs sev:low
Difficoltà 1/5 1-3 ore Idoneità per principianti 82/100
LucasSantana-Dev/Lucky#3251 ·
I maintainer di solito rispondono entro 1 giorno