"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Adding a Vocabulary Service into GeoNetwork

Contents


Overview:

Adding a Vocabulary Service to a GeoNetwork instance is manual. Any changes or updates made to vocabulary service will require the user to manually update the record in GeoNetwork.

Procedure:

Below is a list of the fields, their description, the approach to insert the data and examples to accomplish this.

Section: Identification Info

Field Title
Description Name by which the cited resource is known as
Direction Under the Identification Info field, give your service a name. Use free text to describe your service here.
Example SISSVoc Vocabulary Service
Source From the custodian of the service
Obligation highly recommended

Field Date
Description the exact date of creation, publication or revision on your map
Direction Indicate the exact date of creation, publication or revision on your map
Example 2011-01-31T13:21:00
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Date Type
Description The Type of Date
Direction Indicate the type of date used; creation, publication or revision
Example Creation: Date identifies when the resource was brought into existence
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Presentation Form
Description How the data is presented, eg Map, digital documentation
Direction Specify the type of presentation, i.e. digital, hard copy, table, etc.
Example Digital document: Digital representation of a primarily textual item (can contain illustrations also)
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Abstract
Description Brief narrative summary of the content of the resource.
Direction Enter some description of the map
Example

The Spatial Information Service Stack Vocabulary Service provides formal specification of shared Earth & Environmental Sciences domain conceptualisation (also known as “ontologies”), and a web service interface (API) for querying and navigating these concepts and their relationships.

In developing the SISS Vocabulary Service (SISSVoc), we adopted Australian and international standards of geosciences thesauri and terminologies, formalised their encoding in SKOS/RDF, and stored them in a triple store accessible with any web browser.

Clients maintain a mapping of the terms from their database to the community agreed controlled concepts in SISSVoc. This allows for efficient reconciliation of heterogeneous geodata sources in similar or related data store and makes related geodata to be interoperable within the AuScope Discovery portal.

Source From the custodian of the dataset.
Obligation highly recommended

Field Purpose
Description The reason for the existence of the portal
Direction Enter a short summary of the purposes for your map to be developed.
Example To allow user to access a Vocabulary Service.
Source From the custodian of the dataset
Obligation Optional

Field Status
Description The current status of the dataset.
Direction Specify the status of your map within the following options: completed, historical archive, obsolete, ongoing, planned, required, under development.
Example On going: Data is continually being updated
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Point of Contact
Description Party that is responsible for the dataset information
Direction Enter all mandatory information and others you have at hand for the contact of the person(s) associated with this resources of the map. Note that some fields are only conditionally mandatory, such as Organization Name if Individual Name and Position are not entered.
Example

Individual name

Terry Rankine

Organisation

CSIRO

Role

Point of contact: Party who can be contacted for acquiring

knowledge about or acquisition of the resource

Voice

61 8 6436 8601

Facsimile

61 8 6436 8555

Delivery Point

26 Dick Perry Ave

City

Kensington

Administrative area

WA

Postal code

6151

Country

Australia

Electronic mail address

Terry.rankine@csiro.au

Source From the custodian of the dataset or from the portal deployment team
Obligation mandatory or highly recommended

Field Maintenance and update frequency
Description how often is the dataset updated
Direction Specify the frequency with which you expect to make changes and additions to your map after the initial version is completed. If any changes are scheduled you can leave As Needed selected from the drop-down list.
Example As needed: Data is updated as deemed necessary
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Descriptive keywords
Description Commonly used words(s) or formalised word(s) or phrase(s) used to describe the subject
Direction Enter keywords that describe your map. Also specify the type of keyword you are entering, i.e. place, theme, etc. Remember that you can add another keyword field if you need to add different types of keywords.
Example Vocabulary (theme)
Source From the custodian of the dataset
Obligation highly recommended

Field Access constraints
Description Access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource
Direction Enter an access constraint here, such as a copyright, trademark, etc. to assure the protection of privacy and intellectual property.
Example Copyright: Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor
Source From the custodian of the dataset
Obligation mandatory or highly recommended

Field User Constraints
Description User constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource
Direction Enter a user constraint here to assure the protection of privacy and intellectual property.
Example N/A
Source From the custodian of the dataset
Obligation Optional

Field Other Contraints
Description Any Other constraints that applies to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource
Direction Enter other constraint here to assure the protection of privacy and intellectual property. Note that this field is conditionally mandatory if Access and Use constraints are not entered.
Example N/A
Source From the custodian of the dataset.
Obligation Optional

Field Spatial representation type
Description How the spatial information are represented.
Direction Select, from the drop-down list the method used to spatially represent your data. The options are: vector, grid, text table, stereo model, video. Do note that even though the Vocabulary service doesn't contain spatial data, we include this information as dummy data.
Example Vector: Vector data is used to represent geographic data
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Equivalent scale
Description Level of detail expressed as the scale denominator of a comparable hardcopy map or chart
Direction Enter the denominator for an equivalent scale of a hard copy of the map. Do note that even though the Vocabulary doesn't contain spatial data, we include this information as dummy data.
Example

Denominator:

100000

Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Language
Description The language used in the resource.
Direction Select the language used within your map
Example English
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Character set
Description Dataset character set.
Direction Select the character set used within your map
Example UTF8: 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Topic category code
Description The <ISO_Topic_Category> field is used to identify the keywords in the ISO 19115 - Geographic Information Metadata (http://www.isotc211.org/) Topic Category Code List. It is a high-level geographic data thematic classification to assist in the grouping and search of available geographic data sets.
Direction Specify the main ISO category/ies through which your map could be classified.

Do note that even though the Vocabulary doesn't contain spatial data, we include this information as dummy data.

Example Boundaries
Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Extend
Description extent information including the bounding box, bounding polygon,
vertical, and temporal extent of the dataset
Direction Enter the longitude and latitude for the map or select a region from the predefined drop-down list. Make sure you use degrees for the unit of the geographic coordinates as they are the basis for the geographic searches.

Do note that even though the Vocabulary doesn't contain spatial data, we include this information as dummy data.

Example

North

-10.1357

South

-54.7539

East

158.96

West

112.907

Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Field Supplemental Info
Description Additional Information
Direction Enter any other descriptive information about your map that can help the user to better understand its content.
Example N/A
Source From the custodian of the dataset
Obligation Optional

Section: Distribution Information

Field Transfer options
Description Resource Locator
Direction

Enter information about online resources for the map, such as where a user may download it, etc. This information should include a link, the link type (protocol) and a description of the resource.

Example

http://services.auscope.org/SISSVoc/client/ (Web URL)

SISSVoc Client

CLIENT Web APP

http://services.auscope.org/SISSVoc/

(Web URL)

Service

Service API

Source From the custodian of the dataset or from the portal deployment team
Obligation highly recommended

Section: Reference System Information

Field Code
Description

The spatial and temporal reference system used

Direction Describe the spatial and temporal reference system used. Do note that even though the Vocabulary doesn't contain spatial data, we include this information as dummy data.
Example WGS 1984
Source From the custodian of the dataset.
Obligation highly recommended

Section: Data Quality Info

Field Hierarchy level
Description Scope to which dataset applies.
Direction

Specify the hierarchal level of the data (dataset series, dataset, features, attributes, etc.) and provide a general explanation on the production processes (lineage) used for creating the data. The statement element is mandatory if the hierarchical level element is equal to dataset or series. Detailed information on completeness, logical consistency and positional, thematic and temporal accuracy can be directly added into the advanced form.

Example Service: Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case
Source From the custodian of the dataset.
Obligation highly recommended

Section: Metadata

Field File Identifier
Description File identifier of the metadata to which this metadata is a subset
Direction Auto Populated?
Example 8a618f41-03e8-407a-ada0-700b336bef3a
Source Auto Populated
Obligation highly recommended

Field MetaData language
Description Language used for documenting this metadata
Direction Enter Language used for documenting this metadata
Example English
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Character set
Description The metadata character set used.
Direction Enter the metadata character set used.
Example UTF8: 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Date stamp
Description The date that the metadata was created.
Direction Enter the date that the metadata was created.
Example 2011-06-09T12:58:37
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Metadata standard Name
Description The standard that is used for the metadata
Direction Enter the standard that is used for the metadata
Example ISO 19115:2003/19139
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Metadata standard Version
Description The version of the standard that is used for the metadata.
Direction Enter the version of the standard that is used for the metadata.
Example 1.0
Source From the custodian of the dataset or from the portal team
Obligation highly recommended

Field Point of Contact
Description Party that is responsible for the dataset information
Direction Enter all mandatory information and others you have at hand for the contact of the person(s) associated with this resources of the map. Note that some fields are only conditionally mandatory, such as Organization Name if Individual Name and Position are not entered.
Example

Individual name

Terry Rankine

Organisation

CSIRO

Role

Point of contact: Party who can be contacted for acquiring

knowledge about or acquisition of the resource

Voice

61 8 6436 8601

Facsimile

61 8 6436 8555

Delivery Point

26 Dick Perry Ave

City

Kensington

Administrative area

WA

Postal code

6151

Country

Australia

Electronic mail address

Terry.rankine@csiro.au

Source From the custodian of the dataset or from the portal deployment team
Obligation mandatory or highly recommended

Summary:

Reference:

http://inspire.jrc.ec.europa.eu/documents/Metadata/INSPIRE_MD_IR_and_ISO_v1_2_20100616.pdf

http://gcmd.nasa.gov/User/difguide/https://www.seegrid.csiro.au/subversion/xmml/metadata/ANZLIC_1_0/documents/19115-IS.pdf

http://geonetwork-opensource.org/manuals/trunk/users/quickstartguide/new_metadata/index.html#entering-metadata-for-your-map

http://mest.ivec.org/geonetwork/srv/en/metadata.show?id=1547http://geonetwork-opensource.org/stable/users/admin/harvesting/index.html

https://www.seegrid.csiro.au/subversion/xmml/metadata/ANZLIC_1_0/documents/19115-IS.pdf

http://geonetwork-opensource.org/stable/users/admin/harvesting/index.html


 

 
Topic revision: r3 - 07 Sep 2011, DerrickWong
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).