IML stands for ISE Markup Language, a boutique SMGL language with some tags borrowed from TEI-XML, HTML, and DublinCore. This markup language was processable only in the ISE Platform. ISE, DRE, and QME editors used these tags to prepare the following types of texts:

These files come to us in two different ways. We have rescued files from the ise-developers repository (a secure repository hosted on HCMC space), as finished and published (although not necessarily peer-reviewed) files. These files are usually easier to convert than unpublished files because the IML was corrected and validated in the ISE’s old workflows. When you are remediating these files, you’ll be able to view the output of the original IML on the staticized ISE, DRE, and QME sites, which can be helpful if you are trying to confirm the mode of parts of the text (prose or verse) or if you are checking a text for completion. We also receive IML files directly from editors and/or anthology leads who are continuing to work on their editions in IML. These are in-progress, unpublished files that require extra attention in the conversion process because the IML inevitably contains many errors. They require extra attention in the remediation process because there’s nothing to guide you on the staticized ISE, DRE, and QME sites for these files. (Note that LEMDO has committed to doing a one-time conversion from IML to TEI for in-progress files. Once the Developers and Remediators have remediated the file, the editor will have to work in TEI or pay someone to work in TEI.)

These files were created in (or moved to) an XWiki platform. We no longer have access to the original files from XWiki. The XWiki files that LEMDO was able to retrieve were batch-converted in 2018. The only work remaining is the remediation of those files. The output from the published XWiki files can be seen on the staticized ISE, DRE, and QME sites, which you as Remediator may find helpful.

We won’t have to convert any new XWiki files. With the platform having failed in 2018, no one has been able to create XWiki files.

We do seem to be missing some material that was probably created in XWiki. Ultimately, the editor and/or anthology lead are responsible for ensuring that their LEMDO edition contains all the material that should be in the edition. If an editor or anthology lead alerts us to missing material, we simply ask the editors to send us their original files and we encode them from scratch.

Types of materials from XWiki include:

Some files were encoded in an XML-compliant set of IML tags and validated against an RNG schema. They were saved as .xml files.

Types of files that were prepared in XML include:

We also have programmatic conversions for the transcriptions created by the Text Creation Partnership and encoded in TEI-XML P4. Our conversions retrieve the TCP files from Github and convert them to LEMDO’s TEI-XML P5 customization. The transcriptions contain errors, and do not include all of the material that LEMDO captures (such as bibliographical features of the text and special pieces of type). Remediation therefore includes both correction of the transcription as well as proofing of the encoding.

We have the ability to create camera-ready copy for potential print publication. Our print output is a shorter version of the edition. To create the print output, we have to create alternate short versions of some annotations, designate some annotations onlineOnly, and split up some annotations into various types. There is no programmatic conversion for this work. These remediations are done by humans (usually the Remediator and the Project Director working together) on our own already-remediated and valid XML files.