http://www.citeulike.org/user/hohmanms1
Hmmm...I fiddled and experimented, but still I ended up with only 28 articles in my library, even though I had 34 in my Zotero library, plus 9 from CiteULike. I don't know whether my problem was on the pre- or post-exporting side.
Tuesday, September 30, 2008
Monday, September 29, 2008
Wednesday, September 24, 2008
Week 6 Readings
Wikipedia: Local Area Network and Computer Network
I. Ways to classify networks
A. Scale
1. PAN - personal workspace (computer + printers, scanners, fax, etc.)
2. LAN - small area like a home, office, or building; usually multiple computers connected to shared external devices
3. CAN - connects LANs but in a contiguous area (college campus, military base)
4. MAN - connects LANs or CANs and covers a town/city area
5. GAN - still in the defining stages, goal of supporting mobile coverage between any number of networks
6. Internetwork - describes various types of interconnection between networks
a. Intranet - set of networks controlled by a single administrator, with only authorized participants
b. Extranet - single organization, but with limited external connections to trusted entities
c. Internet - backbone of the WWW, worldwide interconnection of networks
B. Connection Method
1. Physical Wiring connections: include Ethernet, optical fiber, etc.
2. Wireless technology: uses radio waves
C. Functional Relationship: e.g. active networking, client-server, peer-to-peer
D. Network Topology: describes logical relations of network devices (as opposed to physical network layout)
II. Basic Hardware Components
A. Network Card/Adapter/Interface Card
B. Repeaters: retransmit signals to allow a signal to cover a longer physical distance in a network
C. Hubs: copies a packet for retransmission through several ports
D. Bridges: copies traffic to several ports, but selectively (unlike hubs)
E. Switches: include routers and bridges, or other devices that distribute traffic through all or selected ports
F. Routers: use headers and forwarding tables to use the best path to forward packets between networks
Management of RFID in Libraries
It was interesting to learn about the wide variety of common technologies based on RFID. For inventory identification purposes, it is easy to see how useful this technology could be for libraries and retail store use. But it is even more worthwhile an investment in libraries, since these are unique in that inventory recirculates many times. An added function is security. Though, as the article discusses, it is not a rock-solid theft prevention method, it is no worse than other library security measure and saves money since security is a double-duty.
Yet another advantage are the saved time and money resources, especially in inventory. Not only does this technology allow several items to be scanned at once, but since no direct line of 'sight' is required, books can remain on shelves to be scanned.
Even though several disadvantages are discussed, none of them seem devastating, and I would imagine that issues such as bulky tag size will be resolved with further development of the technology.
I. Ways to classify networks
A. Scale
1. PAN - personal workspace (computer + printers, scanners, fax, etc.)
2. LAN - small area like a home, office, or building; usually multiple computers connected to shared external devices
3. CAN - connects LANs but in a contiguous area (college campus, military base)
4. MAN - connects LANs or CANs and covers a town/city area
5. GAN - still in the defining stages, goal of supporting mobile coverage between any number of networks
6. Internetwork - describes various types of interconnection between networks
a. Intranet - set of networks controlled by a single administrator, with only authorized participants
b. Extranet - single organization, but with limited external connections to trusted entities
c. Internet - backbone of the WWW, worldwide interconnection of networks
B. Connection Method
1. Physical Wiring connections: include Ethernet, optical fiber, etc.
2. Wireless technology: uses radio waves
C. Functional Relationship: e.g. active networking, client-server, peer-to-peer
D. Network Topology: describes logical relations of network devices (as opposed to physical network layout)
II. Basic Hardware Components
A. Network Card/Adapter/Interface Card
B. Repeaters: retransmit signals to allow a signal to cover a longer physical distance in a network
C. Hubs: copies a packet for retransmission through several ports
D. Bridges: copies traffic to several ports, but selectively (unlike hubs)
E. Switches: include routers and bridges, or other devices that distribute traffic through all or selected ports
F. Routers: use headers and forwarding tables to use the best path to forward packets between networks
Management of RFID in Libraries
It was interesting to learn about the wide variety of common technologies based on RFID. For inventory identification purposes, it is easy to see how useful this technology could be for libraries and retail store use. But it is even more worthwhile an investment in libraries, since these are unique in that inventory recirculates many times. An added function is security. Though, as the article discusses, it is not a rock-solid theft prevention method, it is no worse than other library security measure and saves money since security is a double-duty.
Yet another advantage are the saved time and money resources, especially in inventory. Not only does this technology allow several items to be scanned at once, but since no direct line of 'sight' is required, books can remain on shelves to be scanned.
Even though several disadvantages are discussed, none of them seem devastating, and I would imagine that issues such as bulky tag size will be resolved with further development of the technology.
Monday, September 22, 2008
Thursday, September 18, 2008
Week 5 Muddiest Point
I sure this must have been addressed in the readings somewhere, but I either missed it or the explanation went over my head. I don't quite understand where compression and decompression occurs. Are the programs in charge of this part of the individual OS? Are they in the computer's hardware or in software? Are instructions for "rehydrating" files tacked on to the files themselves somehow, or are they recognizable and assumed by the computer? Sorry to use such remedial language...
Week 5 Ctd...
Imaging Pittsburgh
It was nice to see a real-life application of many of the things we've been learning about. The overview of the various challenges the team faced in communication and in how they viewed the items in the collection. In the end, it was probably an advantage because the situation will be the same on the users' end - people will be searching the databases for different criteria and with different interests.
YouTube and Libraries
Sounds like a decent idea in theory - why not take advantage of a service that's so simple to use... and free. But would people actually use it for purposes such as these? I have never known anyone that used YouTube for anything other than purely recreational and largely mindless reasons.
It was nice to see a real-life application of many of the things we've been learning about. The overview of the various challenges the team faced in communication and in how they viewed the items in the collection. In the end, it was probably an advantage because the situation will be the same on the users' end - people will be searching the databases for different criteria and with different interests.
YouTube and Libraries
Sounds like a decent idea in theory - why not take advantage of a service that's so simple to use... and free. But would people actually use it for purposes such as these? I have never known anyone that used YouTube for anything other than purely recreational and largely mindless reasons.
Wednesday, September 17, 2008
Week 5 Readings
Wikipedia: Data Compression
I really enjoyed this read, partly because I wasn't utterly lost reading it!
When I read about how "lossless compression algorithms usually exploit statistical redundancy", and later: "any compression algorithm will necessarily fail to compress any data containing no discernible patterns", I first generalized that these types of algorithms could be used to compress language (words) but not number data. But in actuality, numerical data is by no means random. It should even be predictable to some extent, depending on what it is describing. The article mentioned the ability to find patterns in numbers themselves, such as repeating digits. But are there algorithms that recognize the probability of certain patterns occuring for data that describes weather vs. test scores vs. race times, for example?
It also caught my attention to find that the study of rate-distortion theory was so old - dating to the very earliest days of the computer era - and the linked articles about Claude Shannon were especially interesting.
Data Compression Basics
I had so many "aha" moments reading this article! I am pretty remedial when it comes to computer matters, but readings like this help establish so many new connections in my brain. For instance, I knew nothing about what file extensions meant, except for the frustration they could cause me when trying to open them with incompatible programs. Now I understand that the extension basically indicates how the file is to be decompressed, which explains the ghastly stings of unreadable code that can appear when I open a file with the wrong application (if the file opens at all)
This also helped to really break down what audio, stills, and video data looks like at a fundamental level, and therefore why so many different compression methods are needed.
By far the most informative and enjoyable read so far - I even liked the writing style and subtle British humor.
Other articles and Muddiest Point to follow...
I really enjoyed this read, partly because I wasn't utterly lost reading it!
When I read about how "lossless compression algorithms usually exploit statistical redundancy", and later: "any compression algorithm will necessarily fail to compress any data containing no discernible patterns", I first generalized that these types of algorithms could be used to compress language (words) but not number data. But in actuality, numerical data is by no means random. It should even be predictable to some extent, depending on what it is describing. The article mentioned the ability to find patterns in numbers themselves, such as repeating digits. But are there algorithms that recognize the probability of certain patterns occuring for data that describes weather vs. test scores vs. race times, for example?
It also caught my attention to find that the study of rate-distortion theory was so old - dating to the very earliest days of the computer era - and the linked articles about Claude Shannon were especially interesting.
Data Compression Basics
I had so many "aha" moments reading this article! I am pretty remedial when it comes to computer matters, but readings like this help establish so many new connections in my brain. For instance, I knew nothing about what file extensions meant, except for the frustration they could cause me when trying to open them with incompatible programs. Now I understand that the extension basically indicates how the file is to be decompressed, which explains the ghastly stings of unreadable code that can appear when I open a file with the wrong application (if the file opens at all)
This also helped to really break down what audio, stills, and video data looks like at a fundamental level, and therefore why so many different compression methods are needed.
By far the most informative and enjoyable read so far - I even liked the writing style and subtle British humor.
Other articles and Muddiest Point to follow...
Monday, September 15, 2008
Comments: Week 4
https://www.blogger.com/comment.g?blogID=854093220520038877&postID=174628254612469280&page=1
https://www.blogger.com/comment.g?blogID=2369947867373070193&postID=7977490293481423923&page=1
https://www.blogger.com/comment.g?blogID=2369947867373070193&postID=7977490293481423923&page=1
Friday, September 12, 2008
Week 4 Readings and Muddiest Point
Wikipedia: Database
This article was very helpful to me in that it set forth basic principles that I sort of grasped instinctively about databases without having the knowledge to articulate it. For instance, the DBMS ideals of atomicity, consistency, isolation, and durability make perfect sense, but I wouldn't have been able to put my finger on them just through observation. Of the three basic database models - hierarchical, network, and relational - I am still having trouble making a solid mental image of a relational model.
Metadata
The concept of "data about data" blew my mind until I read on to some of the examples. It is still a little treacherous that the term has quite different connotations in different times and fields.
Soo...is metadata what is contained within a database? Or is 'metadata' a term interchangeable with 'database'?
Dublin Core Data Model
Ambitious. I may have missed the target, but is the goal here a universally standardized world database? Is this even possible in theory? I guess I never realized how far we are from being able to collaborate worldwide on any topic.
Muddiest Point:
I think I understand a lot more about databases after these readings, but I am still having trouble visualizing the models, or coming up with concrete examples. Do all models fall into one of the three given categories, or are there major variations?
This article was very helpful to me in that it set forth basic principles that I sort of grasped instinctively about databases without having the knowledge to articulate it. For instance, the DBMS ideals of atomicity, consistency, isolation, and durability make perfect sense, but I wouldn't have been able to put my finger on them just through observation. Of the three basic database models - hierarchical, network, and relational - I am still having trouble making a solid mental image of a relational model.
Metadata
The concept of "data about data" blew my mind until I read on to some of the examples. It is still a little treacherous that the term has quite different connotations in different times and fields.
Soo...is metadata what is contained within a database? Or is 'metadata' a term interchangeable with 'database'?
Dublin Core Data Model
Ambitious. I may have missed the target, but is the goal here a universally standardized world database? Is this even possible in theory? I guess I never realized how far we are from being able to collaborate worldwide on any topic.
Muddiest Point:
I think I understand a lot more about databases after these readings, but I am still having trouble visualizing the models, or coming up with concrete examples. Do all models fall into one of the three given categories, or are there major variations?
Monday, September 8, 2008
Friday, September 5, 2008
Week 3 Readings
Linux: completely new to me, so I found this article particularly intriguing. If Linux was the result of the first attempt at a standardized operating system, I wonder how the development of other OS's paralleled it, and when and why they began to surpass Linux in popularity. What I got from the readings was that it was because the other OS's seem to put their focus on user-friendliness and customer appeal.
I also found it interesting that anyone with Linux has the ability to further develop/alter the programming (if I understand correctly) I wonder how far these manipulations can be taken and if the system can even become unrecognizable from the original "kernel".
[kernelthread] Wow...I just couldn't much beyond the introduction, history and conclusion. As soon as I got into the "meat" of the article, I was tempted to just skip this reading altogether. I moved on to the Wikipedia article, which felt like a walk in the park - almost too un-technical as it seemed to dwell mainly on basic features and appearance. But this helped a lot when I revisited the kernelthread reading; I was able to digest more than I thought I could.
What I do know is...I love my Mac!
I also found it interesting that anyone with Linux has the ability to further develop/alter the programming (if I understand correctly) I wonder how far these manipulations can be taken and if the system can even become unrecognizable from the original "kernel".
[kernelthread] Wow...I just couldn't much beyond the introduction, history and conclusion. As soon as I got into the "meat" of the article, I was tempted to just skip this reading altogether. I moved on to the Wikipedia article, which felt like a walk in the park - almost too un-technical as it seemed to dwell mainly on basic features and appearance. But this helped a lot when I revisited the kernelthread reading; I was able to digest more than I thought I could.
What I do know is...I love my Mac!
Thursday, September 4, 2008
Week 2 Readings
These readings complemented each other very well; I tabbed back and forth between them. The subject matter this week well beyond my area of expertise, so my notes this week are basic outlines to aid myself in getting the material straight.
Computer Hardware (the Guts)
I. Motherboard
-CPU (brain)
-internal buses (connect internal components)
-external bus controllers (connect to external devices)
II. Power Supply
-converts AC to low-voltage DC power, includes cooling fan
III. Removable media devices
-include CDs, DVD, blu-ray discs, and others
IV. Internal storage
-hard drive
V. Sound and Graphics cards
VI. Networking
-modem, other internet connections
VII. Input and output devices include:
-keyboard, mouse, game controllers, scanner, microphone, webcam
-printer, monitor, speakers
Moore's Law
Exploring some of the linked articles (esp. transistors) was well worth the extra time - things made much more sense to me with the aid of some background info.
I. History
-a few similar predictions prior to Moore's Law
-1965: Moore's orginal observation of transistor count doubling every year
-1970: term "Moore's Law" coined
-1975: projection altered to doubling every two years
II. Areas of similar growth
-number of transistors per integrated circuit
-rate of increase of transistor density at minimized cost
-cost per transistor
-manufacturing costs have gone up, however (not sure I understand this)
-transistor speed per cost unit
-power consumption (closer to Moore's original rate)
III. Moore's law evolved from an observation of an existing trend into a goal for the pace of these technological advances
IV. The future and limits of the law
-remember, originally only referred to semiconductor circuits. many have broadened the usage to describe many other technologies
-expected to continue for anywhere from a couple decades to several centuries (?!) by a few speculators.
-ultimately, transistors built on the atomic scale (necessary stopping point)
Computer History Museum
The Computer History Timeline was a good (non-technical) supplement to the Moore's Law article. I found the Internet History Exhibit quite interesting as well.
Computer Hardware (the Guts)
I. Motherboard
-CPU (brain)
-internal buses (connect internal components)
-external bus controllers (connect to external devices)
II. Power Supply
-converts AC to low-voltage DC power, includes cooling fan
III. Removable media devices
-include CDs, DVD, blu-ray discs, and others
IV. Internal storage
-hard drive
V. Sound and Graphics cards
VI. Networking
-modem, other internet connections
VII. Input and output devices include:
-keyboard, mouse, game controllers, scanner, microphone, webcam
-printer, monitor, speakers
Moore's Law
Exploring some of the linked articles (esp. transistors) was well worth the extra time - things made much more sense to me with the aid of some background info.
I. History
-a few similar predictions prior to Moore's Law
-1965: Moore's orginal observation of transistor count doubling every year
-1970: term "Moore's Law" coined
-1975: projection altered to doubling every two years
II. Areas of similar growth
-number of transistors per integrated circuit
-rate of increase of transistor density at minimized cost
-cost per transistor
-manufacturing costs have gone up, however (not sure I understand this)
-transistor speed per cost unit
-power consumption (closer to Moore's original rate)
III. Moore's law evolved from an observation of an existing trend into a goal for the pace of these technological advances
IV. The future and limits of the law
-remember, originally only referred to semiconductor circuits. many have broadened the usage to describe many other technologies
-expected to continue for anywhere from a couple decades to several centuries (?!) by a few speculators.
-ultimately, transistors built on the atomic scale (necessary stopping point)
Computer History Museum
The Computer History Timeline was a good (non-technical) supplement to the Moore's Law article. I found the Internet History Exhibit quite interesting as well.
Monday, September 1, 2008
Information Literacy and Information Technology Literacy
Beginning on the second page of the article, Lynch elaborated on the two basic views on what information technology literacy means (oversimplified: skills vs. theory). This is not exactly what the focus of the article, but it did make me wonder:
We are gaining access to rapidly advancing technologies and can learn how to use them skillfully and efficiently without having any literacy in the technology itself.
Certainly, this is not true exclusively for the present; this statement could be applied to people and advancements in the past. Early humans did not understand scientifically what fire was and how it worked, yet they learned to create and manipulate it for their use. I do not have full understanding of how a car works, yet I can use one proficiently.
Does the average consumer/user of today's technologies have a lower level of literacy than in
previous times? How much of a problem (if any) is this illiteracy?
Beginning on the second page of the article, Lynch elaborated on the two basic views on what information technology literacy means (oversimplified: skills vs. theory). This is not exactly what the focus of the article, but it did make me wonder:
We are gaining access to rapidly advancing technologies and can learn how to use them skillfully and efficiently without having any literacy in the technology itself.
Certainly, this is not true exclusively for the present; this statement could be applied to people and advancements in the past. Early humans did not understand scientifically what fire was and how it worked, yet they learned to create and manipulate it for their use. I do not have full understanding of how a car works, yet I can use one proficiently.
Does the average consumer/user of today's technologies have a lower level of literacy than in
previous times? How much of a problem (if any) is this illiteracy?
Week I Readings
Information Format Trends: Content, not Containers
Although the purpose of this article seems to be to set forth statistics and point out trends in information accessibility in a very straightforward manner, it automatically raises questions and brings up issues along the way. It is not hard to observe that information is becoming more portable and instantly accessible to the individual. It is not a impossible to imagine libraries, at least in their current roles, becoming less popular, relevant, or useful. The question that came up to me as I read was on the role of the librarian and how this role might ever be filled virtually/digitally. The article finally hints at this issue on p. 14. As a topic for personal research, I would like to find out:
- what types of more sophisticated programs already exist that help to map out available information in a more useful way than just searching for some keywords
- what is the predicted trend for these programs: Is there a virtual replacement for the librarian?
Although the purpose of this article seems to be to set forth statistics and point out trends in information accessibility in a very straightforward manner, it automatically raises questions and brings up issues along the way. It is not hard to observe that information is becoming more portable and instantly accessible to the individual. It is not a impossible to imagine libraries, at least in their current roles, becoming less popular, relevant, or useful. The question that came up to me as I read was on the role of the librarian and how this role might ever be filled virtually/digitally. The article finally hints at this issue on p. 14. As a topic for personal research, I would like to find out:
- what types of more sophisticated programs already exist that help to map out available information in a more useful way than just searching for some keywords
- what is the predicted trend for these programs: Is there a virtual replacement for the librarian?
Subscribe to:
Posts (Atom)
