EA: Documenting research process in Wiki

[ValeriyaMetla]

Dependency

• Summarizing key takeaways from review of past research #600

Overview

The EA Wiki page doesn't have any information about research activities. We need to develop a research section in the projects' Wiki.

Action Items

• Review an example of how another HfLA project - tdm-calculator - document their usability testing process.
• Add examples from other HfLA projects with good research folder structure
• Construct timeline of the past research
  • identify relevant document to upload to Wiki
  • Summarizing key takeaways from review of past research #600
  • write each project in the portfolio style to then build into WIKI
• document research preparation for usability testing
  • internal: IUT1; IUT2
  • user dependent on completion of Identifying target user #1387
• build an internal wiki on GitHub

Working Drafts

Research Timeline
Past Research Page for Wiki
Last updated in Oct 2022: GitHub Wiki

Resources/Instructions

• example: TDM Calculator - usability study
• example 1: Access the Data - research folder
• Research Summmary - Record Clearance
• example: Intern Research Plans and Goals

[ExperimentsInHonesty]

@ValeriyaMetla I came across this in my notes and thought it would make a good addition to the wiki when you document the service map we created for new way of life
https://law.ucla.edu/academics/centers/critical-race-studies/race-and-re-entry-initiative

[ValeriyaMetla]

Hi everyone,
To make it super simple, let's each contribute one thing that is useful for new researchers to know when they join the project. Draw from your own experience when thinking about it.

For me, I wish there was an organized history of the project's research! Essentially, if there was a Wiki page where I could go and access the past research. I would want to know the timeline of research, key insights, and how those influenced product iterations and the business side of product development.

Thank you for your feedback!
Val

[ValeriyaMetla]

Also, feel free to just randomly contribute any thoughts about how the research page of the project's Wiki can look like in terms of structure, content, and anything I might be missing. We basically need to design our page:)

[ghost]

Seconding Val, re: the timeline of research. That would be really helpful for new people to understand what's going on now. I also saw that there's a link for a Glossary that was never made. That could also be useful!

…

On Sun, Mar 6, 2022 at 7:54 PM ValeriyaMetla ***@***.***> wrote: Also, feel free to just randomly contribute any thoughts about how the research page of the project's Wiki can look like in terms of structure, content, and anything I might be missing. We basically need to design our page:) — Reply to this email directly, view it on GitHub <#473 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALNF4YJ4QTJ6TQA24OJ74O3U6V4WBANCNFSM5OQBXFXQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were assigned.Message ID: ***@***.***>

-- <http://goog_867028585> https://jbsteinhardt.com/

[SamHyler]

@ValeriyaMetla I'm putting the reminder here for you that 'how to use Github' for our project (how to use labels, how to write an issue, where to put them, etc.) should be added to the wiki somewhere.

[Ndoyle118]

Agree with all previous comments! I also thought it was very helpful in the TDM Calculator Wiki that a section/link to a "Website Landing Page" was included - it would be nice to have an easily accessible way for the research team to see a visual of the current version of the website/tool. For me, it initially took a bit to locate the figma prototypes of the EA personal statement generator., but once I did, it helped clarify quite a bit about the project!

[ana-lobos]

Maybe not essential, but following from the timeline comments I'd find it helpful if the page had some sort of calendar showing not only the timelines/deadlines for the project, but also the meetings we attend and everything else we're doing at a given point. Like an activity dashboard of sorts that has all in one place (hope that makes sense!). I'm picturing something along the lines of "what's on this week/month" as a calendar view. I think that would also showcase how active we are as a team :)

[ghost]

That would be helpful. For me, the thing that was most confusing was landing as a new person on the project and not really understanding where we were in the process -- like, what had already happened, what we are working towards now, and what we're doing in that linear context (if that makes sense). I think the research timeline and the folder that Ana just made will help to answer these questions, and we can link to all of this in the Wiki.

…

On Fri, Mar 11, 2022 at 10:10 AM ana-lobos ***@***.***> wrote: Maybe not essential, but I'd find it helpful if the page had some sort of calendar showing not only the timelines/deadlines for the project, but also the meetings we attend and everything else we're doing at a given point. Like an activity dashboard of sorts that has all in one place (hope that makes sense!). I'm picturing something along the lines of "what's on this week/month" as a calendar view. I think that would also showcase how active we are as a team :) — Reply to this email directly, view it on GitHub <#473 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALNF4YORDADR6UQU4QCNNBLU7OEDBANCNFSM5OQBXFXQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were assigned.Message ID: ***@***.***>

-- <http://goog_867028585> https://jbsteinhardt.com/

[Thomas-Pietruszewski]

I definitely felt this way as well! Having an organized timeline I think will help contextualize what's been done, what's being done, and what we'll be working on in the future.
Regarding the wiki I think having links to original sources of information embedded into the different sections will be useful for verifying if information is correct/up to date as well.

[raeraeicky]

@sylvia-nam since @melissareca is no longer on this project, should we reassign this issue to close out?

[sylvia-nam]

@raeraeicky I took Melissa off, but we should discuss this issue to either: 1) build a new one and close this one, 2) modify this one. It's been on the board since 2022

[raeraeicky]

@sylvia-nam Let's discuss it in the Monday meeting! I'll add it to the agenda

[raeraeicky]

Closing this issue after discussion with @sylvia-nam and @saraisabelcf. Will look into documentation as it exists currently and create any needed new issues, and user usability testing can't be completed until target user is identified (#1387).