Grant interface promise: Read-only visualization surface
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- javascript
- Área
- frontend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- JavaScript
- Estrellas
- 2
- Forks
- 3
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CenterForDigitalHumanities/TPEN-interfaces
-
enhancement ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
CenterForDigitalHumanities/TPEN-interfaces#569 · 1 comentario ·
-
enhancement ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
CenterForDigitalHumanities/TPEN-interfaces#566 · 1 comentario ·
-
bug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
CenterForDigitalHumanities/TPEN-interfaces#562 · 1 comentario ·
-
enhancement ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
CenterForDigitalHumanities/TPEN-interfaces#526 · 1 comentario ·
-
License link borkedAbiertobug ready-for-agent
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
CenterForDigitalHumanities/TPEN-interfaces#516 · 1 comentario ·
Todos los issues de CenterForDigitalHumanities/TPEN-interfaces
Issues similares
-
parity: scripting.net's net-http row fails on macOS with errno 61 where the BDS golden has 111AbiertoBug Tests
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
JSPrismarine/JSPrismarine#3384 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
desec-io/desec-stack#1312 ·
Los mantenedores suelen responder en 14 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
blowhorn-ai/blowhorn-mcp#70 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
xdelmo/Portfolio-minimal#613 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
chrisk123999/chris-premades#708 ·
Los mantenedores suelen responder en 1 día