Feed aggregator

Jobs in Information Technology: August 24, 2016

LITA Blog - 4 hours 18 min ago

New vacancy listings are posted weekly on Wednesday at approximately 12 noon Central Time. They appear under New This Week and under the appropriate regional listing. Postings remain on the LITA Job Site for a minimum of four weeks.

New This Week

American Institute for Radiologic Pathology, Medical Archivist / Case manager, Silver Spring, MD

Visit the LITA Job Site for more available jobs and for information on submitting a job posting.

Categories: Library News

Axiell partners with Odlio to expand digital content offering to libraries

Library Technology Reports - 8 hours 8 min ago
(August 24, 2016). Axiell announce a partnership with Odilo, one of the leading digital content providers for libraries. The partnership will enable libraries to easily access and manage digital content, integrate a mix of content sources and quickly distribute high-quality content to patrons.
Categories: Library News

Family tree : a novel /

New At the Library - 8 hours 8 min ago

    ISBN: 9780062425430
    Author: Wiggs, Susan

Categories: Library News

Year 2010 : Sine Qua Non

Equinox Blog - 9 hours 26 min ago

This is the fifth in our series of posts leading up to Evergreen’s Tenth birthday.  

I often tell people I hire that when you start a new job the first month is the honeymoon period. At month three you are panicking and possibly wondering why you thought you could do this. At six months you realize you’ve actually got the answers and at twelve months it’s like you never worked anywhere else. For me, 2010 represented months six through eighteen of my employment with Equinox and it was one of the most difficult, rewarding, and transformative years of my career. Coincidentally, it was also an incredibly transforming year for Evergreen.

In early 2010, Evergreen 1.6 was planned and released on schedule thanks to contributing efforts from the usual suspects back at that time. Bug fixes and new development were being funded or contributed by PINES, Conifer, Mohawk College, Evergreen Indiana, Calvin College, SAGE, and many others in the community. Somewhere in the midst of the ferocious adoption rate and and evolution of 2010, Evergreen quietly and without fanfare faced (and passed) its crucible. Instead of being thrown off stride, this amazingly determined community not only met the challenge, but deftly handled the inevitable friction that was bound to arise as the community grew.

In late August of 2010 KCLS went live on a beta version of Evergreen 2.0 after just over a year of intense and exhilarating development. It marked the beginning of another major growth spurt for Evergreen, including full support for Acquisitions, Serials, as well as the introduction of the template toolkit OPAC (or TPAC). I have nothing but positive things to say about the teams that worked to make that go-live a reality. KCLS and Equinox did amazing things together and, while not everything we did was as successful as we had envisioned, we were able to move Evergreen forward in a huge leap. More importantly, everyone involved learned a lot about ourselves and our organizations – including the community itself.

The community learned that we were moving from a small group of “insiders” and enthusiasts into a more robust and diverse community of users. This is, of course, natural and desirable for an open source project but the thing that sticks out in my mind is how quickly and easily the community adapted to rapid change. At the Evergreen Conference in 2010 a dedicated group met and began the process of creating an official governance structure for the Evergreen project. This meeting led to the eventual formation of the Evergreen Oversight Board and our current status as a member project of the Software Freedom Conservancy.

In the day-to-day of the Evergreen project I witnessed how the core principles of open source projects could shape a community of librarians. And I was proud to see how this community of librarians could contribute their core principles to strengthen the project and its broader community. We complement one another even as we share the most basic truths:
*The celebration of community
*The merit of the individual
*The empowerment of collaboration
*The belief that information should be free

Evergreen is special. More importantly, our community is special. And it’s special because behind each line of code there are dozens of people who contributed their time to create it. Each of those people brought with them their passion, their counter-argument, their insight, their thoughtfulness, and their sheer determination. And together, this community created something amazing. They made great things. They made mistakes. They learned. They adapted. They persevered. And those people behind those lines of code? They’re not abstractions. They are people I know and respect; people who have made indelible marks on our community. It’s Mike, Jason, Elizabeth, Galen, Kathy, Bill, Amy, Dan, Angela, Matt, Elaine, Ben, Tim, Sharon, Lise, Jane, Lebbeous, Rose, Karen, Lew, Joan, and too many others to name. They’re my community and when I think back on how much amazing transformation we’ve achieved in just one year, or ten years, I can’t wait to see what we do in the next ten.

– Grace Dunbar, Vice President

Categories: Library News

bibliotheca partners with Living Language as the exclusive distributor of digital subscriptions for public libraries

Library Technology Reports - 11 hours 8 min ago
(August 24, 2016). bibliotheca announced a new partnership with Living Language, an imprint of Penguin Random House, for exclusive distribution of digital language learning courses into public libraries.
Categories: Library News

Evergreen 2009: Not Just Code

Equinox Blog - Tue, 2016-08-23 15:13

This is the fourth in our series of posts leading up to Evergreen’s Tenth birthday.  

I first became aware of Evergreen in 2007 when I saw a posting on a library technology listserv.  As an open source advocate and a librarian, I began following it’s progress. Skip forward to a cold morning in January 2009 and I was letting IT managers and library directors from around the state of South Carolina into a meeting room.  I was the IT manager at the Florence County Library and two months previously we, as a library, had decided to move to Evergreen.  We had written a long term technology plan and a critical part was our Integrated Library System.  Aside from Georgia, we saw Evergreen being adopted in Michigan and Indiana.  I knew that in time Evergreen would match and surpass our other options.

We also knew that an open source community was going to require changing our perspective of what our relationship to the ILS looked like.  The old proprietary vendor had legal control over aspects of the community and there were limits to what we could share among ourselves as customers.  Libraries had to strike special deals with strict non-disclosure agreements to gain access to source code and the insight to how the ILS worked behind the user interface.

To say that this was going to be different would be an understatement.  The source code was not only not confidential but openly published.  People developed reports and freely published them on community wikis while articles appeared in journals and on personal blogs.  The lack of a corporate gatekeeper was both invigorating and a little overwhelming.  Bringing in a vendor to run an ILS as a service made sense to us but could we convince others to join us?

We asked if other libraries would be interested in an Evergreen consortium.  The answer was yes.  There were a lot of concerns but the experts we called in, Equinox Software, seemed the perfect choice.  No one knew Evergreen as a team as well as they did and they had worked with small libraries and big consortiums.  Partnering with Equinox allowed us to start the migration process quickly despite very little in-house knowledge of Evergreen across our libraries.  And without a proprietary gatekeeper, other libraries in the consortium could dig into the deeper technologies to the degree they were comfortable doing so.  My library was definitely one of the others that wanted more.

We knew that user community was important.  Even with its limitations the user group of our previous ILS had been valuable.  2009 was the year I went to the inaugural Evergreen Conference.  2009 was the year I became active on the listservs, mostly watching but answering questions where I could.  2009 was the year I first volunteered to help out with community activities.  2009 was the year I first gave feedback on new features and bugs.  2009 was the year I, as a user, became a part of the community and saw an impact from it.  And, frankly, it was kind of easy.  I had an advantage being both a librarian and having a technical background but as I met others as new to the community as I was I saw them doing the same thing.  Where they became involved varies based on their interests and skills but everyone who wanted to found a place.  I even recognized a few from the user groups of my old ILS.  Before these people had been names and faces I vaguely recognized from meetings at ALA and listservs.  They had been users of the same thing I used.  Now, in the Evergreen community they were fellows and peers.

The open development process meant that I got a chance to provide feedback on features being developed that we weren’t paying for.  I had participated in feedback about features for proprietary ILSes.  It always felt like throwing pennies in a wishing well and crossing my fingers.  I didn’t work at libraries large enough to drive the process of development so we had to hope that the really big customers wanted the same things we did.  Here, the process wasn’t just open in name but discussion about requirements and needs was being done in public forums.  Input was not just allowed but encouraged.  It was clearly a matter of pride for the developers to know that their work was as widely useful as possible.  I could follow the process and choose to participate if it was a feature I was interested in.  And behind each of these things was a person, someone I got to know on a listserv or a conference.  

In December of 2009 our third wave of libraries went live.  Things had calmed down from the hectic early days of migrations.  It had been almost a year now since that early meeting when we went from “we want to” to “we are doing this.”  I remember having time to spend looking at bugs because we had the Christmas slowdown common to public libraries when a developer at another consortium sent me an email.  I commented on a bug that wasn’t a high community priority but it, well, bugged me.  I had helped this developer with testing some patches both to help him out and to give myself more patching experience.  He carved out time and fixed that bug for me.  The truth is that any human endeavor involves an economy of personalities.  But in the software world of meritocracy, open source projects are often more about code than people.  They are often tightly focused projects that do specific things.  An ILS isn’t tightly focused.  It touches on a vast swath of a library’s operations.  It took me a while to realize what now seems obvious in hindsight, but Evergreen isn’t tightly focused and it’s not about code.  Code is critical to the project as it is the means to an end but Evergreen is about people.  I learned a lot in 2009 but things have changed.  I’ve changed jobs and code has changed but the fact that Evergreen is about people hasn’t changed.

–Rogan Hamby, Project and Data Analyst

Categories: Library News

Evergreen 2008

Equinox Blog - Mon, 2016-08-22 13:42

This is the third in our series of blog posts leading up to Evergreen’s 10th birthday.  The other posts can be found here and here.

At the beginning of 2008, I was working for the South Carolina State Library. Like many libraries, we were joining the OSS movement by implementing open source tools to market services and increase discoverability of our collections. We were encouraging our public libraries to do the same offering classes on blogging, wikis and social media. It was no surprise when the State Library hosted visitors from PINES and Equinox to introduce Evergreen.

Having worked for an ILS vendor previously, I was intrigued by the possibility of an open source ILS. The idea that libraries could take back some control over how their ILS developed was exciting! There was a fair amount of skepticism in the audience. Evergreen was in its toddler years and, for some, they needed to see it mature a little before jumping on board. For others, they were ready for a change and saw Evergreen as the opportunity they needed to move their libraries into the future. This is where SC LENDS started to form, but I’ll let my colleague Rogan tell you that story.

For me, 2008 was the year I packed my bags for Georgia to join the Equinox team. I was inspired by what PINES had started and wanted to be a part of building Evergreen further. I knew libraries would gravitate quickly toward the open source business model and developing their own solutions. After all, libraries have been centered around open access and community since their inception.

It’s been a privilege to watch Evergreen grow from those early days to adulthood. I no longer have to talk to potential customers about open source concerns or the maturity of Evergreen. Our discussions are centered around the robust features of Evergreen and how it can work for their library. I still encounter skepticism but it often results in the best discussions. On those occasions where skeptics become true believers, we find our strongest community supporters.

Evergreen is turning 10 years old! It feels more like a 21st birthday celebration because we’ve come so far so fast. I raise my glass to Evergreen and everyone who has been a part of this first 10 years. I can’t wait to see what the next 10 years will bring!

–Shae Tetterton, Director of Sales

Categories: Library News

Round Rock Public Library goes live on ByWater Solutions Koha support

Library Technology Reports - Fri, 2016-08-19 12:40
(August 19, 2016). ByWater Solutions announced that the Round Rock Public Library of Round Rock, Texas is now live on their Koha open source integrated library system.
Categories: Library News

Evergreen 2007

Equinox Blog - Fri, 2016-08-19 12:34

This is the second in our series of posts leading up to Evergreen’s birthday.  The series starts with Jason’s post from yesterday.  Please do read that if you haven’t already!

In 2007 Evergreen became Open Source software in practice, not just in name.

The three committers to the subversion repository in use at the time, Jason, Bill, and myself had, over nearly three years, personally typed all of the code that made up the software, gladly accepting the many suggestions for improvement we received via email and in person, of course.

On Monday, March 5, 2007 that changed when Bill applied the first actual patch we’d received over the previous weekend. It wasn’t a huge new feature or reams of documentation, but it was a watershed moment for the project — with that one commit, pictured below, Evergreen was now software owned by more than one entity, locking in the promise of its Open Source licence by making sure nobody could hide the code away in the future.

Soon after that we began receiving contributions of code from more individuals, some folks from libraries, such as Travis Schafer, and some, like Scott McKellar, just folks that make a hobby of “nosing about in other people’s code.” By the end of 2007, the list of committers had grown from 3 to 4 — Dan Scott got the commit bit on September 7 — and contributors were in the double digits. Both accelerated quickly in later years.

Some of these early contributors were at institutions either testing or deploying Evergreen. Some of them are still there, running those installations. Of the production deployments, most were small compared to the PINES. However, the seeds of large sites were being planted.

It was in late 2007 that the first two SITKA libraries migrated to Evergreen; Prince Rupert Library and Fort Nelson Public Library. Now SITKA numbers approximately 200, but I’ll remember those first two clearly forever. I’ll remember them because 2007 was also the year Equinox began providing services to libraries interested in Evergreen, and I had the opportunity to personally perform those migrations in the fall of 2007.

It’s interesting, to me, at least, to remember that SITKA was Equinox’s very first customer; they signed their support and migration contract with us more than a month before PINES. In a way I think of that as emblematic of Evergreen’s past and its future promise.  We are a community that innovates. We are largely a community of early-adopters-cum-leaders.  And we are a community focused on both the promise and the pledge of Open Source — the development methodology and philosophy.  Looking back, all the way to the start, I see that’s always been the case and I’m proud to have been and still be a part of that.

— Mike Rylander, President


Categories: Library News

Librarians in the Wild: Selling Librarian Skills Outside of Libraries

LITA Blog - Fri, 2016-08-19 11:00


When I decided to pursue the MLIS seven years ago, it wasn’t so that I could tap into a vast supply of readily available Librarian positions. I did it because I was drawn to the profession and intrigued about how technology was changing it. My first job search as a degree-toting Librarian was a lucky one: I happened to find a place who needed someone with a strong foundation in project management and web development as well as an interest in librarianship, and that is as good a description of my professional self as you will find. That’s how I ended up at Avery Library.

Then life happened. As the project I was working on was ending, my wife and I decided to leave New York and return to San Diego. I’m not going to go into our reasons for moving, because they’re not relevant here; suffice it to say, my professional goals took a backseat to other considerations. The point is, I was back on the job market. This time, however, I wasn’t so fortunate: it took a while for me to find work, and when I did it was related to my pre-MLIS career. I’m still working in academia, but my current position is as a business analyst/project manager type person. Hey, sometimes you just have to pay the bills.

This recent experience got me thinking (again) about what being a librarian means in terms of everyday work and marketable skills. I’m not going to link to a bunch of depressing articles about the library job market, or the tenuous nature of the profession’s future; suffice it to say, there’s a lot of people with MLIS degrees out there, and, depending on where you live, not too many jobs in traditional Librarian positions.

Over the course of the next few months, I plan to highlight several different types of opportunities that provide a good fit for librarians looking to branch out, and in doing so answer three basic questions:

  1. What makes you (a librarian-type person) a good candidate for that job/field/organization type?
  2. How do you market your skills and experience to compete in that market?
  3. Why would you want to work there? What makes it a good fit not just for a librarian’s skills, but also her professional needs?

This is not a critique of the MLIS degree or the reasons people choose to pursue one. My goal is to provide information that is useful to you if you are trying to broaden your job search when finding a job in a traditional library is proving difficult, or if you just want to take your hard-earned skills and use them to try something new. I hope to highlight opportunities where librarians can not only get hired, but that also make meaningful use of librarianship skills and fulfill the needs of someone with a librarianship background. If you have suggestions for topics or any other feedback, please submit them it in the comments below.

Public Domain image courtesy of user Shyamal, Wikimedia Commons. Originally published in The Literary Digest.

Categories: Library News

Olin College selects TIND ILS and TIND Repository

Library Technology Reports - Fri, 2016-08-19 09:40
(August 19, 2016). TIND was selected by Olin College of Engineering to provide their cloud-based library management system. TIND is replacing the EOS.Web ILS and Digital Commons Repository. The solution will be integrated with EBSCO's Discovery Service.
Categories: Library News

Wiley signs definitive agreement to acquire Atypon

Library Technology Reports - Fri, 2016-08-19 09:40
(August 19, 2016). John Wiley and Sons, a global provider of knowledge and knowledge-enabled services that improve outcomes in research, professional practice and education, announced today it has signed a definitive agreement to acquire Atypon, a Silicon Valley-based publishing-software company, for $120 million in cash. Atypon is a trusted technology partner that enables scholarly societies and publishers to deliver, host, enhance, market and manage their content on the web. The transaction is expected to close October 1, 2016.
Categories: Library News

Swept away /

New At the Library - Fri, 2016-08-19 09:40

    ISBN: 9780778319016
    Author: Carr, Robyn

Categories: Library News

The angels' share /

New At the Library - Fri, 2016-08-19 09:40

    ISBN: 9780451484208
    Author: Ward, J. R., 1969-

Categories: Library News

The lost girls /

New At the Library - Fri, 2016-08-19 09:40

    ISBN: 9780062456601
    Author: Young, Heather, MFA,

Categories: Library News

La Universidad de Bath mejora la Colaboración entre Bibliotecarios y Docentes con Leganto de Ex Libris

Library Technology Reports - Thu, 2016-08-18 15:39
(August 18, 2016). Ex Libris anunció que la Universidad de Bath está implementando Leganto como solución para la gestión de listas de lectura, para mejorar el apoyo de la biblioteca en la enseñanza y el aprendizaje. La Universidad se une a una creciente comunidad global de clientes que ahora son capaces de integrar las listas de lectura de cursos con los procesos de la biblioteca.
Categories: Library News

Follett Destiny 14.0 Features Learning Management System Integration

Library Technology Reports - Thu, 2016-08-18 15:39
(August 18, 2016). Follett's new Destiny 14.0 release now supports IMS LTI (Learning Tools Interoperability) capability providing seamless, single sign-on integration to resources available in Destiny Discover via districts' learning applications. Earlier this week, Follett announced a series of significant updates to its market-leading Destiny solution, including an innovative Chrome extension and access to open education resources.
Categories: Library News

EBSCO Information Services expands U.S. Software as a Service Team hiring Andrew Nagy

Library Technology Reports - Thu, 2016-08-18 15:39
(August 18, 2016). EBSCO Information Services has expanded its Software as a Service Team, hiring Andrew Nagy as Director of SaaS Innovation. In this role, Nagy will work directly with libraries to help support the growth and development of the open source FOLIO Library Services Platform and the EBSCO SaaS portfolio. With his background in open source software, Nagy will continue to champion open source software in libraries.
Categories: Library News

University of Bath enhances collaboration between librarians and faculty with Ex Libris Leganto

Library Technology Reports - Thu, 2016-08-18 12:38
(August 18, 2016). Ex Libris announced that the University of Bath is implementing the Leganto reading list solution from Ex Libris to enhance library support for teaching and learning. The university joins a growing global community of customers that are now able to integrate course reading lists with library processes.
Categories: Library News

Venue and agenda announced for first OpenAthens Customer Conference

Library Technology Reports - Thu, 2016-08-18 12:38
(August 18, 2016). OpenAthens are pleased to announce the venue and agenda for the first OpenAthens Customer Conference, which will bring together information professionals and technical experts from across the spectrum of healthcare, academia, corporate and publishing under the theme of Creating Connections to discuss the key challenges and opportunities facing organisations in the context of Identity and Access Management.
Categories: Library News


Subscribe to Valley Library Consortium aggregator