Pilot "Editionsprojekte in der Schweiz"

Zielsetzung

Konkrete Beispile, fokusiert auf tools und institutional support (nicht eine allgemeine Übersicht).

Zusammenhänge von Tools, Workflows und Institutionen zu verstehen.

Für die Mitglieder der DARIAH WG.

Vernetzung und Berührungspunkte zwischen Projekten.

 

Research question

  • landscape of editions is very fragmented. people end up having different institutional orioentations

    • towards Dasch, fondue etc

  • idea, take example of editions and model the workflows, how do they look like and how do they involve different institutions?

Wichtigste Klassen

Classes

Examples

Comments

Classes

Examples

Comments

Institutionen

DaSCH, Swissuniversitites, UNI Z, e-editiones

 

Tools

Geovistory, Transkribus, TEI Publisher, Fondue, eSkriptorium, Oxygen

 

Standards

TEI, IIIF

 

Edition

Edition = Event + Output + Group

  • Institutionen & ihr Rollen in den Editionsprojekten

  • Personen & ihre Rollen in den Editionsprojekte

 

  • Editionsprojekte

Edition = Event + Output + Group

  • Institutionen & ihr Rollen in den Editionsprojekten

  • Personen & ihre Rollen in den Editionsprojekte

 

Editionen (plus relevante Aspekte)

Fragen:

  • wie modelliert man ein “tool”?

  •  

 

Personen

Information of interest

Properties

Examples

Description & Comments

Information of interest

Properties

Examples

Description & Comments

Person

  • First Name

  • Surname  

  • Further Surnames

 

 

Birth

  • Date of Birth

  • Place

 

 

Gender

man/woman

 

 

origine

  • before studies

  •  

 

 

functions in “institutions”

  • president of university

 

 

roles/positions/functions

  • professor in modern languages

 

 

 

Editionsprojekte

Definition

  1. Group - eine Gruppe von Leute die an einer Edition beteiligt sind

  2. Event - Prozess der Entstehung einer Edition mit entsprechenden sub-Events. An edition as an event consists of a series of sub-events that represent different steps of the edition process. (For the purpose of this project we map these sub-events conceptually, rather than in a content-specific manner? i.e. we speak of “Scanning of paper manuscripts” as an event, and not “Scanning manuscripts X1234 to Y9876”? or both/either?)

  3. Output - eine Sammlung von Outputs von einer Edition (TEI-Daten, HTML-Darstellung des Textes), die entsprechend den Events Ihrer Entstehung modelliert sind

Information of interest

Properties

Examples

Description & Comments

Information of interest

Properties

Examples

Description & Comments

Name

 

 

 

Relations

 

 

 

Dates

  • start date

  • end date

 

 

Zweck

 

 

 

Institutions

Information of interest

Properties

Examples

Description & Comments

Information of interest

Properties

Examples

Description & Comments

Name

 

 

 

Relations

funder

host (of an edition project, of a tool, of a database etc.)

collaborating institution

project lead institution

provider of services

 

 

 

 

 

 

Tools

How do we model a tool?

Tools can be large software offered by commercial or non-commercial providers e.g. Transkribus or Neo4J or TEIPublisher, they can also be small things developed in-house, e.g. a python script used for a particular purpose.

Services

Operations like DaSCH developing a data model. Is it enough to model this as an event?