Web Development With
SAS by Example
- Tags are used in mark up languages to annotate the document content.
- Mark up tags are used to format the display of webpages
- Extensible Hypertext MarkUp Language is recommended by the World Wide Web Consortium for its stricter and cleaner reformulation
- Unlike HTML, XHTML documents must be lowercase, nest together properly, posses closing tags and attributes must be cited
- XHTML must follow Document Type Definition, requiring page formats to be in style sheets and not included as part of the make up
- This allows for a constistent look across the entire page
- Mark up tags give browsers the information regarding how to display the webpage
- All XHMTL are required to have the closing tag which is </html>
- Tags can be used to separate different sections of a webpage (title, head, style, etc)
- For HTML, case of the letters do not matter, but all open tags must have a closing tag
- HTML are allowed to have additional attributes that are separated by an equal sign
- For XHTML there does not need to be a closing tag, all information is held in the tag
- Class, SRC and ALT are all found on the <img> tag already
- Tables can hold data as well as pictures, videos and other things
- There are two types of links, relevant and
- Syle sheets are used to make the webpage more uniform, it is similar to using a template
- HTML forms can collect user input
- HTML tags are used to communicate the output of the
- Developing and re-imagining library web guides in a content management system
- Content Management is the process of
collecting, managing, and publishing content.
- CMS (content management systems) do not
require a lot of experience to build.
Because of this, it is possible for almost anyone to create one.
- The
display of the system is separate from the content, allowing libraries to
concern themselves with the identifying, creating, annotating, and selecting
of content.
- Content can be: resource links,
internal web pages, images, files in different formats
- All content added to the database can be
reused whenever necessary.
- Within a CMS there are/should be
different levels of access. Some
objects are able to be accessed by the librarian that uploaded them, while
others are able to be accessed by any librarian.
- Some libraries have a problem with staff
not being able to have enough access to materials in the CMS, while others
have the opposite problem. CMS
allows librarians to custom this to their benefit.
- Customizing (also called tagging) allows
librarians to put information in different groups and catagories, which
helps to make the content more meaningful for users.
- CMS have a mixture of complexity and
simplicity that make them more beneficial than files and folder sharing
systems. CMS offers scalability
without hindering editing and publishing, web development staff can more
easily assign access rights, and content being used cannot be deleted by
other libraries.
- Open
Source option was considered but they did not include any all inclusive
services. The ones that did were
for Linux/Unix but libraries servers ran on Windows.
- A series of tables were
created to join subscription databases and personnel tables allowing
librarians to contribute individually or collectively.
- Administration
links pass a specific variable for “action” so that each page knows
whether to display content for a specific guide, add new content, update
existing content, or delete content.
- 1 ASP file page can manage an entire CMS
ASP files depend on URL to make calls to the CMS. ASP code then gets the information from the database and assembles it for the viewer. - The MySQL database contains tables for
specific types of resource objects
such as databases,
e-journals, books, media, and internet links. – can often act like a digital
library, most often managed by the electronic resource librarian or CMS
administrators.
·
Site administrators and librarians both have access to control
mechanisms.
·
Presentational controls allow information to be
organized so it can be utilized in classrooms properly.
·
The research guides component combines content
from different tables.
·
Library guides were broken up into secondary
pages linked to the main one, and others were single scrolling pages of
resources.
·
Reasons for CMS migration include ease of use
and standardization.
·
There is a crucial gap among librarians
understanding about web site information architecture and writing for the web
medium.
* Both tutorials completed!
* Both tutorials completed!
Muddiest Point: I did not have a muddiest point this week
