Skip to content

Latest commit

 

History

History
184 lines (123 loc) · 9.85 KB

index.md

File metadata and controls

184 lines (123 loc) · 9.85 KB

This page contains the resources needed to take workshops about the Standardization Survival Kit.

Purpose of the workshops

  1. Stress the importance of documenting research best practices;
  2. Document them with the Standardization Survival Kit.

The expected result of the SSK workshops is the creation and/or review research scenarios.

Workshops

  1. SSK Vienna Workshop, January 31st - February 1st 2019 // Workshop space
  2. SSK 3D Worksop (Marseille), February 25-27 2019 // Workshop space
  3. SSK, Research practices in a digital environment (Athens), May 10 2019
  4. SSK workshop on Archaeological data (Tours), May 23-24 2019

The SSK in 5 minutes

Concept

The Standardization Survival Kit (SSK) is a tool that supports the digital evolution within Social Sciences and Humanities research, by giving access to standards and best practices in a meaningful way, with the mediation of research scenarios. A research scenario is a (digital) workflow practiced by researchers, that can be repeatedly applied to a task that will help to gain material or insights in view of a research question.

These scenarios are at the core of the SSK, as they embed resources with contextual information and relevant examples on standardized processes and methods in a research context. The SSK is an open tool where users are able to publish new scenarios or adapt existing ones. These scenarios can be seen as a living memory of what should be the best research practices in a given community, made accessible and reusable for other researchers.

A presentation of the SSK

This browser does not support PDFs. Please download the PDF to view it: Download PDF.

SSK's survival kit

Create a scenario

How to write a scenario for the SSK?

A tutorial with formal guidelines for creating a scenario can be found in the SSK documentation: SSK Tutorial

SSK user interface

A user interface to create scenarios is under development.
In the context of workshops, a temporary access to a beta version is granted.
The full public version will be available soon.

[Old fashioned] Creating scenarios in XML-TEI

TEI workflow

The documentation of the TEI data model can be found here: SSK TEI model

Scenarios and steps are encoded with the standard XML-TEI. All the information displayed within the SSK proceed from TEI files, hosted on the GitHub repository:

Every TEI file must be validated against the SSK TEI schema.

In case you want to start from scratch, the link to add in the XML declaration is the following: https://raw.githubusercontent.com/ParthenosWP4/SSK/master/spec/TEI_SSK_ODD.rng

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="https://raw.githubusercontent.com/ParthenosWP4/SSK/master/spec/TEI_SSK_ODD.rng"
            type="application/xml"
            schematypens="http://relaxng.org/ns/structure/1.0"?>

Or there is a local copy of the schema in workshops/validation/resources/TEI_SSK_ODD.rng

Template file for scenarios and steps can be used:

Keywords

The SSK scenarios and steps are described with the help of selected vocabularies, among which the most relevant is the TaDirAH Taxonomy:

Other list of terms used in the SSK are:

See the SSK Glossary for a complete overview of all available terms.

In the SSK Glossary, a button copies the exact TEI code:

TEI button for terms

Clicking on the </> symbol copies the following:

<term key="Archaeology and Prehistory" source="AureHAL" type="discipline"/>

NB: It is possible to add new standards entries to the list. Copy the template file available here, fill the requested information (JSON syntax) and send it to ssk [at] inria [dot] fr

Validate XML files

The validation of the SSK TEI files consists of two steps:

  • An classic XML validation with a RELAX NG schema
  • Content-oriented validation with Schematron.
The <oXygen/> XML Editor software makes it easy to validate TEI files.

To create a specific SSK validation scenario in <oXygen/>, see this page for more information: https://www.oxygenxml.com/doc/versions/18/ug-editor/tasks/create-validation-scenario.html

Important It is necessary to specify the schema used (see the Schema section of the document linked above). The settings are the following:

Oxygen Validation scenario

NB: A trial version of <oXygen/> is available here

It is also possible to generate a validation report with a Python script.

This method will output CSV reports with the schematron errors, but won't validate the XML.

Installation
  • It requires Python 3 (and pip) and Java (see here).
  • Clone or download this repository (ParthenosWP4/Workshops).
  • On the console, go to the validation/ folder
  • Run the following command
pip install -r requirements.txt
Usage

Run the python script validation.py with two parameters:

  • the path to the scenario you want to validate as parameter 1
  • the path to the folder of the steps you want to validate as parameter 2
validation$ python validation.py ../Vienna19/corpusModellinginTEI ../Vienna19/corpusModellinginTEI/steps

NB: You may need to replace python by python3, depending on your installation. NB2: For Windows, you also need to use backslahes for the pathes (..\Vienna19\corpusModellinginTEI).

Result

If the script runs successfully, it should create in validation/ a new folder called reports_{Name of the scenario}_{date}_{time}, containing reports for the scenarios checked and its steps.

There is one folder per scenario with:

  • A readme file contains links to the TEI files on the SSK Github, so that you can identify quickly the file corresponding to the report:
    NB: they share almost the same name: theScenario.xml // theScenario_report.csv

  • A csv table : the report for the scenario file

  • A folder containing the reports for each steps.

These reports are tables that contain the following information, related to the XML file checked:

  1. location: In which precise XML element the issue was raised;
  2. line: The line number of the previous location (Caveat, when the message is related to the root element TEI, there is no line number, but you have to check the root (between line 3 to 5, more or less);
  3. role: Three possible values:
  • error: Something is missing or badly formatted and needs to be corrected;
  • warning: It is strongly recommended to take the message into account, but it’s not mandatory;
  • information: The message gives a piece of information, but an action is not necessarily required.
  1. message: A suggestion of what you could do to solve the problem (The most important).

Important note: The messages listed in the tables are not always synonyms of errors in the file, you have to consider them rather like guidelines to check if the corresponding content is correct or not.