Clayphan, Robina wrote:
> Thanks Pete,
>
> The DC-Lib definition for Location is:
> "Identifies the organization holding the resource or from which access
> is obtained"
>
> The DC-Lib Comment is:
> "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. Can also contain further
> identification within a location such as call number, accession
> number."
>
> The term seems to be included for physical access reasons and we
> therefore *do* want to talk about the place/repository as defined in
> the Heaney model. The distinction between the organisation and the
> location does become blurred because the value for the term could be the
> name and address of the holding organisation or an organisation code
> with other details recorded in the metadata related to the code.
OK.... I think the DC CD property would indeed do the job then. But I
think the "value string" really is "representing" the location/place,
even if that same string happens also to be the name of an organisation.
"Identifies the organization..." sends a slightly confusing message, so
maybe that DC-Lib definition string might be tweaked a little bit. I
guess I'm splitting hairs (surely not! ;-)) but it does help remove any
ambiguity.
(I'm not sure what the comment about a URI being a poor substitute means
but that's a separate question!)
Pete
--
Pete Johnston
Research Officer (Interoperability)
UKOLN, University of Bath, Bath BA2 7AY, UK
tel: +44 (0)1225 383619 fax: +44 (0)1225 386838
mailto:[log in to unmask]
http://www.ukoln.ac.uk/ukoln/staff/p.johnston/
|