Metadata Definitions and Requirements
The following tables describe the metadata standards used by Data.gov.au.
Create Dataset (Page 1)
| Term Name | Term Definition | Required Field |
|---|---|---|
| Title | The title or name given to the dataset. | Yes |
| URL | The online location of the dataset. | Yes |
| Description | Notes about the dataset and what it contains. | Yes |
| Keywords | A description of the content and/or components of the dataset. | No |
| License | License details giving official permission to use the dataset. | No |
| Unpublished | Metadata stays at draft status; therefore, Users will not be able to view the dataset resources. | No |
| Organisation | The agency or division responsible for publication of the data represented in the dataset. | Yes |
| Visibility | Public: Dataset is visible to all Users/Custodians. Private: Dataset is only visible to Organisation/Custodian responsible for dataset. | No |
| Coverage | Geographical area covered by the data. | No |
| Reference Period From: | The date in which the dataset begins. | Yes |
| Reference Period To: | The date in which the dataset ends. | No |
| Language | The language the data set is presented in, default language is English. | No |
| Data Custodian | The agency; division; department that shares the dataset, if different from the Organisation. | No |
| Point of Contact | Contact email address for questions about content of published dataset. | Yes |
| Geospatial Topic | The high level ISO1 9115 topics (drop down box). | No |
| Archive | Whether the data is no longer updated but is still published. | No |
Add Data (Page 2)
| Term Name | Term Definition | Required Field |
|---|---|---|
| File | Upload: Manually uploading dataset file. Link: Adding link to API dataset URL. | No |
| Name | Name of the resource. | No |
| Description | Useful information explaining the content of the resource. | No |
| Format | The file type of the resource that is uploaded. | No |
| Extract Resources from Zip Files | Whether any files inside zip files should be extracted into separate resources. | No |