The following is the metadata schema to be used for metadata ingestion using the
ECLAP Metadata Ingestion Service. The whole process of content and metadata ingestion and upload is presented at the
following page.
The metadata schema is divided in four sections:
For the DC and DCTerms metadata it is indicated if the the (metadata) language (xml:lang attribute) is mandatory or optional or not necessary.
The general rule should be that language should be provided if has sense to have it translated in other languages.
When mapping a metadata element from your schema to the ECLAP one, use the more specific element:
-
if the metadata element you are mapping can be mapped to a performing art metadata (e.g. a professional) do it, it will be mapped to one of the generic DC/DCTerms metadata when providing metadata to europeana
-
if the metadata element you are mapping cannot be mapped to a performing arts metadata map it to one of the DCTerms or as a second chance to one of DC elements.
Performing arts metadata
In this section are reported the metadata specific for performing arts.
Note:
the first performance is the première, therefore its “place”, “city”, “country”, “date” might not correspond with the “place”, “city”, “country”, “date” in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held at:
Théâtre des Bouffes du Nord, Paris, France, 2000-11-20
But what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – at
The Globe Theatre, London, England, 2001-04-05
However we think both dates are important and should be reported (if known)
FirstPerformance Place
Name of the theatre or venue where the performance taken place for the first time.
Examples |
“Théâtre des Bouffes du Nord” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “place”, might not correspond with the place in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held at: “Théâtre des Bouffes du Nord”,
but what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – at “The Globe Theatre” |
Refinement of |
DCTerms.spatial? or EDM Place |
FirstPerformance City
Name of the city where the first performance taken place.
Examples |
“Paris” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “City”, might not correspond with the city in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held in: “Paris”, but what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – in “London” |
Refinement of |
DCTerms.spatial? or EDM Place |
FirstPerformance Country
Name of the country where the first performance taken place
Examples |
“France” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “Country”, might not correspond with the country in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held in: “France”, but what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – in “England”. |
Refinement of |
DCTerms.spatial? or EDM Place |
FirstPerformance Date
Date of the first performance
Examples |
“2000-11-20” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “date”, might not correspond with the date in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held in:
“2000-11-20”,
but what we are looking at on the ECLAP portal might be a video of the performance held months later, in “2001-04-05” |
Refinement of |
DCTerms.issued |
Performance Place
Name of the theatre or venue where the shown performance taken place
Examples |
“The Globe Theatre” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “place”, might not correspond with the place in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held at: “Théâtre des Bouffes du Nord”,
but what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – at “The Globe Theatre” |
Refinement of |
DCTerms.spatial? or EDM Place |
Performance City
Name of the city where the shown performance taken place.
Examples |
“London” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “City”, might not correspond with the city in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held in: “Paris”, but what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – in “London” |
Refinement of |
DCTerms.spatial? or EDM Place |
Performance Country
Name of the country where the shown performance taken place
Examples |
“England” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “Country”, might not correspond with the country in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held in: “France”, but what we are looking at on the ECLAP portal might be a video of the performance held months later - while the show was touring – in “England”. |
Refinement of |
DCTerms.spatial? or EDM Place |
Performance Date
Date of the shown performance
Examples |
“2001-04-05” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
the first performance is the première, therefore its “date”, might not correspond with the date in which the show was recorded.
For example: the opening night of “The Tragedy of Hamlet” directed by P. Brook might be held in:
“2000-11-20”,
but what we are looking at on the ECLAP portal might be a video of the performance held months later, in “2001-04-05” |
Refinement of |
DCTerms.issued |
PerformingArtsGroup
Name of the theatre or dance company or musical group (if present)
Examples |
“Momix” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
None |
Refinement of |
DC.creator |
PlotSummary
Summary of the plot
Examples |
“Prince Hamlet mourns both his father's death and his mother, Queen Gertrude's remarriage to Claudius. The ghost of Hamlet's father appears to him and tells him that Claudius has poisoned him: Hamlet swears revenge, etc.” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
None |
Refinement of |
DC.description |
Cast
Name/Names of a member of the cast.
Examples |
“Ryszard Cieślak, Rena Mirecka, Antoni Jahołkowski, Mieczysław Janowski, Maja Komorowska, Stanislaw Scierski” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
Use this element only if the Professional elements cannot be used, as the case of a cast written in a single text that cannot be easily split in all the different professional people |
Refinement of |
DC.contributor |
PerformersAndCrew
Name/Names of a performers and crew of a performance.
Examples |
... |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
Use this element only if the Professional elements cannot be used, as the case of a performers written in a single text that cannot be easily split in all the different professional people |
Refinement of |
DC.contributor |
Professional
A list of the people involved in the performance indicating which role each person had in the performance (eg. Actor, director, set designer etc.). It includes all the information listed in a playbill, such as the artistic cast of the show and the technicians, but also the names of the troupe which recorded the performance (eg. Cameraman, Director of Photography, etc.). Possible roles are:
-
Acrobat
-
Actor
-
Adaptator
-
Architect
-
Assistant_director
-
Casting
-
Choreographer
-
Clown
-
Composer
-
Concept_originator
-
Costume_designer
-
Critic
-
Dancer
-
Director
-
Dramaturge
-
Hairdresser
-
Light_designer
-
Make-up_artist
-
Marketing_manager
-
Mask_designer
-
Mime
-
Musician
-
Patron
-
Performer
-
Playwright
-
Producer
-
Puppet_designer
-
Scenographer
-
Seamster
-
Set_builder
-
Set_designer
-
Singer
-
Sound_designer
-
Stage_manager
-
Technician
-
Theatre_manager
-
Theoretician
-
Translator
-
Other
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
None |
Refinement of |
DC.contributor or DC.creator |
Object
Objects used in the performance, (i.e. Sets, Costumes, Props, Programs, Prints, Drawings,...)
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
|
Refinement of |
DC.description |
Genre
The genre in which the work can be categorized (i.e. Ballet, Butho, Commedia dell'Arte, Drama, Feast Flamenco, etc)
Examples |
“Tragedy” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
we will work on a shared vocabulary for this |
Refinement of |
DC.subject |
PerformingArtType
Type of performing art present in the content.
Examples |
“theatre” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
identified in WP4 as cinema, dance, music, theatre, performance art |
Refinement of |
DC.type |
HistoricalPeriod
Historical period the topic of the resource refers to.
Examples |
“XV century” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
None |
Refinement of |
DCTerms.temporal? |
ArtisticMovementAndActingStyle
Artistic movement and acting styles in which the work can be categorized (e.g. Classicism, Dada, Epic, Expressionism, etc.)
Examples |
“Futurism” |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
we will work on a shared vocabulary for this |
Refinement of |
DC.type? |
ManagementAndOrganization
management and organization…
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
Deprecated |
RecordingDate
Date of creation of the digital object,
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
Use this element in case what it is recorded is not a public performance (e.g. an interview) otherwise use the Performance Date |
Refinement of |
DC.date |
PersonRecord
Credits for the audio or video recording
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
Deprecated, use Professional elements |
Refinement of |
DC.contributor |
PieceRecord
Credits for the text or image. The meaning of this field is a bit complex.... The text we are dealing with in this field is the script of the play. We intend this field to be filled out with the original title of the performance (eg. Medea) - which might differ from the title of the item (eg. Photo of Medea_2) - and with the name of the person who wrote the script. The records pertaining to the novel or the literary work which inspired the script should be mapped in the field "reference" instead; the field “reference” should also include the title of the novel and its author(s).
Examples |
Title: Il Principe Costante; scenario: Jerzy Grotoski; adaptation: Julius Slowacki |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
None |
Refinement of |
DCTerms.references |
ProductionRecord
Credits of the production team. the name of the producer(s) and of other people involved in the organization.
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Notes |
Deprectaed, use the Professional element with the appropriate role |
Refinement of |
DC.contributor |
DC – dublin core metadata
This section contains information about the dublin core metadata to be associated with the content to be ingested:
title
The name given to the resource. Typically, a Title will be a name by which the resource is formally known. The title of the original analog or born digital object. The title should be significant.
Examples |
“Romeo and Juliet” |
Count
(1, 0..1, 0..many, 1..many) |
1..many |
Language |
Mandatory |
Notes |
None |
creator
An entity primarily responsible for making the content of the resource. Examples of a Creator include a person, an organization, or a service. Typically the name of the Creator should be used to indicate the entity. In ECLAP, the name of Partner uploading is kept automatically in a separate field. This is the name of the creator of the original analog or born digital object. . This field should be used only to indicate the creator of the work of art (usually the director for a performance, the author if we are dealing with a book, the composer if we are uploading a script and so on). Often, in devised work, the creator might be the whole company or the actors might collaborate with the director. Nevertheless I guess we need to set a rule to be applied to every situation, so that I would consider actors and other artistic figures as contributors and eventually explain in the field "description" if their role as creator of the performance was capital.
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Language |
Optional |
Notes |
None |
subject
The topic of the content of the resource. Typically, a Subject will be expressed as keywords or key phrases or classification codes that describe the topic of the resource. Recommended best practice is to select a value from your own classification scheme. This is the subject of the original analog or born digital object.
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Language |
Mandatory |
Notes |
None |
description
An account of the content of the resource. Description may include but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. A description of the original analog or born digital object.
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
Language |
Mandatory |
Notes |
None |
publisher
The entity responsible for making the resource available. Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity. In ECLAP, the name of Partner that has provided the content is automatically tracked and stored in a different field. The name of the publisher of the original analog or born digital object.
Examples |
In case of a Name of the newspaper where a review was published |
Count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
Notes |
None |
contributor
An entity responsible for making contributions to the content of the resource. Examples of a Contributor include a person, an organization or a service. Typically, the name of a Contributor should be used to indicate the entity. In most cases, the authors of a document are listed here. The name of contributors to the original analog or born digital object. This could be a person, an organisation or a service.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
date
A date associated with an event in the life cycle of the resource. Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [Date and Time Formats, W3C Note, http://www.w3.org/TR/NOTE-datetime] and follows the YYYY-MM-DD format. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Many other schemes are possible, but if used, they may not be easily interpreted by users or software. Use for a significant date in the life of the original analog or born digital object. Use dcterms:temporal (or dc:coverage) if the date is associated with the topic of the resource.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
type
The nature or genre of the content of the resource. Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMIType vocabulary
http://dublincore.org/documents/dcmi-type-vocabulary/ ). To describe the physical or digital manifestation of the resource, use the FORMAT element. The type of the original analog or born digital object as recorded by the content holder, this element typically includes values such as photograph, painting, sculpture etc.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Mandatory |
notes |
None |
format
The physical or digital manifestation of the resource. Typically, Format may include the media-type or dimensions of the resource. Examples of dimensions include size and duration. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [http://www.iana.org/ assignments/media-types/] defining computer media formats). The unqualified element includes file format, physical medium or dimensions of the original and/or digital object. Use this element for the file format of the digital object or born digital originals. Internet Media Types [MIME] are highly recommended (
http://www.iana.org/assignments/media-types/). Use of the more specific elements dcterms:extent (dimensions) and dcterms:medium (physical medium) is preferred where appropriate.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
identifier
An unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Examples of formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN). This is the identifier for the original analog or born digital object.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
source
A Reference to a resource from which the present resource is derived. The present resource may be derived from the Source resource in whole or part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system. In general, include in this area information about a resource that is related intellectually to the described resource but does not fit easily into a Relation element. In ECLAP, this value should be the URL or the filename of the original resource. The file uploaded and the URL provided in the upload form are tracked automatically in different fields. This element can be used for several different types of source that are related to the object (such as reference sources). The name of the content holder should no longer be recorded here as a new element.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
language
A language of the resource. Use ISO 639 two letter language tags (it, en, fr, de, el, …) Use this element for the language of textual objects and also where there is a language aspect to other objects e.g. sound recordings, posters, newspapers etc). If there is no language aspect to the digital object (e.g. a photograph), please ignore this element. This element is not for the language of the metadata of a resource, which may be described in xml:lang attribute. In case the digital object presents more languages, use more language elements, one for each language.
examples |
en, it, fr, de, el, hu, es, ca |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
No |
notes |
None |
relation
A reference to a related resource. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system. This is information about resources that are related to the original analog or born digital object.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
coverage
The extent or scope of the content of the resource. Coverage will typically include spatial location (a place name or geographic co-ordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [Getty Thesaurus of Geographic Names,
http://www. getty.edu/research/tools/vocabulary/tgn/]). Where appropriate, named places or time periods should be used in preference to numeric identifiers such as sets of co-ordinates or date ranges. Coverage is the unqualified spatial or temporal coverage of the original analog or born digital object. Use of the more specific dcterms:spatial and dcterms:temporal elements is preferred where possible.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
rights
Information about rights held in and over the resource. Typically a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource. This is a free text element and should be used for information about intellectual property rights or access arrangements for the digital object that is additional to the controlled value provided in europeana:rights.
examples |
“All rights reserved” |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Mandatory |
notes |
None |
DCTERMS – dublin core terms metadata
-
alternative
-
conformsTo
-
created
-
extent
-
hasFormat
-
hasPart
-
hasVersion
-
isFormatOf
-
isPartOf
-
isReferencedBy
-
isReplacedBy
-
isRequiredBy
-
issued
-
isVersionOf
-
medium
-
provenance
-
references
-
replaces
-
requires
-
spatial
-
tableOfContents
-
temporal
alternative
An alternative name given to the resource. Typically, an Alternative title will be a name by which the resource is alternatively referred and it is different from the formal Title. Any alternative title by which the original analog or born digital object is known. This can include abbreviations or translations of the title.
Examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Mandatory |
notes |
None |
tableOfContents
A list of subunits of the resource. A list of the units within the original analog or born digital resource object.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Mandatory |
notes |
None |
created
Date of creation of the resource. This is the date when the original analog or born digital object was created.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
issued
Date of formal issuance (e.g., publication) of the resource. The date when the original analog or born digital object was issued or published.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
extent
The size or duration of the resource. Refinement of format. Size or duration of the digital object and the original object may be recorded.
examples |
“30 pages”, “01:15:20” |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
medium
The material or physical carrier of the resource. Refinement of dc:format.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
isVersionOf
A related resource of which the described resource is a version, edition, or adaptation. Changes in version imply substantive changes in content rather than differences in format. Refinement of dc:relation. See also dcterms:hasVersion.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
hasVersion
A related resource that is a version, edition, or adaptation of the described resource. Changes in version imply substantive changes in content rather than differences in format. Refinement of dc:relation. See also dcterms:isVersionOf. Use dcterms:hasFormat for differences in format.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
isReplacedBy
A related resource that supplants, displaces, or supersedes the described resource.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
replaces
A related resource that is supplanted, displaced, or superseded by the described resource.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
isRequiredBy
A related resource that requires the described resource to support its function, delivery, or coherence.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
requires
A related resource that is required by the described resource to support its function, delivery, or coherence.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
isPartOf
Is Part Of - A related resource in which the described resource is physically or logically included. Use for the name of the collection which the digital object is part of.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
hasPart
A related resource that is included either physically or logically in the described resource. Refinement of dc:relation. See also dcterms:isPartOf.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
isReferencedBy
Is Referenced By: A related resource that references, cites, or otherwise points to the described resource.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
references
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
isFormatOf
A related resource that is substantially the same as the described resource, but in another format. Refinement of dc:relation. See also dcterms:hasFormat.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
hasFormat
A related resource that is substantially the same as the pre-existing described resource, but in another format. Refinement of dc:relation. See also dcterms:isFormatOf. Use dcterms:hasVersion for differences in version.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
conformsTo
An established standard to which the described resource conforms. Refinement of dc:relation. The names of standards that the digital object (digitized or born digital) complies with and which are useful for the use of the object.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
spatial
Spatial characteristics of the resource. Information about the spatial characteristics of the original analog or born digital object, i.e. what the resource represents or depicts in terms of space. This may be a named place, a location, a spatial coordinate or a named administrative entity.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
temporal
Temporal characteristics of the resource. The temporal characteristics of the original analog or born digital object i.e. what the resource is about or depicts in terms of time. This may be a period, date or date range.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
provenance
A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource. This relates to the ownership and custody of the original analog or born digital object.
examples |
… |
count
(1, 0..1, 0..many, 1..many) |
0..many |
language |
Optional |
notes |
None |
Technical metadata
In this section are reported the metadata the are used for the content ingestion.
Type
type of content, basic, playlist or collection
-
BASIC_CONTENT
-
PLAYLIST
-
COLLECTION
Examples |
BASIC_CONTENT |
Count
(1, 0..1, 0..many, 1..many) |
1 |
Notes |
None |
ProviderID
partner acronym providing the data, possible values are:
-
BEELD EN GELUID
-
BELLONE
-
CTA-UNIROMA
-
CTFR
-
ESMAE-IPP
-
FIFF
-
IKP
-
ITB
-
MUZEUM
-
ODIN
-
OSZMI
-
TWM
-
UCAM
-
UCLM
-
UG
-
UVA
-
DSI
-
NTUA
-
FRD
-
OTHER
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
1 |
Notes |
None |
ProviderName
optional name of content provider (to be used if OTHER is set as ProviderID)
Examples |
… |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
None |
ProviderContentID
identifier of the content for the provider (used for aggregations)
Examples |
1267abc |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
Should be mandatory |
ProviderContentUrl
url or filename of the content, use filename if you are providing content via HardDisk or you use the ftp site (
ftp.eclap.eu), in this case the file will be searched in the partner specific folder.
AggregationID
identifier that may be used to aggregate different content e.g. content related to the same performance or to the same piece.
Examples |
Aggregation-234 |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
None |
AggregationName
name of the aggregation if not provided the aggregation id is used
Examples |
“Shakespeare content” |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
None |
IPRModelID
free ID identifying the IPR model to be used for the content, content with same ID will use the same IPR model. If during the ingestion an IPR model with this ID is not present a new one is automatically created.
Examples |
dsi-ipr-model-01 |
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
It should be mandatory |
IPRContactUrl
information (e.g. email or url) to be shown to users to get detailed information on IPR of the content
Examples |
|
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
Deprecated, it is not used, the same information is get from the IPR model associated with the content. |
EuropeanaRightsUrl
the europeana rights url
Examples |
|
Count
(1, 0..1, 0..many, 1..many) |
0..1 |
Notes |
Deprecated, it is not used, the same information is get from the IPR model associated with the content. |
Bookmark/Search this post with: