Grant interface promise: Read-only visualization surface

Abierto
#576 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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

enhancement needs-triage

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 (tag tpen-read-only-view-transcribe), hosted at interfaces/project/view-transcription.html (route /project/view-transcription, og:url points at app.t-pen.org/components/read-only-transcribe/?projectID=).
  • It is effectively unreachable: repo-wide, view-transcription appears only in that page itself and the route list in 404.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 — collectionID parsed, never consumed; collection-level import listed as future work in components/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-screen flow) — 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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CenterForDigitalHumanities/TPEN-interfaces

Todos los issues de CenterForDigitalHumanities/TPEN-interfaces

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.