caCORE 1040: Creating Well-formed Metadata and Metadata Business Rules
Completion Quiz

1.  The preferred terminology for creating Common Data Elements in the
    caDSR is:

    a.  NCI Thesaurus

    b.  NCI Metathesaurus

    c.  SNOMED

    d.  LOINC

2.  One of the benefits of using the NCI Thesaurus as a source for CDE
    names is that it is editable and maintainable in real time.

    a.  True

    b.  False

3.  The "short name" is an abbreviated name for an Administered Item
    (e.g. Data Element).

    a.  True

    b.  False

4.  The required parts of a Data Element Concept include the Object
    Class and Property.

    a.  True

    b.  False

5.  To create a Data Element Concept name, you will need the following:

    a.  Object Class and Property

    b.  Data Element

    c.  Value Domain

    d.  Representation Term

6.  The CDE Curation Tool provides links to search the NCI Thesaurus for
    Object Class, Property and their Qualifiers.

    a.  True

    b.  False

7.  What do you do if you can't find the term you need in EVS?

    a.  Make up your own term

    b.  Use the Admin Tool instead

    c.  Suggest a new term to EVS

    d.  Give up

8.  To create a Value Domain name, you will need the following:

    a.  Data Element Concept

    b.  Data Element

    c.  Conceptual Domain

    d.  Representation Term

9.  There are three options for selecting a short name for an
    Administered Item. Which option do you choose if you want to enter a
    [customized]{.underline} abbreviation of the name?

    a.  System Generated

    b.  Abbreviated

    c.  User Entered

10. CDE Long names can have duplicate terms in the name.

    a.  True

    b.  False

11. Good definitions promote metadata standardization and reuse of Data
    Elements, which facilitates data sharing and interoperability of
    information systems.

    a.  True

    b.  False

12. A metadata definition should be unique, singular and not contain
    embedded definitions.

    a.  True

    b.  False

13. What caDSR Tool can be used to search for existing Data Element
    Concepts and Value Domains?

    a.  UML Loader

    b.  caDSR Sentinel Tool

    c.  Semantic Integration Workbench

    d.  CDE Curation Tool

14. Within a context, a DEC and VD can be paired only once to make a
    unique CDE.

    a.  True

    b.  False

15. An example of a major version change for a Data Element is:

    a.  v2.0 v3.0

    b.  v2.0 v2.1

    c.  v2.0 v2.0

16. An example of a minor version change for a Data Element is:

    a.  v2.0 v3.0

    b.  v2.0 v2.1

    c.  v2.0 v2.0

17. If you change the Value Domain Type from Non-enumerated to
    Enumerated, you should:

    a.  Version the Value Domain to the next whole number

    b.  Version the Value Domain by one tenth (e.g. 2.1 to 2.2)

    c.  No versioning is necessary

18. Correcting typographical errors in a Data Element definition
    requires a new version.

    a.  True

    b.  False

19. The workflow status assigned to Data Elements (and associated
    Administered Items) that have been reviewed and approved by the
    owning context\'s review process is:

    a.  DRAFT MOD

    b.  RELEASED

    c.  APPROVED FOR TRIAL USE

    d.  RETIRED PHASED OUT

20. A minor version change is required when a semantic change is made to
    the definition of a Data Element Concept.

    a.  True

    b.  False

21. A major version change is required when a Value Domain is associated
    to a different Conceptual Domain.

    a.  True

    b.  False

22. Changing the max length of a Permissible Value constitutes a minor
    version change in the Value Domain.

    a.  True

    b.  False

23. Changing the Value Domain in a Data Element requires a minor version
    change for the Data Element.

    a.  True

    b.  False

24. Adding a Permissible Value from the same source as the other values
    to a Value Domain constitutes a major version change.

    a.  True

    b.  False

25. Changing the wording of the document text constitutes a minor
    version change to the Data Element.

    a.  True

    b.  False

Answers:

1.  A. NCI Thesaurus. It is a nonproprietary source of naming
    components; editable; maintained in real time; provides semantic
    linking of preferred terms; gives guidance in using homographs; and
    shows equivalence, hierarchy, and associations between concepts.

2.  A. True. Other benefits include: a nonproprietary source of naming
    components; provides semantic linking of preferred terms; gives
    guidance in using homographs; and shows equivalence, hierarchy, and
    association between concepts.

3.  A. True. The short name is a 30 character (maximum) abbreviated name
    for an administered item. The short name may be generated by the
    database system, abbreviated by the system, or entered by a user.

4.  A. True. Object Class - a set of real world ideas, abstractions, or
    things that have explicit boundaries and meanings; whose properties
    and behaviors follow the same rules. Property - a characteristic
    common to all members of the Object Class.

5.  A. Object Class and Property. Object Class -- The concept or 'thing'
    described in the data being captured. Property -- The characteristic
    of the Object Class that makes it identifiable. You can add
    additional descriptions or qualifiers to both.

6.  A. True. The Curation Tool provides a search mechanism to search EVS
    for concepts -- this way you can search for concepts when doing
    curation activities instead of having to use multiple tools.

7.  C. Suggest a new term to EVS. If a desired term is not in EVS, you
    can suggest a term and definition by using the 'Suggest to EVS'
    button located in the Curation Tool at the top right of any concept
    search screen.

8.  D. Representation Term. The semantics of the VD reside entirely
    within the representation term and qualifiers. Best practice is to
    build the name of the Value Domain using the Representation Term and
    Qualifiers exclusively.

9.  C. User Entered. The maximum character length for the short name
    is 20. If a standard abbreviation doesn't exist, create a new
    abbreviation by truncating the term to the first four letters of the
    long name term or an appropriate short term that has meaning.

10. B. False. CDE Long Names should not contain duplicate terms -- you
    have the ability to edit this field to delete redundant terms.

11. A. True. This data sharing is the purpose of a metadata registry.
    Without standardization and sharing, we would continue to build and
    maintain local databases, but there wouldn't be a frame of reference
    to exchange data between them.

12. A. True. A well-formed definition should be distinguishable from
    every other definition in the registry as well as express the
    definition as a single instance.

13. D. Curation Tool. The Curation Tool is used to search for existing
    Data Element Concepts and Value Domains. Remember, the CDE Browser
    will only search directly for Data Elements.

14. A. True. A DEC and VD can only be paired once top make a CDE within
    a context. If a VD is shared, you have to pair it with two different
    DECs. The result is two different CDEs.

15. A. v2.03.0. When the version number is increased by a whole point,
    it is considered to be a major version change.

16. B. v2.02.1. When the version number is increased by a tenth of a
    point, it is considered to be a minor version change.

17. A. Version the Value Domain to the next whole number. Changing the
    type of a Value Domain (non-enumerated to enumerated) is considered
    to be a major version change.

18. B. False. Typographical corrections do not require a version change.

19. B. Released. Released Administered Items must be fully specified and
    compliant with the caDSR naming guidelines and conventions as well
    as the ISO 11179 model. Versioning rules apply. These CDEs may be
    designated and reused by non-owning contexts.

20. A. True. A substantive or semantic change to a definition requires a
    minor version change. Please note that typographical corrections are
    not substantive or semantic changes.

21. A. True. A major version change is required when the Value Domain is
    associated with a new Conceptual Domain or a different version of
    the previously associated Conceptual Domain.

22. A. True. Changes to other Value Domain attributes warrants a minor
    version change including: Data Type, Unit of Measure, Display
    Format, Character Set, Maximum Length, Minimum Length, High Value,
    Low Value, Decimal Place, and Representation.

23. B. False. Changing the Value Domain in a Data Element requires a
    major version change.

24. B. False. Adding a Permissible Value from the same source as the
    other values to a Value Domain requires no version change.

25. A. True. A Document Text change for a Data Element constitutes a
    minor version change.