Grant interface promise: Read-only visualization surface
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
- Ambito
- frontend
Direzione di ricerca
Start by reading components/read-only-transcribe/index.js and interfaces/project/view-transcription.html to understand the existing single-project viewer. The issue leaves the surface, access model, data freshness, and collection scope undecided, so implementation needs planning before work can be scoped; first clarify those choices with maintainers. Done means delivering an agreed read-only visualization experience that supports the selected access and project scope.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
This was generated by AI during triage.
Grant promise: Read-only visualization surface (Workstream 2 — "better interfaces", feeds workstream 3 aggregation)
The NEH grant narrative promises read-only visualization of TPEN project content — public/curated viewing that goes beyond the current single-project transcription viewer, toward browsable, shareable, aggregate presentations of transcription and annotation work.
What exists today (verified on main, 2026-11)
- One read-only viewer, single-project, static:
components/read-only-transcribe/index.js(tagtpen-read-only-view-transcribe), hosted atinterfaces/project/view-transcription.html(route/project/view-transcription, og:url points atapp.t-pen.org/components/read-only-transcribe/?projectID=). - It is effectively unreachable: repo-wide,
view-transcriptionappears only in that page itself and the route list in404.html:212— no interface links to it. Tracked and briefed for a fix in #458 (ready-for-agent: add the manage-home link). - Collections are a dead stub (
api/TPEN.js:33—collectionIDparsed, never consumed; collection-level import listed as future work incomponents/manifest-import/IMPLEMENTATION.md:252), so there is nothing to visualize at collection/aggregate level. - Everything viewer-adjacent is authentication-gated (
components/check-permissions,tpen-screenflow) — there is no unauthenticated read path.
What's missing
- A visualization layer: presentation modes beyond "read the transcription" (e.g., per-page mosaic, contributor/progress view, annotation density) rendered from RERUM/TinyPEN data.
- Public or link-shared access without login (ties directly to #472's questions).
- Collection/cross-project scope — the aggregation story of workstream 3 begins here.
- Share/embed affordances (permalink to canvas/line, iframe embedding, IIIF Presentation export wiring).
Not yet decided
- Is the surface a TPEN-hosted page, an embeddable web component for external sites, or both?
- Access tiers: fully public vs token-shared vs curated-list "exhibition" mode.
- Data freshness: live RERUM reads vs periodically exported snapshots (affects services/rerum_server_nodejs).
- Relationship to read-only exported projects (existing static export flow) — consolidate or deprecate.
Related
- #458 (entry link for the existing viewer — ready-for-agent) and #472 (unauthenticated UX incl. "search TPEN Projects" / Manuscripts-Browser idea — needs-triage): the maintainer approved treating these as this promise's anticipators rather than duplicating them; scope them into this promise during January 2027 planning.
- CenterForDigitalHumanities/TPEN-interfaces#581 ("Readonly Viewer") and CenterForDigitalHumanities/TPEN-interfaces#582 ("Browse Available Manifests") — historical anticipations 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
-
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
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
desec-io/desec-stack#1312 ·
I maintainer di solito rispondono entro 14 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
blowhorn-ai/blowhorn-mcp#70 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
xdelmo/Portfolio-minimal#613 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
chrisk123999/chris-premades#708 ·
I maintainer di solito rispondono entro 1 giorno