Standard Mappings vs. Columns in TVMTS

[jonathanrobie]

Paratext and the versification mappings use a set of standard mappings, and say that each custom mapping is based on one of these:

• eng.json
• ethiopian_custom.json
• lxx.json
• org.json
• rsc.json
• rso.json
• vul.json

Each of these comes with its own mappings:

  "mappedVerses": {
    "DAG 2:1-49": "DAN 2:1-49",
    "DAG 3:1-23": "DAN 3:1-23",
    "DAG 3:91-97": "DAN 3:24-30",
    "DAG 4:1-3": "DAN 3:31-33",
    "DAG 4:4-37": "DAN 4:1-34",
    "DAG 4:1-2": "DAN 4:4-5",
    "DAG 5:1-30": "DAN 5:1-30",
    "DAG 6:1-29": "DAN 6:1-29",
    "DAG 7:1-28": "DAN 7:1-28",
    "DAG 8:1-27": "DAN 8:1-27",
    "DAG 9:1-27": "DAN 9:1-27",
    "DAG 10:1-21": "DAN 10:1-21",
    "DAG 11:1-45": "DAN 11:1-45",
    "DAG 12:1-13": "DAN 12:1-13",
    "EXO 20:13": "EXO 20:14",
    "EXO 20:14": "EXO 20:15",
    "EXO 20:15": "EXO 20:13",
    "EXO 21:16": "EXO 21:17",

These mapping support splitting and merging, but not partial verses.

I think the task for the versification tool is to identify missing mappings or mappings that differ from the standard mapping and override what is in the standard mapping.

Or do we need to identify a base for the text as well?

[jonathanrobie]

A user can specify a base versification.

If a base versification is present, the versification is generated as follows:

• maxVerses: as computed from the derived text
• partialVerses: as computed from the derived text
• verseMappings: never duplicate a mapping from the base versification, omit it if it already exists
• excludedVerses: manual
• unexcludedVerses: manual

If you don't want that, don't specify a base.

[jonathanrobie]

@jonathanrobie to close when implemented.