Discussion of Metadata Standards for the Items in HCLE Collection
(related pages: Catalog, Catalog Data Entry Process, Catalog Discussion, Database Team, Metadata Team, Relational Structure
HCLE metadata schemae, Metadata Research Linked open data research



Introduction

The topic of metadata turns out to be much more complicated than I first thought (says Liza Loop on May 9, 2015). The field is exploding with new taxonomies, ontologies and schemae. To keep this discussion a little better organized I'm creating a series of daughter pages. One branch will discuss the HCLE metadata schemae as it has evolved over the last several years. The other branch, Metadata Research will capture links to information from English speakers around the world who have much more know-how in this arena than I do. Under Metadata Research you will find a page devoted to Linked Open Data. Understanding linked open data is necessary to ensure that HCLE can connect disparate parts of its collection together. It also make our content discoverable via standard search engines without going through the HCLE catalog.

The rest of the page below is legacy notes from 2013-2015.

First, the type of items we have, then organizations that offer metadata standards for these items, then metadata lists, then discussion of the pro's and con's of each.

Types of Items


HCLE needs to keep track of and make discoverable:
  • Items in the archive

    • Documents
      • Academic papers
      • Letters
      • Posters
      • Listings of programs
      • Catalogs
      • Magazines
      • Journals
      • Informal notes
      • Business documents
      • Emails
      • Copies of articles published elsewhere
    • Scans of documents
    • Images on paper
    • Digitized images
    • Books (Printed)
    • Books (Digital)
    • Artifacts
      • Computer Systems
      • Computer Parts
      • Toys
      • Packaging
      • Ephemera
        • T-shirts, cups, etc.
    • Software
    • Memoirs
  • People related to HCLE

    • Staff
    • Volunteers
    • Ed Tech Pioneers
    • Authors
    • Programmers
    • Educators
    • Funders
    • Advisers
    • Collaborators
    • Members
    • Contacts (no other category)
    • ...
  • Institutions related to HCLE

    • Funders
    • Professional Associations
    • Museums, Libraries, Archives
    • Universities/Colleges
    • University Departments
    • University Research Projects
    • Commercial Research Groups
    • Software Developer Companies
    • Software Consultant Companies
    • Vendors
    • Government Agencies
    • ...
  • Published items with bibliographic information
  • Copyrights and reproduction permissions
  • Provenance and Deaccession information
  • ...

Elements/Fields in Some Metadata Standards


HCLE Fields:

Existing now (August, 2014) 92 HCLE fields for description items in HCLE collection are aimed, as any other metadata standards, to ensure the effective way of finding and retrieving an item in our collection. Since HCLE is a wiki project, it needs to track editing, preservation, and some other processes and document's features usually not described by other metadata standards.


Marc Fields:


California Digital Library (used by OAC and University of California Libraries )
ID
MARC Org Code
Other Codes
Organization Name(s)
Address
Dates
41311
CaGuLC
normalized: cagulc
ISIL: US-CaGuLC

LO*OP Center, Inc.
Variant name(s):
History of Computing in Learning and Education
16511 Watson Rd.
Guerneville, California 95446
United States
created:
2015-03-18 15:54:51
modified:
2015-03-18 15:54:51
Home » Search the Codes
The Library of Congress » Librarians, Archivists » MARC 21 Home
April 5, 2011



The MARC Organization Code you requested has been assigned. You can find your code by searching the database at:

http://www.loc.gov/marc/organizations/org-search.php

***
WHAT IS A MARC ORGANIZATION CODE FOR?

MARC organization codes are assigned for use in Machine-Readable Cataloging (MARC) records in fields 003 (Control Number Identifier), 040 (Cataloging Source), and 852 (Location). These MARC fields require a code to identify whose control number is in the record, who created/input the cataloging information, and who holds a copy of the item described in the bibliographic record. Some library systems can generate your organization code in these MARC fields automatically if you were able to supply the code to the system during installation. The MARC code in field 003 can be changed if your MARC records are ever moved to another organization's library system. The MARC codes in field 040 subfield $a (Original cataloging agency) and subfield $c (Transcribing agency) should not. If after a MARC record has been created some other organization makes a change to it, their MARC code is put in field 040 subfield $d (Modifying agency). You may have occasion to put your own MARC code in field 040 subfield $d as well, if you modify your own record.

Each organization code assigned is unique whether it is recorded using all uppercase letters, all lowercase letters, or a combination, as may be exemplified in your code(s). We recommend you record your code(s) using the same style letters (upper or lower case) as given in this confirmation message.

Each new code and information about the organization it represents will be published in the next edition of "MARC Code List for Organizations". This information will be available online at:
http://www.loc.gov/marc/organizations/

The database is refreshed to add new codes. Any questions about code assignments or names/addresses should be referred to the Network Development and MARC Standards Office (contact information given below).
ndmso@loc.gov

EAD


see this paper for overview

The Fifteen Elements of the Core Dublin Core (see Users' Guide)

The Elements:

  1. contributor
  2. coverage
  3. creator
  4. date
  5. descripton
  6. format
  7. identifier
  8. language
  9. publisher
  10. relation
  11. rights
  12. source
  13. subject
  14. title
  15. type
    Collection
    Dataset
    Event
    Image
    Interactive Resource
    Service
    Software
    Sound
    Text
Term Name: contributor
URI:
http://purl.org/dc/elements/1.1/contributor
Label:
Contributor
Definition:
An entity responsible for making contributions to the resource.
Comment:
Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
Term Name: coverage
URI:
http://purl.org/dc/elements/1.1/coverage
Label:
Coverage
Definition:
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
Comment:
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
References:
[TGN] http://www.getty.edu/research/tools/vocabulary/tgn/index.html
Term Name: creator
URI:
http://purl.org/dc/elements/1.1/creator
Label:
Creator
Definition:
An entity primarily responsible for making the resource.
Comment:
Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
Term Name: date
URI:
http://purl.org/dc/elements/1.1/date
Label:
Date
Definition:
A point or period of time associated with an event in the lifecycle of the resource.
Comment:
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
References:
[W3CDTF] http://www.w3.org/TR/NOTE-datetime
Term Name: description
URI:
http://purl.org/dc/elements/1.1/description
Label:
Description
Definition:
An account of the resource.
Comment:
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
Term Name: format
URI:
http://purl.org/dc/elements/1.1/format
Label:
Format
Definition:
The file format, physical medium, or dimensions of the resource.
Comment:
Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
References:
[MIME] http://www.iana.org/assignments/media-types/
Term Name: identifier
URI:
http://purl.org/dc/elements/1.1/identifier
Label:
Identifier
Definition:
An unambiguous reference to the resource within a given context.
Comment:
Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
Term Name: language
URI:
http://purl.org/dc/elements/1.1/language
Label:
Language
Definition:
A language of the resource.
Comment:
Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
References:
[RFC4646] http://www.ietf.org/rfc/rfc4646.txt
Term Name: publisher
URI:
http://purl.org/dc/elements/1.1/publisher
Label:
Publisher
Definition:
An entity responsible for making the resource available.
Comment:
Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Term Name: relation
URI:
http://purl.org/dc/elements/1.1/relation
Label:
Relation
Definition:
A related resource.
Comment:
Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
Term Name: rights
URI:
http://purl.org/dc/elements/1.1/rights
Label:
Rights
Definition:
Information about rights held in and over the resource.
Comment:
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
Term Name: source
URI:
http://purl.org/dc/elements/1.1/source
Label:
Source
Definition:
A related resource from which the described resource is derived.
Comment:
The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
Term Name: subject
URI:
http://purl.org/dc/elements/1.1/subject
Label:
Subject
Definition:
The topic of the resource.
Comment:
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary.
Term Name: title
URI:
http://purl.org/dc/elements/1.1/title
Label:
Title
Definition:
A name given to the resource.
Comment:
Typically, a Title will be a name by which the resource is formally known.
Term Name: type
URI:
http://purl.org/dc/elements/1.1/type
Label:
Type
Definition:
The nature or genre of the resource.
Comment:
Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
References:
[DCMITYPE] http://dublincore.org/documents/dcmi-type-vocabulary/
Errata:
  • 2013-11-05. Updated reference to ANSI/NISO Standard Z39.85-2012 of February 2013 [NISOZ3985]

Terms for the Type Element in DC

  • 1. Collection
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#collection
Label
Collection
Definition
A collection is an aggregation of items. The term collection means that the resource is described as a group; its parts may be separately described and navigated.
2. Dataset
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#dataset
Label
Dataset
Definition
A dataset is information encoded in a defined structure (for example, lists, tables, and databases), intended to be useful for direct machine processing.
3. Event
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#event
Label
Event
Definition
An event is a non-persistent, time-based occurrence. Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, responsible agents, and links to related events and resources. The resource of type event may not be retrievable if the described instantiation has expired or is yet to occur. Examples - exhibition, web-cast, conference, workshop, open-day, performance, battle, trial, wedding, tea-party, conflagration.
4. Image
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#image
Label
Image
Definition
An image is a primarily symbolic visual representation other than text. For example - images and photographs of physical objects, paintings, prints, drawings, other images and graphics, animations and moving pictures, film, diagrams, maps, musical notation. Note that image may include both electronic and physical representations.

5. Interactive Resource
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#interactive
Label
Interactive Resource
Definition
An interactive resource is a resource which requires interaction from the user to be understood, executed, or experienced. For example - forms on web pages, applets, multimedia learning objects, chat services, virtual reality.

6. Service
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#service
Label
Service
Definition
A service is a system that provides one or more functions of value to the end-user. Examples include: a photocopying service, a banking service, an authentication service, interlibrary loans, a Z39.50 or Web server.

7. Software
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#software
Label
Software
Definition
Software is a computer program in source or compiled form which may be available for installation non-transiently on another machine. For software which exists only to create an interactive environment, use interactive instead.

8. Sound
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#sound
Label
Sound
Definition
A sound is a resource whose content is primarily intended to be rendered as audio. For example - a music playback file format, an audio compact disc, and recorded speech or sounds.

9. Text
URI
http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/#text
Label
Text
Definition
A text is a resource whose content is primarily words for reading. For example - books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre text.


Achievement Standards Network

Some Common Core Educational Standards

Thoughts and Comments about HCLE Catalog Screen Views
11/7/2014
Item Number.
How does an item number form? The possible way is including a year of acquisition (or cataloging), item number of the large collection (set of items received at one time from a single source or related to each other) and the number of item in that collection, letters for certain parts of item (e.g. mouse, monitor as parts of a computer). Identifier in DCMI is usually URL. *If there is any logic in the collection, item number should reflect the structure of the collection, not just ordinal number.

Metadata crosswalk

(HCLE database fields, Dublin Core, MARC, EAD and two particular museums)
metadata crosswalk

HCLE Metadata

as of August 3, 2016 (92 fields)
Item Number
Title
Description
DescComment
SubjectTop
DonorComts
WherMade
Color
Material
Condition
ConditionNts
Fragility
Functional
Power
ToC
IsPart
IsVer
HasPart
HasVer
Creator
Publisher
Contributor
Created
Copyrighted
DateCR
Available
Medium
Type
Format
Dimensions
Extent
Type1
Moves
Resolution
Software
Still
Weight
Identifier
Model #
Serial #
Part #
Series #
Other #
ToDo
Location
Interim
Loc
ToGo
AddCom
CatBy
EditBy
AltTitle
BibCit
SubKes
Description1
Source
Relation
Conforms
Coverage
RightsMGMT
Format1
Bit-depth
Resolution1
NatLlang
ProgLang
DateScan
ProcInit
FormatBP
URI
AbIint
IntInit
InstrMeth
Audience
AudLev
Mediator
References
Is referenced by
Replaces
Is replaced by
Requires
Is required by
Access rights
Rights holder
License
Provenance
Spacial
Temporal
Accrual comments
Accrual Method
Accrual Periodicity
AccPol
Hist
HCLEItem NumberTitleDescriptionDescCommentSubjectTopDonorComtsWherMadeColorMaterialConditionConditionNtsFragilityFunctionalPowerToCIsPartIsVerHasPartHasVerCreatorPublisherContributorCreatedCopyrightedDateCRAvailableMediumTypeFormatDimensionsExtentType1MovesResolutionSoftwareStillWeightIdentifierModel #Serial #Part #Series #Other #ToDoLocationInterimLocToGoAddComCatByEditByAltTitleBibCitSubKesDescription1SourceRelationConformsCoverageRightsMGMTFormat1Bit-depthResolution1NatLlangProgLangDateScanProcInitFormatBPURIAbIintIntInitInstrMethAudienceAudLevMediatorReferencesIs referenced byReplacesIs replaced byRequiresIs required byAccess rightsRights holderLicenseProvenanceSpacialTemporalAccrual commentsAccrual MethodAccrual PeriodicityAccPolHist