Log (to be updated by Thérèse Lalor only)
|Raised by||Last comment|
|Data Structure Component||#34||Simplifying data structure component objects||Thérèse Lalor||29 Oct||VOTING ON OPTIONS||Revised option added by ABS - for decision. Need to have discussion at #7 first.|
|Reference Metadata||#17C||Reference Metadata||Thérèse Lalor||29 Oct||LOW PRIORITY - WORK REQUIRED|
Can we do an example like we have an example for quality?
Chris says he could have an example from Eurostat - Metadata Structure Definition.
To be discussed at Sprint
|Documentation||#25||GSIMv2 documentation||Thérèse Lalor||13 Sept||WAITING||Vote on which GSIM documents you use the most to help us understand what it useful|
|Views of GSIM||#15||Creating views of GSIM||Gareth McGuinness||18 Jul||WAITING|
|Modelling||#14||Relationships and Attributes||Jenny Linnerud||---||WAITING||Action: All relationshipsand attributes need to be reviewed and made explicit at Sprint|
|Modelling||#22||Objects to be added/removed||Thérèse Lalor||---||WAITING|
|Modelling||#33||Definitions||Thérèse Lalor||---||WAITING||Action: All definitions need to be reviewed at Sprint|
Changes to be implemented at Sprint
|Instrument Implementation||#35||Remove all object below Instrument Implementation||Dick Woensdregt||---||WAITING|
Following agreements made:
** have to make changes with a good business case**
** not going to leave it as it is **
**balance of simple to understand and not leading down the wrong path **
--> Go to Sprint for elaboration
|Acquisition Activites||#37||Review to definition of a number of acquisition related objects||Dick Woensdregt||11 Oct||WAITING|
What is the outcome here? Is it a change or an acknowledgement?
depends on result of decision at #35
|Interviewer Instruction||#27||Rename Interviewer Instruction||Helen Toole||2 Oct||WAITING||Arofan has provided input. For discussion - depends on result of decision at #35|
|Questions||#30||Question and Multiple Question Item||Helen Toole||2 Oct||WAITING|
Input from Arofan and Chris given. Need a resolution based on that advice
depends on result of decision at #35
Channel Activity Specification, Channel Design Specification?
Relationship to Data Resource
|Dick Woensdregt||29 Oct||DECIDED|
Objects related to acquisition decided
|Quality||#17A||Quality||Thérèse Lalor||2 Oct||DECIDED||new text attached to wiki. waiting for picture from Helen|
|Attribute Component||#31||Attribute Component||Jenny Linnerud||2 Oct||DECIDED|
Jenny has provided an improved definition.
Related to issue #31 and #7
|Thérèse Lalor||11 Oct||DECIDED|
We agree to the tenet of it and exact changes - in terms of relationships and definitions - to be worked out at sprint. We also need to tighten up all the definitions of dataset related objects.
|Statistical Activity||#28||What is the difference between Statistical Activity and Process Step Execution Record||Dick Woensdregt||18 Sept||DECIDED||Action: Definition to be improved. we could look into the relationships between these objects. This deserves some attention/discussion.|
|Process Step||#29||What does a CSPA Service map to?||Dick Woensdregt||4 Oct||DECIDED|
GSIM should add a mention of Statistical Service either to the description or examples of a Business Service
Review text at Sprint to ensure alignment
|Methodology||#17B||Methodology||Thérèse Lalor||5 Sept||DECIDED||no changes to be made|
|Data set||#24||Distinguishing between different types of datasets||Jenny Linnerud|
Are we ready to resolve this? Is this something for GSIM version after this one?
Categorized as future work. Is this something other groups could solve? eg Data without Boundaries or Stats Network
|Instrument||#32||Instrument and Instrument Implementation definitions||Helen Toole||2 Oct||DECIDED|
Action: fix the table....
Action: Change definition. Better explanatory text around this.
Action: Rename instrument implementation to represented instrument. It has the advantage of linguistic consistency
|Non Structured Dataset||#6||Non Structured Data Set||Thérèse Lalor||2 Oct||DECIDED||Action: Remove and make small text explanation that we may need this in the future|
|Node Sets||#12||Hierarchy in Classifications and codelists||Helen Toole||06 Aug||DECIDED||Action: In the documentation we need to have a good example of what is a classification and what is a codelist (drawn from the the comments at the top of the thread).|
|Methodology||#3||Design Context||Jenny Linnerud||16 Jul||DECIDED||Action: We are not making changes to the methodology for this version. We should remove this item.|
|Index/Index Entry||#26||Index/Index Entry||Thérèse Lalor||13 Sept||DECIDED|
|Add unit type object|
A new object will be added called Unit Type
Action: Definition, relationships and attributed need to be drafted
|#13||Survey and Frame Populations||Jenny Linnerud||27 Aug||DECIDED|
All subtypes of population will be removed
All subtypes of Unit will be remove
|#16||Add relationship to unit type||Helen Toole||4 Jun||DECIDED||Action: Relationship to Logical Record to be added|
Code vs Code List
Category vs Category Set
|Klas Blomqvist||13 Aug||DECIDED|
Provide clearer explanation of the differences
Code is kept in the model with better explanation
Action: Text needs to be drafted from examples in discussion forum
|Level||Helen Toole||26 Mar||DECIDED|
Change the diagrams to include Level in the next release.
Action: New diagrams to be created
|#11||Statistical Classification Cardinality||Helen Toole|
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)
Fixed in Neuchatel changes
|#21||Alignment with Neuchatel||Thérèse Lalor||13 Aug||DECIDED|
Change according to proposal
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
|Thérèse Lalor||09 Apr||DECIDED|
Dissemination Service to be a subtype of Business Service
Action: Text needs to be drafted and attributes aligned
|Data Resource||#5||States of data||Jenny Linnerud||31 Jul||DECIDED|
Information about how states of data "could be done" should go into the next version of the User Guide, rather than trying to fit into the model
Input to be given by countries using states of data may be done.
Action: Text needs to be drafted
|Data Channel||#9||Data Channel||Thérèse Lalor||03 Jul||DECIDED|
Data Channel stays in model
Action: Review definition of Data Channel
|Representation||#10||Representation||Thérèse Lalor||09 Apr||DECIDED|
Change name of Representation to Presentation
Action: Name changed in documentation and model
|Data Point||#18||Data Point||Helen Toole||16 Jul||DECIDED|
Example in glossary to be fixed (Proposal 1)
Action: Fix Example
|Process Output||#19||Add Process Output subtype||Gareth McGuinness||27 Aug||DECIDED|
Remove all subtypes of Process Input
Remove all subtypes of Process Output
|Assessment||#20||Assessment||Gareth McGuinness||16 Jul||DECIDED|
Definition to be improved
Action: Fix definition
|Data Provider||#23||Data Provider||Jenny Linnerud||13 Aug||DECIDED|
No change to model required. Although perhaps clarification in text would help future users?
Action: clarification in text would help future users?
Search this discussion forum