Week 8 Readings

Sorry about this post, it is rather dry.

1) W3schools HTML Tutorial: http://www.w3schools.com/HTML/

I've accessed this website before for a computer science class I took as an undergrad. It is really helpful as it breaks each tag down and gives great examples. I also really appreciate the ability to "try it out." This is a very helpful tool for new HTML users. Below I have included some of the tags I would like to keep reference of. In my use of HTML I have found this pages reference to table tags most helpful.

2) HTML Cheatsheet http://www.webmonkey.com/reference/HTML_Cheatsheet/

This cheatsheet form webmonkey, "the web developer's resource" is very useful. I love that the cheatsheet is a list. It is helpful, easily accessible, and and highly informative. Its selection of frame tags are very helpful as their are greatly detailed, covering a vast array of scenarios. Again, I have added some references I would like to reference.

3) W3 School Cascading Style Sheet Tutorial: http://www.w3schools.com/css/

Aside from the helpful content, particularly the color sheets, the tutorial is interesting in its assertion that HTML was never intended to house style sheets:

HTML was intended to define the content of a document, like:

When tags like , and color attributes were added to the HTML 3.2 specification, it started a nightmare for web developers. Development of large web sites, where fonts and color information were added to every single page, became a long and expensive process.

To solve this problem, the World Wide Web Consortium (W3C) created CSS.

In HTML 4.0, all formatting could be removed from the HTML document, and stored in a separate CSS file. All browsers support CSS today.

4) Goans, D., Leach, G., & Vogel, T. M. (2006). Beyond HTML: Developing and re-imagining

library web guides in a content management system. Library Hi Tech, 24(1), 29-53.

Dev system using MySQL and ASP

New system exceeded their expectations, providing, “greater control over appearance and navigation while still offering customization features for liaisons. When integrating a CMS attention must be given to user issues and technical issues Initial lack of control over content, architecture and organization led to inconsistency. – too diverse, lack of training was at time apparent- doesn’t seem like a good expenditure of time, or money for that matter. Minimal security, not robust-

First web dec librarian hired in 2000- implement web security for Frontpage, also built MySQL applications to manage databases and e journals as well as photographic collections. – however, unregulated creation of guides still continued.

2003- site standards identified four common elements, database technology could now be applied to GSU guides. Away from static HTML into more dynamic and automated system.

CMS defined: Collecting, managing and publishing content. A database or repository is oversimplifying it.

The content is disconnected from the layout and design elements of the page guides are created in form based environment- helps with inability or lack of experience in HTML. Lib can focus on content rather than presentation. Content definition depends on institution. Reusability is also a key element, material can be reused and added to without disruption. Object-oriented site development.

Allows for enhanced editorial access while still functioning as a limited gatekeeper to provide cohesive visual and navigational standards.

By limiting content style editing, users know what to expect in each guide, ease of use and access is increased.

Tagging allows for lib to create cross referenced user guides. – enhanced the reuse of content. Opportunity to create unique descriptions. Metadata customization gives meaning and additional context.

There are commercial options, open sources options and In-House options.

GSU CMS technology is made up of resource tables, metadata, and personnel metadata tables. Edits are done through administrative forms.

Great examples of directories. Interesting representation of HTML. Librarians can edit resources and web pages while site admins have online forms to edit or add website sections and also assign people and authorship rights. – manages presentational control. This structure has helped to reduce redundancy, lack of cohesion, and has increased user ability of the guides.

The decision to build the database around existing categories was due to cost, staff, and the desire to limit the reworking of the guides. – varying degree of HTML/CSS experience. – reason for migrating was clearly communication. One of the ultimate goals was to build a system that could ultimately be expanded to other departments.

How might we learn from this experience? I would imagine that the very opportunity to include reference guides is out of reach for some less funded libraries. Perhaps the GSU experience can save future libraries the time and funding of reformatting and training.