Here is the link to my image collection. Unfortunately, I missspelled "tomato" in my tags...
http://www.flickr.com/photos/dalittleneon/
Sunday, September 26, 2010
Saturday, September 25, 2010
9/25 Comments
Discussion Board: Technical Discussion
It is supposed to be Assignment 3 for Unit 4 (Sept. 27) it just was not changed when the weeks were switched. If you check the Course Documents it has it listed as Assignment 3. The assignment will be discussed in class Monday Sept. 27th.
Assignent 4 will be discussed in class on October 4th.
Hope that helps.
Blogger
tp://jsslis2600.blogspot.com/2010/09/week-3-muddiest-point.html?showComment=1285374788721#c4387872630135102044
It is supposed to be Assignment 3 for Unit 4 (Sept. 27) it just was not changed when the weeks were switched. If you check the Course Documents it has it listed as Assignment 3. The assignment will be discussed in class Monday Sept. 27th.
Assignent 4 will be discussed in class on October 4th.
Hope that helps.
Blogger
tp://jsslis2600.blogspot.com/2010/09/week-3-muddiest-point.html?showComment=1285374788721#c4387872630135102044
Unit 5? Reading Notes
Unfortunately, I read the required readings for next week and not this week. I printed out the readings, read the email, read the heading on the unit and thought I had the right readings until just now when I rechecked and realized there were four readings listed instead of the original three. I will try and get the reading notes for this week posted as soon as I can. In the mean time, here are the reading notes for next week.
Gilliland's Metadata
While I have heard of metadata before, it was mostly descriptive metadata that I was familiar with so it surprised me to see all of its other functions. I do not quite comprehend the types of data standards but found the tables listing the types, functions, and attributes and characteristics very informative. I also liked this article because it applied directly to libraries and archives which helped me to understand the other articles.
Miller's DCDM
It took me a bit to get past some of the jargon and the "simple examples" I could see how this article directly applied to the first one. Basically, everything has metadata but everyone will use different metadata to describe each object. The DCMI is trying to find ways to overcome this by first identifying some of the issues that need to be overcome (language, definitions, specificity, etc) and then finding what is needed to overcome this so that metadata is more easily searchable. I found the conclusion a bit lacking.
Wiki's Database
This was one of those great articles that takes something I thought I knew and upon reading it makes me realize that I have no idea what I am talking about. I can see a connection between databases and metadata specifically in the section Indexing. Indexing is used to make running a query more efficient which, in turn, requires the input of metadata as well as the searching of metadata to find results. One thing I am confused with about this article is that I can quite figure out what a database is "physically" in a computer. Is it a form of software, is it on the hard drive, etc...
Gilliland's Metadata
While I have heard of metadata before, it was mostly descriptive metadata that I was familiar with so it surprised me to see all of its other functions. I do not quite comprehend the types of data standards but found the tables listing the types, functions, and attributes and characteristics very informative. I also liked this article because it applied directly to libraries and archives which helped me to understand the other articles.
Miller's DCDM
It took me a bit to get past some of the jargon and the "simple examples" I could see how this article directly applied to the first one. Basically, everything has metadata but everyone will use different metadata to describe each object. The DCMI is trying to find ways to overcome this by first identifying some of the issues that need to be overcome (language, definitions, specificity, etc) and then finding what is needed to overcome this so that metadata is more easily searchable. I found the conclusion a bit lacking.
Wiki's Database
This was one of those great articles that takes something I thought I knew and upon reading it makes me realize that I have no idea what I am talking about. I can see a connection between databases and metadata specifically in the section Indexing. Indexing is used to make running a query more efficient which, in turn, requires the input of metadata as well as the searching of metadata to find results. One thing I am confused with about this article is that I can quite figure out what a database is "physically" in a computer. Is it a form of software, is it on the hard drive, etc...
Saturday, September 18, 2010
9/12-9/18 Comments
I also made the following comment in the Technical Discussion Board:
"Basically, the file you upload onto your computer is you master copy.
The screen copy the version of the picture that will fit onto your entire screen like a desktop background. In you don't know what your screen resolution is right click on your desktop background, then click on properties, and then settings. Mine for instance is at 1024X768 pixels. You are going to need to resize your master copy to be the same size as your desktop background.
Thumbnails can be made the same way you make a screen copy, by just resizing the image in either Paint or Photoshop or whatever you prefer.
If you are using Paint, you can adjust the picture size by clicking Image and then Stretch/Skew. I personally don't like this if you need an exact image size because it resizes by percentage and not measurement. If you need to know the pixel size of your image in Paint, click and drag the tiny blue dot at the bottom right corner of your screen. A box in the bottom right corner of your screen (just above the clock) will display the image size in pixels. This is also used to adjust the canvas size. Also, if you image is longer than it is wide, you may want to rotate it, otherwise it will be fat when you resize it to screen size. Do do this in Paint go to Image, then Flip/Rotate, click on By Angle, and then select either 90 degrees or 270 depending on which way you want the image to lie.
Unfortunately I dont have Photoshop on my computer but adjusting the image size is even simpler in there. I think you go to Edit, Adjust Canvas (or image) Size and then you can simply type in the pixel size you want.
I hope that helps and if any of these explanations are wrong or you think are wrong please feel free to correct me (I don't want the entire class to get it wrong!)"
"Basically, the file you upload onto your computer is you master copy.
The screen copy the version of the picture that will fit onto your entire screen like a desktop background. In you don't know what your screen resolution is right click on your desktop background, then click on properties, and then settings. Mine for instance is at 1024X768 pixels. You are going to need to resize your master copy to be the same size as your desktop background.
Thumbnails can be made the same way you make a screen copy, by just resizing the image in either Paint or Photoshop or whatever you prefer.
If you are using Paint, you can adjust the picture size by clicking Image and then Stretch/Skew. I personally don't like this if you need an exact image size because it resizes by percentage and not measurement. If you need to know the pixel size of your image in Paint, click and drag the tiny blue dot at the bottom right corner of your screen. A box in the bottom right corner of your screen (just above the clock) will display the image size in pixels. This is also used to adjust the canvas size. Also, if you image is longer than it is wide, you may want to rotate it, otherwise it will be fat when you resize it to screen size. Do do this in Paint go to Image, then Flip/Rotate, click on By Angle, and then select either 90 degrees or 270 depending on which way you want the image to lie.
Unfortunately I dont have Photoshop on my computer but adjusting the image size is even simpler in there. I think you go to Edit, Adjust Canvas (or image) Size and then you can simply type in the pixel size you want.
I hope that helps and if any of these explanations are wrong or you think are wrong please feel free to correct me (I don't want the entire class to get it wrong!)"
Readings for 9/20
I had a difficult time getting through the technical jargon in some of these articles but could find some key points that may pertain to libraries. For the most part, operating systems are constantly trying to tweak and improve and are evolving at incredible speeds (such as the Mac OS X having 6 versions in 10 years.) This can be confusing or frustrating for your average person. While most people can cope with change, they don't like to deviate from routines. In a library setting, you will have users who are up-to-date with all the latest versions and some who only update when their current computer needs replacing or the version they copied onto their floppy disk will not run on the library computers. While most patrons may only speak "Windows", you will also have Mac users and maybe even a Linux user needing help. If a library is struggling to keep up-to-date with the one operating system installed on their public computers, how do they keep on top of all other systems?
Mac OS X Article and Wiki
Oddly enough, I found the Singh explanation of Mac OS X easier to understand than the Wiki article despite the warning that it was full of technical jargon. The Wiki article was insightful in showing just how often OSs are updating to make way for new evolutions in technology and programing. It mentions, as other articles do as well, that newer versions do not work on "older" machines. What is "old" for an operating system? The Singh introduction does explain that backwards compatibility can contribute to "malice and malfunction" so it is understandable. Unfortunately, I think it contributes to our "disposable culture" and giving our commodities ever shorter shelf lives. The Singh introduction also has the best explanation as to why Windows is more popular as an OS than Linux or even Mac. The average user wants to read the picture book version rather than take the time to read and comprehend the novel. While users do want systems that they can tailor to their liking, they also want to keep it simple. Canned spaghetti sauce may not taste like Momma's but it is a lot cheaper and easier to make and you can still add meat and peppers.
Garrels Linux
Again, technical jargon confused me with this book but toward the end I think I was starting to understand things (scary!) Linux is the DIY of operating systems in basic terms. It sounds like it could be the most user-friendly if the user knows what he or she is doing. These users are like a large group of beta-testers except more public(someone who tests a product for weaknesses): if the software is not to their liking, they change it so that the next user does not run into the same problem. The article mentions that a pro of Linux is "free speech" which makes me wonder what copyright restrictions there are on Linux software.
Thurott Windows
I'm slightly bias with this article because I like XP and do not like Vista. Like the earlier article, it too mentions how new systems are not compatible with "very old" devices. Again, what is "very old" in computer terms? Compatibility is an issue that is brought up in this article and I think that is relevant to both users and libraries. It takes time to get the kinks worked out, obviously, but there are situations where you need them to work now. For example, at my library our print release program does not work with Vista thus the two computers that run Vista tend to be our biggest paper wasters because people either don't pick up their print jobs or end up printing multiple copies because they don't know why they are not getting the normal print release screen. Subsequently, how can a library stay on top of individual pieces of technology when their other pieces of technology can't stay on top?
Mac OS X Article and Wiki
Oddly enough, I found the Singh explanation of Mac OS X easier to understand than the Wiki article despite the warning that it was full of technical jargon. The Wiki article was insightful in showing just how often OSs are updating to make way for new evolutions in technology and programing. It mentions, as other articles do as well, that newer versions do not work on "older" machines. What is "old" for an operating system? The Singh introduction does explain that backwards compatibility can contribute to "malice and malfunction" so it is understandable. Unfortunately, I think it contributes to our "disposable culture" and giving our commodities ever shorter shelf lives. The Singh introduction also has the best explanation as to why Windows is more popular as an OS than Linux or even Mac. The average user wants to read the picture book version rather than take the time to read and comprehend the novel. While users do want systems that they can tailor to their liking, they also want to keep it simple. Canned spaghetti sauce may not taste like Momma's but it is a lot cheaper and easier to make and you can still add meat and peppers.
Garrels Linux
Again, technical jargon confused me with this book but toward the end I think I was starting to understand things (scary!) Linux is the DIY of operating systems in basic terms. It sounds like it could be the most user-friendly if the user knows what he or she is doing. These users are like a large group of beta-testers except more public(someone who tests a product for weaknesses): if the software is not to their liking, they change it so that the next user does not run into the same problem. The article mentions that a pro of Linux is "free speech" which makes me wonder what copyright restrictions there are on Linux software.
Thurott Windows
I'm slightly bias with this article because I like XP and do not like Vista. Like the earlier article, it too mentions how new systems are not compatible with "very old" devices. Again, what is "very old" in computer terms? Compatibility is an issue that is brought up in this article and I think that is relevant to both users and libraries. It takes time to get the kinks worked out, obviously, but there are situations where you need them to work now. For example, at my library our print release program does not work with Vista thus the two computers that run Vista tend to be our biggest paper wasters because people either don't pick up their print jobs or end up printing multiple copies because they don't know why they are not getting the normal print release screen. Subsequently, how can a library stay on top of individual pieces of technology when their other pieces of technology can't stay on top?
Friday, September 17, 2010
Weeks 1 and 2 Comments
I know it is not necessary but I wanted to post my earlier comments to see if I can copy and paste them from a word document. I thought I had more from Week 1 but I could not locate them...
September 3
September 11
Saturday, September 11, 2010
Week 2 Reading Notes
Wiki: Personal Computer Hardware
This article was a bit of a wake up call for me. I did not realise how much and how little I knew about personal computers. Many of the components mentioned in the article were things that I knew about and had a rough definition for but for the most part I did not really know what they did, what it meant, or what it was for. For instance, I knew that a DVD was a type of CD but because I've always associated it with movies I never made the connection that it was a CD just with more storage capacity (nor did I know it stood for digital versatile disc which rather ironic because previously I associated the term CD or disc with more versatile functions than DVD.) Being a wiki article, I found the links very helpful as well for allowing me to further learn about each component as well as to get specific definitions of things I previously took for granted.
Moore's Law: Wiki and Video
I think Christie Nicholson in the video described it best when she said that Moore's Law is not really a law but more of a "technological trend." The exponential doubling has become more of a goal rather than a rule. This seems to have been quite beneficial over the past 40 years because it has motivated us to take great leaps in computing hardware. Will it last forever, most agree the answer is "no." However, that doesn't mean that we will stop building faster computers. As the transistor replaced the vacuum tube (1947-computer history museum website) is it possible that we may need to look for replacements for the transistor in the future? One concern about Moore's Law I have from reading the wiki is whether or not the need for quantity over quality will eventually affect its sustainability. Under the subheading "Density at minimum cost per transistor" the article says that the need to sustain Moore's Law leads to an increase in defects. Do we allow ourselves time to iron out these defects before another another increase has occurred? If not, will these defects eventually add up making it more difficult to produce a quality product?
Computer History Museum
This was a fun website to explore. Oddly enough when I first visited the site I thought it was a digital museum because of all the information on it. While I am sure there are many computer enthusiasts who would love to go to the actual museum, not being much of a tech. buff, I think the website may be a bit more informative for me. The timelines were the most informative part of the website (although I am a bit perturbed that they consider anything before 1940 "ancient") because it helped to put the history of computers into perspective; something that is becoming increasingly harder to do in my opinion as computers become more and more a part of our daily lives (like the person who wonders why there are no photographs of George Washington.)
This article was a bit of a wake up call for me. I did not realise how much and how little I knew about personal computers. Many of the components mentioned in the article were things that I knew about and had a rough definition for but for the most part I did not really know what they did, what it meant, or what it was for. For instance, I knew that a DVD was a type of CD but because I've always associated it with movies I never made the connection that it was a CD just with more storage capacity (nor did I know it stood for digital versatile disc which rather ironic because previously I associated the term CD or disc with more versatile functions than DVD.) Being a wiki article, I found the links very helpful as well for allowing me to further learn about each component as well as to get specific definitions of things I previously took for granted.
Moore's Law: Wiki and Video
I think Christie Nicholson in the video described it best when she said that Moore's Law is not really a law but more of a "technological trend." The exponential doubling has become more of a goal rather than a rule. This seems to have been quite beneficial over the past 40 years because it has motivated us to take great leaps in computing hardware. Will it last forever, most agree the answer is "no." However, that doesn't mean that we will stop building faster computers. As the transistor replaced the vacuum tube (1947-computer history museum website) is it possible that we may need to look for replacements for the transistor in the future? One concern about Moore's Law I have from reading the wiki is whether or not the need for quantity over quality will eventually affect its sustainability. Under the subheading "Density at minimum cost per transistor" the article says that the need to sustain Moore's Law leads to an increase in defects. Do we allow ourselves time to iron out these defects before another another increase has occurred? If not, will these defects eventually add up making it more difficult to produce a quality product?
Computer History Museum
This was a fun website to explore. Oddly enough when I first visited the site I thought it was a digital museum because of all the information on it. While I am sure there are many computer enthusiasts who would love to go to the actual museum, not being much of a tech. buff, I think the website may be a bit more informative for me. The timelines were the most informative part of the website (although I am a bit perturbed that they consider anything before 1940 "ancient") because it helped to put the history of computers into perspective; something that is becoming increasingly harder to do in my opinion as computers become more and more a part of our daily lives (like the person who wonders why there are no photographs of George Washington.)
Friday, September 3, 2010
Week 1 Muddies
1) Because I am new to Blogger and RSS Feeds I am a little unsure of how they work. Do I need to subscribe to everyone's RSS Feed (~60 students) and is there a way to sort through their posts (or do I read through 60+ posts in my dashboard each week?) Also, is there a way of tracking the comments that I have made to other posts (this is something that irks me about LiveJournal in that I cant track my own comments to other posts.) 2) It was mentioned in class that we generally have two weeks to complete an assignment. Would it be safe to guess that in the syllabus where it says "Assignment X is out" that the assignment will be due about two weeks afterwards? The only reason I ask is because I have to schedule my Saturdays for work.
3) As others have mentioned in their muddies, I too am interested in learning a bit more about teh DIKW Hierarchy. If you look up information, knowledge, and wisdom in the dictionaries you find that the words act as synonyms which makes finding the distictincion between the words difficult. It also doesn't help that the concepts become more abstract as you go higher up the pyramid.
That's about it for this week. I don't know if the second one really counts as a muddy but I suppose seen as the first lecture was about the basics of the class that it may count this week.
~ Jessica
3) As others have mentioned in their muddies, I too am interested in learning a bit more about teh DIKW Hierarchy. If you look up information, knowledge, and wisdom in the dictionaries you find that the words act as synonyms which makes finding the distictincion between the words difficult. It also doesn't help that the concepts become more abstract as you go higher up the pyramid.
That's about it for this week. I don't know if the second one really counts as a muddy but I suppose seen as the first lecture was about the basics of the class that it may count this week.
~ Jessica
Week 1 Reading Notes
Content Not Containers
There were several points brought up in this article that I found interesting. The fact that consumers are "format agnostic" is rather intriguing. I would assume that users would have preferred formats but apparently certain factors, such as cost as the paper notes, override those preferences. Also, while it is true that books are no longer the "sacred objects" and text is no longer the only medium, it is obvious that many of our electronic devices still rely on text as the vehicle for information communication.
I am a little unsure about the research done comparing email and ILL requests (p. 4-5.) The paper does not make the distinction between types of email that is sent. ILL is specifically requested content. Email is both response for requested content and unsolicited information. However, even if you only count email with requested content, I would assume the number would still be quite significant when compared to the number of ILL requests.
Overall the article points to changes in how consumers conduct their lives both personally and academically. How they obtain and produce information is changing and, not only does this affect all libraries but it has them worried. One of the most important parts of this article from a libraries perspective, I believe come from the last few paragraphs. They say we are drowning in information but starving for knowledge and that also applies to our overabundance of content and lack of context. Libraries need to look at these two issues and find out how they can become solutions to those problems.
Information Literacy and Information Technology Literacy
One thing in particular that I found interesting in this article is the author's thoughts on skills not being enough. This is the opposite of what I have been taught before as in many classes I have heard "You do not need to know why this happens unless you choose to study this further on in your education; just accept that it does." However, the author's points as to why this is wrong are quite valid. If you don't understand why technology works it becomes harder to both adapt to and, perhaps more importantly, predict change. Sometimes you need to learn how to learn before you can learn.
This applies to the issues brought up in the first article concerning the libraries role. The more that they understand these systems, the more they will be able to understand consumers and how they can help their users.
Lied Library
While most of this article bogged me down with names and abbreviations I did not understand, the overall message was one that any library worker should understand. Being on top of information technology is only part of the equation. A knowledgeable staff is the other. Working in a library where being under the age of 30 qualifies you as a "computer professional" I understand how important it is to have a knowledgeable staff not just for helping patrons but also for keeping the building running. Reading the article reiterates the message from the second article where it is not just enough anymore to know a set of skills.
There were several points brought up in this article that I found interesting. The fact that consumers are "format agnostic" is rather intriguing. I would assume that users would have preferred formats but apparently certain factors, such as cost as the paper notes, override those preferences. Also, while it is true that books are no longer the "sacred objects" and text is no longer the only medium, it is obvious that many of our electronic devices still rely on text as the vehicle for information communication.
I am a little unsure about the research done comparing email and ILL requests (p. 4-5.) The paper does not make the distinction between types of email that is sent. ILL is specifically requested content. Email is both response for requested content and unsolicited information. However, even if you only count email with requested content, I would assume the number would still be quite significant when compared to the number of ILL requests.
Overall the article points to changes in how consumers conduct their lives both personally and academically. How they obtain and produce information is changing and, not only does this affect all libraries but it has them worried. One of the most important parts of this article from a libraries perspective, I believe come from the last few paragraphs. They say we are drowning in information but starving for knowledge and that also applies to our overabundance of content and lack of context. Libraries need to look at these two issues and find out how they can become solutions to those problems.
Information Literacy and Information Technology Literacy
One thing in particular that I found interesting in this article is the author's thoughts on skills not being enough. This is the opposite of what I have been taught before as in many classes I have heard "You do not need to know why this happens unless you choose to study this further on in your education; just accept that it does." However, the author's points as to why this is wrong are quite valid. If you don't understand why technology works it becomes harder to both adapt to and, perhaps more importantly, predict change. Sometimes you need to learn how to learn before you can learn.
This applies to the issues brought up in the first article concerning the libraries role. The more that they understand these systems, the more they will be able to understand consumers and how they can help their users.
Lied Library
While most of this article bogged me down with names and abbreviations I did not understand, the overall message was one that any library worker should understand. Being on top of information technology is only part of the equation. A knowledgeable staff is the other. Working in a library where being under the age of 30 qualifies you as a "computer professional" I understand how important it is to have a knowledgeable staff not just for helping patrons but also for keeping the building running. Reading the article reiterates the message from the second article where it is not just enough anymore to know a set of skills.
Subscribe to:
Posts (Atom)