WP21 kick-off meeting, 25th May 2012


  • Barbara Bazzanella
  • David Giaretta
  • Stefan Hein
  • Ash Hunter
  • Gerald Jaeschke
  • Kirnn Kaur
  • Kimmo Koivunen
  • Simon Lambert
  • Juha Lehtonen
  • Maurizio Lunghi
  • Rudolf Mayer
  • Silvio Salza
  • Arif Shaoen (STFC)
  • Yannis Tzitzikas
  • Rene van Horik

Review of Description of Work

Simon summarised the WP as defined in the DoW. There is a single deliverable D21.1 "Design of preservation services" due at Month 24. The WP is divided into three tasks, starting with collection of preservation services, then comparison of them to understand their scope and limitations, and finally mapping out the services in a systematic way.

The PARSE.Insight roadmap, survey and list of threats to preservation are fundamental as a basis for scoping which services are needed.

Assigned to Due date Description State Closed Notify  
SimonLambert 2013-05-10 WP21 : Simon to put links to PARSE.Insight documents on the wiki. 2013-06-03 SimonLambert   edit

David pointed out the relationship with WP14 for testing purposes. Ash Hunter mentioned that Tessella is laucnhing "preservation as a service" and this could be a test system for APARSEN.

Barbara Bazzanella noted that it would be nice to create a connection with the persistent identifier interoperability service from WP22.

Report on SCIDIP meeting

A SCIDIP project meeting took place earlier in the week, and David gave a report. SCIDIP was planned after APARSEN so is not mentioned in the APARSEN DoW; nonetheless it is very relevant to the APARSEN services. SCIDIP could offer a number of services, originating from the CASPAR project, such as a registry repository of representation information. This will give APARSEN the freedom to look at other services not being produced in SCIDIP. Such services could sit on top of the SCIDIP services so giving an opportunity to implement them fairly easily.

René van Horik observed that SCIDIP is focussed on earth science, whereas APARSEN is more generic. David replied that the services are generic. We could also think about domain-specific toolkits.

Scope of services

Ash Hunter urged that the work should contribute to the VCoE.

Ash also noted that the DoW is very broad. Should we consider services such as PRONOM and UDFR? David thinks that everything has its place so we should collect together and see where it all fits together. We could also think of an advisory service as part of the VCoE.

Maurizio was worried that our definition of services might be too general to be useful. David emphasixed that services should be those that can be shared - highly specific services such as ingest probably can't be shared.

First steps (Task 2110)

The first step will be to assemble a collection of different servicess that we all know about as a basis for classification and discussion. This will also help to identify what is missing. Yannis suggested using a template for describing services. It could have fields such as name, website, scope, specific domain, ....

The other Stream 2 WPs will certainly offer services. Maurizio suggested that WP21 could act as an aggregator for services. In any case we must make clear what is unique in this WP and what is picked up from elsewhere. David expects that the common vision WP11 could take up the results of this WP.

Assigned to Due date Description State Closed Notify  
SimonLambert, DavidGiaretta 2013-05-10 WP21 : Simon/David to produce simple template for describing services. 2013-06-03 SimonLambert   edit

Assigned to Due date Description State Closed Notify  
TWikiUsers 2013-05-20 WP21 : All partners to fill in the template for the services of which they are aware. 2013-06-03 SimonLambert   edit

The aim is to have a good collection of services for discussion at the all hands meeting/workshop in June.

-- SimonLambert - 2012-05-27

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2013-06-03 - SimonLambert
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback