Open pandanista opened 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.
@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.
Progress: 25% done with transcript cleaning/deidentifying Blockers: none Availability: 6 hours ETA: next Tuesday Pictures or links (if necessary): none
Progress: 80% done with cleaning/deidentifying Blockers: none Availability: 6 hours ETA: today Pictures or links (if necessary): none
@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.
@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.
@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.
We need to decide on the format of the timestamps (00:00:00 vs 00:00).
@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
@AndrewSalvatore Welcome back, and hope your 2024 is off to a good start.
Would you please provide an update?
Added a few guidelines on the transcript formatting. You are already following most of them. I am listing them below as a reference.
@AndrewSalvatore Please provide update
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
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!
@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.
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].
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].
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!
Made the above changes and signed off on it.
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).
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
Thank you very much, @AndrewSalvatore. I am closing this issue since it is all done.
Reopening this issue since we need to track people being mentioned in the transcripts.
[ ] UX Research Lead assigns the assignee to the PII drive so they have access to the recording and original transcripts
Fill out any individual's name and relevant information in the TWE: IS21: RP001: Participants List from Interviews (Interns & UXR Excluded) spreadsheet by following the steps below:
[ ] UXR Lead will review the TWE: IS21: RP001: Participants List from Interviews (Interns & UXR Excluded) spreadsheet
[ ] UXR Lead will add the de-identified participants' information to the TWE: IS21: RP001: De-identified Participants List from Interviews (Interns & UXR Excluded) and save in RP001's folder in the shared Google Drive
Let me know if you have any questions. Thank you.
Dependencies
- [ ] All the user interview issues have been createdIS21 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 createdThe interviews were conducted before we set up the upload form, so it doesn't apply in RP001's caseOverview
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
Customize Resource for Wiki Page Link
]
and the left parenthesis(
, so it turns into a hyperlinkCustomize Resource for this Research Plan's Google Drive Folder
Intern
folderRP001
folderRP001
folderRP001
folder]
and the left parenthesis(
, so it turns into a hyperlinkCustomize Resource for Interview Recordings and Transcriptions Tracking Sheet
TWE: IS21: RP001: Intern Exit Interview Recordings and Transcriptions Tracking Sheet
in the folderTWE: IS21: RP001: Intern Exit Interview Recordings and Transcriptions Tracking Sheet
]
and the left parenthesis(
, so it turns into a hyperlinkCustomize Resource for Interview Recording Folder stored in the Internship - PII's
My Drive
TWE Interview Recordings by Plan #
folder in Internship - PII'sMy drive
(Resources # 1.03)TWE Interview Recordings by Plan #
]
and the left parenthesis(
, so it turns into a hyperlinkCustomize Resource for the De-identified Transcripts Folder in the Shared Drive
RP001 De-identified Transcripts
folder]
and the left parenthesis(
, so it turns into a hyperlinkCustomize Resources for the Recording and Transcript you are Assigned to
De-identify:
TWE: IS21: RP001: Intern Exit Interview Recordings and Transcriptions Tracking Sheet
(Resources # 2.03)]
and the left parenthesis(
, so it turns into a hyperlink]
and the left parenthesis(
, so it turns into a hyperlinkTranscription Link
that matches the participant number (Resources # 2.07)Open with Google Docs
Copy of
from the file name when the Rename text box pops up]
and the left parenthesis(
, so it turns into a hyperlinkClean up and de-identify the transcript
RP001 De-identified Transcripts
folder. This is to make sure that the version history does not include any identifiable information.Transcription Link - de-identified
in the tracking sheet (Resources # 2.03)]
and the left parenthesis(
, so it turns into a hyperlinkResources/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"