hackforla / internship

The Internship project provides an opportunity for students to work on open source projects in the fields of software, product development, project management, and UI/UX research and design at LA’s fastest growing Civic Tech non-profit organization during their summer.
GNU General Public License v2.0
15 stars 4 forks source link

TWE: IS21: RP001: intern Exit Interview Recordings: De-identify: Intern 005 #480

Open pandanista opened 8 months ago

pandanista commented 8 months ago

Dependencies

- [ ] All the user interview issues have been created IS21 didn't set up those issues, but all interviews were conducted. See TWE: IS21: RP001: Intern Exit Interview Roll Call and Session Table - [ ] Interview Recording Upload Form needs to be created The interviews were conducted before we set up the upload form, so it doesn't apply in RP001's case

Overview

We need to clean up and de-identify RP001's Intern Exit interview transcripts so that we can move on to the data analysis and insights generation phase.

During these tasks, you will be asked to add links to the Resources/Instructions section, and that section is at the bottom of this issue (go view it now).

Another tip is to use split browser windows side by side when working on any GitHub issue, so you can edit the issue on one window, and check the resources or click through links on the other window to avoid a lot of back and forth. Make sure to refresh both windows to reflect any changes you made, including updating the issue or checking the boxes on one of them.

Action Items

Customize Resource Links

Clean up and de-identify the transcript

Resources/Instructions

Resources for creating this issue

1.01 Wiki: Research Output Overview 1.02 Google Drive Folder: Research by Type 1.03* TWE Interview Recordings by Plan # 1.04 Guidelines to Interviews Page 8 1.04.01 Brackets vs. Parentheses 1.04.02 Video folder 1.04.03 Cleaning Up Zoom Transcriptions for Qualitative Research 1.04.04 Determining Best Practice for Filler Words in Captions and Transcripts

Resources gathered during the completion of this issue

2.01 Wiki: Research Plan RP001 2.02 Google Drive Folder: RP001 2.03 TWE: IS21: RP001: Intern Exit Interview Recordings and Transcriptions Tracking Sheet 2.04* RP001 Interview Recording Folder 2.05 RP001 De-identified Transcripts 2.06 Intern 005 Recording Link 2.07 Intern 005 Transcript .txt File 2.08 Intern 005 To be De-identified Transcript Google Doc 2.09 Intern 005 De-identified Transcript Google Doc

*This folder can only be accessed from the Internship - PII's "My Drive"

pandanista commented 8 months ago

Hi @AndrewSalvatore, I assigned intern 005's transcript de-identification issue to you cuz I remember you were working on it.

Also, this issue is based on a new template, so you will need to gather the links again. It might be easier for you to copy from the resources section from #355.

For context, I've split the original transcribe template into two: one for transcribing and setting things up, and the other one is for de-identification.

Let me know if you have any questions.

pandanista commented 8 months ago

@AndrewSalvatore FYI: I've updated the issue above and created a to be de-identified Google doc in the intern 5 folder. Thank you for your feedback.

AndrewSalvatore commented 8 months ago

Progress: 25% done with transcript cleaning/deidentifying Blockers: none Availability: 6 hours ETA: next Tuesday Pictures or links (if necessary): none

AndrewSalvatore commented 8 months ago

Progress: 80% done with cleaning/deidentifying Blockers: none Availability: 6 hours ETA: today Pictures or links (if necessary): none

pandanista commented 7 months ago

@AndrewSalvatore Thank you for working on this issue. The transcript looks good. I made some minor edits to clarify a few sentences. It is ready for the Product to review now.

@sunannie27 Would you please review the deliverable in Resources 2.09? Thank you.

sunannie27 commented 7 months ago

@pandanista We think it may be better if we color code the interviewer/interviewee portions or create an icon so they can be better distinguished.

pandanista commented 7 months ago

@sunannie27 We have decided not to color code the transcript for now since the analysis stage will involve color coding.

Drew has updated the transcript by incorporating the intern number, please see the updated de-identified transcript linked in Resources # 2.09. Let me know if there is anything else needed. Otherwise, we can close this issue after Product's final review. Thank you.

pandanista commented 7 months ago

We need to decide on the format of the timestamps (00:00:00 vs 00:00).

pandanista commented 7 months ago

@AndrewSalvatore Would you please take another look at the transcript?

We have decided at the all-team meeting today, that instead of Grammarly, please use LanguageTool Chrome Extension to clean up the punctuation and verbal ticks in the transcript. Thank you very much!

I've copied Resources 1.04 below for easy reference on how to clean up the interview transcripts. 1.04 Guidelines to Interviews Page 8 1.04.01 Brackets vs. Parentheses 1.04.02 Video folder 1.04.03 Cleaning Up Zoom Transcriptions for Qualitative Research 1.04.04 Determining Best Practice for Filler Words in Captions and Transcripts

pandanista commented 6 months ago

@AndrewSalvatore Welcome back, and hope your 2024 is off to a good start.

Would you please provide an update?

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?" - we know you just came back from break, please just summarize the progress from before then
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
pandanista commented 6 months ago

Added a few guidelines on the transcript formatting. You are already following most of them. I am listing them below as a reference.

  1. Use the 'in-line' format as seen here in Intern 001's transcript
  2. Use 6 digit format for all the timestamps, for example, 01:01:01 as hour one/minute one/second one
  3. Use "Interviewer" and "Intern ###" throughout the transcript. See an example here in Intern 001's transcript.
    • If there were more than two people recorded on the transcript, name the third person based on the interview set-up or context, such as Program Manager, Note Taker, etc. If you are not sure what to name them, ask leads on the project to clarify.
  4. If there are other numerical values in the transcript, transcribe them using texts. For example, if a time such as 6:30 is mentioned, type out six thirty when cleaning up the transcript. Another example is if the interviewee mentioned he mainly sought help from 3 other peers, type out three instead of using the number 3.
sunannie27 commented 5 months ago

@AndrewSalvatore Please provide update

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
pandanista commented 5 months ago

@AndrewSalvatore Hi Drew, would you please provide an update on this transcript?

I included some more instructions and resources in comment 1 and comment 2 above so we can stay consistent when cleaning up the transcript. Let me know if you have any questions.

AndrewSalvatore commented 5 months ago

Progress: Reviewed the transcript and it looks like the formatting abides by all the rules mentioned in @pandanista's comments Blockers: none Availability: 6 hours ETA: done Pictures or links (if necessary): none

pandanista commented 5 months ago

Awesome. Thank you, @AndrewSalvatore.

@sunannie27 I reviewed the transcript, and it looks good to me. Would you please review the transcript in Resource 2.09 before we close the issue? Thank you!

sunannie27 commented 5 months ago

@AndrewSalvatore We noticed this large paragraph of text in the transcript and thought there should be a paragraph break before "As for help". If there is a lot of talking by one person and there are places that seem logical for a separate paragraph tag, then we should insert them for it to be easier to process.

Paragraph without breaks (currently in the document)

There weren't really any issues in Java. I think there's only one team in Hack for LA that really uses Java, and also because almost all my knowledge in Java was mostly just from school I never really… I mean I'd made programs obviously for school work but never actually worked with it in a professional setting before. I don't really know what motivated me but I think it was because I had to learn so I did learn. As for help, what I did at first I usually just Googled to see if I could just find something that explained to me how to fix the problem, or what to do. Because also usually with the issue they usually gave a pretty good description of what you needed to do and also they usually give you resources to check out so that you could check on the things that they thought that you would probably need to use to complete the issue. If I couldn't figure it out that way, I'd usually just reach out on the Hack for LA site channel or there were some other people I would just direct message and ask like “Hey, can you help me?” And then for one of the issues, it was for… because my first large issue was also my first back-end issue I also got a couple of mentors to help me out. Oh, actually no. Really only one [mentor].

Paragraph with breaks

There weren't really any issues in Java. I think there's only one team in Hack for LA that really uses Java, and also because almost all my knowledge in Java was mostly just from school I never really… I mean I'd made programs obviously for school work but never actually worked with it in a professional setting before. I don't really know what motivated me but I think it was because I had to learn so I did learn.

As for help, what I did at first I usually just Googled to see if I could just find something that explained to me how to fix the problem, or what to do. Because also usually with the issue they usually gave a pretty good description of what you needed to do and also they usually give you resources to check out so that you could check on the things that they thought that you would probably need to use to complete the issue.

If I couldn't figure it out that way, I'd usually just reach out on the Hack for LA site channel or there were some other people I would just direct message and ask like “Hey, can you help me?” And then for one of the issues, it was for… because my first large issue was also my first back-end issue I also got a couple of mentors to help me out. Oh, actually no. Really only one [mentor].

sunannie27 commented 5 months ago

There is a break used with hyphens but hyphens should only be used if there is an emphasis on what was said in the interview, otherwise use commas.

I really appreciate you sharing your honest feedback, and your responses were very insightful. So thank you so much for that. I really appreciate you taking the time to share your journey, your experience, your hiccups, and everything else. Thank you. Getting feedback from you - as I mentioned before - is really going to help us improve and enhance the program for our prospective interns. And hopefully it'll enable students interested in STEM programs to learn and move forward with confidence in their workspace. So, I really appreciate your time, and it looks like we're pretty motivated!

sunannie27 commented 5 months ago

Made the above changes and signed off on it.

pandanista commented 4 months ago

Thank you for being so patient with us, @AndrewSalvatore!

Would you please update "interviewer" with "UXR 001" in intern 005's transcript? Much appreciated!

We decided to include the UXR numbers in the transcripts because 1). there might be different probing questions for semi-structured interviews from different interviewers, and 2). it will be easier to reference the UXR when doing analysis or making highlight reels (if needed).

AndrewSalvatore commented 4 months ago

Thank you for being so patient with us, @AndrewSalvatore!

Would you please update "interviewer" with "UXR 001" in intern 005's transcript? Much appreciated!

We decided to include the UXR numbers in the transcripts because 1). there might be different probing questions for semi-structured interviews from different interviewers, and 2). it will be easier to reference the UXR when doing analysis or making highlight reels (if needed).

@pandanista Done

pandanista commented 4 months ago

Thank you very much, @AndrewSalvatore. I am closing this issue since it is all done.

pandanista commented 1 month ago

Let me know if you have any questions. Thank you.