Define Service Description, Requirements and Components for Data Stories including a workflow schema (visual)

[roelandordelman]

As a scholar, I want to tell a story illustrated by live queries on CLARIAH data sources and attractive visualisations of the answers in order to present the results/value of my data work.

We want to bring together:

• the WP4 / DRUID activities on data stories (mainly focussed on sparql endpoint + visualisations + publication in run time environment)
• the WP5 / Media Suite activities on data stories (mainly focussed on API search + visualisations + publication in blogs / enhanced publications referencing to the runtime environment/Media Suite)
• WP3 / La Machine activities (Jupyter Notebooks)

We need to:

• [ ] define the service based on the requirements from WP4-5 activities and plans

• [ ] identify the main components and visualize the workflow(s) in a diagram.

[proycon]

The 'LaMachine activities' around Jupyter Notebooks merely consist of the fact that LaMachine offers a Jupyter Hub/Lab environment (with possible intergration in the CLARIAH authentication infrastructure), and providing an execution context to the notebooks/IDE in which a lot of software is available. Content-wise there aren't any coordinated WP3 activities around data stories.