Madga has asked for examples of bad Inventory / MARC data. Please get in touch with her, if you can share examples.
Discovery group meeting with Khalilah every other week about API requirements. This week looked at this document: Brainstorm page for the availability interface Next meeting will be on the 15th. In particular, some discussion about how inventory holdings and items are displayed may be of interest to MM members.
ARLEF ( Academic Research Library Exchange on FOLIO) held a discussion on problems academic institutions are having with data import. It will be an ongoing topic for that group. Today is a data import lab and I expect there will be some discussion about this there. Meeting Agenda,Background DocandSlidesare all available now.
From last week's PC- discussion around Prokopovich development work and bugs- Khalilah was tasked to reassigning features and she is looking at other models for onboarding some new POs. Also she met with the National Library of Australia to find out more about the development resources they are willing to provide to the project.
Community Council report was that elections subgroup underway, cleaned up the documentation copyright statement changed to create commons license, and resourcing subgroup is still working hard on community resourcing
Today: Aleksey Petrenko announced that the Orchid bugfest will start on Monday and 66% of the test cases have not been claimed yet. He gave a presentation on his release notes for Nolana (what I saw in his QUICK presentation less bugs and he has a video on bulk edit) and he will post that work sometime soon. It will be posted here on the wiki: Morning Glory. Aleksey was asking the PC for someone to help him produce these release notes complete with videos on the features included in the release. The PC will try to find someone to help Aleksey and it is an opportunity for the community to align with releases and roadmap.
PC started brainstorming about WolfCon in Chicago in August- ideas to have governance and other working groups meet at different times around presentations and sharing sessions. Have sharing sessions on cross app functionality, ERM and meetings with developers. Ideas to have preparation videos and "homework" before the meeting to get the most out of meeting F2F.
Christine is working on MARC and call number browse in Inventory
UXPROD-3569 - call number browse by type
Options to browse by call numbers should not focus only on North American schemes. Should include global call number types
There is a bit confusion around the call number type "Title" and "Shelved separately", but we will look into this at a later point.einrücken
If type does not exist, what should happen?
default to "other scheme"? → no!
add a value "not specified" to the list of types?
there is already a value "no information provided", which is different from actually not having any value assigned to the property which leads to not having a call number type element in the data
set to "none"? Should "none" then be an option in the list or just an internal property used in the browse backend?
No decision, but we'd like to distinguish between "no value set" and "other scheme"
Should we add more types to that list? If not, what should we do for browse with values added by the libraries by themself? Should these custom types be treated as "other scheme"?
This is based on the fact that you need to build in normalization for each option
If we delete existing values from the list, it would be problematic for libraries that already use those values as call number type
The group is in favor of option 1: include the call number types in the index selection
There was a question around: should the call number type be mandatory? At the moment, it's an optional element. → No, there are reasons for not having a type, if a call number is set.
Present plans on holdings source ID and item source ID
Goal is to support flexibility around other existing metadata workflows different from the typical FOLIO-MARC workflow solution
Changing the source field on the instance level from being a string field to a UUID field does not include any logic around locking down or blocking fields in the instance record from editing.
Please reach out to Charlotte and Felix if you have questions or concerns around this proposal
In the Folio wiki > Tips and tricks page for Data Import there is documentation on changing the default MARC mappings as well as documentation about the default mapping that is included in a fresh Folio installation: MARC Mappings Information
The numeric subfields are often not mapped, because they include source information
Changes to the GitHub code do not change the local defaults in a FOLIO tenant
Changes are published in the FOLIO release notes
If you want to have those changes applied to your local mappings, you have to get in contact with your service provider and ask them to adjust the JSON. Changes could also include bug fixes