Deprecated records validation errors

[wlpotter]

Following the instructions for our current system for merging and deprecating duplicate records (https://github.com/srophe/syriaca-data/wiki/Deprecated-Records), I get the following schema errors. Using person record 1486 and the deprecated 2078.

• no issues with the non-deprecated record (i.e., 1486 validates even after following the Deprecated Records steps)

The following are issues in the deprecated record (2078 in this example):

• publicationStmt/idno[@type="redirect"], https://github.com/srophe/syriaca-data/blob/development/data/deprecated/persons/tei/2078.xml#L51. Validation error: Only an <idno> element with a @type attribute of "deprecation" may have a @change attribute.
• revisionDesc/@status of "deprecated", https://github.com/srophe/syriaca-data/blob/development/data/deprecated/persons/tei/2078.xml#L130. Validation error: value of attribute "status" is invalid; must be equal to "draft", "incomplete", "published" or "uncorrected-draft"
• body/desc, https://github.com/srophe/syriaca-data/blob/development/data/deprecated/persons/tei/2078.xml#L149. Validation error: element "desc" not allowed here; expected element "listPerson"
  • Also an error on the @change and @type attributes on this desc
• person/idno[@type="redirect"], https://github.com/srophe/syriaca-data/blob/development/data/deprecated/persons/tei/2078.xml#L158. Validation error: Only an <idno> element with a @type attribute of "deprecation" may have a @change attribute.

@dlschwartz not sure if we care about any of these since the records are deprecated and so won't get serialized or even used in search, etc. They're honestly just here for data provenance and URI redirection reasons, but wanted to raise whether the schema should handle deprecated records in any way?