/
2026-03-17 Documentation Interest Group meeting notes

Samvera Community Wiki

2026-03-17 Documentation Interest Group meeting notes

Zoom link

 Participants

  • @Sarah Proctor -

  • @Morgan McKeehan -

  • @Rebekah Kati

  • @Nic Don Stanton-Roark

  • @Heather Greer Klein

roles

  • mtg facilitator Sarah

  • mtg notetaker Morgan

 

 Agenda

  • Any questions or topics from DocIG participants?

  • check in about any docs support needed for Accessibility

  • quick check on action items from Feb.17 IG mtg

  • decision from Feb.17 DocIG mtg:

    • Q: For modules/functionality that are in both Hyrax and Hyku, do we have a policy/established approach about: is there a “default” location where the documentation for it resides?

    • Documentation for items in Hyrax and Hyku should be in Hyrax and be linked as needed to the Hyku pages

  • Categorizing/prepping tickets in Doc Tasks Board

    •  Any issues that need coordination/feedback with other groups? 

 Discussion notes

  • Documentation sprint is being confirmed -

    • tentatively scheduled for week of May 18 - HGK will confirm date, and is waiting to announce the Docs Sprint until after Community Sprint, to avoid confusion about diff sprints

  • Sarah P enabled labels in doctasks board so the Accessibility label should show up now

  •  

 

 Action items

Morgan make a draft in doc-tasks board: someone check for a Hyku Accessibility Documentation page, (an equivalent to Hyrax docs Accessibility page)
(the Hyku Accessibility page can be a good pilot/test case for conforming with general approach about modules/functionality that are in both Hyrax and Hyku) - Hyku may have addt’l Accessibility functionality requirements - since it has addt’l features to Hyrax
Rebekah will check with Nick H about potentially consolidating or connecting the Hyrax Accessibility docs pages
Morgan - check in doc-tasks board overall for other tickets that we can add the new Accessibility tag to
Morgan - check if we can make an “Accessibility” view in doctasks board, now that the Accessibility label is visible there. This could be useful to have for the community sprint?
Morgan - write a description of Project Board workflow for drafts -> issues. Add to Project Board instructions page.
include updated instructions for custom fields (for the dropdown values for all custom fields)
also include: labels vs. custom fields. Why labels are not available to drafts.
when to convert a draft to an issue, and which labels are then available. Also note what happens to custom fields from drafts, when a draft is converted to an issue.

 Decisions