Fourth year (final) reporting

The fourth year of the project runs from 1 January to 31 December 2014.

Periodic report for fourth year

Each Work Package active in Year 4 must provide an individual report - please attach file with text, template here:

  • WP11 Common vision (STFC) - WP11_Periodic_Report_P4.docx
  • WP13 Coordination of common standards (ICT) - here
  • WP16 Common tools, software repository and marketplace (APA) - WP16_Periodic_Report_P4.docx
  • WP22 Identifiers and citability (FRD)
  • WP31 Digital rights and access management (DNB)
  • WP35 Data policies and governance (CSC) - WP35_Periodic_Report_P4.docx
  • WP41 External workshops, symposia and events (LTU)
  • WP42 Formal qualifications (FTK)
  • WP43 Training courses (DPC)
  • WP44 External communications and awareness raising (ONB)
  • WP45 Liaison with other stakeholders (STM)

Final report

All WPs (including WPs that finished earlier in the project) must provide a few key points on the main achievements of the WP over the whole life of the project, and particularly how it contributed to defragmentation. Please add to this table.

WP Leader Main achievements over life of project
WP11 Common vision STFC
  • An integrated view has been produced with allowed the project to bring together its results and those of many other research activities. The view places digital preservation within an overall business process in order to answer the question "who pays and why"

  • A blueprint for the VCoE has been created which, using the integrated view to provide coherence, allows many contributions to be brought to bear in order to create practical solutions to customers' digital preservation problems.

WP13 Coordination of common standards ICT

  • A Web-based database has been implemented for standards and projects with a database schema aligned/harmonized with an audiovisual register established by Presto4U

  • This database is available to the public thru the VCoE. It contains more than 170 standards and 70plus preservation-related projects

  • A sample GAP analysis has been performed for a typical life cycle of the design and engineering domain

WP14 Common testing environments Tessella (Not needed)
WP16 Common tools, software repository and market place APA

  • A collection of tools and supporting evidence has been created which can help users with a need to identify what tool/ technique/ service to try first

  • This is linked to the SCIDIP-ES Registry of Representation Information to improve preservation capabilities.

WP21 Preservation services STFC

  • An analysis of services useful for digital preservation - built on the fundamantally important concepts from the ISO standards 16363 and 14721.

WP22 Identifiers and citability FRD

WP23 Storage solutions ESA The activities of WP23 have been organized in two sub-work packages. The WP23_1 produced a summary about options available for storage, including in-house and use of external storage providers, and a preparation of a questionnaire (D23.1). The boundaries of the report's scope is limited to the investigation of the storage solutions adopted at a key set of WP23 partners' premises, including two representative use cases of research activities in the domain of digital preservation at storage level. The survey prepared has the overarching objective to broaden the community feedback on the topic 'relevance of storage solutions with respect to digital preservation of the data', and so to provide a deeper insight on the topic than what already acquired through WP23 partners. In a second step, the survey is meant to promote APARSEN results on such a topic, preparing the ground for future developments. The WP23_2 produced an integrated view of the options for storage solutions for preservation of digital resources, based on the experience of partners in APARSEN and a survey conducted on the subject (D23.2). Moreover, the project has also analysed the scalability problems that arise from the increase in number and size of preserved digital objects that many repositories are currently experiencing. A deeper analysis of the returned questionnaires pointed out that requirements collection, design phase and quality assessment process of the storage architectures, frequently show major gaps, sometime partially considered or in some situations even neglected. In particular, it is expected the design phase will address specific needs, first collected from involved user communities, and hence translated in system requirements. An example of architecture, filling most of the gaps identified and analysed within the document, is going to be provided in the framework of Copernicus EC program (
WP24 Authenticity and provenance CINI Providing proper management of authenticity and provenance along the digital preservation process is a central issue in ensuring trust. The main objective of WP24 has been to analyze the state of the art and to elaborate an unifying approach, with the aim to reduce fragmentation and to build an interoperable framework. A main result of the work package has been the proposal of a formal model for the digital resource lifecycle, that allows to identify the main events that impact on authenticity and provenance and to gather and preserve appropriate evidence to conveniently document the history of the digital resource. As part of the proposal, a set of operational guidelines have been derived to improve the current (and often very limited) practices, that especially address the interoperability issue, since the digital resources may go along their lifecycle through several changes of custody. To check the validity of the model and of the guidelines, a case study analysis has been performed to verify how the proposed approach specializes to specific environments. To this purpose, three different repositories have been selected among those managed by the project partners, their current practices have been analyzed according to the proposed methodology and necessary improvements have been devised. In a subsequent evolution, the APARSEN authenticity model has been the subject of a successful cooperation with the SCIDIP-ES project, that has led to a prototype implementation as part of the SCIDIP-ES authenticity toolkit. This activities are documented in deliverable D24.1, which reports on the state of the art, the model and the guidelines, and in D24.2 where the case studies are discussed. A second relevant contribution has consisted in developing mappings between provenance models to allow interoperability, notably OPM (Open Provenance Model) promoted by W3C and CRMdig as an extension of the CIDOC CRM ontology for capturing digital resources. Indeed, these two models act as very good hubs since a lot of mappings exists between them and other models. Moreover, a set of relevant reasoning rules has been proposed that can be exploited to reduce the amount of provenance information to be stored. Implementation policies of the inference rules and change operations have also been proposed over the various existing technologies (RDF triple stores, rule engines and query languages). This activity is documented in internal deliverable ID24.1. A further activity has concerned secure logging mechanisms, a specific aspect of the problem which has a significant impact on managing authenticity. More specifically, an overview has been given about current logging systems and their security and a survey of the existing methodologies has been provided. As for dissemination, the results of WP24 activities have been published in seven peer reviewded conference and journal papers, presented to several additional workshop and conferences, and have been the subject of numerous training activities.
WP25 Interoperability and intelligibility FORTH Please see the Y4 report of WP25 here
WP26 Annotation, reputation and data quality AFPUM
  • Data quality and via this reuse, preservation and reputation are critically dependent on appropriate annotation.
  • There are strong relations between annotation, reputation and data quality: For example, high quality should result in high reputation; high reputation should permit to assume high quality. In the context of preservation this suggests that the data must be annotated concerning quality and reputation, to facilitate appraisal (whether and what to preserve) and re-use (establish reliability).
  • APARSEN decided to use the term annotation as it refers a much broader set of explanatory information than mostly associated with the term metadata.
  • Annotation is not only a prerequisite for reuse its quality also directly influences who can reuse the data. Thus quality annotation of data is a major approach against the "silofication" of research data.
  • Reuse of data in contexts not originally envisaged is - especially in combination with text and data mining technology - perceived as a major source for new and accelerated knowledge production.
  • Establishing broad and deep context, detailed critique and amendment through annotation contributes further to establish trust in data, enables their review, being added to or being merged into larger scale datasets and finally, higher level data products being derived from them.
WP27 Scalability IBM
  • Parameters important to the scalability of preservation systems were identified.
  • Sources of information for scalability needs were located.
  • A survey questionnaire was prepared based on the scalability parameters identified. The questionnaire was merged with the questionnaire
  • storage services and distributed to organizations that preserve data.
  • Analysis of scalability in digital preservation systems was performed, based on the questionnaire results, other available questionnaires, data obtained on scalability needs from external sources, and data on current preservation solutions and research projects.

  • Gaps related to scalability were identified and recommendations were prepared.
  • A report was prepared summarizing all the data, analysis, and recommendations.
  • The recommendations report was integrated to the VcoE and will be used by the VCoE to direct activities towards covering identified gaps and requirements. The work on scalability is important to enable better supporting the rapid increase in the amount of data produced and its growing complexity.

WP31 Digital rights and access management DNB Dissemination Activities in 2014: Paper for IS&T Archiving Conference 2014; APARSEN Training Programm; APARSEN Webinar; Presentation at Satellite Event on 21st May 2014 in Vienna; APARSEN Access and Usibility Workshop at LIBER conference in Riga in July 2014; Access & usability training event in Florence in September 2014; Paper for iPres 2014 in Melbourne
WP32 Cost/benefit data collection and modelling BL

  • This work package evaluated and tested cost models for the preservation of digital objects, and provided findings through its two deliverables, D32.1 and D32.2.
    These deliverables presented: results of the analysis of cost parameters and identified areas for further investigation and development; tested cost models for digital repositories or archives and provided the costs of digital preservation services or workflows with recommendations on any future developments as well as advice on the creation of new models; relationship between costs and benefits. The outputs of this research were further developed under the Coordination Action, 4C (Collaboration to Clarify the Costs of Curation).

  • In terms of the VCoE, the results of this work package could be used to provide advice and guidance on the use of cost models. Training events related to cost models were undertaken and the material provided could be used as training material for interested parties in any future online courses.

WP33 Peer review and 3rd party certification of repositories AFPUM
  • This document reports on the work which has been undertaken in support of the European Framework for Audit and Certification of Digital Repositories which was initiated by the European Commission.
  • The European Framework provides three levels of evaluation for repositories, ranging from the DSA as an entry point which requires a few days' effort from the repositories to the much more detailed formal standards from DIN and ISO, which required between 1.5 to 3 person months to collect the evidence and take part in the audits.
  • The main part of this report provides details of the test audits which were carried out, the problems encountered and the lessons learned:
  • There is a need and a demand for a number of levels for accreditation, for both cost and effort reasons.
  • The three levels of assessment established in the European Framework provide a clear and balanced response to the needs of the community and the stakeholders.
  • All three levels of assessment are appropriate to be used by organisations involved in digital preservation whether in the public or the private sector or for SMEs as opposed to large knowledge institutions.
  • The test audits have shown strengths and weaknesses in the processes of conformity assessment, including in the construction of an explicit audit methodology.
WP35 Data policies and governance CSC
  • The work in this Work Package, and its deliverable, contributes to APARSEN common vision and VCoE by giving guidelines what should be taken into account when drafting or revising data policies and strengthens the interoperability with regard to data policies and governance.
  • Stakeholders, bodies and individuals to be contacted were identified. This was done in co-operation with Work Package 31.
  • A web-based questionnaire was implemented, which was open from in Fall, 2013. The invitation to participate was distributed via several mailing lists devoted to digital preservation or data management. In addition, flyers regarding these questionnaires were distributed in relevant conferences. A total of 27 respondents participated in the survey from ten countries.
  • The results of the survey was analysed together with a desktop research of selected policies available on the Internet. The desktop research, which was not a specific task mentioned in the DoW, complemented the online questionnaire.
  • The deliverable D35.1 (Exemplar good governance structures and data policies) gives guidelines on governance and data policy management mechanisms to enhance interoperability based on online questionnaire and the desktop research. The deliverable concludes with 13 selected recommendations that should be taken into account when drawing up data policies concerning digital preservation.
  • The work and results in this Work Package have been presented in several events:
    - A poster was presented in Open Repositories conference in Helsinki, June 913, 2014.
    - Two different workshop presentations were given in LIBER 43rd Annual Conference in Riga July 25, 2014 and in DPC's and 4C's Investing in Opportunity conference in London, November 1718, 2014.
    - Training sessions (including presentation and work group exercises) in two different APARSEN training events were given: Advanced Practitioner Training in Vienna, July 711, 2014 and Training on Access and Usability in Florence, September 1718, 2014.
WP36 Business cases UPAT

WP41 External workshops, symposia and events LTU Please see the Y4 periodic report of WP41 here
WP42 Formal qualifications FTK Resources about existing initiatives and curricula have been collected through desk-based research and documented in the APARSEN wiki. As the initial focus was set upon European resources, admissible candidates have been identified for further analysis by the WP42 partners. The extended survey analysis collected and documented 77 eligible offerings (18 curricula, 40 academic courses and 19 continuing professional education courses) systematically and further investigated the findings. The survey results are available in the Deliverable D42.1 and the affiliated Annex published on the APARSEN website. A dialogue with relevant stakeholders and communities from the supply side and the demand side was established to contribute their feedback for the reflection of the APARSEN Curriculum framework and to the learning offers collected in the APARSEN Online Training Portal. A curriculum for a generic APARSEN Digital Preservation curriculum (120 ECTS) was developed as a blueprint for a Digital Preservation curriculum in Higher Education. The APARSEN Curriculum has been defined and reflects the APARSEN Common vision. In collaboration with WP43, the APARSEN Online Training Portal (OTP) has been set-up and customized to the needs of APARSEN and the prospective VCOE. The Deliverable D42.2 "Report on definition of curricula and course contents, summary of liaison actions and co-operations" was finished.
WP43 Training courses DPC

  • Six training courses reaching more than 200 participants and covering all 4 APARSEN topic areas and the Common Vision.

  • Training courses included co-operation with SCAPE, TIMBUS, EUDAT, DigCurV and the IMPACT Centre, creating cohesive curricula across projects.

  • Developed the Online Training Portal, providing a variety of 'mini-courses' on Digital Preservation as well as a single point of access to training material from previous EC funded projects.
WP44 External communications and awareness raising ONB

WP45 Liaison with other stakeholders STM

  • A series of 12 webinars were held during the project on Deliverables of the project as and when they came available. The webinars drew on average around 30 to 35 participants (with peaks up to 60 people for very popular topics) and always had guest speakers of related projects and initiatives in Digital Preservation, next to APARSEN-partners presenting project work. The webinars were a powerful and meaninfgul way for discussing the work within APARSEN at early stages with stakeholders outside the project. In most webinars, around half of the audience consisted of non-project partners.

  • Topics discussed in the webinars were always in the core of the defragmentation aim of APARSEN; from persistent identifiers, to storage solutions, to scalability, training courses, developing a common vision, cost models, business models, certification of repositories and digital rights management and of course the shaping of the Virtual centre of Excellence. The spectrum of speakers helped provide a good overview of the state of the art, of parallel initiatives going on and gaps that need attention, while the APARSEN deliverables aimed at offering more holistic solutions that are compatible and interoperable with ongoing work.
    A full overview of all webinars plus summary reports and recordings can be found at

-- SimonLambert - 2014-11-05

Topic attachments
I Attachment History Action Size Date Who Comment
Microsoft Word filedocx 2014_WP45_Periodic_Report_P4.docx r2 r1 manage 20.0 K 2014-12-17 - 15:15 EefkeSmit This is the CORRECT Yr4 report for WP45 (please ignore the P3 version)
Microsoft Word filedocx APARSEN_WP13_Periodic_Report_Year_4.docx r1 manage 18.8 K 2015-02-10 - 23:19 AndreasHundsdoerferI WP13 report
Microsoft Word filedocx WP11_Periodic_Report_P4.docx r1 manage 17.0 K 2014-12-18 - 08:42 DavidGiaretta WP11 report
Microsoft Word filedocx WP16_Periodic_Report_P4.docx r1 manage 16.0 K 2014-12-18 - 08:57 DavidGiaretta WP16 report
Microsoft Word filedocx WP31_Periodic_Report_P4.docx r1 manage 18.8 K 2014-12-11 - 10:51 KatarinaHaage WP 31 DRM Periodic Report Y4
Microsoft Word filedocx WP35_Periodic_Report_P4.docx r1 manage 15.7 K 2014-12-18 - 18:13 HeikkiHelin  
Microsoft Word filedocx WP41_Periodic_Report_Year4.docx r1 manage 16.2 K 2014-12-05 - 12:47 DaryaPlankina Y4 periodic report
Microsoft Word filedocx WP42_Periodic_Report_2014.docx r1 manage 26.6 K 2014-12-18 - 10:53 BeateDeska WP42 Periodic Report 2014
Microsoft Word filedocx WP43_Periodic_Report_P4.docx r1 manage 19.2 K 2014-12-19 - 10:14 SharonMcMeekin WP43 - Year 4 Review Report
Microsoft Word filedocx WP_Periodic_Report_P4.docx r1 manage 15.2 K 2014-11-05 - 14:23 SimonLambert Template for WP reports for the fourth year periodic report
Edit | Attach | Watch | Print version | History: r28 < r27 < r26 < r25 < r24 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r28 - 2015-02-10 - AndreasHundsdoerferI
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback