Do not use Location to record the data coverage (temporal/spatial) of a registry object. Use the Coverage element instead.
Location should also not be used to record the repository in which a collective work is held. Instead use an instance of RelatedObject with a Relation Type of "isLocatedAt".

Meaning and purpose

Location is a wrapper for Address and Spatial elements, describing the physical and/or electronic location(s) of a registry object, with the purpose of enabling access to the object. Each Location element should contain information about a single entity; however, the Location element can be repeated. The location information recorded will vary according to the class of entity being described (collection, party, activity or service). 

Location contains the following child elements:

Spatial location is less commonly used, since electronic and physical addresses fulfill the purpose of enabling access more directly.

Where the address has changed and older addresses have been recorded in the metadata being provided, the time period for which the location information was current can be specified using DateFrom and DateTo attributes.

Location attributes

Location Type

The Location Type attribute is not currently used in the RDA Registry.

Date From and Date To attributes

Optionally, record the time period for which the location information was current using the DateFrom and DateTo attributes. This is only applicable where the location has changed over time and older versions of the location have been recorded in the metadata being provided. A single date or a range of dates can be provided and may include both start and end dates or an open ended date. Dates should be UTC and of one of the forms described in section 3.2.7 of the W3C Schema Data Types document

Use in Research Data Australia

Location information is displayed in Research Data Australia for use in accessing collections or services, contacting parties, or obtaining more information about research domain activities or entities. 

URLs are displayed as active hyperlinks and on collection view pages, these are accessed via the "Access the data" button.

Email and physical addresses display under "Contact Information" in records in Research Data Australia, or on a map in the body of the page if information is provided in the Spatial element.

Dates provided within Location are not displayed or searchable.

Best practice

Only location information that provides access to the object, or aids in the discoverability of the object or in assessing its value, should be recorded. If other location information is readily available and more easily maintained elsewhere, do not record it in the RDA Registry.

Electronic addresses are preferred over physical addresses or spatial locations.

Recording multiple locations

The Location element is a wrapper element that contains repeatable child elements: Address and Spatial. The child element Address is also a wrapper element that contains the Electronic and Physical address elements. The separation between the elements exists to allow different formatting to be used for the different kinds of locations—URIs for electronic addresses, text for physical addresses, and spatial coordinates for geospatial locations.

To describe multiple locations:

Locations for collections

Locations for services

Locations for activities 

Locations for parties

 

In RIF-CS v1.0.1 temporal and spatial coverage was provided using the Location element. The information below applies only to those users. Upgrade of feeds to the current version of RIF-CS is recommended to take advantage of schema enhancements and the new Research Data Australia display.

Spatial coverage was recorded in a Location element, with type="coverage".

<location type="coverage">
 <spatial type="iso19139dcmiBox">northlimit=-20.4; southlimit=-21; westlimit=115.2; eastLimit=115.6; projection=WGS84</spatial> 
</location>

XML encoding examples

<location>
	<address>
		<electronic type="url" target="landingPage">
			<value>http://uni.edu.au/repo/one</value>
		</electronic>
		<electronic type="email">
			<value>sarah.smith@uni.edu.au</value>
		</electronic>
		<physical type="streetAddress">      
			<addressPart type="addressLine">798 Palmer Street</addressPart>
    		<addressPart type="addressLine">Townsville QLD 4810</addressPart>
		</physical>
	</address>
</location>

<location dateFrom="1997-01-01T00:00:00Z" dateTo="1997-12-31T23:59:59Z">
	<address>
	<physical type="streetAddress">      
		<addressPart type="addressLine">798 Palmer Street</addressPart>
    	<addressPart type="addressLine">Townsville QLD 4810</addressPart>
    	<addressPart type="addressLine">Australia</addressPart>
	</physical>
	</address>
</location>
 

Syntactically and semantically equivalent examples:

<location>
  <address>
   <electronic type="url"><value>http://uni.edu.au/one</value></electronic>
   <electronic type="url"><value>http://uni.edu.au/two</value></electronic>
  </address>
</location>
<location>
  <address>
   <electronic type="url"><value>http://uni.edu.au/one</value></electronic>
  </address>
  <address>
   <electronic type="url"><value>http://uni.edu.au/two</value></electronic>
  </address>
</location>

 

 

Change history

DateChange history

April 2010

Consultation draft

26 Oct 2010

With the introduction of RIF-CS v.1.2.0 , the following changes to the location element were made:

  • Telephone and fax numbers are described as part of Physical Address instead of Electronic Address

  • A separate Coverage element is available for describing spatial and temporal coverage

25 Jan 2011

Link to new information about recording locations for services added

15 Feb 2012

Simplified layout and separated content relating to RIF-CS v1.0.1, added advice about XML using location wrapper

18 July 2017

Content reviewed and updated. Advice on recording multiple locations revised.

27 Jul 2018Changed the reference to the "Go to Data Provider(s)" button in RDA to the "Access the data" button.