Page Comparison

Aaron Neslin

John Banionis

Peter Breternitz

Alissa Hafele

Kimberly Pamplin

Peter Sbrzesny

Dennis Bridges

Kimberly Wiljanen

Rhonda Fuhrmann

Dung-Lan Chen

Linh Chang

Sarah Kees

Dwayne Swigert

Lisa Smith

Susie Skowronek

Heiko Schorde

Lucinda Williams

Suzette Caneda

Jackie Magagnosc

Molly Driscoll

Sven Thomsen

Jean Pajerek

Sylvia Hamann

Joe Reimers

Timothy Nelson

Housekeeping

• Housekeeping -

  • Molly Driscoll covering notes

  • Reminder - Bugfest continues until Friday, Nov. 29th

  • Call for a volunteer to take on documentation for the Claiming app (Sunflower), see Slack: https://folio-project.slack.com/archives/C217N937A/p1732643097879859

  • Next meeting - Tuesday, Dec. 3rd, at 1 pm EST

Questions related to version history

Dennis Bridges

Dennis raised issues/questions related to version history

• Exists in Orders app, but now being implemented in other acquisitions apps

• There are some limitations, e.g. accordions whose changes cannot be currently tracked

  • Issue: it is currently possible to create a new address in Settings > Tenant > Addresses, while including a name but no address.

    • When changing to that address for an order’s bill to/ship to, this is listed as ‘record deleted’, rather than ‘no address listed’

    • Is there any use case for creating an address with name only and no address data?

      • Molly l said I can't think of a use case. I would imagine just not using that field...

      • Lisa said MSU would want something in the address field - even if "same as ship to"

      • Proposal to make that field in Settings app required

  • Issue: Vendor information on invoice records is sourced from Organization record

    • If accounting code does not exist on a vendor record, for example, what would a library want to display?

      • Options included on UIOR-1355

      • Dung-Lan proposed using “Field blank” if the field truly contains no data

      • Susie clarified this is only displaying in version history; indicated it would be confusing if on the record itself

  • UAT for Invoice version history and Organization version history is coming soon

    • For invoices, not all accordions show in initial release

      • Vendor details (address changes will not be shown in version history because this is pulled from the vendor record in real time)

      • Links & documents

      • Invoice line deletion not shown

      • Invoice line addition is not shown in invoice version history as such, but appears on invoice and has distinct version history, showing creation date/time/user information

      • Working through some technical limitations to include missing info in subsequent releases

    • Is invoice line version history still useful without showing deleted invoice lines?

      • Dung-Lan clarified that once an invoice is approved, invoice lines cannot be added/deleted

      • After approval, exchange rates, notes, etc. can still be edited

    • For organizations, in initial release, limitations around these record types that will need their own version history:

      • Contact people – can show addition/removal, but not edits to contact record

      • Interfaces

      • Integration details

      • Notes

      • Contact/interface changes to be separated from edit form and added to view form in a future release to improve UX