Page tree
Skip to end of metadata
Go to start of metadata

Current DAM (Assets) properties stored

The following table display the current situation.
  First column display the property name stored and his Asset equivalent if different
  Second column display the Dublin Core equivalent 
  Third column display the description.

Asset property NameDublin core property NameDescription
 contributorExamples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
 coverageSpatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
jcr:createdBycreatorExamples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
mgnl:lastModifieddateDate may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
descriptiondescriptionDescription may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
jcr:mimeType formatThe file format, physical medium, or dimensions of the resource.
Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
jcr:uuididentifierAn unambiguous reference to the resource within a given context.
Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
languagelanguageA language of the resource.
Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
 publisherAn 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.
 relationA related resource.
Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
copyrightrightsInformation about rights held in and over the resource.
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
 sourceA related resource from which the described resource is derived.
The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
subjectsubjectThe topic of the resource.
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary.
titletitleA name given to the resource.
Typically, a Title will be a name by which the resource is formally known.
typetypeThe nature or genre of the resource.
Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
name Probably not a MetaData
subject Probably not a MetaData
caption Probably not a MetaData
extension Currently equivalent to type.
fileName File Name
height File height
width File width
size File size
jcr:data Binary

As shown in the table, some fields already exist, but many do not yet - they should be added.

 

 

  • No labels