...
| Product Council Update | Discussion centered on the MVP document (Market Viable Product). This document was approved to move forward, guiding decision making over the following year. Harry Kaplanian previewed a presentation he is planning on giving at the stakeholders meeting in Cologne. The MVP may be given its own page on the FOLIO wiki. Product Council will not meet next week due to the stakeholders meeting. | |||||||||||
| Subgroup Updates and Other Updates | Renaming of notes (e.g., Instance notes, Holdings notes, Item notes) to distinguish from "Notes" app that will be integrated (rather than being a helper app). | |||||||||||
| Role of Inventory | https://docs.google.com/presentation/d/1xUNm06LnI_4DHUvKWk5wlMlMARdee3izM_oD4wumKLw/edit#slide=id.g5d85ead0a1_0_26 | |||||||||||
| Batch Editing in FOLIO – may be postponed | Use cases for batch editing needs within and across apps: 1) Identification & selection of records to be acted on 2) Definition of edits to be made (and implementing those changes) e.g., find/replace; delete field
| |||||||||||
Multiple Graphical Representations | STILL ON HOLD for future meeting (possibly with representative members from Tech Council) working document: https://docs.google.com/document/d/1e6zlt7Gsd50W1HsRWWM6aerClXYe1l7XACaInVuWcoE/edit Problems:
Functional requirement: Create an instance record and be able to have multiple graphical representations of the language, or be able to put a non-transliterated title that can be searched in other scripts. Note: Charlotte has added following feature description (UXPROD) in Jira:
Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well? | |||||||||||
| Future meeting topics | Source of truth (SRS). Review the FOLIO metadata flow based on test of the newly implementation of edit freeze of records in Inventory when having only SRS and Inventory installed. Is the freeze to happen between SRS and Inventory, or freeze of Inventory is only when there is a MARCcat equivalent of the Inventory record? Rename the Notes accordion in Instance, Holdings, Item and Container record to be renamed, in order to distinguish between the new Notes app (https://docs.google.com/presentation/d/1BMitl09O4C_cg2cN34T5ofZ88Xg3ub3RysDfS6Vue20/edit#slide=id.p) and the notes we have in the metadata records. Inventory Permissions (
Search enhancements - possible also look at more general requirements for defining search, e.g. when to use: Phrase search, Truncating (left and/or right), Stemming, Nested search, Boolean search, etc. (TC and MM task) Authority Data and Inventory Vision (small group work first) Discovery Item record statuses and the apps that affect them Music / Maps / Media cataloging review of data elements in Inventory Felix (via chat) "@charlotte: I could ask a colleague (from one of the 180 network libraries) if she/he could review the beta elements from a 'musical' point of view." Texas A&M may have a music cataloger that can help. Christie offered to load cartographic and music data from other libraries into their test FOLIO instance. Jennifer (via chat): We should also look at video as well. Videos have other standard numbers EAN for instance and fields that people like to search and discovery them by https://wiki.folio.org/pages/viewpage.action?pageId=78336464 |
...