Versions Compared

Old Version 4

changes.mady.by.user Jana Freytag

Saved on

compared with

New Version Current

changes.mady.by.user Molly Driscoll

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Laurence Mini

@Patty Kishman

Mark Canney

Joanne Leary

mey

Darcy Branchini

@Robert Scheier

tpaige@umass.edu

Jana Freytag



Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia

Jana Freytag

  • Jana vaccationvacation: 8th, 12th, 15th April 2021
  • who wants to take over as convener for these three dates?
  • 5th is Easter Monday and a national Holiday in Germany we will cancel this date.

Documentation WG updates

(OLD ACCOUNT) Erin Nettifee

Work is continuing! Goal is to have a "complete" set of docs for apps in Iris.

Circulation Documentation - Needs

Some broad groups of documentation that I've identified for work include:

  • fees/fines and blocks
    • Has some existing documentation Settings - Users
    • Need to write some basic fee/fine docs:
      • Viewing a patron's fee/fine history
      • Waiving a fee/fine - full waive, partial waive
      • Refunding a fee/fine - full waive, partial waive
      • Accepting payment for a fee/fine - full/partial 
    • Need to write some basic docs on blocks
      • manual blocks
      • automated item blocks
      • automated patron blocks
    • Need to write more detailed documentation focused on learning the system

      • FOLIO's fee/fine model - actual cost vs. set cost - how does each approach work? What are the differences between them, and consideration for implementers?

      • How do overdue fines accrue?
      • How do lost item charges accrue?
  • Notices
    • has existing documentation from Fameflower as a base - Patron Notices
    • we need to add troubleshooting documentation and answer the questions we identified:
      • How do scheduled notices work when they run on day intervals
      • How do scheduled notices work when they run on hour or minute intervals
      • What triggers different kinds of notices – all of the different kinds of patron notices available
      • How do staff slips work? how do you format them?
      • Tips for troubleshooting patron notice delivery
      • Tips for troubleshooting staff slips
  • circulation rules & policies
    • Basic documentation already exists -  https://github.com/folio-org/mod-circulation/blob/master/doc/circulationrules.md
    • what happens when circulation rules change after an item has been checked out? what happens when item information changes after an item has been checked out? what happens when patron information changes after an item has been checked out?
    • Things to consider when deciding how to write circulation rules
      • How the fallback policy works
      • How prioritization works
      • Special characters and indentations
      • Sample circulation rule sets from adopters

I'm glad to work on each of these areas and help shepherd it through, but really need to have help writing these. This is a great opportunity to force yourself to learn how this stuff works, too.







...

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue




























Notes

Onboarding document –

  • Please feel free to take a look and comment on it; it is linked in the agenda
  • Jana will provide it to new members, but encourages new members to continue engaging and asking questions

Bugfest –

  • There are still ~300 unclaimed test cases; quite a few in RA areas (notices, fees/fines)
  • Erin gave an overview of what Bugfest is and how it works
  • There are 30% more tests for this Bugfest than last, which is contributing to the higher level of unclaimed tests.
  • There is a Slack channel that people can be added to; need to be signed up for Testrails
  • Bugfest will happen for every release and new community participants are encouraged to hop in as it is a great learning opportunity.
  • Cheryl pointed out that this is not just testing new features but also regression testing for existing features.
  • Bugfest environment allows testing at larger scale than Snapshots (more patrons, greater collection size in Inventory)
  • Some of the new functionality will not be available until Monday (Bugfest is 2 weeks for the first time)
  • Jana would like to have a recap meeting after Bugfest to discuss experiences and findings.

Jana on Vacation –

  • Jana is on vacation until 4/19
    • Monday, 4/5 is cancelled
  • Sharon Wiles-Young will convene for 4/8, 4/12, 4/15
    • Please send topics to Sharon

PC Update, Sharon Wiles-Young

  • Time of transition with newly elected Community Council.
  • Jesse K. and Sharon are acting in an interim capacity until new PC is elected in May.
  • Roadmap Proposal was approved; will discuss next steps next week for the interim basis.
  • New pointing system to begin 4/12 for Kiwi prioritization.
  • MM SIG new PC liaison is Philip Schreur, Stanford
  • Consortia SIG new PC liaison is Paul Moeller, University of Colorado, Boulder

Documentation Update, Erin Nettifee

  • Extensive updates in the agenda.
  • Erin is excited for the Inventory documentation (Jesse leading this effort) and User Management (Christine leading this effort).
  • Glossary being developed to act as central repository for platform-wide definitions: https://docs.google.com/document/d/1c2NkqJ0amsorBBWB8MuvSqXaQSIwqhL4t3i2zxEFR5I/edit
  • RA Season of Docs intern already did a significant amount of documentation reviewed by SMEs, but we do have a fair amount of additional documentation to build out.
  • Erin has been organizing outstanding documentation needs into distinct categories
    • Fees, fines, blocks
      • Cornell could contribute here
    • Notices
    • Circulation rules and policies
      • Cheryl has some documentation but would be helpful to see adopter rules.
      • Cornell is beginning to build their circulation rules and would be happy to document the process.
      • Molly volunteered for this group.
    • Would like to form groups which may include the PO but does not shoulder the POs with the responsibility of writing the documentation.
      • 3-4 people for each topic
      • Brooks is happy to be available but cannot commit to any writing responsibility right now.
      • Erin will post to the RA Slack channel to gather other participants.
      • This effort is essential to implementers so the effort now will translate to efficiency later.
      • Most of the efforts will be done via Google doc collaboration; avoiding supplemental meetings if not strictly necessary.