This presentation was delivered by Anna Eggers (State and University Library Göttingen) and Fabio Corubolo (University of Liverpool) at PERICLES final project conference 'Acting on Change: New Approaches and Future Practices in LTDP' (Wellcome Collection Conference Centre, London, 30 Nov -1 Dec 2016). This 'PERICLES in practice' session aimed at demonstrating how the PET and the EcoBuilder tools can be used to generate information to populate Digital Ecosystem Model (entities) and how the model can be fed into the Entity Registry Model Repository (ERMR). This session showed how the PERICLES tools can contribute to automated model instance creation and automatic updating. The 'PERICLES in practice' sessions presented specific outcomes of the PERICLES project set in an example workflow, combining tools to accomplish a goal defined by practitioners and derived from real life challenges they experience in their field of work.

1. GRANT AGREEMENT: 601138 | SCHEME FP7 ICT 2011.4.3
Promoting and Enhancing Reuse of Information throughout the Content Lifecycle taking account of Evolving Semantics
[Digital Preservation]
“This project has received funding from the European Union’s Seventh
Framework Programme for research, technological development and
demonstration under grant agreement no601138”.
PERICLES IN PRACTICE
Workflow for the automated updating of Digital
Ecosystem Models with Significant Environment
Information
Anna Eggers (State and University Library Göttingen)
Fabio Corubolo (University of
Liverpool)

2. 1. Overview of the Workflow
2. The Digital Ecosystem Model
a. Our Scenario
3. The Mediator Script for our workflow
4. The PERICLES Extraction Tool
5. The EcoBuilder
6. The Entity Registry Model Repository
7. What to do with the resulting model
▶ For each workflow step: live demo
▶ After each demo: Questions and discussion
Agenda

3. ▶ PERICLES Extraction Tool
◦ extraction of Significant Environment
Information
▶ Digital Ecosystem Model
◦ ontology for modelling Digital Ecosystems
▶ EcoBuilder
◦ tool to create Digital Ecosystem Models
▶ Entity Registry and Model Repository
◦ repository for the created models
▶ further models and model processing Tools
Overview PERICLES Tools for
the Model Updating Workflow

4. ▶ Complex Digital Ecosystems are hard to
maintain.
▶ It is also hard to estimate and analyse the
impact of planned and unplanned change,
and to identify and solve problems.
→ Automated updating of models supports
maintaining, preservation, and analysis
Problems & solutions

5. Model Updating Workflow

6. The Digital Ecosystem
Model

8. General Description
▶ Scenario: A weather scientist is doing research on
cloud thickness. He uses data from the Eumetsat
data services, and cloud computing Service (BIRA).
▶ EUMETSAT is the European Organisation for the
Exploitation of Meteorological Satellites. Besides
the launch and operation of satellites it is also
responsible for delivering satellite data to end-
users, e.g. scientists.
Space Science: Experiment Workflow

9. General Description
▶ SEVIRI Images is data from the Meteosat Second
Generation (MSG) geostationary satellite with
Spinning Enhanced Visible and InfraRed Imager
(SEVIRI). It senses the Earth's atmosphere in 12
different spectral channels.
▶ BIRA: Belgian Institute for Space Aeronomy.
Provides the necessary technical infrastructure for
carrying out the calculation based experiment.
Space Science: General Workflow

10. General Description
▶ Workflow: A Scientist…
◦ accesses the EUMETSAT data service via a web portal
interface to select and download the relevant data
◦ makes use of an own calculation script
◦ transmits data and calculation script to BIRA services
◦ executes the calculation process
◦ downloads the resulting data to his local system
◦ view and analyze the results for a scientific
publication.
▶ Three complex areas are interacting: Local system of the
scientist, EUMETSAT data services, BIRA computing
system.
Space Science: General Workflow

12. Our Scenario for the first
workflow

14. Step 1: Template Creation

15. The Mediator Script is the controller of the
workflow.
▶ has a scenario specific template
▶ gets information from PET
▶ puts the information into the template to
create DEM instances
▶ sends the model instances to ERMR
The Mediator Script

16. → Create scenario dependent DEM template
DEMO Step 1:
Template for our science
Scenario

17. ▶ The Digital Ecosystem Model
▶ Our scenario
▶ Mediator Script
▶ Creation of scenario dependent templates
Questions?

18. The PERICLES Extraction
Tool

19. PERICLES Extraction Tool (PET)
• Open source framework for the extraction of
environment information
• Sheer curation
• Generic, modular, domain agnostic
• Collection by observation
o monitor environment changes
o extraction in case of change
• Snapshot of the system environment
• To observe unstructured workflows

20. • Extract information that is usually ignored by
current metadata extractors
• From outside the digital object
• At the right time and place: within the creator
or curator’s environment
• Supporting continuous extraction (time
series)
• Be easily customisable with extraction
profiles
PET aims

21. The PERICLES Extraction Tool

22. • Available and used system resources
• File format identification and checksums
• Currently running processes
• Event information from processes
• Graphic configuration information
• MS Office and PDF font dependencies
• Native commands
PET Extraction Modules

23. Step 2: PET Configuration

24. Step 3: SEI Extraction

25. Step 4: Information Sending

26. → Step 2: Configure PET for the scenario
→ Step 3: Extraction of Significant Environment
Information
→ Step 4: Send extracted information
DEMO Step 2-4:
PET in our Workflow

27. ▶ The EcoBuilder
▶ Model Instantiation
▶ The Entity Registry Model Repository
▶ Model sending / storing
Questions?

28. The EcoBuilder

29. Tool for the creation of Digital Ecosystem Models
▶ GUI
◦ Simplifies the creation of the model
◦ Usable by scenario experts without the
necessity to write ontology or Java sources
▶ Java API
◦ Facilitates integration into workflows
◦ Used by our Mediator Script!
▶ Uses Java Jena API - can output OWL/XML or Turtle
EcoBuilder

31. Step 5: Template Instantiation

32. → Instantiate the template with the
extracted information
DEMO Step 5:
Template instantiation

33. Entity Registry Model
Repository

34. ▶ Large scale distributed data store and model
repository (triple store)
◦ in PERICLES model and data store
▶ Accessible via Web interface or RESTful API
▶ Notification system
The Entity Registry Model
Repository

35. Step 6: Model Submission

36. → Send the updated model to the repository
DEMO Step 6:
Model Submission

37. ▶ The EcoBuilder
▶ Model Instantiation
▶ The Entity Registry Model Repository
▶ Model sending / storing
Questions?

38. Step 7: Model Analysis

39. Other PERICLES tools connect to the ERMR
where the models are stored. They can get the
models to
▶ model validation and difference calculation
(LRMS)
▶ visualise the impact of change (MICE)
▶ edit policies (Policy editor)
▶ assess content and risks (Appraisal Tool)
▶ high level translation/connection layer for
PERICLES tools (PerSIST API)
DEM Step 7:
Get and analyse the models

40. ▶ simulate impact of change
▶ reveal single point of failures
▶ use in a sheer curation scenario
◦ extraction of significant environment
information
◦ automatic updating of models
▶ analyse provenance
Resulting Model

41. Questions?
The presented tools are available under open source
license on GitHub: https://github.com/pericles-project