• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Whenever you search in PBworks, Dokkio Sidebar (from the makers of PBworks) will run the same search in your Drive, Dropbox, OneDrive, Gmail, and Slack. Now you can find what you're looking for wherever it lives. Try Dokkio Sidebar for free.


Meeting (2019-05-09) - Planning for Summer Research Camp 2019

Page history last edited by Alan Liu 3 years, 9 months ago


Meeting Time:       9 May 2019, 11am-1pm(Pacific)

Meeting Location: DAHC (Digital Arts & Humanities Commons) (directions)

Meeting Zoom:     We'll use Alan's "instant" Zoom ID (our default meeting Zoom):  https://ucsb.zoom.us/j/760-021-1662


Advance preparation for this meeting


0. Preliminary Business


  • Next all-hands meeting: Thursday May 23rd, 11am-1pm?
    • Can we get a new topic model with new visualizations ready by the Monday May 20th so that we can have people look at it, using at least one of the Qualtrics Interpretation Protocol modules before the meeting?
    • If so, then we can make the focus of the meeting a discussion of methods, tools, and workplan for answering research questions in the summer.  
  • Updates  
    • Collection work 
    • WE1S platform: Recent developments 
      • Model optimization
      • Pre-processing
      • Visualizations 
    • Hand coding exercise 
    • Human subjects research  


Purpose of today's meeting

  • Planning for Summer Research Camp 2019 



1. Summer Research Camp 2019





2. Research Questions for summer (continued)


I've taken the initial step of pruning and prioritizing the research questions we have so far come up with. See the second sheet in that spreadsheet titled "Research Questions (version 2)".


There is a new column in the sheet for "Priority level (1 is best)" and explanations of additional priority levels "x" and "z" in the header. Plus I've added explanations in a column titled "New Notes" (preserving our original notes in "Original Notes").


I am not sure of my choices and prioritizations (they are subject to your changes). But the logic I am following is this:


High priority is assigned to questions that:

  • seem to be cardinal questions for our project;
  • represent important parts of our corpus;
  • or bear centrally on project goals.


Lower priority is given to questions that:

  • are subordinate to other questions;
  • might be better staged later in the project;
  • may not be answerable based on materials and metadata we have.


In terms of our summer work plan: it's not necessarily the case that we tackle priority-level 1 questions first. We may decide that it's better to start with simpler, lower priority questions just to learn our interpretation workflow well before going on to the crucial questions.


Note also that I've not much tweaked the original forms of the questions or their operationalized forms, leaving that for later or for the summer teams.








Comments (0)

You don't have permission to comment on this page.