Showing posts with label licensing. Show all posts
Showing posts with label licensing. Show all posts

Tuesday, August 26, 2008

Will the FM Radio Band Be Expanded?

I'm surprised I didn't come across this one earlier.

In March, the FCC proposed turning over the bandwidth currently occupied by analog channels 5 and 6 over to the FM band (76-88 MHz). If approved, this could open opportunities for additional channels when the digital television transition is complete next February. The spectrum currently reserved for channels 5 and 6 is immediately adjacent to the existing FM broadcast dial and could be easily be re-appropriated to expand the FM dial to accommodate up to 60 new stations.

This will be an interesting change. I know I am used to seeking out local college and Public Radio stations down in the lower FM band. The question I have is if the FCC will be simply expanding the low power band to accomondate new community stations. This may be the case since the idea was embedded deep within a proposal to promote diversity ownership. Sphere: Related Content

Wednesday, April 30, 2008

Cern 'Open Sourced' the Web

Sir Tim Berners-Lee was recently interviewed by the BBC to mark today's 15th anniversary of the day that Cern put the web's code into the public domain.

Berners-Lee indicated that making the web free to use had a vital role in spreading its use worldwide. However, the decision by physics laboratory to release the web code into the public domain was not a straightforward one. The difficult part was explaining the true nature of what the web was going to be and that this was going to take off and it was a really big thing. Therefore, Cern couldn't hold on to it and "the best thing to do was to give it away."

In a fateful decision that significantly helped the web to grow, Berners-Lee and Robert Cailliau managed to get Cern to provide a certification on April 30, 1993. Once the technology and program code was in the public domain anyone could use and improve it.

Cailliau notes:

"If we had put a price on it like the University of Minnesota had done with Gopher then it would not have expanded into what it is now. We would have had some sort of market share alongside services like AOL and Compuserve, but we would not have flattened the world."


As a side note, in A Short History of the Web, Mr. Cailliau recalls that during sessions in the CERN cafeteria, he and Berners-Lee discussed a catching name for the system. The only exception that he noted when Berners-Lee proposed 'World-Wide Web' was that it is difficult to pronounce in French. Sphere: Related Content

Wednesday, November 07, 2007

Revisited: Are OSS4Lib Networks Needed?

Over a year ago, I posted a piece entitled Are OSS4Lib Networks Needed? I argued that libraries have traditionally banded together to pool resources with the common goals of obtaining monographs, serials, and databases as economical as possible. The decision to develop or become involved with a library network is to affect a positive change on a library’s ability to plan and budget.

Unlike these cooperative efforts of the past, libraries have chosen to work independently on information system solutions. So, I asked this question: With the significant costs involved in the purchasing and maintenance commercial information systems why haven't more libraries banded together to build library systems?

A post by Joe Lucia to NGC4Lib presents a compelling case in support of this concept. He discusses a shift from an investment in commercial software support to a collaborative support environment for open source applications facilitated by regional networks.
"It is frightening for many to contemplate the leap to open source, but if there were a clear process and well-defined path, with technical partners able to provide assistance through the regional networks, I suspect some of the hesitancy to make this move, even among smaller libraries, might dissipate quickly... The success models are there and developing best practice frameworks and implementation support methods that will scale will not be rocket science."

"What if, in the U.S., 50 ARL libraries, 20 large public libraries, 20 medium-sized academic libraries, and 20 Oberlin group libraries anted up one full-time technology position for collaborative open source development. That's 110 developers working on library applications with robust, quickly-implemented current Web technology -- not legacy stuff. There is not a company in the industry that I know of which has put that much technical effort into product development. With such a cohort of developers working in libraries on library technology needs -- and in light of the creativity and thoughtfulness evident on forums like this one -- I think we would quickly see radical change in the library technology arena. Instead of being technology followers, I venture to say that libraries might once again become leaders. Let's add to the pool some talent from beyond the U.S. -- say ! 20 libraries in Canada, 10 in Australia, and 10 in the U.K. put staff into the pool. We've now got 150 developers in this little start-up. Then we begin pouring our current software support funds into regional collaboratives. Within a year or two, we could be re-directing 10s of millions of dollars into regional technology development partnerships sponsored by and housed within the regional consortia, supporting and extending the work of libraries. The potential for innovation and rapid deployment of new tools boggles the mind. The resources at our disposal in this scenario dwarf what any software vendor in our small application space is ever going to support...

I couldn't have said it any better.

The State of Ohio has a great resource in OhioLink. OhioLink is a consortium of 86 Ohio college and university libraries, and the State Library of Ohio, that work together to provide Ohio students, faculty and researchers with the information they need for teaching and research. Serving more than 600,000 students, faculty, and staff at all 87 institutions, OhioLINK’s membership includes 16 public/research universities, 23 community/technical colleges, 47 private colleges and the State Library of Ohio.

I have been in discussions for over the years involving concepts like a state-wide electronic document delivery system. They go nowhere. Right now, much of the technical site of the OhioLink system lies on the shoulders of Peter Murray and Thomas Dowling (There are a couple others, but they are the ones I know of) The usual response is they can provide a LAMP box for testing, but have no spare staff for development, let alone ongoing support. So, the question I have been posing for a while now is:

What if each of the 87 institutions provided 1/2 of an IT position to OhioLink as a condition of membership?

That would result in over 40 FTE developers. Not only would the state be able to build and maintain an vendor-based catalog system that uses open standards and service-oriented architecture, they could build other systems and services that could benefit the entire state rather then each struggling to find resources to do so. Imagine if each provided a full FTE!

The challenge that Joe will find is libraries are very protective of their IT resources. This issue became apparent to me in the question/answer period following my presentation at a Library 2.0 conference earlier this year. A library director asked how libraries can change from the siloed systems we currently have and adopt SOA. My response was essentially it is up to you! The discussion then turned to the limited numbers of IT human resources. (In my opinion, this is because too many library directors still equate all technical knowledge as being interchangeable and that all IT staff know everything. As a result, most libraries do not allocate enough resources into IT yet have high expectations of their limited staff. But, I digress.)

The challenge continues to be that libraries leaders/directors need to be willing to see the benefits and more importantly, willing to make the sacrifice. They control the resources and therefore hold all of the cards. So, having more of us out there talking to them like Joe, is key! (assuming, of course, that they are not in this communication space and not a part of the dialog).

There have been many of us out there evangelizing for over 10 years now, (Thanks, Dan Chudnov and Eric Lease Morgan, for helping me see the light!) and we are only now beginning to see some daylight. Sphere: Related Content

Tuesday, September 25, 2007

I'm Tired of Hearing This From Library System Vendors:

"...our development folks have talked about...I'll let them know of your interest in such functionality and we'll consider it as potential enhancement to the system"

I was at OhioLink yesterday attending a demo of the OCLC / Illiad system. Since the presentation was by a sales rep I sent this email to Atlas after the meeting:
"As you may be well aware, a general library trend is figuring out ways to get into our customers workflow. We can no longer expect our customers to want to come into each of our silo library systems. To that end, we have been doing some pilot testing of various Google and Facebook gadgets. It makes a great deal of sense that one of the systems which we can create gadgets for is the Illiad customer interface. We would love to be able to provide our customers with an easy view of their pending requests from their iGoogle home page or their Facebook profile. We are interested in building such gadgets, which are customizable so that any Illiad licensee could modify them for their local system."

"Are their any APIs or Web Services available from Illiad/Atlas Systems which would enable us to build such gadgets for the Illiad community?"

"Exposing such services in those spaces would enable all libraries to raise the profile of the Illiad service."

The top of this post was a part of the reply I received (sigh).

Before I continue, I want to say that Illiad is a very powerful system that can save valuable staff time. The efforts that Jason Glover and Atlas Systems team have made in developing and promoting an open standard for Internet document delivery (even if as a community we continue to support a proprietary closed system as the defacto standard) are commendable.

Based on my past interactions with Atlas, part of me expected (hoped?) that they would have already thought of this. The response is unfortunate. It appears that Atlas has simply grown up into just another library system vendor, waiting until there is a large enough group requests an enhancement.

The problem is that this is exactly the kind of functionality we desperately need from our systems - today. If we are going to continue to rely upon hosted or licensed solutions we need vendors to be thinking about integration between products before we say we need them.

The reality is that by the time that a large enough group of Illiad customers realize the potential of such functionality and communicate it to Atlas, and it is developed, yet another window of opportunity will have closed behind us. Sphere: Related Content

Monday, July 16, 2007

Service Oriented Library Systems Pt. 4: Challenges

In my three (1 2 3) SOLS posts I have provided a basic introduction to SOA and how it can be applied to the development of the next generation of library systems.

Historically, library information systems solutions have been built (almost) exclusively by vendors. While some libraries do build their own systems or use open source solutions, the large majority still rely upon vendors. Most of our challenges in implementing SOA are the direct result of this decision.

Commercial software developers rarely develop new products until they find a critical mass of users since they need to recoup development costs and make a profit at the same time in order to survive. The relatively limited size of the library system market makes it a difficult one for new vendors to enter. This means libraries have few choices when choosing software solutions and few libraries will switch once a significant investment in licensing, maintaining, and training support. When a library becomes so dependent on a vendor for products and services and cannot move to another vendor without substantial costs, whether real or perceived.

The first challenge to adopting SOA is that library systems vendors have created an effective paradigm that many libraries cannot afford to break away from. The vendors of key library systems understand the lock in phenomenon and libraries let them get away with it.

Many library vendors, if not most, build their solutions upon proprietary architectures. Some vendors are beginning to build their systems around some of the principles of SOA. Still, the core of what makes SOA work - the API - remains one of their their most tightly guarded core intellectual properties and revenue streams. The vendors place a death grip on those very APIs which would allow libraries to create SOLS using services provided by disparate systems.

The lack of compatibility between different library systems intentionally or unintentionally forces a customer to continue to use products and services from a particular vendor. Developers may design their products so that replacement parts or add-on enhancements must be purchased from the same manufacturer, rather than from a third party. Developers may also build in incompatibility between versions of their systems to force customers to upgrade.

The second challenge to adopting SOA is that the lack of compatibility and the API licensing fees charged to developers to create compatible products - required in SOA - creates a barrier for new vendors trying to enter the market for a particular library system. If the costs of entry or compatibility are great enough an effective monopoly can be maintained.

Libraries have built entire resource sharing networks around single vendor solutions. This results in a de facto standards. De facto library system standards are those which have been accepted for practical purposes by a significant proportion of the marketplace. What comes to mind is a significant library Internet document delivery network based on a product who's name is now a verb.

The third challenge to adopting SOA is that for work flow or legacy reasons we continue to support single vendor supplier solutions. In doing so, we create an environment where library products do not have to keep up with current technology needs, service support that does not meet expectations, and systems that will not allow for the adoption of SOA.

When one steps back and looks at it, we have nobody to blame for outdated library information systems or our inability to more readily adopt SOA except for ourselves. We keep licensing these products at a time when the number alternative approaches available to libraries has never been greater.

In the last posting in these services (no. 5) I will provide some closing remarks and observations.

CONTENTS:

Part One: Introduction
Part Two: What We Have Today
Part Three: Where Are We Heading?
Part Five: Final Comments Sphere: Related Content

Monday, June 18, 2007

CIC / Google Cooperative Agreement Details

For those of you that find reading legal documents enjoyable, the 16-page Cooperative Agreement between the CIC and Google has been posted on the CIC web site. Sphere: Related Content

Tuesday, June 12, 2007

OhioLINK's Tom Sanville Receives ASCLA Award

One of many reasons that it is great to be a librarian in Ohio (yes, there are many) is OhioLink. For the past fourteen years, Tom Sanville has served as OhioLINK's executive director. He also led the way for the partnership that created Libraries Connect Ohio and is one of the founders of the International Coalition of Library Consortia.

Tom's hallmark has been demonstrating that librarians can successfully negotiate with vendors. While having breakfast at a conference with a vendor representative last year he looked at the institution on my name tag. His first words were, with a hint of fear in his eyes, "Oh, you are from Ohio. I have had many tough negotiations with Tom Sanville."

I just received an email that Tom has been named the 2007 recipient of the Association for Specialized and Cooperative Library Agencies (ASCLA) Professional Achievement Award. This award is presented for professional achievement within the areas of consulting, networking, statewide service, and programs.

The award will be presented during the ALA Conference as part of the ASCLA President’s Program and Awards Ceremony, "Is Your Information Technology Accessible? Section 508 and Libraries," on Sunday, June 24, 10:30 a.m. - 12:30 p.m., at the Grand Hyatt Washington Hotel, Constitution B.

Congrats Tom! Sphere: Related Content

Wednesday, June 06, 2007

CIC Enters Google Books Project

It was announced this morning the twelve Committee on Institutional Cooperation (CIC) Libraries (of which Ohio State is a member) have entered into agreement with Google to digitize up to 10 million titles from their collective library collections. The details of the agreement will be released shortly by the CIC and Google. A FAQ is available.

Digitized titles from the collections that are in the public domain (generally those published before 1923 or by government agencies) will be made freely and fully available, while digitized titles still in copyright will be completely indexed and discoverable (readers will still be required to get the full text from a copy in a library or through purchase from the copyright holder/publisher).

The CIC is a consortium of 12 research universities including the 11 members of the Big Ten athletic conference and the University of Chicago. With campuses in eight states, CIC universities enroll more than 300,000 undergraduates and 76,000 graduate students, and employ some 33,000 full-time faculty and 139,000 full-time staff. The CIC is guided by the provosts of the member universities. Sphere: Related Content

Wednesday, May 23, 2007

Library Information Systems Quicksand

When the Internet came of age over ten years ago libraries had few information systems choices. Creating software applications back then required fairly complicated development tools and a relatively high degree of programming skills. It was rare for a library to have staff with such skills. Libraries had little choice but to license technologies from vendors.

As the paradigms have changed so have the tools and protocols of application development. They have become very accessible. Still, from my vantage point libraries seem to continue to fall further behind. As a profession we seem to be stuck in information system quicksand.

One of the problems is that most of the vendors used proprietary technologies instead of those that support open standards. These closed systems which our vendors have provided us have made solutions such as federated and metasearching quite complicated, if not impossible, primarily since our systems can not talk to one another.

While libraries have embraced consortia solutions for most large scale purchases, the collective vision of library leadership has failed to see the potential for open systems development that would result in new library systems based on open standards. These systems could be built using an open architecture and shared with the library community. Community source, if you will.

At the very least, I believe our library leadership and professional organizations need to begin demanding that vendors begin using open standards and opening up their APIs. By continuing to embrace proprietary vendor solutions - as they decide to build them - we may be destined to remain two or three years behind the technology curve.

I do applaud those libraries that have abandoned traditional library ILS vendors like Ex Libris, Innovative Interfaces, and SirsiDynix and instead have embraced systems like Endeca and AquaBrowser. While the later are still vendor solutions at least they are offering solutions that libraries need now, not just talking and planning for "future enhancements." Sphere: Related Content

Monday, February 19, 2007

Lockout Software that Locks-In Customers

As an open source/standards advocate I have communicated the evils of vendor lock-in. I came across this example tidbit in Ed Foster's 2/13 GripeLine column in InfoWorld:

In 2003, the U.S. Air Force held an open bidding for a post-warranty service contract on about $80 million worth of Eaton Powerware UPS (uninterruptible power supply) equipment it had purchased. Air Force officials were surprised when Powerware informed them that proprietary service software is required to fully maintain the UPS equipment and that Powerware would not provide that software to any of the third-party bidders or to the Air Force itself.

The Air Force had no choice but to award the contract to Powerware, costing taxpayers more than $20 million over what other firms were prepared to bid.

The lockout software is essentially a laptop-based replacement for the physical instrumentation and controls that used to come on UPS equipment and is required for getting complete internal readings and calibrating performance settings. According the the report, the requirement is not disclosed in product literature, their web site, or anytime during the purchasing process.

While I have not heard of any library vendors that have resorted to this tactic, it does go to show what a vendor can and will do to protect market share and revenue stream.

As the tools to create applications become more mainstream, and standards become more open, this strategy is one that libraries need to be aware of. Those encountering such undisclosed licensing issues need to communicate their experiences to the rest of the community in order to prevent other libraries from falling prey to such tactics. Sphere: Related Content