This shows you the differences between two versions of the page.
- | Both sides previous revision Previous revision Next revision |
- | public:metadata [2017/11/16 10:04] penhleak [Guidelines for creating accurate metadata] |
---|---|
+ | Previous revision |
+ | public:metadata [2020/10/09 02:55] (current) mchung [Guidelines for creating accurate metadata] |
@@ Line -8,5 +8,5 @@ | |
==== What this guide teaches ==== | |
* What is | |
* Guidelines for creating an accurate metadata | |
* Open Development metadata templates | |
@@ Line -17,4 +17,6 @@ | |
Imagine you had a present for someone. | |
Without having to tear the wrapping papers and open the box, a label with written note attached can tell you what they are going to get. | |
A carefully wrapped present with out a label might add excitement for the gift recipient, but data without a metadata is not usable. Data is simply number and figures. Data doesn’t mean anything without a description, a metadata. | |
For CKAN purposes, data is published in units called “datasets”. A dataset is a parcel of data - for example, it could be the crime statistics for a region, the spending figures for a government department, or temperature readings from various weather stations or a reference document. | |
@@ Line -28,5 +30,5 @@ | |
Example: [[https://opendevelopmentmekong.net/dataset/?id=hydro-basins-level-6-greater-mekong-subregion-laos-myanmar-thailand-vietnam-cambodia&search_query=P3M9aHlkcm9iYXNpbiZ0eXBlPWRhdGFzZXQmcGFnZT0w|Hydrobasins level 6 dataset on OD Mekong]] | |
{{ : | |
Metadata provides important context about an informational asset’s source and manner of creation, as well as in what applications or environments the asset is relevant. | |
@@ Line -46,9 +48,9 @@ | |
We aim to produce, to the best of our ability, an accurate metadata by describing the extent of our knowledge about the asset/resource. A good metadata should clearly state what is known about the resource and what is not known or problematic. Metadata changes when the asset itself or knowledge about its condition changes. | |
If information is missing or inconsistent, describe the known inconsistencies or gaps instead of disregarding the resource. Mention any steps being taken to address these issues, along with an expected timeline. **[THIS INSTRUCTION IS UNDER REVIEW] | |
** | |
==== Open Development Platform metadata templates ==== | |
For each different type of data, there are specific terms that relate to that type of data. On the Datahub 4 different types of datasets, each requires its own metadata template, are currently stored/administered: | |
* Dataset (both spatial and non-spatial) | |
@@ Line -57,200 +59,27 @@ | |
* Agreement records (for contracts) | |
These metadata templates | |
The templates below outline information that should be included and offer instruction for each metadata field. | |
==== Metadata for dataset (both spatial and non-spatial) ==== | |
==== Metadata template for library publications ==== | |
==== Metadata template for law and policy documents ==== | |
==== Metadata for agreement documents (contracts) ==== | |
Other metadata fields exposed by the CKAN API: |