[DDI-SRG] DDI3::Child elements of top modules not being identifiable (fwd)

[Joachim Wackerow]

Wendy,

I had only a short look at it. The proposed solution seems to be 
reasonable. Nevertheless the issue seems to be worth to get a thorough 
review. Perhaps it should be - in addition to the proposed solution - 
marked as bug in 3.0, so the review can be made later.

Achim

Wendy Thomas wrote:
> PLEASE NOTE:
> I have put this in as a RESOLVED bug as it is clearly a real case problem. 
> Read it and respond asap if you see a problem with this. It is bug 191. I 
> have also put in a bug 192 for a review of all children of top level 
> elements regarding their identifiable type.
> 
> Wendy
> 
> 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
> 
> ---------- Forwarded message ----------
> Date: Fri, 28 Mar 2008 14:51:51 +0100
> From: Jannik Vestergaard Jensen <jvj at dda.dk>
> To: Wendy Thomas <wlt at pop.umn.edu>
> Subject: SV: DDI3::Child elements of top modules not being identifiable
> 
> Yes Wendy I agree with you, thanks.
> 
> 
> Med venlig hilsen/ Best regards
> Software developer
> Jannik V. Jensen
> 
> Dansk Data Arkiv/ Danish Data Archive
> Islandsgade 10 - DK 5000 Odense C
> Tlf: +45 6548 0342 - Fax: +45 6611 3060
> E-mail: jvj at dda.dk - URL: www.dda.dk
> 
> -----Oprindelig meddelelse-----
> Fra: Wendy Thomas [mailto:wlt at pop.umn.edu]
> Sendt: 28. marts 2008 14:49
> Til: Jannik Vestergaard Jensen
> Emne: Re: DDI3::Child elements of top modules not being identifiable
> 
> Jannik,
> 
> As I understand you, you are running into these problems when working
> with groups...correct? Clearly we were thinking only in terms of
> referencing when we ran our last check.
> 
> I'm expanding on your request...let me know if this makes sense to you.
> 
> 
> Methodology - parent Maintainable - children identifiable
>     Versionable may be a better option as I may modify or add to its
> contents during the course of the study
> 
> ProcessingEvent - parent Maintainable - childeren 2 identifiable most
> not identifiable
>     Make Identifiable
> 
> DataRelationship - parent Maintainable - children identifiable
>     Make Identifiable
> 
> CategoryGroup - parent Maintainable - child versionable
>     Make Versionable (parent should not be lesser than child on the
> identification hierarchy
> 
> Wendy
> 
> 
> On Fri, 28 Mar 2008, Jannik Vestergaard Jensen wrote:
> 
>> Hey Wendy
>>
>> I am writing to you because you are so good at answering my questions
>> :-
>> )
>> While doing the GroupParser for the DDIFTP I stumbled upon these
>> questions when coping elements from one module to another.
>>
>> The main problem I am facing is that child elements of topmodules not
>> are identifiable therefore it is problematic to identify relationships
> 
>> among elemets within these because the can be zero or many of these
>> non identifiable containers.
>>
>> Below I have listed problems I have identified.
>>
>> Datacollection::Methodology
>> As there can be zero to many Methodologies within a DataCollection it
>> is not possible to define relations among AbstractIdentifiable
>> elements within a Methodology or to specifically identify which
>> Methodology a DataCollectionMethodology, TimeMethod, SamplingProcedure
> 
>> or DeviationFromSampleDesignresides resides in.
>> Suggestion: Methodology made Identifiable
>>
>> Datacollection::ProcessingEvent
>> It is not possible to identify relations between the varios
>> AbstractIdentifiable within a ProcessingEvent, red. Weighting and
>> Coding.
>> Suggestion: ProcessingEvent made Identifiable
>>
>> LogicalProduct::DataRelationship
>> It is not possible to identify relations between a LogicalRecord and a
> 
>> RecordRelationship within a DataRelationship as their parent is not
>> identifiable.
>> Suggestion: DataRelationship made Identifiable
>>
>> LogicalProduct::CategoryScheme::CategoryGroup
>> As there can be zero to many CategoryGroups within a CategoryScheme it
> 
>> is not possible to define which CategoryGroup a Category resides in.
>> Suggestion: CategoryGroup made Identifiable
>>
>> Med venlig hilsen/ Best regards
>> Software developer
>> Jannik V. Jensen
>>
>> Dansk Data Arkiv/ Danish Data Archive
>> Islandsgade 10 - DK 5000 Odense C
>> Tlf: +45 6548 0342 - Fax: +45 6611 3060
>> E-mail: jvj at dda.dk - URL: www.dda.dk
>>
>>
> 
> 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
> _______________________________________________
> DDI-SRG mailing list
> DDI-SRG at icpsr.umich.edu
> http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg