User:TBurmeister (WMF)/GLAMToolhub

This page is currently a draft. More information pertaining to this may be available on the talk page.

Translation admins: Normally, drafts should not be marked for translation.

This is a draft of a session proposal by TBurmeister for WikiCon North America 2024. Proposals are due May 31.

What is the session?

An edit-a-thon focused on adding Toolhub annotations for GLAM tools.

Goal 1: Improve the usability of Toolhub for finding GLAM tools and their documentation:

Improve the discoverability of GLAM tools in Toolhub by improving coverage and quality of attributes introduced in the v2 Toolhub taxonomy: audiences, tasks, content types, subject domains (i.e. GLAM subject ___domain).
Improve the findability of GLAM tool documentation by adding links to user and developer docs in Toolhub records. (This lays a foundation for future edit-a-thon work to improve the tool documentation itself.)

Goal 2: Expand the GLAM community's awareness of Toolhub and tool documentation best practices.

Reasons for focusing on GLAM tools:

A specific scope is crucial for coordinating edit-a-thon-style event tasks;
Many lists of GLAM tools already exist and are relatively recent thanks to work like the Content Partnership Hub;
WikiCon NA usually has a strong presence of GLAM folks in attendance.

Outline of what the process might look like:

Resources to be covered / prerequisites:

Phabricator account & basic usage
Wikimedia account + linked to Toolhub
Basic understanding of how and why Toolhub annotations are useful + guidance about how to decide which annotation values to apply (and how to not overthink it)

Pre-work to be done by organizer(s):

Create Phabricator tickets: one for each tool that appears on multiple of the lists of GLAM tools. Tickets should include:
- Link to the tool's Toolhub record
- Link to (or some abbreviated version of) the process instructions for the annotation tasks
Figure out how to have a leaderboard of some sort and track contributions during the conference
Prepare an intro/pitch deck for orienting participants to the project

Can Toolhub handle ~50 (max) concurrent annotation editors making changes? Would we run into any IP blocking / spam-resistance tooling?

Resolved. bd808 says this would not be a problem

What are good existing options for logistics like leaderboards based on phab tasks?
- Toolhunt is great but wouldn't quite work for this use case because it doesn't (yet) support specifying the tool info field you want to edit.
- Comments from bd808 (copied from early draft doc):
  - https://toolhub.wikimedia.org/audit-logs might be useful to pull reports of changes made by during a date range by a user. The same information is available via the https://toolhub.wikimedia.org/api/auditlogs/ endpoint which would allow scripting of reports.
  - https://toolhub.wikimedia.org/recent and https://toolhub.wikimedia.org/api/recent/ is nearly the same data. The main difference is that the audit log feed contains information about things beyond content edits like account attachment and user permissions changes.

Content Partnerships Hub lists:

Other lists and resources relating to GLAM tools: