Presentation on theme: "Ali Alshowaish. dc.coverage element articulates limitations in the scope of the resource, typically along the following lines: geographical, temporal,"— Presentation transcript:
dc.coverage element articulates limitations in the scope of the resource, typically along the following lines: geographical, temporal, jurisdictional. dc.coverage example:
dc.type: The nature of the content of the resource. Types includes terms describing general categories, functions, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMIType vocabulary ).DCMIType vocabulary dc.type example: Types includes: Collection, Dataset, Event, Image, InteractiveResource, Moving Image, PhysicalObject, Service, Software, Sound, Text.
dc.contributor is an entity responsible for making contributions to the resource dc.contributor example: Contributor include but not limited to: translator, adviser, editor, designer …etc.
dc.publisher is an entity responsible for making the resource available. dc.publisher example: Publisher may include but is not limited to: person, an organization, or a service …etc. Typically, the name of a Publisher should be used to indicate the entity.
dc.description: a textual description or abstract of the content of the resource. dc.description example: Description may include but is not limited to: an abstract, a table of contents, or a free-text account of the resource.
dc.format: The physical or digital manifestation (media-type) of the resource. dc.format example: Format may include but is not limited to: The file format, physical medium, or dimensions of the resource.
dc.identifier: an unambiguous reference to the resource within a given context. dc.identifier example: 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).
dc.subject: Indicates the topic of a resource (subject descriptor) or a set of keywords that describe the contents of the object. dc.subject example:
Terms used should be selected from a controlled vocabulary such as: LCSH (Library of Congress Subject Heading) MeSH (Medical Subject Headings) GoC Core (Government of Canada Core Subject Thesaurus) etc…
dc. source : a reference to a resource from which the present resource is derived. dc.source example: (ISBN)
dc.relation: relationship to other resources. For example part of a serial. dc.relation example: Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
dc.rights: The content of this element is intended to be a link (a URL or other suitable URI as appropriate) to a copyright notice, a rights- management statement, or perhaps a site tht would provide such information in a dynamic way. The intent of specifying this field is to allow providers a means to associate terms and conditions or copyright statements with a resource or collection of resources dc.rights example:
Qualifiers are additional terms to the original core elements, which allow us to make DC records more specific. Qualifiers are used for two things: Refinement: Make the scope of an element narrower Encoding Scheme: Specify a scheme that control the value strings. Simple DC uses the 15 base elements and does not use qualifiers ( element refinements or encoding schemes) Qualified DC uses qualifiers for element refinements and encoding schemes.
55 elements or attribute-value pairs – qualified DC Full description of the qualifiers is available: http://dublincore.org/documents/2000/07/1 1/dcmes-qualifiers/ http://dublincore.org/documents/2000/07/1 1/dcmes-qualifiers/
16 http://dublincore.org/documents/usageguide/qualifiers.shtml examples: ElementQualifierExample TitleAlternativeTitle=Tristram Shandy Title.Alternative=The Life and Opinions of Tristram Shandy DateCreated Modified Copyrighted Date.Created=01.29.2005 Date.Modified=01.30.2005 Date.Modified=02.02.2005 RelationIsAVersionOf Requires IsPartOf [each takes a valid URI]