Anthology Diagnostics Technical Writer Navarra Houldin Proofreader Mahayla Galliford Project Director Janelle Jenstad Project Manager Mahayla Galliford Training and Documentation Lead Navarra Houldin Programmer Martin Holmes Programmer Joey Takeda Junior Programmer Tracey El Hajj Social Sciences and Humanities Research Council of Canada

Released with Linked Early Modern Drama Online 1.0

 University of Victoria on the Linked Early Modern Drama Online Platform

This file is licensed under a CC BY-NC_ND 4.0 license, which means that it is freely downloadable without permission under the following conditions: (1) credit must be given to the author and LEMDO in any subsequent use of the files and/or data; (2) the content cannot be adapted or repurposed (except in quotations for the purposes of academic review and citation); and (3) commercial uses are not permitted without the knowledge and consent of the editor and LEMDO. This license allows for pedagogical use of the documentation in the classroom.

Linked Early Modern Drama Online

TEI Customization created by Martin Holmes, Joey Takeda, and Janelle Jenstad; documentation written by members of the LEMDO Team

Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines

n/a

 Automatically generated this file by extracting its content from lemdo.lite.odd.
Prior Reading <ref target="doc:learn_generalDiagnostics">LEMDO Diagnostics</ref> <ref target="doc:learn_handshakeModel">The Handshake Model of Inclusion</ref>
Rationale

LEMDO has created a series of checks for the status of anthologies before they publish. Before an anthology can be released, all checks must be successful for every file slated for publication. This documentation will guide you through the process of checking the status of your anthology and clearing diagnostics in the lead up to anthology release.

Practice: Check Your Anthology Diagnostics

You will check your anthology diagnostics from the LEMDO-dev site. To access the anthology diagnostics, click on the Anthologies tab in the top navigation bar, then select the option for your anthology’s pre-release status. For example, anthology leads wanting to check the status of the DRE anthology would select the option DRE Pre-Release Status. This will bring you to the Web page containing your anthology diagnostics.

Your anthology diagnostic Web page will contain a list of diagnostic checks for each file included in your anthology. Checks that are passed are highlighted green and say [Diagnostic check] is OK. Checks that do not pass are highlighted red and have a message containing PROBLEM. All diagnostic checks must pass for all files included in a release before the anthology is published.

For all files being released (anthology pages and edition pages), there are two checks: Publication status: the status of each file must be published. LEMDO will change the value of the status attribute on the revisionDesc element of files shortly before release. This only happens when all other work in a file is complete. Edition statement: LEMDO has an expected format for the editionStmt element that must be followed before a file is released. Checking the editionStmt should be done when the metadata for a file is updated.

For each file in the editions being included in a release, there is an additional check for license status. This diagnostic checks that the licence element in the publicationStmt contains the necessary information. Each licence element must have a logical licensing date encoded using the from attribute, a person who licenses the file for publication (typically the editor) encoded by linking to the person’s xml:id using the resp attribute, and the anthology that is being licensed to release the edition encoded using the corresp attribute. The publicationStmt (including the licence element) should be updated when the metadata is checked in each file during the pre-freeze phase of anthology release.

Other Resources LEMDO YouTube video: Releasing Your Anthology (Editorial)
Further Reading <ref target="doc:learn_checkLinks">Check Link Validity</ref>