April 9, 2010

Protecting User Privacy in the Age of Digital Libraries -- Blog Post #7

The article is a reflection by an electronic services librarian. She is reflecting on the troubles surrounding privacy issues for SUNY Cortland library patrons. According to the article, the university had four areas in which patron information was being held, unnecessarily. They were: ILS, LLS, websites, and proxy servers. The author didn't try to tackle the ILS problem because it was, at the time, already being addressed by SUNY Cortland. The ILL system was unnecessarily keeping track of the books students requested. The websites were keeping browsing histories, cookies, and IP addresses. Then, the proxy servers were keeping track of IP addresses used to gain remote access to library resources.
To remedy these problems, the author (Karen Combs) did the following. She eliminated the history of ILL loans, changed the CPU settings so that the browser histories and cookies would be deleted upon log-out, and removed the last 8 digits of the IP addresses that were using proxy servers. By doing this, in addition to eliminating SSNs within the library/student record system, she was able to greatly increase anonymity among digital resource users within her library system.

*Coombs, K. A. Protecting User Privacy in the Age of Digital Libraries. Computers in Libraries v. 25 no. 6 (June 2005) pp. 16-20

March 31, 2010

The system development life cycle and digital library development

This article is more about generic system development life cycles than about "digital library system life cycles." The main idea is that there is a standard set of steps that all systems undergo. It can honestly be applied to any system. The steps, in a nutshell are: Preliminary investigation, Problem analysis, Requirements analysis, Decision analysis, Design, Construction, Implementation, Operation and support. I'll very briefly explain them.

Preliminary investigation is determining what, if anything, needs to be done. Problem analysis determines the shortcomings of the current system. Requirement analysis determines the cost and time needed to undergo the change. Decision analysis is when the "higher ups" determine whether or not the plan is feasible. Design builds the idea for the system while Construction builds the actual system. Implementation puts the system into place. Operation and support use and trouble shoot the system.

The article explained, fairly well, the process by which systems change over. I should mention that the author wrote about the difficulties of the final stage (having two concurrently running systems). The situation, according to the article, happens because it is the easiest way to transition from old to new systems. The trouble is that the organization must then maintain both systems.

While they eventually fully integrate the new system, it is only on step one of its life cycle ... only to soon be replaced by another.



MANAGING DIGITAL LIBRARIES:
THE VIEW FROM 30,000 FEET
The system development life
cycle and digital library
development
H. Frank Cervone
Northwestern University, Evanston, Illinois, USA

March 16, 2010

Blog #5 - "Introduction to Databases"

P. Tero (2004). "Introduction to Databases"


The article is very much an introduction to databases. That is to say, Tero doesn't get into much detail. He does however, cover four areas: SQL, websites/databases, scripts, and querys.


He explains that SQL is an acronymn for Structured Query Language. This is apparently the language in which relational databases speak to one another. Its operations look similar to HTML, but the similarities end there. Tero mentioned that popular database software programs use SQL but hide them behind the user interface.


He mentions briefly the relationship websites can have with databases. The only use for this I saw, for companies, based on his explanation was the idea of constantly having access to company records and orders via an intranet. With respect to his ideas on queries, the explanation was rather simple. He only says that they can be used to retrieve specific data. He also shows what a stringed query would look like in SQL. However, the explanation and examples ... and subsequent explanation of the examples are sparse.


The entire article seemed like an abstract or executive report that would be given to a company president, with the intent of convincing them of the necessity of using a database.

March 2, 2010

Library 2.0: Service for the Next-Generation Library

The article is outdated. It was written in 2006, and has long since been surpassed. The essence of the article is the then move towards library 2.0. This, of course, has already happened. The authors focus on what was relevant at the time. That is to say, they write about user generated content, online downloads, and reviews. This was very interesting in 2006, but we're in 2010. User generated content should be automatic.


Unfortunately, it is not true. Many libraries are still filled with Baby Booming Generation Exers and remain clueless to the changing trends and how to employ them.


I will say that for the time period, the authors had the right idea. User generated content was coming of age, so to speak. However, with the move towards newer better and more expansive "library 2.0" apps and methods, the article seems little more than an example of what libraries and librarians should be doing with respect to the changing technologies of the day.


Library 2.0: Service for the Next-Generation Library by: Casey, Michael E., Savastinuk, Laura C

February 15, 2010

Response to "How Internet Infrastructure Works" by Jeff Tyson

This article gives a very basic overview of internet infrastructure. It focuses on explaining the different parts and aspects of the internet and how they operate and communicate with one another.
The topics and areas covered are IP addresses, NAP's ISP's, PoP's, Routers, URLs, DNSs, Ports, and HTTP. Essentially, the author gave a series of brief definitions on each of the aspects of the internet and explained why they are all crucial.
This isn't technically an article. It seems like something you'd see in a textbook. Because of the articles bullet-ed style, its hard to really pin down an overall theme. This is not to say that I didn't learn what the pieces of internet infrastructure are. Its just to say that the "article" was really more of a list of elongated definitions.
However, I did learn some relevant information about how information is shared and accessed via the world wide web.

How Internet Infrastructure Works

by Jeff Tyson

January 31, 2010

Blog #2 ILS Systems

Overview of ILS
Deddens’ Overview of Integrated Library Systems is a brief look at three companies and their respective offerings in the field of academic integrated library systems. In the article, Deddens first gives a somewhat vague interpretation what an ILS is.
After the introduction, there is, what seems to be, a company outline of options from each of the three ILS providers (MAPS, III, and Endeavor). All three companies, essentially, offer the same products. They all focus on three things: XML harvesting, metadata creation, and access to digital resources.
Endeavor seemed outdated. The company didn’t offer anything new, in that everything there has been seen before. Access to e-books, e-journals, etc. just isn’t good enough. While efficient, it is not groundbreaking in any way.
“MAPS” within Sirsi was different. Sirsi is usually seen as more public than academic. However, it does complete the same tasks as Endeavor. It’s everything you’d expect to see in an ILS.
Now, III was the best example of an ILS provider in the article. III offers the same things as the others. But, two things stick out. III offers support for Dublin Core storage and the ability to index and add trusted websites to the ILS. This is not to say that the other vendors don’t offer these tools. Perhaps they failed to mention this. III’s ability to do this is impressive. It shows that the vendor has a better understanding of the needs of the users and custodians of the ILS.

Dismantling Integrated Library Systems
Andrew Pace’s Dismantling Integrated Library Systems, is not exactly what the title of the article suggests. It isn’t as drastic. He is simply making the point that in order for ILS systems to remain relevant, they must adapt to changing trends and advances in technology. In order ILS systems to do this, they must dismantle, both literally and figuratively.
They must literally dismantle their current systems and, a.) update the ILS and integrate new technologies or b.) start anew. Pace makes a good point that the current array of ILS systems is quickly falling out of date. There are so many new options and abilities that the ILS systems can create or integrate to make searching, researching, and general information seeking and keeping entirely better.
The good news for ILS systems and their creators and custodians is that the field is wide open, waiting to be pounce upon.


M. Deddins (2002). "Overview of ILS" EDUCAUSE http://net.educause.edu/ir/library/pdf/DEC0201.pdf
A. Pace (2004). "Dismantling Integrated Library Systems" Library Journal. http://www.libraryjournal.com/article/CA374953.html

January 25, 2010

Toward a Twenty-First Century Library Catalog - Blog #1

To be honest, this article was a snoozer. While the title seemed interesting, the content was yesterday's news. It feels like Academics as well as the "Baby Boomers" think they've caught on to something new once its existed for a few years.

The crux of the article is the idea that library catalogs are still functioning the way they did in the eighties. They are, of course, obsolete. It is overwhelmingly difficult to find exactly what you want. This can be said of academic databases as well. If you're not well versed in "Controlled vocabulary" and "Boolean terms," you're out of luck.

To remedy this problem, NC State Univ. decided to try using a catalog that bases itself on, essentially, popular search engines. It encompasses ratings, like terms, similar searches, and corrects spelling.

I like this idea. I'm actually a bit confused as to why it hasn't been done before.
The conclusion was that integrating the more user-centric approach, as opposed to a rigid librarian based one, was a better option.