Factsheet

Resource reviewed
Title Transkribus
Editors University of Innsbruck and READ-COOP SCE
URI https://transkribus.eu/
Publication Date 2019
Date of last access 10.12.2021
Reviewer
Name Perdiki, Elpida
Affiliation Democritus University of Thrace
Place Komotini, Greece
Email eperdiki@helit.duth.gr
General information
Software type

(?)
Software tool: A “Tool” is broadly defined as a computational application to be used for accomplishing one task or a number of related tasks in the process of digital scholarly editing.
Virtual Reseaerch Environment (VRE): An “environment” is defined as a platform on which various tools (independent or not) are working as an integrated whole in order to perform a series of tasks or to cover the entire workflow.
What type of software is it?
 Virtual Reseaerch Environment (VRE)
Identification of the environment

(?)
Operating system: e.g. for stand-alone applications
Web browser: for web-based applications, web-services, and APIs
Another application: i.e., a plugin
On which platform runs the tool?
 Operating system
Purpose
For what purpose was the tool developed?
 developed to accomplish a general task
Funding
Which is the financial model of the tool?
 Support-based
Maturity
What is the development stage of the tool?
 Release
Methods and implementation
Programming Language
Which programming languages and technologies are used?
 C family, Java, Python, Other: HTML
Reuse
Does the tool reuse portions of other existing software?
 no
Input format
Which input formats are supported?
 .txt, .pdf, Other: .jpg, IIIF
Output format
Which output formats are supported?
 .xml/tei, .txt, .pdf, Other: .docx
Encoding
Which character encoding formats are supported?
 latin-1, utf-8, utf-16, Other: MUFI (Medieval Unicode Font Initiative)
Encoding preprocessing
Is a pre-processing conversion included?
 yes
Dependencies
Does the documentation list dependencies on other software, libraries or hardware?
 no
Dependencies installation
If yes, is the software handling the installation of dependencies during the general installation process (you don’t have to install them manually before the installation)?
 not applicable
Documentation and support
Documentation
Is documentation and/or a manual available? (tool website, wiki, blog, documentation, or tutorial)
 yes
Documentation format
Which format has the documentation?
 .html
Documentation parts
Which of the following sections does the documentation contain?
 ‘Getting Started’ section (installation and
configuration), Step-by-step instructions, Examples, Troubleshooting (a selection of possible error messages and related
solutions), FAQ, Support
Documentation language
In what languages is the documentation available?
 English, German, Italian
Support
Is there a method to get active support from the developer(s) or from the community?
 yes
From of support
Which form of support is offered?
 Help desk, Forum, Mailing-list
Issue tracker
Is it possible to post bugs or issue using issue tracker mechanisms?
 yes
Usability and sustainability
Build and install
Grade how straightforward it is to build or install the tool on a supported platform:
 straightforward
Tests
Is there a test suite, covering the core functionality in order to check that the tool has been correctly built or installed?
 no
Portability and interoperability
On which platforms can the tool/software be deployed?
 Linux/BSD/Unix, Mac OS X, Windows, Not applicable (if web-based for example)
Devices
On which devices can the tool/software be deployed?
 Desktop, Laptop, Not applicable (if web-based for example)
Browsers
If the tool is web-based: On which browsers can the tool/software be deployed?
 Mozilla Firefox, Google Chrome, Safari
Plugins
If the tool is web-based: Does the tool rely on browser plugins?
 no
API
Is there an API for the tool?
 yes
Code
Is the source code open?
 yes
License
Under what license is the tool released?
 GNU/GPL
Credits
Does the software make adequate acknowledgement and credit to the project contributors?
 yes
Registered
Is the tool/software registered in a software repository?
 yes
Possible contribution
If yes, can you contribute to the software development via the repository/development platform?
 not applicable
Analysability, extensibility, reusability of the code
Analysability
Can the code be analyzed easily (is it structured, commented, following standards)?
 Unknown
Extensibility
Can the code be extended easily (because there are contribution mechanisms, attribution for changes and backward compatibility)?
 Unknown
Reusability
Can the code be reused easily in other contexts (because there are appropriate interfaces and/or a modular architecture)?
 no
Security and privacy
Does the software provide sufficient information about the treatment of the data entered by the users?
 yes
Supportability and maintenance
Is there information available whether the tool will be supported currently and in the future?
 yes
Citability
Does the tool supply citation guidelines (e.g. using the Citation File Format)?
 no
User interaction, GUI and visualization
User profile
What kind of users are expected?
 Humanities researcher, Digital humanist, General public
User interaction
What kind of user interactions are expected?
 Reading, Text editing, Text analysis, Searching
User Interface
What kind of interface does the tool provide?
 Graphical User Interface (GUI)
Visualization
Does the tool provide a particular visualizations (in terms of analysis) of the input and/or the output data?
 no
User empowerment
Is the user allowed to customize the functioning of the tool and the output configuration?
 no
Accessibility
Does the tool provide particular features for improving accessibility, allowing „people with the widest range of characteristics and capabilities” to use it?
 no
Personnel
Editors University of Innsbruck and READ-COOP SCE
Programmers University of Innsbruck and READ-COOP SCE
Advisors University of Innsbruck and READ-COOP SCE
Designers University of Innsbruck and READ-COOP SCE
Contributors University of Innsbruck and READ-COOP SCE