proposal part b - The Bernstein Project
proposal part b - The Bernstein Project
proposal part b - The Bernstein Project
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
CIP-ICT PSP Call 4 39<br />
Pilot B<br />
[Imperialle]<br />
Work package number : 2<br />
Start date or starting<br />
event:<br />
Work package title: Database design and metadata specification<br />
Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 13<br />
Participant short name OEAW BAM TUG IVCR SMK ICPAL WRM BL HERTZ UTBV BAL ISM ACV<br />
Person-months per <strong>part</strong>icipant: 10.0 0.0 25.0 6.0 5.5 9.0 12.0 9.0 6.5 12.0 6.0 8.0 4.5<br />
Objectives (ii)<br />
O2.1 – Analyze all the available data resources (digitized masterpieces) of <strong>part</strong>ner institutions and provide a<br />
metadata specification for these objects to make it possible to integrate them into the <strong>Bernstein</strong> portal and to<br />
allow their import into Europeana.<br />
O2.2 – Provide a Database Specification that allows flexible storage and efficient retrieval of the<br />
(referenced) digitized masterpieces along with their metadata.<br />
O2.3 – Implementation of a Database to store the (references to) digitized masterpieces and their metadata<br />
and to provide search and retrieval mechanisms to support <strong>Bernstein</strong> portal services and to allow the import<br />
into Europeana.<br />
Description of work (iii)<br />
T2.1: Data resources analysis (OEAW, ICPAL)<br />
- Analyze all the data resources the Imperialle <strong>part</strong>ner can provide (European masterpieces of art,<br />
music, literature, architecture, and science that were made or planned on paper)<br />
o What kind of “masterpieces” are to be integrated?<br />
o If information on these masterpieces is already electronically (in digitized form) available,<br />
how is it stored and how can it be accessed and retrieved?<br />
o What kind of metadata on these masterpieces is available and what kind of metadata should<br />
be added<br />
- Analyze all the data resources the Imperialle <strong>part</strong>ner can provide (including possible metadata)<br />
with respect to:<br />
o Usage in a shared and joined portal (issues: usability, accessibility …)<br />
o Applicability regarding additional services provided by the Imperialle portal<br />
o Qualification regarding import of metadata into Europeana<br />
T2.2: Metadata specification (HERTZ, SMK)<br />
- Harmonization of all the metadata upon all the different and diverse kind of masterpieces that are to<br />
be integrated<br />
- Specification of a unified common metadata schema for Imperialle<br />
T2.3: Database design (TUG, SMK)<br />
- Design of the Imperialle database which contains the aggregated data of all databases of the<br />
<strong>part</strong>ners<br />
T2.4: Database implementation (TUG, OEAW)<br />
- Implementation of the Imperialle database:<br />
o Implementation of the database schema (create tables, views, indices …)<br />
o Specification of a persistence layer API that can be used by portal services and gateways to<br />
store, access, retrieve metadata of digitized masterpieces<br />
o Implementation of the persistence layer API<br />
m4