Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

As organisations begin to use GSIM, this discussion forum will be used to explore issues with the model or propose extensions to the model.

Discussion Forum

 

Add new discussion topic

Open Issues

Topics 40 Replies 206
Topic Author Replies Last Reply
Cold Attachments 1
04 Oct
5
16 Nov
Cold 2
27 Sep
2
03 Oct
Cold 3
17 Sep
2
02 Oct
Cold 4
11 Sep
4
04 Oct
Cold 5
11 Sep
5
30 Oct
Cold 6
05 Sep
5
03 Oct
Cold Attachments 7
08 Aug
5
18 Sep
Cold 8
31 Jul
1
28 Oct
Cold 9
31 Jul
2
05 Sep
Cold 10
01 Jul
5
16 Jul
Cold 11
25 Jun
4
27 Aug
Cold Attachments 12
04 Jun
2
16 Jul
Cold Attachments 13
03 Jun
2
16 Nov
Cold Attachments 14
03 Jun
0 -
Cold 15
21 May
0 -
Cold Attachments 16
21 May
14
18 Jul
Cold Attachments 17
20 May
14
05 Nov
Cold 18
25 Mar
7
09 Apr
Cold 19
21 Mar
3
03 Jul
Cold 20
14 Mar
2
26 Mar
Cold Attachments 21
07 Mar
17
02 Oct
Cold 22
26 Feb
5
31 Jul
Cold 23
19 Feb
8
02 Oct
Cold Attachments 24
15 Feb
8
13 Aug
Cold Attachments 25
01 Feb
18
22 Nov

Instructions for use:

  • To reply to a topic, click on the name of the topic in the table below. Then choose 'add comment' and enter your comment in the box. You can choose 'watch this page' to receive email notifications when new responses are posted. Click save to post your reply.
  • To reply to an existing reply (that is, to continue a discussion thread) follow the instructions about but click 'reply' instead of 'add comment'.
  • To create a new topic, click 'add new discussion topic' below. Once you have added the topic, you will need to enter a title in the box at the top that says 'new page'. Then enter your text in the large text box and when you are done, click 'save' at the top right of the text entry box.

Log (to be updated by Thérèse Lalor only)

TopicBackground
Object/ Issue
Raised by
Status
Outcome
Open Question?
Population

#1

 

Add unit type object

Alistair Hamilton

 

DECIDED

A new object will be added called Unit Type

Action: Definition, relationships and attributed need to be drafted

 
#16Add relationship to unit typeHelen TooleDECIDEDAction: Relationship to Logical Record to be added 
#13Survey and Frame PopulationsJenny LinnerudWAITINGABS to providing improved definitions 

Node Sets



#2

Code vs Code List

Category vs Category Set

Klas Blomqvist DOUBLE CHECK

Provide clearer explanation of the differences

Action: Text needs to be drafted from examples in discussion forum

 Need to revisit idea of removing code as an object in its own right

(and replacing it with an attribute on the category object)

#8

LevelHelen TooleDECIDED

Change the diagrams to include Level in the next release.

Action: New diagrams to be created

 
#11Statistical Classification CardinalityHelen TooleDOUBLE CHECK

Classification Scheme (Statistical Classification) has Mandatory Level

Action: Change the definition of (Statistical Classification) such that it must contain at least one Level.

(Statistical Classification) 1..* Level (Mandatory, Many)

Does this hold up after Neuchatel proposal????
#12Hierarchy in Classifications and codelistsHelen TooleOPEN TOPICChris providing example of hierarchical codelist as example 
#21Alignment with NeuchatelThérèse LalorDECIDED

Change according to proposal

Action:

Remove Classification Version from model

Remove Classification Variant from model

Change Classification to Classification Series

Change Classification Scheme to Statistical Classification

Revise relationships according to proposal

Add attributes according to proposal

Revise definitions

 
Methodology#3Design ContextJenny LinnerudWAITING(Waiting for Methodology discussion to happen before decision made) 
 #17BMethodologyThérèse LalorOPEN TOPIC  
Business Service#4

Business Service

Dissemination Service

Thérèse LalorDECIDED

Dissemination Service to be a subtype of Business Service

Action: Text needs to be drafted and attributes aligned

 
Data Resource#5States of dataJenny LinnerudDOUBLE CHECK

Steady states of the data is an optional attribute on the DataResource, with an uncontrolled vocabulary.

Action: Attribute to be added to Data Resource

Action: Information about how states of data "could be done" should go into the next version of the User Guide

Double check: Attribute or User Guide only?

If attribute, Data Resource or Data Set?

Non Structure Dataset#6Non Structured Data SetThérèse LalorOPEN TOPIC  
Data Set#7

unit data

dimensional data

Thérèse LalorOPEN TOPIC  
Data Channel#9Data ChannelThérèse LalorDECIDED

Data Channel stays in model

Action: Review definition of Data Channel

 
Representation#10RepresentationThérèse LalorDECIDED

Change name of Representation to Presentation

Action: Name changed in documentation and model

 
Relationships#14RelationshipsJenny LinnerudOPEN TOPICAction: All relationships need to be reviewed and made explicit before next release 
Views of GSIM#15Creating views of GSIMGareth McGuinnessWAITINGWaiting for input from CSPA 
Quality#17AQualityThérèse LalorOPEN TOPIC  
Reference Metadata#17CReference MetadataThérèse LalorOPEN TOPIC  
Data Point#18Data PointHelen TooleDECIDED

Example in glossary to be fixed (Proposal 1)

Action: Fix Example

 
Process Output#19Add Process Output subtypeGareth McGuinnessOPEN TOPIC  
Assessment#20AssessmentGareth McGuinnessDECIDED

Definition to be improved

Action: Fix definition

 

 

 

 


Search this discussion forum

  • No labels