...
| Product Council Update | There was a presentation from the Capacity Planning Team regarding the MVP and the prioritization of features. The Council tentatively approved the recommendation from the Capacity Planning Team. Goal - identify what libraries will be able to implement based on the Capacity Planning Team's recommendations. By August 27, Project Council is looking for at least 5 libraries to commit to going live with FOLIO by the summer of 2020. The group can go to the Product Council's meeting minutes. | |||||||||||
| Subgroup Updates and Other Updates | Metadata Export Group: Magda reported: This new group will meet on Thursdays between 2:00 and 3:00 pm. Meetings will be recorded. The first meeting will be scheduled for August 29th. Christie and Laura joined the first part of today's RA meeting to speak with the group about bound-with materials. Laura will work on a mock-up. | |||||||||||
| Feature ranking/new features? | Note: Please post questions about these on Slack. Dracine said there is a chance new rankings of these features could influence MVP rankings if there are available resources. UXPROD-1922 Item. Easy copy of barcode and make barcode a link in item list UXPROD-1923 Settings > Inventory > Item: Implement material type category UXPROD-1924 Item. Copy should not be a repeatable element UXPROD-1889 Instance: Delete warning when deleting format or contributor type UXPROD-1890 Instance: Additional controlled vocabularies for Instance menus UXPROD-1891 Instance: Lookup by code (contributor type, resource type and format) UXPROD-1892 Instance: Add related instances data element UXPROD-1893 Instance: Implement preceding and succeeding titles UXPROD-1894 Settings > Inventory > Instance: Implement format category | |||||||||||
| PO-MVP/MVP and Capacity Planning update | Laura E Daniels | Inventory features - CWFeaturesByEpic Note that the "cap-mvp" is not the same as the "po-mvp". Felix: "Will the features marked cap-mvp be developed by summer 2020?" - Charlotte - "yes" Christie: Is the goal to have features ready for testing by January 2020, to give six months time for testing and training? Laura: "Early December 2020 is the goal for having a feature freeze" Work on Search and Sort query would probably be possible to implement after Q1, 2020. "Source Recor | ||||||||||
| Search in Inventory update, mock-up | Charlotte Whitt | Slide deck - Search in Inventory - UXPROD-140 (Misc. UX) – There is no UX to model the look of the advanced search feature in Inventory, yet. The "Orders" app has some developments we may wish to replicate. For example, there is the ability to have default open filter list, and default closed lists. Lookups within the Locations filter is possible. In "Date created" there are fields that enable a user to define a time period. In the Finance, Orders, and Agreements app they have what could serve as a model in Inventory for changing the search criteria from Instance, to Holdings, or Items. | ||||||||||
Multiple Graphical Representations | Laura, Christie, and Jacquie met with Tech Council Aug. 7 – still some work to be done around ideal display options and sample data 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. 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 – 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 |
and not completely done (time was running too fast)
...