Friday, September 30, 2011

EUROPEANA - Towards a new Europeana Data Exchange Agreement


Towards a new Europeana Data Exchange Agreement

Europeana supports open re-use of the metadata provided by our content providers and aggregators

The Data Exchange Agreement

Why support open metadata re-use?

It brings tangible benefits for heritage organisations:

  • Increases traffic to your site
  • Allows the Europeana APIs to be widely used
  • Provides income-generating opportunities, e.g. for image licensing
  • Enriches your data for your own use
  • Increases usability and knowledge generation through Linked Open Data applications
  • Enables the development of innovative services and new revenue streams

Our metadata principles

Europeana has set out fundamental principles for its dealings with your metadata. These include:

  1. Europeana is committed to consultation with the network of data providers
  2. Europeana does not intend to make direct commercial use of providers' metadata
  3. The contribution of data to Europeana does not prevent you from selling metadata to a third party
  4. Data Providers are not required to provide Europeana with complete metadata for digital objects
  5. Providing metadata relating to some works in your collections does not create the obligation to provide metadata about complete collections
  6. Thumbnails and previews will only be used by Europeana. Unless explicitly specified they cannot be reused by third parties

Strategic outlook

Jill Cousins' presentation* describes how the new agreement relates to the Comité des Sages New Renaissance Report and Europeana's Strategic Plan 2011-2015. It outlines what restrictions the current Agreement imposes that need to be overcome.
Your Metadata and Europeana gives a useful overview of our plans and explains the strategic need for an open metadata licence.
Validity of the Creative Commons Zero 1.0 Universal Public Domain Dedication with regards to the German Copyright Law. An expert analysis.

Related Europeana initiatives

We have recently released the Europeana API and search widget. APIs are ways of showing Europeana data through third-party sites. We currently limit the use of APIs to network partners because of the non-commercial restriction in the current Agreement. We need an open metadata licence to allow the API to be embedded in educational websites and academic blogs that use Google ads or are linked to commercial services.

We have published a guide to Linked Open Data and Europeana.

We are also running a Linked Open Data pilot, which is working with over 3 million metadata records from 20 partners including the Austrian National Library, the Danish Film Institute and the Swedish National Heritage Board. See related pages.

Recommended reading

FAQ's

Why there is need for a new agreement between Europeana and the providers?

Is the new Data Exchange Agreement the same for data providers and for aggregators?

Why drop the non-commercial clause from the agreement?

How is attribution handled in the context of the Data Exchange Agreement?

Does Europeana plan to use data from its data providers for commercial purposes?

What does the Data Exchange Agreement foresee about previews (thumbnails, a/v snippets, etc.) and content?

Do I loose control over the data if my metadata becomes available under the new Data Exchange Agreement/CC0?

Why is it not possible to create licenses at record level so that some data submitted to Europeana can be excluded from an onward CC0 license?

Can I continue generating income with my metadata if it becomes available under the new Data Exchange Agreement/CC0?

What can others do with my metadata after it has been published by Europeana?

What is Linked Open Data?

Why does Europeana want to publish my data as Linked Open Data?

Are there any examples of LOD implementation in the cultural heritage sector?

What is Europeana doing with LOD?

What will happen when we move from the old agreement to the new?

What are the next steps in the process towards agreeing the new Data Exchage Agreement?

I am an aggregator/data provider and I deliver data to Europeana. I already have signed the existing aggregator/ data provider agreement. Do I need to sign the new one?

I am an EU-funded project and I deliver data to Europeana. Do I need to sign the Data Exchange Agreement?

My project is coming to an end before September and I don't have any kind of Agreement signed with Europeana. What do I need to do?

What happens to my metadata if I sign the Data Exchange Agreement?

What happens with my metadata if I don't sign the agreement?

Europeana asks me to deliver the data I feel comfortable with delivering. What are the different implementation scenarios?

Europeana asks providers to deliver what they feel comfortable with but at the same time makes more metadata fields mandatory. Isn't this an oxymoron?

In some domains it can be difficult to differentiate clearly between content and metadata, and as a result whatever data is given to Europeana is called, for purposes of this agreement, metadata. In the DEA it says explicitly anyway that Europeana is not aggregating content. So which is true?

Is Europeana going to update the agreement any time soon?

* note: large file size - 11.6mb

The Data Exchange Agreement and Use Guidelines are part of Europeana's Licensing Framework which was developed in the context of EuropeanaConnect.

Preuzeto sa sajta EUROPEANA http://www.version1.europeana.eu/web/europeana-project/newagreement

Enhanced by Zemanta

No comments:
http://ncrcbiblioteka.blogspot.com/2011/09/europeana-towards-new-europeana-data.html
ncrcbiblioteka.blogspot.com
crawl=CC-MAIN-2013-20
233695
application/http; msgtype=response
sha1:ASL5FXPTJP6G7VJ245JA2KJR5JMVDI4E
<urn:uuid:b2771e82-5af5-4014-a4e3-020db6de2ab7>
2013-05-26T08:05:34Z
74.125.228.44
sha1:ZHWBXVR3L62TZYDISJE2LZUWXLQK4VSM
<urn:uuid:02ccb879-3b0a-476d-b1c5-1090f19c2916>
http://ncrcbiblioteka.blogspot.com/2011/09/europeana-towards-new-europeana-data.html
response
<urn:uuid:85445227-39f8-4c5d-b782-099f96e5dda8>
robots: classic
hostname: ip-10-60-113-184.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2013-20
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for Spring 2013
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf