Updates: | @Kristin Martin | @Michael Winkler is still pursuing the discussion about the role of ERM in FOLIO. @Kirstin Kemner-Heek is taking over @Maria Grzeschniok's spot on the RM SIG. A group from FOLIO visited the Library of Congress to talk about the project Visitors included Kristin Martin, Lynn Bailey, Sebastian Hammer, Peter Murray, Sharon Wiles-Young, Dean Krafft, Harry Kaplanian, and Christopher Spalding. Kristin led a session about Resource Management and Sebastian talked about the Codex. LC is very interested in licensing support, both for e-resources licenses and donor stipulations, as well as management of special collections materials They are also interested in products that will scale up to support their collection, which includes hundreds of millions of items It's possible we'll see some LC people looking in on SIG meetings in the near future.
|
E-holdings App https://folio.frontside.io/ | @Khalilah Gambrell E-Holdings App Group | Khalilah reviewed the charge and activities of the E-Holdings group Members include Bethany Greene, Kristen Wilson, Steve Brown, Peter McCracken The group's first meeting took place Oct. 11. It included intros, objectives, and a review of the current state of the dev build. Going forward the group will meet every two weeks. Completion date is now scheduled for late November due to delays related to OKAPI 2.0. The group's objectives include:
Khalilah also provided a demo of the current app The demo site can be found at http://folio.frontside.io/ Username/pw is admin/admin Current functionality includes searching for resources, viewing results and records, and selecting titles for the local colleciton
Questions and discussion What is the point of this app? The e-holdings app brings KB data directly into FOLIO and allows it to be viewed and edited in the FOLIO environment It also brings the data into FOLIO, allowing it to be used throughout the system The data is actually more important than the app, as the goal is to eventually integrate that data into apps throughout FOLIO By bringing KB data into FOLIO, we hope to provide a centralized point of management Many of the integrations and workflows that will use this app are still TBD. Possible integrations include relationships with acquisitions data, licenses, usage data, admin and contract info, and bib records There will also be a tie in with the Codex. Oliver's simplified explanation is that the Codex is the the great leveler and normalizer across different data sources – it's a way to join things together
How will bib records intersect with KB data? The Codex may provide a way to map a KB or inventory item to a work level; bib records would also be associated with a work We know from experiences with OCLC that matching bib and KB data is very challenging To support this work, we will need to use automation, but be conservative so that bad matches are not made
Is there a danger in recreating the KB interfaces and functionality within FOLIO? Peter raised the concern that duplicating the effort of knowledge base work within FOLIO might not be the best use of resources Would it be better to focus on the data, and have people use the native KB for editing? This is an area that the e-holdings group will need to look into more deeply
Will the e-holdings app work with KB's other than EBSCO's KB? The goal is that it will The APIs are being built in a way that others should be able to use them as a starting point; they are also public There was some concern that nothing is happening now to ensure that the APIs will work for a variety of KBs or test functionality with non-EBSCO KBs This is another topic for the e-holdings group to think about
|