Assessment criteria 'Services'

All Services are assessed with a set of general assessment criteria. In addition, for each subtype of Services extra metadata or additional criteria may be required. The tables below specify the extra metadata and general assessment criteria that apply to all services. The type specific metadata and criteria are listed on page 24-30 of De Leeuw et al. 2017.

---

Extra metadata	Description
Support contact	Provide contact details (email address, or other means of soliciting support, like issue tracker, helpdesk, feedback form).
Underlying software	Detail which software underlies the service. If the software itself is being developed and maintained then it is a separate contribution (namely, Software development).

---

Assessment criterion	Description
Maturity level	Indicate whether the service an ad hoc service (proof of concept), whether it is repeatable (best effort basis, could change or go offline), or the service is managed (stable and long-term commitment in place).
Support level	Indicate whether there is a support Contact, and whether or not it is served with dedicated capacity to process support requests.
User documentation	Indicate whether user documentation is available (online or as contextual help in the application) and in what state it is (partial or comprehensive).
Developer documentation	Indicate whether developer documentation is available (inline in the code and/or comprehensive documentation of the system architecture, functions and APIs as part of the software package or online) and in what state it is (partial or comprehensive).
Administrator documentation	Indicate whether administrator documentation is available and in what state it is (partial or comprehensive).
Multilingual User Interface	Indicate whether the UI is available in English (working language of DARIAH) and/or other languages, and its support for localisation, multi-script (allows to switching scripts in one input field) and right-to-left text (where applicable).
Impressum & Terms of Use	Indicate the availability of an Impressum (+ Info on use of cookies) & Terms of Use.
API	Indicate whether the service exposes an API - programmatic access to (read and write) data; typically, RESTful web service, OAI-PMH endpoint, Feeds, but also an option to call the service/application via URL passing data as parameter.
Monitoring	Indicate whether the service is monitored locally or by the DARIAH monitoring service (added value of being monitored by DARIAH is the sense of the service being part of one coherent infrastructure and an independent control instance).
User statistics	Indicate whether user statistics are being collected via a an own solution or via DARIAH (user statistics via DARIAH allow to view the service in the context of the bigger infrastructure).
DARIAH login	Indicate whether the service supports federated DARIAH login (Single-Sign-On, AAI via Shibboleth https://de.dariah.eu/en/aai), and/or via OpenID.