Hello all,
I’m a little puzzled what information should define.xml contain in the CodeList sections and non-standard values.
#1. The Codelist entry should contain all available values for that CodeList or jjust the ones used into the current dataset?
E.g. CL.C66731.SEX contains the F, M, U, UN values (see “SEND Terminology.xls”). If my dataset contains just M and F values for SEX, the Codelist in define.xml should contain:
a) entries just for M and F?
b) entries for all 4 values from SEND Terminology?
Going for option a) is easier and also has as result a smaller define.xml & define.pdf. However I’ve seen here: http://www.opencdisc.org/forum/codelist-extensible-vs-non-extensible recommendations for option b)…
#2. For an extensible CodeList the user can specify its own entries.
E.g. CL.C77808.SPECIES is extensible. So, if the user uses a species that is not in SEND terminology like “Primate” (instead of MONKEY which is in standard SEND CT), he can add an entry like below:
_**Primate**_
Is this correct?
#3. For a non-extensible CodeList, the user is not allowed to specify other entries than the standard ones. If he still wants to use both standard and non-standard entries, what can he add for that CodeList in define.xml?
a) add just standard SEND entries; ignore the non-standard ones?
b) add both standard and non-standard entries. But this would contradict the definition of “non-extensible”?
c) don’t add an entry for that CodeList at all.
E.g. CL.C66781.AGEU is non-extensible. If the user uses as units both “DAYS” (in CT) and “SEMESTER” (not in CT), how the Codelist entry for AGE should look like?
Amelia