[DDI-SRG] Bug resultions

[Wendy Thomas]

Today's call dealt with bugs assigned to Wendy. The following is a summary 
of the decisions. Note that a new updated spreadsheet has been attached to 
ID0006 and contains the integrated information as these items are 
interrelated. If you have comments to make do so in MANTIS

ID00006
The problem is being addressed by simplification of the DataRelationship 
description for simple files and continued requirement of the reference 
from PhysicalDataProduct. Note that LogicalDataProduct/DataRelationship 
remains optional because a LogicalDataProduct may contain just a 
CategoryScheme early in the lifecycle.

In LogicalDataProduct/DataRelationship

CHANGE: Description from 1..n to 0..n
CHANGE: LogicalRecord from 0..1 to 1..n

NO CHANGE TO REQUIRED REFERENCE FROM 
PhysicalDataProduct/GrossRecordStructure/LogicalRecordReference


ID00021

Changes in ID0006 also address this bug.

In LogicalDataProduct/DataRelationship

CHANGE: LogicalRecord/CaseIdentification from 1..n to 0..n
This allows for NO case identification in simple files with single record 
types


In LogicalDataProduct/DataRelationship/VariablesInRecord
ADD to documentation: The variables in the logical record can be noted by 
inclusion or exclusion to facilitate the easiest means of describing the 
variables in the LogicalRecord. The attribute allVariablesInLogicalProduct 
when set to true includes all variables in the LogicalProduct. 
VariableSchemeReference can then be used to exclude individual Variables 
schemes or include schemes from other logical products. In the same way 
VariableReference can be used to exclude specific variables from the 
previously defined variable set or include variables not already included. 
Most simple LogicalProduct descriptions with a single LogicalRecord can be 
described using only the attribute allVariablesInLogicalProduct="true"

attribute  allVariablesInLogicalProduct   type="boolean"        This is 
not a default because it would be easy to miss
ADD (before VariableRefernce):
element  VariableSchemeReference     0..n
     attribute: inclusion   value="inclusion | exclusion"
     Documentation: This allows for the inclusion or exclusion of a 
VariableScheme

Change: VariableReference from 1..n to 0..n
         ADD attribute inclusion value="inclusion | exclusion"


ID0008

This seems to be a carry over from DDI 2 which did not have the detailed 
information now provided by BaseRecordLayout and alternate means of 
describing DataItem structure. As this is the format of the data set and 
does not fall within the group of default settings for DataItems, it is 
only required at the PhysicalDataProduct level.

Remove: FormatScheme from both PhysicalDataProduct and DataItem
Add: Format documentation - expand to include examples (fixed, delimited, 
SPSS .sav, SAS, EXCEL, etc.)
REMOVE DataItem/Format


ID00022

This change simplifies the description to accommodate simple data files 
using minimal description.
In PhysicalRecordSegment

ADD attribute  hasSegmentKey  type boolean   default="false"
           documentation "false implies default identification is by 
segment order in file if segmentOrder is > 1"

MOVE RecordSegmentRelationship to a position above current CHOICE

REMOVE   CHOICE
CHANGE   Hierarchical from 1..1 to 0..1
CHANGE   SeparateFile form 1..1 to 0..1
CHANGE       FileNameIdentifion from 1..1 to 0..1
REMOVE   ENDCHOICE



ID0037

CHANGE  correct spelling SeperateFile to SeparateFile


ID00036/ID00023

DataItem was a typographical error should have been DataSet as in Public 
Review version
However, a DataSet is really a special inline storage structure for a 
BasicRecordLayout and as such would not occure when an external data 
structure is being described.

REMOVE: GrossRecordStructure/DataItem
MAKE DataSet a substitution for BaseRecordLayout   0..n



ID0010

MOVE PhysicalRecordSegmentReference FROM DataItem TO RecordLayout
CHANGE PhysicalRecordSegmentReference FROM 0..1 to 1..1
MOVE attribute NamesOnFirstRow  boolean default   FROM DataItem to 
PhysicalRecordSegmentReference

This allows for common information regarding the location of the item in a 
specified physical segment to be declared once


ID0011

Remains open....References should use URN so that parent scheme is 
declared within the VariableReference. Do we really want to introduce 
tracking a default scheme and providing just the Variable ID's?

ID0012

CHANGE PhysicalLocation form 0..n to 1..1
REMOVE ValueLocation   [with other changes it has become a single child 
and can be removed]

Wendy L. Thomas                          Phone: +1 612.624.4389
Data Access Core Director		 Fax:   +1 612.626.8375
Minnesota Population Center              Email: wlt at pop.umn.edu
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455