Page Comparison

• Election for Community Council is underway. March 12 is the deadline. Dracine is a candidate!
• Shanghai is going to contributing some backend developers
• Dennis Bridges, PO for acq, walked group through user acceptance for FYRO
• Update from Jesse who is leading the roadmap taskforce.  The taskforce will work next with the capacity planning team to help finalize deadline. Members of the taskforce
• Virtual WolfCon - June 1 to June 3 this year. May be a more "outward facing" meeting. Possibly some presentation from in production libraries. Desire expressed to have other OLF projects to have sessions. 
• Planning also for WolfCon 2022!
• Laura: Virtual working meetings at WolfCon? Reach out to Laura. A special topic meeting, or working meeting with a particular focus. 

Homework for next week

Modes of issuance agreement needed in light of RDA's direction/update. Laura will create a document where we can outline with different options for vocabulary for modes of issuance. 

Christie - If anyone is interested in deviating from FOLIO default mode of issuance recommends not doing it - Chicago discovered that so much of the current mode of issuance have been baked into the current FOLIO so deviating will break functionality. 
Two issues: 1) Within settings app any vocab tied to that vocab cannot be changed. 2) MARC to Instance mapping is also a problem. Mode of issuance is tied to MARC to Instance map. However, that is configurable by editing the JSON file. However, the mapping calls a function that is embedded in the code. You can create local concepts for mode of issuance. Any source MARC will not be mappable - can't be displayed

• Jacquie - Does this mean we can even talk about changing the terms? 
• Laura - Important to define what we DO what the reference mode of issuance data should be.
• Jacquie - Maybe the Entities Management app is the place to do this - allowing users to change labels. 

Configuration of MARC to Instance mapping - Jessica (via chat) "So how does the source MARC get mapped the Instance?" - Christie - we need to change the approach to make it configurable. 

Jessica (via chat) - "I saw some of the slacking about reference data and it seems like it is a real problem."

Christie (via chat) - "In summary, at Chicago we are going with the defaults now because we have not figured out how to customize and have everything work. I think we called it sample data and not default data."

Jacquie (via chat) - "I agree, Jessica. And +1 Christie!"

Jacquie - We thought this was configurable. How do we convey that this should be configurable so this does not happen again? 

Jenn (via chat) - "so part of what we hand to devs should be the request that it be really customizable and make clear what that means"

Goal is to have clarity for developers on what we are asking for.

Let's collectively dive in to the Information and User Guides pages and add comments, add text, ask questions, etc.

Also, let's do some clean-up on the MM wiki pages – maybe we can make a page similar to this one (App Interaction) for recent meetings?

We are responsible for Data Export, Data Import, quickMARC

Note: there are two efforts for documentation underway - One for docs.folio.org and the other for our "Tips and Tricks" page. 

Documentation Needed:

1. Data Import
   https://folio-org.atlassian.net/wiki/x/jYBW - Add to this, perhaps making each its own page:

• Field protections,
• Overwriting field protections
• Updating individual fields of MARC records
• MARC modification.

2. Glossary - Add terms

3. Searching documentation 

• Common query searches - Laura is thinking about it. Affirmations for this via chat

4. Single record import - will need its own page (Ann-Marie put a quick outline on page)