Create Assessment Questions

[kallewesterling]

• Make sure you are in the right branch and have recently pulled all the content from the GitHub repository before you start working.

• Create a assessment.md file in the root directory of your repository
  Here, you can find the template for assessment.md. Copy the contents into the new file in your repository.

• Complete the quantitative self-assessment section

  • Use ## Quantitative Self-Assessment to indicate the beginning of the section.

  • Move all the relevant quantitative self-assessment questions from DHRI/DRI exit slips found in the GCDI Google Drive over to this file.

  • Each question should be a regular paragraph.

  • Each question should have multiple choice answers, added as bullet points under the paragraph (in markdown, you use - on a new line to create a bullet point).

  • Make sure that the questions enable the learner to evaluate their understanding of specific concepts from the workshop.

• Complete the qualitative self-assessment section

  • Use ## Qualitative Self-Assessment to indicate the beginning of the section.

  • Move all the relevant qualitative self-assessment questions from DHRI/DRI exit slips found in the GCDI Google Drive over to this file.

  • Each question should be a regular paragraph.

  • For each question, think of readings/tutorials/projects/challenges from the "Theory to Practice" section to direct them to, and add a note of that as a bullet point under relevant questions (in markdown, you use - on a new line to create a bullet point).

  • Make sure that the questions enable the learner to evaluate their understanding of specific concepts from the workshop.

[kallewesterling]

move over from the exit slips (from DRI and DHRI) - see the GCDI google account.

[kallewesterling]

The assessment section looks great here! I am, of course, thinking more about how we can move into programmatically getting this into our interface and create some interactivity around this, in the Django version that we're developing. It is definitely not going to happen for this sprint but perhaps in a later alpha-version, like second or third sprint around, we can see if we can move that up to priority for me. Then we might have more assessment sections finished for workshops, and I can see what I can do with it. And it would also give us some time to sketch out what we envision that feature to look like.

[lmrhody]

The only problem thus far is that "self-assessment" doesn't really describe it. So, for example, the self-assessment "quantitative" questions are really just multiple choice questions, but they're as much for us as they are for the user. However, assessing whether or not the user understands what a work plan is... that's a different kind of assessment. So, what I'm thinking is that we need to maybe look at all the different types of questions, and maybe describe them differently-- maybe even making it obvious what we want to assess. For example, one is about how valuable the workshop was for the person. Another question is about information retention. Another is about the lesson value, etc. etc. I think we could probably find better headings for these... but I'm glad we've got the process started.

…

On Tue, Jun 16, 2020 at 10:56 PM Kalle Westerling ***@***.***> wrote: The assessment section looks great here! I am, of course, thinking more about how we can move into programmatically getting this into our interface and create some interactivity around this, in the Django version that we're developing. It is definitely not going to happen for this sprint but perhaps in a later alpha-version, like second or third sprint around, we can see if we can move that up to priority for me. Then we might have more assessment sections finished for workshops, and I can see what I can do with it. And it would also give us some time to sketch out what we envision that feature to look like. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKUYUO63SOSGFUIYQVEKZDRXAWE7ANCNFSM4NS5QMMA> .

-- Lisa M. Rhody, Ph.D. Deputy Director of Digital Initiatives Director of Digital Fellowship Programs Director, Digital Humanities Research Institutes The Graduate Center, City University of New York [email protected] | @lmrhody

[kallewesterling]

Thinking beyond this particular workshop and for the project as a whole:

Maybe we should keep calling them exit slips? Do we need to rename them? I kind of like the idea of seeing us use the language that we have, as exit slips emphasizes that the "assessment" is not something impersonal that happens after you are "done" but rather when "leaving the room"... so, if we could contextualize that for the user on the website, perhaps we could call these "exit slips" still, and maintain clarity in what these questions are, and why we're asking them.

[kallewesterling]

Opening a new issue, #18 Describe assessment differently, as this seems to be a conversation for sprint 2 + also goes beyond the scope for issue #8.