This document discusses Europeana's use of unique identifiers and provides guidance on publishing and republishing metadata. It notes that Europeana uses EDM resource identifiers to distinguish items and detect duplicates. It advises ensuring unique local identifiers are used for each imported item to avoid duplicates being discarded. It also presents four cases involving publishing new or updated metadata and actions to take, such as unpublishing existing imports before publishing overlapping new ones.
2. Unique identifiers
Europeana uses the EDM resource identifiers to
distinguish your items and detect duplicates.
EDM resource identifiers in MINT are created by using
the project name and your local identifier
Make sure you use unique identifiers among your
imports for each item, otherwise the second item
harvested by Europeana having the same identifier will
be discarded.
3. Local Identifier
EDM Resource Identifiers
<edm:ProvidedCHO rdf:about="http://mint-
projects.image.ntua.gr/data/sounds/108_0851b">
<dc:creator>Johann Sebastian Bach</dc:creator>
<dc:identifier>108_0851b</dc:identifier>
<dc:title>Bourree in e-minor</dc:title>
. . .
<edm:type>SOUND</edm:type>
</edm:ProvidedCHO>
Unique identifiers
10. Monitoring of metadata
production
You can see the number of published records
by visiting the OAI-PMH manager page at
http://panic.image.ntua.gr:9876/manager/projects/
sounds
12. Case 1: Update published
metadata
Import_1 contains metadata for 1000 items
and it is published.
Feedback sent from Europeana about it
Action
Unpublish
Correct mapping
Re-publish
13. Case 2: Non overlapping
imports
Import_1 contains metadata for 1000 items
and it is published.
Import_2 contains metadata for 2000 items
that are not contained in Import_1
Action
If Import_2 is compliant with Import_1 use an
existing mapping to publish
If Import_2 is not is compliant with Import_1 make
a new mapping for Import_2, and publish
14. Case 3: Overlapping imports
Import_1 contains metadata for 1000 items
and it is published.
Import_2 contains metadata for 2000 items
some of them are contained in Import_1
Action
Unpublish Import_1
Use an existing mapping, if Import_2 is compliant
with Import_1 if not make a new mapping for
Import_2, and publish
15. Case 4: Unpublish from
Europeana
Import_1 contains metadata for 1000 items
and it is published.
These metadata have been harvested and
published by Europeana but for some reason
you want to unpublish them. (i.e. remove them
from Europeanas portal)
Action
Unpublish Import_1
Inform me about the import you want to unpublish
from Europeana