00:06:18 Jennifer Eustis: We can check it off our list 00:06:24 Thomas Trutt: Reacted to "We can check it off ..." with πŸ˜‚ 00:09:04 Thomas Trutt: Id be happy to help again next year 00:09:32 Jennifer Eustis: Reacted to "Id be happy to help ..." with πŸ’― 00:14:23 Thomas Trutt: I use AI to inject the chat into the transcript. 00:24:59 Kristin Martin: https://folio-org.atlassian.net/wiki/spaces/PC/pages/4884965/FOLIO+Prioritization+and+Roadmap+Working+Group 00:29:12 Jennifer Eustis: https://folio-org.atlassian.net/wiki/spaces/PC/pages/931070022/Community+Priorities+Dashboard 00:29:20 Huff, Jeremy T: Reacted to "https://folio-org.at..." with πŸ™ 00:38:21 Thomas Trutt: User lever setting is being introduced in T.. Or I should say a module to save the settings to is being added. 00:38:31 Alexis Manheim: Reacted to "User lever setting i..." with πŸŽ‰ 00:38:35 Martin Scholz: Reacted to "User lever setting i..." with πŸŽ‰ 00:38:40 Thomas Trutt: RA would be the next biggest Sig that would be interested.. 00:38:44 Autumn Faulkner (she/her): same at MSU 00:38:51 Huff, Jeremy T: Reacted to "same at MSU" with πŸ‘ 00:39:30 Felix Hemme: Reacted to "RA would be the next..." with πŸ‘ 00:42:24 Thomas Trutt: Agreed.. 00:43:07 Christie Thomas (she/her): I think there needs to be a distinction between being format agnostic (and not MARC centric) and supporting the standards that are being most used in the system at a given point in time. 00:43:25 Christie Thomas (she/her): Right now MARC is the prevalent metadata format being used in FOLIO. 00:43:48 Thomas Trutt: Possible yes. It may be the way its implemented… Ie the storage module sends index data to a central index, and like settings the search function is extended dynamically by that sub-module. 00:43:52 Jennifer Eustis: Another way of seeing it is being able to access your data in a way that allows you do the work you need to do. 00:43:57 Charlotte Whitt: It’s not really a TC question :-) 00:44:28 Lucy Harrison: I like that. Focus on having access to all data rather than a specific type 00:44:57 Thomas Trutt: β€”old saying.. Anything possible with enough time and money.. :) 00:45:04 Huff, Jeremy T: Reacted to "β€”old saying.. Anythi..." with πŸ’― 00:45:10 Huff, Jeremy T: Reacted to "I like that. Focus o..." with πŸ‘ 00:45:26 Charlotte Whitt: Reacted to "I like that. Focus o..." with πŸ‘ 00:45:43 Thomas Trutt: But is was my understanding is that FOLIO was not ment to be MARC centric β€” In its original design. 00:46:11 Christie Thomas (she/her): Just because the system supports searching MARC does not make it MARC centric. 00:46:12 Alexis Manheim: Reacted to "I think there needs ..." with πŸ‘ 00:46:30 Alexis Manheim: Reacted to "Another way of seein..." with πŸ‘ 00:46:33 Charlotte Whitt: Yes, the MM-SIG did write up a vision document. And Inventory was not to be MARC centric. 00:46:50 Felix Hemme: Reacted to "Just because the sys..." with πŸ‘ 00:47:01 Huff, Jeremy T: Reacted to "Yes, the MM-SIG did ..." with πŸ‘ 00:47:05 Felix Hemme: Reacted to "Just because the sys..." with πŸ’― 00:47:13 Thomas Trutt: Would this be solvable by custom fields at the instance level and data mappings? β€” it may drop the need for the multiple indexing schemes based on source. 00:47:17 Alexis Manheim: Reacted to "Just because the sys..." with πŸ’― 00:47:17 Felix Hemme: Reacted to "I like that. Focus o..." with πŸ‘ 00:48:13 Christie Thomas (she/her): Replying to "Would this be solvab..." I would refer back to Felix’s comment that creating a more bloated Instance record is not the solution either. That creates different development and sustainability problems. 00:48:48 Tod Olson: This conversation suggests to me that the granular searching of specific record types may belong in or close to the storage for the different records types, rather than at the higher-level interface. 00:49:03 Martin Scholz: Reacted to "This conversation su..." with βž• 00:49:09 Thomas Trutt: Replying to "Would this be solvab..." In part.. I took his comment as adding more static fields to the instance level.. If they where custom fields added at the tenant level would it add the same complexity? 00:49:30 Thomas Trutt: Reacted to "This conversation su..." with βž• 00:50:03 Jennifer Eustis: This also ties into which records are used for discovery too 00:50:06 Tod Olson: Replying to "Would this be solvab..." Custom fields add their own complexity. It's all a bunch of trade-offs. 00:50:14 Christie Thomas (she/her): Replying to "Would this be solvab..." I think so. I would argue that this is data that does not necessarily belong in the Instance record anyway. For my own institution this is mostly historical data and is not being perpetuated forward. 00:50:59 Thomas Trutt: Replying to "This conversation su..." That is kind of what I was suggesting where the data stores would be in charge of creating and pushing indexed data to a central index and injecting search terms into the central search.. It would put the burden on the specific data stores instead of inventory. 00:52:43 Charlotte Whitt: Replying to "This conversation su..." Some libraries have the source records stored outside of FOLIO in the union catalogue 00:52:48 Thomas Trutt: This spaces issues has been a problem for Circ as well.. 00:53:19 Huff, Jeremy T: Replying to "This spaces issues h..." Certainly not the first time we’ve heard about this 00:53:29 Thomas Trutt: Reacted to "Certainly not the fi..." with πŸ’― 00:53:46 Thomas Trutt: Replying to "This spaces issues h..." The issue has been some institutions want the spaces in the data. 00:54:56 Huff, Jeremy T: Replying to "This spaces issues h..." Leading and trailing? 00:55:00 Tod Olson: I hope the issue of leading and trailing whitespace will be addressed at the backend API level rather than just in the UI. Padded data can come in from other sources, not just from cut-and-paste into the UI. 00:55:13 Lucy Harrison: Replying to "This spaces issues h..." Strip it out unless its in quotes or something? 00:55:20 Martin Scholz: Reacted to "I hope the issue of ..." with βž• 00:56:01 Thomas Trutt: Replying to "This spaces issues h..." Yes unfortunately. Its a result of bad data being inserted into FOLIO, or one case bad printed barcodes 00:56:12 Huff, Jeremy T: Reacted to "Yes unfortunately. I..." with 🫠 00:56:15 Thomas Trutt: Reacted to "I hope the issue of ..." with πŸ’― 00:56:51 Martin Scholz: https://folio-org.atlassian.net/jira/dashboards/10302 00:57:10 Kristin Martin: That dashboard is linked to on the Roadmap page too. 00:57:24 Felix Hemme: Cudos to Jennifer Eustis for creating this Dashboard! 00:57:53 Charlotte Whitt: Reacted to "I hope the issue of ..." with πŸ’― 00:58:05 Tod Olson: Reacted to "Cudos to Jennifer Eu..." with πŸ‘ 00:58:27 Charlotte Whitt: Reacted to "Cudos to Jennifer Eu..." with πŸ‘ 00:58:28 Lucy Harrison: I think it was very useful for Consortia SIG. Though we haven't presented to you yet. Maybe twice a year would be good? 00:58:31 Ros, Amanda L: Reacted to "Cudos to Jennifer Eu..." with πŸ‘ 00:58:55 Lucy Harrison: One thing: It's not clear to me what happens NEXT with these priorities. I know you've talked about it but I'm still not clear 01:01:07 Thomas Trutt: Reacted to "Cudos to Jennifer Eu..." with πŸ‘ 01:02:32 Alexis Manheim: Replying to "One thing: It's not..." Thanks for bringing this up @Lucy Harrison. We are going to talk about this at the Community Priorities group today.