...
Product Council Update |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subgroup & other updates? |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Postman help | Magda Zacharska | Andy Rodgers, customer support manager in Postman, joined the FOLIO community. He is eager to help with API testing. He joined the Postman Slack channel. You can contact him there if you have any questions. Andy was a Systems Librarian for years. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Location facets | faceting only available at the lowest level of location – what would the ideal location facets look like? Example from Cornell's sandbox; This becomes more confusion with a consortium on a single instance. The hope is that a hierarchical searching will be allowed. There may be plans to do this. Suggestion that each level should have its own filter that could be turned on and off. Situation is very different for single institutions vs. consortia. Queries can be written to report out on different facets of the full location hierarchy. 1)What do we recommend concerning facets in Inventory 2) Can we do complex queries in Inventory to pull out specific items from certain locations 3) How do reports work. Naming locations and coding them carefully would make it easier to query by location. 5 colleges are looking at their locations with an eye towards FOLIO. Want to clean up their location names. Start by documenting use cases for facets and filters. Holdings and items only hold the string. Use cases from the Five Colleges will be gathered. Should we reach out to the Consortia SIG? FLO may be worth talking to. Could we use another facet between Library and Location? OLE uses one called "Collection". "Adding a new level won't help the situation if the lowest is the only one that displays or is the only one where the data cannot be duplicated. " Action: Gather use cases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Future meetings format & structure | Laura E Daniels | https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Inventory Documentation Edit-a-Thon | Will be happening March 27 12-4 pm Eastern Time: Inventory (Inventory tips and tricks page) For every app there are pages of documentation - some are placeholders. Action: Volunteers needed to collaborate on creating documentation for Inventory pages. It does not have to be in a perfect final form. You can start to record information. If you need a wiki logon let Laura know. She will help you get a log on. Ann-Marie suggested using this page as a model for a similar page for Inventory - Settings - Reference data >Individual Apps: Information, Tips, and Tricks | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Future MM meetings | Do we want to start formally splitting meetings between development and implementation discussions? Have a more organic structure? Something else entirely? What future topics would you like to discuss? https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit Please think about this over the next week. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Future meeting topics |
Statistical codes: type = "Action" – create list of recommended values Refine the result list - work planned for development Q3 2020
Filip Jakobsen suggests to use Message banner (a new component) to display if an instance record is marked as: Suppressed from discovery, Staff suppress, or Previous held, or holdings/item is marked Suppressed for discovery. This use is intended as a MVP solution: https://ux.folio.org/docs/guidelines/components/message-banner/ Post-MVP we aim for ux consitency with MARCcat.
Source format (FOLIO, MARC and more) and Source of truth (SRS, LIBRIS, K10Plus and more). 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)
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 Council Item statuses and the apps that affect them - https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit#gid=2006676577 Music / Maps / Media cataloging review of data elements in Inventory
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://issues.folio.org/browse/REP-234 https://wiki.folio.org/pages/viewpage.action?pageId=78336464 |
...