Service Tab

Note: Only visible when editing Service Metadata records

The Service tab holds most important additional metadata elements needed for a service resource. It consist of two sections:

• Service
• Contains Operation

When creating metadata for services, it is recommended that one metadata record be created for each service type provided by the resource. If a service offers a viewer and an API for data delivery, separate metadata records Should be provided for each.

Service

Service Type

A name identifying the type of service provided by the described resource

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/ServiceType
• One Service type entry Must be populated in a service metadata record.
  • The value of this field Should be populated with a selection from the provided “Recommended values” dropdown.
  • If necessary, other values can be entered as free text.

Service Type Version

Provides search based on the value of the service type

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/ServiceTypeVersion
• One or more service type versions Should be provided if useful to allow discovery and use of resources based on the version of the service provided.

Coupling Type

Documents the relation of the service to associated data

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/CouplingType
• One selection Must be made from the three options provided in the dropdown - “Tight”, “Loose” or “Mixed”.
  • For tight couplings, a coupled resource Must be provided using the “Link to a dataset” button in the “Thumbnails & Distributions” sidebar section.

Contains Operation

Operation Name

A unique identifier for this interface

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/ContainsOperations.html
• A name for the operation Must be provided in the provided text field.

Distributed computing platform (DCP)

DCP on which the operation has been implemented

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/ContainsOperations.html
• One value Should be selected from provided dropdown.

Operation Description

Free text description of the intent and results of the operation

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/ContainsOperations.html
• Provided text entry field Should be populated with a short description of the purpose of the service.

Connect point

Address for connecting to the described service interface

• ICSM Guidance - https://icsm-au.github.io/metadata-working-group/defs/ContainsOperations.html
• Consist of the following fields:
  • URL - The address of the service endpoint Must be entered here.
  • Protocol - The protocol of the service Should be populated using the dropdown to the right of this field.
    • Free text entry maybe used if the appropriate protocol is not in the list.
  • Function - A value Should be selected from the dropdown that aligns with the service purpose.
• If additional connect points are needed for a service, the Connect point “+” button will allow additional entries.

  Note: Not Recommended - Addition operations provided by a service can be documented by clicking on the Contains Operation “+” button.