D2.1 Publication of metadata schema for Pan-European Aggregator · 2017-04-25 · Project Title:...

DELIVERABLE

Project Acronym: EUscreenXL

Grant Agreement number: ICT PSP 325100

Project Title: EUscreenXL, the pan-European audiovisual aggregator for Europeana

D2.1 Publication of metadata schema for Pan-‐European Aggregator

Revision: Final version v1

Author(s): Marco Rendina (Cinecittà Luce)

Project co-funded by the European Commission within the ICT Policy Support Programme Dissemination Level

P Public X C Confidential, only for members of the consortium and the Commission Services


2

DOCUMENT INFORMATION

Deliverable number: D2.1 Deliverable title: Publication of metadata schema for the Pan-‐European Aggregator Contractual date of deliverable: 31-‐08-‐2013 Actual date of deliverable: 11-‐11-‐2013 Author(s): Marco Rendina (LUCE) Participant(s): Jean-‐Pierre Evain (EBU) Work package: 2 Work package title: Aggregating and enriching content Work package Leader: BUFVC Dissemination Level: Public Version: v1 Keywords: metadata, schema, information architecture, aggregator

HISTORY OF VERSIONS

Version Date Status Author (organisation) Description/Approval Level

0 05/07/03 First draft Marco Rendina (LUCE) First draft for the preparation of the Metadata and Content Handbook v1

0.1 30/08/03 Draft Marco Rendina (LUCE), Jean-‐Pierre Evain (EBU)

Input and revision by Eve-‐Marie Oesterlen (BUFVC) and official publication in the Metadata and Content Handbook v1

0.2 30/09/03 Draft Marco Rendina (LUCE), Jean-‐Pierre Evain (EBU)

Deliverable ready for peer review

1 11/11/03 Final Marco Rendina (LUCE) Integrated the internal review comments from Arne Strabenau (NTUA)

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.


3

ABSTRACT

The EUscreenXL project aims to make audiovisual content from broadcasters and audiovisual archives across Europe findable and accessible online. The main objective of the project is to act as the Pan-‐European aggregator for Europeana in the audiovisual domain, bringing together all major European broadcasters and to actively reach out to all European audiovisual archives. This document examines the audiovisual metadata landscape, focusing mainly on the descriptive type of metadata, and looking in particular at the work done on this matter in related EU co-‐funded projects, such as the European Film Gateway, and in relevant standardisation initiatives like the CEN EN 15907 and the European Broadcasting Union EBUcore, in order to investigate the suitability and make the necessary adaptation to the EUscreen metadata schema for its use in the Pan-‐European aggregator for audiovisual content. These changes are necessary in this new context since the metadata schema developed in EUscreen was mainly devised for television content, whereas the EUscreenXL project aggregates a broader range of audiovisual media. Together with this overview and analysis of the current situation in the audiovisual metadata domain, this document presents the results of a survey completed by all EUscreenXL content providers. The outcomes of this survey enabled us to assess and evaluate the different local situations regarding metadata and – together with ensuing discussions with the community of content providers in regional workshops – provided the input and highlighted possible new requirements to be considered for the final objective of this deliverable, which is the publication of a metadata schema for the Pan-‐European Aggregator.


4

TABLE OF CONTENTS

Document Information ........................................................................................................................................ 2

History of Versions ............................................................................................................................................... 2

Abstract .................................................................................................................................................................. 3

Table Of Contents .......................................................................................................................................... 4

A Audiovisual metadata landscape ................................................................................................................ 5 1 Introduction ............................................................................................................................................................ 5 2 The EFG metadata schema ................................................................................................................................. 6 3 The EN 15907 standard ...................................................................................................................................... 7 4 EBUCore .................................................................................................................................................................... 8 5 BBC News Storyline Ontology ........................................................................................................................ 10 6 The EUscreen metadata schema ................................................................................................................... 11

B EUscreenXL metadata survey .................................................................................................................... 13 1 Introduction ......................................................................................................................................................... 13 2 Metadata survey findings ................................................................................................................................ 13

C The EUscreenXL metadata schema ........................................................................................................... 17 1 Introduction ......................................................................................................................................................... 17 2 Metadata elements for series/collection record type ........................................................................... 18 3 Metadata elements for item/clip record type .......................................................................................... 19 4 Conclusions .......................................................................................................................................................... 19

D Reference ...................................................................................................................................................... 21

E List of controlled vocabularies ................................................................................................................... 39


5

A AUDIOVISUAL METADATA LANDSCAPE

1 Introduction

In the cultural heritage domain there are several metadata models and standards that have been used in different communities, like libraries, archives and museums. Some of these models are generic enough to be also adopted in multiple domains. Among this plethora of standards and models we can mention the more common and widely adopted ones, like Dublin Core1 (used by various cultural heritage sub-‐domains), LIDO2 Lightweight Information Describing Objects (mainly adopted by museum organisations), EAD3 Encoded Archival Description (endorsed by the Library of Congress and used mainly by archives) and finally EDM4, the Europeana Data Model (used by Europeana for its multi-‐domain aggregator).

All these models and standards, generally adopted in the cultural heritage domain, are not really well suited for the description of audiovisual material, mainly because of the time-‐dependent nature of this content and also for the peculiarity of the audiovisual media. This is why in this document we will focus specifically on the analysis of the audiovisual metadata models only. The EUscreenXL project aims to give access to audiovisual content through Europeana and the EUscreenXL portal. For this reason the subject of this brief investigation on audiovisual metadata standards and models will be focused on the metadata used for access and fruition, the so called “descriptive metadata”, and will not consider the “administrative metadata”, such as the ones used for preservation, identification and distribution of audiovisual content (i.e. technical and rights metadata).

The following Sections outline the main initiatives and standards related to descriptive metadata for audiovisual content together with an analysis of their characteristics and their suitability for the EUscreenXL project. This overview does not claim to be exhaustive. Instead, it focuses on the initiatives in the audiovisual and multimedia domain most suitable for the scope of the project, considering in particular the initiatives carried on by similar projects or endorsed by the EUscreenXL communities of reference (broadcasters and audiovisual archives). For a extensive overview of all the metadata initiatives in the audiovisual domain see the PrestoPrime deliverable “Metadata Models, Interoperability Gaps and Extensions to Preservation Metadata Standards”5.

1 http://dublincore.org/ 2 http://www.lido-‐schema.org/ 3 http://www.loc.gov/ead/index.html 4 http://pro.europeana.eu/edm-‐documentation 5 https://prestoprimews.ina.fr/public/deliverables/PP_WP2_D2.2.2_MetadataModels_InteroperabilityGaps_v1.50.pdf


6

2 The EFG metadata schema

The European Film Gateway6 Best Practice Network, funded by the European Commission under the eContentplus programme, aimed to provide a single access point to 59 collections from 19 film archives across 14 European countries.

The three-‐year project, which ended on October 2011, has developed a metadata model7 for the description of film related content. The model took into consideration standards such as EAD and Dublin Core and models like FRBR8, as well as more film-‐specific standards, such as the Cinematographic Works Standards EN 15907 (described in the following chapter).

Following the FRBR model, the EFG schema defines three different levels of description: Creation (referring to the concept of Cinematographic Work, including only properties that remain constant throughout all of its manifestations), Manifestation (the physical embodiment of an audiovisual creation, including all properties that can change during the lifecycle of an audiovisual creation without affecting the identity of a film work as such) and Item (a logical wrapper for the digital object, pointing to the digital file held in the source repository).

On these three main levels, eight interrelated entities have been defined in the EFG metadata model: • The AVCreation contains the properties of a cinematographic work: the film title, the record source

(archive), the country of reference, the publication year, etc. • The AVManifestation contains the information about the physical embodiment of an audiovisual

creation. Examples are archival copies (analogue or digital) and database files. Properties of an AVManifestion include language, dimension, duration, coverage, format, rights holder, and provenance.

• The NonAVCreation describes all non-‐audiovisual creations that can be represented in EFG. These are pictures, photos, correspondence, books or periodicals. The properties of NonAVCreations are: title, record source, keywords, description, date of creation and language.

• The NonAVManifestation entity keeps track of copies of non-‐audiovisual objects. It has properties such as type (e.g. text, image, sound), specific type (e.g. photograph, poster, letter), language, dates (i.e. a date or period associated with the issue of the manifestation), digital format (including its status, size, resolution), physical format, geographic scope, rights holder.

• The Item entity points to the digital file held in the source archive. Its attributes are isShownBy (i.e. the URL reference to the digital object on the content provider’s web site), isShownAt (i.e. the URL reference of the object in its information context), digital format, provider and country.

• The Agent is defined as an entity that can perform an action. The model includes three agent types: Person, Corporate Body and Group.

• The Event is an entity that can occur within the lifecycle of an audiovisual or non-‐audiovisual creation. Examples of Events are Physical Event (e.g. a public screening or a broadcast), Decision Event (e.g. when a manifestation of a creation was evaluated by a censorship body), IPR registration, Award (i.e. the award obtained by an audiovisual creation or an agent), Production event (e.g. dates and places where castings took place, dates and locations of shooting).

6 http://www.europeanfilmgateway.eu 7 http://www.efgproject.eu/downloads/D2%202_Common_Interoperability_Schema_final.pdf 8 http://www.ifla.org/publications/functional-‐requirements-‐for-‐bibliographic-‐records


7

• The Collection is defined as a compilation of creations (audiovisual or non-‐ audiovisual).

The model defines XML element types and attributes for all the eight entities and their relevant properties. The common schema is conceived as the type union of eight XML schemas (one for each entity) in such a way that one EFG XML record represents one entity together with its relationships to other entities. Furthermore, the schema defines the so-‐called “controlled elements”, which are the XML elements whose values must comply with a given vocabulary of terms.

This model, which is quite articulated, is well suited for the description of film material, stressing in particular the different physical embodiments (manifestations) of the audiovisual content, making it more purpose-‐oriented for use in audiovisual and film archives (asset management and preservation).

3 The EN 15907 standard9

The EN 15907, “Film Identification – Enhancing interoperability of metadata – Element sets and structures” became a European Standard in July 2010, and it specifies a set of metadata for the description of cinematographic works, as well as a terminology for use by parties wishing to exchange such descriptive metadata. It also defines some basic entities and relationships useful for defining data models as well as for structuring hierarchically ordered and serialised representations of metadata about cinematographic works including their variants, manifestations, and items.

The main objective of this standard is to define the metadata essential for facilitating data exchange between film databases and for allowing consistent identification of films.

This metadata model is based on the FRBR structure and it represents an evolution of the EFG data model described above. Core members10 of the CEN Technical Committee 372, who prepared the standard, were also in the EFG group that issued the EFG metadata schema.

The model defines a set of 5 primary entities: Cinematographic Work, Variant, Manifestation, Item, Content; and 2 contextual entities: Agent and Event. Each of these entities can be related to the others through different kind of relationships, following the diagram below:

9 http://filmstandards.org/fsc/index.php/EN_15907 10 Namely Detlev Balzer (DIF) and Marco Rendina (Istituto Luce Cinecittà)


8

Entity-‐Relationship diagram of EN 15907

As for the EFG metadata model, the EN 15907 standard is aimed mainly at film archives, film museums, cinematheques and any other cultural organisations with databases about film content, and it has been defined to facilitate access to filmographic metadata and to allow their interoperability.

Despite the well-‐articulated structure, the model has not been extensively tested with television content, and its actual implementation is complicated by the fact that this standard specifies only a metadata model and not its formal representation. To this date, no complete XML or RDF representations of this model exist.

4 EBUCore

The European Broadcasting Union (EBU) published EBUCore11 for the first time in 2000. It was originally a set of definitions for audio archives, applied to the Dublin Core. This first version did not have a schema as it strictly adhered to the Dublin Core elements set. In 2005, an EBU user group of archivists decided to review the requirements for metadata supporting query, access and exchange of archive content online. The requirements were identified devoid of any reference to technology or a particular set of metadata. The result was a core set of metadata fitting well what Dublin Core had defined, but also the need for more structured technical metadata as well as the possibility to “customise” the Dublin Core set. The new EBUCore schema and its specification have been released in 2008.

Since then, EBUCore followed this evolution to become what it is today: the Dublin Core for media, a framework that can be used to describe just about any media content (incl. audio, video, images, documents). It has been designed as an extension of Dublin Core, which is imported as the base structure of the EBUCore schema.

11 http://tech.ebu.ch/docs/tech/tech3293v1_4.pdf


9

Customisation was also made possible, allowing for the possibility to add “type” attributes to the defined properties. For example, it is possible to specify an arbitrary number of types for the “title” or “description” properties, as each implementer may use different names/kinds of titles or description, such as “original title”, “English title”, “summary”, “extended description”, etc. But the most significant effort was put on the two Dublin Core elements considered as the most sensitive, “dc:type” and “dc:format”:

• “dc:type” is often interpreted in different ways and EBUCore restricts its use to the definition of the type of object being described (e.g. a program or a clip or a series), the genre of the object content (e.g. news, or comedy or sports) and the target audience of the content.

• In EBUCore, “dc:format” gives structured technical information about the content (does it contain audio, video? How is it encoded? Does it contains subtitling/captioning, signing? What is the size of the file, the type of container? Etc.).

Another peculiar characteristic of EBUCore is that it permits the description of content parts/segments/fragments at a very low level of granularity, either to provide an editorial analysis of the content (e.g. tracks of a record of performances in a show with appropriate contextual information on each performer), or to generate timelines of dynamic technical parameters.

EBUCore has been represented in XML, JSON, SMPTE-‐KLV and RDF/OWL (Resource Description Framework/Web Ontology Language) as ontology. The EBUCore ontology complements the EBU's Class Conceptual Data Model (CCDM) modelling broadcast, from ingestion to the delivery of content to the end user. It responds to the need for more effective querying and it also paves the way for effective metadata enrichment using Linked Open Data (LOD). The work on EBUCore and EBU's CCDM also greatly influenced the development of W3C Ontology for Media Resources12, which based its work on the EBU data model. MA-‐ONT, as it is known, is a subset of the EBUCore ontology and the RDF/OWL representation rules are common to both.

The EBUCore schema has been adopted by several broadcasters in Europe and it has been used in different European initiatives, like the UK’s Digital Production Partnership (DPP), the Framework for Interoperable Media Services13 (FIMS) and the EU co-‐funded Best Practice Network EUscreen, the predecessor of EUscreenXL. The EBUCore model has been used also to propose extensions to the schema.org ontology (a project from Google, Yahoo and Bing) in order to describe TV and radio programmes and associated services and schedules. This work has been done in close cooperation between BBC and EBU.

EBUCore has been registered by SMPTE14 has EBU metadata for public use. This now allows embedding EBUCore metadata in MXF files.

The EBUCore is developed and maintained by the EBU metadata community, which is open to all metadata developers including non-‐EBU members. The main advantage of using a standard like EBUCore is that the community of developers and implementers benefit from all new developments around the xml schema and the RDF/OWL ontology.

The simplicity and the expressivity of the model together with the above mentioned points, makes EBUCore a very good candidate as model for the metadata schema for the Pan-‐European aggregator of audiovisual

12 http://www.w3.org/TR/mediaont-‐10/ 13 http://www.fims.tv 14 http://www.smpte.org


10

content. It is general enough to be adapted also for the description of film and, more in general, audiovisual content at large.

5 BBC News Storyline Ontology

The News Storyline Ontology is a generic model for describing and organising the stories news organisations tell. The ontology is intended to be flexible to support any given news or media publisher's approach to handling news stories. At the heart of the ontology, is the concept of Storyline. As a nuance of the English language the word 'story' has multiple meanings. In news organisations, a story can be an individual piece of content, such as an article or news report. It can also be the editorial view on events occurring in the world.15

The journalist pulls together information, facts, opinion, quotes, and data to explain the significance of world events and their context to create a narrative. The event is an award being received; the story is the triumph over adversity and personal tragedy of the victor leading up to receiving the reward (and the inevitable fall from grace due to drugs and sexual peccadillos). Or, the event is a bombing outside a building; the story is an escalating civil war or a gas mains fault due to cost cutting. To avoid this confusion, the term Storyline has been used to remove the ambiguity between the piece of creative work (the written article) and the editorial perspective on events.

15 This information is taken from http://www.bbc.co.uk/ontologies/storyline/2013-‐05-‐01.html


11

A Storyline in its most basic form can be an individual, but typically would consist of a richer collection of storyline components. These components exist in slots that can be fully ordered using an index property, ordered temporally, or arranged in a graph to possibly express parallel running developments.

Storyline components can be indisputable real world events, or other storylines (chapters, sub-‐plots, updates, news developments etc). Storylines can be associated with Topics in some knowledge domain (eg people, places, organisations). As news stories are typically of a subjective nature (one news publisher's interpretation of any given news story may be different from another's), Storylines can be attributed to some agent to provide this provenance. The BBC News Storyline is of relevance for future developments in EUscreenXL, as EUscreenXL aims to publish metadata in ways that support workflows within broadcasters. This will further promote EUscreenXL data in TV production contexts.

6 The EUscreen metadata schema

EUscreen16 was a Best Practice Network co-‐funded by the EC under the eContentplus program, with the aim to aggregate television and audiovisual content for Europeana and promote the use of television content to explore Europe's rich and diverse cultural history. Together with EFG, EUscreen is one of the main audiovisual content aggregators for Europeana.

The EUscreen metadata model is based on the EBUCore metadata schema (described in the previous chapter), and it consists of 39 elements, 18 of which are mandatory. Here is the list of the mandatory elements:

Identifier Material type Item type Title Title in English Summary Summary in English Thesaurus terms Genre Topic Broadcast date Production year Item duration IPR restrictions Rights terms and conditions Provider Original identifier Video file name

To integrate the model there is also a list of optional elements:

16 http://www.euscreen.eu/


12

Series Title Series Title in English Clip title Extended description Information Contributor First Broadcast channel Country of production Language used Original language Subtitle language Item colour Item sound Aspect ratio Local keywords Geographical Coverage Metadata language Original URI Relation Relation type

The EUscreen model is a simple, flat model that can effectively describe audiovisual and television content. In the EUscreen framework it has also been used to describe related material like photographs, documents and radio broadcasts. It has been mapped to EDM and EBUCore and it has been also represented in RDF using the EBUCore ontology, allowing for the publication of the EUscreen metadata as linked data17. But its simplicity is also its limitation, as this model is not completely suited for describing audiovisual objects in a hierarchical relation, such as serial programmes, only allowing for a flat representation of the audiovisual objects that it describes.

17 http://lod.euscreen.eu/


13

B EUSCREENXL METADATA SURVEY

1 Introduction

In the EUscreenXL project, within the framework of Work Package 2 (Aggregating & Enriching Content), two online questionnaires have been circulated to all content providers in the early stages of the project (April 2013).

The objective of these questionnaires was to gather information on the content to be provided by all the partners to the EUscreenXL portal and to Europeana, and to analyse the situation regarding their local information infrastructures and practices (metadata standards, classification methods, cataloguing practices, etc.). The results of these questionnaires served also as a basis for the discussions during the regional workshops, organised with all the content providers in May/June 2013.

In the following paragraphs we will report some of the most significant outcomes regarding the metadata models in use, the classification schemes adopted, and its implications for the assessment of the EUscreen metadata model, as defined and used in the previous project, EUscreen. The results of the content surveys will be a subject of the Deliverable 2.2 “Publication of content selection policy for enriched content”.

2 Metadata survey findings

As mentioned above, the questionnaires were investigating several aspects from the content details and provision status, IPR conditions and metadata and classifications schemes. We will report below the results of the four main metadata related questions that we gathered, based on the submission by 20 providers:

What metadata standards do you use for cataloguing your audiovisual material in your institution?

EBUCore 2 Dublin core 1 MARC21/MARCXML 0 EN 15907 0 In-‐house schema 11 Other… 6


14

From the answer above is clear that the 55% of content providers are using an in-‐house proprietary metadata schema. Analysing the specification of the six answers related to “Others”, we notice that 4 out of 6 replies state that the metadata schema in use is “largely based” on Dublin Core, one reply states that EAD metadata standard is used and another one state that a combination of EBUCore and Dublin Core is used.

The conclusion is that the majority of content providers are not using one standard metadata model, but that amongst the most used standard ones is Dublin Core (or DC based), followed by EBUCore.

Please indicate which of the following metadata elements for moving image (film and/or television) are routinely provided by the cataloguing system you use in your own institution.

Elements Response Percent

Response Count

Title 100,0% 20 Series Title 95,0% 19 Summary/Description 90,0% 18 Production Year 90,0% 18 Broadcast Date 90,0% 18 Item Duration 90,0% 18 Publisher/Broadcaster 85,0% 17 Material type (video, audio, etc.) 80,0% 16 Contributor 80,0% 16 Keywords 80,0% 16 Provider 75,0% 15 Item Color 75,0% 15 Aspect Ratio 75,0% 15 Genre (e.g. news, drama, etc.) 70,0% 14 Item Sound 70,0% 14 Country of Production 65,0% 13 Original Identifier 65,0% 13 Subject Thesaurus 60,0% 12 Geographical Thesaurus 55,0% 11 IPR Restrictions 55,0% 11 Rights, terms and conditions 55,0% 11 Language Used 50,0% 10 Original Language 45,0% 9 Clip Title 40,0% 8 Filename 40,0% 8 Additional information 35,0% 7 Item Type (e.g. whole, extract) 35,0% 7 Subtitle Language 30,0% 6 Topic 25,0% 5 Relation (e.g. linking one item to another)

25,0% 5

URI 25,0% 5 Metadata Language 20,0% 4 Other 20,0% 4


15

The elements listed above are taken from the EUscreen metadata schema. It does not come as a surprise that the main Dublin Core descriptive elements (title, description, type, creator, etc.) are almost always present in the cataloguing systems of the EUscreenXL partners. Apart from the main DC elements, another element is worth mentioning, as it is present 95% of the time: the “series title”. This indicates that in the cataloguing systems of our content providers information on series and serial audiovisual content is considered to be essential information. This finding strongly indicates the need to allow the description of serial content (series record and its episodes) in the EUscreenXL framework.

Does your institution use controlled vocabularies/thesauri for cataloguing audiovisual material?

If YES, please indicate which controlled vocabularies/lists/authority files are used for the following.

Options Library of Congress

GeoNames IPTC VIAF IMDb EBUCore Propietary Other

Geographic names 0 0 0 0 0 1 7 2

Subject thesaurus

0 0 0 0 0 1 9 2

Historical/time period 0 0 0 0 0 0 2 1

Events 0 0 0 0 0 0 1 1 Genre 0 0 0 0 0 1 8 1 Person names 0 0 0 0 1 0 9 1 Roles (producer, writer, etc.)

0 0 0 0 1 0 8 1

Institutions 0 0 0 0 0 0 7 1


16

13 out of 20 content providers are using controlled vocabularies, especially for subject terms, person names, geographic names and genre. However, in most of the cases the controlled vocabularies/thesauri are developed in-‐house, with the exception of the IMDb authority file for person names and roles and the EBUCore vocabularies for genre, subjects and geographic names.


17

C THE EUSCREENXL METADATA SCHEMA

1 Introduction

The metadata model defined for the EUscreenXL project is the result of the analysis of all the elements reported in the previous chapters (from the metadata schema of related initiatives, to the input gathered from the internal questionnaires).

Starting from the assumption that in EUscreenXL we do not want to define “yet another metadata standard”, but rather – based on the EUscreen experience – improve what has been used effectively in that project, the main conclusion that we can draw from the above mentioned analysis is to embrace as a reference, also for the Pan-‐European aggregator of audiovisual content, the EBUCore schema, for the simplicity, flexibility and expressivity of its model, for its availability in multiple representations (XML, RDF/OWL, JSON e SMPTE-‐KLV) and because it is maintained by a large community and by the EBU, which is also a member of the EUscreenXL consortium.

The set of metadata elements used to describe the EUscreenXL Core Collection18 will be a subset of the EBUCore elements and for obvious reasons of backward compatibility, it will include almost all the elements that were used in the previous EUscreen project. The main novelty in the EUscreenXL information architecture is the introduction of a record type for the description of series and/or collection content (for a complete definition of series and collection see section B.3 of the “Metadata and Content Handbook”).

Series and collections will be a central element in the content selection policy of EUscreenXL, adding a new facet through which users are able to browse audiovisual content on the EUscreenXL portal and allowing content providers to easily select material that can span over a period of years or decades to demonstrate historical changes and to allow comparative studies.

When applicable, content providers import or insert in the MINT backend tool series records that will be linked with related item/clip records describing selected episodes (or part of them). The relation between the series record and its episodes will be expressed by the relation type 'hasEpisodes' that will automatically link the unique identifier of the series records to the identifiers of the item/clip records of related episodes (or part of them).

For an alphabetically ordered detailed definition of the EUscreenXL metadata elements please refer to Section D: Reference below. A full list of all controlled vocabularies and reference data is available in Section E: List of controlled vocabularies.

18 see the EUscreenXL “Metadata and Content Handbook” for more information on the Core Collection and related definitions.


18

Mandatory

2 Metadata elements for series/collection record type

The following are the list of mandatory and optional elements that will be used to describe a series or a collection.

Mandatory: Series/collection title Series/collection title in English Alternative series/collection title (if applicable) Summary Summary in English Provider Publisher/Broadcaster Broadcast date (mandatory if broadcast) Production year (mandatory if non-‐broadcast) Material type Record type Relation type Relation identifier Identifier

Optional: First broadcast channel Extended description Information Last broadcast date (if known/applicable) Last production year (if known/applicable) Original language Language used Local keywords Country of production Contributor Metadata language Landing page URL Filename


19

3 Metadata elements for item/clip record type

The following are the list of mandatory and optional elements that will be used to describe an item (i.e. whole episode/programme/film/document/still) or a clip (extract/part) of any generic audiovisual entry (video, audio, document or image).

4 Conclusions

In defining the EUscreenXL metadata schema we may not have reinvented the wheel, but we tried to perfect it. The decision to build the schema on EBUCore and on the EUscreen metadata model ensures backward compatibility for the 40.000 items of EUscreen audiovisual content. At the same time the introduction of a record type for the series/collection adds a new level of description improving the original EUscreen schema.

Mandatory: Title Title in English Series/collection title (if applicable) Series/collection title in English (if applicable) Series/season number (if applicable) Episode number (if applicable) Summary Summary in English Provider Publisher/Broadcaster Broadcast date (mandatory if broadcast) Production year (mandatory if non broadcast) IPR restrictions Rights terms and conditions Genre Topic Thesaurus terms Geographical coverage Material type Record type Item duration Language used Identifier Original identifier Filename

Optional: Clip title Extended description Information First broadcast channel Country of production Original language Local keywords Contributor Item colour Item sound Aspect ratio Subtitle language Metadata language Relation type Relation Digital item URL Landing page URL


20

The newly defined metadata model is flexible enough to be adapted and used for the description of heterogeneous audiovisual content, satisfying the requirements of a Pan-‐European audiovisual aggregator, and having used EBUCore as a base enables the representation of the EUscreenXL metadata model in RDF/OWL, through the EBUCore ontology, allowing the publication of the EUscreenXL metadata as Linked Open Data and maximizing in this way data diffusion and re-‐use.


21

D REFERENCE

The following is an alphabetical list of elements (mandatory and optional), which form the EUscreenXL Common Metadata Scheme based on the EBUcore schema. Each field will include an explanation of the information to be contained for both item/clip and series records. In most instances examples are provided. An important outcome presented in this reference list is the mapping of the EUscreenXL elements towards EDM (the Europeana Data Model). EUscreenXL is going to deliver its aggregated content to the Europeana portal and an accurate semantic mapping between the information structure of EUscreenXL and the one of Europeana is crucial to valorise the audiovisual content that the project will provide. The mapping to EDM is still in a draft form and will be finalised together with the Europeana Foundation by the end of 2013. A full list of all controlled vocabularies and reference data will be made available on euscreen.eu. Name Alternative series/collection title

Cardinality Unique

Definition An alternative name given to the series/collection in the provider language. The alternative titles represent the different names under which a series/collection is known.

Format Free text

EDM mapping ProvidedCHO/dcterms:alternative

EBUCore mapping /ebucore:coreMetadataType/ebucore:alternativeTitle/dc:title /ebucore:coreMetadataType/ebucore:type/ebucore:objectType/@typeLabel = "Series" or "Season" or "Collection"

Reference data n.a.

Examples Title: ‘Ritorno alla mia valle’ Name Aspect ratio

Cardinality Unique

Definition Aspect ratio of the item

Format Controlled vocabulary

EDM mapping WebResource /dcterms:format

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:videoFormat/ebucore:aspectRatio and /ebucore:coreMetadataType/ebucore:format/ ebucore:videoFormat/ebucore:aspectRatio @typeLabel or /ebucore:coreMetadataType/ebucore:format/ ebucore:videoFormat/ebucore:aspectRatio @typeDefinition (ratio height:width)

Reference data See Section E.

Examples Aspect ratio: '16:9'


22

Name Broadcast date

Cardinality Unique

Definition The first known date the item was broadcast/transmitted or the start date of the broadcasting of a series

Format dd/mm/yyyy (if only the year is known please use the “production year”, if year and month are known set the day to “01”)

EDM mapping ProvidedCHO/dcterms:issued

EBUCore mapping /ebucore:coreMetadataType/ebucore:publicationHistory/ ebucore:publicationEvent/ebucore:publicationDate and /ebucore:coreMetadataType/ebucore:publicationHistory/ ebucore:publicationEvent/@firstShowing="True"

Reference data n.a.

Examples Broadcast date: 20/11/1975 -‐ should be converted from display to storage using xml date format: 1975-‐11-‐20

Name Clip title

Cardinality Unique

Definition The title assigned to a clip extracted from a programme/episode preferably in English or alternatively in the provider language.

Format Free text

EDM mapping ProvidedCHO/dcterms:alternative

EBUCore mapping /ebucore:coreMetadataType/ebucore:title/dc:title /ebucore:coreMetadataType/ebucore:type/ebucore:object@typeLabel=”clip”

Reference data n.a.

Examples Clip Title: ‘People in the streets during Christmas holidays’ Clip Title: ‘Il Papa apre la Porta Santa’

Name Contributor

Cardinality Multiple

Definition A person or institution responsible for the realisation of the artistic or intellectual content of the item.

Format Free text, but see the examples section below for style recommendations.

EDM mapping ProvidedCHO/dc:contributor (as literal)

EBUCore mapping /ebucore:coreMetadataType/ebucore:contributor/ebucore:contactDetails/ebucore:name

Reference data n.a.


23

Examples Contributor: 'Peter Arnett (interviewer)' Contributor: 'Loach, Ken'

Name Country of production


Definition The country where the item or the series was produced.

Format ISO country codes (ISO 3166-‐1)

EDM mapping ProvidedCHO/dc:description

EBUCore mapping /ebucore:coreMetadataType/ebucore:description/dc:description and /ebucore:coreMetadataType/ebucore:description/dc:description@xml:lang=”en” /ebucore:coreMetadataType/ebucore:description @typeLabel = “Country of Production”

Reference data http://www.iso.ch/iso/en/prods-‐services/iso3166ma/02iso-‐3166-‐code-‐lists/list-‐en1.html

Examples Country of production: “BE” Country of production: “GR”

Name Digital item URL

Cardinality Unique

Definition A unique internet address to access a digital representation of the item on the content provider site. This element will be used primarily to allow Europeana users to access directly the item digital file.

Format Free text

EDM mapping ProvidedCHO/edm:isShownBy WebResource/rdf:about

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:locator

Reference data URL: Unique Resource Locator: http://tools.ietf.org/html/rfc3986

Examples Item URL: 'http://www.archivioluce.com/archivio/jsp/schede/videoPlayer.jsp?tipologia=&id=&physDoc=26331&db=cinematograficoCINEGIORNALI&findIt=false&section=/'

Name Episode number

Cardinality Unique

Definition The progressive number of the episode to which the item refers to

Format Free text



24

EBUCore mapping /ebucore:isEpisodeOf/@runningOrderNumber /ebucore:isEpisodeOf/@totalNumberOfGroupMembers /ebucore:isEpisodeOf/@orderedGroupFlag and /ebucore:isEpisodeOf/ebucore:relationIdentifier (pointing to a series ID) or /ebucore:isEpisodeOf/ebucore:relationLink (pointing to a series object) or /ebucore:isEpisodeOf/dc:relation (e.g. providing a series name) or /ebucore:coreMetadataType/ebucore:alternativeTitle/dc:title /ebucore:coreMetadataType/ebucore:type/ebucore:objectType/@typeLabel ="Episode Number"

Reference data n.a.

Examples Episode number: '18'

Name Extended description

Cardinality Unique

Definition Detailed description of item content that may include: individual programme description, shot lists or transcriptions. It could be in provider language or in English.

Format Free text


EBUCore mapping /ebucore:coreMetadataType/ebucore:description/dc:description and /ebucore:coreMetadataType/ebucore:description @typeLabel = “extended description”

Reference data n.a.

Examples Extended description: ‘Programme réalisé par Emile Lanc, avec Lisette et les marionnettes du Théâtre de l’Enfance / Photo Delraux.’

Name Filename

Cardinality Unique

Definition The file name of the associated digital item (it could be the same as the “original identifier”, if this is the naming convention internally used); or for a series/collection record the filename of a thumbnail/image that is associated to the series/collection, if available.

Format Free text

EDM mapping n.a.

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:filename

Reference data n.a.


25

Examples Filename: FTA001019290_006_con.png Filename: 0185_20-‐02-‐1990_NEWS_-‐_BERLIN_WALL.mp4

Name First broadcast channel

Cardinality Unique

Definition The channel that originally broadcast the item.

Format Free text

EDM mapping WebResource/edm:publisher

EBUCore mapping /ebucore:coreMetadataType/ebucore:publicationHistory/ ebucore:publicationEvent/ebucore:publicationChannel

Reference data n.a.

Examples First broadcast channel: 'Canal 33' Name Genre


Definition Information about the genre of the resource (as defined in EUscreen)


EDM mapping ProvidedCHO/dc:type@xml:lang=”en”

EBUCore mapping /ebucore:coreMetadataType/ebucore:type/ebucore:genre


Examples Genre: ‘News’ Genre: ‘Drama/Fiction’

Name Geographical coverage


Definition The spatial topic of the item.


EDM mapping ProvidedCHO/dcterms:spatial@xml:lang=”en”

EBUCore mapping /ebucore:coreMetadataType/ebucore:coverage/ebucore:spatial /ebucore:location/ebucore:name @typeLabel (e.g. country or city) and /ebucore:coreMetadataType/ebucore:coverage/ebucore:spatial/ebucore:location /ebucore:name

Reference data Geographical thesaurus


26

Examples Geographical coverage: 'Italy' Geographical coverage: 'Barcelona, Spain'

Name Identifier

Cardinality Unique

Definition A unique, unambiguous reference to the item within the EUscreenXL repository (automatically assigned by the ingestion system)

Format Free text

EDM mapping ProvidedCHO/dc:identifier

EBUCore mapping /ebucore:coreMetadataType/ebucore:identifier/dc:identifier and /ebucore:coreMetadataType/ebucore:identifier @typeLabel = “main” /ebucore:coreMetadataType/ebucore:identifier @formatLabel = “EUscreen”

Reference data n.a.

Examples Identifier: 'EUS_TVC002745' Name Information

Cardinality Unique

Definition Additional information about the whole programme or the series (any further information that contextualises the item – such as transmission history, awards, production notes etc).

Format Free text


EBUCore mapping /ebucore:coreMetadataType/ebucore:description/dc:description and /ebucore:coreMetadataType/ebucore:description @typeLabel = 'additional information'

Reference data n.a.

Examples 'Panorama is a BBC current affairs programme, first broadcast in 1953, and is the longest-‐running current affairs programme in the world. It has been presented by many well known BBC presenters, including Richard Dimbleby, Robin Day and David Dimbleby.'

Name IPR restrictions

Cardinality Unique

Definition Statement about the f IPR status of the item. The value of this element corresponds to one of the values listed in the Europeana rights statement, namely: Rights Reserved -‐ Free Access Rights Reserved -‐ Paid Access Rights Reserved -‐ Restricted Access Unknown


27

Creative Commons -‐ Zero (CC0) Creative Commons -‐ Attribution (BY) Creative Commons -‐ Attribution, Share Alike (BY-‐SA) Creative Commons -‐ Attribution, No derivatives (BY-‐ND) Creative Commons -‐ Attribution, Non-‐commercial (BY-‐NC) Creative Commons -‐ Attribution, Non-‐commercial, Share Alike (BY-‐NC-‐SA) Creative Commons -‐ Attribution, Non-‐commercial, No derivatives (BY-‐NC-‐ND)


EDM mapping Aggregation/edm:rights WebResource/edm:rights

EBUCore mapping /ebucore:coreMetadataType/ebucore:rights/dc:rights or /ebucore:coreMetadataType/ebucore:rights/dcebucore:rightsLink and /ebucore:coreMetadataType/ebucore:description @typeLabel = 'IPR Restrictions'


Examples IPR restrictions: 'Rights Reserved -‐ Free Access' Name Item colour

Cardinality Unique

Definition Information about colour reproduction of the item


EDM mapping WebResource/dcterms:format

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:videoFormat/ebucore: videotechnicalAttributeString /ebucore:coreMetadataType/ebucore:format/ebucore:videoFormat@typeLabel = 'colour type'


Examples Item colour: 'Black & White' Name Item duration

Cardinality Unique

Definition Time-‐based duration (extent) of the item

Format hh:mm:ss

EDM mapping /dcterms:extent

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:duration/ebucorenormalPlayTime

Reference data n.a.


28

Examples Item duration: ‘01:13:45’ -‐> ebucore/xml: PT1H13M45S Name Item sound

Cardinality Unique

Definition Information about the audio reproduction of the item


EDM mapping WebResource/dcterms:format

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:audioFormat/ audiotechnicalAttributeString /ebucore:coreMetadataType/ebucore:format/ebucore:audioFormat@typeLabel ='audio type'


Examples Item sound: 'mute' Name Landing page URL

Cardinality Unique

Definition A unique internet address to access the item (or the series) in its original information context on the content provider site. This element will be used primarily to allow Europeana users to access directly the original metadata record in the source archive.

Format Free text

EDM mapping /edm:isShownAt

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/ebucore:Locator and /ebucore:coreMetadataType/ebucore:format/ebucore:Locator/@typeLabel="Landing Page"

Reference data URL: Unique Resource Locator: http://tools.ietf.org/html/rfc3986

Examples Landing page URL: 'http://www.archivioluce.com/archivio/jsp/schede/schedaCine.jsp?db=cinematograficoCINEGIORNALI&section=/&physDoc=13788' or ‘http://www.euscreen.eu/play.jsp?id=EUS_07C6ADE94ABF4486BD8A2B1EF4F3C478’

Name Language used


Definition The main language (also dubbed language or voice over) of the item.

Format Controlled vocabulary (ISO 639-‐1 or ISO 639-‐2)


29

EDM mapping ProvidedCHO/dc:language

EBUCore mapping /ebucore:coreMetadataType/ebucore:language/ebucore:languageCode /ebucore:ebuCoreMain/ebucore:coreMetadata/ebucore:language/dc:language and /ebucore:ebuCoreMain/ebucore:coreMetadata/ebucore:language@typeLabel (e.g. dubbing, voice over, subtitling or captioning)

Reference data http://www.ebu.ch/metadata/cs/web/ebu_Iso639_1LanguageCodeCS_p.xml.htm http://www.ebu.ch/metadata/cs/web/ebu_Iso639_2LanguageCodeCS_p.xml.htm

Examples Language used: 'FR' Name Last broadcast date

Cardinality Unique

Definition The last date of the broadcasting of the original series (if known/applicable).

Format dd/mm/yyyy (if year and month are known set the day to “01”)

EDM mapping ProvidedCHO/dcterms:issued

EBUCore mapping /ebucore:coreMetadataType/ebucore:publicationHistory/ ebucore:firstTransmissionDateTime and /ebucore:coreMetadataType/ebucore:publicationHistory/ ebucore:publicationEvent/@lastShowing="True"

Reference data n.a.

Examples Last Broadcast date: 15/04/1979 Name Last production year

Cardinality Unique

Definition The last year the series/collection was created or produced (if known/applicable).

Format YYYY

EDM mapping ProvidedCHO/dc:date

EBUCore mapping /ebucore:coreMetadataType/ebucore:date/ebucore:alternative and /ebucore:coreMetadataType/ebucore:date/ebucore:alternative/@typeLabel="last production date" /ebucore:coreMetadataType/ebucore:type/ebucore:objectType/@typeLabel="Series" or "Season" or "Collection"

Reference data n.a.

Examples Last production year: '1982'


30

Name Local keywords


Definition Keywords used internally by the content provider for classifying the intellectual content of the item. Keywords are usually expressed in the local language of the content provider. Important note: use the field “Geographical Coverage” for names of places (if they are normalised), and the field “Contributor” for names of persons responsible for the realisation of the described item.

Format Free text

EDM mapping ProvidedCHO/dc:subject

EBUCore mapping /ebucore:coreMetadataType/ebucore:subject/dc:subject and /ebucore:coreMetadataType/ebucore:subject @typeLabel = 'keywords'

Reference data n.a.

Examples Local keywords: ‘Piana del Fucino | Ingegneria idraulica | industria energetica | agricoltura | industria alimentare | allevamento di bovini | fiere ed esposizioni’

Name Material type

Cardinality Unique

Definition The nature or type of the item.

Format Controlled vocabulary (VIDEO|SOUND|IMAGE|TEXT|3D)

EDM mapping ProvidedCHO/dc:type

EBUCore mapping /ebucore:coreMetadataType/ebucore:format/dc:format


Examples Material Type: 'VIDEO’; Material Type: 'IMAGE'

Name Metadata language

Cardinality Unique

Definition The language in which the metadata of the item or series/collection is written.


EDM mapping ProvidedCHO/dc:language (also provided through lang tags)

EBUCore mapping /ebucore:coreMetadataType/ebucore:language/ebucore:languageCode and /ebucore:coreMetadataType/ebucore:language@typeLabel = 'metadata language' or /ebucore:ebucoreMain/@xml:lang



31

Examples Metadata language: 'DE' Name Original identifier

Cardinality Unique

Definition A unique, unambiguous reference to the item within the source archive (content provider internal identifier)

Format Free text

EDM mapping ProvidedCHO/dc:identifier WebResource/rdf:about

EBUCore mapping /ebucore:coreMetadataType/ebucore:identifier/dc:identifier and /ebucore:coreMetadataType/ebucore:identifier @typeLabel = “Original”

Reference data n.a.

Examples Identifier: 'D0002745' Name Original language


Definition The original language of the item or series, if different from the language used



EBUCore mapping /ebucore:coreMetadataType/ebucore:language/dc:language and /ebucore:coreMetadataType/ebucore:language@typeLabel = 'Original'


Examples Original language: 'IT', 'FR' Name Production year

Cardinality Unique

Definition The year the item or the series was created (produced), for the series is the first production year.

Format YYYY

EDM mapping ProvidedCHO/dc:created

EBUCore mapping /ebucore:coreMetadataType/ebucore:date/ebucore:created

Reference data n.a.

Examples Production year: '1982'


32

Name Provider

Cardinality Unique

Definition The name of the content provider for the given item. It could be directly assigned in the mapping stage on the MINT tool.


EDM mapping ProvidedCHO/edm:dataProvider

EBUCore mapping /ebucore:ebuCoreMain/ebucore:coreMetadata/ebucore:creator/ebucore: contactDetails/ebucore:name and ebucore:role@typeLabel= “Publisher” or /ebucore:ebuCoreMain/ebucore:metadataProvider/ebucore:contactDetails /ebucore:name


Examples Provider: 'Cinecittà Luce' Name Publisher/Broadcaster

Cardinality Unique

Definition The name of the entity primarily responsible for making the item available to the public (through broadcasting, publishing and other modes of distribution). It could be the same as 'Provider'.

Format Free text

EDM mapping ProvidedCHO/dc:publisher

EBUCore mapping /ebucore:ebuCoreMain/ebucore:coreMetadata/ebucore:creator/ebucore: contactDetails/ebucore:name ebucore:role@typeLabel=”Broadcaster” or "Publisher" or "Publisher/Broadcaster"

Reference data n.a.

Examples Publisher/Broadcaster: ‘Československa televize’ Name Record type

Cardinality Unique

Definition Information about the type of record, i.e. is it a series/collection entry, a whole programme/film, or an extract

Format Controlled vocabulary (series/collection | item | clip)

EDM mapping ProvidedCHO/dc:type


33

EBUCore mapping /ebucore:coreMetadataType/ebucore:type/objectType/@typeLabel

Reference data n.a.

Examples Record type: 'item' Record type: 'clip' Record type: 'series/collection'

Name Relation identifier


Definition Reference to an item to which the current item is related at production level. (See Relation Type for the kinds of relations that this specifies.) This reference of the related item can be the 'Identifier' (EUscreen unique identifier).

Format Free text

EDM mapping ProvidedCHO/dc:isRelatedTo (work type is "item" or "series" or "Season" or "Collection") ProvidedCHO/ebucore:isEpisodeOf (work type is "item") ProvidedCHO/ebucore:hasEpisode (work type is "series" or "Season" or "Collection") ProvidedCHO/dc:isPartOf (work type is "item") ProvidedCHO/dc:hasPart (work type is "series" or "Season" or "Collection") ProvidedCHO/dc:isVersionOf ProvidedCHO/dc:hasVersion ProvidedCHO/dc:isReferencedBy (work type is "item" or "series" or "Season" or "Collection") ProvidedCHO/dc:references (work type is "item" or "series" or "Season" or "Collection") WebResource /dc:isPartOf (work type is "item") WebResource /dc:hasPart (work type is "series" or "Season" or "Collection")

EBUCore mapping /ebucore:coreMetadataType/ebucore:relation/dc:relation /ebucore:coreMetadataType/ebucore:relation/ebucore:relationIdentifier and/or /ebucore:coreMetadataType/ebucore:relation/ebucore:relationLink or directly (without using "Relation type" below) isEpisodeOf/hasEpisode isRelatedTo isVersionOf/hasVersion isPartOf/hasPart isReferencedBy/references isSeasonOf/hasSeason with dc:relation, ebucore:relationIdentifier or ebucore:relationLink

Reference data n.a.

Examples Relation: 'EUS_TVR0126734'


34

Name Relation type


Definition To specify the type of relation to another item at production level. This will be one of the following: isEpisodeOf / hasEpisode isRelatedTo isVersionOf / hasVersion isPartOf / hasPart isReferencedBy / References


EDM mapping ProvidedCHO/dc:isRelatedTo (work type is "item" or "series" or "Season" or "Collection") ProvidedCHO/ebucore:isEpisodeOf (work type is "item") ProvidedCHO/ebucore:hasEpisode (work type is "series" or "Season" or "Collection") ProvidedCHO/dc:isPartOf (work type is "item") ProvidedCHO/dc:hasPart (work type is "series" or "Season" or "Collection") ProvidedCHO/dc:isVersionOf ProvidedCHO/dc:hasVersion ProvidedCHO/dc:isReferencedBy (work type is "item" or "series" or "Season" or "Collection") ProvidedCHO/dc:references (work type is "item" or "series" or "Season" or "Collection") WebResource /dc:isPartOf (work type is "item") WebResource /dc:hasPart (work type is "series" or "Season" or "Collection")

EBUCore mapping if direct mapping to equivalent EBUCore relations is not used: /ebucore:coreMetadataType/ebucore:relation/dc:relation /ebucore:coreMetadataType/ebucore:relation/ebucore:relationIdentifier and/or /ebucore:coreMetadataType/ebucore:relation/ebucore:relationLink and /ebucore:coreMetadataType/ebucore:relation@typeLabel and /ebucore:coreMetadataType/ebucore:relation@typeDefinition


Examples -‐ an item isEpisodeOf a series -‐ one item isVersionOf another in that it is a differently edited version, e.g. shorter, made for overseas distribution etc. -‐ a clip isPartOf a longer programme -‐ a news story references footage from another item

Name Rights terms and conditions

Cardinality Unique

Definition Information about rights held in and over the item

Format Free text

EDM mapping ProvidedCHO/dc:rights WebResource/dc:rights

EBUCore mapping /ebucore:coreMetadataType/ebucore:rights/dc:rights


35

and /ebucore:coreMetadataType/ebucore:rights/@typeLabel="Rights Terms and conditions"

Reference data n.a.

Examples Rights terms and conditions: 'Copyright limited to United Kingdom satellite broadcast delivery' Rights terms and conditions: ‘Copyright owner of this material is the Hellenic National Audiovisual Archive (HeNAA). For further inquiries please e-‐mail to [email protected]’ Rights terms and conditions: ‘Creative Commons: Attribution-‐NonCommercial (for details of Creative Commons license see http://creativecommons.org/licenses/)’

Name Series/collection title

Cardinality Unique

Definition The title of the series or collection in the content provider language.

Format Free text

EDM mapping /dcterms:isPartOf

EBUCore mapping /ebucore:coreMetadataType/ebucore:alternativeTitle/dc:title and /ebucore:coreMetadataType/ebucore:alternativeTitle @statusLabel = “Series”

Reference data n.a.

Examples Series Title: 'La Settimana Incom' Series Title: 'Panorama'

Name Series/collection title in English

Cardinality Unique

Definition The title of the series in English (it could be the same as the 'Series Title' if translation is inappropriate – for example: ‘Wochenschau’).

Format Free text

EDM mapping ProvidedCHO:dc:title (work item is "Series" or "Season" or "Collection" in dc:type)

EBUCore mapping /ebucore:coreMetadataType/ebucore:alternativeTitle/dc:title@xml:lang=”en” /ebucore:coreMetadataType/ebucore:alternativeTitle @statusLabel = “Series Title in English” or “Collection Title in English” and /ebucore:coreMetadataType/ebucore:type/ebucore:objectType/@typeLabel = “Series" or "Season or "Collection"

Reference data n.a.

Examples Series Title in English: 'La Settimana Incom' Series Title in English: 'Panorama'


36

Name Series/season number

Cardinality Unique

Definition The number of the series or season to which the item belongs.

Format Free text

EDM mapping ProvidedCHO:dc:title (work item is "Series" or "Season" or "Collection" in dc:type)

EBUCore mapping /ebucore:coreMetadataType/ebucore:alternativeTitle/dc:title@xml:lang=”en” /ebucore:coreMetadataType/ebucore:alternativeTitle @statusLabel = “Series Number” or "Season Number" and /ebucore:coreMetadataType/ebucore:type/ebucore:objectType/@typeLabel = “Series" or "Season or "Collection"

Reference data n.a.

Examples Series number: '4' Series number: 'VI'

Name Subtitle/captioning language


Definition The language of subtitles, if any.



EBUCore mapping /ebucore:coreMetadataType/ebucore:language/ebucore:languageCode and /ebucore:coreMetadataType/ebucore:language@typeLabel = 'subtitle' or "captioning"


Examples Language used: 'EN-‐UK' Name Summary

Cardinality Unique

Definition Short description of content in provider language to give an idea or sense of the item. This should be a maximum of two lines of text.

Format Free text


EBUCore mapping /ebucore:coreMetadataType/ebucore:description/dc:description and /ebucore:coreMetadataType/ebucore:description @typeLabel = “Summary”

Reference data n.a.


37

Examples Summary: ‘Amb motiu de la tancada d'uns 300 immigrants "sense papers" en una església de Barcelona, per demanar que l'administració doni resposta a les peticions de legalització’

Name Summary in English

Cardinality Unique

Definition Short summary of the content of the item in English language. This should be a maximum of two lines of text.

Format Free text

EDM mapping ProvidedCHO/dc:description@xml:lang=”en”

EBUCore mapping /ebucore:coreMetadataType/ebucore:description/dc:description and /ebucore:coreMetadataType/ebucore:description/dc:description@xml:lang=”en” /ebucore:coreMetadataType/ebucore:description @typeLabel = “English summary”

Reference data n.a.

Examples Summary in English: ‘300 illegal immigrants stage a sit-‐in at a Barcelona church to demand a response from the government to their requests for residence and work permits.’

Name Thesaurus terms


Definition Keywords used to classify the item. Values are taken from the IPTC thesaurus integrated in the EUscreen annotation tool.


EDM mapping /dc:subject@xml:lang=”en”

EBUCore mapping /ebucore:coreMetadataType/ebucore:subject/dc:subject and/or /ebucore:coreMetadataType/ebucore:subject/ebucore:subjectCode (termId) and /ebucore:coreMetadataType/ebucore:subject @typeLabel = 'IPTC subject'

Reference data IPTC thesaurus for subject terms

Examples Thesaurus terms: ‘Lifestyle & Leisure, Eating habits, Restaurants, Environmental Issues’ Name Title

Cardinality Unique

Definition A name given to the item in the provider language (the title of a specific episode (if in a series), the title of a programme, the subject of a photo, etc.). The title is the name by which an item is formally known and that everyone should use to refer to or search for that particular item. If the item has no proper title then an assigned title needs to be defined.


38

Format Free text

EDM mapping ProvidedCHO/dc:alternative +xml:lang

EBUCore mapping /ebucore:coreMetadataType/ebucore:title/dc:title /ebucore:coreMetadataType/ebucore:title/dc:title@xml:lang

Reference data n.a.

Examples Title: ‘ACHTER HET NIEUWS’ Title: ‘Ritorno alla mia valle’

Name Title in English

Cardinality Unique

Definition The title of the programme/episode/photo in English (it could be the same as the 'Title' in the provider language).

Format Free text

EDM mapping ProvidedCHO/dc:title@xml:lang=”en”

EBUCore mapping /ebucore:coreMetadataType/ebucore:title/dc:title /ebucore:coreMetadataType/ebucore:title/dc:title@xml:lang=”en”

Reference data n.a.

Examples Title in English: ‘Behind the news’ Title in English: ‘Back to my valley’

Name Topic

Cardinality Unique

Definition Information about the topic of the resource (defined in EUscreen). Please assign each item to ONE historical topic ONLY.


EDM mapping ProvidedCHO/dc:subject

EBUCore mapping /ebucore:coreMetadataType/ebucore:subject/dc:subject and /ebucore:coreMetadataType/ebucore:subject @typeLabel = 'topic'


Examples Topic: ‘Lifestyle and consumerism’ Topic: ‘Education’


39

E LIST OF CONTROLLED VOCABULARIES

The following is a list of all the accepted values for each of the controlled vocabularies defined in the EUscreenXL metadata schema. The name used for the labelling of the vocabularies is the name of the EUscreenXL elements as defined in Section D.

Aspect ratio 4:3 14:9 16:9

Genre News Drama/Fiction Entertainment and performing arts Factual Advertisements Interstitials and trailers Sport

IPR restriction Rights Reserved -‐ Free Access Rights Reserved -‐ Paid Access Rights Reserved -‐ Restricted Access Creative Commons -‐ Zero (CC0) Creative Commons -‐ Attribution (BY) Creative Commons -‐ Attribution, Share Alike (BY-‐SA) Creative Commons -‐ Attribution, No derivatives (BY-‐ND) Creative Commons -‐ Attribution, Non-‐commercial (BY-‐NC) Creative Commons -‐ Attribution, Non-‐commercial, Share Alike (BY-‐NC-‐SA) Creative Commons -‐ Attribution, Non-‐commercial, No derivatives (BY-‐NC-‐ND) Unknown

Item colour Mono Mute Stereo


40

Item sound Black & White Colour Mixed

Material type VIDEO SOUND IMAGE TEXT

Provider CT DR DW INA KB LCVA LUCE Memoriav NAVA NINA NISV ORF RTBF RTE RTP RTV SLO SASE TVC TVP TVR BUFVC

Record type SERIES/COLLECTION ITEM CLIP


41

Relation type isEpisodeOf hasEpisodes isVersionOf hasVersion isPartOf hasPart isReferencedBy References isRelatedTo

Topic Arts and culture Disasters Education Environment and Nature Health Lifestyle and consumerism The media National holidays, festivals, anniversaries and annual events Politics and Economics Religion and belief Transportation, science and technology Society and social issues Wars and conflict Work and production Special collections Being European History of European Television

D2.1 Publication of metadata schema for Pan-European Aggregator · 2017-04-25 · Project Title:...

Documents

Transcript of D2.1 Publication of metadata schema for Pan-European Aggregator · 2017-04-25 · Project Title:...