Friday, October 31, 2014

Muddiest Point Week 9

My muddiest point for this week has to deal with the values for CSS. How come there are word values for colors, like green, in some declarations, but there are codes for colors in others? I may have missed it in the readings, and would just want some clarification.

Week 9 Notes Cascading Style

This weeks readings are on the Cascading Style Sheet (CSS) code language which was touched up on a little bit last week. The CSS language seems like it is easier to learn than HTML, the one thing I noticed is that some colors require codes while others require just the numbers.

Here's an example of CSS:
H1 { color: green }
Selector and declaration

The selector chooses what kind of action for the code to choose from and the declaration sets forth the effect that the action that is chosen.

Declarations have their own breakdown as well
{ color: green }
Property and value

the property tells you what type of an effect is being selected, whether it is the font, alignment, background, or color. The value of the property tells the document what it should look like, if the text should be green, or if the text should be left-aligned, or if the background should be purple. It really gives documents a nice way to customize and stand out.

The chapter from the ebook that really explains CSS makes it clear about what to do, and touches on gluing the CSS into the HTML, which was discussed in last weeks readings. An example of gluing looks like:

<HTML>
  <TITLE>Bach's home page</TITLE>
  <STYLE>
    H1, H2 { color: green }
  </STYLE>
  <BODY>
    <H1>Bach's home page</H1>
    <P>Johann Sebastian Bach was a prolific
        composer. Among his works are:
    <UL>
      <LI>the Goldberg Variations
      <LI>the Brandenburg Concertos
      <LI>the Christmas Oratorio
    </UL>
    <H2>Historical perspective</H2>
    <P>Bach composed in what has been referred to as
      the Baroque period.
  </BODY>
</HTML>


The other sites were another way to touch up on learning the CSS and even HTML code writing that I enjoyed last week. I think these sites are very beneficial for someone who has never attempted to write code before.





Friday, October 24, 2014

Muddiest Point Week 8

This week's lectures and readings seemed fairly straight forward, but I guess I would have to make a point regarding the assignments. For assignment 4, making HTML and a bookshelf on KOHA, would there be any use of this kind of work in an archives? Or is this mainly for libraries?

Reading Notes Week 8: HTML

This week's discussion is HTML and coding languages. I am new to writing codes so this reading/activity was something I really enjoyed to do.

Seeing how to write a heading or a body for a paragraph in HTML was really fun to do honestly, I tried out a bunch of different combinations on the site to test HTML. 

I think that learning these languages will really help myself obtain a job in the job market these days. A company could always use more tech savvy employees.

Out of the two languages it seems like CSS is easier, because it has the properties and the values within the text. But I have to say that HTML is fairly easy to use as well, and would seem to me that employers would want more. But if I could use CSS alongside with HTML it would make webpages look a lot nicer, and make myself more useful. 

Examples of HTML:
<body> </body>
<heading> </heading>
<p> </p>
<address> </address>

Examples of CSS:
H1 { color: green }
H2 { font-weight: bold }
H3 { 
        color: green; 
        text-align: center;
}

Saturday, October 18, 2014

Class Notes Week 7 Internet

This week's readings regarding the Internet and how it works was rather enjoyable this week. The article "How Internet Infrastructure Works" sounds like a boring title and would be rather tedious to read, but I found that to be one of the better articles we've read for class. Seeing how the internet infrastructure is made up of a bunch of smaller networks into one seems like it was something I've known before, but seeing it discussed in the article made it even clearer to me. The graph that the article provides describing the Internet Hierarchy really help clear up any confusion on the way that the Internet is established for a personal computer using a large Internet Service Provider (ISP) or even a company that uses a Large Area Network (LAN) for their internet needs.

The second article for our readings discussed the use of the Internet and its effects on the Integrated Library Systems across the nation. It seems like it is an issue that has no easy solution because of how many libraries that use the integrated systems for a lot of their services, but it needs to be changed eventually. Because of the ever growth of the Internet and how it continues to expand into more fields and become more useful it makes sense that the libraries across the nation would get rid of their systems that are becoming outdated. On the other hand, it seems like it would cost a lot of money for a library to do something like that and would deter it from taking on a project like that. The one thing that I have to note is that the article is from 2004, and could be out of date due to the new technology that is in place today. Some new technology could have been invented between the article and now that makes the process of changing a system over slightly easier for a library.

Overall I rather enjoyed these articles that we had for readings this week. If there are more articles like this ahead I would appreciate it.

Friday, October 3, 2014

Muddiest Point 4

This week's muddiest point comes from metadata scheme; when a community defines a scheme for the metadata, would it be beneficial for it to be changed when a better type of scheme is introduced indirectly? For example, if an archives uses a scheme for many years and their metadata is all that type, would it be beneficial for that archives to change all of their metadata to a new format that is better for the archives storage and retrieval? Or would it be something that just wastes time and energy for the archives?

Week 6, Networks and Mendeley

This week's reading regarding Local Area Networking (LAN) was one that really interested me, because I use it everyday. When I heard LAN my first reaction was ethernet cables and connecting to the internet via cables and plugs, not Wi-Fi. I had no idea that the routers and different types of Wi-Fi connectors used LAN, it makes so much sense now that I read about it, but beforehand I thought that Wi-Fi was its own separate type of networking. The reading on networks themselves was also enlightening. The development of networks overtime really makes you think how lucky we are to live in an era where beams of light carrying information are transmitted through a cable is possible. It was nice to read about the networks that we use everyday, how they can be structured. Structures include: ring, star, bus, mesh, tree, fully connected, and line. Each of these configurations has their own benefits and issues.

The blog post regarding Mendeley was a unique way to interpret how useful the software is. I knew there were other sites like Zotero and EndNote, I never used them. I had a public history course that discussed Zotero and how to use it, but rarely actually did. The author of the blog was very adamant regarding how useful Mendeley was, or lack of usefulness, to him. He even addresses it how Mendeley could be useful, but says that his field uses Zotero and it would be hard to switch the entire field over to Mendeley. Using Mendeley myself I have found it very useful and like the fact that there are more types of programs and software like it. It creates a vast market that allows the communities of different fields to decide what is important and useful to them.