Base Group (2.0)

Administrative Details

Base

extensions to the model based on an organisation's administrative needs

The Administrative Details is designed to act as a 'placeholder' to allow for future extensions to the existing model. It allows for further information to be added about the Administrative Details required to maintain the other information classes outlined by GSIM.

Administrative Status

Indicator for access to an item: under review, open for use, or removed.

0..1

ControlledVocabulary

Alias

The alias or alia associated with the information class.

0..*

String

Annotation

A comment or instruction which provides additional explanations about the information class and how to use it.

0..*

String

Created Date

The date on which the information class was created.

0..1

Date

Documentation

An official document or paper that has been published by an organisation.

0..*

String

Last Updated Date

The date on which the information class was last changed.

0..1

Date

Life Cycle Status

Indicator for the quality of an item: incomplete, valid, superseded, or retired.

0..1

ControlledVocabulary

Url

Allows location of the information class. Distinct from the identification of the class as handled by the identifier attribute in Identifiable Artefact.

0..*

String

Valid From

The start date included in the period during which the classis effective or valid. It is effective or valid from that date.

0..1

Date

Valid To

The end date included in the period during which the information classis effective or valid. It is no longer effective or valid after that date.

0..1

Date

Agent

Base

someone or something that plays an active role in the lifecycle of an Identifiable Artefact

An Agent may be an Individual, an Organisation (or part of it) or a Software Agent that affects in some way an instance of a GSIM class. For example, an Agent can play a role in the execution of a Business Processes or in the way a Statistical Classification (or a Concept) changes over time.

Change Event

Base

indication of the occurrence of a change to an Identifiable Artefact

A Change Event relates to the information class(es) that has(have) been affected. It can be applied to only one Identifiable Artefact and result in one or more Identifiable Artefact(s). On the other hand, a Change Event can be applied to more than one Identifiable Artefact and result in only one Identifiable Artefact.

Change Date

The date on which the Change Event occurred.

1..1

Date

Change Type

The type of change that occurred during the Change Event.

1..1

String

Identifier

The unique identifier of the Change Event that is applied to an information class; assigned by the owner agency.

1..1

String

Contact

Base

Role in which Individual(s) is(are) responsible for providing additional information about an information class and/or its metadata, either directly or indirectly by linking to its source

Change Event

Base

abstract class that comprises the basic attributes and associations needed for identification, naming and other documentation

All GSIM classes except Administrative Details, Agent In Role, Change Event, Datum, Process Input (and its sub-types) and Process Output (and its sub-types) are a sub-type of Identifiable Artefact. In SDMX, “Identifiable Artefact” is defined as “construct that contains structures capable of providing identity to an object”.

Description

The description of the information class.

0..1

MultilingualText

Id

The unique identifier of the information class; assigned by the owner agency.

1..1

String

Local ID

This is an identifier in a given local context that uniquely references an information class. For example, Local ID could be a variable name in a dataset.

0..1

String

Name

A term which designates a concept, in this case an information class. The identifying name will be the preferred designation. There will be many terms to designate the same information class, such as synonyms and terms in other languages.

1..1

MultilingualText

Version

The version designator of the information class assigned by the owner agency.

0..1

String

Version Date

The date on which the version was created. 

0..1

Date

Version Rationale

The reason for making this version of the information class.

0..1

String

Individual

Base

person who acts, or is designated to act towards a specific purpose

Maintainer

Base

Role in which a unit or group of persons within the Organisation is responsible for managing an information class and its metadata

A unit or group of persons with the role of Maintainer is responsible for all administrative and operational issues relating to one or a set of information classes and its metadata (e.g. adding, modifying or deleting metadata about an information class). It is answerable to all stakeholders for all issues related to the information classes under its responsibility. A Maintainer is not a decision-making body. Decisions are made collaboratively among the owners of the artefact.

Organisation

Base

unique framework of authority within which a person or persons act, or are designated to act, towards some purpose

Organisation represents a collection of people organised together, often with hierarchical structures. Examples of Organisation: national statistics office, international agency

Owner

Base

Role in which a statistical office, authority or other organisation is responsible for defining, specifying, creating and making decisions about the maintenance of a class and/or its metadata

Some information classes may have several Owners.

Role

Base

function assumed by an Agent

Part played by an Individual, an Organisation (or part of it) or a Software Agent in a particular situation. Examples: Contact, data steward, scheduler. Role can be maintained by a controlled vocabulary (e.g. RASCI).

Software Agent

Base

software that carries out Process Step based on Process Control

Examples: google bot

PROV “Software Agent”, DDI “Machine”