2019-08-08 Metadata Management Meeting notes
Date
Attendees
please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!
Discussion items
Product Council Update | A coordinating committee is forming to work on the agenda and logistics for WolfCon 2020. This will include but not be limited to FOLIO working meetings. The Privacy SIG is being revivied Holly Mistlebauer gave an update on Capacity Planning: Capacity Planning / MVP update MVP recommendations from the Capacity Planning Team should be available next week. Harry Kaplanian has started drafting a "reverse RFP" document. He began with Acquistions and will be addressing Inventory next. This document is available in the PC google drive if anyone is interested in reviewing it. | |
Subgroup Updates and Other Updates | Container Small Group Update - Group has been working on some modelling. There are drawings available in Google Drive, if interested Data Export Subgroup - Laura thanked those who volunteered for the group. Data Import - Ann-Marie reviewed feedback on MARC to Instance mapping. She presented the changes to the developers. MARCCat - The next meeting should be help on Monday, August 12 | |
Feature ranking/new features? | Ann-Marie reported that At Cult is doing some cleanup in Jira. Some features may arise from that activity. Laura will try to make sure we are made aware of this. | |
Bound-with/In-analytics requirements review | - UXPROD-1856Getting issue details... STATUS - UXPROD-1241Getting issue details... STATUS Most institutions are ranking these go-live. Let's make sure we have a shared understanding of how this solution works and plan to get input from RA on display needs for circulation purposes. Natascha who was part of the original subgroup that dealt with bound-with/in-analytics requirements group, reported on their past activity. In her memory some in the group wanted to link items, some link instances. Natascha feels we need now to address the item to item relationship. She mentioned considering this in terms of circulation Felix (via chat) - "This is our small area in the Google Drive folder (data samples, drawings etc.): https://drive.google.com/drive/folders/1JKppoiWoeXe6C8G2T6W7lYMv2HA9Fyya" Laura wondered if the Jira for Instance to Instance (UXPROD-1856) relationship is independent of the Jira for Item to Item relationship (UXPROC-1241) . Felix stated that they do not depend on each other in any way. The RA group is interested in this discussion due to circulation concerns. Laura also mentioned there has been some confusion in some thinking that container records will fill this need - which is not the plan. Example of container model shown (link?) "Archival collection with container and instance option 1" There is a desire that a container that have one or more instances, and also that a container can have items that are not connected to instances, but relate to the container. Felix (via chat): "I totally agree with UChicago that we need more input from the US libraries re. item to item linking. At that time it turned out that each institution dealt with bound-withs differently and that it would be difficult to generate a uniform solution in a new system." Jason - the discussion of a container should be brought before a group of special collections/archival specialists. Michelle stressed that the value of a container could be to show through dynamic linked relationships between collections, parent/child or instance to instance - several levels. They are going to ask Rita (via chat) - "Is the function of a "container" to build any kind of hierarchy in metadata? (You could also think about linking an instance for the greater Ressource to instances for the components ... Will you use a container to describe a multipart monograph?" Laura answered "It depends. A container is a way to represent a hierarchy." Laura invited the group to add drawings to the FOLIO > Metadata_Management > Container folder Michelle (via chat, regarding the container example) - "This might very well be a case of a parent/child relationship between two different instances, with the same item [Box 3] linking to both via holdings (if that’s possible?), and thinking about it as a container could be complicating things" | |
Multiple Graphical Representations | Laura, Christie, and Jacquie met with Tech Council Aug. 7 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: - UXPROD-1646Getting 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 | 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 ( - UXPROD-1371Getting 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 – 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 |
present? | Name | Organization |
---|---|---|
Aaron Trehub | Auburn | |
Alice Krim | ||
Ann-Marie Breaux | EBSCO | |
Ann Kardos | UMass Amherst | |
Charlotte Whitt | Index Data | |
x | Christie Thomas | Chicago |
Colin Van Alstine | Smith (FC) | |
Damian Biagi | ||
Dennis Bridges | Stacks | |
Dennis Christman | Duke University | |
Dracine Hodges | Duke University | |
ZBW | ||
Filip Jakobsen | ||
Jacquie Samples | Duke University | |
Jason Kovari | Cornell | |
Jenn Colt | Cornell | |
Jennifer Eustis | UMass Amherst | |
Jessica Janecki | Duke University | |
Kristen Wilson | Index Data | |
x | Laura Wright | Cornell |
Lisa Furubotten | Texas A&M | |
x | Lisa McColl | Lehigh University |
Lisa Sjögren | Chalmers | |
Lynn Whittenberger | ||
Martina Schildt | VZG | |
x | Mary Alexander | Univ. of Alabama |
Nancy Lorimer | Stanford | |
x | Natascha Owens | Chicago |
Niels Erik Nielsen | ||
Patty Wanninger | EBSCO | |
x | Former user (Deleted) | HeBIS-Verbundzentrale |
Sara Colglazier | MHC/5C | |
Sarah Ross | Cornell | |
Sarah Schmidt | Duke University | |
Tiziana Possemato | ||
Theodor Tolstoy | EBSCO | |
Wayne Schneider | Index Data |