Data Capture

Summary

Important highlights from this release

All updates for this release

Improvement

• DCAP-77 OPEN Relationship between RepresentedQuestion and Subject/Keyword is missing
• DCAP-76 OPEN Relationship question - mode of data collection needed
• DCAP-75 OPEN Relationship Question to (sub)-universe needed
• DCAP-72 OPEN Language of the Instrument for a Study is missing
• DCAP-71 OPEN How to attach a note to a question that is used in different studies
• DCAP-70 OPEN Unclear usage of ExternalAid and ExternalMaterial for ShowCard
• DCAP-68 OPEN Mode of Instrument should be explicit defined
• DCAP-58 OPEN Mode of Collection
• DCAP-50 DONE Instrument View - various
• DCAP-49 DONE Instrument view - relationship between question and concept (design level)

Task

• DCAP-73 OPEN Mapping concepts between variables and Capture
• DCAP-64 IN PROGRESS Complete modeling of Response Domains
• DCAP-63 OPEN Identify missing content needed to support priority use cases in Prototype 2018-06
• DCAP-62 IN REVIEW Why does CodelistResponseDomain have a separate Codelist?
• DCAP-61 OPEN connecting Capture to ConceptualVariable
• DCAP-57 OPEN Update the Instrument View contents after any revisions have been made to model
• DCAP-56 OPEN Is separation of instrument and internal processing assumed to be separate?
• DCAP-55 OPEN The term "Capture" can be misinterpreted
• DCAP-54 IN REVIEW Sentinal domains in Represented Questions
• DCAP-53 OPEN Need the ability to link from a specific represented variable through response domain to a specific represented question
• DCAP-52 OPEN What is the purpose of Workflows?
• DCAP-51 IN REVIEW Recent edit to Process included only a general "hasParameter"
• DCAP-48 TO DO Revisit QuestionGrid and QuestionBlock discussion as it relates to the newly created Response Domains
• DCAP-44 IN REVIEW Wolfgang's question about attaching category to booleanResponseDomain.
• DCAP-38 DONE How do we create enumerations in Drupal? i.e. classificationLevel 'nominal', 'ordinal', 'interval', etc. Do we even need these?
• DCAP-37 DONE NumberRange does not need to be annotated or identifiable.
• DCAP-34 IN PROGRESS Where to put intendedRepresentation
• DCAP-32 OPEN We need a touch point between data capture and analysis (exists as a GenerationInstruction in DDI 3.2) to capture derived and other transformations.
• DCAP-30 DONE WorkflowSequence should have a clear beginning and end point
• DCAP-29 DONE Binding should be updated.
• DCAP-28 DONE Binding - Target Objects - InputParameter and OutputParameter should be 0..1
• DCAP-27 DONE Command definition needs to be updated
• DCAP-26 DONE structuredCommand is very XML centric in its description and the way it is used.
• DCAP-25 DONE CommandCode definition needs to be updated
• DCAP-24 DONE IfThenElse - the final elseContains should be 0..1 - only one else available
• DCAP-23 DONE ControlConstruct should not contain a WorkflowStep
• DCAP-22 DONE Elseif cardinality should be 0..n not 1..1.
• DCAP-21 DONE ElseIf should not be identified or annotated and should not derive from ConditionalControlConstruct
• DCAP-20 DONE workflowSteps should have bindings
• DCAP-19 DONE The Parameters class does not need to be identified or annotated, it's just a collection of input/output parameters.
• DCAP-18 OPEN SubstantiveValueDomain does not specify different types of ValueDomain with enough specificity, i.e. numeric text, date/time, ranges, etc. Only provides one string.
• DCAP-16 IN PROGRESS RespresentedVariable should not have a universe.
• DCAP-15 DONE Move RepresentedVariable from RepresentedQuestion to ResponseDomain
• DCAP-14 OPEN RepresentedQuestion does not have output parameters
• DCAP-13 DONE Remove SubstantiveValueDomain and SentinelValueDomain from ResponseDomain because they are inappropriate.
• DCAP-12 TO DO Base workflowStep does not require hasProcessFramework or isPerformedBy, should be created in a derived class as needed.
• DCAP-11 TO DO Too much information in workflowStep
• DCAP-10 DONE Remove instructionalCommand from base Act class. Not all Acts need it.
• DCAP-9 OPEN Distinguish patterns from properties
• DCAP-8 IN REVIEW Defining order in WorkflowSequence
• DCAP-7 DONE All identified items should have the ability to link to additional material, i.e. a scanned copy of a questionnaire.
• DCAP-6 RESOLVED Create ResponseDomains
• DCAP-5 IN REVIEW The In/Out parameters should have at least names, description, and representation, maybe even default value? hasParameters
• DCAP-4 IN REVIEW The ambiguity and/or redundancy of the name, title, or annotation of a question
• DCAP-3 DONE Bindings should not be identified
• DCAP-2 IN REVIEW Workflow contains object relationships that are unnecessary for DataCapture
• DCAP-1 RESOLVED Appoint new Data Capture modeller from modelling team

Sub-task

• DCAP-74 OPEN Cardinality in ResponseDomain intendedRepresentation is currently 0..1 source and 0..n target
• DCAP-60 OPEN How can a compound question be modeled?
• DCAP-59 OPEN In Boolean response domain – what does the category do?
• DCAP-47 TO DO RankingResponseDomain needs to be modeled.
• DCAP-46 TO DO RankingDomain - recommend creating a ranking group that ranking domains will link to.
• DCAP-45 TO DO ScaleResponseDomain needs to be modeled.
• DCAP-42 TO DO How do we manage missing representation?
• DCAP-41 DONE Should we add intendedRepresentation to ResponseDomain
• DCAP-40 TO DO What to do about multiple selection on code list response domain
• DCAP-36 IN PROGRESS Need to add OutParameters to the response domain when it's complete
• DCAP-35 TO DO Do we need classificationLevel as a property in the NumericResponseDomain?