Kuali OLE

Process Module: Describe Entity

Process Title: Create Metadata

Definition: The process used to generate information about an entity. Entities can include resources, collections, people, organizations, services, events, courses, facilities, finances, relationships, etc.  Entities can be electronic/digital or physical. Entities can be held/maintained locally or remotely.  Metadata will identify the entity and can be descriptive, structural, technical, and/or administrative.  Metadata can be created in real-time or via a batch process.  Metadata will generally be encoded using XML and will generally conform to an identified metadata content standard.  The Obtain Metadata Process is independent of application end point, resource, data object, or underlying communications protocols and service models.

Workflow / Process Diagrams:

Use Cases: Metadata is created (using templates, extraction tools, mark-up tools, conversion tools) for: resource discovery (what is available, where it is located and how it is used), supporting the management of resources by administrators or curators, ensuring the long-term maintenance and availability of resources, recording provenance, ownership, copyright, access conditions, etc.

Metadata being created may include descriptive, holdings, authority, financial, structural, and administrative or other types of data.

Reference(s):

1. (NLA Services Framework 6.5: Describe) “Process where metadata for an entity that has been selected for acquisition or trial, either permanently or temporarily, is selected, imported, validated and saved. https://wiki.nla.gov.au/display/LABS/3.+Service+framework(v. 0.91, p. 35/46)
2. (NLA Services Framework 7.1: Register) “Add metadata to a registry.” https://wiki.nla.gov.au/display/LABS/3.+Service+framework(v. 0.91, p. 41/46)
3. (e-Framework Service Genre: Add) “This Service Genre has been prepared from a number of disparate projects and work. This Service Genre has been developed to provide a description of the behaviors required when a service wishes to offer functionality allowing for the creation, update and deletion of data items within collections of like data.” http://www.e-framework.org/Services/ServiceGenres/ServiceGenreRegistry/Add11/tabid/843/Default.aspx
4. (e-Framework, Service Genre – Generate Metadata)  “The generate metadata service genre defines how to generate a metadata object, encoded in an XML document, containing basic cataloging and descriptive metadata for/from a content object.  The metadata object SHALL conform to an identified metadata standard.  This service genre is applied to a content object which SHALL conform to an identified content object standard.”
   This is a general description of a generate metadata service genre, independent of application end point, resource, data object, or underlying communications protocols and service models.  The service genre includes the notion of generating metadata for different types of objects, in different metadata schemes and in different file formats; it is not otherwise dependent on a data model.  The service genre includes a mechanism to authenticate clients.  The service genre does not include authorization methods to control the return and filtering of results.
5. (e-Framework: Service Genre: Validate) Check whether a business object meets specified conformance requirements http://www.e-framework.org/Contributions/ServiceGenres/tabid/987/Default.aspx
6. (CollectionSpace: Cataloging Requirements)  “The compilation and maintenance of key information, formally identifying and describing objects. It may include information concerning the provenance of objects and also collections management documentation e.g. details of acquisition, conservation, exhibition and loan history, and location history. It need not bring together in one location everything known about an object, but should provide cross references to any other relevant information source known to the organisation.”