Grant interface promise: Read-only visualization surface

未关闭
#576 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
javascript
领域
frontend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
JavaScript
星标
2
派生
3
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CenterForDigitalHumanities/TPEN-interfaces 的其他 Issue

查看 CenterForDigitalHumanities/TPEN-interfaces 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。