XmsDescDataCreation - chigc/documentation GitHub Wiki

DataTable to MsDesc

The initial data collection was carried out using a Google Spreadsheet. The following transformation workflow was created to convert the data semi-automatically into XML/TEI, which serves as the source data for the edition.

Step 1 Download of Spreadsheet:

  • Download of Table from Google Drive
  • Delete Unnecessary rows (not! columns) and sheets, e.g. header-row, legend of color-coding, etc.)

Step 2 Spreadsheet to TEI-Table

  • Conversion of the Spreadheet table to a TEI-Table with TEIGarage.

Step 3 XSL Transformation:

  • Transformation of TEI-Table to TEI-Files with chigc.xsl
  • all information of Spreadsheet represented in the TEIHeader
  • One TEI-File per row ( = One TEI-File per manuscript)

Step 4 Manual Control of Data

  • check on correct transformation of dates (esp. when manuscript has multiple dates)
  • check on correct transformation of Version / Extension

MsDesc

  • Different levels of data collection
  • Erfassungstabelle --> "basis metadata collection"
  • Erfassungstabelle + Info from Form --> "rich metadata collection"

MsDesc Github Workflow

Prerequisites:

  • Github Account & writing rights to the data repository
  • OxyGen Editor
  • Github Desktop (Introduction to Github Desktop can be found here)

0) Set Up

  • Clone software and data repository from Github.
  • Associate the framework in the Oxygen Editor (see Wiki, on how to do this)
  • Configure OxyGen Editor:

Create Oxygen Project vor easier access to the files (see here)
Set "Author" as default view (see here)

1) Working on already "registered" Manuscript

  • Decide, who is working on which manuscript to minimize the risk of merge conflicts

  • Open Github Desktop
  • Fetch (and Pull) Software Repository, to keep it up to date
  • Fetch (and Pull) Data Repository, to have access to the newest changes

  • Open OxyGen Editor and select the manuscript in the project view
  • Fill the data into the Form (Framework)
  • Change the “Status” on the bottom of the Page, if a phase is done

Data Recording of a new Manuscript (DONE)
Review of Content (DONE)
Publicationready


  • Open Github Desktop
  • Commit and Push your changes to the Repository on Github

!! Commit and Push your changes regularly, at least at the end of the workday!!!

2) Adding new Manuscripts

  • Send us (Team Graz) an e-mail with the following information on the manuscript:
  • City
  • Name of Institution, Library or Archive
  • Signature
  • Team Graz will create the initial TEI for you on GH and inform you, that the file is fetchable and ready to be worked on.

3) Introduce new team members to work on manuscripts

  • They need to send us their GitHub credentials in order to give them the necessary permissions.

Adding data via the Framework:

Rules:

  • Add ID's everywhere - even if the item is not in the manuscript and you chose 'no' in the dropdown;
  • Not every field has it's own note field, sometimes only a notefield for the whole section is provided - if you want to take notes to a specific item in those sections, not them down as follows --> {ItemName1}: observation; {ItemName2}: observation; e.g.

Color Coding: somethingsomething; Letter Coding: somethingsomething

ID special cases:

Some ID's might not be so easy to find, because the name in the ID is written differently. Below is a list of those special cases:

  • Zedekiah : #p-sedechia
⚠️ **GitHub.com Fallback** ⚠️