Versions Compared

Old Version 18

changes.mady.by.user Jesse Lambertson

Saved on

compared with

New Version 19

changes.mady.by.user Jesse Lambertson

Saved on

Key

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

Date

...

PC updateYFormer user (Deleted)

Agenda/Notes

  • Will need to identity how the MM SIG can help Charlotte
  • will hope to catch bugs earlier, before bugfest, and this is cheaper to fix
  • the whole bugfest race will start again, right after the previous bugfest race
    • so, trying to balance out that rate of bugtesting between bugfests
    • expecting more testcases and more specific and granular testcases then for bugfest would result
    • This new bugtesting process will get more people into the weeds in FOLIO
  • Wondered if a specific person would take on a role for a timeframe to help this bugtesting process (not casual, very important)
  • from chat (

    We did the writeup of testcases early in the beginning of the ERM project. It was a good way to get familiar with the app and find strange behavior)

  • Core functional team capacity
    • diminished starting soon
    • FOLIO needs more developers
    • they do dev for Inventory and many other apps
    • for instance, results enhancements may get slowed
    • Are there ways to contribute needs, is there an easy way to contribute code back to FOLIO?
      • WolfCON topic?
      • it needs to be easier for local devs to contribute CODE to FOLIO (as opposed to just using the local code for local needs, but that could be helpful in a wider community)
      • comment: (the project should not have to rewrite the code all new if a local institution has made something that could be contributed back
      • Attempting to think about the issue of limits in programmer resources
      • There is a survey about this, but this issue just needs to be continually raised
      • some folks are making local things because they have come to expect that the FOLIO contribution plan and portal is not easy or clear
      • Comment: the code and community could be more robust if the local contributions could be added easily
      • But there is always a balance between local staff time for local work and larger FOLIO code contribution (which helps the whole project)
      • Even when institutions come together and make funds available, this process takes a LONG time
      • from chat (It is quicker to develop locally. )
      • folks are getting frustrated
        • we need a faster turn around
    • cofunctional
      • working on different scenarios
Other updates, announcements
  • QuickMARC subgroup has met twice
    • authorities and biblios are under conversation have been talked about
    • holdings are next on the larger agenda
  • data-import updates?
    • maybe update from Ann-Marie later
DocumentationJesse LambertsonWould something like this page: Circulation Documentation - Needs be useful for MM? If so, how to organize? By workflow? By app? Other?

Mode of Issuance, Other Reference Data:

deviating from defaults (such as note types, identifier types, alternative title types)

Laura E Daniels

Christie Thomas

Conversation continued from last week's meeting

In case it helps, the definition of reference data is: Data that are referred to by other records in the system (see: https://wiki.folio.org/x/XwEuAg and https://wiki.folio.org/x/jjcuAg for more information)

Documentation of current implementation

To Do Today:

Document specific examples for developers: e.g., how we would like to be able to customize reference data (adding, deleting, changing)

Google doc for working draft (Laura will turn this into a wiki page if appropriate)

...