Versions Compared

Old Version 14

changes.mady.by.user Sharon Wiles-Young

Saved on

compared with

New Version 15

changes.mady.by.user Christie Thomas

Saved on

Key

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

...

Notetaker


Announcements



PC update

Sharon Wiles-Young


  • Roadmap and Prioritization group is meeting on Wednesdays at 9:00 am ET- Jesse K. is the lead 
    • Start with reviewing the roadmap and review the prioritization process software tools
  • Onboarding subgroup shared their slides and will be open for comments for 2 weeks
    •  these slides will be used to get others involved once MOU is signed and have conversations with new members
    • LOC will be a test group for this presentation
  • Said goodbye to Holly M. and thanks for all her work on FOLIO; she is leaving us with a transition document- Cornelia and others are helping out for fees and fines for now 
  • Council updates:  
    • Community Council 
    • Sunsetting discuss platform
    • preparing for next Council elections Harry and council chairs- need qualified volunteers for CC
    • Funding- sufficient and meeting our ongoing expenses
    • Technical edit funding- Marcia covered for about 4 months 
    • Anton's job scope and filling this position-not finalized
    • Resourcing group still preparing final report
    • Changes in governance - how to handle ties in elections; memberships levels reviewed
    • Technical Council:
      • Mod Settings approved - need to review module process 
      • How to guide configuration settings- move to decentralized or centralized configuration
      • How Kafka is used with an eye to reduce hosting costs
    • PO
      • Need PO for fees and fines
      • Cornelia will be in charge of testing for Orchid
      • New PO Christine from Ebsco working on quickMarc on Spitfire
      • Orchid release dashboard and working on Poppy scope
  • Release planning group meeting: Need a definition for this group and Kristin and Jenn Colt were invited to this meeting and they want to clarify the role of this group; timeline for Poppy on the wiki
    • Scope timelines trying to be worked out and draft for scope 
    • Propokovych how to address with the team and resources going away TAMU cannot contribute their developers anymore to this team- TAMU will have a new development team in FOLIO
      • So what should the PC help with and how does the PO group, PC transition this and find development resources? WHO is going to take the responsibilities for these resource needs and changes in the project
      • Charlotte has been waiting since summer to be released and no PO found and still working in Nolana she needs to get out of this PO role

Jennifer Eustis 


MM SIG Release Note & Other Highlights

Data Import: Seeking examples of MARC records for any MARC Modifications actions for modifying the 001, LDR, and/or fixed fields in incoming MARC bibliographic records. MODDATAIMP-767 - Data Import MARC Modification Mapping for MARC Fixed Fields, LDR, 001 Open 


Review of the parking lot

Continued from last week


MM SIG Parking Lot (restructured)

The previous MM SIG Parking Lot (Old) has been renamed and moved under the new parking lot.

Discussion about whether the topics are still relevant and need to be added to a future agenda. Possibly create an archive for the topics that are retired from the list

Referential cataloging - term used early in the project - copy cataloging / pointing to external cataloging. We have already made a lot of decisions that have moved us away from this model of cataloging within FOLIO. Suggestion that we remove this from the list and if we do need to revisit it the SIG should redefine our needs based on the current cataloging ecosystem / roadmap within FOLIO. 


Preliminary item status work(OLD ACCOUNT) Erin Nettifee 

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3475

Questions about keeping Data import and Inventory behavior in sync - Item Record Statuses and Data Import 

  • In transit
  • On order
  • Order closed
  • Withdrawn

There is no identified release or identified resources for this. Defining issues in Jira provides a framework for identifying the resources and that is what is being done now. 

It is not possible to change an item status to Available from within Inventory. There are use cases for this. Changes are to the Inventory UI and would allow to change to Available when item record status is in the list. Two stories: one for Inventory behavior and one for permissions.

There is a question about whether this work may be more complicated given any dependencies on the underlying item statuses.

Given the focus on using check-in to make items available, should we consider leveraging the check-in api from within Inventory to check something in? 

Another question came up about the business logic associated with receiving - on order to in process. Will this impact any of that business logic? Breaking workflows is also the possibility for other statuses that have workflows associated with them. 

Another concern was raised about the prescriptive nature of this. If there are no system-wide ramifications then maybe we should implement in a way to allow institutions to determine their workflows rather than they system. There were also concerns that doing so would create problems with workflows in other institutions. This will be discussed more at the acquisitions sig, which is the next step for this JIRA. 














Chat: