Chalmers University is up and running on FOLIO!

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
Users OpenAthens
Orders GOBI
Inventory Bibliotheca selfcheck machines
Orders The union catalog of Sweden
Organizations EBSCO Discovery Service
Agreements
Licenses
eholdings
SIP2

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.

Thank you!

Harry Kaplanian

 

Records Merge Working Group Invites you to 2 Open Discussions

The last records merge open discussion focused on special collections, analyzed sets, bound-with, and  electronic resources. A recording, summary, and images of notes can be found in the FIT Documents folder for the Record Merge Working Group. A word of warning about the recording – we broke out into groups which didn’t translate to the recording. The beginning and end was captured. If you were unable to attend or have more you’d like to contribute, post your comments to this form which is anonymous and only for internal use.

We are in the process of scheduling two additional open discussions. Save the date for these upcoming events:

  • April 30, 2019, 1:00 pm – 2:00 pm, The Annex: Open Discussion on (Not) Merging Suppressed Records
  • May 10, 2019, 9:30 am – 11:00 am, Mt. Holyoke: Open Discussion on Merging and What steps should be taken to prepare to Merge (or Not) on: Special Collections, Analyzed/Bound-withs/Cat Seps/etc., a third topic to be announced

We encourage everyone to continue the discussions on merging and how to prepare for the merge with their colleagues. If you have a group and a topic for the May 10th discussion that isn’t special collections or the analyzed/etc, let us know via the form, by email (jeustis@umass.edu) or Slack #5crmwg.

Five Colleges Discovery Committee User Stories Survey – Accepting stories till the end of April 2019.

The Five College Discovery Committee is gathering discovery user stories till the end of April 2019 to inform decisions regarding improvements to EBSCO Discovery Service (EDS) and decisions regarding discovery systems in general in support of the move to FOLIO. Please take a few minutes to fill out our user story survey.

http://bit.ly/discoveryuserstory

Discovery is searching and finding books, journals, articles, or other items in the library catalog or research databases. A discovery interface can search all of these at one time (such as EDS) or individually (such as a catalog).

A user story is a tool typically used in software development in order to build a user centered framework for system requirements. The Discovery Committee is gathering user stories to help us identify the discovery needs of our community, improve our current discovery tools, and to develop future functionality in our discovery systems. User stories are short simple descriptions of a feature told from the perspective of a user. A user story includes the type of user, what they want and why and typically follows the format:

As a < type of user >, I want < to do an activity> so that < I can reach a goal>.

For example:

As a student, I want to find a book on reserve so that I can do my assigned reading.

You can help us and the Five Colleges FOLIO project by contributing your discovery user stories!

We are looking for two types of user stories, stories about what is currently working and/or liked in your current discovery system(s) and what could be improved. You can submit either one or both each time you use the form. A user story can be that of an external user (i.e. student, faculty, or researcher) and/or an internal user (i.e. library staff). It can be a story from your own experience as a user or a story you encounter in your day to day work with your patrons. We encourage you to send as many user stories as you want–the more, the better! Please share this with any students and faculty that you work with, the more user stories from a wide perspective the more we understand discovery needs.

Your input is incredibly helpful!

http://bit.ly/discoveryuserstory

If you have any questions about this survey please feel free to reach out to me or to the Discovery Committee representative from your institution.