Attendees

please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!

Discussion items

Item	Who	Notes
Product Council Update	Former user (Deleted)	Holly Mistlebauer updated the group on how she is compiling the results of the gap analysis report. Hkaplaniangave a brief presentation about documentation. He separated documentation types into three groups by user type: Endusers, Sysops staff, Developers. Harry's plan recommended hiring experts in this area to fill this need. Harry's slides: https://drive.google.com/open?id=1xfeP36_Q87kB1ULACpSjxxoDMVvtcFPm There was some discussion about inviting non-EBSCO vendors to collaborate and provide input.
Face to face meeting planning	Laura E Daniels	Meeting dates: June 17-19, Location/Hotel: DoubleTree by Hilton Hotel Washington DC - Crystal City, 300 Army Navy Drive, Arlington, VA 22202 Attendance fee: ~$100 ; Target number of attendees: ~120 Registration link: https://www.eventbrite.com/e/folio-meeting-june-2019-tickets-59544369813 Tentative agenda: https://docs.google.com/spreadsheets/d/1TwhNbJydkLNnd0ciLQpeJ1fIeQ2HIefMnH2tVAI9pVQ/edit?usp=sharing (This is being updated depending on who is registering.) ____________________________ If you will not be attending, but are interested in participating in a particular meeting, please let Laura know. (We have about 8 confirmed MM attendees, several "maybes" and at least 4 who will not be able to attend.) ______________________ Agenda Notes: Most of the MM meetings will be cross-app focused, other than a group that will work on the prioritization of Inventory. Laura submitted suggestions for topics including entity management and search enhancements. Charlotte suggested that when the final agenda is released, goals can be written up to help focus the face to face meeting discussion. If members cannot attend but would like to participate, let Laura know so she can set up a Zoom session.
Inventory UI review		Wanted: A few volunteers needed to spend about 1 hour with Charlotte reviewing the Inventory UI. A list of topics to be addressed will be provided by Charlotte for to up to 3 volunteers for feedback. Examples: Presentation of long call numbers in Inventory. Presentation of Primary contributor. Enumeration data display. Volunteers: Jennifer Eustis, Martina Schildt, Natascha Owens, and Laura Wright
Subgroup Updates and Other Updates		Ann-Marie Breaux (Deactivated) I'll miss today's meeting, but a quick update from Data Import. A couple people continue meeting with Filip to finalize the matching and action UI. UI developers are finishing the job profile settings and starting work on the match profile settings. Backend developers have added the SRS UUID to the MARC 999 field, and are almost finished adding the related Instance UUID. I still owe final writeup on the 001/003/035 HRID handling. MARCCat - MARCCat subgroup group gap analysis was completed and submitted.
Report on EAD-Inventory Mapping	Aaron Trehub Laura E Daniels Lisa Furubotten	Postponed until May 9: Proof of concept – a few additional proposed elements defined for Container records https://docs.google.com/document/d/17NL62V93O73uOTbHv6LMLf3WdTfcVrT1z-dmYooW-Y0/edit
Multiple Graphical Representations	Laura E Daniels, Jacquie Samples, Christie Thomas	(to be continued) working document: https://docs.google.com/document/d/1e6zlt7Gsd50W1HsRWWM6aerClXYe1l7XACaInVuWcoE/edit Problems: If multiple forms of the value are represented in a single JSON object, both scripts have to be included in a single value cell. This limits the search function. Chicago is testing graphical representation in FOLIO. Here is an example: See MARC record: https://catalog.lib.uchicago.edu/vufind/Record/8539712/Details#tabnav See JSON sample: (Christie will provide) Functional requirements need to be built so developers can understand the issues. What would we like to have happen in FOLIO? Proposed solution: Single JSON object for the property, e.g., Title, with the ability to have an array of values for display (labels). Values should allow for a property that identifies the script. This would allow for the ability to configure displays to include multiple representations or a selection of representations. 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: UXPROD-1646 - Getting issue details... STATUS 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		Reporting: in-app and data warehouse (planned for May 16) Inventory Permissions ( UXPROD-1371 - Getting issue details... STATUS ) 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
		Container Record? - Initial impetus was to provide another level of hierarchy to unite records together in some way. Different institutions could use it to solve different problems. It should be available to be used flexibly. The vision is that it will "live" in the Inventory app. https://docs.google.com/document/d/1DakHW6D5_09uKJPQzCSTwycP0gqkPs6E7k35_KpfCxg/edit Implications of Container and cross-app interactions will need to be discussed with Reporting -- -invite Reporting SIG members to the Package (Agreements) / Container (Inventory) interaction session at the F2F meeting

present?	Name	Organization
	Aaron Trehub	Auburn
	Alice Krim
	Ann-Marie Breaux	EBSCO
x	Ann Kardos	UMass Amherst
x	Charlotte Whitt	Index Data
x	Christie Thomas
	Colin Van Alstine	Smith (FC)
	Damian Biagi
	Dennis Bridges	Stacks
	Dennis Christman	Duke University
	Dracine Hodges	Duke University
	Felix Hemme	ZBW
	Filip Jakobsen
	Jacquie Samples	Duke University
	Jason Kovari
	Jenn Colt
	Jennifer Eustis	UMass Amherst
	Jessica Janecki	Duke University
	Kristen Wilson	Index Data
x	Laura Wright	U Colo Boulder
	Lisa Furubotten	Texas A&M
	Lisa McColl	Lehigh University
	Lisa Sjögren
	Lynn Whittenberger
	Martina Schildt	VZG
x	Mary Alexander	Univ. of Alabama
	Nancy Lorimer	Stanford
x	Natascha Owens
	Niels Erik Nielsen
	Patty Wanninger
x	Sara Colglazier	MHC/5C
0 (OpCo)	Sarah Ross	Cornell
	Sarah Schmidt	Duke University
	Tiziana Possemato
	Theodor Tolstoy
	Wayne Schneider	Index Data

Browser not supported