lom:lom/general/identifier/entry

Identifier

1 and only 1

URI

A globally unique, persistent expression associated with the Course.

The use of absolute, dereferenceable URIs are recommended for this element.

Each repository will assign an identifier to courses within its collections.  A course represents an offering of a MIT Subject.  These offerings are principally characterized by the semester and year in which they were taught.  Courses in different repositories that represent the same offering 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 course identifiers, Stellar should adopt a similar practice.

DSpace DSpace will assign a Handle to every course in its collections.  Example: http://dspacehdl.mithandle.edunet/handle/1721.1/52322&nbsp52321 ; OCW:http://ocw.mit.edu/OcwWeb/BiologyChemistry/75-88JFall-2007 3) Archived Course - Library Link for the course lom:lom/general/title/string 37Spring-2009

Title

1 and only 1

String

The name given to the Course.

Protein Folding Problem

The desired content of course titles has not been resolved.  Course titles may or may not include the course number and semester information. 

"Introduction to Organic Synthesis Laboratory" or "5.37 Introduction to Organic Synthesis Laboratory Spring 2009"

lom:lom/general/description/string

Description

1 and only 1

String

A textual description of the content of the Course.

This course focuses on the mechanisms by which the amino acid sequence of polypeptide chains (proteins), determine their three-dimensional conformation. Topics in this course include sequence determinants of secondary structure, the folding of newly synth

Course descriptions for each MIT subject are made available by the registrar's office through the course catalog and should be adopted from that source whenever possible.  Certain subjects are designed to contain different content each time the course is offered.  Descriptions for these offerings are often not found in the course catalog and must be discovered via other sources.

Classical mechanics in a computational framework, Lagrangian formulation, action, variational principles, and Hamilton's principle. Conserved quantities, Hamiltonian formulation, surfaces of section, chaos, and Liouville's theorem. Poincare integral invariants, Poincare-Birkhoff and KAM theorems. Invariant curves and cantori. Nonlinear resonances, resonance overlap and transition to chaos. Symplectic integration. Adiabatic invariants. Applications to simple physical systems and solar system dynamics. Extensive use of computation to capture methods, for simulation, and for symbolic analysis. Programming experience required. Students taking the graduate version complete additional assignments. lom:lom/lifeCycle/contribute/entity

Contributor

1 or more

Agent

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

Authority Control should be provided in choosing the form of the contributor's name. Each assigned Contributor should be paired with a Contributor Role element that appropriately characterizes the contribution. There are two kinds of Contributors, Creator

King, Jonathan

The form of contributor names should be controlled and consistently applied across all three course-content systems.  This requires a shared resource that defines preferred forms of names, cross references variant forms, and provides identifying information for each contributor.  MIT OpenCourseWare is developing such a resource for its own collections.  If possible, this resource should be shared with the other course-content systems.  Contributions should be characterized by the role of the contributor.  A vocabulary of roles should be adopted.  MIT OpenCourseWare uses the following candidate vocabulary: Course Instructor, Creator.  Course Instructors are those members of the MIT faculty primarily responsible for course preparation and instruction.  Creators are those individuals other than Course Instructors that are responsible for course content.

King, Jonathan

Publisher

1 and only 1

Agent

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

This element allows the three DOS course-content systems to put their imprimatur on Courses they have produced.  Values for this element should be restricted to the names of the DOS systems.  The form of those names should be strictly controlled and consistent across all course-content systems. It is unlikely that the DSpace@MIT 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"

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7a0d3cfe-a2f3-4667-9898-58e75feded80"><ac:plain-text-body><![CDATA[

lom:lom/lifeCycle/publicationDate/dateTime

Publication Date

1 and only 1

DateTime

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

A publication date will be assigned by the [what are we calling these three things again – content management systems?, enterprise systems?, repositories?] Stellar Course Creation Date For DSpace this each system.  This date corresponds to the day when access to the course content is first allowed by the system.  Stellar's publication date is the course creation date. The DSpace publication date is the date the course is deposited in the repository. For OCW this is   Courses deposited in DSpace are immediately available to the public. OCW records the date they publish first run the course through the publication engine.

8/25/2008

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

  Values for this element should conform to the ISO 8601 date and time format standard.

2008-05-28

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6bf44546-e9c0-4ff3-93c6-b5064c8e17ae"><ac:plain-text-body><![CDATA[

lom:lom/lifeCycle/version/string

Semester

1 and only 1

String

The semester in which the Course was taught.

This is common but Stellar is source. This may come from RegistrarThe form of semester declarations should be controlled and consistently applied across all three course-content systems. The values for this element should conform to the following format: “[semester] [year]”. Years should include all four digits. The allowable values for semester are: “Fall”, “Spring”, “January (IAP)”“IAP”, “Summer”.

Fall 2007

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

lom:lom/general/identifier/entry

Master Course Number

1 and only 1

Controlled Vocabulary

The primary number assigned to the Course according to the MIT Course Numbering System.

This element Course numbers should always be used in conjunction with the lom:lom/general/identifier/catalog element. The value of that element should always be “OCW Master Course Number”be consistently formatted across the three course-content systems.  The registrar's office is a candidate for a common source and format for these numbers.

7.88J

lom:lom/general/department

Department

0 or 1

Controlled Vocabulary

The course belongs to this department

Source is Stellar

Physics

lom:lom/general/currentStatus

Current Status

1 and only 1

Controlled Vocabulary

This represents where the course currently resides and the state

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

lom:lom/general/identifier/entry

Cross-Listed Course Number

0 or more

Controlled Vocabulary

Additional number's assigned to the Course according to the MIT Course Numbering System.

Stellar is the source of this Info. This element should always be used in conjunction with the lom:lom/general/identifier/catalog element. The value of that element should always be “OCW Linked Course Number”.

10.543J

Course numbers should be consistently formatted across the three course-content systems.  The registrar's office is a candidate for a common source and format for these numbers.

10.543J

Current Status

1 and only 1

Controlled Vocabulary

The name of the course-content system in which the course resides, and its state within that system.

A vocabulary of states needs to be identified.  Potential values for OCW are Unpublished, Staging, Published, Archived.

  lom:lom/general/language

Language

1 or more

ISO 639-1

The languages in which the Course 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. Follow the format used in the example.

en-US

lom:lom/general/aggregationLevel/value

Aggregation Level

1 and only 1

Controlled Vocabulary

The granularity kind of the Course in the OCW object from the DOS 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 Courses will always be “4”.

4

described by the metadata record.

There are only two kinds of objects for which metadata definitions have been created: Courses and Resources.  Courses are equivalent to OCW Courses and Stellar Sites.  Resources are equivalent to OCW Resources and Stellar Materials.  Both Courses and Resources are likely DSpace Items. 

Course

lom:lom/technical/location

Location

1 and only 1

URL

The url at which the Course may be found.

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

It depends on the state of the Course. 1) Stellar Course - Stellar Link 2) OCW - http://ocw.mit.edu/OcwWeb/Biology/7-88JFall-2007/CourseHome/index.htm 3) Archived Course - Library Link for the course

lom:lom/technical/otherPlatformRequirements/string

Technical Requirements

0 or 1

String

A textual description of software and hardware requirements for consuming resources included in the Course. If applicable, one field should aggregate all requirements that may apply to the various resources in the Course. The requirement declarations should conform to the vocabulary of such statements

This element is optional.

Scheme software is required to run the .scm files found on this course site. File decompression software, such as Winzip® or StuffIt®, is required to open .gz and .zip files found on this course site. The .exe files found on this course site are executabl

lom:lom/educational/context/value

Educational Context

1 or more

Controlled Vocabulary

The MIT level of study at which the Course is taught.

This element is governed by a controlled vocabulary. MIT courses are taught at either the “Undergraduate” or “Graduate” levels, or both. If the Course is taught at both levels, this element should be repeated for each value. This element should always be

Undergraduate lom:lom/rights/description/string

Rights

1 or more

String

The statement of copyright associated with the Course.

The use of rights metadata is not consistent across all three course-content systems. OCW and DSpace make courses available to the general public while Stellar content is typically available only to students and faculty.  This engenders different intellectual property use policies and different rights metadata requirements.

License

0

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

lom:lom/rights/description/string

License

1 or more

CC License (URI)

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

lom:lom/relation/kind/value

Relation Kind

If relation exists, 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)

This field is optional and is subject to the same inconsistencies of use as rights metadata.

MIT Subject

0 or more

Controlled Vocabulary

The name of the MIT Subject of which the course is an individual offering.

Use of this field is optional. MIT Subjects should be consistently referenced by all three course-content systems, either by the use of shared identifiers or by controlling the form of MIT Subject names.  Ideally, the MIT Registrar's Office will maintain the subject vocabulary.  MIT Subject relationships should always be characterized by using the Dublin Core relation element refinement "isVersionOf".

Department

0 and more

Controlled Vocabulary

The department from which the course is offered.

Use of this field is optional.  The DOS course-content systems should reference departments in the same way, either by the use of shared identifiers or by controlling the form of Department names.  Ideally, the MIT Registrar's Office will maintain the department vocabulary.  Department membership should always be characterized by using the Dublin Core relation element refinement "isPartOf".

Physics

Track

0 or more

Controlled Vocabulary

Use of this field is optional.  The DOS course-content systems should reference tracks in the same way, either by the use of shared identifiers or by controlling the form of Department names.  Ideally, the MIT Registrar's Office will maintain the track vocabulary.  Track membership should always be characterized by using the Dublin Core relation element refinement "isPartOf".

Prerequisites

0 or more

URI

Use of this field is optional.  Prerequisites are MIT subjects, not individual subject offerings (i.e. courses).  It is inappropriate to use the identifiers of other courses to identify prerequisites.  The DOS course-content systems should reference prerequisites in the same way, either by the use of shared identifiers or by controlling the form of MIT Subject names.  Ideally, the MIT Registrar's Office will maintain the prerequisites vocabulary.  Prerequisites should always be characterized by using the Dublin Core relation element refinement "requires".

General Institute Requirements

0 or more

Controlled Vocabulary

GIR's should always be characterized by using the Dublin Core relation element refinement "isPartOf".

Course Textbook

0 or more

URI

Course textbooks should always be characterized by using the Dublin Core relation element refinement "requires".

Related Courses

0 or

lom:lom/relation/resource/identifier/entry

Relation

0 and more

URI

The URI for the related Course.

The primary use of this element is to relate different versions of the same course, including versions in other course-content systems. Other reasons to relate courses may identify themselves. Each assigned Relation Related courses should be paired with a Relation Kind element that appropriately characterizes the relationship. The use of absolute, dereferenceable URIs are recommended for this element. These URIs should be identical to the Identifier element of the pertinent Course. This element should always be used in conjunction with a lom:lom/relation/resource/identifier/catalog element. The value of that element should always be “URI”. always be characterized by using the Dublin Core relation element refinements (conformsTo, hasFormat, hasPart, hasVersion, isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires).

http://ocw.mit.edu/OcwWeb/Biology/7-88JProtein-Folding-ProblemFall2003 lom:lom/classification/taxonPath/taxon/entry/string

Other Relations

0 or more

URI or String

The name or identifier of other things to which the Course is meaningfully related.

This is a catch-all for important relationships identified in the future.  Relations should always be characterized by using the Dublin Core relation element refinements (conformsTo, hasFormat, hasPart, hasVersion, isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires).

Classification

1 or more

Controlled Vocabulary

The topic of the Course as taken from a classification scheme.

A shared taxonomy needs to be identified or developed for this element. Current use of CIP codes should be abandoned. This element should always be used in conjunction with a lom:lom/classification/taxonPath/source/string element that names the taxonomy.

?

lom:lom/classification/keyword/string  

Keywords

0 or more

String

Words and phrases that describe the intellectual content of the Course.

This element is optional.  Keywords are unrestricted by any taxonomy.

chemical bonding