2024-04-10 Documentation Working Group Agenda/Meeting Notes

note takers for today: Amanda R., Brandon K.

next meeting:  May 8th

note takers for the next meeting: Martina Tumulla, Lisa Lorenzo

Katharina: Deadline for Session Proposals for WOLFcon has been extended to April 30th

Katharina: German translation project is online via: https://poppy-i18n.d2dtr4k5dz0jv3.amplifyapp.com/de/docs/users/. Feedback welcome.

Martina: PC: Doug Lyons presented ideas, plans and work on Linked Data Module. Link to PC meeting minutes incl. slides. 

Amanda: MM SIG contact concerning a volunteer for settings >tenants

• No volunteers yet

Katharina: Getting information about GitHub's background not easy, it seems that Ian is the only one person who can push the documentation's update to the website. Julian gave me some more information about GitHub and that he has the opinion the new branches should be created as late as possible to reduce finishing work.

Laurence: RA SIG contact concerning a volunteer for settings > tenants documentation

• No volunteers yet

Martina: to add terminology document contents to https://docs.folio.org/docs/about-folio/ and potentially revisit first paragraph to align

• Terminology document should be unchanged and will be included on the website

Martina & Katharina registered a 50 minutes timeslot community sharing for the WOLFcon

Molly: contact Julian and Ian concerning search field's problem with small screens or shrink browser window.

• Julian provided this response and I tagged Katharina and Martina for confirmation because I'm not sure who is able to authorize an upgrade: https://folio-project.slack.com/archives/C01LZK2JAUE/p1711539640532709?thread_ts=1707925695.005479&cid=C01LZK2JAUE
• Would need to consider difficulty and time involved in upgrade. Will clarify with Julian how different the theme upgrade would be and the extent it would affect current site.

Molly: contact Owen re: Serials app documentation

• Martina Schildt and Peter Sbrzesny are still looking for a volunteer within GBV. They agreed that you we can add their names provisionally for that section of documentation and they will contact Katharina when they secure a final volunteer.

Serials App: wg representative? where to localise in the documentation? branches in Google/GitHub already exist?

• Please see above. Molly's opinion would be to add the Serials app documentation under Resource Management.

Settings > tenants:

ERM > eComparisons: Katharina is in contact with possible volunteers

• Martina Schildt also said she would check for volunteers.

ERM > eUsage: no success with contact to Leipzig, any other ideas for volunteers?

• Will keep checking

ERM > Local KB admin: Katharina is in contact with possible volunteers

• Martina Schildt also said she would check for volunteers.

MM/Cataloging > QuickMARC: also Lisa and not yet in the table?

Inconsistency in links

• Example code from github: 
  • "See [Settings > Acquisition units]({{< ref "/settings_acquisition_units.md" >}}) for more information" – this style of link goes to the default flower release documentation (currently Poppy). See for example in https://orchid.docs.folio.org/docs/acquisitions/orders/, click on the Settings > Acquisition units link, it jumps to Poppy release notes. Contrast this behavior with any of the links in the Users section (see, for example https://nolana.docs.folio.org/docs/users/#permissions, try clicking on the  Platform Essentials > Permissions link, it stays in Nolana release notes).
  • Preferred example: "[Settings > Circulation > Title level requests.](../../../settings/settings_circulation/settings_circulation/#settings--circulation--title-level-requests)" will go to correct release documentation
• Katharina hopes we can use this to determine consistent link policy

Brandon (Home/About; Getting Started part of; Platform Essentials part of):

• Addressing some issues in Getting Started, working on completing Platform Essentials

Ingolf (Getting Started part of):

• Documentation for installing the release. May be waiting for release, to do it. Martina will check

Laurence (Platform Essentials part of; RA):

• Not too much to do for Quesnelia, so in good shape.

Christine (Users; Lists; Bulk edit (users); Consortium Manager together with Lucy):

• Not many updates for Bulk Edit and Lists
• Needs to work on Users with Laurence
• Will be done on time

Molly (RM; Export manager):

• On track for 22 April.

Emma (ERM; Dashboard (ERM)):

• No update (absent from meeting)

Annika/colleague (eUsage ERM):

• No update (absent from meeting)

Lisa: MM:

• On track for 22 April

Amanda (Bulk edit items, holdings):

• On track for 22 April

Eliana and others (Reporting):

• No updates in Quesnelia, so working on minor edits

6th meeting as convenor - Please give a short feedback to Katharina - e.g. satisfied with 

• Slack Channel communication
• Agenda preparation
• co-convener opinions

• anything to improve?
• Feedback
  • Christina said Katharina is doing a fantastic job keeping everything organized and if Katharina thinks she needs a co-convener, she supports that
  • Amanda agreed with Christine

Quesnelia public release is planned for Apr 29

Quesnelia documentation deadline as ever 1 week before: Apr 22 is the aim

Ramsons public release is planned for Nov 18

Ramsons documentation deadline as ever 1 week before: Nov 11 is the aim