Ali Alshowaish

dc.coverage element articulates limitations in the scope of the resource, typically along the following lines: geographical, temporal, jurisdictional.

dc.coverage example:<meta name="dc.coverage" content="1875 to 1910">

<meta name="dc.coverage" content="Europe, US and Canada">

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 ).

dc.type example:<meta name="dc.type“ content="text">

<meta name="dc.type“ content="image">

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:<meta name="dc.contributor" content=“Khalid Aba Alhassan">

<meta name="dc.contributor“ content=“King Saud University">

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:<meta name="dc.publisher" content=“McGraw Hill">

<meta name="dc.publisher“ content=“King Faisal University">

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:<meta name="dc.description" content=“This dissertation examines the

impacts of social movements through a multi-layered study of the Mississippi Civil Rights Movement from its peak in the early 1960s through the early 1980s. By examining this historically important case, I clarify the process by which movements transform social structures and the constraints' movements face when they try to do so. ">

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:<meta name="dc.format" content=“text/html">

<meta name="dc.format“ content=“image/gif">

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:<meta name="dc.identifier" content=“http://www.ischool.utexas.edu">

<meta name=“dc.identifier“ scheme="ISBN" content="1-56592-149-6">

<meta name=“dc.identifier“ scheme="DOI" content="10.12345/33-824688ab">

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:<meta name="dc.subject” content=“Student loans; Scholarships;

Debt; Financial assistance; Grants; Financial management; Budgets; Personal finance; Loans ">

<meta name=“dc.subject“ content=" Federal Departments; Foreign Affairs; Travel; Information; Government Services “>

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:<meta name="dc.source” content=“Journal of American

Psychology Association">

<meta name=“dc.source” content=" 1-56884-452-2“> (ISBN)

dc.relation: relationship to other resources. For example “part of a serial”.

dc.relation example:<meta name="dc.relation” content=“computers for dummies">

<meta name=“dc.relation” content=“http://lu.com/showseries.cfm?serid=20”>

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:<meta name="dc.rights” content=“Public domain">

<meta name=“dc.rights” content=“http://www.someplace.se/copyright.html”>

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/11/dcmes-qualifiers/

16

http://dublincore.org/documents/usageguide/qualifiers.shtml

examples:

Element Qualifier Example

Title Alternative Title=“Tristram Shandy”

Title.Alternative=“The Life and Opinions of Tristram Shandy”

Date Created

Modified

Copyrighted

Date.Created=“01.29.2005”

Date.Modified=“01.30.2005”

Date.Modified=“02.02.2005”

Relation IsAVersionOf

Requires

IsPartOf

[each takes a valid URI]

17

http://dublincore.org/documents/usageguide/qualifiers.shtml

More examples:

Element Qualifier Example

Subject LCSH

DDC

MeSH

Subject=“baking”

Subject.LCSH=“Cookery--Baking”

Type DCMI Type.DCMI=“image”

Type.DCMI=“movingImage”

Type.DCMI=“text”

Language RFC1766

[ISO 639]

Language.RFC1766=“en”