<?xml version="1.0" encoding="UTF-8"?><div xmlns="http://www.tei-c.org/ns/1.0" xml:id="learn_anthDiagnostics" resp="or:odd_HOUL3_wtm or:odd_GALL2_pfr" ana="audAnthologyLead audEncoder">
   
   <head>Anthology Diagnostics</head>
   
   <div xml:id="learn_anthDiagnostics_prior">
      <head>Prior Reading</head>
      
      <list rend="bulleted">
         <item><ptr target="doc:learn_generalDiagnostics"/></item>
         <item><ptr target="doc:learn_handshakeModel"/></item>
      </list>
   </div>
   
   
   <div xml:id="learn_anthDiagnostics_rationale">
      <head>Rationale</head>
      
      <p>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.</p>
   </div>
   
   
   <div xml:id="learn_anthDiagnostics_practice">
      <head>Practice: Check Your Anthology Diagnostics</head>
      
      <p>You will check your anthology diagnostics from the LEMDO-dev site. To access the anthology diagnostics, click on the <quote>Anthologies</quote> 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 <quote>DRE Pre-Release Status</quote>. This will bring you to the Web page containing your anthology diagnostics.</p>
      
      <p>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 <quote>[Diagnostic check] is OK.</quote> Checks that do not pass are highlighted red and have a message containing <quote>PROBLEM</quote>. All diagnostic checks must pass for all files included in a release before the anthology is published.</p>
      
      <p>For all files being released (anthology pages and edition pages), there are two checks:
         <list rend="numbered">
            <item>Publication status: the status of each file must be <val>published</val>. LEMDO will change the value of the <att>status</att> attribute on the <gi>revisionDesc</gi> element of files shortly before release. This only happens when all other work in a file is complete.</item>
            <item>Edition statement: LEMDO has an expected format for the <gi>editionStmt</gi> element that must be followed before a file is released. Checking the <gi>editionStmt</gi> should be done when the metadata for a file is updated.</item>
         </list>
      </p>
      
      <p>For each file in the editions being included in a release, there is an additional check for license status. This diagnostic checks that the <gi>licence</gi> element in the <gi>publicationStmt</gi> contains the necessary information. Each <gi>licence</gi> element must have a logical licensing date encoded using the <att>from</att> attribute, a person who licenses the file for publication (typically the editor) encoded by linking to the person’s xml:id using the <att>resp</att> attribute, and the anthology that is being licensed to release the edition encoded using the <att>corresp</att> attribute. The <gi>publicationStmt</gi> (including the <gi>licence</gi> element) should be updated when the metadata is checked in each file during the pre-freeze phase of anthology release.</p>
   </div>
   
   
   <div xml:id="learn_anthDiagnostics_otherResources">
      <head>Other Resources</head>
      
      <list rend="bulleted">
         <item>LEMDO YouTube video: <ref target="https://youtu.be/oTCFSgTUG4w">Releasing Your Anthology (Editorial)</ref></item>
      </list>
   </div>
   
   
   <div xml:id="learn_anthDiagnostics_further">
      <head>Further Reading</head>
      
      <list rend="bulleted">
         <item><ptr target="doc:learn_checkLinks"/></item>
      </list>
   </div>
</div>