UXR - Create wiki pages for research studies 14-16

[jberzowska]

Overview

We need to create wiki pages for all recent research studies to accomplish our research ops initiative.

Action Items

• [ ] review the internship's research page wiki template
• [ ] Use this format to create individual research plan pages for our most recent studies:
  • [ ] RP014
  • [ ] RP015
  • [ ] RP016
• [ ] Link to these pages from the Research Output Overview and from the research summary table

Resources/Instructions

• part of #1926
• internship team's template: https://github.com/hackforla/internship/wiki/research-wiki-template
• research study links: https://github.com/hackforla/311-data/wiki/Research-Output-%E2%80%90-Summary-Table
• example from the internship team: https://github.com/hackforla/internship/wiki/Research-Plan-23:-Interns-Application-Interviews
• Other RPs (not ready to move forward on)
  • [ ] RP017

[jberzowska]

When I spoke to Bonnie this spring, she had emphasized that she would like these summary pages in the same format as other teams have them.

Notes for product:

• I think it makes sense to batch these and to work backwards from the present. That said, is this too many pages to put in one ticket?
• Would you like this added to the research documentation epic, the research ops epic or both?

[danagfleming]

Hey @jberzowska ! Working on getting this prioritized, I just have one clarification question - is our "research ops initiative" a formalized plan? If so can you link to any related materials? Otherwise, if it's just our general goal of getting the program rolling, we are all good and I will get it moved. Thanks :-)

[jberzowska]

@danagfleming - Yes, we're documenting all of the ops tickets in #1926. I'm sorry I've been forgetting to link the epic.

There was another ticket to try to layout all of the details in one doc, but I'm currently suggesting we close that and stick to adding things to the epic as we need them. Does that work?

[danagfleming]

@jberzowska Okay perfect! Thank you, I'll move this over into the backlog. Closing that ticket makes sense to me but I'll let @ryanfchase make the final call on that

[ryanfchase]

I updated the milestone to 10.03, which is a better fit than Ongoing, which typically exists for Agendas, Onboard/Offboard tickets, etc.

[ryanfchase]

@jberzowska yes, I think I see what you mean about closing #1955 as a duplicate of the epic. PMs will review #1955 to make sure all pertinent info is copied over, then we can close as duplicate.

Click to see supporting discussion thread

(context) from earlier discussion on this ticket... JB: There was another ticket to try to layout all of the details in one doc, but I'm currently suggesting we close that and stick to adding things to the epic as we need them. Does that work?

(context) The other ticket: https://github.com/hackforla/311-data/issues/1955#issuecomment-3304098630 JB: I'm starting to think this ticket is a duplicate of the epic. We're doing a lot of this thinking in #1926, and we are taking on one piece at a time as they become clear. Maybe we close this as a duplicate? Thoughts?