Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

There are two primary locations for metadata documentation:

a) Metadata Wiki

b) Digital Collections Wiki (not open)

Some metadata documentation may be maintained on project specific wikis, such as the Durst Collection Wiki, though those are generally linked to from the Metadata Wiki.

The Metadata Wiki contains project specific documentation on the CU Digital Projects Metadata Documentation page. This includes data dictionaries, metadata mapping tables, meeting minutes, etc. 

A Table of Core CUL Metadata elements was created in Dec. 2012: https://wiki.cul.columbia.edu/display/metadata/Table+of+Core+CUL+Metadata+Elements

This table is MODS-based since this is the primary non-MARC schema used by Columbia University Libraries. 

More information on Columbia's Columbia’s MODS usage can be found in the MODS Implementation Registry.

...

The current process of metadata consultation and review was not in place when Omeka was implemented in 2009. The Metadata Coordinator and Metadata Assistant are now remediating the older exhibitions.

Customer orders:

"Customer “Customer orders metadata" metadata” is generated by digitization requests by internal or external patrons to Columbia University Libraries. These requests include among other types of resources: Single pages from books and periodicals, photographs, art objects, archival materials, and complete publications. While this is not metadata that is being displayed to the public, the images are loaded into the Fedora Staff Collection Viewer. The metadata has to conform to a minimal level of consistency to allow for the management of these digital images. The metadata is being created by staff in the Preservation and Digital Conversion Division. The Metadata Coordinator and the Digital Projects Librarian created a list of required elements and a data dictionary.

...

Digital Projects are web initiatives that require advanced functionality (e.g., specialized searching, browsable indexes).  The objects in these projects come from Columbia Libraries' Libraries’ special collections. The G.E.E. Lindquist Native American Photographs http://lindquist.cul.columbia.edu/ or the recently launched Community Service Society Photographs http://css.cul.columbia.edu/ are two such examples. 

...

https://wiki.cul.columbia.edu/display/webresourcescollection/Policies+and+procedures.

Archives:

EAD finding aids are created outside technical services. Archival collections can be found via the Archival Collections portal.

...

Hyacinth is a proposed tool to support creation and editing of non-MARC metadata and will serve as a front end to Columbia's Columbia’s Fedora repository. There is an agreed upon data dictionary from which data elements can be selected for specific application profiles. Records will be able to be output in a number of schemes, including, but not limited to, MODS.  This tool will support work on Customer Orders, Omeka exhibitions, and digital projects. A plan of work was drafted in Oct. 2012. Implementation will proceed when development time allows.

...

eCommons@Cornell is Cornell University Library's Library’s DSpace-based institutional repository that provides long-term access to the intellectual output of of Cornell's Cornell’s faculty, staff and students. Content is primarily user-submitted and Dublin Core metadata are collected and during deposit. Metadata guidelines are available for user submissions, http://ecommons2.library.cornell.edu/eCommons_Best_Practices.pdf

...

Documentation for CULAR is not yet written; workflows and level/types of required metadata are still being decided. A CUL-only wiki is available that references metadata and there is a template to capture collection-level descriptive metadata.

CuLLR (https://confluence.cornell.edu/display/culwebdev/CuLLR)

The CuLLR (Currated List of Library Resources) team is charged to design and implement a process whereby print and electronic resources in the library catalog (in the form of metadata), and from other sources to be determined, are extracted in accordance with the subject areas for a specific library. These resources may then be annotated to identify the subject areas for which the resource is useful and other attributes as determined by the project team. 

...