DToC
Dynamic Table of Contexts
Please rotate your phone or open DToC on a large screen.
open
- From the Cloud
- From URL
- From your device
- Paste
- New
loading
DToC
Dynamic Table of Contexts
Please rotate your phone or open DToC on a large screen.
open
Dynamic Table of Contexts
The Dynamic Table of Contexts (DToC) provides:
Dynamic Table of Contexts developed to think through interactions between semantic markup, navigational apparatus, & long-form argument. Implemented as part of Voyant Tools through the INKE Partnership
Development: Stéfan Sinclair, Andrew MacDonald Design: Stan Ruecker, Jennifer Guiliano, Milena Radzikowska, Susan Brown Curating | Testing | Documenting: Jeff Antoniuk, Nadine Adelaar, Sharon Balasz, Mark Bieber, Anita Cutic, Brooke Heller, Mihaela Ilovan, Olga Ivanova, Ruth Knechtel, Thomas M. Nelson, Jeff Antoniuk, Megan Sellmer Scoping|Direction|Analysis: Linda Cameron, Patricia Clements,Teresa Dobson, Isobel Grundy, Susan Liepert, Brent NelsonGeoffrey Rockwell, Scott Schofield
DToC integrated into the Canadian Writing Research Collaboratory’s semantic editing and publishing workflows
Development: Andrew MacDonald ,Jeffery Antoniuk, Nia Kathoni, Stéfan Sinclair Project management: Mihaela Ilovan Scoping| Direction | Analysis: Susan Brown
DToC offered as part of the Linked Editing Academic Framework’s suite of Commons tools for Text Encoding Initiative editing and publishing & as an integrated component of the LEAF Virtual Research Environment platform
**Development: **Andrew MacDonald, Luciano Frizzera, Umed Singh Scoping | Direction | Analysis: Susan Brown, Diane Jakacki, James Cummings Curating | Testing | Documenting: Mihaela Ilovan, Amelia Flynn, Kiera Obbard, Rachel Milio
DToC Commons "configures" one or more files encoded using the TEI (Text Encoding Initiative) guidelines, so that the editor can then "curate" the semantic tags in the file(s). Furthermore, by pointing to an index file, the editor can produce an interactive edition that reveals conceptual information as well as semantic content from within the text. The editor can also share the DToC with others, who can then curate the edition to pursue their own readings of the text. When creating a new DToC, the editor opens the "Input Configuration Form" to enter metadata including URL(s) where the TEI-XML file(s) are hosted (we recommend GitHub for this purpose). The "Corpus Parts" section of the form requires the editor to add information in X-Path format so that the tool can properly structure the edition. For step-by-step instructions on how to add this information see DToC Step-by-Step Tutorial. Those interested in learning more about X-Path should look at W3 school's tutorial. Tag curation is managed within the DToC environment, and work is saved in a JSON (JavaScript Object Notation) file. The .json file can be hosted online or downloaded to the desktop. Because the configuration is saved in that .json file, further work on the edition can be done by re-uploading the .json file from the desktop or via a link to where it is hosted online. DToC never makes any changes to the TEI files, which means that multiple DToC editions can be produced from the same files without changing the materials in any way.