Week 6 Readings

Local Area Network: http://en.wikipedia.org/wiki/Local_Area_Network

This reading really developed my understanding of computer network coverage systems. In my mind, LAN just silently exists in the walls of buildings, throughout cities and in the steam tunnels at MSU. HA!

The wiki's description of standard evolution is surprising in its assertion that 1983 was the "year of LAN" It's difficult to believe that networks were being developed so early in personal computer popularity terms. I was also under the impression that LANs were generally separated from one another purposefully- the discussion of largely linked LANs (say that three times fast) elaborated on the use of redundant links as a means of preventing loops and enhancing the functionality of "difficult traffic" types.

Computer network http://en.wikipedia.org/wiki/Computer_network

I enjoyed the wiki's classification of computer networks by distinct characteristic.

Particularly interesting is the discussion of coaxial cables mode of reducing inference and distortion through the inclusion of layered insulation. The wikis network type classification is also found highly interesting. College campuses, airports and office buildings are interesting examples of Local Area Networks

Common types of computer networks http://www.youtube.com/watch?v=1dpgqDdfUjQ

This link is dead.

Coyle, K. (2005). Management of RFID in libraries. Journal of Academic Librarianship, 31(5), 486-489.

Great article! Earlier in the semester Dr. He had mentioned RFID technology is class, since than I had been waiting in anticipation to hear where and how this technology would impact libraries. The uses for RFID (inventory pallets, dvds, drug labeling, pet IDs) are expansive and interesting. Coyle's discussion of the pros and cons of integrating RFID's into a library setting include attention to fiscal considerations, the possible structural and institutional gains, and the security opportunities. Her discussion of the trends in RFID technology developments draw attention to the need for libraries to decide for themselves how they will approach the new technology, if at all. Coyle makes very clear the likelihood that RFID will become a vital asset to libraries.

Week 5 Muddiest Point

I have no muddiest point for this week.

Assignment 3: Google Scholar, Zotero, Citeulike

http://www.citeulike.org/user/bbb9

Week 5 Comments

http://sregan-lis2600.blogspot.com/2009/09/unit-5-multimedia-representation-and.html?showComment=1253892593254#c2674006594503251055

http://brandonlocke.blogspot.com/2009/09/readings-week-five.html?showComment=1253893062944#c6320051811262818273

Week 5 Multimedia Representation and Storage

1. Data Compression. http://en.wikipedia.org/wiki/Data_compression

Data compression is an interesting and semi confusing topic, for me.

Compression: the process of encoding information using fewer bits than the encoding representation. Compression is used to optimize disk space.

In practice, lossless and lossy compression are easy enough to grasp.
Lossless- complete algorithem, through exploitation of statistical redundancy the data can be compressed and decompressed without change or error.
Lossy- data compression through perpetual coding. This form of compression is only acceptable when minimal data loss is acceptable.

The only past experience I have had with compression is the lossless compression of music files onto a cd. At the time, I must admit, I knew absolutly nothing considering the difference between lossless and lossy compression. I am sure that this lack of understanding resulted in some, if not all, of the aggrevation I felt while attempting to compress those music files. This may be in part due to my additional lack of understanding that for compression to be successful both the sender and reciever must both recognize the schemes being used.


2. Data compression basics (long documents, but covers all basics and beyond):
http://dvd-hq.info/data_compression_1.php

I found this article most interesting in its description of Run Length Encoding (RLE). Before reading this section, I do not believe I was able to grasp the steps of compressing data. Sensibly, Run Length encoding replaces the run (of the character) with a single digit followed by the length of the run.

3. Edward A. Galloway, “Imaging Pittsburgh: Creating a shared gateway to digital image collections of the Pittsburgh region” First Monday 9:5 2004 http://www.firstmonday.org/issues/issue9_5/galloway/index.html

This report offers an interesting glance into the process of working collaboratively on a digitization project. I found most interesting their examination of the challenges they faced in choosing a standard metadata format. I think there resolve to adopt 9 mappings in Dublin Core shows positive paths that can be taken in collaborative projects. Additionally, I like there decision to use the controlled vocabulary of LCSH. Finding common ground in a project with such a scope can be a real challenges, it sounds like they worked well to create a meaningful project.

4. Paula L. Webb, YouTube and libraries: It could be a beautiful relationship C&RL News, June 2007 Vol. 68, No. 6 0

This article discusses the ways libraries could, and have, used YouTube to spread information to their patrons, these include: instructional media, updated user information, and upcoming events.

This article raised a few questions for me, including:
1. Would individual institutions develop a formal guideline for the creation and format of their videos?
2. Who within the library would become responsible for monitoring these videos, let along producing, editing and uploading them.

I have used YouTube to share videos with my family and agree that it is a great venue for sharing. However, moving from video creation to posting does involve work..I wonder who's shoulders this would fall on.

3. Would funding for the work discussed above come out of libraries multimedia budgets, such as those for in house instructional media sessions?

Muddiest Point Week 4

I do not have a muddiest point for this week.

Week 4 Comments

http://jbullough.blogspot.com/2009/09/week-4-metadata.html?showComment=1253314750153#c1767250736088333794

http://annie-lis2600-at-pitt-blog.blogspot.com/2009/09/week-4-reading-notesr.html?showComment=1253315370095#c1761373324600106064

Week 4 Readings

I find our readings for this week, particularly Gilliand's "Introduction to Metada," to have aided me greatly in applying information technology to the field of Library science. I would like to spend the rest of this discussion post reflecting on a few of the most helpful sections.

Database (DB) Wiki

The wiki helped me to form a more concrete definition of databases. Additionally, the wiki has really aided me in understanding how collections managers use the fluidity of database architecture to enhance manageability and mobility of their collections. The components section enabled me to categorize the operations and functions of a database. I was equally enlightened by the author's description of types of DBs. I found myself reflecting on the types of DBs i have used and interacted with throughout my life: End User DB, External DB, Hypermedia. It is a very enticing feeling to perspective work on the operational end of DBs, as I have always benefited from their existence. The wiki also aided my understanding of the technical advancements in indexing and replication practices. Great wiki.

Introduction to Metadata

Anne J. Gilliland

This article was monumental in my understanding of the origins, importance, and responsibilities associated with metadata.

How is it so simply- data about data?

Her discussion of the importance of understanding the critical roles of different types of metadata as a means of ensuring access, establishing authority, and stabilizing the preservable qualities of cultural heritage, is fundamental to future information managers. I employ everyone who reads this article to think deeply on their perspective responsibilities as custodians of information. Deciding on a schema becomes increasingly vita as the plethora of object types and available data structures continue to grow exponentially. I enjoyed and benefited from her discussions of available structure standards. Her section on establishing authenticity standards speaks loudly to the increased presence of User Created Metadata (Blogs, Flicker, etc.). This article enhanced my ability to draw connections between the actions of society and the responsibility of information collectors and managers.

An Overview of the Dublin Core Data Model

Eric J. Miller

This article was more dense than the other two. DCES- Dublin Core Element Set- supports cross-disciplinary resource discovery. The most telling portion of this article is Miller's description of DCMI's functional requirements.

1. Internalization

2. Modularization

3. Element Identity

4. Semantic Refinement

5. ID of Encoding Themes

6. Specification of controlled vocab

7. ID of structured compound value

The data model insists four standards:

1. Both writer and reader must understand the the terms to mean the same thing

2. Communities may choose to utilize richer semantic definitions

3. A set of compound values are vital as the model's output will be commonly used as an authority.

4. Community themes must be clarified.

Week 3 Comments

http://brandonlocke.blogspot.com/2009/09/readings-week-three.html?showComment=1252677638195#c4262400932731410334

http://sregan-lis2600.blogspot.com/2009/09/unit-3-computer-software.html#comments

Assignment 2: Digitization/Flicker

http://www.flickr.com/photos/29273416@N03/sets/72157622314403392/

Week 1-2 Comments

Week 1:

http://bombrisk-lis2600.blogspot.com/2009/09/week-1-reading-notesmusings.html#comments

Week 2:

http://jmgb-introinfotech.blogspot.com/2009/09/week-2-reading-notes.html?showComment=1252624627568#c1936930675936033526

Week 3 Readings

1) Machtelt Garrels. “Introduction to Linux: A Hands on Guide”
http://tldp.org/LDP/intro-linux/html/

This guide to Linux is highly informative as an introduction and platform for those interested in learning more about this UNIX-type operating system. For me, the most useful sections included: What is Linux, and Current Linux Applications. Before reading this introduction, I had decidedly categorized Linux as a "programmers operating system." However, Garrells representation of Linux, as an operating system developed for simplicity, elegance, and user accessibility, has changed my mind. I find it interesting, but no longer surprising, that Linux provides service to The US Post Office and Amazon. Sensible, as Linux is widely knows for its reliability. Upon review, I find screenshots a great tool in exemplifying the user based interface developed by Linux.

2) http://www.kernelthread.com/mac/osx/
http://en.wikipedia.org/wiki/Mac_OS_X

The Kernalthread is interesting in its academic approach. The history section was both informative and an interesting example of the varied backgrounds demonstrated in the computer industry.

I find the Wiki to be more useful, particularly in it's description of Aqua. As a Mac user, I have always enjoyed the clarity and "photo realistic" icons provided by Aqua. Also, I agree with the author's assertion that iLife is one of OS X's best bundle products. In my opinion, the abilities of iLife to manage and organize stored data is unmatched.

While I was aware of the Intel transition of 2005, I was not aware of Steve Job's announcement that apple had always had Intel based versions.

3) Paul Thurott “An Update on the Windows Roadmap” http://community.winsupersite.com/blogs/paul/archive/2008/06/27/an-update-on-the-windows-roadmap.aspx

This "roadmap" is interesting due to its content, voice, and perceived audience.

Particularly interesting is Thurott's inclusion of the security enhancements available through an upgrade to Vista: "60% less likely to experience issues with MalWare, 1/2 number of vulnerabilities as experienced with Windows XP." I also find interesting his inclusion of a discussion concerning compatibality, particulalry having just

articulated that most updates were feedback driven.

Excellent readings for this week.

Week 2 Muddiest Point

I do not have a muddiest point this week.

Week 2 Readings

1) Moore's Law video:

From the video I was able to efficiently grasp the following definition of Moore's Law: Moore's Law developed out of the prediction research of Gordon Moore. Moore concluded that the number of transistors created at optimum minimal cost doubled every two years. Nicholson develops a great perspective in innovation and time, citing the development of transistor miniaturization as highly divergent in its speed, accuracy, and longevity when compared to alternative products of technology. She quickly comments on the impossibility of doubling transistors indefinitely.

I found the video to be informative and intellectually stimulating. For me, basic human explanation is always a great buttress for unfamiliar topics.

2) Moore's Law Wiki:

Unlike the video, the Wiki went into depth explaining the limits, capacity, and driving forces surrounding Moore's Law. I gained a better understanding of the limited computer aspects impacted by transistors. (45% increase in transistor= 10-20% increase in processor speed). I had previously assumed, due to lack of understanding, that transistor increase resulted in a much more positive ratio. The wiki also provided interesting comments on the driving force behind transistor miniaturization technology, citing marketing and computer engineering as being large contributors. This is an interesting additive when thinking on the impeding limits of transistor miniaturization. Will this focus shift to additional aspects of transistors once their size decrease has been achieved?

3) Computer Hardware Wiki:

I found this Wiki to be most interesting in its combination of text and image. The ability to reference the image of each component made understanding their placement, role, and composition easier to grasp. I must admit, the definitions of each component were rarely in line with my previous conceptions surrounding the purposes of each component. Additionally, there were components which I had never heard referenced, including: Chipset, Bios, and Internal Buses. While each of these components seem vital to the overall operations of the computer I am at a loss to where I previously placed their responsibility. For me, I am sure, this stems from the overall lack of knowledge of the inter workings of technology. This lack is something I hope to work on in the future.

4) Computer History Museum:

WOW!

I had no idea this museum existed! I am impressed, though not surprised, by the expanse of their online exhibit collection. Their most intriguing (and interactive) application comes in the form of how the museum has chosen to present the multiplicity of computer applications. I found the structure of this presentation highly user friendly, interactive, and filled with information. I imagine, the act of finding a balance between presenting the history of the computer, and drawing the visitors attention constitutes a real give and take. The museum looks to represent the "age of information" through varied means of user interaction including: video, voice recording, and audio series. Great museum, cant wait to visit!

Week 1 Muddiest

This week I feel the muddiest point concerns the interactive or live chat with our teaching assistant. I would have preferred that he stay for the first session of class so that any questions considering his participation could be clarified. I am still unclear as to where and how we will receive an invitation to live chat with him.

Week 1 reading notes/musings

Readings:

1) OCLC report: Information Format Trends: Content, Not Containers (2004).http://www.oclc.org/reports/2004format.htm

2) Clifford Lynch, “Information Literacy and Information Technology Literacy: New Components in the Curriculum for a Digital Culture” http://www.cni.org/staff/cliffpubs/info_and_IT_literacy.pdf

3) Vaughan, J. (2005). Lied Library @ four years: technology never stands still. Library Hi Tech, 23(1), 34-49.

http://www.emeraldinsight.com/Insight/ViewContentServlet;jsessionid=C5A0E976F56F442F9919082BF1F79360?Filename=Published/EmeraldFullTextArticle/Articles/2380230105.html

Notes:

1)OCLC report: Information Format Trends: Content, Not Containers (2004).http://www.oclc.org/reports/2004format.htm

* Interesting concept of unbundling content

Short discussion on content trends

* Legitimacy of open-source publishing, collaborative entries, e published books, journals (blogs)

* Wordpress, Movable Type

* Expanding economics of micro content

* Old content repurposing

*Portable device multimedia

* Contextual searching

While the articles partial focus is on content legitimacy it lacks a mentioning of information security. This got me thinking about the effort required in sustaining an open source publishing tool. For the user/admin the container represents a value of time and effort. How able is the user/admin able to maintain the platform? To what cost to we sacrifice legitimacy for ease of use? Discussing content as opposed to container incites a need to explore deeper the platforms for open source publishing.

2) Clifford Lynch, “Information Literacy and Information Technology Literacy: New Components in the Curriculum for a Digital Culture” http://www.cni.org/staff/cliffpubs/info_and_IT_literacy.pdf

This opinion paper draws comparison between information literacy and information technology literacy. Drawing from his varied background, Clifford Lynch develops the following summaries of these two aspects of literacy:

Info Tech Lit: Understanding of technology infrastructure, tools that allow for interaction, and the legal and social policy shaping these.

* Lynch finds two perspectives on information technology lit- skills in use of literacy tools (word, etc) and proficiency in the infrastructure.

Info Lit: Content & communication, authoring, research and findings. Variety of content: text, video, etc. Variety of purpose: education, art, etc.

* Lynch comments on the need to develop for oneself an understanding of the policy that drives information in the digital age. This notion raises interesting thoughts on information literacy education, search proficiency, and the changing state of information practices.

3) Vaughan, J. (2005). Lied Library @ four years: technology never stands still. Library Hi Tech, 23(1), 34-49.http://www.emeraldinsight.com/Insight/ViewContentServlet;jsessionid=C5A0E976F56F442F9919082BF1F79360?Filename=Published/EmeraldFullTextArticle/Articles/2380230105.html

This case study by Jason Vaughn examines the progress, challenges, and future of the Lied Library at UNLV. His discussion of the evolution of the library's systems left me completely swimming in software! Sooo..

EzProxy: Remote access (OCLC), providing access to e-information, catalogs

http://www.oclc.org/ezproxy/

DiMeMa (Digital Media Management): Organization controlling CONTENTdm. CONTENTdm allows for the storage, management, and delivery of digital collection. (http://www.oclc.org/news/releases/200633.htm).

This article from OCLC's webpage denotes their acquisition of DiMeMa.

Serial Solutions: ProQuests E-resource access, assessment, and management service. (http://www.serialssolutions.com/).

SFX: Widely used link service providing content based links for "library-defined resources"- Ex Libris (http://www.exlibris.co.il/category/SFXOverview)

Docutek ERes: E-reserve system managed by SirsiDynix. (http://www.docutek.com/products/eres/index.html)

Uniprint: Virtual printing service allowing for remote printing, networked printing, and security. (http://www.uniprint.net/home.asp).

I find Vaughn's assessment of the Lied Library as a leader in practice, planning, and infrastructure too awarding, at times. I have no doubt in the institutions position as an exemplary model for management and planning. However, Vaughn's explanation of the library's funding projects leaves much to desire. Only in the conclusion does he expand on the necessity of collaborative funding as a vital component in the library's future longevity. This absent component leaves the reader wanting for explanation of their current funding endeavors.