Page MenuHomePhabricator

Assess data access doc collections
Closed, ResolvedPublic


In 2022 July-Sept this task tracked our investigation and iteration on how to audit a group of docs. ("What are the meaningful assessment techniques? What tools are useful? What criteria do we repeatedly look for as tech writers, and how can we translate those into something anyone can use?") The outcome of that was, and an audit of the Pywikibot doc collection. (see subtasks)

For tracking work in 2022 Oct-Dec, I'm repurposing this task for simplicity to capture the work that includes and goes beyond the Data_dumps and Research:Data collection assessments.

Event Timeline

KBach changed the status of subtask T312993: Assess Quarry collection from Open to In Progress.Aug 17 2022, 9:34 AM
TBurmeister changed the task status from Open to In Progress.Sep 20 2022, 8:37 PM
TBurmeister claimed this task.
TBurmeister triaged this task as Medium priority.
TBurmeister updated Other Assignee, added: KBach.

I'm now going to follow the process documented at mw:Documentation/Toolkit/Collection_audit to assess the documentation landscape for the topic of "data access". I already know that work is going to explode beyond to include docs at:

Therefore, I'm going to decline T312996 and T312995 in favor of tracking this larger scope of work in this task, which I'll rename to more accurately reflect the work for Q3 FY22/23..

TBurmeister renamed this task from Assess document collections to Assess data access doc collections.Oct 25 2022, 6:54 PM
TBurmeister updated the task description. (Show Details)
TBurmeister moved this task from To-Do to In Progress on the Developer-Advocacy (Oct-Dec 2022) board.
TBurmeister changed the task status from In Progress to Stalled.Nov 4 2022, 2:58 PM

Moving this to "stalled" because it's not prioritized work for Dev Advocacy this quarter and will take a significant amount of time, including input and collaboration with the Research & Data Eng teams, to really do this effectively. Plans/hopes to revisit in the coming quarters.

@TBurmeister All subtasks are resolved or declined. Can this ticket be resolved?

TBurmeister claimed this task.

Yes, resolving. Future work on data access docs will be tracked under T193296 and other tasks, since it's planned as part of "hypothesis" work that data teams are doing as part of the FY23-24 annual plan.