As part of the Mellon Foundation grant funding the start-up of LYRASIS Technology Services, LTS is establishing a registry to provide in-depth comparative, evaluative, and version information about open source products. This registry will be free for viewing and editing (all libraries, not just LYRASIS members, and any provider offering services for open source software in libraries). Drupal will be the underlying content system, and it will be hosted by LYRASIS.
I’m seeking input on a data model that is intended to answer these questions:
What open source options exist to meet a particular need of my library?
This is a preview of Seeking feedback on database design for an open source software registry. Read the full post (513 words, 2:03 minutes estimated reading time)
We’re taking a break this week from the HarperCollins e-book story; although the commentary continues from librarians (and a few authors), there hasn’t been anything new (that I’ve seen) from HarperCollins itself. There is still plenty more to look at, though. First up is a report from the health care sector on the applicability of open source and open systems. Next is an interview with a financial analyst that sees the end of the “big deal” for library journal subscriptions. And lastly is a list of web archive services that you could use to find old copies of web pages.
This is a preview of Thursday Threads: Open Source in Health Care, The Big Deal, Archives of Web Pages. Read the full post (829 words, 3:19 minutes estimated reading time)
Below is the text of an article I wrote for the LYRASIS member newsletter in which I talk about how a community of users of open source software is as important (if not more so) than the code. I’m reposting it here for the DLTJ readership.
One of the challenging and rewarding aspects of open source software is building and sustaining the community that surrounds the software. It is challenging because people and institutions use open source software for a variety of reasons. For some, having the computer source code means that they are empowered to adapt the software to fit their needs. For others, contributing talent and budget to a communal effort – something arguably aligned with the general ethos of libraries – means that ultimately a better solution is created for their own users. Yet another group sees an open source solution as simply the best tool to solve a particular problem.
This is a preview of The Challenges and Rewards of Open Source. Read the full post (459 words, 1 image, 1:50 minutes estimated reading time)
It has been the longest of weeks and the shortest of weeks. Longest because of a working weekend with the ALA Midwinter conference in San Diego. Shortest because the activities leading up to, during, and after the conference didn’t leave much time for reading items to prepare a DLTJ Thursday Threads article. This edition has three short pointers: a report from Midwinter on a project from OCLC to offer a basic website for every library, why governments are coming around to liking open source software, and a discussion of measurements of reliability.
This is a preview of Thursday Threads: Websites for Small Libraries, Open Source in Govt, Measuring Reliability. Read the full post (796 words, 3:11 minutes estimated reading time)
The turn of the year brings commentary on the past 12 months and thoughts on the future. This edition of DLTJ Thursday Threads looks at the relationship between libraries and electronic books with an offer by Sony to explain e-reader hardware to libraries and an opinion piece that libraries need to get their act together on the adoption of e-books. Then there is a look forward at possible trends for the new year; I try to pick out the ones that I think will have an impact on libraries. One trend that does seem to be emerging is the migration of libraries from proprietary software to open source software for their integrated library systems. Lastly, we’ll wrap up with a look at Public Domain Day.
This is a preview of Thursday Threads: Ebooks in Libraries, Prognostications for the Year, Open Source Adoption, Public Domain Day. Read the full post (1631 words, 6:31 minutes estimated reading time)
I was reading a story last week about the Linux Foundation‘s third annual report [PDF] of the Linux kernel, and in it was a section that talked about the affiliation of the programmers that contributed to the development of the kernel. This got me thinking about the affiliation of programmers in the library open source community. More on that after a brief detour to explain what the “kernel” is.
This is a preview of When Closed Source Companies Contribute to Open Source Communities. Read the full post (907 words, 3:38 minutes estimated reading time)
It has been a long week, so for many of you this edition of DLTJThursday Threads will actually be read on Friday. The spirit was willing, the topics were certainly out there in the past seven days, but the necessary distractions were numerous. Please enjoy this edition whenever you read it. As always, there is lots more on my FriendFeed aggregation page.
Google Refine 2.0, a power tool for data wranglers
This is a preview of Thursday Threads: Refining Data, Ebook Costs, Open Bibliographic Data, Copyright Infringement. Read the full post (606 words, 2:25 minutes estimated reading time)
News of my joining Lyrasis has been officially reported (“Timothy Daniels and Peter Murray to Lead LYRASIS Technology Services” [PDF]) so I can talk about it here now. On September 10th I left OhioLINK to join LYRASIS on September 13th as the assistant director for the newly emerging LYRASIS Technology Services (LTS). Along with Tim Daniels, I’ll be forming a group to help members among the various open source and commercial software options works best for their situations, including options where LYRASIS can effectively and efficiently aggregate Software-as-a-Service hosting options.
This is a preview of Now Working for LYRASIS. Read the full post (222 words, 1 image, 53 seconds estimated reading time)
Last month, the eXtensible Catalog (XC) project posted job openings for Java developers. These are short-term, grant-funded projects and, having been on the hiring side of that equation before myself, I know how difficult it is to get good people for a one- or two-year project. The XC posting is different, though, in one important way: it is possible to have XC buy out the time of a developer on staff for the time that the development is happening.
Consideration will be made for qualified developers that are currently employed at another institution, but who may be available for loan to the XCO [eXtensible Catalog Organization]. The XCO would cover the salary and benefits of such individuals in the form of a direct payment to their host institution. This is an excellent opportunity for a library to invest in open-source software for libraries as well as a way to temporarily offset staffing costs in a difficult economic environment. Only staff that can be made available to XCO at 100% time (or close to that level) will be considered for this arrangement.
This is a preview of Extensible Catalog Project Seeking Developers in Innovative Ways. Read the full post (239 words, 57 seconds estimated reading time)
Carl Grant, president of Ex Libris North America, posted a pair of messages on his corporate blog that it is worth calling attention to regarding the OLE Project final report, if you haven’t already run into them: OLE; The unanswered questions and Library Software Solutions – We need a higher level of discourse... Equally important is the comment on the first by Brad Wheeler, Vice President for Information Technology and Chief Information Officer at Indiana University. The whole thread should take about five minutes to read; five minutes well spent if you are interested in the intersection of community source software development with proprietary, closed-source software development. It is even more important if you are looking for a case study of governance issues surrounding community source software development. Go ahead…I’ll wait.
This is a preview of A Thread of Comments on the OLE Project Draft Report. Read the full post (648 words, 2:36 minutes estimated reading time)