Hello, all:
I'm working with the IMS – RLI Working Group to identify metadata elements
necessary for Citation to and Location of Resources to add to Resource
Lists, and Resource Lists per se. We're currently at the stage where we're
trying to map the elements we've come up with against the IEEE-LOM metadata
element set for an IMS-CP and IEEE-LOM binding, and I'd love to get some
feedback on what we've come up with so far. There was some discussion about
this at the last IMS meeting in San Jose where a number of people present
noted the range of experience with using IEEE-LOM represented on this
listserv, and suggested that I post any questions I had to this group. I'm
attaching a Word document to this message which illustrates the mapping that
I've come up with, but am also putting that information into the full
message below (in a much more messy format -- sorry about that!). The
IMS-RLI WG would appreciate any advice / thoughts you'd like to offer us.
I've now signed on to the CETIS-METADATA listserv, so will be able to see
the comments herein.
***********************
1. Resource = Entire Document: For a resource that is not a part of
another digital object, i.e., a book or entire journal, the mapping would
look like the following:
RLI Element Name / LOM Element Name / Comments
Creator / 2.3.2:Lifecycle.Contribute. Entity / When 2.3.1: Lifecycle.
Contribute. Role has value of "Author"
Title 1.2 General Title Title being cited
Edition 2.1:Lifecycle.Version
Publisher 2.3.2:Lifecycle.Contribute.Entity When 2.3.1: Lifecycle.
Contribute. Role has value of "Publisher"
Place of Publication ? Unclear if used; may be considered unnecessary.
Date of Publication 2.3.2:Lifecycle.Contribute.Date When 2.3.1: Lifecycle.
Contribute. Role has value of "Publisher"
URN 1.1.1:General.Identifier.Entry 1.1.2:General.Catalog.Entry would name
the ID scheme, e.g., ISSN or ISBN
Language 1.3: General. Language Language in which intellectual content of
the resource is expressed.
Format 4.1: Technical.Format Datatype or MIME type of resource using IANA
media type vocabulary
Location 4.2: Technical.Location Using either location (URL) or method that
resolves to location (URI).
2. Resource = Part of a whole
RLI Element Name LOM Element Name Comments
Creator 2.3.2:Lifecycle.Contribute. Entity When 2.3.1: Lifecycle.
Contribute. Role has value of "Author"
Title 1.2 General Title Title for the subpart which is the Resource being
cited
Source Title 7.2: Relation.Resource Title of whole in which cited Resource
is a part. 7.1: Relation.Kind should have value "IsPartOf".
Edition 2.1:Lifecycle.Version Of Source title, if applicable.
Publisher 2.3.2:Lifecycle.Contribute.Entity When 2.3.1: Lifecycle.
Contribute. Role has value of "Publisher"
Place of Publication ? Unclear if used; may be considered unnecessary.
Date of Publication 2.3.2:Lifecycle.Contribute.Date When 2.3.1: Lifecycle.
Contribute. Role has value of "Publisher"
Volume designation, Part designation, Article Number, Starting & Ending Page
Numbers, Total pages covered 7.2.2: Resource.Description Should include the
necessary parts to the citation (volume or part number, article number,
pages, etc.) within the description. Guidelines for describing the
necessary information can be found in the ISO 690-2 standard "Bibliographic
references to electronic documents).
URN of part, if existent 7.2.1.2: Resource. Identifier. Entry 7.2.1.1:
Resource. Identifier. Catalog names the ID scheme for the number, e.g., DOI,
SICI
URN for whole, e.g., Book in which chapter is located.
1.1.1:General.Identifier.Entry 1.1.2:General.Catalog.Entry names the ID
scheme, e.g., ISSN, ISBN, DOI
Language 1.3: General. Language Language(s) in which intellectual content of
the resource is expressed.
Format 4.1: Technical.Format Datatype or MIME type of resource using IANA
media type vocabulary
Location 4.2: Technical.Location Using either location (URL) or method that
resolves to location (URI).
3. RESOURCE LIST (as an aggregation of Resources):
RLI Element Name LOM Element Name Comments
Creator 2.3.2:Lifecycle.Contribute. Entity When 2.3.1: Lifecycle.
Contribute. Role has value of "Author"
Title 1.2 General Title Title for the Resource List being created
RL Version 2.1:Lifecycle.Version Of Source title, if applicable.
Date Created 2.3.2:Lifecycle.Contribute.Date When 2.3.1: Lifecycle.
Contribute. Role has value of "Publisher"
RL Identifier. 1.1.1:General.Identifier.Entry 1.1.2:General.Catalog.Entry
names the ID scheme, if any, e.g., DOI
Language 1.3: General. Language Language(s) in which intellectual content of
the Resource List is expressed.
Kind 5.2: EducationalLearningType LOM vocabulary would use the term "index"
for a Resource List. The RLI WG may recommend the addition of a new term
for the vocabulary, called "Resource List."
Location 4.2: Technical.Location Using either location (URL) or method that
resolves to location (URI).
Rights Statement 6.3:Rights.Description Declaration of Rights Statement(s)
RL Owner wishes to make about Resource List in human readable format.
RL Owner 2.3.2:Lifecycle.Contribute. Entity Would require the addition of a
new term for the 2.3.1: Lifecycle. Contribute. Role element with the value
of "Owner. This is the person or organization to contact for re-use of the
RL, if the Rights Statement requires it. "
4. Annotation (used at either the Resource or Resource List level):
RLI Element Name LOM Element Name Comments
Annotator 8.1: Annotation.Entity Either person or organization creating the
Annotation. VCard is recommended format for information within this
element.
Annotation Date 8.2: Annotation.Date Use ISO 8601:2000 format, if possible.
Otherwise, textual description.
Annotation 8.3: Annotation.Description Content of the annotation.
Other questions, comments:
We're recommending that an OpenURL be created for each Resource or Resource
List if a persistent URL does not exist for either. All components
necessary to build an OpenURL are present in the identification /
description information above. I’ve approached a couple of OpenURL NISO
committee members to help me understand how to use the new 1.0 version of
OpenURL correctly, and they’ve offered assistance. We’re also planning to
include the information necessary to construct a DOI for a resource or
resource list, understanding that the registration of such a DOI would have
to be done more formally.
Thanks in advance for your input.
Regards,
Nancy Hoebelheinrich
***************************8
Metadata Unit Coordinator
Cataloging and Metadata Services Dept
Meyer Library 3rd Floor
Stanford University Libraries / Academic Information Resources
Stanford, CA 94305-6004
voice 650-725-6843 fax 650-725-1120
[log in to unmask]
|
