innovation in metadata design, implementation & best practices

Usage Board-Holding Location Proposal

DC-Libraries Working Group

Proposal for Holding Location element

13 April 2002

This proposal is for review by Dublin Core community. It proposes a new element Holding Location that is included in the proposed DC-Library Application Profile. This review period is 15 April-11 May 2002.


 

Proposal: Holding Location
Name holdingLocation
Label Holding Location
Definition Identifies ownership of and/or the organization responsible for access to the resource.
Comment

Use for a physical location that allows the user to retrieve the item when a URI is not appropriate (e.g. for physical items not available electronically). This also facilitates access if the URI doesn't retrieve anything or only a poor substitute.

Value may be free text or use a value from a controlled list, such as the MARC Code List for Organizations. DC-Libraries Working Group will also evaluate the need for other encoding schemes, possibly a URI to an entry in an authority file.

Examples Ann Arbor (MI,USA), University of Michigan Museum of Art; DLC (using encoding scheme MARC Code List for Organizations)
Type of term Element
Term qualified  
Why needed This element is needed for description of non-electronic resources that are not Web accessible and do not have URLS. Many of them also lack universal identifiers of any kind, even ISBNs. For physical resources, a user viewing the metadata must know at a minimum which institution to approach to gain access.
Proposed status Domain-Specific
Related DCMI terms Publisher; Identifier
Related non-DCMI terms MARC Field 852 (Location); VRA element Location.Current Repository
Impact on applications This element has not been used in DCMI applications and should have no impact.
About the proposers

DC-Libraries Application Profile drafting committee list: http://www.jiscmail.ac.uk/cgi-bin/wa.exe?A2=ind0110&L=dc-libraries-ap&F=&S=&P=60

Messages in support of inclusion: http://www.jiscmail.ac.uk/cgi-bin/wa.exe?A2=ind0108&L=dc-libraries&F=&S=&P=518 (Aug. 2001)

http://www.jiscmail.ac.uk/cgi-bin/wa.exe?A2=ind0108&L=dc-libraries&P=R448 (Aug. 2001)

http://www.jiscmail.ac.uk/cgi-bin/wa.exe?A2=ind0204&L=dc-libraries&F=&S=&P=2176 (Apr. 2002)

Related terms:

DC:Publisher. Other communities have needed to supply the holding location for physical objects described using Dublin Core. CIMI filled this need for museums by adopting the Publisher element. For museum materials, which are largely unpublished, this did not create an internal conflict. However, for libraries, where the majority of resources are published, it is crucial to distinguish between the actual publisher and the holding location. (A variation on the CIMI option is to use the Contributor or Publisher elements with an appropriate Role qualifier once the technique for expressing Role is finalized.) The drawback would be the inability, in any unqualified DC systems to distinguish, for example, works by Oxford University from those held at Oxford University, with predictably bad consequences for search precision. The relationship of a holding institution to an information resource can be considered to be quite different conceptually from the relationships between other "agents" and the resource.

DC:Identifier. The definition of DC:Identifier is "an unambiguous reference to the resource within a given context." DCMES considers recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. In the case of Holding Location, applied to non-electronic resources, many lack identifiers from a formal identification system. Thus, any qualifier adopted for DC:Identifier would not refine but change the approved definition.

MARC Field 852. The proposed element is roughly equivalent to field 852 in the MARC 21 Bibliographic and Holdings Formats, which is defined as information that identifies the organization holding the item or from which it is available. It is not clear what it means to reference a MARC element in a DC profile (further discussion needed), so this approach has not been pursued.

VRA (Visual Resources Association) Core Version 3.0. The proposed element is equivalent to Location.Current Repository. Since that standard is limited to description of visual resources and the definitions convey that, it would not be appropriate to simply reference the element.

Application of this element:

Holding Location could be used with a value from an authority which would be registered as a DCMI encoding scheme or it can contain the name of the organization responsible for access. DC-Libraries WG intends to register as an encoding scheme the MARC Code List for Organizations; also to be considered is the need for other encoding schemes, possibly a URI to an entry in an authority file.

Issues with this element:

The element could be considered administrative metadata in nature (i.e. metadata used in managing and administering information resources) rather than resource discovery metadata. However, one could argue that unless you can find something, you haven't discovered much. Where a physical resource can be found is certainly as critical to successful resource discovery as Rights, for example. Rights can tell you whether you may or may not use the item. If you are permitted to use it, you will need to know where it is. See further discussion as indicated above under "about the proposers".