Category Archives: Writing

Academic Papers Artwork baby names Blog blogging democracy Design ethics Facebook firefox Flickr folksonomies Google Google Docs Google Spreadsheets how-to information-architecture information-retrieval information design internet iphone journalism listserv mailing list maps mass media Online News Papers Photography plugin poll social-bookmarking social networking social software spam tagging trust Twitter Usability web-development Web2.0 webspam web standards WordPress Writing

Notes on “Systems of Knowledge Organization for Digital Libraries: Beyond Traditional Authority Files”

Academic Papers, Writing, , , , ,

Systems of Knowledge Organization for Digital Libraries:

Beyond Traditional Authority Files

(G Hodge – 2000)

One thing I liked was this definition:

“A KOS serves as a bridge between the user’s information need and the material in the collection. With it, the user should be able to identify an object of interest without prior knowledge of its existence.”

 

I like the notion that a KOS helps users find resources they’re not even aware of. I think that’s an important goal.

 

An impression I get from a lot of LIS people is a mild disdain for the web. Obviously the web is in many ways unstructured and can be difficult to use in ways that library systems are not. At one point the article states that “Someone recently compared the Web with a large room filled with books that were scattered all over the floor.”

 

The description above is an example of the kind of lame metaphors this disdain fosters. If the web is a large room filled with books, it is the largest room that has ever existed; the vast majority of books are available virtually for free; and although they are scattered all over the floor, thousands of people will freely provide you with maps to find books on certain subjects, and everyone is provided with magical binoculars that let them see deep inside books and find a single phrase.

 

I’m not saying that bringing better standards to the web any devising better KOSs to organize web resources is bad, just that it seems like many LIS people take the existence of the web for granted.

 

One thing mentioned throughout this article is the high cost of indexing and cataloging or merging different cataloging schemes together. I think the costs may be exaggerated in some ways. For example, if you wish to catalog web resources for educators and for medical professionals, two groups that probably have different terminology for similar concepts, you don’t need to pay thousands of grad students to index everything under one, then the other scheme. Instead develop a mapping system that translates between the two types of terminology. The mapping system would be a big project and have to be very robust, but once it’s built it can run behind the scenes when anyone does any kind of searching. The article mentions cases where this has been done (with MESH terms, for example) but insists that it is a high-cost venture.

 

Similarly, what’s wrong with using the users of the indexing system as the workforce? Logs of search terms and phrases and how they are used together can be analyzed. Users can be tracked to see which titles or abstracts they click on when searching for certain terms, how long they spend at that resources, etc. Users can even be asked to rate resources and search results. If you are in the market for a hard drive or digital camera, I recommend you go to bizrate.com, pricegrabber.com, or any of a dozen services that allow users to rate both products and merchants, making it easy to find a good LCD monitor at a reputable dealer despite the massive anonymity of the Internet and the ease of creating fly-by-night stores or selling junk merchandise online. Something similar could be done to winnow out junk information and organize information resources.

Ignorance, paralysis or expense: The problem of software and business method patents for information architects and web designers

Academic Papers

[Note: this is a paper prepared for a graduate course in the IAKM program at Kent State University.]

What is the first step an information architect or web designer makes when designing a web site? Designers are often worried about principles such as giving users control, being consistent, providing feedback, or not relying on users’ memory (Dumas). Or, they are mentally checking off any one of a thousand “top ten mistakes” lists available in books and on the web. They may even start by discussing requirements with clients or conducting usability tests. But chances are, they aren’t at the US Patent Office web site. The last thing most information architects and web designers think about before creating a web site is doing a patent search. And this is becoming a big problem.

The introduction and explosion of software and business method patents relating to website design features presents a major problem to those who design sites, and designers and companies find themselves in three positions: ignorant of the issue, caught up in the “defensive” patent race themselves, or perhaps ultimately paralyzed and unable to continue work.

Continue reading →

Usability test of the Kent State IAKM home page

Academic Papers, Usability, Writing, , , , , ,

Note: this report shows the results of a usability test of the Information Architecture and Knowledge Management program web site at Kent State University in 2003. The site has since been redesigned.

1. Introduction

In usability study of the IAKM web site I found a number of serious problems. Current IAKM students were asked to complete a series of tasks using the site. Although participants were able to complete the tasks 91.67 percent of the time, they met all performance goals for each task only 36.11 percent of the time. The site is not fundamentally broken, but clearly there is room for improvement. Through statistical analysis, observations of the students, and remarks made by the students a number of issues were uncovered.

Many of the problems were global problems with site navigation and labeling, but there were also a number of prominent local problems. The severity of problems were rated via three categories:

  • Severe—prevents the user from completing a task or results in catastrophic loss of data or time.
  • Moderate—significantly hinders task completion but users can find a work-around.
  • Minor—irritating to the user but does not significantly hinder task completion. (Artim, 1).

Problems are also rated by scope. Any problem can be either global, meaning it applies to most pages or the site as a whole, or local, meaning it is particular to a page or specific section. Global problems are generally more pressing than local ones.

Findings are presented first in order of importance, followed by a description of the study methods.

  Continue reading →