2025-01-27 Meeting Agenda and Notes

5 minutes

Check-in

• Michelle - new version changelog. Is that something that we could make - a detailed changelog in the newest version of ASpace?

  • Closest thing we have is the release notes. Release V4.0.0 · archivesspace/archivesspace

  • Trying to translate PRs and Jira tickets into summaries of differences between previous/current version.

  • This would be opportune time - start creating this with 4.0 and continue working on it in future releases to make it better/more readable.

  • Where to post this? A blog on the new techdocs website could work (could share a link to the blog on listservs too).

    • This could live as a separate page on the techdocs website.

    • Blogs could be a markdown file we contribute to in the techdocs repo.

  • We could make separate Jira tickets to assign different parts of the summary to individuals - compile our summaries together into a blog.

  • What we would do is more narrative/prose to translate the tickets/PRs into understandable language for users - different than what Christine does which is more machine-generated notes.

  • We would want to start on this before a blog page - just to get a Work In Progress/test case to write ourselves and send out for feedback.

  • What Michelle’s colleague created previously: https://docs.google.com/document/d/1p4zpYbaaQYrqVrfm9np1wSPidYbjU6EUo0v3RZnAekM/edit?usp=sharing

  • Thimios and Brian could review the PRs and release notes and condense for the techdocs team to take and review/summarize.

5 minutes

Discuss topics surfaced in listserv/community discussions

• Alexander - EAD Export maps

  • ArcLight migration, creating mapping of ASpace fields > EAD > ArcLight. Wanted an EAD mapping part of ASpace, but it wasn’t updated since 2013/doesn’t exist.

  • Do we want this to live on the data mapping and migration page on ASpace’s website?

    • Could live on techdocs website. Then we link it on the above page.

    • This would have a different audience - might be more geared toward metadata folks - not systems folks.

  • Also would this need to be updated every 2 years or some per-defined time period?

    • Could this be automated?

      • Alex not sure if there is an automated way to transform the code into mapping.

  • At next TAC meeting - bring up this issue to the Metadata Team to discuss cross-collaboration.

  • TODO:

    • Alex to research if possible to automate the process.

    • Talk with Metadata Standards to see if this could be shared project.

20 minutes

ArchivesSpace Technical Documentation + 4.0 released

• Bonnie - looks beautiful and very navigable.

• Thoughts on helping support the new release and techdocs website?

  • Work related to the website are in TD Jira board - https://archivesspace.atlassian.net/jira/software/projects/TD/boards/57 . If you want to pick up a ticket, let Brian/Thimios know via ping.

  • Feel free to open tickets on the board as ideas/brainstorming. This is why “New” column to discuss within ticket/here at these meetings.

• https://archivesspace.atlassian.net/jira/software/projects/TD/boards/57?selectedIssue=TD-24

  • Can fork the techdocs repo to your local machine then push PR. OR edit files in the repo directly in GitHub web interface (make sure you have permissions - check with Bonnie).

20 minutes

ArchivesSpace Endpoint Documentation

• New techdocs site and API documentation interact

  •  

• Assignments:

  • Jobs endpoints - Bonnie

    • Difficult to determine how to improve documentation because different jobs have different schemas.

      • Ex. Create a new job endpoint - in example there is a hint there are different types of jobs. But not clear where the schema for different types of jobs. That feels like outside the scope of API.

      • In API documentation on the techdocs website, nothing about job schemas, but does have Background jobs page.

      • Thimios wants to version the API documentation and API itself - that way there is better tracking for documentation and changes can be separately maintained. Wants to chat with Corey about future of API docs.

  • Search endpoint - Alex

  • Agents endpoint examples - Michelle

  • Groups endpoint examples - Corey

    • https://archivesspace.atlassian.net/jira/software/projects/TD/boards/57?selectedIssue=TD-28 - Thimios thinks it’s ready to review. Still in draft - ok to assign it - preferred to have PR submitted.

  • Classifications - Ojas

• TODO: if not working on API docs, people to review techdocs board for taking issues to do.