Work Packages - WP4: Renewed Daguerreobase and service delivery

Article Index

WP4: Renewed Daguerreobase and service delivery

Objectives

WP 4 will include all tasks related to the renewal of the existing Daguerreobase to:

  • Provide a suitable infrastructure for a metadata aggregator for historical and contemporary daguerreotypes that:
    • Is complementary and interoperates with Europeana
    • Will enable access to a critical amount of descriptions of significant cultural heritage
    • Will enhance the quality of new and existing content for Europeana
    • Will enable improved search ability and retrieve ability
    • Will improve semantic interoperability, multilingual and cross-language searching
    • Will improve services

Input from all partners is required on the structure and functionality of the Daguerreobase platform.

Description of work

This work will be executed by the technical partner in accordance with the outcomes of the WP 3 tasks on standards and multilingual sets of thesauri/entries lists and the Community requirements and comments in order to the proposed structure and functionality. In the above chapter B3.2.a. Chosen approach, Improvement of the database structure and service delivery (WP4), the requirements and functionalities as proposed by PIM are described in detail. PIM will present a roadmap with a brief description of the development activities in order to the project progress at the first BP Workshop / meeting and to the PBM (Month 3, second PBM meeting). All partners can/will give feedback to PIM. With this comments and information, PIM can start to develop a first concept of the new Daguerreobase.

This concept will be presented at the second BP Workshop to all partners (Month 6, third PBM meeting). Again, all partners can/will give feedback and remarks. PIM will receive the draft versions of all standards and thesauri/entries lists at the same meeting. Together with the remarks of all partners, PIM can proceed with the further development of the Daguerreobase.

The first release (Month 8) will be tested by eDAVID, resulting in a first acceptance report. (Month 9)

The second release (Month 10) will be tested by eDAVID, resulting in a second acceptance report. (Month 11) The final version will be presented at the third PBM (Month 12).

The multilingual manual and guidelines will be ready at month 11 to integrate in the renewed Daguerreobase. Content providers can start editing starting month 13. eDAVID will continue with a long term evaluation of the web services, resulting in a Web services and functionality report. (Month 18)

eDAVID will be involved in the improvement of the database structure and the development of services. The database structure must provide the necessary elements to guarantee sustainability overtime. Together with a good documentation of the data model and the information architecture, these elements are important building blocks for the development of a preservation strategy for the database. The information model of the OAIS-standard will function as framework. eDAVID will also contribute in the acceptance testing of the improved database and the web services.

Deliverables

  • D4.1 Road map (Month 3).
  • D4.2 Renewed Daguerreobase portal, first concept (Month 6), release 1 (Month 8), release 2 (Month 10), final version (Month 12)
  • D4.3 Reports of the acceptance testing of Daguerreobase (Month 9 and Month 11)
  • D4.4 Multilingual online user manuals and guidelines (Month 10)
  • D4.5 Web services and functionality report (Month 18)