You might have read that there is a shift in the FOLIO implementation timeline. In light of this decision, the working group has an amended timeline.
BSLW Testing: Ongoing 2019-2020: Work on BSLW sample sets, deciphering reports, and collection codes
Open House for BSLW Reports: Mid-late February 2020: Provide an open house on deciphering BSLW reports and updates
Deduplication Profile: May 2020: Work on deduplication profile
Open House on Deduplication Profile: June 2020: Share deduplication profile with community
Refine Deduplication profile & retest: August 2020: Based on feedback from open house, make any modifications to profile
Full test with test FOLIO & test EDS: September – December 2020: Complete full test with refined/tested deduplication profile and community input
Please note that all dates are tentative and subject to change. For feedback, you can reach the working group on its Slack channel #5crmwg, via email, phone, or in person.
The FOLIO Implementation Team met with the leads of the Five College Libraries working groups and representatives from FCLC earlier this week. We discussed the current FOLIO software development plan released by the FOLIO Product Council at the end of September and what we perceived as gaps in software functionality. Based on the pace of the software development and the set of features that will be available in early 2020 the Five College FOLIO Implementation Team has decided to focus our efforts on Electronic Resources Management and Acquisitions. The new plan we are developing will propose implementing parts of Electronic Resource Management and Acquisitions in FOLIO during the summer of 2020.
The plan is to continue work on implementing the other modules with the goal of having all modules live by the summer of 2021. The FOLIO community will simultaneously continue to complete and add new features which we think are important for our implementation as a consortium.
We plan on presenting a detailed project plan that reflects these changes later this fall.
A message From FOLIO Product Manager Harry Kaplanian of EBSCO Information Services:
As of Monday, Chalmers University is up and running on FOLIO!
Thank you all in the FOLIO community for all your hard work and effort over the last 3 (or more) years to make FOLIO real. You have volunteered your knowledge and experience of libraries, workflows and defined the key problems that needed to be solved in order to make FOLIO viable. This first “go live” milestone is the result of all your hard work, and the entire community has participated in this achievement.
Chalmers University is actively fulfilling loans, requests, adding and updating users while maintaining physical inventory and maintaining e-resources with the following applications:
|FOLIO applications running at Chalmers
||FOLIO integrations to
|Check in, Check out & Requests
||EBSCO Holdings IQ
||Bibliotheca selfcheck machines
||The union catalog of Sweden
||EBSCO Discovery Service
In return, this has provided the community valuable feedback for FOLIO which will make FOLIO substantially better for the next round of early adopters in the following areas:
- Critical performance & reliability issues
- UI concerns and improvements
- Critical security defects
- General defects and feature “misses”
I would also like to specifically call out and thank:
- The FOLIO POs and UI designers who ensured that FOLIO features were prioritized, defined and ready for development and tested
- The hours of testing from staff librarians from the community libraries and at Chalmers
- Special thanks to Holly for her tireless efforts in helping organize priorities to get FOLIO into a usable state
I would also like to thank the community developers for helping to accelerate FOLIO feature development by:
- Being active participants in the community with quality code
- By adapting industry standard best practices
- For unblocking releases in a timely manner so that the release timeline was not impacted
- For being on call when needed to investigate and fix problems often going above and beyond in solving key performance, security and stability issues
I would also like to thank the PC for it’s hard work in providing oversight in community process, roadmap alignment and organization of SIG structures and governance to define the requirements critical for FOLIO and the community developers to build the features needed by the greater FOLIO community.
Everyone who worked on this project in big and small ways please take a moment and celebrate, you are a part of academic library automation history.
For a bit fun, Chalmers took some time this weekend and created this fun video https://chalmersuniversity.box.com/s/rhjyvoci0up40kxfcqgltccbm68wy4z2.
If I’ve missed anyone, please forward.
The 5C Record Merge Working Group is currently working on a match profile, which we sometimes refer to as a mapping. This match profile will include all the MARC fields in our bibliographic records that are part of the merge and notes on what to do on merge. In short, these notes will be the decisions that we make for each field. For example, for 590 field, do we map this to a 500 note and add a subfield 5 with the code for the owning institution? The merge profile will also add comments on the type of behavior we’d like to see on merge, whether certain fields need to be normalized, what to do with like or exact matches, etc.
One of our first steps towards this match profile is to look at our collection codes. Our decisions are not based solely on location. However, this first entry will help us see what collections and/or locations we have across the 5C and ask questions as to what should be included and excluded. This process is just fine tuning what we recommended in our Recommendations Document.
Alongside this work, the members of the group will be doing small tests with Backstage to tease out more questions and start forming a decision narrative for the merge profile. You can follow our tests from our Sample Tests with Backstage spreadsheet.
- 1:19 – Q3.1 and Q3.2 release discussion; important “Definition of Done” change
- Not many team changes – Anatolii switched from folijet to EPAM, Bohdan joined EPAM
- Q3.1 bugfix update done on time
- Q3.2 module release (Daisy) public by 2019-09-25
- Q4 (Elderflower) public by 2019-12-20
- Expanded Definition of Done to include proper documentation of APIs, use pull request guidelines
- 10:43 – Acquisitions
- Thunderjet (Acq): Dennis Bridges, Aliaksei Chumakou, Andrei Shumski, Mikita Siadykh
- Password management 12:43
- Linking orders to invoices 16:44
- Assigning acquisitions units to orders 19:18
- Templates 26:08
- 31:37 – eHoldings app and tags
- Spitfire: Maksym Dryha
- Filtering note types 31:37
- Searching by tags 33:21
- Adding/deleting notes 34:45
- 40:11 – Data Import (Bib/Acq), File Upload
- Folijet: Ann-Marie Breaux, Sasha Yehorov, Taras Tkachenko
- field mapping profiles for Data Import app 40:11
- refined integration between SRS and Inventory: suppress-from-discovery option 43:39
- 48:43 – Patron notices, staff slips and other core features
- Vega: Maxim Didenko and Oleksandr Antonenko
- Users app password reset 48:43
- Circulation staff slips; checkout notes 50:26
- 52:59 – Anonymizing loans, circ rules and other core features
- Concorde: Viktor Soroka, Dmytro Popov
- improvements to locations display in Settings app; location code validation; new cancel/save button demoed in Users app 52:59
- saving patron group for anonymized loans 58:32
- 1:01:11 – Stripes, UX, Accessibility
- Stripes-force: Ryan Berger and Rasmus Wølk
- UI app template for developers 1:01:11
- overall UI improvements 1:08:00
- 1:10:25 – Resource access (loans, requests etc), inventory and other core features
- Core Functional: Zak Burke, Michal Kuklis, Magda Zacharska
- Inventory app: new lookup tables; improvements to search. Fix “add all permissions” button in Users app 1:10:25
- Requests app move request to another item; improvements to search/filter widget; improvements to UI connections to back end 1:15:33
- title-level requests 1:19:45
- 1:25:25 – FOLIO Platform, CI/CD
- Core Platform: Eric Valuk
- CQL array modifiers; CQL query across tables 1:25:25
- 1:28:40 – QA update
- QA Update: Anton Emelianov
– Sprint breakdown by Colin Van Alstine
The Five College Inventory Working Group is picking up steam. We started back at the beginning of June, with the task to review the MARC to Inventory instance record mappings. Our goal is to decide if the standard FOLIO mapping will work for what we want and need to see in our Inventory instance records.
Members have been reading through MARC mapping suggestions, searching for records in our Five College FOLIO instance and testing if we have what we think staff will need when using Inventory. Stay tuned! We’ll be reaching out to colleagues in each of the colleges to view and test sample Inventory records soon!
The Five College Record Merge Working Group submitted its Recommendations report to FIT and FCLC in June of this year. If you remember, the charge of this working group has multiple phases. The first was to create a recommendations document on how to merge bibliographic records in preparation for the migration to a single tenant FOLIO. The second phase is to act on those recommendations to deduplicate bibliographic records.
FCLC endorsed the decision to use Backstage Library Works (BSLW) as our vendor to help us deduplicate bibliographic records within the scope of the record merge. Because of the number of bibliographic records involved, approximately 5 million, FIT and FCLC have decided to forgo authority control loads until this can be handled by FOLIO. The entire file will be reset at that time.
The group has a number of items to address in these early stages to prepare for deduplicating bibliographic records. We will be working with BSLW on refining the contract, timeline of events, algorithm used for deduplication, and testing samples. The working group is also beginning to work on a testing procedure and mapping document.