Apr 19, 2018  

Economic and Community Development

Webpage Policies and Procedures
07:00:03 Webpage Policies and Procedures


  1. Introduction
    1. This document defines the standards that shall govern all Web pages and Web sites for Chattanooga State Community College. All development efforts must follow the standards defined in this document and maintain a Web site that is professional, consistent, aesthetically appealing, accurate, easy to navigate, and accessible. The Chattanooga State Community College Web site must contribute to increased enrollment and student retention.
  2. Technical Requirements
    1. The technical requirements address the scripting languages, database design standards, and the time requirements for developing Web content.
      1. Scripting languages - All Chattanooga State Community College Web sites shall be developed using scripting languages approved by the College's Web Site Standards Committee. Microsoft® Active Server Pages (classic and .NET), JavaScript, and Flash are currently approved for use on College Web sites. Other scripting languages such as PHP or Perl are approved on a caseby- case basis.
    2. Database design standards - Some Web pages require interactive content that is stored in a database and incorporated into the page using a scripting language. This section of the procedure lists standards for creating the database part of the Web site.
      1. Database provider - If a Web site requires the use of a database, the database will be stored and maintained using an enterprise-level relational database management system (RDBMS) such as Microsoft® SQL Server or Oracle. Use of open-source RDBMSs such as MySQL will be decided on a case-by-case basis. Personal database providers such as Microsoft Access or Microsoft FoxPro are not allowed on any Web site managed by the College. - Method of specifying database connection
      2. Web pages that connect to a database must have a way to specify the details of how to connect to the RDBMS. Pages on the College's Web site must use a Data Source Name (DSN) that has been created on the server and that will display the Web pages. Connections without a DSN, or similar connections where the details are spelled out in text on the Web page, are not allowed due to the security risks they create.
      3. Method of storing details of database commands - Web pages that connect to a database must have a way to specify the SQL code that will be run against the database to retrieve or maintain data. As of the enactment of this policy, all new database code will be included in a procedure that is stored within the database.
      4. No SQL will be created in dynamic SQL strings that are passed from the Web page to the database. This methodology will reduce the risk of SQL injection attacks in which an attacker adds malicious code to the input of a form field. All existing code that uses dynamic SQL strings will be revised to use the stored procedure method.
    3. Time required to develop Web content - While users may request whatever deadline they desire for the development of new Web pages for the College's Web site, it is up to the developers to determine the minimum required time to develop the new pages. This required time should be transmitted to the users during the development process.
  3. Web Design Standards
    1. This section addresses the guidelines for the style guide, server side include files, cascading style sheet for the template, div IDs, and classes.
      1. Style guide
      2. For ease of creation and to maintain a consistent look throughout the Web site, a page template will be used to create the Chattanooga State Community College Web pages. There are several page templates including a links page, a content page, a 2-column page, a 3-column page, and a table template. The College template contains a Chattanooga State Community College header include file, a navigation menu include file, and footer include file.
      3. The advantages of using include files are the ease of maintenance and management. By changing one include file, changes are made to hundreds of pages without uncertainty as to whether all Web pages have had the change made.
      4. An external style sheet is linked to the template, which provides the formatting on the Web page and separates presentation from content. This technology is a useful technique for Web site maintenance, development, and standardization. The external style sheet also assists in accessibility compliance with Section 508 of the Americans with Disabilities Act.
      5. The Web site is designed and optimized for viewing on an 800X600 pixel screen resolution or better.
  4. Server side include files
    1. Include files have been created for use on every Web page, allowing changes to a few files propagating through the entire Web site without having to edit every single Web page.
      1. Header - The header contains the words Chattanooga State, page finder identifying department, date and time generated by asp code, and navigation to the department home page in the top right corner.
      2. Menu - The menu contains standard navigation to Home, Academics, Admissions, Catalog/Schedule, People Finder, Giving, Search, Students, and Contact Us.
      3. Footer - The footer contains the Contact Webmaster link, the College's address and phone number, and the drop-down menu.
  5. Cascading style sheet for the template
    1. The cascading style sheet for the template is Global.css. The specifications are listed below.
      1. Standard hexadecimal colors
      2. The standard hexadecimal colors for the cascading style sheet for the template are:
  1. Navy
  1. Red
  1. Dark tan
  1. Medium tan
  1. Light tan
  1.  Body - The page background color is #BCAE9. The left, right, top and bottom margins are set to 0.
  2. Text specifications - The text specifications for the body, the head tags, and hyperlinks are designated below.
    1.  Font specifications for the body
    2. To increase reading comprehension and to provide easier readability on a computer screen, as well as accommodate the default fonts installed on all computer platforms, theses specifications are to be used for the Chattanooga State Community College Web site.
  • The font styles are Arial, Helvetica, and Verdana
  • The font color is black
  • The font size is 62.5%, a relative size to the default font size of the browser, which provides better accessibility than an absolute font size
 Font specifications for the head tags
  • The font styles are Arial, Helvetica and Verdana
  • The font Color is #091D63
  • The h1 font size is 125%
  • The h2 font size is 110%
  • The h3 font size is 100%
Font specifications for the hyperlinks

The font specifications for hyperlinks are defined below.

a. Link, vlink, and active hyperlinks
  • The font styles are Arial, Helvetica, and Verdana
  • The font Color is white
  • The font face is Bold
  • Text-decoration is underlined except for active
b. Hover
  • The font styles are Arial, Helvetica, and Verdana
  • The font color is #091E63
  • The background color is white
  4. Div IDs
  1. The #banner ID defines the elements within SSI for the banner on top of every Web page.
  2. The #menu ID is used for the menu links at the top of every Web page under the banner.
  3. The #modified ID is used for the date the Web page was modified on every page.
  4. The #container IDs are used as a wrapper with a navy and tan background image that contains the div page elements including the navigation side menu and content, and is modified based on the width of the navigation div.
  5. The #navigation IDs define the elements in the navy background side menu based on the width of the navy background.
  6. The #content IDs define the elements in the navy background side menu based on the width of the content area, and the left margin defines the location of the text.
  7. The #footer ID defines the elements located within SSI at the bottom of the Web page, including the drop-down menu.
  8. The #navydecimal and #list IDs are used for ordered lists.
  9. The #red, #navy, and #tan IDs are used for colored boxes that contain text within the Web page.
 5. Classes

Textcenter is a class used to center align text. Textright is a class used to right align text. Floatingimage is a class for the placement of an image left aligned and text wraps around the image. Right is a class for the placement of an image right aligned and text wraps around the image. The bg325 class is for the cell background on the links page in a subWeb.

  1. Steps for Using the Internet Page Template

    1. The steps for using the Internet page template are outlined below.
      1. 1. If you are creating an additional page for your Web site, copy the template from the templates folder and paste it into the root of your Web site. Save the page using .asp extension and the assigned prefix. For example, the home page is prefixmain.asp, and the prefix assigned to Allied Health is 'ah' so their designation would be ahmain.asp. The page name cannot be over eight characters in length and should be descriptive of the content on the Web page.
      2. The browser will not show the banner until the pages are renamed with the asp extension.
      3. 2. Confirm the path of the style sheet in the HTML code. It should be located right above the ending head tag "</head>" and read <link rel="stylesheet" type="text/css"href= "../global.css" >
      4. For Web pages that are located within a folder the path would be href="../../global.css.
      5. 3. Change the page title to reflect the page content by right clicking on the Web page in design view.
      6. 4. Rename the banner include file in the HTML code to reflect the appropriate subWeb name by clicking on the HTML code tab. For example, the subWeb name for Allied Health would be ahbnrB.inc. The include file is located after the body tag and is named generic.inc.
      7. 5. Replace all of this text with page content (see Section 4, Content Placement).
      8. 6. For the links page, insert hyperlinks in the left column.
      9. 7. Format the content. The browser will not show the banner until the pages are renamed with the asp extension.
  2. Content Placement

    1. There are three ways to place content on a Web page.
  1. Type content directly on Web page.
  2. Use content from a Word document by following these steps.
  3. Save the Word document as a .txt file
  4. When the file Conversion dialog box opens, select "other encoding" and "USASCII" under " text encoding "
  5. Click OK
  6. In FrontPage, place the cursor where you want text to go on the Web page
  7. Choose Insert >file>locate text file on computer>Open
  8. Choose the option "Normal paragraph with line breaks"
  9. Format the content using classes
  10. Copy text from a Web page that exists, paste the copied text into Notepad, copy the text from Notepad, and paste it into the new Web page
  1. Microsoft Word creates additional styles that conflict with cascading style sheets. Saving your Word document or existing Web page with formatting tags as a text file removes all of those Word styles, so that when you insert the text file into your Web page the styles from the College's style sheet will be properly utilized. The style sheet automatically sets the font size, style, and color for your Web page content. If you need further formatting such as bold or italicized text or alignment, refer to the formatting content instructions in Section 5 of this document.
  2. Formatting Content
    1. To bold or italicize text, use strong for bold and emphasis for italicize. Highlight the text, choose Format, choose Font, and select either strong or emphasis under effects. Classes have been created in an external Cascading Style Sheet named global.css for the Chattanooga State Community College Web Site.
    2. If there is a certain formatting that you need for your Web page that is not available in the style sheet, you must submit a work order for a class to be created.
    3. Use classes from the Cascading Style Sheet for formatting your Web page content including center test or page elements and align test around an image. Do not use SharePoint formatting features.
  3. Layout Specifications
    1. Bold typeface should be used cautiously. Bold typeface is acceptable for headers, but after ten words in running text it is difficult to read, especially for people with a vision impairment. Most people tend to skip long sentences or paragraphs written in boldface font.
    2. The underline format should never be used unless it references a hyperlink.
    3. Each line of text should contain no more than an average of 10-12 words on each row. Use div tags or cells to constrain the size of the text so it does not go across the entire screen.
    4. Frames are not recommended due to accessibility incompatibility.
  4.  Web Site Maintenance
    1. Do not rename or relocate a Web page once the Web site has been published to the
    2. College's server.
    3. Keep the Web site content current.
    4. Notify the webmaster of any changes in personnel who have responsibility for Web site
    5. maintenance or content.
    6. Keep files organized.
    7. Save images in the images folder.
    8. Save PDF files in a PDF folder.
    9. To maintain a professional look, overuse of animated gifs is not recommended.
    10. You must obtain permission from other Web sites if you are using their graphics.
  5. Content Guidelines

    1. Create microcontent; use forty to sixty words that describe the main idea of the content.
    2. Use content-driven headlines.
    3. Use the inverted pyramid style of writing, which places the most important information
    4. at the top of the paragraph or page.
    5. Use plain language and avoid jargons and cliches.
    6. Do not use teasers as users tend to ignore them.
    7. Do not use graphics to relay content unless that content is also repeated in the text.
    8. For a content-heavy site, provide links to larger files such as scrolling pages and/or
    9. PDFs.
    10. Use short words such as data for information.
    11. Be concise.
    12. Use bolded keywords.
    13. Use sentence fragments.
    14. Use lists.
    15. Update content regularly.
    16. Edit for one-half word count by eliminating the passive voice, transitional phrases,
    17. prepositional phrases, and any unnecessary wording.
    18. Emphasize only one idea per paragraph.
    19. Shorten content with bulleted lists.
    20. Create short sentences of no more than 11 words.
    21. Create short paragraphs of no more than 3 sentences.
    22. Include contact information.
    23. Proof your content; double-check the spelling and grammar.
    24. Check the content to make sure the message is clear.
  6. Section 508 of the Americans with Disabilities Act and Accessibility
    1. Web sites have to be designed with accessibility for all users. Users with disabilities can be defined as users who have difficulty using computer input and output devices; disabilities may include visual, hearing, or cognitive disabilities. To ensure accessibility to the College's Web site to everyone, the College uses and tests various technologies.
    2. 1. The basic requirements of Section 508 of the Americans with Disabilities Act and accessibility for Web-based Intranet and Internet information and applications are as follows.
      1. Design the Web site so that information in color is also adequately conveyed without color.
      2. Provide the text equivalent for each nontext element by using descriptive alt text tags for every image.
      3. Synchronize equivalent alternatives for multimedia presentation with the presentation.
      4. Design the document so that it is readable even without the associated style sheets.
      5. Provide redundant text links for any image maps or other navigation objects used.
      6. Use client-side image maps rather than server-side image maps.
      7. Provide row and column headers for tables containing DATA.
      8. Provide code to associate data and header cells in data tables having two or more logical levels of row or column headers.
      9. Avoid screen flicker in color or graphics with a frequency greater than 2Hz and lower than 55Hz.
      10. Provide text-only pages when compliance is not possible any other way; update text-only pages as frequently as the corresponding main page.
      11. Provide functional text when a script is used to display content or create interface elements.
      12. Provide a link to a page that complies with Section 508, Subpart B, § 1194.21(i) when a page requires an applet, plug-in, or other application be present on the client system to interpret the content. Section 508, Subpart B, § 1194.21(i) states "Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element."
      13. Provide form directions and label form elements that allow completion and submission of form through assistive technology.
      14. Provide a method to skip repetitive navigation such as hidden skip to content link, skip to navigation link, or skip to site map link in top of page code with anchors in template.
      15. Alert the user when a timed response is required and give the user sufficient time to indicate more time is required.
  7. Accessibility solutions
  1. Accessibility solution to item 9.1.1 above: Design the Web site so that information in color is also adequately conveyed without color. Use alternate or 'alt' tags for images; provide a meaningful text representation of the images.

  1. Accessibility solution to item 9.1.2 above: See the above image.
    1. Accessibility solution to item 9.1.5 above: Provide redundant text links for any image maps or other navigational objects used (see http://www.boroarts.org). On long pages, redundant text links are also user-friendly since users do not have to scroll back to the top to find the navigation.
    2. Accessibility solution to item 9.1.7 above: Provide row and column headers for any tables containing DATA (see the following example).

  1. The code for the preceding example is:
<TABLE BORDER="1" SUMMARY="This table lists amount of money raised
and spent by the major party candidates in the Hardball election">
<CAPTION>Hardball 20th Century Fundraising (or a sample table to illustrate our point) </CAPTION>
<TH id="t1">Candidate</TH>
<TH id="t2">Amount Raised</TH>
<TH id="t3">Amount Spent</TH>
<TD headers="t1">Candidate 1 </TD>
<TD headers="t2">$193,088,650</TD>
<TD headers="t3">$185,921,855</TD>
<TD headers="t1">Candidate 2 </TD>
<TD headers="t2">$132,900,252</TD>
<TD headers="t3">$120,371,857</TD>
  1. c. Accessibility solution to item 9.1.13 above: For forms, provide a label before the form object and associate the label to the form object in the code (see the following example).

<label for="FirstName">
First name:
<input name="fn" type="text" id="FirstName">
<label for="SecondName">
Second name:
<input name="sn" type="text" id="SecondName">

  1. d. Accessibility solution to item 9.1.14 above: Provide method to skip repetitive page
elements or navigation (view source on this page). Place this code at the start of your
page (make sure you have a 1x1 pixel transparent gif to reference).

<a href="#content">
<img src="../images/spacer.gif" alt="Skip to Content" width="1" height="1"
<a href="#navigation">
<img src="../images/spacer.gif" alt="Skip to Navigation" width="1" height="1"
<a href="sitemap.htm">
<img src="../images/spacer.gif" alt="Skip to Site Map" width="1" height="1"
<a name="content"></a> - place this code right before your content
<a name="navigation"></a> - place this code before your main navigation (probably
the utility navigation if it is text)
  1. Visual disability
    1. Accessibility solutions for visual disabilities include the following.
  1. Provide ALT tags within the HTML code, containing no more than 8 to 10 words, describing the image for the text readers.
  2. Use a null value in the ALT tag for decorative images to prevent a slowdown of the text reader. Otherwise the reader will let the user know there is an unknown image present, which could leave the user guessing what is on the Web page.
  3. Avoid busy backgrounds.
  4. Contrast background and text colors.
  5. Simplify scanning of long pages with Heading tags <H1> that specify the level of importance for various topics. Also, include hypertext links.
  6. Use relative font sizes set to a percentage of the default font size.
  7. Avoid using frames, as it is difficult for people with screen readers to navigate frames. It is also difficult for search engines to index Web pages created in frames.
  8. Avoid combinations of red and green for colorblind people (8-12% of the population).
  9. Do not use tags like <blockquote> to get the appearance of an indent. Screen readers may indicate the material is a quotation when it is not.
  10. Use the summary attribute set to null if you must use tables for layout. For example: <table summary = " "> Do not use table headers for columns or rows.
  11. Use the summary attribute to describe the contents of the columns and rows to the user for tables used for data. Use the scope attribute to describe more complex relationships among data.
  12. Make sure a screen reader will read the table in an order that makes sense to the user. Use a validation tool that will show you the order that the cells will be read by a screen reader.
  13. Avoid flashing and flickering graphics and text. Flickering items trigger seizures in people who have seizure disorders.
  14. If you have a graphic you must use that flickers, create a separate link to it with a warning that it flickers.
  1.  Hearing impaired
    1. To provide accessibility for people with hearing impairment, provide text version transcripts or captioning for audio.
  2. Speech and motor disabilities
    1. Voice-activated user interfaces, such as Quadriplegic and Palm pilot, are becoming more popular with people who are unable to use a mouse or keyboard. Accessibility solutions for speech and motor disabilities include the following.
  1. Simplify navigation.
  2. Avoid "click" "click here" and "click again."
  1. Cognitive disabilities
    1. Accessibility solutions for cognitive disabilities include the following.
  1. Provide comprehensible content.
  2. Simplify navigation.
  3. Provide a site map and search functionality.
  4. Include hypertext links and headings in long documents.
  5. Chose typestyles that increase reading comprehension.
  6. Use san-serif fonts such as Ariel, Helvetica, and Verdana. In the online environment, these fonts are easier to read.
  7. Test Web pages for accessibility, and validate the HTML.
  1. Web Site Content

    1. The purposes of the Web content are to promote the college, increase retention, and to conduct the business of the College.
    2. Web content roles - The following explanations define the roles that apply to the management of the Web site content.
  1. The Web Content Responsible Person is the person responsible for the accuracy of the Web content for the College Web site. This person is appointed by the division Vice President.
  2. The Web Content Approval Person is the person who approves the content for the College Web site. This person is appointed by the division Vice President.
  3. The Web Site Access Person is the person who updates content for the College Web site using Microsoft SharePoint Designer. The Web Site Access Person is given permission to access a particular area of the College Web site located on the development server and to make updates to the Web content.
  4. The Web Site Access Person must have knowledge of Cascading Style Sheets, Include files, HTML, and SharePoint Designer
  5. The Web Site Access Person must receive Web site training from the webmaster.
  6. The Web Site Access Person must adhere to the Web policies and procedures established by the College.
  7. The Web Site Access Person's Web access privileges will be removed if the above criteria are not followed.
  8. The Web Content Responsible Person, Web Content Approval Person, and Web Site Access Person may be the same person.
  1. 2. Web content review process
  2. The following guidelines define the Web content review process.
    1. a. The webmaster must send an e-mail reminder three times a year to the Web Content Responsible Person to review the Web content.
    2. b. To have updates completed by semester registration, work orders must be received by March 1, June 1 and October.
    3. c. The guidelines for content review for accuracy by the Web Content Responsible Person are as follows.
  • The content is reviewed three times a year during the following times.
  • February 1 to March 1
  • June 1 to July 1
  • October 1 to November 1
  • The Web Content Responsible Person receives e-mail approval from the Web Content Approval Person to make any required changes.
  • The Web Content Responsible Person submits a work order request for updates to be completed by Marketing. One week should be allowed for code review and publishing completion.
  • The Web Content Responsible Person forwards the e-mail approval, along with any necessary files for updating, to the webmaster.
  • The webmaster sends a link to the content changes by e-mail to the Web Content Responsible Person to proof for accuracy.
  • Once the webmaster receives accuracy confirmation, the Web site is published from the development server to the College delivery server.
  • The completed work order confirmation is e-mailed to the Web Content Responsible Person by the webmaster.
  1. The guidelines for content review for accuracy by Web Site Access Persons are as follows.
  •  The content is reviewed three times a year during the following times.
  • February 1 to March 1
  • June 1 to July 1
  • October 1 to November 1
  • The person responsible for updating the Web content receives e-mail approval from the Web Content Approval Person.
  • The Web Content Approval Person submits a work order for updates to be published and forwards e-mail approval, along with any necessary files for updating, to Marketing.
  • The webmaster reviews and approves the HTML code and the Web standards. The content is published to development server, and then published to the College delivery server. One week should be allowed for code review and publishing completion.
  • The webmaster e-mails the completed work order confirmation to the Web Content Responsible Person.
  1. New Web content development
  2. New Web Content Development is defined as a new Web site or new sections of an existing Web site.
    1. New Web content development requirements
    2. The guidelines for new Web content development are as follows.
  1. Complete a new content approval form.
  2. Obtain the required signatures.
  3. The Web Content Approval Person submits a work order for the Web request that confirms it is all right to develop the new Web content.
  4. All content must be approved by Marketing prior to development.
  5. The new Web content is developed by the Web Site Access Person or Marketing. The requester should allow 60 days for new Web content development by Marketing.
  6. The new Web content development is created on the test server.

 7. Once the Web content development is completed, these guidelines are followed.

  1. The Web content is reviewed and approved by the Web Content Approval Person who then submits the work order to Marketing.
  2. The Web content is reviewed and approved by Marketing.
  3. The webmaster reviews and approves the HTML code and the Web standards. The content is published to development server, and then published to the College delivery server. One week should be allowed for code review and publishing completion.
  4. The webmaster e-mails the completed work order confirmation to the Web Content Responsible Person.
  1. Evaluation of Web content for improvement
    1. Web traffic statistics will be tracked and analyzed annually separated out quarterly by division. A report will be presented to Web Content Approval Person to determine if content is still valuable information, if content should be revised, and if content should be removed.
  2. Social Networking Site Development
    1. Special considerations are applied to any development of material for social networking providers like MySpace, Facebook, Twitter, or other social networking providers. The following guidelines apply to social networking sites.
  1. No individual faculty, staff, or student is allowed to create an individual presence using College resources. All sites must represent the College or a department.
  2. A single person must be designated as the responsible person for any Web site created for a social networking provider.
  3. Developers of material for social networking Web sites must obey all policies and procedures that apply to the development of material for the College's own Web site.
  4. Any violation of the College's Web site development standards in a social networking site related to the College may result in the site being shut down.
  1. TigerWeb Management Policy
    1. The Chattanooga State Community College TigerWeb is a secure, single sign-on, Web-based service that provides a single point of access to resources that support end users in their Chattanooga State employee roles or student roles. Users can personalize TigerWeb to provide access to the information, tools, and services that they personally need to meet the demands of job or school successfully.
    2. General policies -The general policies that govern TigerWeb are stated in the following guidelines.
      1. Addition of policies - During the implementation phase and prior to TigerWeb "go-live," several subcommittees of the TigerWeb implementation team are working on functional (as opposed to technical) policies. At the end of the implementation process, these documents will be incorporated into this policy.
      2. Purpose of the policy - TigerWeb maintenance policy will be used to define procedures for maintaining Chattanooga State's Web portal. The policy is intended to address TigerWeb content and appropriate usage. It is not intended to address technical issues such back-ups, disaster recovery, Internet protocol issues, or other technical issues. TigerWeb will fall under the Computing Center's current plan for backups and disaster recovery.
      3. Administration and amendment of the policy - This policy will be the continuing responsibility of the Technology Advisory Committee (TAC). This committee will review this policy and discuss policy revisions at least twice annually (or more frequently if needed). The TAC will incorporate any revisions that it approves into this document.
        1. The TigerWeb Content Administrator should be an ex-officio member of the TAC committee.
        2. Any authorized TigerWeb user may make comments or suggestions by completing a form on the "Feedback" channel. Questions regarding issues not covered in this policy or any suggestions for amendments may be directed to any member of the TAC. Information regarding changes to igerWeb will be published prominently via the "Portal News" channel.
        3. This policy shall remain in effect unless and until appropriate amendments are made and approved by the TAC and the President's Cabinet.
        4. Conformance with state, Tennessee Board of Regents, and other Chattanooga State policies
        5. This policy is to be compliant with the following policies.

In the case of a discrepancy, these policies will take precedence in the following order: (1) state policy, (2) TBR policy, and (3) Chattanooga State policy.

  1. ADA compliance - On its official Web pages, including TigerWeb pages, Chattanooga State strives to provide equal accessibility to all persons and to conform to the Americans with Disabilities Act (ADA) accessibility standards. All text and image use should conform to these standards. For specific applications of this standard, refer to ADA Home Page - ada.gov - Information and Technical Assistance on the Americans with Disabilities Act.
  2. Support and training - Faculty and staff training will be provided by Computer Services personnel. Student training will be offered by Computer Services personnel and library staff. Technical support will be provided by Portal Support Team. Functional support will be provided by the Computer Services Helpdesk and the Library Reference Desk.
  3. User access
    1. The policies that govern user access for TigerWeb are as follows.
      1. Access and purpose - TigerWeb is a conduit to facilitate access to a variety of information technology resources.
    2. Responsibility for access - The following guidelines address responsibility for access to TigerWeb.
      1. The Chattanooga State Computer Services Department and the TigerWeb Support Team are responsible for creating and administering TigerWeb accounts.
      2. The Portal Steward is responsible for defining the structure and characteristics of access groups with appropriate guidance from the Technology Action Committee and TigerWeb Support Team. The Portal Steward will fully document the access group structure and assure knowledge transfer and sustainability of this process.
      3. The Computer Services Helpdesk is responsible for TigerWeb login or account issues. If the Helpdesk staff is unable to resolve the issue, a work order will be created and the issue will be assigned to the appropriate analyst.
      4. Account creation  - As part of the employee orientation process, the TigerWeb Support Team will assign faculty and staff users their portal user names and default passwords. User names and passwords will only be issued after the appropriate forms have been signed and approved. Students will be notified of their user names and passwords via mail once they acquire the role of "Student" in the Banner system.
    3. Password policy
      1. The policy on changing TigerWeb passwords will conform to Banner requirements. Users' default TigerWeb password is their Self-Service Banner Pin Number. Employees should contact Human Resources to have their TigerWeb PIN reset. Students should contact the records office to have their TigerWeb PIN reset. If a user has access, passwords can be changed within Banner Self-Service.
    4. Access consistent with the college's FERPA / security statement - Members of the Chattanooga State community will be able to access TigerWeb using their Chattanooga State computer accounts in accordance with the Chattanooga State Community College FERPA / security statement.
    5. Inappropriate access - When accessing TigerWeb, users will exercise privileges assigned to their user role(s). It is not acceptable for individuals to circumvent or attempt to obtain access to services or information not appropriate to their authorized role(s).
      1. Default user roles - Accounts will be created and activated based upon information associated with each user's Chattanooga State computer account. Default user roles (access groups) will be automatically assigned to students, faculty, and staff according to Banner policy.
      2. Exceptions to default user roles - A user can have multiple default user roles. For example, a user could be a faculty member and a student as well as a portal publisher, so this user account would therefore be affiliated with three roles.
        1.  Anyone requesting the creation and assignment of roles other than the defaults must fill out a Computer Services work order, which must be signed by the requestor's supervisor or dean and the Portal Steward.
        2. New user role definitions will only be created and assigned by the Portal Support Team after verification of appropriate need and approval by the Portal Steward.
        3. Users requiring more than the default type of access should submit requests through the Computer Services work order system when a change is required to their portal account because of a role change at the college. All TigerWeb help requests shall be forwarded directly to the Portal Support Team.
        4. Changing user roles - Any changes in a user's status at Chattanooga State may affect that user's Chattanooga State computer account. These changes will automatically be reflected in the user's TigerWeb account. These changes may include (among other alterations) creating a new account, deactivating an old account, completely deleting a person's account from the system, and / or assigning a set of default user roles different from those a user was previously assigned.
        5. Users must submit a change request through the Computer Services word order system when the need arises for a role change. Such requests will be routed to the Portal Support Team for action.
        6. Examples of situations requiring a change in access privileges include:
  • A user leaves one department and is hired by another department.
  • A user is named the new Targeted Message Publisher for the Registrar's Office, and his or her predecessor no longer works at Chattanooga State.
  • A change in policy or procedure at the unit level results in changes in access privileges in the Portal.
  1. Terminating access
TigerWeb accounts will be terminated in accordance with existing policies and procedures for account termination. At a minimum, user accounts flagged for deactivation will fail authentication if a user whose account has been terminated attempts to access TigerWeb.
Users with special circumstances are responsible for contacting the Chattanooga State Computer Services Department prior to change in status to avoid automatic account termination. Such requests shall be forwarded directly to the Portal Steward who will engage the appropriate parties to evaluate the situation and make a decision as to the appropriate access.
  1. Disclaimer concerning access to systems beyond TigerWeb
    1. Since TigerWeb is an information gateway providing easy access to many other systems, some non-TigerWeb systems may require their own unique user authorization and authentication protocols, usually in the form of a specific user ID and password. Usage and access policies for these systems, along with their support services, exist outside the supported TigerWeb environment. Details onthe policies, procedures, and support structures of these systems are beyond the scope of this policy.
    2. Tabs - The policies that govern tabs for TigerWeb are as follows.
      1. Access categories and tabs - Access categories and tabs include "All Users," "Faculty/Staff," and "Student."
        1. The "All Users" access category should contain these same tabs for everyone:
  • Home
  • How Do I
  • My Banner
  • My Tab
  • Library
  • My Courses
  1. In addition to the tabs defined in the "All Users" section, the "Faculty/Staff" access category should include the following tabs:
  • My Work
  • My Banner
  1. In addition to the tabs defined in the "All Users" section and the "Faculty/Staff" section, the "Student" access category should also include the following tab:
  1. My Info
  1. The "Library" tab, "My Courses" tab, and "My Tab" tab should be available to faculty, staff, and student users. The "Library" tab should contain all of the resources available through the Chattanooga State Kolwyck library. The "My Courses" tab may be eliminated Chattanooga State decides not to implement the "Course Studio" software since there is also an icon available to access other course management software for Chattanooga State. The "My Tab" tab is for each user to personalize the information.
  2. The "Home" tab should contain the same channels for faculty, staff, and students.
  1. Campus Announcements
  2. Personal Announcements
  3. My Calendar
  4. Activities Calendar
  5. Academic Calendar
  6. E-mail
  7. Promo
  8. Survey / Poll
  9. News Feed
  10. Quick Links
  11. Portal News
  12. Weather
  14. Word of the Day
  15. Weather
  17. Word of the Day
  1. Faculty / staff tabs
    1. The policies that govern Faculty/Staff tabs for TigerWeb are as follows.
      1. 1. The "How Do I" tab
      2. The "How Do I" tab for faculty and staff should provide information for how to accomplish tasks and where to find information. This tab should contain the following channels.
  • Quick Links
  • Helpdesk
  • Where do I find
  • Courses
  • Luminis Tutorials
  • Business Office
  • Human Resources
  • Getting Started with portal
  • Banner essentials
  • Media Services
  • Faculty staff Training
  • Students
  • TTC
  1. 2. The "My Work" tab
  2. The "My Work" tab for faculty and staff should provide information related to work at Chattanooga State. This tab should contain the following channels.
  • Forms
  • Human Resources
  • Travel
  • Advising
  • Academic Calendar
  • Student
  • Policies & Procedures
  • College Initiatives
  • Quick Links
  1. 3. The "My Banner" tab
  2. The "My Banner" tab should contain banner information.
  • SSB
  • Banner Channels
  • INB
  • Quick Links
  1. Student tabs

    1. The policies that govern student tabs for TigerWeb are as follows.
      1.  1. The "How Do I" tab
      2. The "How Do I" tab should contain the following channels.
  • Registration
  • Help
  • Quick Links
  • Records
  • Financial Aid
  • Academics
  • TTC
  • Account Information
  • Courses
  • Forms
  • College Services
  • Advising
  • Getting Started in the portal
  • Learning Resources
  • Training
  1. The "My Info" tab
    1. The "My Info" tab should contain the following channels.
  • Registration
  • Financial Aid
  • Quick Links
  • Academics
  • Account
  • Services
  • Resources
  • GPA Calculator
  • Forms
  • Career
  • Continuing Ed
  1. Channels
    1. The policies that govern channels for TigerWeb are as follows.
    2.  1. Channel responsibility
  • Student information: Wanda Faulkner and Josh Wilson
  • Academic information: David Haddock and Deanna Swinney
  • Banner: Donna Appleget, Bruce Carlyle, and Mike Rogers
  • Training and tutorials: Percy Parakh
  • All other: Vickie Boles, Donna Appleget, and Bruce Carlyle

The portal support team may designate others to assist as necessary.

  1. Channel opt out
    1. The University of Memphis consultant recommended that individual users be able to opt out of viewing the majority of the TigerWeb channels. Therefore, the committee recommends that only the following channels be locked so that they cannot be removed from the view screen by the individual users:
  • Home Tab
  • Campus Announcements
  • Personal Announcements
  • E-mail
  • Feature of the week
  • Portal news
  • My Banner tab
  • INB
  • SSB
  1. Channel creation process
    1. The channel creation process must follow these guidelines.
  • The TigerWeb Support Team shall consist of the Director of Computer Services, the TigerWeb System Administrators, and the TigerWeb Content and Layout Administrator.
  • A TigerWeb channel is a customized method for publishing information for some subset of the TigerWeb population. The user may select channels from an approved list available in the TigerWeb environment. These channels may originate from Chattanooga State and non-Chattanooga State sources. Chattanooga State channels can be made available by authorized units within Chattanooga State upon approval as described below. Channels originating outside of Chattanooga State are made available only after being approved as described below.
  • Anyone who wants to have a new channel created should submit a "Channel Request Form" to the Portal Support Team. This form will be available in both the "Forms" channel and the "Portal Feedback" channel.
  1. Channel creation requirements
    1. A channel must:
  • Benefit the campus community
  • Meet "Acceptable Use Policy" and other TBR and campus policies as applicable
  • Enhance communications
  • Provide easy access to tools needed to perform the work of Chattanooga State
  1. Channel creation process
    1. The channel creation process is as follows.
  • Those seeking to publish a channel are strongly encouraged to discuss channel creation issues with the TigerWeb Support Team prior to submitting their Channel Request Form.
  • The policy for channel development is to make TigerWeb as customizable as feasible. Thus, strong justification for locking a channel or for requesting special placement must be presented at the time of the request.
  • The TigerWeb Support Team will review requests at least twice a year, and more frequently if needed, in light of the entire TigerWeb framework.
  • The TigerWeb Support Team will promptly communicate to the requestor its decisions and its rationale for acceptance or nonacceptance of the request.
  • All decisions will be final.
  1. Channel creation form
    1. The "Channel Creation" form will require the following information, and additional information as required.
  • Name of person or group requesting the creation of the channel
  • Date of the request
  • Requested name of the channel
  • Scope of content intended for the channel
  • Rationale for creating the channel
  • Intended audience that will benefit from viewing the channel
  • Requested placement for the channel on default screen layouts (tab? screen placement? status: locked, movable, or removable?)
  • Rationale for the requested placement of the channel and its status
  1.  Channel alteration
    1. Approved channels are not to be modified in scope or intent from the original authorization. Since any changes to the channel can affect TigerWeb performance, any modifications to the channel must be approved and tested prior to publishing.
    2. Channel content - Channel content shall be limited to that authorized for the purposes of doing the business of the College, promoting communication within the College, and providing information and resources for authorized TigerWeb users. Channels must not promote activities that are illegal or that violate the rights of others, nor should they support commercial activities not associated with the College.
    3. Channel publishing - Once channels have been approved and developed, the Portal Steward, TigerWeb Support Team, and channel publishers will assure that quality assurance testing is performed prior to publishing. The Portal Steward is the only user authorized to publish TigerWeb channels on the TigerWeb production server. Authorized channel publishers may develop and test channels on the TigerWeb test server. Each channel owner is responsible for the content within his or her channel and must comply with all applicable Chattanooga State policies, including issues of copyright, responsible language, and other items listed in this policy.  
    4. Channel subscription - Chattanooga State has two required channels for all TigerWeb users: the "Campus Announcements" and "Personal Announcements" channels. These are fixed in location on the main page of all TigerWeb users and cannot be changed. "Campus Announcements" are for all campus groups (administrators, faculty, staff, and students). Announcements that apply only to some campus groups should be sent via the "Personal Announcements" channel. Users can choose all other channels to which they wish to subscribe from an authorized list available to them on their Content/Layout screens when they click on the "Add Channel" button.
    5. Channel termination - Channels that are not effectively maintained or are in violation of College policies will be subject to removal from the TigerWeb environment. The TigerWeb System Administrator will compile a list of those channels that are not being maintained. The administrator will notify the people responsible for maintaining the channels and the owners of the channels at least two weeks before the TigerWeb Support Team meets. If no changes are made by the time for the review meeting, the channels will go on a deletions list that will be submitted to the team at the time of the review. TigerWeb policies and content will be reviewed at the semiannual review by the TigerWeb Support Team.
  2. Groups
    1. TigerWeb Groups are available to Chattanooga State students, faculty, and staff for campus committees, groups, and clubs for creation of home pages with space for a calendar, file storage, e-mail, links, and a message board. Group content must be related to the group topic and conform to the purpose, goals, and mission of Chattanooga State Community College. A new group should be created if the focus of the group changes.
    2.  Initial categories of groups - Initially, group categories will correspond with targeted content channel categories. New categories can be added with the approval of the Portal Support Team. Admin blocked groups can be created only with the recommendation of a Chattanooga State vice president.
    3. Criteria for creating groups - Groups are authorized and may be established in TigerWeb Groups only if they meet the necessary criteria. These criteria include: -
      1. The group must be composed of students ("Student Groups") or employees of the College ("College Groups") and it must be used for activities related to College functions.
      2. Groups must not promote activities that are illegal or that violate the rights of others, nor should they support commercial activities not associated with the College. (See the College's Information Technology Responsible Use Policy.)
      3. Student Groups may be created only if they are associated with a College sanctioned group of students or if the group leader has obtained permission from the Dean of Students. Groups must govern themselves in accordance with the College's current Information Technology Responsible Use Policy and the guidelines for student organizations as outlined by the Division of Student Affairs.
      4. Students should seek a College sponsor, such as Student Life, Athletics, or an Academic Department. That sponsor should then follow the instructions for Faculty/Staff.
    4. College Groups may be created only for College chartered employee governance groups (i.e. the Faculty Senate and the Employee Support Committee), college units, or committees. College Groups may also be created for Project Workgroups as approved by the President or a Vice President to facilitate work on specific projects defined by the College. Faculty or staff may submit a request online. The submitting Faculty or staff member will be notified within three to five business days of the status of the request.
    5. Appeal process if the group creation request is denied
    6. If a group creation request is denied by the Groups Administrator, the requestor can write a rationale stating the need for the group. The requestor must then submit that rationale along with a copy of the current TigerWeb Groups Creation Policy to his or her dean or student advisor, ask the person to endorse the rationale, and send it to the TigerWeb Groups Administrator.
    7. Responsibilities of group leaders
    8. The group leader is responsible for content on the group's homepage, announcements, news, photos, links, files, message board, and calendar. The group leader may designate group members to provide content, but is still ultimately responsible for the content. The group leader must specify in the original Group Creation Request) who will be allowed to access the group. A current group leader or member of the group can recommend a replacement group leader if the group leader is unable to complete the mission or the business of the group. The new group leader will be approved using the guidelines established in the TigerWeb Groups Creation Policy. Group leaders must attend a training session led by the campus Computer Training Coordinator.
    9. Group e-mail
    10. Group e-mail will be limited to the topics within the group or to other group members. Group links and files must be relative to the group's topic, must not promote activities that are illegal, must not support commercial activities that are not associated with the College, and must not violate the rights of others.
    11. Group announcements - Announcements must be on the topic of the group or related to the group's schedule or function. No personal messages will be allowed.
    12. Size limit for group files - No file posted for a group can exceed 10 MB. The portal only supports .gif and .jpeg image files. The portal server will downsize all uploaded photos and images to an average size of 40K.
  3. Targeted announcements
    1. The guidelines for targeted announcements for TigerWeb are defined below.
    2. Responsibility - Campus communication will funnel through TigerWeb, not campus e-mail. The designated staff person will receive daily announcements via e-mail and paste them into a targeted announcement in TigerWeb.
    3. Two channels for targeted announcements - Two channels in TigerWeb can be used for announcements: "Campus Announcements" or Personal Announcements." The campus community will send announcements to the designated staff person who then will publish them on the "Campus Announcements" channel or on the "Personal Announcements" channel on the "Welcome" tab. "Personal Announcements" will be reserved for announcements to targeted groups.
    4. Campus announcements - The "Campus Announcements" channel will be used for announcements to the entire campus, including students. Only designated personnel will have the access necessary to send out campus announcements.

Messages for broadcast on the "campus announcements" channel in TigerWeb will be messages of a general nature applicable to all faculty, staff, and students on campus. Examples include campus closings, campus construction updates, emergency announcements such as unexpected computer or phone system failures, emergency weather notifications, registration and financial aid deadlines, fee payment deadlines, and any other messages approved by the president.

  1. Personal announcements
    1. TigerWeb users will receive announcements from groups to which they belong through their personal announcements channel. For instance, if a user is a member of the Faculty Development group and someone in that group sends a message to the entire group, the user will see this message in personal announcements. Only members of that group will see the announcement; anyone not in that group will not see the announcement.
      1. Items appropriate for faculty/staff or student "personal announcements" include faculty, staff, and student accomplishments, event notifications, and reminders (in moderation), press releases from public relations, retirement/goodbye receptions, information on noncredit classes, job postings,
      2. fundraising events with College accounts, and PIE partner fundraisers.
      3. b. Items that are not appropriate include sympathy news, medical reports, personal expressions of gratitude, baby and wedding shower invitations, lost and found items, as well as community events and fundraisers not affiliated with the College. If warranted, a group can be created for these types of announcements and members of the campus community can decide individually if they want to join and receive messages from the group's moderator in their "personal announcements" section.
      4. Items not allowed in targeted announcements
    2. In accordance with state policies, personal "for sale" items will not be broadcast on TigerWeb.
  2. Forms
    1. The policies that govern forms for TigerWeb are as follows.
      1. Standard format - The standard format for initial startup of all forms on the TigerWeb "Forms" channel should be a PDF file so that users can download the forms and fill them in electronically.
      2.  Initial forms - Forms that are currently on CSWeb and the Chattanooga State Web site should be the initial forms to be placed on the channel by the system analyst.
      3. 3Placement of forms - Forms should be presented and accessed through the "Forms" channel where they can be accessed alphabetically or by categories.
  3. TigerWeb portal glossary
  1. Access groups (also known as user roles): A common set of privileges and/or criteria that can be assigned to multiple TigerWeb users.
  2. Authorized portal user (also known as TigerWeb user): Any individual affiliated with Chattanooga State who has obtained TigerWeb access through official College procedures as specified or referred to in this Policy.
  3. Availability: The percentage of time during which an authorized user can retrieve information when needed. Information can be unavailable due to destruction/erasure, system or network outage, or overload.
  4. Calendaring: The process of maintaining and viewing a schedule of user-defined events and activities through the utilization of portal tools.
  5. Campus announcement: A targeted announcement approved by College Administration and delivered via a protected TigerWeb channel to all TigerWeb users.
  6. Channel: A method of providing related data in a bordered presentation format with click-through access to expanded content or Web resources.
  7. Channel owner: The person responsible for approving the content presented in the channel and the currency and accuracy of the information as well as making sure it does not violate any of the policies mentioned in this document.
  8. Chief content and layout administrator: A user who has been granted authorization for publishing channels to the production TigerWeb portal.
  9. Content administrator: A user who has been granted authorization to develop channels and the content in them.
  10. Departmental policy: Policy approved at the department or unit level that complements but does not supersede College-wide policies.
  11. Group: A set of TigerWeb users who share membership in a group portal.
  12. Group category: A classification that represents a subset of groups within the TigerWeb Group Index.
  13. Group Index: A list of group categories available in TigerWeb.
  14. College-wide policy: Policy approved by authorized administrators that applies to the entire Chattanooga State Community College community.
  15. Messages: Targeted announcements delivered in a portal channel interface and/or e-mail based upon specific attributes such as user role, major, or group membership.
  16. Messages channel: A channel for displaying messages targeted to any subset of TigerWeb users.
  17. PDA (personal digital assistant): A hand-held computer that allows one to store, access, and organize information.
  18. Portal: A personalized single point of access to consolidated web-based digital content and collaborative tools organized for straightforward usage.
  19. Portal support team: Those persons authorized to maintain the TigerWeb portal and its content. Includes, but is not limited to, the Director of Computing Services, the TigerWeb (Luminis) System Administrators, the Chief Layout and Content Administrator for TigerWeb, and the College Webmaster.
  20. Portal steward: The person that the Portal Support Team is authorized to report to.
  21. Public group: A group that any TigerWeb user is able to join.
  22. Restricted group: A group whose membership is subject to review and approval by the Group leader before a user is allowed to join since membership in that group is restricted.
  23. Targeted announcements publisher: A user who has been granted administrative rights to send targeted announcements.
  24. TBR policy: Policy approved by the Tennessee Board of Regents and which applies to the entire Chattanooga State Community College community.
  25. TigerWeb account: An account issued to all faculty, staff, and students that provides access to the TigerWeb Portal.
  26. User role: A subset of TigerWeb portal users representative of a certain demographic category of users in the Chattanooga State community. For example, "Student" exists as a role within the Portal and contains the subset of Portal users that are defined in Banner to be students. "Faculty" is also defined in a similar way and exists as a role within the Portal environment.
  1. Responsible Use Policy for World Wide Home Pages
    1. In order to encourage sharing of information, creativity, diversity, and technical knowledge within the campus community and beyond, the College offers the use of its facilities for publishing information on the World Wide Web to authorized users of computing resources. Due to system limitations, certain restrictions as to platforms available for WWW publishing and resources allotted may be necessary. Publishers of Web pages must avoid the use of inflammatory or offensive language and symbols in their individual home pages. Due to the public nature of Web publishing, and the increasing number of K- 12 students who are accessing the Web, individual home pages must not contain violent or prurient material, or provide links to sites that contain such material.
    2. Standards for use
      1. Web pages must maintain the highest standards of quality possible and enhance the image of Chattanooga State. The following standards of quality apply to all Chattanooga State Community College's Web pages.
  1. The following must not appear on any of the College's Web pages.
    1. Obscene pictures or profanity
    2. Links to items of an obscene or profane nature
    3. Illegal use of college resources
    4. Copyrighted materials
  2. Web pages must comply with all the College's policies and procedures as well as state and federal laws concerning appropriate use of computers and computer networks.
  3. College resources cannot be used for commercial gain.
  4. College resources cannot be used to advertise noncollege-related functions.
  5. Individual home pages are the intellectual property of the individual; publishers of home pages must refrain from representing their pages as an official College publication.
  6. Use of the College's insignia or logos is specifically prohibited.
  7. Individual home pages are subject to all applicable provisions contained in this policy and/or other applicable institutional policies.
  1. Termination of access
    1. The College may provide resources for WWW pages, but it takes no responsibility for the individual opinions expressed therein. However, the College reserves the right to monitor content and to terminate access to any pages that do not comply with this policy.
  2. Sanctions
    1. Violations of this Policy shall subject users to the regular disciplinary processes and procedures of the College for students, staff, administrators, and faculty and may result in loss of their computing privileges. Illegal acts involving College computing resources may also subject violators to prosecution by local, state, and/or federal authorities.
  3. Disclaimer
    1. As part of the services available through the College's campus network, access is provided to a large number of conferences, lists, bulletin boards, and Internet information sources. These materials are not affiliated with, endorsed by, edited by, or reviewed by the College and the College takes no responsibility for the truth or accuracy of the content found within these information sources. Some of these sources may contain material that is offensive or objectionable to some users.

Approved: Executive Staff, 05/20/09
Approved: President's Cabinet, 05/20/09
Approved: President, 05/20/09
Reviewed and Revised by: Economic and Community Development, 04/06/09