In a merging of two of my great interests, NASA has issued a Request For Information (ROI) on how best to “analyze and catalog notes from spaceflight pioneer Wernher von Braun into an electronic, searchable database or other system.“

Sample Page from Von Braun's Notes

At first glance, this is something that would be solved by using library tools and software.  However, the list of potential ways to set this up seems to illustrate the gaps in library technology (all points are mine):

• Users should be able to see the notes as they exist.
• The text in the notes, as well as all labels and notations, should be fully keyword searchable.
• All elements of the notes, including text, formulas, diagrams, etc. should be able to be targeted and described in a way that allows for keyword searching.  This includes “tagging”, but also commentary, description and critique.
• Users should be able to define relationships (create links) between ideas within the notes, as well as documents and other resources from other collections.  For instance, someone seeking information on the Saturn V Engine Bell should find all drawings, notes, diagrams, and formulas within the notes, as well as outside resources relating to all of these.

This project begs for a combination of a traditional database (for storing and searching text) with the added functionality provided by social software products.  Nothing in the list is beyond the current means of technology… think  of a wiki combined with flickr-type functionality that can utilize PDF documents and you have a good starting point.

Why hasn’t this been done?  How many libraries and archives have document sets like this that could become a researcher’s favorite collection, with the right application of technology?  Have any been digitized with a social annotation feature?

Why do I suspect that the development of this will come from outside the library community?  We should already have projects that utilize this kind of mash-up philosophy… our collections could be so much more powerful.

There are some great things being done in the library technology realm, and many people and projects that are worth praising.  But now and then I see something like this and wonder how we missed this obvious application of existing technologies.

found via ResourceShelf and Wired Science

Web 3.0 Concepts Explained in Plain English is a collection of presentations, all striving to describe the next phase of web activity and development.  If all you look at is the single slide that sums up the differences between the three web generations, you will likely have a better grasp of what is coming than before.

found via Stephen’s Lighthouse

This has been a busy week; so much so that the previous post, HTML 5, Google Wave, and the Future of the Web was started last weekend, with some editing and additions each day, and them actually posted yesterday.  Note that it says “posted”.  I realized last night that I hadn’t actually finished it.  So, if you read it and wondered what the heck did HTML 5 have to do with the rest of the post, here is my wrap up:

You may be wondering why I started this post discussing HTML 5.  The newest version of HTML has been in development for years, and has had its share of controversy.  Many developers and users have spent years pushing for effective use of web standards, with an eye towards XHTML use and support, which emphasizes the separation of content and style.

HTML 5, according to some, muddies the content/style waters too much, and will make it harder to preserve the gains that continue to be made.

However, with the timely announcement of Google Wave, it seems clear that HTML 5 is a game changer with serious potential, and that it will make many things easily possible that currently require a great deal of work and computing power.

For the next few years, at least, we will be working with web pages that, at best, will be coded to two fairly different standards.  XHTML and HTML 5 will co-exist, and if web developers approach their task with an understanding of each, we can design sites around the standard that suits them best.

Perhaps the next iteration of HTML will be a unification of the standards, allowing everything to exist within one framework.  I don’t know if that is possible (and don’t know HTML 5 enough to have a grasp of the differences between them), but I for one will be very happy to have two powerful and well-created standards to work with, and look forward to seeing what lies in the future.

Amidst a great many other topics, HTML 5 has been on my mind the past couple of weeks.  It started on Tuesday, May 26th, with Kevin Yank posting HTML 5 : Now or Never? on the SitePoint blog.  He was floating the question of whether or not they should look into publishing a book on HTML 5 now, or if they need to wait until it matures enough for developers to use with confidence.  If you read his post, and especially if you look over the comments, you will see that there is a full range of opinions (including that HTML 5 should never be implemented) by developers about the topic.

This remained a relatively minor, background issue until two days later, Thursday, May 28th.  On that day Google announce the existence of a new project called Google Wave.  My initial thought was that Google was simply creating their version of a FaceBook/Twitter/Blogging style platform.  The more I looked, the more I realized that this was much different, and much more important, than a differently branded service.  Wave is something that has the potential to change many, many aspects of how we use the internet.

What is Google Wave?  I have spent a good part of last week trying to distill it into a couple of paragraphs, and am not having much success.  The overall essence of it is something that I haven’t yet wrapped my head around, but here are a few aspects of it that will hopefully illustrate some of it:

It is a communication platform that allows users to send, receive, and use a variety of information (think communications like e-mails, IM, tweets, feeds, etc.) in a way that offers greater control, speed, and usability.  Messaging becomes “real-time”, with your keystrokes being sent live to the person you are communcating with (unless you select to hold the message until you are ready).  The effect of this is that it becomes possible to hold a real-time conversation with others utilizing a variety of communication forms simultaneously.  You can incorporate text, images, documents, and other digital formats into the conversation in a free-flowing manner that saves time, effort and reduces confusion.

To quote from the introduction to an interview, “Email is asynchronous conversation. Instant messaging, by contrast, is synchronous. Wave is both.“  Possibly the best general description of Wave could be that it lets users and groups easily communicate and collaborate in one interface, using whatever editing/communication/collaboration techniques fit the task at hand.  Think of it as a collaboration mash-up tool.

A few places to find further info:

• Went Walkabout : Brought Back Google Wave. (Google Blog)
• Google Wave Drips with Ambition. (TechCrunch)
• Video Interview with the Google Wave Founders (TechCrunch)
• Live with the Google Wave Creators (TechCrunch)
• Sergey Brin : Google Wave Will Set a New Benchmark for Interactivity (TechCrunch)
• Google I/O A Real Eye-Opener (SitePoint)

Watch for the technological shift from these developments.  This will not only give us new and improved tools to perform tasks and work together (think of the possibilities for online meetings and conferencing), but will set standards for what will be expected from web presences.  Our OPACS may have some new goals to aim for.

Note added later:  I have had a busy week, and forgot to actually address the relationship between HTML 5 and Google Wave.  I do so in another post, Why HTML 5.  Apologies for not getting it right the first time!

The National Library of Australia has launched the beta of their new search interface, SBDS Prototype (SBDS stands for Single Business Discovery Service, I think), and the search experience is not only better than any other library-related search I have used, it is faster than most of them as well!

Other reactions:

• Roy Tennant at LibraryJournal.comt
• Roy Tennant at HangingTogether.org
• Lorcan Demsey (1)
• Lorcan Demsey (2)

This is an excellent example of what is possible today, and what we should all strive for in our search interfaces.  There is such a diversity of resources, and unifying these into a usable and fast single-search service is a credit to the developers at the National Library of Australia.

Open Jurist is a great add-on to the free case law resources I wrote about a few days ago.  Consisting of over 600,000 opinions from the federal court system, including the United States Supreme Court and the Federal Appellate Courts.  This looks to be a great resource for research into federal court cases.

One minor negative:  one of the first searches I performed, Bush v. Gore (the Supreme Court decision regarding the 2000 presidential election) didn’t work as it should have because the case is listed as “George Bushs v. Albert Gore“.  The “s” at the end of the word kept it from the first page of results.  I initially thought it might have referred to the plurality of petitioners (”et al.”), but a Google search actually produces no results when the “s” is included.  I looked for a way to notify those who run the site, but only found an e-mail address that was to be used “if you have access to more cases or know where we can get more of them”.  Any website meant to offer a service should have (at least) a method for general contact.

found via ResourceShelf

Eric Shonfeld at TechCrunch writes:

“Once again, the Internet is shifting before our eyes. Information is increasingly being distributed and presented in real-time streams instead of dedicated Web pages. The shift is palpable, even if it is only in its early stages.”

Twitter.  RSS.  Facebook.  Digg.  You-Name-It-Feed.  It is becoming apparent that this is the next big shift in internet usage, and, as with the previous shifts, it is hard to guess what the effects will be, and who will be affected.

And this, like previous shifts, will not supplant previous internet use trends.  HTML, or some form of it, will still be very dominant.  Blogs and Wikis will continue to exist, and will be useful tools for certain types of communication and interaction.  Integration will continue to be the norm, with the “now” infusing itself throughout.  How will this change be considered dramatic?

“Traffic occurs in bursts, depending on what people are paying attention to at that second across a variety of services. Someone might notice an obscure blog post on Twitter, where it starts spreading, then it moves to FriendFeed and Facebook and desktop stream readers such as Tweetdeck or Seesmic desktop and before you know it, a hundred thousand people are reading that article. The stream creates a different form of syndication which cannot be licensed and cannot be controlled.”

This “cannot be licensed and cannot be controlled.”  Think about this.  How much of your web presence is based on control:  control of layout, content, contributors, and most of all, control over the rate at which change occurs?   For a library web site, how much of this control is able to be ceded before the concept of a library web site itself changes, without controls?

As with many future technology issues, now is the time to begin thinking, discussing, understanding all of this.  We cannot begin the process of deciding or planning, because none of us can predict how this will play out.  What will we have in place to deal with this, to anticipate this, to harness this?  One benefit of this process will be the inevitable inspiration that some will have about the potential of streams; a future must-have library web site technology might come from this.

Start thinking!

Google has made the jump into supporting Microformats as well as RDFa, calling their implementation “Rich Snippets”!

This is great news on several different levels. Semantic markup within web pages provides a way to target searches much more effectively.  TechCrunch provides an excellent example:

“If I was to write a post that mentioned “The President” without naming him, Google probably wouldn’t realize that I was talking about President Obama – it might think I was referring to another US president, or perhaps the leader of a company. But using RDFa I could tag the words “The President” with “Barack Obama”. That tag would be visible to machines spidering the page for indexing (resulting in smarter search results), but wouldn’t be shown to users reading the post. In effect, it’s a way to tell search engines about your content without exposing your visitors to extraneous text.”

In addition, sites that provide well-structured metadata have the potential to be much more usable (and useful).  Library web sites, especially OPACs and Resource pages, should include structured information that details the context of the displayed content.  Using microformats in our web sites will benefit everyone involved over time.  As David Peterson notes on the SitePoint blog:

“Now that Google is supporting structured data it is high time to learn how to use this stuff.”

This post will contain just a couple of links, but there is a wealth of information on the other end of each:

• 101 Great Free Sites and Downloads You’ve Probably Never Heard Of has been put together by PC World.  I will bet you have heard of at least a few of these, and I would recommend using this as a starting point in your search for resources and applications (i.e. if you see something helpful, look for other resources that provide the same… PC World sometimes skips great resources for simply new and flashy resources).  found via ResourceShelf
• 30+ Places to Find Creative Commons Media is a post on the SitePoint blog, which is a great resource for web developers.  This list is fairly focused, but many people forget about the treasure trove that is Creative Commons when they look for pictures, sound or other media resources.

A Periodic Table of Visualization Methods is a great resource if you have information you need to present visually, but don’t know the best way to express it.  Simply go to the site and let your mouse hover over the examples in the different categories.  Note the creative use of the Periodic Table structure.

A word of caution:  too often people fall into the trap of using a visualization method that they find appealing, but that doesn’t quite fit their information.  In addition, focusing on the presentation of information at the expense of Keeping It Simple (a.k.a. Style vs. Substance) can lead to a result that looks great but doesn’t say anything relevant.

found via Dysart & Jones

Now that Google Ventures has been officially announced, I can go public with my own news:

Libology is one of the first group of startup companies which will be receiving Google Ventures funding.  I have been in talks with someone from their Cambridge office over the past few weeks, just sent in the signed contract yesterday, and today the terms of the contract take effect.

The biggest change you will notice is that they requested some design changes to this blog, mainly to make it easier to integrate with other Google services.  (See below for screenshots)  If you are viewing this through a feed reader, check out the main page of this blog, or view this post.

Another change you may notice is that I will stop being critical in any way, shape or form when referring to Google or any of their partners, including OCLC.

And, of course, one must always remember what today is!

Google Style Main Page

Post Googlized

This is just one of my passing thoughts, which I suspect is understood by many, but not necessarily expressed this way:

Google’s PageRank is, for all practical purposes, a form of social networking applied to the concept of a particular html tag.  The ranking system is built upon the idea that someone, somewhere, decided that something on their web page was so associated with another web page that it needed to be wrapped in <a> </a> tags with the web page’s address referenced.  Thousands (millions!) of people finding it imperative to add these tags around their text, and thereby making it possible to judge the importance of specific web sites by aggregating these millions (billions!) of tags.  Will we look back at this and call it the beginning of social networking on the web?

the thought passed through my head while reading Stefano’s Linotype…

File this as a future wish-list item for your online catalog:

There is a new and interesting way to connect an OPAC search result for a journal to the full-text journal articles, and it is called ticTOC.  The application of this shows just how effective a well thought out mashup can be.

Last December, I ran across a blog post on RSS4Lib about the TicToc project, which has been in existence for a couple of years, but had just officially launched. I never got around to posting it, but I made a point to watch for further information.

TicTOC provides, via an RSS feed, the table of contents for the current issue of whatever journal you search for.  There are currently over 12,000 journals included in their service.  Read the RSS4Lib post (above) for a more detailed description.

There is now at least one library, Wageningen UR Digital Library in the Netherlands,  that has created a mashup in their OPAC that shows just how powerfully this can enhance an OPAC search.

Locate a journal using their e-journal search, or go straight to the result screen for the Journal of zoology : proceedings of the zoological society of London.

1. Click on “Show recent articles” on the right side of the screen.
2. To display an article’s abstract in the OPAC, click on “Show abstract”.
3. To get to the full text of an article, click on the title of the article, then click the full text link on the publisher’s site.

Two clicks from the journal result in the opac to the full text of an article in the current issue.  I am not sure what would need to be done to deal with proxys and journal databases, but for articles retrieved through the publisher’s web site, this is very straightforward and useful.

This appears to be a great service, and the Wageningen UR Library has done a fantastic job in creating the mashup.  I look forward to seeing how this is integrated into other collections.

found via RSS4Lib

Sir Tim Berner-Lee started what is now known as the World Wide Web exactly twenty years ago.

In this posted video from Technology, Entertainment, Design (TED) 2009, he discusses how it started, where we are, and where we might be going.

So think about libraries and the web… what we have done in the past 20 years, were we are now, and where we can go.

found via TechCrunch

(and since it happens to be on the same topic, a happy birthday shout-out to Kristine as well!)

Web Tech Guy and Angry Staff Person (an exaggerated tale) is a video designed to be a provocative look at the arguments for opening library/museum data to web 2.0 social uses

The video isn’t so much exaggerated as much as it packs many of the arguments one hears against social uses of data into a short time span.  It was created by Michael Edson, Director of Web and New Media Strategy for the Smithsonian Institution.

found via Stephen’s Lighthouse

I’ve added a couple of plugins to the Libology Blog to increase usability:

• Viper’s Video Quicktags – this is a great improvement over the way video is embedded in blog posts.  First, it is much easier than the other methods I have used; second, it doesn’t break the xhtml validation of the site.  Yesterday’s post on the Touch Book has video embedded using the new method.
• MobilePress – this automatically formats the blog for mobile browsers (i.e. cell phones, I-Touch, etc.).  It seems to work fine on this online emulator, as well as a co-worker’s iPod Touch; if results vary for you, please contact me.

Readability is quite simply one of the easiest-to-use and effective usability aids I have seen in quite a while.

Follow the link, set the controls for your most comfortable reading style, drag the “Readability” button to your bookmark toolbar, and click the the link in your toolbar whenever you want to read an article on an otherwise cluttered or problematic website.

Voila!  It even works great for generating print versions of pages.

found on MetaFilter

The Library Web Site of the Future, written by Steven J. Bell, is yet another essay about what is wrong with library web sites, and yet it is not just another essay…

It is a strong critique that touches upon many aspects of our web presence, and emphasizes that users, both students and faculty, are increasingly bypassing it and seeking information elsewhere.  Read it with a critical eye towards your library’s web site, but I suggest taking some of it with a grain of salt.

Bell’s conclusion is that libraries have erred in not following the lead of marketing design experts, that we are moribund because we don’t let our sites be transformed into an “advertiser of campus wares to those who would buy into the brand.”

I suspect the answer is that our web sites tend to be moribund because we let them be.  We tend to design by committee, attempting to force what should be a easily navigated collection of resources into a click-fest labyrinth.

Try having someone unfamiliar with your website navigate it with a general purpose in mind (”I want to find a full-text magazine article.”) and see what blind alleys they encounter.  This is about the simplest usability test you can create, and it can be telling.  But it is only the start.

Bell suggests that focusing on usability is a misstep, and that it is simply “rearranging the deck chairs on this Titanic.”  I think that the problem is that usability is not a misstep, but only the first step in a different direction.

We need to make accessing our resources so straightforward, so open, and so universal that people will use them because it is the path of least resistance to the information they seek.

There are many elements to this, and Bell is right in many of his criticisms, but libraries need to be as universal as possible.  Keeping our resources in a silo, no matter how good the resources, does not generate traffic.  We need to open it up as much as we can, and continually push to open the rest.

In addition, we need to get our resources where our users are.  Do you use RSS to get information to users?  Do you use social networking to get information to users?  Your resources, if disseminated the right way, become your best marketing strategy.  Figure out where your potential users are, and then figure out how to connect your resources to wherever that is.

You don’t need to turn your site into a product to be marketed; you need to get your product to market.

found via LISNews

SitePoint Reference is an online guide with a wealth of information on web design.  Divided into three sections, HTML, CSS, and JavaScript, it is a great place to find that bit of information you need while designing or editing a web site.  Keep it in your bookmarks.

You might recognize SitePoint from their book publishing, including the recent Everything You Know About CSS Is Wrong! which details the use of CSS tables in web design.  The title is hyperbole, in my opinion, but the book itself is excellent.  It has changed how I view the design of web pages, and I hope to put it into practice in the near future.

found via the SitePoint blog

The New York Times Blog announced today that they have released an API for their Best Sellers list.  Library programmers should jump on this.  Imagine being able to display information about an item’s rankings – dates, placement, etc. – in your OPAC like you can show book covers, Google Books, etc.

The data only covers June 2008 forward, but they will be extending it back to 1930 within the next few months.

This is a great move by the NYT; their Best Sellers list is considered definitive, and encouraging its use and adaptation means it will continue to be influential.

found via Web4lib (thanks to Steve Toub)