2023-02-01 Meeting Agenda and Notes

Owned by Rachel Searcy
Last updated: Feb 27, 2023
3 min read

Date

Feb 1, 2023 at 1pm EST

Zoom/Meeting Info

https://nyu.zoom.us/j/97593576221

Helpful Links

 

Previous Meeting Minutes

2022-12-07 Meeting Agenda and Notes

2022-11-02 Meeting Agenda and Notes (Meeting Canceled)

2022-10-05 Meeting Agenda and Notes

2022-09-01 Meeting Agenda and Notes

Participants

 

  • @Rachel Searcy

  • @Austin Munsell regrets

  • @Jenna Silver

  • @Elizabeth M. Caringola

  • @Blake Carver regrets

  • @Mark Cooper regrets

Goals

  • Assess workplan mid-way through year

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 minutes

Roll call

Rachel

Notetaker: Liz

5 minutes

Previous Month’s Action Items

Rachel

 

@Austin Munsell (and anyone else) Monitor email list for questions where reporter might benefit from pointer to the techdocs
10/25 from Amanda Focke at Rice University to archivesspace@googlegroups: “I have searched the ASpace doucmentation, but am not finding info on how to implement the "request" button on the public side so users can request boxes. Any pointers for me? Sorry if I missed an obvious source. I did search the user manual for "reference" and "request" but didn't find it.”
2 additional possible tech doc related messages: Mike <mike.uofs@gmail.com> 11/10/2022 re: jetty; Hutchinson, Tim <tim.hutchinson@usask.ca> 11/11/2022 re LDAP atuhentication and ASpace API; 3 other inquiries that look like bugs or user doc questions.
@Austin Munsell @Jenna Silver @Elizabeth M. Caringola @Rachel Searcy Consider talking with your local developers/system maintainers to get their opinions on the documentation, identify gaps, identify potential contributors
Austin hopes to do this in the coming month. Local developer is swamped with a large system migration. UPDATE: Austin checked in with the developer. They reported a) not having issues with the tech docs and b) not remembering anything about them…this is good?
Jenna asked her dev if he has noticed gaps in documentation; he says he’ll just go to the lists and ask and doesn’t consult the docs. A new dev starting soon, so she’ll chat with him as well.
Liz will ask her dev group after they complete the 3.3.1 upgrade this month. UPDATE: Might have info to share after meeting with them on Friday.

5 minutes

Repo check-in

Rachel


30 minutes

Workplan review


All

  • Review 2022-2023 TechDocs Work Plan :

    • What have we completed?

      • Clarify access to tech-docs repository and how to add new contributors. Thank you, Rachel!

      • Identify who on sub-team should be responsible for reviewing and merging pull requests. Subteam lead will do straightforward PRs, with more complicated ones (branch conflicts, etc.) best left to Lyrasis devs.

      • Rachel and Liz added info about the subteam to the Technical Documentation page.

    • What is in progress?

      • Documentation re: reviewing and merging pull requests

        • Rachel is working on this and will send to TAC to try it out and for feedback when finished.

      • Collab with User Docs

        • Had initial meeting to discuss opportunities to work together.

        • Outcome was User Docs would create a pointer to Tech Docs in the Help Center as a starting point. We could send a message to the community after this happens to bring attention to both set of docs.

      • How to best identify gaps in documentation: Survey? Trying to install ASpace ourselves using the docs? Cold call/email?

      • Later in the year: The ASpace Development Roadmap for 2023 included time for developers to work with us on improving the Tech Docs.

    • What might we have promised that is not achievable this year?

      • Consensus was that there’s nothing to remove from the work plan at this time.

  • Administrative Documentation page in progress: Technical Documentation

  • Virtual Forum? Submission form open until March 24

    • Ideas: How different users may use the Tech Docs, things I wish I had known were in the Tech Docs

    • Rachel will contact User Docs to see if they’re still interested in a joint proposal. Liz volunteered to be Tech Docs point person if they are.

Next meeting

 

 

March 1, 1pm EST

Action items

Continue as a group to monitor the listserv/group and answer any tech doc related questions
@Rachel Searcy Start documentation on reviewing and merging Github pull requests
@Rachel Searcy Contact User Docs to gauge interest in proposing a session for the virtual forum