Standards de métadonnées sur les droits

Olivier Charbonneau 2018-11-03

Quelques sources:
Open Archives Initiative

Open Archives Initiative Protocol for Metadata Harvesting 2.5

Dublic Core

  • Dublin Core Metadata Element Set: rights, source…
  • Dublin Core Metadata Initiative DCMI Metadata Terms

DMCI Terms

Publishing Requirements for Industry Standard Metadata PRISM Metadata from ideaalliance

The Library of Congress >> Standards >> Metadata Encoding and Transmission Standard (METS) Draft Rights Declaration Schema

<amdSec> elements contain the administrative metadata pertaining to the files comprising a digital library object, as well as that pertaining to the original source material used to create the object. There are four main forms of administrative metadata provided for in a METS document: 1. Technical Metadata (information regarding files’ creation, format, and use characteristics), 2. Intellectual Property Rights Metadata (copyright and license information), 3. Source Metadata (descriptive and administrative metadata regarding the analog source from which a digital library object derives), and 4. Digital Provenance Metadata (information regarding source/destination relationships between files, including master/derivative relationships between files and information regarding migrations/transformations employed on files between original digitization of an artifact and its current incarnation as a digital library object). Each of these four different types of administrative metadata has a unique subelement within the <amdSec> portion of a METS document in which that form of metadata can be embedded: <techMD>, <rightsMD>, <sourceMD>, and <digiprovMD>. Each of these four elements may occur more than once in any METS document.

J. Paul Getty Trust > Practical Principles for Metadata Creation and Maintenance

9. Research and documentation of rights metadata must be an integral part of an institution’s metadata work flow. This metadata should be captured and managed in an appropriate information system that is available to the all of the individuals in the organization who need to contribute to it as well as those who need to use it. (See “Rights Metadata Made Simple.”)

Metadata Guidelines – UMass Amherst Libraries

March 2013, p. 29-30

Access, Use, and Rights

Recommended Dublin Core map: rights

(Recommended, Repeatable, Free-text)

Overview

Access, Use, and Rights provides information about the conditions that affect the availability of the resource or about the rights associated with resources.

  • Provide access or use information in the most granular form.
  • The audience for this element is the end-user, so use clear language free of legal or library jargon.
  • This element may be used to describe a lack of use restrictions.
  • Provide rights information in the most granular form.
  • The audience for this element is the end-user, so use clear language free of legal or library
  • jargon.
  • State any restrictions on use of the resource.
  • If the resource is in the public domain, state the lack of copyright restrictions.
  • Metadata Guidelines 30
  • A link may be provided instead of or in addition to the content.
  • Provide contact information for use by end users who wish to pursue required permissions for
  • publication, dissemination, etc.
  • The <rights> container available in the OAI protocol should not be used to describe rights

pertaining to the resource, but to describe rights pertaining to the metadata. See

DLF’s Expressing Rights for Metadata within the OAI Protocol for more information.

More guidance can be found in your chosen Content Standard.

Access, Use, and Rights expressed in select metadata schema

 

Open Digital Rights Language (ODRL) Information Model 2.2
Recommandation du W3C (15 février 2018)

Ce contenu a été mis à jour le 2018-11-04 à 8 h 25 min.