Journeys of a FOLIO early implementer

20190516_141514.jpg

I remember when, a wide-eyed young cataloger (this was about three years ago), I was asked by my colleagues Siska and Marie – then in the process of capturing the staff’s thoughts on our current library systems – to list things I wished it were possible to do in our ILS Sierra. In response to many of the things I pointed out, I was informed that the functionality I requested actually exists – we just don’t use it. One of the main lessons I took away from that experience was the importance of articulating my assumptions and ideas, so that others can challenge, confirm or make them better.

The past months have provided plenty of opportunity for me to do just that. From a three day working meeting in Amherst with our fellow EBSCO beta partners, via the annual meeting of the EBSCO Systems Nordic User Group which Chalmers had the pleasure of hosting in early April, to the German FOLIO days in Bremen.  April also saw the birth of the FOLIO Implementers interest group, which meets virtually every week to discuss challenges of and strategies for implementing FOLIO.

Common to all of these meetings is that they provide the opportunity to share experiences and ideas, inspiring you to think beyond your own horizons, and to develop and sustain that invaluable network of people – with names and faces – that you know you can get in touch with when you need help, advice, or someone to bounce ideas with. Keep reading to learn more about how we experienced this at the EBSCO beta meeting and at the German FOLIO Days.

Meeting the EBSCO betas in Amherst, MA

In late March, my colleague Lari and I spent three productive days getting to know and working together with colleagues from the libraries at University of Alabama and the Five Colleges in Amherst. Like Chalmers, these libraries are implementing FOLIO as EBSCO beta partners, with hosting, implementation and support services from EBSCO. Hosted by the 5 Colleges and organized by EBSCO’s team of implementation consultants, the meeting included many interesting discussions and quite a bit of hands-on work.

One day of the meeting was spent going through each library’s existing feature prioritizations in small groups (e.g. resource access, ERM). The slightly daunting task of expressing your library’s requirements by ranking features (needed to go live, needed later, not needed) in FOLIO’s issue tracking system JIRA is something every early FOLIO implementer has, or will very soon, come into contact with. It’s one of our primary tools for helping the project decide which features need to be developed first.

At Chalmers, planning to go live in 2019, we have already reviewed our rankings several times to make sure they properly reflect our actual needs. Still, discussing them in new constellations can give new insights: it forces you to go back and explain, maybe reexamine, those assumptions and familiar habits that underlie your decisions. Which features do we really need to provide good service to our patrons, which ones to recreate the workflows we have in our current ILS:s, and which ones because we simply haven’t thought of other possible (good) solutions that exist? And which are those features that will make us think of FOLIO as a really good system? These are excellent questions to discuss with fellow implementers.

At the end of that day, we could all be very proud that, defying belief, we had actually made it through all the features and refined our prioritization of them.

Amherst1-1

Feature prioritization in action. (Photo by Theodor Tolstoy)

Among the many interesting implementation topics we touched upon during these three days, I found it particularly valuable share the other betas’ experiences with and ideas regarding how and when to talk about FOLIO with the general staff. When is it fun and exciting, and when unnecessarily unsettling, to see a system in development? How do we best leverage curiosity and deal with legitimate concerns? How does training to prepare for go-live differ from training to keep up to date and to foster an atmosphere of engagement and continued learning?

I found it very inspiring to hear about the communication activities at Five Colleges, which include a monthly FOLIO newsletter and open events where staff watch and discuss the FOLIO Forum webinars together. Their view has been that, when given the ability to stay informed and take part in the conversation, staff members can turn their concerns and ideas into involvement in the project.

At Chalmers, we have for the past months at several occasions invited library staff to come and, in a very informal and exploratory setting, try out some basic workflows in FOLIO. We’ve done this in small groups, through open invitations, and with at least two implementation team members present. The idea with these workshops is to give staff a chance to familiarize themselves with the system, while giving us great feedback on functionality and UI that we’re able to relay to the community. Seeing our colleagues test FOLIO with fresh eyes really has been inspiring and energizing as well as informative.

German FOLIO Days in Bremen

bremen1

A captive audience at the German FOLIO Days.

In mid-April my colleague Marie and I went to Bremen for the German FOLIO Days, which we saw as a chance to get to know European members of the FOLIO community. It was great to see and speak to so many librarians and service providers from all over Germany, and some visitors from other countries, all curious about FOLIO. For Chalmers it is crucial to have a strong footing in the European community. We know that there are issue and interests particular to the European context, like the GDPR and localization and internationalization, that are vital both to us as European institutions and for FOLIO to be a project with a truly international identity and viability in the European market.

The German FOLIO Days programme included demos from several product owners, including fresh looks at acquisitions, MARC cataloging and electronic resource management. The German FOLIO community has played and continues to play a crucial role in the development of FOLIO’s electronic resource management functionality, and the first German implementers, among them the University of Bremen, are planning to start managing their electronic resources in FOLIO this fall. While Chalmers has been using different ERM systems for quite a while, Bremen are taking the leap straight from Excel sheets and e-mails to FOLIO’s integrated resource management modules. We look forward to sharing this journey with them, and with all our fellow FOLIO implementers.

Since neither Marie nor I speak German, we had an interesting time using online translation tools, the advantage of having a Germanic first language, and kind help from fellow conference participants to keep up with presentations and workshops in German. Finding the right balance between a common language and the language that attendants are most comfortable is a tough challenge – but it’s one that I’m actually happy to see us faced with, since it means that the community really is international. It might also have been partly thanks to this creative confusion of languages, paired with the openness of the people present, that I found myself feeling oddly comfortable in a workshop in German on loading user data into FOLIO using bash – another language I’m not quite fluent in yet.

personalworkshop

Chalmers staff testing FOLIO.

As you discuss workflows with fellow FOLIO implementers at the top of the (very high) W.E. Dubois library in Amherst, as you write to a fellow systems librarian to ask how they would tackle a certain issue, as you watch your colleague check out a book in FOLIO for the first time, something falls into place. It’s in these encounters, between people and between software and people, that all that hard work we put in – across time zones and countries and professions – gets a chance to try its wings and embark on its (initially bumpy) flight.

Working with FOLIO, at this moment in time, you get to experience these encounters of people and software and organizations and ideas in abundance. In the coming month I look forward to trying out the latest release of FOLIO in the Q 2.1 release bugfest, to delving further into data migration, and to talking FOLIO with international colleagues at the FOLIO working meeting in Washington DC and at ALA.

/Lisa Sjögren

Curious about FOLIO?

Chalmers Library is planning to migrate to a brand new, actually not yet existing, library services platform called FOLIO. Partnering with EBSCO, we will be the earliest adopter, going live with the first version in 2019. Here I will try to outline the foundations of FOLIO, no previous knowledge required.

A new library system built from scratch

Photo of thinking woman with FOLIO pen behind the ear.
We want a potent library system that meets our requirements today and can adapt to future needs.

The philosophy behind FOLIO is to build what libraries need, with a modern and flexible infrastructure and a well-thought-out design for a good user experience. Well, of course, that is what every library system company would say, but in this case librarians are involved from start to end. And there is no company who owns the system.

One basic idea is the concept of ”apps”, i.e. pieces of functionality. None of these apps should be too large and each could easily be replaced by another app if needed. The technique behind this is called micro services and the intention is that selected apps will serve as one system.

FOLIO will be handling both print and electronic resources and related library tasks. In the core setup, there will be apps for knowledgebase(s) including link resolver activation, licenses and other workflows for e-resources, as well as metadata management and circulation of print books.

Screenshot of FOLIO apps

Later on, anyone who wishes can extend their installation of FOLIO with additional functionality or replace parts of the system with apps they would rather use. For example, a consortium may prefer a more extensive app to handle finances than a small library who prefers simplicity. Or you may feel the need to build an app to integrate with your home grown inter library loan system or institutional repository.

The user interface is a for librarians only. There will be no OPAC among the core apps, instead the user has to find the material in a discovery system who will call FOLIO to display loan status, make requests etc. EBSCO discovery system (EDS) as well as some open source discovery systems are currently working with FOLIO integration.


Who is developing FOLIO?

FOLIO is an acronym for The Future of Libraries is Open. It may sound a bit fishy, but the basic idea is that the source code is open for anyone to use and to build upon. Also, anyone can install FOLIO locally, free of charge.

FOLIO is being developed as a collaboration within the non-profit open source promoting organization Open Library Foundation (OLF). In OLF, The Open Library Environment (OLE) coordinates the work together with EBSCO information services, the Danish software development company Index Data and several other teams.

Computer screen showing web meeting text
Librarians work together with product owners at online meetings. There are Special Interest Groups (SIGs) for metadata management, accessibility, reporting, and many more.

As a community driven project, engaged librarians are working in together with product owners to determine which functionality the apps should encompass, how the workflows should behave and to test the user experience. The work is completely transparent and anyone can join.

However, the tempo would not be this high without the involvement of commercial companies who are investing heavily with dedicated teams of developers. EBSCO, ByWater, SirsiDynix, Index Data and others are planning to sell hosted environments and support services as well as endeavouring to integrate with existing library systems components. To make FOLIO a success is of course vital for these companies.

Further on, the idea is that a flora of libraries and companies will make and offer new apps with extended functionality. It’s up to the developer to decide weather the app should be free of charge or not.

Is any library using FOLIO?

No, not yet. But Chalmers Library is intending to go live with FOLIO as the very first library, soon, really soon.

So why on earth are we planning to leave established library systems to embark on this project? Well, that’s another blog post…

Want to learn more?

Folio.org – the starting point.

The FOLIO wiki – The node for the special interest groups and, well, essentially everything. For example, have a look at some app ideas or The Codex vision which is currently being discussed within the community. Go to the bottom of the page to learn how to join a SIG.

FOLIO UX – demos of the design work and vision.

FOLIO demo site – the latest stable version. Login with diku_admin / admin

At Open Library Forum on You Tube you will find several presentations. For example, this recent roadmap update which also covers the basics about FOLIO and shows how features are prioritized.

Previous blog posts about FOLIO

/Marie Widigson & the FOLIO team at Chalmers

A year closer to FOLIO

As the winter holidays draw close, so does the end of Chalmers’ first year of working hands-on as EBSCO’s beta partner within the FOLIO project. We started off 2018 with a workshop where my colleagues at Chalmers and I, together with Theodor, our FOLIO implementation consultant from EBSCO, first started discussing our hopes and goals for FOLIO and the future. While the spring that followed was primarily dedicated to going from Summon to EDS and to exploring and setting up our FOLIO alpha environment, and summer introduced us (and other “early implementers” of FOLIO) to the wonderful world of feature ranking for development, the autumn semester saw us focusing more intensely on future data flows between systems, circulation functionality in FOLIO, and e-resource management.

Sharing bibliographic metadata

For the past months, we’ve put a lot of work into planning and preparing the flow of bibliographic metadata between Swedish union catalog LIBRIS, FOLIO, other metadata sources, and EDS. One thing that we knew early on is that, from now on, we want to do all our print cataloging in LIBRIS. Using LIBRIS to its fullest lets us take advantage of other libraries’ cataloging and subject expertise, while sharing our own expertise with the rest of the LIBRIS community and to the world – and we are of course looking forward to exploring the possibilities created by LIBRIS’ transition to linked data together with the fact FOLIO is not based on the MARC format. We also knew that we do not want to duplicate data, that we want to automate the data flows between the systems as much as possible, and that we need to differentiate between data used for circulation and data used for discovery.

IMG_20180907_102148_771-e1545162958540.jpg

Looking at a patron record in Chalmers’ FOLIO environment before a meeting with LIBRIS. The hat behind the coffee cup was purchased in Durham, NC, where I attended a FOLIO conference in May. Read more about the conference in this blog post.

One of the exciting activities that was born from this was a hackathon where some of our own developers, our FOLIO implementation consultant, my systems librarian colleague Siska, and I, worked together to create an OAI-PMH client that would automate the flow of metadata between LIBRIS and FOLIO, and convert the incoming data from the format provided by LIBRIS to the FOLIO Inventory format. We found that the hackathon format has suited us especially well in this project.  First of all, the developers get direct real-time input on what the tool they’re building needs to do from the end-users (librarians, in this case). Secondly, it’s a great opportunity for systems librarians who do not have a background in programming to pick up some of the knowledge, practical experience, vocabulary and confidence needed to understand, talk about and work with our systems and data on a deeper level.

hackaton1

Systems librarians, electronic resource librarians and developers hard at work at our first hackathon, held in spring, where we built an interim solution for displaying Terms of use (as we we lost that service going from Summon to EDS).

What we (need FOLIO to) do

We have also spent countless hours trying to figure out what it actually is that we need from FOLIO: which functionality is necessary, which workflows have to be supported, what makes an interface easy to work with. As the library set to implement FOLIO first, we have a great opportunity to make our voice heard and contribute with our knowledge and vision. In this, we’ve had assistance from several people from EBSCO and the FOLIO community, who’ve walked us through existing and planned FOLIO functionality in order to help us understand how it supports our current and desired workflows. In November, we welcomed three product owners from FOLIO with whom we had great discussions about circulation, acquisitions and ERM.

Our feedback, both to the FOLIO community when reviewing planned features and to ourselves when looking at our own current workflows, has often boiled down to one thing: make it simpler. This owes in part to the modest size of our library, in part to philosophy.

A few weeks later, we had a visit from one of the American EBSCO implementation consultants who helped us get started writing manual tests based on our own workflows. That is something we look forward to sinking our teeth further into this coming spring. Writing and carrying out these tests will, besides letting us find bugs and gaps for the FOLIO developers to fix, provide an opportunity for us at Chalmers to try out our workflows in FOLIO and to get acquainted with the system before we go live.20181219_141722So there we are. From that first workshop in January where we were just starting to figure out our part in the FOLIO project and the potential FOLIO holds for us, through a fairly harmonious implementation of EDS, great encounters and conversations with the FOLIO community, countless discussions of our feature requirements, and some interesting discoveries made while cleaning our catalog data, we have had an intense, challenging and exciting year.

Wishing you all a happy holiday season!

/Lisa Sjögren & the FOLIO team at Chalmers

 

Hellre grits tillsammans: rapport från World Open Library Foundation Conference

Sitt namn till trots erbjöd WOLFcon (World Open Library Foundation Conference) få förvillade varulvsfantaster i pälsbeklädd kostym. Istället befolkades denna historiens första WOLFcon av en salig blandning bibliotekarier, systemutvecklare och representanter för systemleverantörer i sedvanlig dräkt. Gemensamt för de deltagande var engagemanget i och intresset för de olika projekt som stiftelsen Open Library Foundation (OLF), tillägnad open source- och opan access-teknik inom biblioteksvärlden, driver. Bland dessa projekt finns också organisationen Open Library Environment (OLE) och knowledge basen GoKB, men det var tydligt att fokus just nu ligger på open source-projektet och bibliotekstjänstplattformen FOLIO.

Det var förstås även FOLIO, och Chalmers planer på att inom en inte alltför avlägsen framtid börja använda FOLIO som biblioteksdatasystem, som förde mig till ett försommarvarmt Durham, NC, nyfiken på den ”community” som så ofta beskrivs som FOLIO-projektets kärna men som kan te sig litet abstrakt betraktat från kontoret på ett förhållandevis litet bibliotek i Sverige. Att  komma till WOLFcon — som välkomnade 190 deltagare — och inse att communityn faktiskt utgörs av människor, med kunskap, erfarenhet och engagemang, var inspirerande och hoppingivande.

Möten och modeller

2018-05-08 19.19.49

Kristin Martin från University of Chicago håller i en session om e-resurshantering. (Foto: Theodor Tolstoy)

Veckan inleddes med ett ”FOLIO Meetup”, med samma upplägg som den FOLIO-dag som hölls i Uppsala i höstas, riktad främst till dem ännu inte börjat engagera sig i FOLIO. Duke Universitys Tim McGearys inledande anförande kring Dukes mångåriga engagemang i FOLIO och OLE följdes av demonstrationer av utvalda delar av systemet, presentationer av special interest groups, datamodeller och roadmaps, och — äntligen! —  ett diskret offentliggörande av namnen på de två biblioteksorganisationer — University of Alabama och Five Colleges Consortium — som tillsammans med Chalmers kommer vara först ut att använda FOLIO med tjänster från EBSCO.

Tisdag, onsdagen och torsdagen riktade sig mer till dem som redan är involverade i FOLIO. Efter morgnarnas plenary sessions erbjöd schemat ett flertal valmöjligheter, med många parallella spår och arbetsmöten. Jag passade på att skaffa mig en bättre inblick i bland annat arbetet med moduler för MARC-katalogisering och batchhantering. Jag bevittnade även delar av ett tre dagar långt arbetsmöte (med ämnesspecialister, UX-designers och utvecklare) kring FOLIO:s framtida, ej ännu utmejslade funktionalitet för e-resurshantering — en synnerligen viktig fråga för oss här på Chalmers, där de elektroniska resurserna utgör en överväldigande stor andel av samlingen.

När WOLFcon inföll var det två veckor kvar till införandet av den nya dataskyddsförordningen, så förstås erbjöd konferensen även en session tillägnad GDPR och anonymisering. Med deltagare från flera amerikanska bibliotek och från några av de företag som arbetar med den tekniska utvecklingen av FOLIO på plats blev det en intressant diskussion om olika tekniska lösningar såväl som om den eventuella konflikten mellan begränsning av datalagring och möjligheter till statistikuttag.

Vid en session hade jag dessutom nöjet att själv, tillsammans med kollegor från Tyskland och USA, vara med och presentera vad arbetsgruppen för hantering av analytiska och boundwith-poster arbetat med. Den datamodell vi visade upp — ett försök att försona europeiska katalogiseringstraditioner med amerikanska, komplexitet och oförutsägbarhet med enkelhet och standardisering — inspirerade en mycket animerad diskussion bland deltagarna.

Det viktigaste målet

Det starkaste intrycket jag tar med mig från WOLFcon är just  diskussionerna, de varierande utgångspunkterna, de ibland delade, ibland vitt skilda, erfarenheterna, generositeten — ja, insikten att FOLIO-communityn består av människor som delar med sig av sin tid och sina idéer. Som, för att parafrasera en representant från Index Datas Sebastian Hammer, arbetar tillsammans om än utspridda för att skapa en flexibel, community-ägd plattform bortom de proprietära systemens slutna trädgårdar. Vem vill inte vara del av någonting sådant?

Nu är Chalmers en del av det — liksom EBSCO, Cornell, Index Data, ett gäng tyska och kinesiska konsortier, Duke, Stacks, Texas A&M, Samhaeng. Aktörer från olika länder, offentliga och privata, av olika omfång, med olika förutsättningar, styrkor, svagheter och insatser. Och som en del av utbytet finns förstås också kompromisserna, missförstånden, de ändlösa diskussionerna, de enskilda behoven som aldrig lyckas blir del av de gemensamma.

”There are many right ways,” sade EBSCO:s Gar Sydnor under ett kort anförande. Tanken är betryggande, men också svår. För om många tillvägagångssätt är rätt, hur kan vi enas kring något med tillräcklig kraft för att genomföra det?

Ett av mina favoritinslag på WOLFcon var den gemensamma konferensfrukosten. Ackompanjerade av ömsom grits ömsom gröt möjliggjorde dessa morgonstunder — innan folk hunnit samla sig i sina vanliga arbetsgrupper — möten med människor som just den dagen råkade äta frukost vid samma tid. Jag tänker att just den öppna och välkomnande atmosfären, tryggheten och spänningen i att kunna slå sig ned vid ett nytt bord och plötsligt vara del av en ny, oförutsedd konstellation av kompetenser och erfarenheter, är en förutsättning för att projektet ska kunna rymma både kompromisser och kreativitet, och för att vi som community ska våga och orka dela med oss av och i någon mån släppa taget om våra tillvägagångssätt och idéer.

Låter det spännande? Med OLE:s Ginny Boyers ord: “To get engaged, just show up.”

/Lisa Sjögren

Inga fler inlägg.