Date
...
| Item | Who | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Product Council Update | The Product Council meeting discussion centered largely around logistics for the Product Council business meeting that will be held at WolfCon. They also talked about the Special Collections/Archives working group. This may result in a future FOLIO Forum. They are not yet ready to form a SIG. A convener is still needed for the Privacy SIG. Please let Dracine know if you or anyone you know is interested in this role. | |||||||||
| Announcements | Laura Wright - UC Boulder will be MM-SIG co-convener MM-SIG "general get-together" at WOLFcon: https://docs.google.com/document/d/1PfAfzrJNEIsFhg3G_W022VV0zMx58vbe7uw27gcacrM/edit - Charlotte suggested looking at the Instance/Holdings/Item UX with Kimmie. Lynn asked that we put our names next to the time we are available on the attached doc. There is some space that has opened up. If you will be at WOLFcon, please put your name on the document. WolfCon Draft agenda here: https://docs.google.com/spreadsheets/d/1jmjRAKBXJN2i1qPLOjdbeqi5xndTPyKzrDKuB8MeeBQ/edit#gid=958073271 No Zoom MM-SIG meeting next Thursday Charlotte asked that the document list all working groups and attendees. Laura asked that everyone please contribute package use case to this doc: | |||||||||
| Group & Subgroup Updates | Charlotte - Analytics and Bound-withs working group, the next meeting will be at WolfCon where they will present the consensus they have developed. | |||||||||
| Inventory UX follow-up | Patron information display discussion with Emma B. (Product Owner for Loan); also discussion about item notes - use for descriptive metadata; use for circulation. Also talk about having the Item record metadata element Number of Pieces separated in two fields (Number of Pieces + Description of Pieces) Per Charlotte:
___________ Patron Information in Item Record Emma - What is the specific concern about borrower information? Is it the number, the name, or both that is the problem? Jacquie - Expressed concern that any access to borrower information is not desirable, whether it is via barcode or name. Ann-Marie - Can this be controlled by permissions? Emma - If the barcode was visible, but patron info could not be accessed, would that be acceptable? Could the permissions be controlled in the user's app? Dennis - Wondered if unique id is a FOLIO id or an institution id. Showing an institution id fully could have negative implications. Lynn - In cases when checkouts are to "users" that are really workflow targets, such as the bindery, it is useful to have the barcode. Laura - Can we leave borrower out of Inventory entirely? Jessica - It would be helpful to have a link that a user with permissions could use to easily jump from inventory to circ apps. Christie - Wondered if the item barcode could be the active/inactive link to circulation. Felix - Also, the FOLIO item id could be used. Emma - Concluded that it is OK to have a link to that information. It cannot be displayed on the screen. And permissions will determine whether or not link to circ will be active. Another suggestion made was to display part of the patron's id. Circulation Checkin Notes, Checkout Notes Emma - One idea is to make available a box for item notes that will trigger a circ notification/popup if checked. Lynn - Should notes by default display to the public or not? Jacquie - Suggested the institution be the one to decide, not the system. It should be configurable by the institution. Lynn - When we talked about types of notes, what did we say we needed to accomplish? Laura - Did we talk about MARC notes? For example - they use a 583 note. They put them in bib and item records. The preference is in item record. Jacquie - By "public" in FOLIO - we're do not necessarily need to think about the public, only the FOLIO users. Charlotte - It would be useful to get an overview of what user notes are being thought about. She suggested starting a document with notes and the type of notes. Dennis - There may be confusion between MARC "action notes" such as the 583 field and notes that FOLIO needs to interact with. When we think about MARC notes, these may be things our discovery layer, or MarcCat need to interact with, but not the circulation. Lynn - We artificially store notes in the MARC record, that must stay there, but are more appropriate in the item record. Lisa (chat) - "Sorry if I'm not getting it right: could we input our own qualifiers, and then the developers only have to leave us a spot. But ... then it sounds like tags doesn't it..." We can discuss this after Wolfcon. Emma would like to know what the MM SIG is thinking about notes as we continue the discussion. | |||||||||
| Inventory<>MARCCat intersections & dataflows | Charlotte, Ann-Marie, and Tiziana prepared a paper that will be discussed at WOLFcon. The session will be held on Tuesday 5/8 at 2:00 - 3:30 pm and called: "How MARC cataloging app and inventory fit together" https://docs.google.com/document/d/1b_DVh1CGaUQmFu6kMp4R44WUKMpMQ8fP5RVhaEv4eFk/edit In this paper, Charlotte, Ann-Marie, and Tiziana, in a series of discussions present how they see MarcCat and FOLIO's inventory interacting. This document has been presented to a larger group that included Sebastian. Charlotte - Please read document thoroughly before WolfCon to be prepared for the discussion there. A MarcCat module will be implemented by the end of the year. It will be part of v.1. Authority control will be part of v.1 also. Discussions about how to make sure the data in in sync between the systems have taken place. A new development, is a discussion about a "box of tools app". This will be the part that makes sure the data is in sync, and also convert MARC data into the inventory storage. Refer to the diagram in the google doc. A v.2 diagram was displayed. The authority app will then be pulled out to be an app unto itself and then be accessible to the inventory app, as well as a projected Dublin Core app, Bibframe app. MarcCat will be the proof of concept for how to hook an cataloging app into the inventory app. Lynn - What is the "deadline" for the architecture? Ann-Marie - The functionality of the batch loader must be sketched out almost completely by June. | |||||||||
| Terminology for the Codex Search | Charlotte Whitt | Terminology for the Codex Search - the conducted usability test shown some confusion re. the terms: Codex, Local, Holdings Status. But this might be more a question about we're missing the build in help text - see Jira UISE-5 (
There has been a user test. People had difficulty understand what a "codex" was. The name itself was difficult for the users to understand. "Local" (local inventory) and Holdings Status, also proved difficult. Lynn will try to have a discussion post-WolfCon about this. |