Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Enable Multiple Transcription Layers

Open
  • Is something wrong?
#1 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
content

Research direction

The issue names sc:Manifest and its layer property, but no repository files or tests. Start by locating manifest handling and the existing creation and editing paths, then compare their behavior with the transcription, translation, commentary, and palimpsest use cases. Done means layer creation and editing support those use cases.

Written by the indexing model from the issue text.

Description

proposed feature

From @cubap on October 16, 2015 3:14

Include creation and editing support for the layer property insc:Manifest which may separate transcription annotations into trans-canvas layers of a shared purpose and potentially continuous content.

Use Cases
  1. A music manuscript may have the notes annotated in MEI terms, while the lyrics are transcribed in one layer and translated in another. This application would not offer a preference to one, as another arrangement may, but still allows for alignment.
  2. A heavily glossed or commented manuscript may benefit from separate layers for the main text and the running commentary.
  3. A palimpsest or similarly reused support may contain parallel annotations, which may in turn preference their own reading angles or image choice.

Copied from original issue: cubap/TPEN3#1

Dominant language
HTML
Stars
5
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/TPEN3

All issues in CenterForDigitalHumanities/TPEN3

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.