Skip to content

Main content

Corpus Rights Statement Label

Preserve literal corpus rights wording with an explicit source reference without determining copyright or reuse permission.

Loading tool…

Description

Label a corpus with supplied rights wording and source reference.

Digital editions separate source readings, editorial uncertainty, witness locators, image requests, identifiers and rights statements. XML character/attribute rules differ from display labels, while URI fragments and TEI pointers need their target-document context. An identifier key or formatted token does not authenticate a witness, validate an edition or authorize reuse.

Label a corpus with supplied rights wording and source reference.

When to use this tool

Use Corpus Rights Statement Label when you already have corpusId, rightsWording, sourceReference and need to label a corpus with supplied rights wording and source reference.

How to use the tool and how it works

  1. Enter corpusId, rightsWording, sourceReference. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read label. Use the output convention below.

Require all three strings nonempty; quote rightsWording as JSON text and append corpus/source labels.1

Input fieldMeaning and unitsAccepted input
corpusIdCorpus IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
rightsWordingRights WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceReferenceSource ReferenceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
labelLabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "corpusId": "C17",
    "rightsWording": "Reuse under stated terms",
    "sourceReference": "licence record 3"
  },
  "output": {
    "label": "C17; rights=\"Reuse under stated terms\" [licence record 3]"
  }
}

Limitations and assumptions

  • A rights label does not grant permission, verify ownership, establish license compatibility or authorize reuse.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Validate the complete XML/TEI document or IIIF request when technical conformance matters, and inspect the original witness and rights record for editorial use. Preserve uncertain readings, source order and attribution rather than treating local tokens as verified scholarly interpretations.

References

  1. Calculation and input contract: digital-humanities/corpus-rights-statement-label — tool.io

Similar or alternative tools