...
| Product Council Update |
| |
| Subgroup Updates and Other Updates |
| |
| Feature ranking/new features? | Laura thanked Christie for chairing thee meetings while she (Laura) was away. | |
| Open Inventory Features Prioritization | Proposed prioritization for post cap-mvp development. We sorted by first the number of P1 votes and then the number of P2 (see "sorted by P1, P2 tab): https://docs.google.com/spreadsheets/d/1c2EygYIdOCcKIiKSJpRF8stmWy7JAl3m/edit#gid=1595596086 The top 10 features seem clear here. Are there any that are not in the top 5 or 10 that need to be reconsidered? (for instance, critical to one or two institutions) Laura asked that everyone take a look at the doc and make sure it meets your institutions' needs. Reach out to Laura with concerns. Jackie from Duke asked if UXPROD-1714 - This is related to UXPROD-140 which we are going to work on. UXPROD-1714 will be added to the spreadsheet. | |
| Single Record Import | Clarification about importing bib records directly from OCLC into FOLIO SRS. Laura believes it would make sense to pull data directly into Source Record Storage from OCLC, just like we want batch import to behave. Proposal by Tiziana for MARCCat behavior: Note: Once a bib gets to SRS it will automatically create an Instance. Holdings: If the library chooses to have MARC Holdings, there will be three different storages for holdings. The flow will still probably be as shown above, plus updated in the Inventory app. Some libraries will not use MARC Holdings. In these cases holdings data will go only to Inventory Holdings storage. SRS holdings is only MARC. Christie asked about the "Rules" area in this diagram. Are we expecting that there will be one profile for OCLC to FOLIO? At Chicago they have many profiles and scenarios for data going from OCLC into their system. Are we expecting to have this type of flexibility? Can we leverage work from data import to work for this too? Laura said in Sierra there was a single default profile. You could also you could import data into OCLC that invoked a different profile. Christie said in OLE Chicago built a simplified UI on top of data import. In OLE, they select a file and a profile for their single bib import. Jacquie said at Duke they use multiple holdings codes put in the 049 that generates a holdings record. Ann-Marie is not sure what is envisioned for the "rule" box pictured above. Christie wondered if this could go through the API. | |
| 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. Inventory, MARCcat, Data Import Permissions interaction review 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 – need to clarify sources of data for discovery vs. data needed for operations; this needs to be documented for the entire FOLIO community and direction should come from Product Counil 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 |
...