Skip to content
Sünje edited this page Feb 7, 2017 · 12 revisions

Notes from the CERN Analysis Preservation/DASPOS/RECAST workshop

February 2nd, 2016 at CERN

Agenda: https://github.com/cernanalysispreservation/analysispreservation.cern.ch/wiki/Joint-CERN-Analysis-Preservation-DASPOS-RECAST-workshop

Additional Materials (slides): https://indico.cern.ch/event/611389/

Attendees: Representatives from LHC experiments, CAP team, members from DASPOS and RECAST

Notes

###Introduction

  • Reminder of the original use case: Preserving the analysis for later access and reuse. With researchers submitting content to CAP, it becomes an aggregator of analysis contents. Hence, use cases are extended for example to easier internal discoverability of analysis elements or better search functionalities. See user stories for more details.
  • This mini workshop aimed at getting everyone involved onto the same page on what has been happening, see the latest prototype, give feedback and decide on the next steps
  • The DASPOS project (presented by Mike Hildreth), consisting of a team of computer scientists, digital librarians and members of the scientists community, has been working very closely with CAP and RECAST recently. The focus has been on metadata aspects (i.e. Ontologies) and the reuse part (with Umbrella and RECAST). Another phase will focus on the integration of CAP into the research workflow, i.e. build connectors to it.
  • RECAST collaborates closely with CAP to build the “reuse” part of the CAP environment (see details below)
  • Work on CERN Analysis Preservation is organized in three pillars:
    • Describe: In order to understand the steps and results of analysis it is crucial to identify the main elements of the analysis. This varies by collaboration/working group so there is a challenge to handle standardisation vs. completeness
    • Capture: To later access and use the content it is needed to capture the content. Additional challenge arise due to large files, reused information, versioning. *Reuse: users accessing content on CAP should be able to instantiate it.

Describe Pillar