attach an analysis Unit to the logicalRecord ?

[dzkwsk]

If I'm not mistaken, In DDI L 3.3 it's not possible to attach an AnalysisUnit to a logical record in a physical instance. Is there a practical way of documenting the analysisUnit in an object higher than the variable level?

[wlthomas]

Christophe, DDI-L v.3.3 allows for the definition of an AnalysisUnit at the following levels: Group <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/group_xsd/elements/Group.html> , LocalGroupContent <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/group_xsd/elements/LocalGroupContent.html> , LocalStudyUnitContent <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/group_xsd/elements/LocalStudyUnitContent.html> , MeasurementConstruct <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/datacollection_xsd/elements/MeasurementConstruct.html> , NCube <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/NCube.html> , QuestionConstruct <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/datacollection_xsd/elements/QuestionConstruct.html> , StudyUnit <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/studyunit_xsd/elements/StudyUnit.html> , Variable <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/Variable.html> , Weighting <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/datacollection_xsd/elements/Weighting.html> If I understand correctly you are asking that an AnalysisUnit be defined for a Logical Record. Does this mean indicating that all the variables of a specific record type have the same AnalysisUnit? Like in a person record, household record, family record? A logical record has the following: <xs:complexType name="LogicalRecordType <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/complexTypes/LogicalRecordType.html> "> <xs:complexContent> <xs:extension base="r:IdentifiableType <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/complexTypes/IdentifiableType.html> "> <xs:sequence> <xs:element maxOccurs="unbounded" minOccurs="0" ref="LogicalRecordName <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/LogicalRecordName.html> "/> <xs:element maxOccurs="unbounded" minOccurs="0" ref="r:Label <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/Label.html> "/> <xs:element minOccurs="0" ref="r:Description <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/Description.html> "/> <xs:element minOccurs="0" ref="VariableValueReference <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/VariableValueReference.html> "/> <xs:element minOccurs="0" ref="SupportForMultipleSegments <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/SupportForMultipleSegments.html> "/> <xs:element maxOccurs="unbounded" minOccurs="0" ref="CaseIdentification <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/CaseIdentification.html> "/> <xs:choice minOccurs="0"> <xs:element ref="VariablesInRecord <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/VariablesInRecord.html> "/> <xs:element ref="NCubesInRecord <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/NCubesInRecord.html> "/> </xs:choice> <xs:element minOccurs="0" ref="DefaultMissingValues <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/elements/DefaultMissingValues.html> "/> </xs:sequence> <xs:attribute name="hasLocator <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/complexTypes/LogicalRecordType.html#a5> " type="xs:boolean" use="optional"/> <xs:attribute name="variableQuantity <https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/logicalproduct_xsd/complexTypes/LogicalRecordType.html#a6> " type="xs:nonNegativeInteger" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> It has a VariableValueReference that is used to point to the variable defining its type but the variable itself defines its options for the analysis unit based on the representation values (H=household, etc.) CaseIdentification points to a specific case (Unit of a specified UnitType in this case the AnalysisUnit) I think that is about the only current option if I'm understanding your usage correctly. Wendy

…

On Thu, Jun 20, 2024 at 11:34 AM Christophe Dzikowski < ***@***.***> wrote: If I'm not mistaken, In DDI L 3.3 it's not possible to attach an AnalysisUnit to a logical record in a physical instance. Is there a practical way of documenting the analysisUnit in an object higher than the variable level? — Reply to this email directly, view it on GitHub <#40>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJT47OXWQM2O6KF5D3IEZ3ZIMABLAVCNFSM6AAAAABJUJ33ESVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DIOBUGM3DINQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Wendy L. Thomas ISRDI [retired] email: ***@***.***

[dzkwsk]

Wendy, Yes the idea would be to be able to define the unit type (or unit of analysis) in the logical record, which would be in line with the definition of a logical record: "A logical record is a description of all the elements (variables or NCubes) linked to a single case or unit of analysis". This would make it easy to document the logical record when all the variables have the same unit type (unitType). (In practice it's true we can have more heterogeneous logical record sometimes).

Christophe

[wlthomas]

Christophe, Then what I suggested in terms of using the case identifier and obtaining the analysis unit from that would be the work around. Note that a record with heterogeneous analysis units (a record containing person and related household variables for example) is really an instance of a physical storage record containing more than one logical record. If you want something more specific, file an issue on this. It would help to have examples and how the information is used to help in discussion. This would be a post version 4.0 change as we are trying to focus 4.0 on the structural shift. Wendy

…

On Tue, Jun 25, 2024 at 3:49 AM Christophe Dzikowski < ***@***.***> wrote: Wendy, Yes the idea would be to be able to define the unit type (or unit of analysis) in the logical record, which would be in line with the definition of a logical record: "A logical record is a description of all the elements (variables or NCubes) linked to a single case or unit of analysis". This would make it easy to document the logical record when all the variables have the same unit type (unitType). (In practice it's true we can have more heterogeneous logical record sometimes). Christophe — Reply to this email directly, view it on GitHub <#40 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJT47PL5DD4DR63DPYWNSDZJEVKFAVCNFSM6AAAAABJUJ33ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYGMZTMOBUGA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Wendy L. Thomas ISRDI [retired] email: ***@***.***

[dzkwsk]

Ok thanks, I'll look into caseIdentification. We ll have examples in the next months if the question still exists