You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

DOS Common Metadata Elements at the Resource/Item/Materials Level

Common Name

Cardinality

Datatype

Definition

Usage Notes

Example

Identifier

1 and only 1

URI

A globally unique, persistent expression associated with the Resource.

Each repository will assign an identifier to the resources within its collections.  Resources are individual components of a course.  Resources in different repositories that contain the same content are not considered identical and should not share identifiers, however, they should reference each other via the identifiers assigned by each repository.  Both DSpace and OCW use URIs as resource identifiers, Stellar should adopt a similar practice.

http://ocw.mit.edu.ezproxyberklee.flo.org/OcwWeb/Chemistry/5-37Spring-2009/MIT5_37s09_lec01_Mod7

Title

1 and only 1

String

The name given to the Resource.

This name should be taken from the Resource itself, whenever possible.

Packing of Secondary Structures

Description

1 and only 1

String

A textual description of the content of the Resource.

Whenever possible use abstracts or other descriptions found on the resource.

Lecture presentation on global supply chains and competition across the China Straits.

Contributor

1 or more

Agent

The name of a person or organization that has contributed to the preparation of the Resource.

Authority Control should be provided in choosing the form of the contributor's name. Contributions should be characterized by the role of the contributor.  A vocabulary of roles should be adopted.  MIT OpenCourseWare uses the following candidate vocabulary:

[Vocab]

Lakhani, Karim

Publisher

1 and only 1

Agent

The name of the course-content system in which the Resource was produced and disseminated.

This element allows the three DOS course-content systems to put their imprimatur on resources they have produced.  Values for this element should be restricted to the names of the DOS systems.   It is unlikely that the DSpace value will ever be used.  Courses are published in either Stellar or OCW and are merely transferred to DSpace.  DSpace will record the name of system in which the course was originally published.

"MIT OpenCourseWare" or "DSpace@MIT" or "Stellar Course Management System"

Publication Date

1 and only 1

DateTime

The date a the resource was made available to the audience of a course-content system.

A publication date will be assigned by each system.  This date corresponds to the day when access to the resource is first allowed by the system.  Stellar's publication date is the resource creation date. The DSpace publication date is the date the resource is deposited in the repository.  Resources deposited in DSpace are immediately available to the public. OCW records the date they first ran the resource through the publication engine.  Values for this element should conform to the ISO 8601 date and time format standard.

2007-04-16

Current Status

1 and only 1

Controlled Vocabulary

This represents where the resource currently resides and the state

We need to come up with the vocabulary. When the resource in Stellar - Created, Being Taught OCW - Unpublished, Staging, Published Library - archived

 

Language

1 or more

ISO 639-1

The languages in which the Resource is taught.

Values for this element should conform to the ISO 639-1 standard for two letter encoding of languages. Two letter language codes may be supplemented by an additional two letter code for the country of origin.

en-US

Aggregation Level

1 and only 1

Controlled Vocabulary

The granularity of the Resource in the OCW content model.

Use the IEEE LOM defined controlled vocabulary for this element. In that vocabulary there are four allowable values “4”, “3”, “2”, and “1”, where 4 = Course, 3 = Section, 2 = Resource, 1 = Object. The value of this element for Resources will always be “2”

2

Location

1 and only 1

URL

The url at which the Resource may be found.

This element should always start with “http://” and contain the full address.

http://ocw.mit.edu.ezproxyberklee.flo.org/NR/rdonlyres/Biology/7-88JFall-2007/AE3E6B3F-E462-4C30-8BE0-73BF9A6D600D/0/7_88_assign1.pdf

Format

1 and only 1

Internet Media Type

The MIME type of the Resource file.

Allowable values should be restricted to those registered with the IANA (see

http://www.iana.org/assignments/media-types/

).

application/pdf

Size

1 and only 1

Non-negative Integer

The size of the Resource in bytes.

The value of this element should be automatically populated.

74611

Technical Requirements

0 or 1

String

A textual description of software and hardware requirements for consuming the Resource.

If applicable, one field should aggregate all requirements that may apply to the Resource. The requirement declarations should conform to the vocabulary of such statements.

Scheme software is required to run this .scm file.

Educational Context

1 or more

Controlled Vocabulary

The MIT level of study for which the Resource is appropriate.

This element is governed by a controlled vocabulary. Resource metadata should inherit values for this element from the metadata for the Course(s) to which the Resource belongs. This element should always be used in conjunction with a lom:lom/educational/c

Undergraduate

Learning Resource Type

1 and only 1

Controlled Vocabulary

The type of Open Educational Material

The value of this element should conform to the OER Commons Material Types vocabulary: Activities and Labs, Assessments, Audio Lectures, Curriculum Standards, Discussion Forums, Games, Homework and Assignments, Lecture Notes, Lesson Plans, Readings, Simul

Video Lectures

Rights

1 or more

String

The statement of copyright associated with the Resource.

The OCW copyright statement should be standard for all Resources and identical with the example provided.

How can we define and communicate rights in common level? This is more a Policy level question in MIT level.

Credit

0 or 1

String

A brief description of the allowance under which a resource is included in MIT OpenCourseWare publications. Usually identifies the person or organization that has granted usage rights to MIT OpenCourseWare.

A brief description of the allowance under which a resource is included in MIT OpenCourseWare publications. Usually identifies the person or organization that has granted usage rights to MIT OpenCourseWare.

Photo by shinyai on Flickr.

License

1 or more

CC License (URI)

The URI for the Creative Commons license associated with the Resource.

This value should always be ""http://creativecommons.org/licenses/by-nc-sa/3.0/us/""

Relation Kind

For each Relation 1 and only 1

Controlled Vocabulary

A characterization of the kind of relationship identified by the Relation element.

This element should accompany every Relation element. Values should conform to the Dublin Core relation element refinements: http://purl.org/dc/terms/conformsTo, http://purl.org/dc/terms/hasFormat, http://purl.org/dc/terms/hasPart, http://purl.org/dc/terms/hasVersion, http://purl.org/dc/terms/isFormatOf, http://purl.org/dc/terms/isPartOf, http://purl.org/dc/terms/isReferencedBy, http://purl.org/dc/terms/isReplacedBy, http://purl.org/dc/terms/isRequiredBy, http://purl.org/dc/terms/isVersionOf, http://purl.org/dc/terms/references, http://purl.org/dc/terms/replaces, http://purl.org/dc/terms/requires, . This element should always be used in conjunction with a lom:lom/relation/kind/source element whose value is “http://purl.org/dc/terms/”.

http://purl.org/dc/terms/replaces (for older version of the Course)

Course

1 or more

URI

The URI for the Course to which the Resource belongs.

This value should be autopopulated.

http://ocw.mit.edu.ezproxyberklee.flo.org/OcwWeb/Biology/7-88JProtein-Folding-ProblemFall2003

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7da2b67a-5643-4910-a1af-346af2ac4559"><ac:plain-text-body><![CDATA[

Relation (to other Resources)

0 or more

URI

The URI for a Resource related to the one described in the metadata record.

Each assigned Relation should be paired with a Relation Kind element that appropriately characterizes the relationship. Examples of related Resources include, but are not limited to: homework assignments and their solutions; homework assignments and stude

[URI scheme for resources is necessary.]"

]]></ac:plain-text-body></ac:structured-macro>

ISBN

0 or 1

String

 

 

 

  • No labels