D6.1 EURO-Photo Interoperability Framework Prototype...
Transcript of D6.1 EURO-Photo Interoperability Framework Prototype...
D6.1 Interoperability Framework Prototype report
ICT Policy Support Program
Grant Agreement ICT-PSP-250468
Disclosing the European Library on common visual historical heritage
D6.1 EURO-Photo Interoperability Framework Prototype report
Deliverable Form
Project Reference No. Grant Agreement ICT-PSP-250468 – EURO-Photo Project
Deliverable No. D6.1 EURO-Photo Interoperability Framework Prototype report
Relevant Workpackage: WP6 – Interoperability implementation and testing
Nature: Report
Dissemination Level: CO
Document version: V 0.1
Date: 15-10-2011
Authors:
Contributors:
Expert System S.p.A
All Parteners
Document description: This document summarize the actual implementation of EURO-
Photo portal prototype (www.europhoto.eu.com), report
testing, validation activities and their results
D6.1 Interoperability Framework Prototype report
2
Executive Summary
This document summarize the actual implementation of EURO-Photo portal prototype
(www.europhoto.eu.com) and report testing and validation activities and their results.
It’s composed by 4 chapter.
Chapter 1 : EURO-Photo Architecture EURO-Photo provide a simplified graphical
representation of the flow of data through EURO-Photo web application outlining used web
application technologies based on a combination of Server-side and Client-side programming.
Moreover search funtionalities implemented by Expert System's COGITO Search Explore
Engine (as web service API’s) are outlined.
Chapter 2 : EURO-Photo portal description briefly describes the feeding mechanism of
photos from News Agencies and the upload functionalities for Europeana. Morover a short
description of the actual implementation of EURO-Photo portal is provided, incorporating the
results of validation and testing activities as described in the next 2 chapter.
Chapter 3 : 3 EURO-Photo WORKGROUP Evaluation and Testing presents the
activities of a workgroup composed by a subset of EURO-Photo participating agencies
namely: MTI (team leader) , ANSA, EFE, EPA and report the reccomandation and suggestion
arised during their activities.
Chapter 4 : EUROPHOTO PORTAL QUESTIONNAIRE present the on line consortium
wide questionnaire and its outcome.
.
D6.1 Interoperability Framework Prototype report
3
REVISION HISTORY AND STATEMENT OF ORIGINALITY
Revision History
RevisionDate Author Organisation Description
1 October
2011
Expert System Report
Statement of originality:
This deliverable contains original unpublished work except where clearly indicated otherwise. Acknowledgement of previously published material and of the work of others has been made through appropriate citation, quotation or both.
D6.1 Interoperability Framework Prototype report
4
Table of Contents
REVISION HISTORY AND STATEMENT OF ORIGINALITY .................... 3
INTRODUCTION ........................................................................................................ 6
1 EURO-PHOTO ARCHITECTURE ........................................................................... 7
1.1 EURO-Photo Web Application Technology ................................. 7
1.2 Application Scheme .................................................................... 8
1.3 Search functionality ................................................................... 9
2 EURO-PHOTO PORTAL DESCRIPTION .............................................................. 10
2.1 Feeding EURO-Photo with data. ............................................... 10
2.1.1 The EURO-Photo Item .................................................................................. 10
2.1.2 Insert, update and delete of an item in EURO-Photo. ..................................... 17
2.1.3 Standard Feeding Mode ................................................................................ 19
2.1.4 Web server Feeding Mode ............................................................................ 21
2.1.5 The Metadata Semantic Auto-Completion Feature. ......................................... 23
2.1.6 The Europeana Metadata item. ..................................................................... 25
2.2 The EURO-Photo Portal features and graphic interface ........... 27
2.2.1 Portal accessibility ........................................................................................ 27
2.2.2 The main EURO-Photo page. ........................................................................ 28
2.2.3 The Photo Visualization Page ....................................................................... 31
2.2.4 Europhoto Galleries ...................................................................................... 33
2.2.5 User Registration Procedure ......................................................................... 36
2.2.6 Europhoto Market Place ................................................................................ 39
2.2.7 Transfering Photos to Europeana .................................................................. 40
3 EURO-PHOTO WORKGROUP EVALUATION AND TESTING ............................... 42
3.1 Issues Examined ...................................................................... 42
3.2 Beta portal test report ............................................................. 44
3.2.1 Frontpage .................................................................................................... 44
3.2.2 Single Picture view ....................................................................................... 45
3.2.3 Performing a search ..................................................................................... 49
3.2.4 Advanced search .......................................................................................... 51
3.2.5 Other issues to remark ................................................................................. 56
CONSORTIUM ASSESMENT QUESTIONAIRE .......................................................... 59
3.3 EUROPHOTO PORTAL QUESTIONNAIRE ................................... 60
3.3.1 Frontpage .................................................................................................... 60
3.3.2 Thunbnail Grid ............................................................................................. 64
3.3.3 List view ...................................................................................................... 65
3.3.4 Single Picture view ....................................................................................... 66
D6.1 Interoperability Framework Prototype report
5
3.4 Questionaire Outcome ............................................................. 69
3.4.1 Front-page general....................................................................................... 69
3.4.2 Galleries ...................................................................................................... 70
3.4.3 Other Information ........................................................................................ 72
3.4.4 Tumbnail Grid .............................................................................................. 74
3.4.5 List view ...................................................................................................... 76
3.4.6 Single picture (Independent) ........................................................................ 78
3.4.7 Single picture (National) ............................................................................... 80
3.4.8 Single picture (English) ................................................................................. 82
3.4.9 Search ......................................................................................................... 84
3.4.10 Registration .............................................................................................. 86
3.4.11 Enquire Form ............................................................................................ 88
CONCLUSION .......................................................................................................... 89
D6.1 Interoperability Framework Prototype report
6
INTRODUCTION
EURO-Photo is based on Open Source technology for the front end and make use of Expert
System's COGITO Search Explore Engine for the back office.
It implements functionalities for the aggregation, dissemination, and commercial activities
support for historical pictures provided by the news agencies of the EURO-Photo consortium.
The portal will:
1) Automatically upload photos and metadata coming from the News Agencies, from
dedicated FTP folders or implementing as an alternative the Open Archives Initiative
Protocol for Metadata Harvesting;
2) Aggregate the data to be accessible in Europeana, automatically feeding the
Europeana system with a converted set of metadata of the EURO-Photo archive, using
the above mentioned mechanism;
3) Implement a graphical interface for browsing and visualizing mid resolution versions
of the images in the archives. An adequate watermark, referring EURO-Photo will be
applied to the preview jpg
4) Implement a graphical interface to show photo metadata;
5) Realize a multilingual search engine for the filtering and retrieval of images;
6) Provide a prototypical commercial platform of photo trading from News Agencies to
Professional users.
.
D6.1 Interoperability Framework Prototype report
7
1 EURO-Photo Architecture
1.1 EURO-Photo Web Application Technology
EURO-Photo is based on combination of Server-side and Client-side programming.
On the server run a Web Server, an interpreter and Semantic search Engine. So user's
request is fulfilled by running a script directly on the web server to generate dynamic web
page.
When a user requests a page to EURO-Photo Website the interpreter responds by sending an
HTML, javascript and css files.
Figure 1-1 : A typical Server-side Client-side logic
A large part of exchanged data between client and server are based on AJAX (Asynchronous
JavaScript and XML) technologies. They allows to make the client side page communicate
with the server without the need of a different page or a refresh. So when a user is on a
EURO-Photo website page some data are exchanged with the server in background and only
the needed parts of the page are refreshed.
D6.1 Interoperability Framework Prototype report
8
1.2 Application Scheme
The following scheme is a simple graphical representation of the flow of data through EURO-
Photo web application.
D6.1 Interoperability Framework Prototype report
9
Figure 1-2 : A simple graphical representation of the flow of data through EURO-
Photo
1.3 Search functionality
Search funtionalities are based on the photo’s metadata. For example, users can search by a
category, subcategory, agency, place, publishing date, etc. The search system is not only a
based on keyword technology but also on semantic intelligence provided by COGITO
technology
EURO-Photo portal infact incorporates Expert System's COGITO Search Explore Engine to
implement semantic search. Cogito Search Explore Engine is commercial product
intended to supports analysts and knowledge workers in the activities of monitoring, search
and automatic correlation of information. At the end of each search, Cogito Search Explore
Engine also provides simple content lists: from the categories/topics discussed in documents
to the list of companies, products and people cited in the text; from the list of geographic
locations to a list of keywords, headwords and concepts; SAO relations, etc.
EURO-Photo uses Expert System's COGITO Search Explore Engine as web service API’s
as listed below :
● Authentication
● Settings refresh
● Supported languages
● Managed metadata / extradata features
● Semantic Net access
● Operator list to build search boolean queries
● Corpora list to be searched
● Weighted search
● Boolean search
● Basic search
● Keyword-based search
● Analysis
● Correlation
● Indexed document retrieval
D6.1 Interoperability Framework Prototype report
10
2 EURO-Photo portal description
2.1 Feeding EURO-Photo with data.
EURO-Photo implements the uploading of images and related metadata from each News A
gency. Some News Agency decided to provide photos and related metadata in a different
physical format semantically compatible with EURO-Photo requirements and agreed with
Expert System. In this case Expert System takes care of mapping the News Agency
proprietary format to the EURO-Photo format.
2.1.1 The EURO-Photo Item
A photo to be inserted in EURO-Photo repository is represented by means of a pair of files
with the same name but with different extention:
• .jpg file
• .xml file
It must be univocally identified by a digital Image GUID, which is a value of less then 32
bytes starting with 3 alphanumeric values which identifies the agency, followed by up to 29
bytes of ASCII values. By example, an ANSA GUID could be :
“ANS-1e3THh56U78Nf2u4”.
The two requested file are a jpg format image file and an xml format metadata file; both
those files must be named with digital Image GUID.
For previous example :
• ANS-1e3THh56U78Nf2u4.jpg
• ANS-1e3THh56U78Nf2u4.xml.
The jpg file must contain a not watermarked mid resolution version of the original image
with the resolution ranging from 400x600 to 1240x780. The colordepth of the image can be
D6.1 Interoperability Framework Prototype report
11
8 bits per pixel (grey tone image) or 24 bits per pixel (fullcolor). If the jpg image is provided
with metadata tags, they will be ignored.
The xml file must be compliant with the OAI-PMH protocol, and contain bi-lingual IPTC
metadata. These metadata are represented using 4 metadata formats: Dublin core (DB),
Photoshop, IPTC core (Iptc4xmpCore) and IPTC extended (Iptc4xmpExt).
Here’s a list of those metadata, with its identifier in the xml file, its IPTC field code, the
language, and its description.
For those metadata that are bi-lingual, two instances for them must be provided in the xml
file: the native language one, and the English one.
D6.1 Interoperability Framework Prototype report
12
Metadata Format Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
Iptc4xmpExt DigImageGUID Digital Image GUID N.A. 32 NO
A unique identifier for the photo; its made of up to 32 bytes, where the first 3 bytes stores a unique identifier
for photo owner News Agency.
Metadata Format Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
Iptc4xmpCore SubjectCode Subject Code 2:012 8 NO
An 8 bytes numeric code identifying the subject and the matter of the image. In appendix A the full list of codes
and their meaning is reported.
Metadata Format Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
DB subject Keyword 2:025 64 YES
A set of keywords related to the photo contents.
Metadata Format Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
Photoshop Instructions Instructions 2:040 256 NO
Special instruction or comments (photo defects, reliability, etc.)
Metadata Format Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
photoshop DateCreated Date Created 2:055 8 NO
The date the images were taken.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
DC creator By-line (Author) 2:080 32 NO
The author of the image.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
photoshop AuthorsPosition By-line Title(Author
position)
2:085 32 NO
The job title of the creator of the Item.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
D6.1 Interoperability Framework Prototype report
13
photoshop City City 2:090 32 NO
The city where the image was taken.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
photoshop State Province/State 2:095 32 NO
The State (US) or the Province where the image was taken.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
Iptc4xmpCore CountryCode Country code 2:100 3 NO
The three-digit representing the Country code where the image was taken.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
photoshop Country Country/Primary Location
Name
2:101 64 NO
The full Country name where the image was taken.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
photoshop Headline Headline 2:105 256 YES
A brief synopsis of the caption/description.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
photoshop Source Source 2:115 32 NO
The original owner of the copyright for the intellectual content of the item. This could be an agency, a member
of an agency or an individual.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
DC rights Copyright Notice 2:116 128 NO
Any necessary copyright notice for claiming the intellectual property for this item. It identifies the current owner
of the copyright for the item.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
DC description Caption/Abstract 2:120 2000 YES
A full description of the contents in the image
D6.1 Interoperability Framework Prototype report
14
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
Iptc4xmpExt PersonInImage N.A. N.A. 256 NO
The names or/and description of people in the image.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
Iptc4xmpExt LocationShown N.A. N.A. 256 NO
The names or/and description of the location where the image was taken
Metadata Standard Identifier IPTC Label IPTC
FIELD
Size in
Bytes
Bi-
lingual
Iptc4xmpExt OrganisationInImageNam
e
N.A. N.A. 256 NO
Name of the organisation or company that is featured in the image.
Metadata Standard Identifier IPTC Label IPTC FIELD Size in Bytes Bi-lingual
DC language N.A. N.A. 3 YES
Specify the language used for the metadata of the section
D6.1 Interoperability Framework Prototype report
15
Here is an example of a xml file properly formatted for the EURO-Photo feeding:
<?xml version="1.0" encoding="UTF-8"?>
<EURO-Photo_record>
<header>
<identifier>ANSa33R45TGthu6Hy9L</identifier>
<datestamp>2011-01-28</datestamp>
<setSpec>EURO-Photo</setSpec>
<setSpec>europeana</setSpec>
</header>
<record
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
xmlns:Iptc4xmpExt="http://iptc.org/std/Iptc4xmpExt/2008-02-29/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<language_independent_metadata>
<Iptc4xmpExt:DigImageGUID>ANSa33R45TGthu6Hy9L</Iptc4xmpExt:DigImageGUID>
<Iptc4xmpCore:SubjectCode>
<rdf:bag>
<rdf:li>15000000</rdf:li>
<rdf:li>10006000</rdf:li>
<rdf:li>01001000</rdf:li>
</rdf:bag>
</Iptc4xmpCore:SubjectCode>
<photoshop:DateCreated>2010-09-09</photoshop:DateCreated>
<dc:creator>Claudio Peri</dc:creator>
<Iptc4xmpCore:CountryCode>ITA</Iptc4xmpCore:CountryCode>
<photoshop:Source>ANSA</photoshop:Source>
</language_independent_metadata>
<native_language_metadata>
<dc:language>ITA</dc:language>
<photoshop:headline>ROMA '60: COLOSSEO ILLUMINATO PER 3 NOTTI.
IMMAGINI DEI 13 OLIMPIONICI ITALIANI E DELLA CAPITALE 50 ANNI FA</photoshop:headline>
<dc:description>
Immagini della Roma del 1960, alternate a foto dei 13 atleti italian che quell'anno vinsero l'oro olimpico e intervallate da gigantografie delle statue dello Stadio dei Marmi: sono gli ingredienti della installazione luminosa che da stasera e fino a sabato, dalle 21 alle 4 di notte, illuminera' il Colosseo, in occasione del 50o anniversario dei Giochi olimpici che si svolsero nella capitale nel 1960.
</dc:description>
<dc:subject>
<rdf:bag>
<rdf:li>colosseo</rdf:li>
<rdf:li>medaglie</rdf:li>
<rdf:li>olimpiadi</rdf:li>
</rdf:bag>
</dc:subject>
<photoshop:City>Roma</photoshop:City>
<photoshop:State>Lazio</photoshop:State>
<Iptc4xmpExt:LocationShown>
<rdf:bag>
<rdf:li >colosseo</rdf:li>
<rdf:li >via dei fori imperiali</rdf:li>
D6.1 Interoperability Framework Prototype report
16
<Iptc4xmpExt:PersonInImage>
<rdf:bag>
<rdf:li >atleti olimpici</rdf:li>
</rdf:bag>
</Iptc4xmpExt:PersonInImage>
<Iptc4xmpExt:OrganisationInImageName>
<rdf:bag>
<rdf:li >Comitato Olimpico</rdf:li>
</rdf:bag>
</Iptc4xmpExt:OrganisationInImageName>
<photoshop:Instructions>controllare qualita' della foto</photoshop:Instructions>
<photoshop:AuthorsPosition>Z85</photoshop:AuthorsPosition>
<dc:rights>ANSA: diritti riservati</dc:rights>
</native_language_metadata>
<english_language_metadata>
<dc:language>ENG</dc:language>
<photoshop:headline>ROME '60: ENLIGHTENED COLOSSEUM FOR 3 NIGHTS</photoshop:headline>
<dc:description>
Images of Rome in 1960, alternating with photos of the 13 Italian athletes that year they won the Olympic gold and interspersed with giant statues of the Stadium Marbles are the ingredients of the lighting installation that until tonight and Saturday, from 21 4 am, lights up the Colosseum on the 50th / anniversary of the Olympic Games that took place in the capital in 1960.
</dc:description>
<dc:subject>
<rdf:bag>
<rdf:li>colosseum</rdf:li>
<rdf:li>medals</rdf:li>
<rdf:li>olympic games</rdf:li>
</rdf:bag>
</dc:subject>
<photoshop:City>Rome</photoshop:City>
<photoshop:State>Lazio</photoshop:State>
<Iptc4xmpExt:LocationShown>
<rdf:bag>
<rdf:li >colosseum</rdf:li>
</rdf:bag>
</Iptc4xmpExt:LocationShown>
<Iptc4xmpExt:PersonInImage>
<rdf:bag>
<rdf:li >olympic athletes</rdf:li>
</rdf:bag>
</Iptc4xmpExt:PersonInImage>
<Iptc4xmpExt:OrganisationInImageName>
<rdf:bag>
<rdf:li > Olympic organization</rdf:li>
</rdf:bag>
</Iptc4xmpExt:OrganisationInImageName>
<photoshop:Instructions>check photo quality</photoshop:Instructions>
<photoshop:AuthorsPosition>Z85</photoshop:AuthorsPosition>
<dc:rights>ANSA: all rights reserved</dc:rights>
</english_language_metadata>
</record>
</EURO-Photo_record>
D6.1 Interoperability Framework Prototype report
17
The xml file must have a header file, with the following fields:
• Identifier: mandatory field. It stores the digital GUID for the item to be added.
• Datestamp: mandatory Field. It stores the date of item inserting request.
• SetSpec: Optional Field. Specify on which platform the item has to be uploaded.
Since the insertion in EURO-Photo is mandatory, the field: <setSpec>EURO-
Photo</setSpec> can be omitted from the Header.
To upload the item in the Europeana platform as well, the field
<setSpec>europeana</setSpec> should be included in the header.
Another optional value can be put in the header for item deletion, as we will see later.
Following the header, the main metadata section will appear. The section is organized in 3
different sections: Language independent metadata, native language metadata, and English
metadata.. As shown before, some metadata are mandatory: an error will occur if some of
the mandatory metadata are missing in the xml file.
2.1.2 Insert, update and delete of an item in EURO-Photo.
To insert a new item the couple of files (xml and jpg) must be put in the harvesting
repository.
To update an already present item, there are two situations:
1) Metadata only update: a single xml file with all metadata must be put in the
repository; an item with same digital GUID must be already present in the EURO-
Photo db. EURO-Photo will update all metadata of the item in the archive.
2) Image only update: a single jpg file, named with GUID to be updated must be put in
the repository. EURO-Photo will substitute the image in the archive with the new one.
3) Metadata and image update: both files, xml and jpg, must be put in the repository.
To delete an existing item, a special version of the xml file should be put in the repository.
D6.1 Interoperability Framework Prototype report
18
It must have only the header part, and the attribute status should be added and set to
“deleted”.
Here is an example, where the setSpec field specify where the deletion should be executed.
<?xml version="1.0" encoding="UTF-8"?>
<EURO-Photo_record>
<header status="deleted" >
<identifier>ANS-a33R45TGthu6Hy9L</identifier>
<datestamp>2011-01-28</datestamp>
<setSpec>EURO-Photo</setSpec>
<setSpec>europeana</setSpec>
</header>
<EURO-Photo_record>
D6.1 Interoperability Framework Prototype report
19
2.1.3 Standard Feeding Mode
The First modality for feeding items in EURO-Photo is simpler to and it’s essentially a batch
style method.
Each Agency involved in the project, produce ( or ask Expert System to create for them
starting from their proprietary format) the needed couple of files for each image to be
uploaded, and copy them (via FTP or other means) in the chosen harvest repository. The
harvest repository is set-up by the EURO-Photo portal administrator.
EURO-Photo will harvest the items using the EURO-Photo OAI-PMH protocol, realizing a
module which manages the repository.
EURO-Photo communicates with the harvesting module using the standard harvesting syntax
OAI-PMH; the requests are specified using a subset of the 6 OAI-PMH verbs.
The typical handshake used for a harvesting session between the EURO-Photo portal and the
harvesting module may be:
1. EURO-Photo starts a Harvesting session. Those sessions are scheduled at certain
time intervals, specified in the harvest granularity value.
2. EURO-Photo requests to the harvesting tool the list of the items that the client
stored in the repository after a certain date and time. The verb to be used for this
request is ‘ListIdentifiers’.
3. The harvest tool responds to the request with an xml file containing the GUID list
of the items to be harvested.
4. For each item of the list, EURO-Photo sends a request for its metadata to the
module, using the verb ‘getRecord’;
5. The Module responds with the metadata xml file of the requested item. At this
time, EURO-Photo can also upload the photo file that is supposed to be stored in
the same repository.
The same handshake is valid also for the deletion of existing items in the EURO-Photo
archive.
D6.1 Interoperability Framework Prototype report
20
If an Agency client wants to delete an existing item from the EURO-Photo archive, the
xml file will have the ‘status=deleted’ set in the xml header file. Of course, in this case no
metadata values have to be included.
D6.1 Interoperability Framework Prototype report
21
2.1.4 Web server Feeding Mode
To implement the Web server mode, an OAI-PMH compliant client that manages an agency
local EURO-Photo repository will be realized.
The OAI-PMH protocol allows feeding of the EURO-Photo archive by means of HTTP requests
to the News Agency Client application. EURO-Photo will be implemented as a standard Web
server that is configured to dispatch OAI-PMH requests to the News Agency software that
handle these requests.
The requests are specified using a subset of the 6 OAI-PMH verbs.
When the connection between an Agency client and EURO-Photo is established, the client
has to ask to EURO-Photo some information about the repository: its name, its URL, and its
granularity. The granularity gives an indication of the frequency of the harvesting requests
that EURO-Photo will perform. This information is requested using the verb ‘Identify’.
The typical handshake used for a harvesting session between the EURO-Photo Server and
the News agency Client may be:
1. EURO-Photo starts a Harvesting session. Those sessions are scheduled at certain
time intervals, specified in the harvest granularity value.
2. EURO-Photo requests to the Agency client via http the list of the items that the
client stored in the repository after a certain date and time. The verb to be used
for this request is ‘ListIdentifiers’.
3. The agency provider responds to the request with an xml file containing the GUID
list of the items to be harvested.
4. For each item of the list, EURO-Photo sends an http request for its metadata to the
client, using the verb ‘getRecord’;
5. The Agency client responds with the metadata xml file of the requested item. At
this time, EURO-Photo can also upload the photo file that is supposed to be stored
in the same repository.
The same handshake is valid also for the deletion of existing items in the EURO-Photo
archive.
D6.1 Interoperability Framework Prototype report
22
If an Agency client wants to delete an existing item from the EURO-Photo archive, the
xml file returned at point 5 will have the ‘status=deleted’ set in the xml header file. Of
course, in this case no metadata values have to be included.
D6.1 Interoperability Framework Prototype report
23
2.1.5 The Metadata Semantic Auto-Completion Feature.
Before submitting a new item in the archive, EURO-Photo performs a preprocessing
activity on metadata, trying to fill missing data, were applicable, with automated
translation and/or with semantic tools. Data generated with automatic tools are clearly
identified in visualization as “automatically generated” (e.g. different color).
That preprocessing, available only on English metadata, will automatically generate
content, performing a semantic analysis on existent metadata.
In detail:
• Auto Translation of Metadata: for all metadata that are expected to appear
in 2 languages (native language and English) a translation is performed
when one of the 2 languages is missing;
• Tentative extraction of photo Headline: for all item where the photo
headline is missing, a semantic analysis is done on existing text fields (in
particular on subject, headline and description fields) to produce a relevant
title;
• Tentative extraction of photo category: for all item where the photo
category is missing, a semantic analysis is done on existing text fields (in
particular on subject, headline and description fields) to find the closest
category among the ipct standard categories;
• Tentative extraction of keywords: for all item where the subject is missing,
a semantic analysis is done on existing text fields (in particular on subject,
headline and description fields) to produce a set of keywords;
• Tentative extraction of keywords: for all item where the subject is missing,
a semantic analysis is done on existing text fields (in particular on subject,
headline and description fields) to produce a set of keywords;
• Tentative extraction of location shown, City, Province and State: when those
geographic information are missing, , a semantic analysis is done on
existing text fields (in particular on subject, headline and description fields);
D6.1 Interoperability Framework Prototype report
24
• Tentative extraction of person shown and organization featured: a semantic
analysis is done on existing text fields (in particular on subject, headline
and description fields);
D6.1 Interoperability Framework Prototype report
25
2.1.6 The Europeana Metadata item.
Europeana is fed using the same harvesting protocol used to feed EURO-Photo.
Such feeding mechanism is implemented as follow: when EURO-Photo import an item, if in
the xml file specifies that the item should be inserted also in europeana, EURO-Photo
generates a proper xml file in the Europeana format (version 3.2) and it will put in the proper
repository. The schema of the europeana xml format can be found at
http://www.europeana.eu/schemas/ese/ESE-V3.2.xsd.
In the following table, all the fields than can be (or must be) present in the xml file are
shown. The Metadata that has to be bi-lingua, two fields of same metadata with attribute
‘lang’ will be specified. (see xml example below)
For metadata that has a correspondent value in the EURO-Photo metadata, that relevant
field is indicated. Constant values are quoted.
europeana metadata EURO-Photo metadata BiLingual mandatory
dc:identifier Iptc4xmpExt:DigImageGUID NO NO
dc:creator dc:creator NO NO
dc:subject dc:subject YES NO
dc:description dc:description YES NO
dc:publisher photoshop:source NO NO
dc:date photoshop:DateCreated NO NO
dc:type "photograph" YES NO
dc:format "image/jpg" NO NO
dc:title photoshop:Headline YES NO
dc:source photoshop:source NO NO
dc:rights dc:rights NO NO
europeana:type "IMAGE" NO YES
europeana:isShownAt url: link to page with image file NO YES
D6.1 Interoperability Framework Prototype report
26
Example of a europeana xml file:
<?xml version='1.0' encoding='UTF-8'?>
<europeana_record>
<header>
<identifier>ANSa33R45TGthu6Hy9L</identifier>
<datestamp>2011-01-28</datestamp>
</header>
<metadata xmlns="http://www.europeana.eu/schemas/ese/"
xmlns:europeana="http://www.europeana.eu/schemas/ese/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<record>
<dc:identifier>ANS-a33R45TGthu6Hy9L</dc:identifier>
<dc:title xml:lang="it">ROMA '60: COLOSSEO ILLUMINATO PER 3 NOTTI. </dc:title>
<dc:title xml:lang="en">ROME '60: ENLIGHTENED COLOSSEUM FOR 3 NIGHTS</dc:title>
<dc:subject xml:lang="it">
<rdf:bag>
<rdf:li>colosseo</rdf:li>
<rdf:li>medaglie</rdf:li>
<rdf:li>olimpiadi</rdf:li>
</rdf:bag>
</dc:subject>
<dc:subject xml:lang="en">
<rdf:bag>
<rdf:li>colosseum</rdf:li>
<rdf:li>medals</rdf:li>
<rdf:li>olympic games</rdf:li>
</rdf:bag>
</dc:subject>
<dc:description xml:lang="it">Immagini della Roma del 1960, alternate a foto dei 13 atleti italiani che quell'anno vinsero l'oro olimpico
e intervallate da gigantografie delle statue dello Stadio dei Marmi: sono gli ingredienti della installazione luminosa che da stasera
e fino a sabato, dalle 21 alle 4 di notte, illuminerà il Colosseo, in occasione del 50o anniversario dei Giochi olimpici che si svolsero
nella capitale nel 1960.</dc:description>
<dc:description xml:lang="en">Images of Rome in 1960, alternating with photos of the 13 Italian athletes that year they won
the Olympic gold and interspersed with giant statues of the Stadium Marbles are the ingredients of the lighting installation
that until tonight and Saturday, from 21 4 am, lights up the Colosseum on the 50th / anniversary of the Olympic Games
that took place in the capital in 1960.</dc:description>
<dc:date>2010-09-09</dc:date>
<dc:publisher>ANSA</dc:publisher>
<dc:source>ANSA</dc:source>
<dc:type xml:lang="it">photograph</dc:type>
<dc:type xml:lang="en">fotografia</dc:type>
<dc:format>image/jpg</dc:format>
<dc:rights>ANSA: all rights reserved</dc:rights>
<europeana:type> IMAGE </europeana:type>
<europeana:isShownAt>http://www.EURO-Photo.eu/db/midpic/ANS-a33R45TGthu6Hy9L.jpg?OpenElement</europeana:isShownBy>
</record>
</metadata>
</europeana_record>
D6.1 Interoperability Framework Prototype report
27
2.2 The EURO-Photo Portal features and graphic interface
Graphical interface described in this chapter has been refined and detailed in close
cooperation with users.
2.2.1 Portal accessibility
The EURO-Photo portal is available either for not-registered users or registered one.
Not registered users could freely search, filter and visualize photos.
Registered users will be able to select photos from different agencies and submit a Request
of Quotation either for mid-resolution or high resolution version.
When a not-registered user tries to submit a Request of Quotation, he is asked to register.
Registration is free of charge, but requires a full identification and qualification (e.g.
specifying country) in order to process the Request of Quotation as stated by copyright
owner. The Request of Quotation is submitted to copyright owner unless he appoints for
some countries a local dealer.
There are also back-office accounts for news agency to manage Photo Galleries and for the
Aministrator to set-up the system configuration and edit photo metadata. The Administrator
is responsible set up and manage the upload process from News Agencies and the feeding of
Europeana.
D6.1 Interoperability Framework Prototype report
28
2.2.2 The main EURO-Photo page.
EURO-Photo portal home page contains the following information:
• a fixed header: present in every page, it’s composed by EURO-Photo logo, and the
link buttons to home page and login page ;
• a EURO-Photo project description of the purposes and functionalities of EURO-Photo.
Throught this page users can:
• perform filters and search for photos.
• visualize the photo lists,
D6.1 Interoperability Framework Prototype report
29
SECTIONS
Photo showing section:
in this section the items, selected according to filters and searches set, are shown. The
items can be shown as thumbnails or as a list. In the thumbnail view, a not watermarked
thumbnail of the photo is shown, among with essential data, such as the title (truncated in
necessary), the dimension and the event date. In the list view, no thumbnail is shown, but a
more verbose description of metadata is presented, including title, description, location and
date of the event, and so on. Clicking on a thumbnail or on a list element will show in a new
page the mid-resolution image among with metadata and other functions (see below). It is
possible to browse among all the pages with direct links to the first and last page.
The filter section:
in this section it is possible to filter the items to be shown by subjects. Multiple subjects can
be selected simultaneously. The subjects match with IPCT categories, and are stored in the
metadata field Subjectcode, in the first 2 significant bytes. If an item in the archive does not
have the subjectCode information, that item will not be filtered and always shown. It is also
possible to filter by Date or Agency.
The query section:
in this field it possible to perform natural language query in different languages to be chosen
in the option menu. The searches will act on semantic bases on relevant fields: the system
will search for exact matches of words inserted, but it will also identify the semantic domain
of the subject of the query finding matches upon similarity rankings. Semantic queries are in
any case performed translating the query in English and using the English metadata of the
photos.
“Exact match” toggle disable semantic search
D6.1 Interoperability Framework Prototype report
30
The advanced search section:
Advanced search allows building a query adding conditions that has to be simultaneously met
(Logic AND). The conditions are built on metadata fields of the photos; each metadata has
different operators
applicable on them, depending on the data type.
Location, People, Organization, Keywords fields are autocompleted using specific
dictionaries automatically generated during photo upload phase.
D6.1 Interoperability Framework Prototype report
31
Sorting Option:
Results could be sorted by “best match” or by “date” in ascendig/descending” order.
2.2.3 The Photo Visualization Page
In this page selected photo and related metadata are shown
D6.1 Interoperability Framework Prototype report
32
Using the “show all toggle” more metadata could be shown like GUID, Image size, and
automatically traslated and semantically entracted metadata.
D6.1 Interoperability Framework Prototype report
33
2.2.4 Europhoto Galleries
A Photo Gallery thematically aggregate a set of pictures (up to 50) and is described, like
a single picture, by a Gallery Headline and Gallery Description metadata. Photo Galleries are
managed (eg search) into the portal in a similar manner of a single photos. Gallery cover
photo is distinguished by a single photo by a red frame; by clicking on it , photos in the
gallery will be shown. Any Agency could create using its back-office account(s) its own
Galleries including, eventually, photos present in the EURO-Photo Portal from other Agencies.
Each agency selected periodically up to 10 Top Galleries that are home page candidate.
The home page is, than, dynamically composed with 18 Top Galleries (two per agency)
selected randomly from the list of 10 provided by each agency. The positioning of the Top
Gallery in home page is random and dinamic.
Gallery List : (enable = active gallery , Hot = gallery always visualized)
= Modify Gallery
= Delete Gallery
D6.1 Interoperability Framework Prototype report
34
Create a new gallery
Red frame around a picture qualify it as gallery cover.
D6.1 Interoperability Framework Prototype report
35
To add a photo to a gallery, right click on picture and select target gallery.
In this page a watermarked version of the photo is visualized, and the metadata for it. It is
possible to choose between English or native language version of the photo metadata. All
metadata fields that are empty are not shown.
It is possible to show the next or previous photo in the current photo list.
It is possible to search for similar photo in the archive, using semantic similarity in relevant
fields. Typically, this is done to find all photos regarding the same event. When the user
search for similar photo, he can decide what metadata field take into account for the
research. The search result is presented as a thumbnail list of the similar photo, with an
indication of the rank of similarity in percentage.
Eventually, it is possible to buy the photo, in the mid and the high resolution version. The
high resolution version will be available only for the News Agency that will allow to. (for
Agency that does not sell hi-res images, the Button “buy Hi-res photo” will not be
presented.)
D6.1 Interoperability Framework Prototype report
36
If the user is logged in, the user-customized price (depending on the user professional
profile, see below) of the two versions of the photo is presented, according to the New
Agency configuration set by the webmaster.
2.2.5 User Registration Procedure
Login
D6.1 Interoperability Framework Prototype report
38
Registration Mail
Succesful registration confirmation.
D6.1 Interoperability Framework Prototype report
39
2.2.6 Europhoto Market Place
EURO-Photo implements a Requests for Quotation mechanism.
Registered users will be able to select photos from different agencies and submit a Request
of Quotations either for mid-resolution or high resolution photos througth an automatically
generated set of e-mails.
When a not-registered user tries to submit a Request of Quotation, he is asked to perform a
free or charge registration.
At registration time user need to fill a form providing legal identification and profiling
information including user type and size (e.g daily newspaper with number of copies, web
portal with registered user number, TV channel with audience, book publisher with type of
publication) and country. In order to manage the routing of the Request of Quotation as
stated by copyright owner. The Request of Quotation is submitted to copyright owner unless
he indicates for some countries a local dealer.
Route Mail Quotation Request
D6.1 Interoperability Framework Prototype report
40
Default E-Mail : copyright owner reference mail address
Add alternative Mail for country : allows, eventually to enter an alternative mail address
for each country, in order to automatically forward the Quotation Request to the local dealer,
accordingly with the “country” field declared by each user at registration time.
On regularly basis EURO-Photo provides a report of submitted Request of Quotations.
2.2.7 Transfering Photos to Europeana
This function is riserved only to Administator
D6.1 Interoperability Framework Prototype report
41
Last Europeana transfer date and result (Correct, Ongoing, Error) is shown.
The number of picture to be transmitted with a define date interval is shown in advance.
D6.1 Interoperability Framework Prototype report
42
3 EURO-Photo WORKGROUP Evaluation and Testing
The workgroup is composed by a subset of EURO-Photo participating agencies namely:
• MTI (team leader)
• ANSA,
• EFE,
• EPA
Accordingly with the methodology described below:
- Till the site wasn’t published our ideas had been discussed about registration and ordering
process
- The URL of the Europhoto portal was sent to every project members. The workgroup collected
the comments, and testing results from them
- The workgroup created the test document draft, and sent to every project member for final
check
- The finalized test document was sent to the developers
3.1 Issues Examined
During the test the workgroup examined the following:
Does it meet the desired goal?
The portal is designed to give the possibility of searching pictures and to forward the
costumers to the agencies
Is it clear and easy to use for visitors?
The design and the structure should be simple
How it helps the returning visitors?
If someone needs he should be a registered user. (Not fully agreed)
D6.1 Interoperability Framework Prototype report
43
The description of the expected ordering process
According to Business model I the agencies will be informed via e-mail about an order.
What kind of information is required in order to serve a potential costumer?
This order e-mail should contain information about the costumer and about the
picture as well. The workgroup defined the required information fields.
Comparison with similar portals
Since there are several portals accessible via Internet offering pictures, the way of
usage should be similar
Legal consideration
How to inform the visitor what he can do and what he can’t do with the pictures
Performing some sample search weather it gives the expected result
The sample searches and the results were fully documented with screen shots and
descriptions.
What kind of information should be shown?
Since there is pictures’ processing are different in every agency we defined the
metadata set are shown on the different pages. The automatic translated fields should
be used only for searching
Does it manage the multilingual content well?
Since there is metadata in several languages it is important to show the language-
specific characters correctly
D6.1 Interoperability Framework Prototype report
44
3.2 Beta portal test report
http://euro-photo.expertsystem.net/index.aspx
3.2.1 Frontpage
• ANSA propose to add in the home page a “Welcome button” to enter to an EURO-
Photo presentation to be prepared
• "Gallery" concept to be defined by Expert System. For every gallery... how is the
“cover picture” selected? They should contain more than two pictures.
• The refreshing time should be increased. It is too fast. Every 20/30 seconds could be
enough.
• "Show galleries"/"Show foto" option not working. Expert System should explain what
they’re planning to do with those checkboxes. What kind of action/filter will be
executed if they are selected or not?
• “Sort by” offers only “best match” order. We need to define different criteria (in
example, date, location, title...) and ascending/descending order option. Date is
important!
• “Broken galleries”. Front picture is broken and if you click them, you get an empty
collection - corrected
D6.1 Interoperability Framework Prototype report
45
• After selecting a gallery the “back to the galleries” button/link would be useful
3.2.2 Single Picture view
• GUID: seems to show an internal field... better if not shown (or put it in the “Show all”
section - ANSA) Actually, we think it should show content in tag
"Iptc4xmpExt:DigImageGUID" provided by sources that identifies a picture uniquely
(EFE), or the filaname (MTI)
• "Data Creazione:" to be translated. Our opinion is that it should show date format too
(dd/mm/yyyy) – Comment : Obviously should be the date of when the picture
has been shooted
• Country: missing field. It should be extracted from “iptc4xmp:countrycode“ tag
• move “State-province” in the second “Show all” page .In my opinion this information
is not so interesting it is related to USA …
• "National language" : better if "dc_language" in "native_language_metadata" is used
to form the label (i.e., if value is "SPA" we suggest showing "Spanish" or "National
language (Spanish)")
D6.1 Interoperability Framework Prototype report
46
We also suggest showing the following information:
- size (height and width in pixels): we should discuss if we need here the maximum
available size instead of the size available in the portal (which is a downsized version
of the original).
Comment : It is important that the customer realize that an high resolution is
available on demand! I’d rather prefer not to show the size of the medium
resolution (it is not useful and could be misleading) and add in all pictures a
warning like “The high resolution is available on demand”.
- nd another point is that there is no tag in the XML containing the original picture size.
We should discuss how Expertsystem will get to know the original size.
- Instructions of use: tag "photoshop:Instructions" in both english and national
languages all fields which were given by the agency
Comment : Keep most important information in the first page and Insert a “Show
all” button for provide all information in a second page
• the national characters are sometimes replaced with “?”, or not shown correctly (next
picture)
• Furthermore the PAP photos have only automatically translated English text – Why?
D6.1 Interoperability Framework Prototype report
47
• The automatic translation or fields are filled by the semantic engine should be hidden
(only useable for search) We should discuss ANSA’s proposal.
Comment : Why not publish them in the “Show all” page? It should be clear that
are automatic-generated information (different color and a special warning). For
example if the English translation is missing it could be useful an automatic one.
• the keywords are divided by space too. It is not good. The forward search with the
selected keyword gives no result. (The function should be nice) seems corrected
D6.1 Interoperability Framework Prototype report
49
3.2.3 Performing a search
When showing result in list view:
- label "matching percentage" is not shown properly
- if the content in "Keywords" is very long, the label "Location Shown" is not readable
(tested in Chrome, Firefox and IE8)
- The state/province field is not shown correctly if the advanced search panel is open
D6.1 Interoperability Framework Prototype report
50
Performing a single search
• The multilingual search doesn’t give correct result
an example:
car in English Result 132
• autó in Hungarian
(the paging control disappeared , and the result set didn’t change. Why?)
• We would like to know which fields are searchable via the simple search? (the
headline, the creator and the credit are not) Our opinion that all the fields which
are exist in the given language should be searchable.
• If the semantic search is too noisy we need a check box saying “Exact match”
D6.1 Interoperability Framework Prototype report
51
3.2.4 Advanced search
- In our opinion, "KEYWORD SEARCH" button should be renamed to "SEARCH" as it
may be filtering by date or category, not only on keywords. If possible, the button
should be placed above "Keyword Search" label to show that it's a button that applies
to any search defined below, not only the first group (Location, People, Organization,
Keywords)
In that case this search button should belong to the advanced search and the other
one to the simple search;
- searching for any of the options in “Keywords” is case sensitive and it should match
exactly the text entered (for example, different results for “FRANCISCO FRANCO” and
“FRANCISCO FRANCO BAHAMONDE”). In our opinion, this is not the best behaviour
for a search engine. We prefer case insensitive search and “part of the search” is
considered “hit”
D6.1 Interoperability Framework Prototype report
52
-------------
- keywords: it seems it's not working (i.e., searching "SMOKING" doesn't give any result
but at least picture EFE766817 has that keyword among all the metadata)
D6.1 Interoperability Framework Prototype report
53
- Search by date: not working. See example.
> More: no way to clear date restrictions in the form. Even if I go out of the page,
everytime we get back to Europhoto site and click "Advanced search", the dates are still
there
• the Clear form deletes only the “keyword search” block
• Filtering by date
o in the calendar the “from” and “to” dates should be allowed only from the
last century (it is difficult to go back to the 1960’s) entering the dates
manually is allowed. it is good.
D6.1 Interoperability Framework Prototype report
54
o but filtering by date doesn’t work
• Filtering by source
o OK
• Filtering by subject
o OK
• Filtering by person
o the More.. link goes to the galleries
o there is no possibility to clear the person filter (if I select a person from the
list, it is not possible to go back, and select another one) The clear form
must delete every search criteria. Hiding the advanced search the filters
remain active and the next simple search gives an unwanted result
o the sample search
� actress – simple search
� Filter by person name:
I was interested in why the “Portrait” in the list. After clicking it, I got the
following result:
D6.1 Interoperability Framework Prototype report
55
� the Filter by person changed
After clicking Anna T, I got this picture:
D6.1 Interoperability Framework Prototype report
56
The actress name is good both in the Headline and description fields
(Tőkés Anna), but wrong in the person shown field.
3.2.5 Other issues to remark
• We should define once and for all if uploaded pictures should have the local logo or
not and where to put the “Europhoto logo”.
• There’s no way to make multiple selection. When clicking on the “cart icon” in a
picture, you get the contact form directly, there’s no way to go on searching and
make the final “order” with all the selected pictures. In one word, there’s no
“shopping cart” functionality (it should also allow review all selected pictures, add and
remove from the cart)
• This picture should be greater with a text as “Buy the photo”. Our goal is to sell
pictures!
• The result set items are seems to be maximized in 1000. The user should be informed
about this. (Or let the set as large as it is)
• To be added a Copyright section
Registration
• We will have a registration form, with these fields:
Name(Company), Name (Person), Username, Password, Email, Country, Phone
(optional)
D6.1 Interoperability Framework Prototype report
57
The user has the possibility to register, but the question if it is mandatory or not is still
open. If the registration is optional, the user has to give this information on the
contact form. The advantage of having such a registration feature might be making it
easier to contact us if they're going to purchase our pictures in a regular basis.
• The user has to accept the “Terms of Use” during the registration, or instead of it.
(We have a draft text)
Order form (Contact form)
• Personal data
o If the user is registered, he should log in.
o If not, he should fill the following fields:
Name(Company), Name (Person), Email, Country, Phone (optional)
• Picture data
o the picture data came from the picture metadata
o usage of picture
How is the user planning to use the pictures (personal use, editorial use, etc.)
as it may result in different selling condition
E-mail notification
The system should send two types of e-mail notification about an order.
1. One to an agency to ask for the high resolution pictures according to the rules were
decided in Frankfurt:
• If the selected pictures of only one agency the mail will be sent on national basis.
(If the request comes from third country the mail will send to the owner)
• If pictures of several agencies is selected the mail will be sent on national basis.
(If the request comes from third country the mail recipient will be selected by an
automatic system)
D6.1 Interoperability Framework Prototype report
58
Comment : I was rethinking about our decision. It seems a bit complicated to
manage. It is much easier to send the e-mail directly and always to the copyright
owner
The mail should contain the following information:
• all the contact information entered by the user (registered or not)
• comments for the current request if exists
• all the information to locate the pictures requested:
ID
Filename
Preview of the pictures
Title
Copyright holder
Special Instructions (if available)
2. An e-mail confirmation to the customer informing him that the request was successfully
sent to xxx (xxx = the name of the agency, which is going to serve him)
This mail should inform the user about the deadline till he is going to be served.
D6.1 Interoperability Framework Prototype report
59
CONSORTIUM ASSESMENT QUESTIONAIRE
Why we needed?
During testing the site we have found some details to be discussed among the partners. The
work of the test workgroup has been continued.
What was it about?
First we have collected the main topics to be discussed. These were the following:
- Frontpage general – It is very important how the front page looks like, how it
describes the portal’s content
- Galleries – If the frontpage has got galleries, how they are organized?
- Footer information – What other information does the visitor need to know? (About
us, privacy policy etc.)
- What metadata should be shown?
o on thumbnail grid
o on list view
o on preview page
- What information should be asked?
o on registration form
o on enquire form
- How the search should work?
o How to help visitors to perform the best search for their needs?
o What kind of fields needed to narrow search?
How was it done?
Since the partners live in different countries it seems the best to use Google spreadsheet to
create the questionnaire, and collect the partner’s opinion. After everyone had filled it, the
gathered information was exported to excel format, where some statistical work was made
to evaluate the answers.
D6.1 Interoperability Framework Prototype report
60
3.3 EUROPHOTO PORTAL QUESTIONNAIRE
the new web address of the EURO-Photo business portal: www.europhoto.eu.com
Please select Your agency! * [ANSA \/]
3.3.1 Frontpage
This is the first page, what one meets first Do You agree with the following statements?
Should the frontpage contain some description about the content?
[ ] YES
[ ] PARTLY
[ ] DON'T AGREE
If yes, which way do You prefer?
[ ] no words only sample pictures show the content
[ ] no pictures only words to describe the content
[ ] sample pictures to show the content + few sentences (short description) + link to
the detailed description
[ ] Other:
What is Your opinion? Do we need galleries to show the content? Please answer YES or NO.
If You think we should show the content somehow, but no galleries, please describe how in
"other" section
[ ] YES
[ ] NO
[ ] Other:
D6.1 Interoperability Framework Prototype report
61
If there are galleries on the front page, how they are organized? If You prefer other selection
critetia please describe your idea in the "other" section
[ ] by agency
[ ] by topic
[ ] Other:
D6.1 Interoperability Framework Prototype report
62
If there are galleries on the front page, what information should be shown?
YES NO Don't know
Cover picture ( ) ( ) ( )
Title (Agency or Topic) ( ) ( ) ( )
Date of creation ( ) ( ) ( )
Number of pictures in it ( ) ( ) ( )
Description of the cover picture
in Alt text ( ) ( ) ( )
Other fields - please define
them later ( ) ( ) ( )
What other fields would you like to see on the frontpage?
Other information (shown for example on the bottom of every page)
(Source: gettyimages.com – please visit getty for the explanations)
YES NO
About us ( ) ( )
Contact us ( ) ( )
Enquiry form ( ) ( )
Privacy policy ( ) ( )
Terms & Conditions ( ) ( )
D6.1 Interoperability Framework Prototype report
63
YES NO
Copyright info ( ) ( )
Registration ( ) ( )
Other - please define them
later ( ) ( )
What other links would you like to see on the bottom?
D6.1 Interoperability Framework Prototype report
64
3.3.2 Thunbnail Grid
This is the result page after a search performed
What information should be shown?
YES NO
Thumbnail picture ( ) ( )
Title in English ( ) ( )
Date when the photo was taken ( ) ( )
Source agency ( ) ( )
Relevancy ( ) ( )
Description of the cover picture in Alt
text ( ) ( )
Other fields - please define them later ( ) ( )
What other fields would you show?
D6.1 Interoperability Framework Prototype report
65
3.3.3 List view
This is the result page after a search performed (2. type)
What information should be shown?
YES NO
Thumbnail picture ( ) ( )
Title in English ( ) ( )
Date when the photo was taken ( ) ( )
Source agency ( ) ( )
Creator ( ) ( )
City ( ) ( )
State/province ( ) ( )
Category ( ) ( )
Relevancy ( ) ( )
Description of the cover picture in Alt
text ( ) ( )
Other fields - please define them later ( ) ( )
Keywords ( ) ( )
What other fields would you show?
D6.1 Interoperability Framework Prototype report
66
3.3.4 Single Picture view
This is the preview page
Do You agree to show the preview image with EUROPHOTO watermark?
[ ] YES
[ ] NO
Should we need a “Show all fields” possibility in this view?
[ ] YES
[ ] NO
What information should be shown? Please look through the field list. YES means, the fields
should be shown immediately, NEVER means the visitor shouldn’t meet this information, ALL
means the field is visible only in “Show all” option
YES NEVER ALL
LANGUAGE INDEPENDENT
FIELDS ( ) ( ) ( )
Digital Image GUID ( ) ( ) ( )
Filename ( ) ( ) ( )
IPTC Subject Code ( ) ( ) ( )
Date when the photo was
taken ( ) ( ) ( )
Creator ( ) ( ) ( )
Country code ( ) ( ) ( )
D6.1 Interoperability Framework Prototype report
67
YES NEVER ALL
Country name in English ( ) ( ) ( )
Source ( ) ( ) ( )
NATIONAL LANGUAGE FIELDS ( ) ( ) ( )
Headline ( ) ( ) ( )
Caption/Description ( ) ( ) ( )
Keywords ( ) ( ) ( )
City ( ) ( ) ( )
State/Province ( ) ( ) ( )
Location Shown ( ) ( ) ( )
Person Shown in the Image ( ) ( ) ( )
Name of Organisation Featured
in the Image ( ) ( ) ( )
Instructions ( ) ( ) ( )
Creator's Jobtitle ( ) ( ) ( )
Copyright Notice ( ) ( ) ( )
ENGLISH LANGUAGE FIELDS ( ) ( ) ( )
Headline ( ) ( ) ( )
Caption/Description ( ) ( ) ( )
D6.1 Interoperability Framework Prototype report
68
YES NEVER ALL
Keywords ( ) ( ) ( )
City ( ) ( ) ( )
State/Province ( ) ( ) ( )
Location Shown ( ) ( ) ( )
...
D6.1 Interoperability Framework Prototype report
69
3.4 Questionaire Outcome
3.4.1 Front-page general
Should the frontpage contain some description about the content?
YES 8
PARTLY 1
If yes, which way do You prefer?
sample pictures to show the content + few sentences (short
description) + link to the detailed description 9
What is Your opinion? Do we need galleries to show the content?
YES 4
YES, but only as a part of the homepage, not covering the whole site 1
NO 3
one gallery for each agency with around 10 images and an explanation
about the agenncy (on subpage hidden behind the logo?) 1
D6.1 Interoperability Framework Prototype report
70
3.4.2 Galleries
If there are galleries on the front page, how they are organized?
by topic
No galleries
Both
Both - by agency and by topic. Each agency is responsible for their galleries, but galleries should be shown up by theme.
A small selection of best images from all agencies
hidden behind the logo of each agency
If there are galleries on the front page, what information should be shown? [Cover picture]
YES
If there are galleries on the front page, what information should be shown? [Title (Agency or Topic)]
YES
Don't know
If there are galleries on the front page, what information should be shown? [Date of creation ]
YES
NO
If there are galleries on the front page, what information should be shown? [Number of pictures in it ]
NO
YES
If there are galleries on the front page, what information should be shown? [Description of the cover picture in
Alt text ]
D6.1 Interoperability Framework Prototype report
71
YES
NO
If there are galleries on the front page, what information should be shown? [Other fields - please define them
later]
Don't know
NO
D6.1 Interoperability Framework Prototype report
72
3.4.3 Other Information
Other information (shown for example on the bottom of
every page) [About us]
NO 1
YES 8
Other information (shown for example on the bottom of
every page) [Contact us]
YES 9
Other information (shown for example on the bottom of
every page) [Enquiry form]
NO 2
YES 7
Other information (shown for example on the bottom of
every page) [Privacy policy]
NO 1
YES 8
Other information (shown for example on the bottom of
every page) [Terms & Conditions]
YES 9
Other information (shown for example on the bottom of
every page) [Copyright info]
D6.1 Interoperability Framework Prototype report
73
YES 9
Other information (shown for example on the bottom of
every page) [Registration]
YES 7
NO 2
D6.1 Interoperability Framework Prototype report
74
3.4.4 Tumbnail Grid
What information should be shown? [Thumbnail
picture]
YES 9
What information should be shown? [Title in
English]
YES 9
What information should be shown? [Date when
the photo was taken]
YES 6
NO 2
1
What information should be shown? [Source
agency ]
YES 9
What information should be shown? [Relevancy]
YES 2
NO 6
1
What information should be shown? [Description of
the cover picture in Alt text ]
YES 8
NO 1
What information should be shown? [Other fields -
please define them later]
D6.1 Interoperability Framework Prototype report
75
5
NO 4
just a remark. there could be
several ways to show the picture.
e.g; only the thumbnail with a
minimum of information.on
mouseover an overlap with more
info (+ maybe some icons such as
order, email...) and after a click one
can go to the detail
D6.1 Interoperability Framework Prototype report
76
3.4.5 List view
What information should be shown? [Thumbnail
picture]
YES 9
What information should be shown? [Title in
English]
YES 9
What information should be shown? [Date when
the photo was taken]
YES 9
What information should be shown? [Source
agency ]
YES 9
What information should be shown? [Creator]
NO 1
YES 8
What information should be shown? [City]
NO 4
YES 5
What information should be shown?
[State/province]
NO 5
YES 4
What information should be shown? [Category]
YES 3
NO 5
1
What information should be shown? [Relevancy]
NO 8
What information should be shown? [Description
of the cover picture in Alt text ]
YES 5
NO 4
What information should be shown? [Other fields
- please define them later]
3
NO 3
D6.1 Interoperability Framework Prototype report
77
YES 3
What information should be shown? [Keywords]
YES 3
NO 4
2
What other fields would you show?
Caption
Complete caption
D6.1 Interoperability Framework Prototype report
78
3.4.6 Single picture (Independent)
Do You agree to show the preview image with
EUROPHOTO watermark?
YES 9
Should we need a “Show all fields” possibility in
this view?
YES 9
Language independent data [Digital Image
GUID]
YES 4
ALL 3
NEVER 2
Language independent data [Filename]
YES 3
NEVER 5
ALL 1
Language independent data [IPTC Subject Code]
NEVER 4
YES 1
ALL 4
Language independent data [Date when the
photo was taken]
YES 8
ALL 1
Language independent data [Creator]
YES 9
D6.1 Interoperability Framework Prototype report
79
Language independent data [Country code]
YES 2
ALL 4
NEVER 2
1
Language independent data [Country name in
English]
YES 8
ALL 1
Language independent data [Source]
YES 9
D6.1 Interoperability Framework Prototype report
80
3.4.7 Single picture (National)
National language data [Headline]
YES 8
ALL 1
National language data [Caption/Description]
YES 8
ALL 1
National language data [Keywords]
YES 4
ALL 5
National language data [City]
YES 6
ALL 3
National language data [State/Province]
YES 5
ALL 3
NEVER 1
National language data [Location Shown]
YES 4
ALL 4
NEVER 1
National language data [Person Shown in the Image]
YES 4
ALL 4
NEVER 1
National language data [Name of Organisation Featured in the
Image]
YES 2
ALL 5
NEVER 2
D6.1 Interoperability Framework Prototype report
81
National language data [Instructions]
YES 6
ALL 3
National language data [Creator's Jobtitle]
YES 2
NEVER 6
1
National language data [Copyright Notice]
YES 7
ALL 2
D6.1 Interoperability Framework Prototype report
82
3.4.8 Single picture (English)
English data [Headline ]
YES
English data [Caption/Description]
YES
ALL
English data [Keywords ]
YES
ALL
English data [City ]
YES
ALL
English data [State/Province]
YES
ALL
NEVER
English data [Location Shown]
YES
ALL
NEVER
English data [Person Shown in the Image ]
YES
ALL
NEVER
English data [Name of Organisation Featured in the Image]
YES
ALL
NEVER
English data [Instructions]
YES
ALL
English data [Creator's Jobtitle]
YES
NEVER
ALL
D6.1 Interoperability Framework Prototype report
83
English data [Copyright Notice]
YES
ALL
What do You think about values come from dictionary? (semantic data) Do we show them on the
preview page?
NO
we should test the quality and depending on this decide wether to show them or not
YES
D6.1 Interoperability Framework Prototype report
84
3.4.9 Search
Do You agree to have a Help button/link to inform
visitors how to use simple search?
YES 5
PARTLY 1
YES, NO 2
NO 1
Do You agree to have a Help button/link to inform
visitors how to use advanced search?
YES 7
PARTLY 1
NO 1
The advanced search is shown
immediately (as now) 7
only after a search (to give the possibility to be more specific) 2
The result set could be narrowed by... [Keywords]
YES 8
NO 1
The result set could be narrowed by... [Person shown]
YES 8
Not important 1
The result set could be narrowed by... [City]
YES 8
Not important 1
The result set could be narrowed by... [Country]
YES 9
The result set could be narrowed by... [Other way
(described later)]
Not important 4
4
YES 1
What other fields could be used to narrow search?
agency (credit/source), photographer
D6.1 Interoperability Framework Prototype report
85
Source
Date picture was taken
Creator
IPTC Subject Code
Digital Image GUID
Date / Source / subject
Category
Agency
Photographer
Creation date
IPTC Subject
Code
GUID
D6.1 Interoperability Framework Prototype report
86
3.4.10 Registration
The searching and the preview images with watermark
without registration. Registration is mandatory for the
HiRes picture. Do You agree?
YES 8
No user registration form 1
Where can one have the possibility to register?
When entering chart (enquire form) 2
On the front page 4
No user registration form at all 1
Anytime 1
Both options 1
Fields to be filled on the registration form [Name
(Company)]
Required 6
Optional 2
Not important 1
Fields to be filled on the registration form [Name
(Person)]
Required 7
Optional 1
Not important 1
Fields to be filled on the registration form [Username]
Required 7
Not important 2
Fields to be filled on the registration form [Password]
Required 7
Not important 2
Fields to be filled on the registration form [Email address]
Required 8
Not important 1
Fields to be filled on the registration form [Country]
Required 8
Not important 1
Fields to be filled on the registration form [Phone]
Optional 3
Not important 1
D6.1 Interoperability Framework Prototype report
87
Required 5
Fields to be filled on the registration form [Other]
Not important 3
Optional 2
4
D6.1 Interoperability Framework Prototype report
88
3.4.11 Enquire Form
Fields to be filled on the enquire form [Usage of
the picture]
Required 8
Not important 1
Fields to be filled on the enquire form [Requred
quality]
Required 7
Optional 1
Not important 1
Fields to be filled on the enquire form [Comment]
Optional 4
Not important 1
Required 4