Sub themes ELAG 2016

Implementing transition

Our world is changing fast and so libraries must change quickly too. Change is a common thread that runs through all library organisations regardless of size. Do libraries that handle this exit thrive well? And do libraries that not change will struggle to survive? At ELAG 2016, we want you to talk about the future: the new services, new data models, new roles and new responsibilities. Why do we need to change? What can’t we leave behind? How do we evaluate our transition? And, what is our future?

We would like you to talk about things like:

  • Where are our users and what are their needs?
  • What is our core mission and is it still relevant?
  • Who in our organisations need to change?
  • How can we implement the transition?
  • How can we evaluate these new services? What are our evaluation methodologies and frameworks?
  • And, where will this all lead?

Transitioning to other applications

Moving to new applications can bring great benefits for libraries and users; it can also be a painful process. With the availability of many different approaches to providing softwares, we want to hear about your successes, failures and new approaches.

We would like you to talk about things like:

  • Doing new things in new ways with your own and other people’s software
  • Moving between commercial/home-grown/open-source systems, including
    • Library management systems
    • Repositories
    • Discovery tools
  • Task automation (moving from manual workflows)
  • Taking a modular approach to systems: replacing parts of systems (submodules/utilities such as circulation, acquisitions) with similar parts of other systems
  • The choices, trade-offs, roadblocks and bottlenecks of transitioning between systems
  • Is now the time to transition to any new library oriented software, or should we wait for the next generation?

Transitioning to cloud systems

For many applications, libraries leave their local installations behind and transition to hosted, multi-tenant environments. This affects how we develop on these applications, and develop applications interacting with them. In addition to sharing software, libraries often share data on these platforms, creating new data workflows and policy demands.

We would like you to talk about things like:

  • Preparing old data for migration to new environments
  • What to do with legacy data
  • Tools and platforms for development with multi-tenant installations
  • Interoperability between cloud applications and local or third-party software and services
  • Risk factors and how you deal with them: legal matters and privacy; one vendor dependencies; retraining staff

Transitioning to new data models, infrastructure and  architecture

Although “MARC must die” is a long-standing joke at ELAG conferences, MARC has never made it through the exit. Some things are very persistent — especially data formats, standards and practices in libraries. From a technology point of view, we often argue that these are outdated, not well-suited for today’s requirements and time for an exit has come. But how can we perform an exit? How can we avoid being stuck in a transitional period, where we have to deal with old and new at the same time without coming closer to an exit? How do we handle migrations to new formats, standards, models, paradigms in an existing software landscape? How do we measure the success of a migration and what is lost during a migration — not only in quantity, but first of all in “quality”? How do we deal with gradual or incomplete migrations?
We would like you to talk about things like:
  •  Linked data is used in lots of new library applications, but it is only slowly making it’s way into core library systems. Do we need to move to new system architectures? Are you doing this? How?
  • How do you handle the migration to new standards, e.g. RDA in an existing systems landscape?
  • How do you monitor what gets lost during the migration to a new data standard or a new library system?
  • How do you make sure that — after adopting the paradigm of entity based cataloguing in your library — you can still interoperate with the rest of the library world that sticks with the traditional paradigm?

Transitioning to other services

Does the library start and end with your paper and electronic collections? Or, do we have new services that very much extend traditional library roles? What are the new service opportunities where our (IT)-knowledge can be reused in unexpected contexts?

In this sub theme we want you to tear down that library wall. Far from the traditional publication-centered services presented in libraries (cataloging, acquisition, loan, ill, institutional repositories, image catalogs, publishing services) you will present new roles and possibly new jobs.

We would like you to talk about things like:

  • The library as computing platform
  • The library as hosting provider of external databases and non-library data sets
  • The deeply embedded librarian as laboratory assistant working far away from catalogs, MARC, MODS and Dublin Core
  • Or, something completely new