Login required to access the wiki. Please register to create your login credentials We apologize for any inconvenience this may cause, but please note that this step is necessary to protect your privacy and ensure a safer browsing experience. Thank you for your cooperation. Documents available for download: GAMSO , GSBPM , GSIM |
Exchange Group is used to catalogue the information that is exchanged within and outside of a statistical organisation.
The UML diagram for this group, as well as definitions and explanatory text can be found below.
For the comparison with the previous version of GSIM (v1.2), the main changes to the model include:
GSIM information class added: 1) Register; 2) Exchange Specification; 3) Dissemination Instrument;
GSIM information class removed: 1) Administrative Register; 2) Statistical Register; 3) Protocol
GSIM information class renamed: Exchange Instrument (previously Exchange Channel in GSIM v1.2)
Data Harvest
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Data Harvest | Exchange | Exchange Instrument to pass information between two sources, usually by a machine to machine mechanism | Examples of Data Harvest include web scraper, API (e.g., to acquire data from administrative sources), scanner, sensor, etc. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Dissemination Instrument
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Dissemination Instrument | Exchange | Exchange Instrument to disseminate information | Examples include: API or web services for data dissemination |
Attributes*
* Attributes inherited from super-type(s) are not included here
Exchange Instrument
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Exchange Instrument | Exchange | concrete and usable tool to exchange information | The Exchange Instrument is a tool to receive or send information and is used for external and internal purposes. Different Exchange Instruments are used for data acquisition and dissemination. An example of Exchange instrument for receiving information is Questionnaire. An example of Exchange Instrument for sending information is Dissemination Instrument. Additional Exchange Instruments can be added to the model as needed by individual organisations. |
Attributes*
Name | Description | Cardinality | Value Type |
Direction | Direction of the Exchange Instrument: acquire or disseminate. | 1..1 | String |
* Attributes inherited from super-type(s) are not included here
Exchange Specification
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Exchange Specification | Exchange | outline or description specifying the design of the Exchange Instrument | GSBPM Phase 2 (Design) results in an Exchange Specification that specifies the design of the data acquisition or dissemination instruments (e.g., Questionnaire, web page). In GSBPM Phase 3 (Build), these instruments are built based on the tools. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Information Consumer
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Information Consumer | Exchange | Role that entails consuming data and information | The Information Consumer accesses a set of information in a Product that is made available via a Dissemination Instrument. The Information Consumer subscribes to the Provision Agreement, which sets out conditions of access. The Information Consumer can be defined in a broad sense with a persona concept (group of Individuals) without specific details. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Information Provider
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Information Provider | Exchange | Role that entails providing data and information | An Information Provider possesses sets of information (that it has acquired, for example by collecting or purchasing it) and is willing to supply that information (data or referential metadata) to the statistical organisation. The two parties use a Provision Agreement to agree on the Data Structure and Referential Metadata Structure of the data to be exchanged via an Exchange Instrument. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Instance Question
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Instance Question | Exchange | use of a Question in a particular Questionnaire | The Instance Question is the use of a Question in a particular Questionnaire Component. This also includes the use of the Question in a Question Block, which is a particular type of Questionnaire Component. |
Attributes*
Name | Description | Cardinality | Value Type |
Question Purpose | A description of the purpose of the question, whether the question has a specific expected function. | 0..1 | MultilingualText |
Question Text | The text which describes the information which is to be obtained. | 1..1 | MultilingualText |
* Attributes inherited from super-type(s) are not included here
Instance Question Block
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Instance Question Block | Exchange | use of a Question Block in a particular Questionnaire | The Instance Question Block is the use of a Question Block in a particular Questionnaire Component. This also includes the use of a Question Block in another Question Block, as it is a particular type of Questionnaire Component. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Instance Statement
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Instance Statement | Exchange | use of a Statement in a particular Questionnaire or more specifically a Questionnaire Component | The Instance Statement is the use of a Statement in a particular Questionnaire Component. This also includes the use of the Statement in a Question Block, which is a particular type of Questionnaire Component. |
Attributes*
Name | Description | Cardinality | Value Type |
Statement Text | The information, note, fact or instruction text making up the statement. | 0..1 | MultilingualText |
* Attributes inherited from super-type(s) are not included here
Output Specification
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Output Specification | Exchange | outline or description of how Information Sets are presented and arranged in Products for Information Consumers | The Output Specification specifies Products and uses the Presentations they contain. The Output Specification may be fully defined during the design process (such as in a paper publication or a predefined web report), or may be a combination of designed specifications supplemented by user selections (such as in an online data query tool). |
Attributes*
* Attributes inherited from super-type(s) are not included here
Presentation
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Presentation | Exchange | way data and referential metadata are presented | Presentations present data and referential metadata from Information Sets. Presentation can be used by an Output Specification to specify how Information Set in Product is presented.
|
Attributes*
* Attributes inherited from super-type(s) are not included here
Product
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Product | Exchange | package of content that can be disseminated as a whole | A Product packages Information Sets for an Information Consumer. The Product is generated according to Output Specifications, which define how the information from the Information Sets are presented (via Presentations) to the Information Consumer. A Provision Agreement between the statistical organisation and the Information Consumer governs the use of a Product by the Information Consumer. The Provision Agreement, which may be explicitly or implicitly agreed, provides the legal or other bases by which the two parties agree to exchange data. In many cases, dissemination Provision Agreements are implicit in the terms of use published by the statistical organisation. For static Products (e.g. paper publications), specifications are predetermined. For dynamic Products, aspects of specification could be determined by the Information Consumer at run time. Both cases result in Output Specifications specifying Information Set data or referential metadata that will be included within the Product. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Provision Agreement
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Provision Agreement | Exchange | legal or other basis by which two parties agree to exchange data | A Provision Agreement between the statistical organisation and the Information Provider (acquisition) or the Information Consumer (dissemination) governs the use of Exchange Instrument. The Provision Agreement, which may be explicitly or implicitly agreed, provides the legal or other basis by which the two parties agree to exchange data. The parties also use the Provision Agreement to agree the Information Structure of the information to be exchanged. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Question
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Question | Exchange | text used to elicit a response for a Conceptual Variable | A Question may be a single question used to obtain a response, or may be a multiple question, a construct which links multiple sub-questions, each with their own response. A Question also includes a relationship to the Value Domain to document the associated response criteria for the question. A single response question will have one Value Domain associated with it, while a 'multiple question' may have more than one Value Domain. A Question should be designed with re-use in mind, as it can be used in multiple Questionnaires. In a national implementation, Question could be further subtyped into:
| Multiple Question |
Attributes*
* Attributes inherited from super-type(s) are not included here
Name | Description | Cardinality | Value Type |
Question Purpose | A description of the purpose of the question, whether the question has a specific expected function. | 0..1 | MultilingualText |
Question Text | The text which describes the information which is to be obtained. | 1..1 | MultilingualText |
Question Block
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Question Block | Exchange | set of Questions, Statements or instructions which are used together | A Question Block should ideally be designed for reuse. The Question Block is a type of Questionnaire Component. A statistical organisation will often have a number of Question Blocks which they reuse in a number of Questionnaires. Examples of Question Blocks include:
|
Attributes*
* Attributes inherited from super-type(s) are not included here
Questionnaire
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Questionnaire | Exchange | Exchange Instrument to elicit information from observation Units | This is an example of a way statistical organisations acquire information (an Exchange Instrument). Each collection mode (e.g. in-person, CAPI (Computer-assisted personal interviewing), online Questionnaire) should be interpreted as a new Questionnaire derived from the Questionnaire Specification. The Questionnaire is a tool in which data is obtained. |
Attributes*
Name | Description | Cardinality | Value Type |
Media | Description of the kind of media conceived for the use of the Questionnaire (printed, electronic, etc.). | 1..1 | String |
Support Artifacts | A list of devices, software programs, storage media, gadgets or other tools needed to support the use of the Questionnaire. | 0..* | String |
Survey | Information on the survey which the Questionnaire will be used by. | 0..* | String |
* Attributes inherited from super-type(s) are not included here
Questionnaire Component
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Questionnaire Component | Exchange | record of the flow of a Questionnaire Specification and its use of Questions, Question Blocks and Statements | A Questionnaire Component defines the structure of the Questionnaire Specification, as a combination of Questions, Question Blocks and Statements. It is the class which groups together all the components of a Questionnaire. A Questionnaire Component is recursive, in that it can refer to other Questionnaire Components and accompanying Questionnaire Logic classes at a lower level. It is only at the top level where the Questionnaire Component links to the Questionnaire Specification. |
Attributes*
Name | Description | Cardinality | Value Type |
Component Sequence | The order in which Instance Question, and Instance Statement appear in the Questionnaire Component. | 0..* | Number |
* Attributes inherited from super-type(s) are not included here
Questionnaire Logic
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Questionnaire Logic | Exchange | management/control of the sequence of Questions, Question Blocks and Statements based on factors such as the current location, the response to the previous questions etc., invoking navigation and validation Rules to apply | Routing |
Attributes*
Name | Description | Cardinality | Value Type |
Routing Information | Routing information, which will also use responses from Rule. | 1..* | String |
* Attributes inherited from super-type(s) are not included here
Questionnaire Specification
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Questionnaire Specification | Exchange | Exchange Specification for Questionnaire | This represents the complete questionnaire design, with a relationship to the top-level Questionnaire Component. There may be many different Questionnaire Specifications, for the same surveys, or tailored to individual observation Units (respondents) so that there would be a different Questionnaire Specification for each respondent. The design would also differ depending upon the specific mode of collection the Questionnaire is designed for. |
Attributes*
* Attributes inherited from super-type(s) are not included here
Register
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Register | Exchange | written and complete record containing regular entries of items and details on particular sets of objects | In official statistics, "statistical registers" and "adminisitrative registers" (registers maintained by other organisations, usually administrative data owners) are usually distinguished. In GSIM, the information class "Register" is used to describe both types because the attributes are more or less the same so from the information management point of view, they can be handled as one GSIM class. There is usually a purpose or authority for maintaining the Register and each object in the Register is described using a pre-defined set of characteristics. Examples include business and population registers as used by statistical organisations. Therefore, from statistical perspective, the Register can be interpreted as a set of objects for a given Population, updated on a regular basis, containing information on identification, accessibility of Units and other attributes. The Register contains the current and historical statuses of the Population and the causes, effects and sources of alterations in the Population. In order to better understand how the Register is used in GSIM, the use cases for the different scenarios are explained. These scenarios are:
|
Attributes*
* Attributes inherited from super-type(s) are not included here
Statement
Definition
Class | Group | Definition | Explanatory Text | Synonyms |
---|---|---|---|---|
Statement | Exchange | report of facts in a Questionnaire | Statements are often included to provide further explanation to respondents. Example: "The following questions are about your health". The class is also used to represent completion instructions for the interviewer or respondent. Statement should be designed with re-use in mind as it can be used in numerous Questionnaires. | Interviewer Instruction Instruction |
Attributes*
Name | Description | Cardinality | Value Type |
Statement Text | The information, note, fact or instruction text making up the Statement. | 0..1 | MultilingualText |
* Attributes inherited from super-type(s) are not included here
Add Comment