2026-01-26 Meeting Agenda

Introductions

Joint meeting between the User Docs and Tech Docs sub-teams

Overview of UserDocs and TechDocs charges/responsibilities

• How do you prioritize/keep track of tasks for your team?

• How do you involve the overall ASpace community in your work?

• How often do you get contributions from the community?

TechDocs website and JIRA board: ArchivesSpace Technical Documentation , https://archivesspace.atlassian.net/jira/software/projects/TD/boards/57 https://archivesspace.atlassian.net/wiki/x/CQC4IQE

Tech Docs is focused on the implementation side of getting users ready to implement ASpace.

Opportunities for cross-collaboration

• config file documentation for users and tech folks

  • Is there something in the user manual that could explain it more higher level?

When making updates to user manual, are you maintaining versions based on different versions of ASpace?

User Docs: When big changes happen, generate new page with version number in title. Old info is put as subpage underneath current info.

How do you manage your workboard, JIRA board?

User Docs:

• 6 team members and use a Google sheet to assign work.

• Currently not using ticket system/Jira.

• User Docs has a long history that has done a lot of own work to standardize processes. Members of the team add themselves as watchers of different sections of the user manual (and secondary watchers to other sections).

  • Reviewing manual and refreshing screenshots for assigned sections

    • Templates and styleguides for all the above

    • Process for taking screenshots, guide for how to review pages

Tech Docs:

• Use JIRA because of close collaboration with ASpace developers

How do you receive feedback on the manual?

User Docs: Comments directly on the page, the ASpace listserv, or direct emails to the ASpace team

For users who are hosted, what do I need TechDocs for?

• Front-end configuration settings - these things you can ask your host to change to improve institutions’ experience.

• Also using the API

How does TechDocs plan on keeping awesome-archivesspace updated and new content added?

• Still in the early stages to determine how to actively solicit additions to the list.

  • May present at an upcoming Virtual Member Forum

• Developing documentation outside of GitHub for awesome-archivesspace

• There is not documentation re: API docs

How did the process for adding watchers/secondary watchers come about?

Trial and error - people writing pages and taking ownership. Then move from separate place to generate the documentation to Confluence meant the “watcher” feature was available.