Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Morning Session

Afternoon Session


Morning Session

Title of session: Data Capture

Day: Monday, October 24

Participants: Barry Radler, Dan Smith, Wolfgang Zenk-Moltgen, Kelly Chatain, Arofan Gregory (visiting)

Chair: Barry Radler

Note taker: Kelly Chatain

Background information

Not much work since Dagstuhl 2015 by the Data Capture team. In general waiting to hear back on the work already completed and in need of review. 

Reviewed the team members, a few were removed due to inactivity (for various reasons). Sophia, Ingo, and Brigitte.  Jannik has not had the time to help with the modelling and therefore a new modeller for Data Capture should be assigned (issue created in Jira).


Backing-up and Reviewing the model:

The group went back to the model to review changes made by others outside of the team. 

Implemented instrument based on conceptual instrument, which organizes infinite number of 'captures' (superclass) that are associated with represented variable. Created Represented Measurement (includes question and non-question) as well as Represented question. Instance question measurement, Instrument component (the base class)...

**All ties into the process model with a DDI Act. But how? Where do we define the questionnaire flow (the sequence), the instrument itself?

10:55 - Arofan brings in Larry's rendering of what's in drupal workflow

Random notes by Kelly (may discard)

  • Defining an Act (instructional command= command code, but not applicable for asking a question) Command code is part of instrument component.
  • Workflow service - not applicable for specifying questionnaire, i.e. for setting the conditional?
  • Workflow has a sequence, acts are ordered by the workflow sequence
  • Instance question = act
  • Conceptional instrument has workflow sequence (concrete). Workflow sequence is control construct, has properties that say instance Q1 (act1), followed by Instance Q2(act2)
  • How to order them? Collection pattern? or the sequential sequence? (Some stuff should be pushed to methodology?)

End of random notes

Dan: Wants to get some response domains defined. 

Issue: How to describe what the actual response domain is?

Goal - Basic questionnaire, workflow

**If methodology needs more information about an act, then they should add it to their patterns. 

Decisions

Use basic questionnaire to walk through the model. Perhaps using three examples to illustrate 1)prescriptive needs for designing a questionnaire 2) run-time needs for processes, and 3) archival needs for describing after data is received.


  • No labels