Monday, November 10, 2008
Friday, November 7, 2008
Unit 10 Reading Notes
Web Search Engines: Part 1 & 2 reminded me just how interesting it is that search engines can get us fast, accurate results, with minimal spam. Spam filters are getting so much better, and the search engine algorithms are improving all the time. It's a complicated system, and there are so many things to be aware of-- the politeness aspect was one I hadn't thought of much, but it's important. I know a bit about SEO, so not all of this information was new to me, but these readings were clear and pretty easy to understand.
Current developments and future trends for the OAI protocol for metadata harvesting - Not really familiar with OAI, but has to do with metadata, searching databases, and so on, to create better access to information.
The Deep Web: Surfacing Hidden Value - Good comments on searching, the limitations of searching, the problems we face trying to both narrow results and provide access to as much information as possible, and the difference between surface content and the deep web. 750 terabytes is a massive amount of information! I'm not surprised that some of the biggest deep web sites are government sites, either. Interesting comment on how "higher quality" really means "did I get what I wanted?"
Current developments and future trends for the OAI protocol for metadata harvesting - Not really familiar with OAI, but has to do with metadata, searching databases, and so on, to create better access to information.
The Deep Web: Surfacing Hidden Value - Good comments on searching, the limitations of searching, the problems we face trying to both narrow results and provide access to as much information as possible, and the difference between surface content and the deep web. 750 terabytes is a massive amount of information! I'm not surprised that some of the biggest deep web sites are government sites, either. Interesting comment on how "higher quality" really means "did I get what I wanted?"
Tuesday, October 28, 2008
Friday, October 24, 2008
Muddiest Point Week 8
I have a question about searching within a site. Why is it that the search feature of so many sites just doesn't work well? I nearly always end up using Google to search within a site. Is it inexperienced programmers? The massive resources of Google? Something else?
Unit 9 Reading Notes
Introducing the Extensible Markup Language (XML)
-XML helps the user combine documents, identify formats, add comments to files.
- XML tags are stuctured and logical, moreso than similar features used by word processors.
- It's clear where the tags begin and end.
- You can create your own tag sets using DTD.
- XML files are easily stored in databases and are easily changed to fit any database.
-XML files are easily transferred to many different kinds of hardware and software. The files will not get outdated quickly, and will only need to be updated.
A survey of XML standards
- XML has different sets of standards, which can make it difficult for new users to determine which standards to use. Standards can be complex. He adds that XML has a lot of components and can intimidate new users.
- This article focused on what the author thought of as the "core XML technologies."
- Some updates to XML are controversial. Some believe changes are not worth it if the benefit is too small.
- The article briefly summarizes several types of XML systems. XInclude is a way to combine XML documents and break them into smaller chunks. XLink is a way to use links that are more complex than basic HTML links.
- I found this one a little harder to follow because I'm not familiar with the many systems he discusses.
Extending your Markup: a XML tutorial by Andre Bergholz
- Starts off by commenting that XML is said to be simple and also does everything you need. He says that this is partially hype, but that XML is useful once you get past the hype.
- Provides several examples of XML and compares these examples to HTML.
- You can learn most of what you need to know about XML online.
- Explains in more detail the difference between using links in HTML and XML, for example, XML links can lead to a specific section of a document, whereas HTML URLs only direct the user to a specific document.
- Goal of XML Schema is to replace DTDs, but only time will tell whether it can.
- I found this reading more beginner-friendly than the previous one because it contained more explanations right in the text rather than primarily linking to other resources.
XML Schema Tutorial
- Tutorial about how to read and create XML Schemas. Like the previous reading, it shows how XML Schema can now be used instead of DTD, and this tutorial aims to show the ways XML Schema is superior.
- Showed differences between XML Schema and DTD. (Supports data types and namespaces.)
- The tutorial went pretty in-depth, I'm not sure how much of the information I absorbed-- and this is only one aspect of what I'd need to know.
- Like the previous tutorials, I found them useful, but can't help being distracted by the ads and the sidebar crowding the page on the right.
-XML helps the user combine documents, identify formats, add comments to files.
- XML tags are stuctured and logical, moreso than similar features used by word processors.
- It's clear where the tags begin and end.
- You can create your own tag sets using DTD.
- XML files are easily stored in databases and are easily changed to fit any database.
-XML files are easily transferred to many different kinds of hardware and software. The files will not get outdated quickly, and will only need to be updated.
A survey of XML standards
- XML has different sets of standards, which can make it difficult for new users to determine which standards to use. Standards can be complex. He adds that XML has a lot of components and can intimidate new users.
- This article focused on what the author thought of as the "core XML technologies."
- Some updates to XML are controversial. Some believe changes are not worth it if the benefit is too small.
- The article briefly summarizes several types of XML systems. XInclude is a way to combine XML documents and break them into smaller chunks. XLink is a way to use links that are more complex than basic HTML links.
- I found this one a little harder to follow because I'm not familiar with the many systems he discusses.
Extending your Markup: a XML tutorial by Andre Bergholz
- Starts off by commenting that XML is said to be simple and also does everything you need. He says that this is partially hype, but that XML is useful once you get past the hype.
- Provides several examples of XML and compares these examples to HTML.
- You can learn most of what you need to know about XML online.
- Explains in more detail the difference between using links in HTML and XML, for example, XML links can lead to a specific section of a document, whereas HTML URLs only direct the user to a specific document.
- Goal of XML Schema is to replace DTDs, but only time will tell whether it can.
- I found this reading more beginner-friendly than the previous one because it contained more explanations right in the text rather than primarily linking to other resources.
XML Schema Tutorial
- Tutorial about how to read and create XML Schemas. Like the previous reading, it shows how XML Schema can now be used instead of DTD, and this tutorial aims to show the ways XML Schema is superior.
- Showed differences between XML Schema and DTD. (Supports data types and namespaces.)
- The tutorial went pretty in-depth, I'm not sure how much of the information I absorbed-- and this is only one aspect of what I'd need to know.
- Like the previous tutorials, I found them useful, but can't help being distracted by the ads and the sidebar crowding the page on the right.
Saturday, October 18, 2008
Tuesday, October 14, 2008
Friday, October 10, 2008
Unit 8 Reading Notes
The HTML tutorial explained the basics of using HTML to create a web page. I have to say that the page itself was cluttered and a little hard to read, with the main text being surrounded by so many boxes and ads. Their editor was a useful way for a user to make sure they understand the concepts and a quick and easy way to test out some HTML. I really liked that aspect of the site.
The HTML cheatsheet was just a listing and brief explanation of many basic HTML tags. Though I will say, I remember trying to learn HTML years ago and not being able to find a simple, organized cheatsheet like this one.
The CSS tutorial was on the same site as the HTML tutorial, and so it was also cluttered and a little hard to read. It was more distracting because I'm not as familiar with CSS. I've seen it used and I've had it explained to me, but I've never actually used it myself, so jumping right into reading a tutorial that didn't give any actual background for CSS was a little confusing at first. However, the tutorial seems pretty straightforward. CSS is more complicated than HTML, though. Of course, it also allows you to do more...
I should have read the Library Hi Tech article first, actually. I think it might have helped clear things up a little, since it discussed HTML and CSS use in libraries, with a major focus on CMS. Good CMS is so important, and I feel should be easy for pretty much anyone to use. This article discusses the use of CMS in libraries to develop a "collaborative publishing process" which connects librarians and web developers.
The HTML cheatsheet was just a listing and brief explanation of many basic HTML tags. Though I will say, I remember trying to learn HTML years ago and not being able to find a simple, organized cheatsheet like this one.
The CSS tutorial was on the same site as the HTML tutorial, and so it was also cluttered and a little hard to read. It was more distracting because I'm not as familiar with CSS. I've seen it used and I've had it explained to me, but I've never actually used it myself, so jumping right into reading a tutorial that didn't give any actual background for CSS was a little confusing at first. However, the tutorial seems pretty straightforward. CSS is more complicated than HTML, though. Of course, it also allows you to do more...
I should have read the Library Hi Tech article first, actually. I think it might have helped clear things up a little, since it discussed HTML and CSS use in libraries, with a major focus on CMS. Good CMS is so important, and I feel should be easy for pretty much anyone to use. This article discusses the use of CMS in libraries to develop a "collaborative publishing process" which connects librarians and web developers.
Muddiest Point
Do people still use HTML (frequently) to build web pages, or is it mostly CSS now? And how much HTML do you really need to know to use CSS-- is a basic familiarity enough?
Monday, October 6, 2008
Assignment #4: Jing video
http://www.screencast.com/users/rrosspitt/folders/Default/media/909c240d-eafb-4594-8f13-992d30bb1775
http://www.flickr.com/photos/30525270@N03/2920135504/sizes/o/
http://www.flickr.com/photos/30525270@N03/2920135632/sizes/o/
http://www.flickr.com/photos/30525270@N03/2919290021/sizes/o/
http://www.flickr.com/photos/30525270@N03/2920135822/sizes/o/
http://www.flickr.com/photos/30525270@N03/2919290193/sizes/o/
http://www.flickr.com/photos/30525270@N03/2920135504/sizes/o/
http://www.flickr.com/photos/30525270@N03/2920135632/sizes/o/
http://www.flickr.com/photos/30525270@N03/2919290021/sizes/o/
http://www.flickr.com/photos/30525270@N03/2920135822/sizes/o/
http://www.flickr.com/photos/30525270@N03/2919290193/sizes/o/
Sunday, October 5, 2008
Friday, October 3, 2008
Muddiest Point from 9/30 lecture
In class, the range of RFID was discussed, and it was said that the distance at which you can read it is maybe 10-20 feet. Is that on purpose, or could we create some which have a longer range?
Unit 7 Reading Notes
How Internet Infrastructure Works
This was a pretty good summary of how the internet works, and covered a lot of basic topics. (The parts where it discussed dial-up made me remember when that was all I had. I don't know how I managed without my high-speed access!) And I agree with this "One of the greatest things about the Internet is that nobody really owns it." Though I know some people are trying to. The site also gives a little bit of history, and I think it's interesting to read about people creating the frameworks for what we have today. I don't really have much else to say about this one, though.
Dismantling Integrated Library Systems
Discusses what is needed for an effective ILS. New technology and developments cost, but libraries can't or don't pay enough to keep updates and innovation moving well enough. New services may not integrate well with existing systems. It basically sounds like no one really knows where to go with ILS systems. Systems are changing, and it is getting more complex to integrate everything.
Inside the Google Machine
Cool visual representation of people using Google, by language.
Search patterns - you can see by country who is searching for things and can also compare interest levels on various topics this way.
Little activity in Africa so far
1 second representation of queries and traffic
Google Foundation and Google Grants - gives ad credit to charities
Googlette - small experimental/innovative project at Google (Google News) is used to keep innovations going. 20% of time can be used for anything.
I think Google is a fascinating company. The talk was pretty interesting.
This was a pretty good summary of how the internet works, and covered a lot of basic topics. (The parts where it discussed dial-up made me remember when that was all I had. I don't know how I managed without my high-speed access!) And I agree with this "One of the greatest things about the Internet is that nobody really owns it." Though I know some people are trying to. The site also gives a little bit of history, and I think it's interesting to read about people creating the frameworks for what we have today. I don't really have much else to say about this one, though.
Dismantling Integrated Library Systems
Discusses what is needed for an effective ILS. New technology and developments cost, but libraries can't or don't pay enough to keep updates and innovation moving well enough. New services may not integrate well with existing systems. It basically sounds like no one really knows where to go with ILS systems. Systems are changing, and it is getting more complex to integrate everything.
Inside the Google Machine
Cool visual representation of people using Google, by language.
Search patterns - you can see by country who is searching for things and can also compare interest levels on various topics this way.
Little activity in Africa so far
1 second representation of queries and traffic
Google Foundation and Google Grants - gives ad credit to charities
Googlette - small experimental/innovative project at Google (Google News) is used to keep innovations going. 20% of time can be used for anything.
I think Google is a fascinating company. The talk was pretty interesting.
Sunday, September 28, 2008
Friday, September 26, 2008
Week 6 Muddiest Point
I wondered about PNG format-- some programs can't seem to handle PNG images. Is this due to it being a newer format and we just need to update to account for it, or is the format more complex than, say, a GIF? I'm still not sure I understand why it's the "best of all worlds."
Unit 6 Reading Notes
The LAN Wikipedia entry was pretty brief and only dedicated a paragraph or
so to any one topic, so I don't have a whole lot to say about it. I didn't
know Ethernet was created in the 70s. Really, the main thing discussed
here is the history of the LAN as it relates to the PC, and the many
competing types of cables and network cards. It sounds confusing and it
probably meant that it was hard to choose what to use when there are 40
types of cables.
Computer network entry: I actually thought the small section about LAN
here was better than the separate entry for LAN. It's short, but clearer
and more straightforward, in my opinion. It goes on to summarize various
types of computer networks and related devices. I was familiar with most
of the basic hardware components, though not so much with bridges.
YouTube video on computer networks: This video was very short and it was also pretty vague. He basically just went over the most common types of networks. I didn't find this very useful at all, to be honest. It barely even gave a description of the networks.
RFID Journal Article: I do wish they had covered more of the privacy issues, but this was more about the functions of it in general. I don't know what I think about self check-out yet. On one hand, I like it, but on the other-- well, I've used self check-out in grocery stores and I have annoying problems popping up maybe 1/4 of the time. An item gets stuck or won't scan or something. So obviously a library would have to have someone monitoring the stations. I agree with Karen Coyle's point that patrons may feel the "burden" is being shifted onto them.
I think I'd like to see both options available. I know that many patrons come to the library and end up chatting with the circ staff. It makes the library a friendlier place. Then again, there are some libraries that are so busy no one would have time to talk, the staff is overworked (and it may lead to repetitive stress injuries as mentioned in the journal article), and people become impatient. Anyway, I think having both options as much as possible is the way to go, at least for now.
so to any one topic, so I don't have a whole lot to say about it. I didn't
know Ethernet was created in the 70s. Really, the main thing discussed
here is the history of the LAN as it relates to the PC, and the many
competing types of cables and network cards. It sounds confusing and it
probably meant that it was hard to choose what to use when there are 40
types of cables.
Computer network entry: I actually thought the small section about LAN
here was better than the separate entry for LAN. It's short, but clearer
and more straightforward, in my opinion. It goes on to summarize various
types of computer networks and related devices. I was familiar with most
of the basic hardware components, though not so much with bridges.
YouTube video on computer networks: This video was very short and it was also pretty vague. He basically just went over the most common types of networks. I didn't find this very useful at all, to be honest. It barely even gave a description of the networks.
RFID Journal Article: I do wish they had covered more of the privacy issues, but this was more about the functions of it in general. I don't know what I think about self check-out yet. On one hand, I like it, but on the other-- well, I've used self check-out in grocery stores and I have annoying problems popping up maybe 1/4 of the time. An item gets stuck or won't scan or something. So obviously a library would have to have someone monitoring the stations. I agree with Karen Coyle's point that patrons may feel the "burden" is being shifted onto them.
I think I'd like to see both options available. I know that many patrons come to the library and end up chatting with the circ staff. It makes the library a friendlier place. Then again, there are some libraries that are so busy no one would have time to talk, the staff is overworked (and it may lead to repetitive stress injuries as mentioned in the journal article), and people become impatient. Anyway, I think having both options as much as possible is the way to go, at least for now.
Monday, September 22, 2008
Friday, September 19, 2008
Week 4 Muddiest Point
My question is if all databases ultimately do the same thing, what differentiates databases using the same model from each other except the language used to interact with them?
Subscribe to:
Posts (Atom)