2017-06-02 Meeting notes

Announcements:

• Come to FOLIO 101 at ALA
• Revised version of Project Plan available

There will be a FOLIO 101 at ALA, Monday 26^th 8:30 – 10 am Location: McCormick Place, W194b

Overview and update about FOLIO, informal gathering with a presentation.  Kristin Martin and Kristin Wilson will be there.  Link from ALA’s scheduler:  https://www.eventscribe.com/2017/ALA-Annual/fsPopup.asp?Mode=presInfo&PresentationID=288930

There is a revised version of the Project Plan available and goes over the development of v.1, timeline, when different areas will be dev., milestones for those areas.  Covers different features for each area for v.1.  

Metadata Use Cases

Mike Showalter created a draft use case that were based real world workflows.  Started from historical documents and looked at workflow and the results of test is to find out what areas in the codex lack information necessary to successfully move through the workflow.  With a typical firm order of a monograph, most areas of the codex carry information to successfully complete the transaction. 

However, a journal package workflow becomes more complicated because even at the base level of Journal package name, they can be non-standard depending on the vendor and the libraries who are purchasing them.  A vendor may name a package that could be very different than what titles a library has with the same package title. 

Discussion

Comment was made that the most important thing to get into the system is each title within the package.  How do you get a link into the record to display the title records?

Question was posed of will there be duplication within FOLIO and a library’s ERM, will libraries be using a separate ERM tool?  The goal for a lot of libraries is to not use a separate tool, to have the workflow within FOLIO.

Cate = Version 1 of FOLIO will support EBSCO KB of their ERM will be introduced into FOLIO, but unclear about how much functionality will be in there vs. a full ERM

Concerned was raised that we are straying from looking at print, electronic, etc workflows holistically and that is how the SIG has approached looking at FOLIO since 2016.   Sounds like we are not building ERM full functionality into FOLIO.   Are we building an ERM into FOLIO or the ability to connect to an outside ERM?

• Cate = The philosophy is to have blended functionality where FOLIO searches at the local catalog level but also connect via APIs to an outside ERM to sync up to the source records.

Question:  Will the codex be able to cover all types of records from the package name to the title list records, to administrative, etc?

• Cate = no, the examples I’ve been using are the instance level, not package

Question:   How do you tie the instances to a package?

• Cate = it will be through the external ERM.  What if any package record lives within FOLIO outside of external ERMs?

It was expressed that it is major stumbling block to have acq workflow separate from the ERM

Mike = The KB data and all the work that keeps it up to date should stand apart from FOLIO but the layering on of workflows and task doing should live in FOLIO.

Question:  How can FOLIO reference subscription start dates and perpetual access (item level).  Will there be the ability to put that into FOLIO?  Or moving target dates?  Need to be able to track what the rights are at point of acquisitions.  How do you capture that in FOLIO?  Data that is stored locally and references what is out in the KB and brings it all together for your customized view?

• Cate = FOLIO would pull data from the EBSCO KB and customization supported there, there’s no reason you couldn’t hang additional objects (in FOLIO such as PO#s or coverage metadata)

Question:  Is the ERM going to be built from scratch or EBSCO’s ERM ported into FOLIO?

• Cate = license/contacts would be built into folio V2, usage consolidation would be ported into FOLIO by API.  Other usage providers could build an app to use with FOLIO but not in V1.

KM = Still a concern feel a philosophical shift in how we’re preparing FOLIO and resource management.  We were going to try to do RM holistic integral part of FOLIO.  Don’t want to head down the path of segregating the ERM portion of the workflow.

Mike showalter = we’re relying on the data from third party KB whether it’s print or electronic but the functionality of licensing and contacts/admin should be built into FOLIO.

KW = I think what people want is to review and build a better version of licensing and holdings management.  Would an expanded data model that brings in aspects of an ERM licensing/contacts alleviate some of the concerns?

Cate = could better illustrate where some of the information is coming from (outside KB, within FOLIO, etc.) and visualize those workflows?

Ann-marie Breaux = Expanding the use case and acquiring a package and this is what FOLIO should capture and what we need it to do, showing where the info is coming from would be useful

Action Item

Cate = can try to put together with an example of an expanded data model, but I’d rather focus on particular use cases and work on the designs (wireframes) on how that would look

Cate will put together four use cases and design quick wireframes for the next meeting

1. Search for pack to see what’s in it
2. Search for an ebook to see what platforms
3. User request, see if we have a title, if not, how to order
4. Search for a record to change the metadata