And here are my not-so-snarky comments. I must be losing my touch.
http://kel2600.blogspot.com/2010/10/reading-notes-october-26-2010.html?showComment=1288360333538#c7556786525865943506
I'll see what else I can come up with as time goes on. . .
Friday, October 29, 2010
Monday, October 25, 2010
Week 8 Reading Assignments: HTML
And now we are hitting a somewhat weak point of mine: HTML encoding. I've never been good at website building or design, so this week's readings/crash course is really appreciated. Now, on with the show!
W3schools HTML Tutorial
I like the approach of this lesson, as it breaks everything down bit by bit. For once, I'm not swimming in a sea of unexplained acronyms or confusing examples, but having the behind-the-scenes of websites displayed before me in a method I can understand.
If anything, it makes the encoding for formats on Blogger and Livejournal that much more understandable, especially with something to compare it to (in my case: comparing the formatting functions to what I would do while using Office Productivity software). I don't think I'll start building websites anytime soon (as I lack that creative spark), but at least I won't be blindsided when I need to do that sort of work.
HTML Cheatsheet
There isn't much to say about this besides being a useful reference while working on anything in HTML.
W3 School Cascading Style Sheet Tutorial
Once again, a lesson written in a way I can understand it. Unless I misread something, CSS allows the user to edit how HTML will appear on the screen. The more I look at it, it seems to be a more elaborate version of what you can do with HTML, or perhaps HTML meets C++.
I would actually like to see the methods working side by side for a better comparison as to where the limitations lie, but that is just my personal opinion and need to view things.
Beyond HTML: Developing and re-imagining library web guides in a content management system
We use a CMS at the library where I work, and while it may be faulty and have some issues, it does allow those without a programming background to design a website by focusing on just the materials and information (which is something this article mentions). In theory, and as presented in the article, there are many benefits of this method compared to working with HTML alone.
While the article states that a CMS allows customization of a site, efficiency through usability, reusable content, and the removal of a "gatekeeper" of sorts to get things done, in practice it doesn't always seem to be the case. I know the librarians who build our website have had numerous issues involving even getting the CMS to function, leading to constant calls to the "Gatekeeper" in charge of things. It can do amazing and complex things, and makes it easy to see what has been done as certain limitations and guidelines are in place, but I have to wonder if the theory behind it will ever come into the world of practice.
W3schools HTML Tutorial
I like the approach of this lesson, as it breaks everything down bit by bit. For once, I'm not swimming in a sea of unexplained acronyms or confusing examples, but having the behind-the-scenes of websites displayed before me in a method I can understand.
If anything, it makes the encoding for formats on Blogger and Livejournal that much more understandable, especially with something to compare it to (in my case: comparing the formatting functions to what I would do while using Office Productivity software). I don't think I'll start building websites anytime soon (as I lack that creative spark), but at least I won't be blindsided when I need to do that sort of work.
HTML Cheatsheet
There isn't much to say about this besides being a useful reference while working on anything in HTML.
W3 School Cascading Style Sheet Tutorial
Once again, a lesson written in a way I can understand it. Unless I misread something, CSS allows the user to edit how HTML will appear on the screen. The more I look at it, it seems to be a more elaborate version of what you can do with HTML, or perhaps HTML meets C++.
I would actually like to see the methods working side by side for a better comparison as to where the limitations lie, but that is just my personal opinion and need to view things.
Beyond HTML: Developing and re-imagining library web guides in a content management system
We use a CMS at the library where I work, and while it may be faulty and have some issues, it does allow those without a programming background to design a website by focusing on just the materials and information (which is something this article mentions). In theory, and as presented in the article, there are many benefits of this method compared to working with HTML alone.
While the article states that a CMS allows customization of a site, efficiency through usability, reusable content, and the removal of a "gatekeeper" of sorts to get things done, in practice it doesn't always seem to be the case. I know the librarians who build our website have had numerous issues involving even getting the CMS to function, leading to constant calls to the "Gatekeeper" in charge of things. It can do amazing and complex things, and makes it easy to see what has been done as certain limitations and guidelines are in place, but I have to wonder if the theory behind it will ever come into the world of practice.
Wednesday, October 20, 2010
Week 7 Muddiest Points
I haven't run into anything that completely boggled my mind yet from the last class or the readings this week. If anything, this week's readings don't lead to any confusion (thanks to the writing styles involved), and the discussion on campus this week didn't leave me with anything to ask.
I do have an open question for the class: does anyone know much about ILSs, or other providers and their respective services? Sirsi was referenced in the article, and I utilize one of their systems in the workplace, but I cannot help but wonder what else is out there and readily available, especially if Open Source options are coming into play.
I do have an open question for the class: does anyone know much about ILSs, or other providers and their respective services? Sirsi was referenced in the article, and I utilize one of their systems in the workplace, but I cannot help but wonder what else is out there and readily available, especially if Open Source options are coming into play.
Tuesday, October 19, 2010
Week 7 Comments
Here are my comments for this week. If/when I find the time to post a few more, I will list them here.
http://jonas4444.blogspot.com/2010/10/reading-notes-for-week-7.html?showComment=1287514213007#c1334532008612180837
And there is a continuation of that discussion here: http://jonas4444.blogspot.com/2010/10/reading-notes-for-week-7.html?showComment=1287760527313#c2880575713695202074
http://marclis2600.blogspot.com/2010/10/readings_21.html?showComment=1287758672538#c4434320220964359230
http://bookwormsince84.blogspot.com/2010/10/andrew-k-pace-dismantling-integrated.html?showComment=1287917050886#c8808118133639643096
http://jonas4444.blogspot.com/2010/10/reading-notes-for-week-7.html?showComment=1287514213007#c1334532008612180837
And there is a continuation of that discussion here: http://jonas4444.blogspot.com/2010/10/reading-notes-for-week-7.html?showComment=1287760527313#c2880575713695202074
http://marclis2600.blogspot.com/2010/10/readings_21.html?showComment=1287758672538#c4434320220964359230
http://bookwormsince84.blogspot.com/2010/10/andrew-k-pace-dismantling-integrated.html?showComment=1287917050886#c8808118133639643096
Week 7 Readings
Contrary to popular believe, I did NOT forget about my blog, and I did survive the trip to and from Pittsburgh for the FastTrack Weekend. That being said, I think it's time I get to why you are here in the first place: the assignments. So, without further ado. . .
How Internet Infrastructure Works
This website has always been at least an interesting, if not educational, stop for me. Seeing this on our weekly reading list set me at ease a bit; at least I know this topic should be interesting, and the opening line reminds me of that: "One of the greatest things about the Internet is that nobody really owns it."
Personally, what I've always loved about this site, and this article included, is the language used to explain everything. While I may be somewhat tech savvy, I do get lost with the abundance of abbreviations and acronyms in the field, and having them presented before me makes this a much easier read.
I think the article does a great job with giving the basic information without going over the heads of the readers nor by making the information so simple as to be boring.
As a final note: I wish I had read this article sooner, as it would have helped relate the lecture on networks from Friday night with something that I work with daily.
Dismantling Integrated Library Systems
This article explains the changes in library systems, the potential ways they can change, and the approaches taken. The article further explains the problems of doing so: costs, interoperability, and even the overall changes in technology, materials, and ways of accessing those materials.
When you look at it, this article does tie in with some previous discussions of Open Access, RFID, automated library services, and the proliferation of personal computers (including supermobile computing devices) and the impact on libraries and research. Anyone have any thoughts on this?
Sergey Brin and Larry Page: Inside the Google machine
I sadly can't view this video while I am at work on campus. I'll try to get this viewed and commented on sooner rather than later.
Edit: So I finally found the time to sit down and watch this video. It gives a nice, behind-the-scenes view on what Google is, what they were trying to do (and seems to be successful at it, at that), and just an early view of the company. While I do often joke that Google is evil and has more raw information at their fingertips than is healthy, I can't really deny the good they do, from the search engine to the charity work.
How Internet Infrastructure Works
This website has always been at least an interesting, if not educational, stop for me. Seeing this on our weekly reading list set me at ease a bit; at least I know this topic should be interesting, and the opening line reminds me of that: "One of the greatest things about the Internet is that nobody really owns it."
Personally, what I've always loved about this site, and this article included, is the language used to explain everything. While I may be somewhat tech savvy, I do get lost with the abundance of abbreviations and acronyms in the field, and having them presented before me makes this a much easier read.
I think the article does a great job with giving the basic information without going over the heads of the readers nor by making the information so simple as to be boring.
As a final note: I wish I had read this article sooner, as it would have helped relate the lecture on networks from Friday night with something that I work with daily.
Dismantling Integrated Library Systems
This article explains the changes in library systems, the potential ways they can change, and the approaches taken. The article further explains the problems of doing so: costs, interoperability, and even the overall changes in technology, materials, and ways of accessing those materials.
When you look at it, this article does tie in with some previous discussions of Open Access, RFID, automated library services, and the proliferation of personal computers (including supermobile computing devices) and the impact on libraries and research. Anyone have any thoughts on this?
Sergey Brin and Larry Page: Inside the Google machine
I sadly can't view this video while I am at work on campus. I'll try to get this viewed and commented on sooner rather than later.
Edit: So I finally found the time to sit down and watch this video. It gives a nice, behind-the-scenes view on what Google is, what they were trying to do (and seems to be successful at it, at that), and just an early view of the company. While I do often joke that Google is evil and has more raw information at their fingertips than is healthy, I can't really deny the good they do, from the search engine to the charity work.
Wednesday, October 6, 2010
Week 6 Comments
And here are the comments that I have posted for this week:
http://jsslis2600.blogspot.com/2010/10/week-6-notes.html?showComment=1286406306075#c8494163197706463619
http://jonas4444.blogspot.com/2010/10/reading-notes-for-week-6.html?showComment=1286406899885#c5430048090739279684
http://jsslis2600.blogspot.com/2010/10/week-6-notes.html?showComment=1286406306075#c8494163197706463619
http://jonas4444.blogspot.com/2010/10/reading-notes-for-week-6.html?showComment=1286406899885#c5430048090739279684
Tuesday, October 5, 2010
Week 6 Muddiest Point
Once again, nothing really comes to mind as confusing. If something comes up during the week that changes my mind, I'll post it here.
Week 6 Readings: Computer Networks, Wireless Networks
Local Area Networks (LAN)
I’ve been on my fair share of LANs (who hasn’t after being in college?), so having the chance to read up on the history of this technology changes my views of it. I didn’t know that my uses of the LAN were close to what it was originally designed for: sharing peripherals (e.g. printers) and disk space. While I primarily used it for transferring files and the mess of C++ programs/assignments, those uses still seem rather closely related to the original purpose. I also liked the note of the evolution from various protocols until TCP/IP.
Computer Networks
I think this article is a bit more relevant to the case of networks than the previous note on LANs. This article was a bit broader in terms, explaining the computer networks as a whole, the different technologies involved (e.g. forms of wired and wireless networks), the scale of the networks, and even the hardware involved for a network.
Personally, I liked the explanations of the internet being a large computer network, the note between a global network and the internet, and the information on intranets and extranets (as I have to utilize and intranet in the workplace).
Common types of computer networks (video)
A video that, following the trend of the week, explains various kinds of networks, starting from the smaller, more common types, and moved up from there. Started off with a PAN, and moved through larger networks. There really isn’t much else to say about this video beyond the note on scaling.
Management of RFID in Libraries
My experiences with RFID are non-existent, and my knowledge on the topic as a whole is sketchy at best, making this a relatively interesting read. I do have to admit that I feel as though the writer is biased to moving libraries to RFID, primarily when referencing the “speeding up” of tasks in society.
I must admit that the concept is rather sound, yet sound like something out of a science fiction novel; chips to denote where a book is located in the building, an extraordinarily fast way to complete inventory, and even combining security and checkout in one action. While the idea of such efficiency is nice, I don’t believe all of the ideas, such as the self-checkout machines, will be the best for library users. Perhaps I am wrong, but as great as the technology is, I don’t think libraries have the proper setup or mentality for this change, nor do I think the technology is at the level needed for such a use. Any opinions?
I’ve been on my fair share of LANs (who hasn’t after being in college?), so having the chance to read up on the history of this technology changes my views of it. I didn’t know that my uses of the LAN were close to what it was originally designed for: sharing peripherals (e.g. printers) and disk space. While I primarily used it for transferring files and the mess of C++ programs/assignments, those uses still seem rather closely related to the original purpose. I also liked the note of the evolution from various protocols until TCP/IP.
Computer Networks
I think this article is a bit more relevant to the case of networks than the previous note on LANs. This article was a bit broader in terms, explaining the computer networks as a whole, the different technologies involved (e.g. forms of wired and wireless networks), the scale of the networks, and even the hardware involved for a network.
Personally, I liked the explanations of the internet being a large computer network, the note between a global network and the internet, and the information on intranets and extranets (as I have to utilize and intranet in the workplace).
Common types of computer networks (video)
A video that, following the trend of the week, explains various kinds of networks, starting from the smaller, more common types, and moved up from there. Started off with a PAN, and moved through larger networks. There really isn’t much else to say about this video beyond the note on scaling.
Management of RFID in Libraries
My experiences with RFID are non-existent, and my knowledge on the topic as a whole is sketchy at best, making this a relatively interesting read. I do have to admit that I feel as though the writer is biased to moving libraries to RFID, primarily when referencing the “speeding up” of tasks in society.
I must admit that the concept is rather sound, yet sound like something out of a science fiction novel; chips to denote where a book is located in the building, an extraordinarily fast way to complete inventory, and even combining security and checkout in one action. While the idea of such efficiency is nice, I don’t believe all of the ideas, such as the self-checkout machines, will be the best for library users. Perhaps I am wrong, but as great as the technology is, I don’t think libraries have the proper setup or mentality for this change, nor do I think the technology is at the level needed for such a use. Any opinions?
Subscribe to:
Posts (Atom)