DateDec 12, 2017
Issues68 issues



Summary

Insert release summary text here.



Important highlights from this release

  1. Highlight 1
  2. Highlight 2
  3. Highlight 3


All updates for this release

Improvement

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

Task

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

Sub-task

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