<?xml version="1.0" encoding="UTF-8"?>
<Tips>
	<versionNumber>1.01</versionNumber> <!--Changed from v1.0 by LT Will Riley to remove tabs in tips which don't render properly. Tabs removed from Lines 18,19,31,36,37,38,39,47-->
	<!-- Dataset Properties -->
	<cmdUC7Tip>ANZMet features and ANZLIC metadata requirements are automatically defined by selecting a Hierarchy Level from the pick list. 
If the user changes this value at a later time it may have an impact on the required metadata values and some information already entered may be lost.
To create a Parent Metadata file navigate back to the ANZMet Explorer screen.</cmdUC7Tip>
	<!-- Title -->
	<cmdUC10Tip>More than one alternative title for the resource can be entered by typing a new line in the relevant entry window.</cmdUC10Tip>
	<!-- Key dates and language -->
	<cmdUC12Tip>Reference dates can be defined generally to a known year or month, or more accurately to a calendar date.
If more than one language is used in the resource, add multiple selections from the pick list.</cmdUC12Tip>
	<!-- Abstract and purpose -->
	<cmdUC13Tip>An abstract or summary describing the resource can be entered into the top window.
A purpose for the resource can be selected from the pick list.</cmdUC13Tip>
	<!-- Metadata author -->
	<cmdUC14Tip>Enter information about the person or organization completing this record.  Click ‘Save as default’ to preserve default metadata author details that will be populated to this screen each time new metadata is created.</cmdUC14Tip>
	<!-- Contacts and recognition -->
	<cmdUC15Tip>To save the metadata author as the resource contact choose Yes in the option box so that details don't have to be reentered.</cmdUC15Tip>
	<!-- Contact -->
	<cmdUC16Tip>Select people from the Contact list by clicking ‘Select from list’ or enter the details of the contact in the boxes provided.
Save contact information to Contact list so it can be retrieved in the future.</cmdUC16Tip>
	<!-- Recognition -->
	<cmdUC25Tip>Select people from the Recognition list by clicking ‘Add from list’ or key in the name of each contributor to a new line in the text box.  
Format is: Surname, Given Names.</cmdUC25Tip>
	<!--  History and quality -->
	<cmdUC28Tip>The purpose of "lineage" is to give the user some objective information about the history and quality of the resource to enable them to make an informed decision on fitness for purpose against their proposed use of this resource.
It describes:
● sources of information collected and incorporated into the resource to make it as it is now.
● processing undertaken on the data collection described above plus any additional data that you have added.
● collection methods (e.g., census, aerial survey) and where appropriate the tools used in data collection.

e.g., 2 m contours were derived by:
● scanning 1:10000 paper maps with 10 m contours on them
● heads up digitising of the 10 m contours
● create DEM from digitised contours
● create 2 m contours from derived DEM
Fitness for purpose is then has very low confidence in accuracy and completeness of the final record as a result of accumulated error.

e.g., A narrative of source materials used and procedures used to produce the product as well as a record of updates/changes.</cmdUC28Tip>
	<!-- Data quality test and result -->
	<cmdUC29Tip>You must select which type of test(s) were applied to the metadata, when the test was done, and details of the specification document describing the test.
NOTE: a full date is required for the date of the test, not just a year or a year/month.</cmdUC29Tip>
	<!-- Business process/function (hierarchies) -->
	<cmdUC30Tip>Use the ‘Lvls to Display’ buttons to open and close levels.
Highlight the required value and then click ‘Add’.
This value will then be displayed in the ‘Hierarchy levels in metadata’ box.
To delete a value from this box, click on the value and then click ‘Delete’.</cmdUC30Tip>
	<!-- Project identifiers -->
	<cmdUC31Tip>Project identifiers can be added either by selecting them from the list at the bottom, or by entering them directly if you cannot find the one you need in the list.  To remove one, click on it then click the Delete button.</cmdUC31Tip>
	<!-- Themes and categories -->
	<cmdUC32Tip>Select as many themes that are required that best describe the content of this resource.</cmdUC32Tip>
	<!-- Status and maintenance -->
	<cmdUC40Tip>Maintenace schedule can be defined generally to a known year or month, or more accurately to a calendar date.</cmdUC40Tip>
	<!-- Scale -->
	<cmdUC50Tip>Provide a general understanding of level of scale or resolution information used to create the dataset.</cmdUC50Tip>
	<!-- Extent information -->
	<cmdUC51Tip>Coordinates are for the bounding box to support spatial searches, and are approximate only.
The relatively small differences between GDA94, WGS84, etc. are not relevant when defining a bounding box.</cmdUC51Tip>
	<!-- Boundary polygon -->
	<cmdUC52Tip>The last point of the polygon is required to be defined as the same point as the first point.  This is automatically provided for the user's convenience under the ‘Coordinates’ box.
Coordinates are nominally in GDA94 and decimal degrees, min, sec.</cmdUC52Tip>
	<!-- Additional extent information -->
	<cmdUC55Tip>Checking and unchecking of geographic, temporal and vertical information will cause their screens to be displayed and removed from the Contents window respectively.
If a screen is removed then all data entered on the particular screen will be deleted.</cmdUC55Tip>
	<!-- Vertical extent information -->
	<cmdUC56Tip>The vertical datum field has been left as free text given the broad range of vertical datum definitions that can be defined.</cmdUC56Tip>
	<!-- Temporal extent information -->
	<cmdUC57Tip>Temporal extent can be defined generally to a known year or month, or more accurately to calendar date or time.</cmdUC57Tip>
	<!-- Geographic description -->
	<cmdUC58Tip>Descriptions can consist of a country alone. If the country is Australia, a lower-level jurisdiction can be selected from the Jurisdiction Type and Jurisdiction Value lists.  You can filter the Jurisdiction Value list by entering a word or part of a word in the Filter box - values containing the filter text will be displayed.</cmdUC58Tip>
	<!-- Defence security restrictions and use limits -->
	<cmdUC66Tip>Resource classification system and Metadata classification system can be copied and pasted if the same.</cmdUC66Tip>
	<!-- Embargoes -->
	<cmdUC69Tip>Explanatory text can be entered for each checked item.  Simply select the checked item (it will highlight in yellow) and enter data into the bottom text box.</cmdUC69Tip>
	<!-- Legal restrictions -->
	<cmdUC70Tip>Explanatory text can be entered for each checked item.  Simply select the checked item (it will highlight in yellow) and enter data into the bottom text box.</cmdUC70Tip>
	<!-- Spatial representation type -->
	<cmdUC72Tip>Select the appropriate data format from the list.
NOTE: 'grid' is equivalent to 'raster'.</cmdUC72Tip>
	<!-- Reference system -->
	<cmdUC73Tip>Reference system is only relevant to data with a spatial context. Select the appropriate projection from the drop down menu where applicable.</cmdUC73Tip>
	<!-- Schedule -->
	<cmdUC74Tip>This screen is present because you checked the "Create metadata for an Australian Government organization" option in the Settings.

Select either Schedule, Auxiliary, or Other to ensure that the metadata is valid.</cmdUC74Tip>
	<!-- Jurisdiction and search words -->
	<cmdUC75Tip>Multiple jurisdiction and search word selections can be made.
Select the relevant entries from the list(s) and click 'Add' until complete.

Jurisdiction - the region in which you have custodial responsibility for the resource being described (e.g., state or territory)

Search Words - a set of key words identified and managed by ANZLIC to assist with structured searches.</cmdUC75Tip>
	<!-- Distributor -->
	<cmdUC76Tip>This screen allows you to specify how a client can access the data described by this metadata record. The screen is optional.

Filling this screen in will activate the three linked screens where additional information on distribution format, transfer methods and ordering can be supplied.
Each of these screens is also optional.</cmdUC76Tip>
	<!-- Format for distributor -->
	<cmdUC77Tip>This screen is optional.

If you choose to enter data into this screen the Data Transfer Format and Version become mandatory.</cmdUC77Tip>
	<!-- Digital transfer options for distributor -->
	<cmdUC78Tip>This screen is optional.

If you choose to enter data into this screen the Linkage field (i.e., URL where the data is stored) becomes mandatory.</cmdUC78Tip>
<!-- Standard order process for distributor -->
	<cmdUC79Tip>This screen is optional.

Insert the relevant details on fees and terms of use, ordering restrictions and delivery times in free text in the appropriate boxes.</cmdUC79Tip>
<!-- Explorer help -->
	<cmdHelp>Unlinked Metadata is metadata created in isolation from the resource it describes. This option allows you to develop metadata as part of the design process for a project or as part of the specification of data required. It also allows you to create metadata when the resource is not immediately available.

Linked Metadata requires that a resource file is selected in the Explorer view and the resulting meatadata record is linked with the resource. Some metadata, such as title and date of last update will be derived from the resource.

Parent Metadata is metadata for a series. (The hierarchy level will be set to series.) Subsequent metadata records can be linked back to this Parent record.

Edit Metadata allows you to update existing metadata records. NOTE records created with other metadata management tools SHOULD NOT be edited with ANZMet Lite.

Delete/Rename allows you to manage existing records.

The User Guide describes the function of each button in more detail.
	</cmdHelp>
</Tips>
