Monday, October 25, 2010
10/25 Muddiest Point
Saturday, October 23, 2010
Assignment 4 Submission
My topics were children and technology, crowdsourcing, and memory and archives.
10/25 Reading Notes
TED Talks: Sergey Brin and Larry Page on Google
I love TED Talks!
So much is noteworthy in this video. Some things that stand out are: Google employees are allowed to spend 20% of their time at work on something important to them personally but not mainstreamed in the company; Larry Page’s statement, “We always hope that Google will be smart, but we’re surprised when only people think that it is” (or something like that); and that advertising allows them to operate worldwide, providing free, open information to everyone regardless of where they’re from and how much money they have.
All those points indicate how aware Google is of its power in the global economy and how consumers perceive the company.
As a side note, this article from NPR was really interesting. It paints Google in a much less flattering light:
“How Internet Infrastructure Works” by Jeff Tyson
This is a really interesting article that explains the underlying structure of the internet, including routers, IP addresses, the domain name system, and URLs. Most of what is said in the article wasn’t new to me, but the section on DNS servers was very informative. The description of the built-in redundancy of the system is interesting because it explains the WWW’s resiliency against hackers.
“Dismantling Integrated Library Systems” by Andrew K. Pace
This quote sums up the article really well: “Library vendors have two choices. They can continue to maintain large systems that use proprietary methods of interoperability and promise tight integration of services for their customers. Or, they can choose to dismantle their modules in such a way that librarians can reintegrate their systems through web services and standards, combining new with the old modules as well as new with each other” (36).
Whatever libraries choose, it will need to be cheap and easy use and maintain. That last requirement should be helped along by MLIS program’s increasing emphasis on technology literacy.
Wednesday, October 20, 2010
Friday, October 8, 2010
10/15 Comments
http://dougappich-informationtechnology.blogspot.com/2010/10/rifd-rifds-are-very-complicated-but.html?showComment=1286585767936#c5713789221064270943
Hi Doug, I’m curious about your claim that “circulation staff represents the human aspect of libraries.” I agree that they’re a big part of the staff/patron relationship, because, as Coyle says, they’re the people most often interacting with patrons. But like Coyle also says, checking books in and out is hardly a stimulating task – couldn’t their MLIS degrees be put to better use elsewhere in the library? Shouldn’t the “human aspect of libraries” be accomplishing something that technology can’t? I think the abilities of librarians are put to much better use when they’re helping patrons find materials, learn new technology, and access digital resources.
And I don’t think the loss of jobs is inevitable. This is probably idealistic, but my hope is that by freeing librarians from the circulation desk, they’ll be more visible and useful to patrons. Then there will be more demand for the services they offer, which would make layoffs impractical.
On Barb's Blog:
You make a good point about RFID currently having too limited applications for library use. It hadn’t occurred to me that libraries would need two checkout systems, but I guess there’d be no other choice if the RFID technology doesn’t work for all materials yet. Electronic media and children’s books are huge draws for patrons; it seems unlikely that technology complicating their circulation would be adopted by most libraries.
10/15 Reading Notes: Computer Networks, Wireless Networks
Common types of computer networks
This video brings to mind our class’s earlier discussion about about YouTube videos as learning tools. While the video does a good job of succinctly explaining types of computer networks, visually speaking it is pretty dull. The audio is useful but I’m not sure what the visual element added to the information being presented.
One of the most surprising things I’ve learned this semester is how involved Xerox has been in technological innovation. I had no idea they were involved in the development of Ethernet.
I would have been interested in a more in-depth discussion of wireless LAN, since it seems like that is the direction most institutions are going.
This article makes clear the cost cutting and efficiency benefits of a well-organized computer network. Easier communication, shared hardware and software, and information and data accessibility are all important when an institution is trying to get the most use out of their technologies without killing the budget.
I also like the discussion of wired vs. wireless technologies, which does a good job of explaining some basic ideas I had heard before but didn’t understand (like coaxial cable). Same goes for the different kinds of networks – I’d heard of intranets and extranets before, but now I know what those terms actually mean.
“Management of RFID in Libraries” by Karen Coyle
RFID is an exciting technology, but it seems unlikely that all libraries will adopt it any time soon. Though it might be cheaper in the long run, I think the initial costs are a huge deterrent with budgets being what they are now. Improving the availability of electronic resources seems to be a higher priority. Maybe a few high profile libraries using RFID technology would make it easier for others to request additional funding; or maybe this is already happening and the economy is just too bad for there to be any effect? Either way, it does seem inevitable that libraries will adopt RFID eventually. Maybe by then, it will be a little more affordable.
Thursday, October 7, 2010
Assignment #3: Epicurious Recipe Box
The video shows how to use the recipe box service of the Epicurious website, including how to save and sort recipes and how to print an ingredients list for multiple recipes at once.
To save a recipe on Epicurious, first sign in to your Epicurious account then type what sort of recipe you're looking for into the search box. A list of results will appear, and you can click on any recipe to see its instructions and ingredients. Next, click "save to recipe box" - this saves the recipe to your recipe box so you can access it later. Click "my recipe box" to access your saved recipes. From inside your box, you can sort your recipes by creating a folder and dragging and dropping in recipes. If you want to print a shopping list for all the recipes in a folder, click on the folder, then select "print shopping list."
The screenshots simply show how to build a recipe box.
Video:
Halloween_Party
Screenshots:
Screenshot 1
Screenshot 2
Screenshot 3
Screenshot 4
Screenshot 5
Friday, October 1, 2010
Week 5: Comments
http://cheyenneof2600.blogspot.com/2010/10/notes-for-unit-5-information.html?showComment=1285968046305#c485446278544859329
"Your question about the differences between MARC records and archives programs is interesting - I'm vaguely familiar with MARC, but not at all familiar with archives databases. I hope we talk about this in class!
I also didn't realize so many locks were involved in databases - still, I'm not sure I understand what they all do, exactly. Wikipedia is so helpful in pointing out what I really, really just don't know... not so helpful with explaining it"
On Melissa's blog:
http://maj66.blogspot.com/2010/09/metadata-and-dublin-core.html?showComment=1285968368285#c7845697027777251799
I agree, that definition of metadata is really illuminating. I wish the rest of the article had been so clear! I'm not at all sure what Dublin Core is, but I'm interested in the idea of standardizing metadata. The pros and cons to that tactic would be interesting to read more about.
Unit 5, Organization by Database & Metadata - Reading Notes
From a records management perspective, the discussion of object database models is very interesting. A friend of mine who works in records management is taking programming classes right now because her employer is attempting to consolidate her job with that of a database programmer. Whether or not a similar fate is in store for archivists (and librarians) is worth thinking about.
I also am intrigued by the ideas of memory management and storage topology mentioned briefly in the article. Conversations about storage requirements vs. ease of use seem to be happening across the information field; organizational methods for databases seem pertinent to such debates.
Introduction to Metadata - Setting the Stage by Anne J. Gilliland
The article has an informative explanation of archival description as it compares to the perspectives of libraries and museums towards metadata. I was also interested, but not surprised, to learn that the integration goal of MOAC has been unsuccessful. The needs of libraries, archives, and museums seem too broad to be successfully forced into one metadata system. This quote speaks well to that idea: “There is no single metadata standard that is adequate for describing all types of collections and materials; selection of the most appropriate suite of metadata standards and tools, and creation of clean, consistent metadata according to those standards, not only will enable good descriptions of specific collection materials but also will make it possible to map metadata created according to different community-specific standards, thus furthering the goal of interoperability.”
Also, I found the article’s depiction of popular metadata techniques as potentially alienating to the communities the archives is meant to serve very surprising. Of course it’s true that a typical archives user is a historian doing research, but do archives help perpetuate that norm by making it harder for people to walk in off the street and find what they’re looking for? Is there a way to make the archives more useable without disturbing their contextual integrity?
An Overview of the Dublin Core Data Model
The list of functionality requirements for the Dublin Core Data Model makes important points, I think, towards supporting diversity for broadly-encompassing metadata so that the needs of different institutions are met without impeding each other. Namespaces seem particularly useful, for example, as the word “records” has very different meanings across institutions.
I’d be interested to read more about this model, because it seems both useful and hindering in terms of meaning and the usability of the data. Hopefully we talk some about this in class.