Computational Publishing Service
Computational Publishing Service – Publish using LOD directly from any Wikibase as multi-format outputs – web, print, or hybrid.
Keywords
Computational Publishing Service (CPS) enables publishing directly from digital collections and data. Users can create scripts to retrieve text, media, code, or data and output as multi-format publications, and as interactive (Jupyter Notebooks) and LOD versions (RDFa, JSON, etc.).
Digital humanities scholars produce papers and monographs that are based on data analysis and use data visualisation, as well as using sources with media and code – 3D models, video, or GND authority data, etc. We support all of these media and code types using modern Open Science infrastructures. At the same time the system provides high quality automated typesetting for PDF and multi-format publication outputs. The system is designed for Open Access Press submission workflows and packages publications as FAIR Principles based repository deposits.
Cultural organisations can use the system to automatically generate websites, produce publication series, or retrieve packaged assets from their digital cultural collection.
CPS uses pipeline architecture to connect different software. At its core it uses Wikibase4Research for LOD storage, Jupyter Notebook for authoring, Quarto render engine for multi-format outputs, and GitLab / GitHub for publication storage. Other NFDI4Culture services can be used as well: Antelope, Semantic Kompakkt, and Culture Knowledge Graph have pipeline integration options.
The pipeline has full open-source versions available.
Use Cases
Use Case #1 Publishing directly from a digital cultural collection using Jupyter Notebooks with Wikibase and Linked Open Data.
Context: A digital collection manager needs to make a catalogue publication - for online, app, and print - to accompany an exhibition.
User Groups:
- Collection managers;
- Curators and Digital Humanities scholars;
- Designers and web developers.
Key requirements:
- Creation of SPARQL queries from Wikibase, Linked Open Data Sources, and APIs;
- Jupyter Notebook editing;
- Creation of multi-format style templates;
- Can be extended as a way to supply content - and keep a record of what was supplied - from collection to different user communities.
Use Case #2 Editorial group producing book series using an online editor with automatic typesetting for multi-format outputs including print-on-demand.
Context: An editorial group needs to commission and review a monograph series – they want an equivalent to Google Docs but with digital sovereignty and academic features like citation management.
User Groups:
- Author, editors, and reviewers;
- Open Access press;
- Typesetting layout designers.
Key requirements:
- Use online editor;
- Create template for multi-format outputs using CSS;
- Single source metadata management;
- Git publication management.
Use Case #3 OER research group creates a book in two days using the Book Sprint co-creation method - online or in-person.
Context: A research group is tasked with creating a guide on a topic. The group members are not familiar with book production or editing.
User Groups:
- Researchers and educators;
- Participants from outside of research;
- Experts or subject specialists.
Key requirements:
- Contributors participate in co-creation process;
- Publication managers coordinate production, document management, and metadata;
- Use toolset: Fidus Writer, Git, and Thoth metadata management.
Service Architecture
Software Stack:
- Wikibase4Research
- Jupyter Notebook
- Quarto
- W3C Paged Media CSS (Vivliostyle)
- Fidus Writer
- W3C Web Publication (Manifest)
- 5-Star Linked Open Data (Documents)
- GitLab/GitHub / GitLab Pages / Git VM GitPod (runtime environment)
Infrastructure Options:
- Open-source publication software, templates and instructions ready to use online
- Consultancy and support services available
- Managed services maintained at TIB
Code Repository:
Contact
Contact Person:
Simon
Worthington