Campus Applications

 

Core Campus Applications

blogs.oregonstate.edu - Campus Wide Central Blogs using WordPress

Campus Map

Drupal, a web content management system

Events Calendar

iOSU

MediaSpace

Multicultural Resource Guide

Search with the Google Search Appliance

Media Manager, a web video management tool.  This tool will no longer be available for uploads, effective June 10th.  Try the new solution for Campus:  MediaSpace


Blogs.oregonstate.edu

Wordpress

Blogs, you've heard about it, and you've read some maybe, and you are thinking, what's the big deal?  Well, blogs are for your story.  In some cases, they are for your site.

If you are a department or unit that needs to tell an ongoing story, don't maintain two separate sites, just maintain a blog.  It's easy to use, easy to edit, and your ramp up is quicker.

Central Web Services provides this core service free of charge to all OSU students, student groups, faculty, staff, and departments.  Check it out at: blogs.oregonstate.edu!

We are using Wordpress as our blog solution.

We encourage everyone to speak up and speak out in their personal blogs, but just as a reminder, use of this application is covered by OSU’s Acceptable Use Policy.

 

WP Help BlogSupport for WordPress can be found in a few different ways:

To get your own blog, visit blogs.oregonstate.edu

 

Plugins

Blogs.oregonstate.edu runs with several Wordpress plugins.  Plugins in blogs.oregonstate.edu come in two forms, those that are enabled on all blogs (and cannot be turned off), and those that can be turned on for an individual blog.

Enabled Site-Wide

CWS has installed two plugins to minimize spam on blogs.  Akismet is used to reduce spam comments.  reCaptcha is also used to prevent comment spam.

To add polling functionality to your blog, we provide a polling plugin, wp-polls.

Individual Blog Settings

Popularity Contest enables the ranking of your posts by popularity, using the behavior of your visitors to determine each post’s popularity.

Sociable will automatically add links on your posts, pages, and RSS feed to your favorite social bookmarking sites

WP-PostRatings adds a rating system for your blog’s posts and pages. 

Google Analytics

Global Site Tags

The blogs.oregonstate.edu Help Blog provides additional details on all of the installed Wordpress plugins.

To request additional WordPress MU plugins, please review our criteria for selecting Wordpress plugins and then contact us using the CWS contact form.

Plugin Evaluation Criteria

Central Web Services reviews all plugins that are included as part of the centralized OSU Wordpress MU installation.  We do this to ensure that blogs.oregonstate.edu remains a stable, secure and supportable product for the campus.  The following are the initial criteria we use to evaluate a plugin.

  • Code Review:
    1. Are there any pending security bugs in the bug tracker?  What are they and how long have they been there?
    2. Is it performing sql queries directly? If so, does the module escape user input?
    3. How does it handle user input? Is it being escaped? Is user input cleaned before printing it out in a page?
    4. Are permissions check in place? Are the checks manual or does the code rely on other core methods?
    5. Is the code well documented? Does it follow a standard?
    6. Is the javascript code and css well structured?  Does it follow follow a standard?
    7. Does it have readme, install and upgrade files?
  • Lifespan/Activity:
    1. How long has this plugin or 3rd party program been around?
    2. How many developers are working on it?
    3. Is there a roadmap? What does it look like?
    4. What is the release life cycle?
    5. What is the average turn around time for critical bugs?
    6. How active are the forums or mailing list discussions?
    7. Do other programs use or depend on this library?
  • Support:
    1. Is there user documentation? Is there documentation for developers?
    2. Is a documentation generation system like phpDocumentor used?
    3. How quickly do the developers respond to requests?
    4. Are newer and older versions of Wordpress supported?
    5. What is the learning curve like?
    6. Is the module usable through the Wordpress interface or does it require users to work with HTML, CSS, theme changes or other advanced techniques?
  • Compatibility:
    1. Does the it conflict with other existing plugins or modules or other updates?
  • Cost/Benefit:
    1. Will the module work with Wordpress MU as is, or would some re-write be needed?
    2. How complex are patches to apply? (# of classes, files, and db tables affected)
    3. What % of our users would benefit from this new module or plugin?
    4. Is there a fee to purchase or use the plugin?
  • Redundancy
    1. Does OSU/CWS already provide this service?
    2. Is this capability already planned for an upcoming Wordpress release or update of a currently supported plugin?

 

To request additional WordPress MU plugins, please contact us using the CWS Help Ticket.

Calendar

Overview

The current OSU Events Calendar was built in March 2006 to provide a long-term web calendar solution for Oregon State University. The calendar was designed in-house to meet the most common public calendaring needs for departments and groups. However, it was realized that no single calendar application could fit everyone's needs, so flexibility and extensibility remained paramount. With data import and export tools, the web calendar serves as a central storage platform for distributed event data. A centralized data source allows individuals to easily find information. Providing export in standard formats allows event data to be accessed and integrated into other web sites and applications.

Features

Enhanced Web Interface

Storage and Data Access

Support

Integrating the Calendar RSS into your website

Central Web Services has written a library to simplify adding OSU Events calendar data to your websites. This script requires PHP to execute. 

If you are using OSU Drupal, integration of the calendar is taught in the Formatting Blocks course.  You do not need to include the file in OSU Drupal.

Update: Drupal sites now come with the Feeds DIsplay module, which makes it very easy to add the News and Events feeds to your site.

View the code or, to use it on your page, download the library, unzip it, and include it on your PHP page:

<?php require_once('calendar_rss.php'); ?>

The library has 2 basic views; a list view suitable for a News or Headlines section on a web page, and a mini-month view useful for linking back to the main OSU calendar site.

The views output simple HTML (a table, for the mini-month, a definition list for the list view) that can be styled via CSS.

More control over the HTML output is possible; this requires a PHP installation that support XSLT (which includes all CWS hosted sites). See Advanced Formatting for a brief description.

A note on performance:

This library makes use of RSS caching when run on CWS hosted sites; for other sites, it might be a good idea to implement some type of caching. Parsing remote RSS feeds on the fly will noticeably slow down your web pages.

List View

A list can be dynamically generated to show the current week's events pulled from the main ('osu') calendar, using this code:

<?php echo minical_list('osu', 'today', 'week'); ?>

today' could also be a date ('20060425'), or include an offset ('today+6', '20060401+13')

'week' could also be one of 'day' or 'month'

The easiest way to show the current month's events would be:

<?php echo minical_list('osu', 'today', 'month'); ?>

Mini-month

The minicalendar is dynamically generated, but uses the 'month' interval instead.

<?php echo minical_month('osu','today','month'); ?>

The minical_month() function accepts the same parameters as minical_list().

For an example of how to style the minimonth, see the minimonth.css stylesheet.

If you don't need feedback about current events on the calendar, it's much faster to build the minicalendar without any event data:

<?php echo minical_empty_month('osu','today','month'); ?>

Advanced Formatting

If the default HTML markup isn't good enough (perhaps you want to show some additional RSS fields, or integrate the calendar data into an page structure), you can control the layout completely by writing an XSL template. Put the XSL template in a file, and pass it into the minical_month function:

<?php echo minical_month('osu','today','week','month_stylesheet.xsl'); ?>

Using the minical_month function, an XSL stylesheet, and any combination of date and range, you can produce your own month, a differently formatted list, or anything else.

A sample XSL stylesheet, for producing a minimonth. Writing XSL is far beyond this page; you should be familiar with XML basics before trying. A web search for XSL tutorial should turn up some useful information.

Campus Map

About the OSU Campus Map

The Campus Map is a tool intended to give an interactive map of the Oregon State University campus.

In Spring 2008,  a complete redesign and overhaul took place to help the OSU Campus Map take advantage of the new web technologies available.  Central Web Services decided to use the Google Maps API and a more responsive ajax-based user interface for the new OSU Campus Map. Central Web Services is committed to supporting users with accessibility needs and a limited non-javascript user interface is provided.

Features:

To experience the campus map for yourself, go to http://oregonstate.edu/campusmap/.

Drupal

Drupal is an open-source content management system (CMS) hosted by Central Web Services for use by the OSU campus.  Drupal allows users with no technical or programming knowledge to create full featured websites. 

CWS provides a centralized installation of Drupal 6, known as OSU Drupal, running a specific set of installed modules.  We keep this installation patched and up-to-date so you don't have to.  If there are specific modules that OSU Drupal does not have and you think would be of benefit to the OSU community, please review our module evaluation criteria and submit a request.

We also provide a core set of customizable OSU themes developed by University Marketing and CWS.  These provide a quick way to give your site an OSU look-and-feel in line with the OSU brand guidelines.  Web Communications provides guidance within the brand guidelines on acceptable customizations of the OSU Drupal themes.  CWS can also build custom Drupal themes from existing graphic designs.  This custom development is done at our standard rates.

CWS offers training on OSU Drupal 6 use and features to the OSU campus.  All of our training is available at no cost.  Visit our training information page to see a description of the courses, or register directly at the Professional Development website.

OSU Drupal is available at no cost to colleges, departments, institutes, groups and projects on the OSU campus.  We provide both development and production Drupal environments, allowing users to create sites before they are live to the public.  To request your Drupal website, please use our contact form.

The OSU Drupal Support list is a mailing list available to all members of the OSU community.  It is a great place to ask and receive answers to Drupal questions. 

Installed Modules

Modules are used to provide features to Drupal.  Modules that are part of OSU Drupal go through an extensive review to ensure security and overall utility to the OSU community.  If you would like to suggest a module for inclusion in OSU Drupal, please review our module evaluation criteria and submit a request.

Central Web Services does our best to ensure that modules included in OSU Drupal will continue to be supported in future versions.  However, the open-source community does not always provide migration paths between version.

OSU Drupal 6 Currently Installed Modules:

  • Administration menu
  • Automatic nodetites
  • Biblio
    • Biblio
    • Biblio - PubMed
  • CAPTCHA
    • reCAPTCHA
  • Content Construction Kit (CCK)
    • Content
    • Content Copy
    • Embedded Audio Field
    • Embeded Image Field
    • Embeded Media Field
    • Embeded Video Field
    • Fieldgroup
    • FileField
    • ImageField
    • ImageField Tokens
    • Link
    • Node Reference
    • Number
    • Option Widgets
    • Text
    • User Reference
  • Caching
    • CacheRouter
  • Core - optional
    • Aggregator
    • Book
    • Color
    • Content Translation
    • Database Logging
    • Help
    • Locale
    • Menu
    • Path
    • PHP filter
    • Poll
    • Profile
    • Taxonomy
    • Throttle
    • Trigger
    • Upload
  • Core - required
    • Block
    • Filter
    • Node
    • System
    • User
  • Date/Time
    • Date
    • Date API
    • Date Copy
    • Date Popup
    • Date Repeat API
    • Date Timezone
  • Gallerix
  • Glossary
  • Image Cache
    • Image API
    • Image API GD2
    • ImageCache
    • ImageCache Actions
  • OSU Drupal
    • OSU Search
    • OSU SSO
    • OSU Update
  • Other
    • Advanced Help
    • Announcement
    • disable form fields
    • Glossary
    • IMCE
    • jCarousel
    • Menu Breadcrumb
    • MIME Detect
    • Nice Menus
    • Path Filter
    • Path Redirect
    • Pathauto
    • Site map
    • Token
    • Transliteration
  • User Interface
    • IMCE
    • IMCE Mkdir
    • IMCE WYSIWYG API Bridge
    • jQuery UI
    • jCarousel
    • WYSIWIG
  • Views
    • Views
    • Views Carousel    
    • Views exporter
    • Views UI
  • Webform

Bibliography Module Setup

Biblio Module, by default, puts the menu link in the navigation menu and is only visible to Administrators of the Drupal site. Depending on your theme and if you are not using the navigation menu it can cause your theme to look broken. You can place the biblio link in the primary & secondary links locations. Once you've fix the menu location your site will return to normal. To make menu changes go to Administer - Site Building - Menu.

Additional Permissions setup is require for others to view/edit etc. Follow the steps outlined below:

  • Step 1: Navigate to Administer - User and click on permissions.
  • Step 2: Find the biblio module section.
  • Step 3: Select all the check boxes on "access biblio content". This will allow other users to be able to view the biblio content, otherwise no one will be able to see the biblio content other than the site adminstrator's.
  • Step 4:Save changes.

Module Evaluation Criteria

Central Web Services reviews all modules that are included as part of the centralized OSU installation.  We do this to ensure that OSU Drupal remains a stable, secure and supportable product for the campus.  The following are the initial criteria we use to evaluate a module.

  • Code Review:
    1. Are there any pending security bugs in the bug tracker?  What are they and how long have they been there?
    2. Is it performing sql queries directly? If so, does the module escape user input?
    3. How does it handle user input? Is it being escaped? Is user input cleaned before printing it out in a page?
    4. Are permissions check in place? Are the checks manual or does the code rely on other core methods?
    5. Is the code well documented? Does it follow a standard?
    6. Is the javascript code and css well structured?  Does it follow follow a standard?
    7. Does it have readme, install and upgrade files?
  • Lifespan/Activity:
    1. How long has this module or 3rd party program been around?
    2. How many developers are working on it?
    3. Is there a roadmap? What does it look like?
    4. What is the release life cycle?
    5. What is the average turn around time for critical bugs?
    6. How active are the forums or mailing list discussions?
    7. Do other programs use or depend on this library?
  • Support:
    1. Is there user documentation? Is there documentation for developers?
    2. Is a documentation generation system like phpDocumentor used?
    3. How quickly do the developers respond to requests?
    4. Are newer and older versions of Drupal supported?
    5. What is the learning curve like?
    6. Is the module usable through the Drupal interface or does it require users to work with HTML, CSS, theme changes or other advanced techniques?
  • Compatibility:
    1. Does it conflict with other existing plugins or modules or other updates?
  • Cost/Benefit:
    1. Will the module work with OSU Drupal as is, or would some re-write be needed?
    2. How complex are patches to apply? (# of classes, files, and db tables affected)
    3. What % of our users would benefit from this new module or plugin?
  • Redundancy
    1. Does OSU/CWS already provide this service?
    2. Is this capability already planned for an upcoming Drupal release or update of a currently supported module?

If you would like to request a module for review, please submit a help ticket.

Moving Your Site to Production

You've been working on your Drupal development website and you think you're now ready to make it your new website.  What do you need to do now?

Before you submit a request:

  • If you have an existing website, is there anything that is a part of the website that you need to keep and isn't on your development site?  You will need to identify any directories that need to remain; if you have other applications under your current website we also need to know if they are to be kept as well.  We generally recommend that all non-Drupal content lives in a sub-directory, not the root of the Drupal website.  Let us know what directories, applications, and other content that you want to keep in your request.
  • When do you want the site to go live?  We move websites to production on Mondays, Tuesdays and Wednesdays in the late afternoon, after 3pm.  This way, if there is an issue, we have staff available for several days to assist you in the resolution. We require a one week lead time for your request to push the site live. Let us know the date you would like your site to be live in your request.
  • If this is a new website (or newly hosted by CWS), do you have a custom URL that has already been approved via the domain name request process and assigned to CWS for maintenance?  Let us know the URL in your request.

Once you know the answers to these questions, you can submit your request to us using a Help Ticket request.  Please be sure to include your development website URL so we know which site you are working with.

Once your site is scheduled, do not work on your development site after 9am on the day it is moving.

After your website is live:

Right after your site is pushed live, you should review it for errors.  Here is a list of items to review on your new website.

  • Broken links - we find many broken links are caused by pages being linked back to the development site. You can use a link checker to assist you in finding broken links.
  • Broken images and videos - again these typically are pointing to the wrong server.
  • Review your entire site for errors: navigation, pages, links

After you've checked your site, there are a few more items to keep in mind

  • Update any bookmarks or saved links you have to point to your new website.
  • It takes time for search engines to find new sites or to re-index your existing site for the new content.  Search results will not be updated right away.
  • CWS will disable the log ins to your development website once we move it to production.  After your new site has been live for a week with no reported errors, we will delete your development website.
  • You can use website statistics to determine if there are a lot of links to content that no longer exist on your website.  If you do not have a custom statistics,  you can request them from us.

You will be given the location to edit your site once it's live.  You'll still be able to edit existing content and add new content as well while your site is live.

If there are any issues that you think are the result of the move, please let us know.

OSU Drupal Themes

OSU Drupal comes with a few pre-installed OSU themes. 

University Advancement has provided guidelines on acceptable customizations of the OSU Drupal themes in the OSU Brand Identity Guidelines.

OSU Standard

The OSU Standard theme was designed by University Advancement Web Communications and developed by Central Web Services.  It has look and feel that blends perfectly with our new main website, it even features the very same top bar.

OSU Standard is designed to have a header navigation element and two right hand sidebars.  It can be customized through the addition of a CCK and view to include rotating story content, inspired by the styling of the OSU Homepage.

Instructions on how to set up this CCK and View can be found in the Brand Guidelines entry on OSU Standard.

OSU Standard Theme

OSU Confident

The OSU Confident theme was designed by University Advancement Web Communications and developed by Central Web Services.  This is the first theme to feature the OSU Tag from the new OSU Brand Identity Guidelines.

OSU Confident is extremely flexible, featuring multiple Drupal regions for editing and placing content.  It is designed so that you can use right and/or left sidebars.  It features a choice of four accent colors (orange, chocolate, steel blue and purple) as well as two background colors (light or dark) .  You can configure the large header image (on the right) to rotate, change on load or be a static single image.  The theme comes with campus images, but you can use your own (560 x 225 pixels).  This theme also features an optional short secondary page header that can be used in place of the large graphic header.

OSU Confident Theme

Permissions

There are multiple permissions levels in Drupal 6, with each one having different access to edit site content and layout. Roles can be added and changed at any time by adminstrators, but this access can be granted to others by the administrator as well. The default roles are:

  • Anonymous Users are visitors to your site that are not registered to your site or logged in; this is the general role that everyone who navigates to your site will have.
  • Authenticated Users are any users that are registered on your site. This means all of the following roles can be considered authenticated users.
  • Authors can create, edit, and publish all default content types, as well as administer menus, taxonomies, and some layout elements. Authors can use the Full-HTML input format, embed videos, images and CSS into individual pages, and can also enable / disable default blocks.
  • Advanced Authors have the above permissions, but can also create custom content types (CCK), administer data queries and displays (views), define and edit input filters, change glossaries, and use the PHP code input format.
  • Administrators have all of the above permissions, but can also change site settings and manage users for the site. This role would be for someone who is in charge of managing the users on a site, and may or may not work in a programming / site structure capacity.

Below is a complete list of the default OSU Drupal permissions:

Permissions in Drupal 6

Permission Anonymous User
Authenticated User Administrator Advanced Author Author
Advanced Help Module
View advanced help index     x x x
View advanced help popup     x x x
View advanced help topic     x x x
Aggregator Module (RSS Feeds)
Access news feeds x x x x x
Administer news feeds     x x x
Announcement Module
Create announcement     x x x
Edit announcement     x x x
Biblio Module
Access Biblio Content          
Administer Biblio     x    
Create Biblio     x x x
Edit All Biblio Entries     x x  
Edit Biblio Authors     x x x
Edit Own Biblio Entries   x x x x
Import from File     x    
Show Download Links x x x x x
Show Export Links x x x x x
Show Filter Tab x x x x x
Show own download links x x x x x
Show Sort Links x x x x x
View Full Text x x x x x
Block Module
Administer blocks     x x x
Use PHP for block visibility     x x  
Book Module
Access printer-friendly version x x x x x
Add content to books     x x x
Administer book outlines     x x x
Create new books     x x x
Content Module
Use PHP input for field settings     x x  
Date Module
View Date Repeats     x x x
Filter Module
Administer filters     x x  
Gallerix Module
Configure Gallerix settings     x    
Create album     x x x
Edit album     x x x
Edit own album     x x x
ImageAPI Module
Administer ImageAPI     x    
IMCE Module
Administer IMCE (Execute PHP)          
Locale Module
Administer languages     x    
Translate interface x x x x x
MenuModule
Administer menu     x x x
Node Module
Access Content x x x x x
Administer content types     x x  
Administer nodes     x x x
Create book content     x x x
Create page content     x x x
Create story content     x x x
Delete any book content     x x x
Delete any page content     x x x
Delete any story content     x x x
Delete own book content     x x x
Delete own page content     x x x
Delete own story content     x x x
Delete revisions     x x x
Edit any book content     x x x
Edit any page content     x x x
Edit any story content     x x x
Edit own book content     x x x
Edit own page content     x x x
Edit own story content     x x x
Revert revisions     x x x
View revisions     x x x
Path Module
Administer URL aliases     x x x
Create URL aliases     x x x
Path Redirect Module
Administer redirects     x    
Pathauto Module
Administer pathauto     x x x
Notify of path changes          
Poll Module
Cancel own vote x x x x x
Create poll content     x x x
Delete any poll content     x x x
Delete own poll content     x x x
Edit any poll content     x x x
Edit own polls content     x x x
Inspect all votes     x    
Vote on polls x x x x x
Site Map Module
Access site map x x x x x
System Module
Access administration pages     x x x
Access site reports     x    
Administer actions          
Administer files          
Administer site onfiguration     x    
Select different theme     x    
Taxonomy Module
Administer taxonomy     x x x
Translation Module
Translate content x x x x x
Upload Module
Upload files     x x x
View uploaded files     x x x
User Module
Access user profiles     x x x
Administer permissions     x    
Administer users     x    
Views Module
Access all views     x x  
Administer views     x x  
Views Export Module
Use Views Exporter     x x  

MediaSpace

mediaspace user interface

MediaSpace is a third-party media portal provided by Kaltura.  MediaSpace facilitates the conversion of many different media formats for easy viewing, distribution, and embedding into your website. The system empowers users with the ability to control their own media. Faculty, staff and students may upload media content themselves, where the conversion of the content is automated.

MediaSpace is the solution chosen to replace OSU Media Manager which, due to rapid shifts in technology, possessed update needs that outpaced the resources available to make the changes.

Media Services engaged in a lengthy review process that included a committee of stakeholders prior to making a decision.

MediaSpace offers a cloud-based solution, which is a virtualized, general purpose computing environment that helps to cut costs in terms of hardware, maintenance, cooling, power, and operational administration.

MediaSpace is under ongoing development, to ensure that features stay fresh, relevant, and secure. A new list of features is available including: higher resolution, capioning, mobile playback and the ability to work with audio files.

For more information on MediaSpace, or on producing video content please visit Digital Media Productions.

MediaSpace Training

A collection of MediaSpace FAQ has been created and is maintained by Digital Media Services. Additional MediaSpace tutorials are available from TAC.

Search

OSU Search lets users search for your content across all of OSU. No matter where they type in their query, results from across OSU will be displayed for any visitors.

As of January 1st, 2010.  OSU has switched to using the Google Search Appliance.

For more information, and to see how to use search in your site, visit the OSU CWS blog.

If you have questions regarding this process, use the contact form and select Search to send us your question.

Statistics

CWS currently offers Urchin Analytics statistical reporting to provide comprehensive information about how your web site is accessed. The live reporting tool allows you to easily generate reports and graphs using custom date ranges and filters so you can quickly find relevant information about your web site.

Reporting services are available for web sites hosted by CWS as well as sites hosted by other OSU departments. You may evaluate Urchin by visiting the free basic reporting for oregonstate.edu. To order reporting for your site, first review our rates and then submit your request.

Help with statistics

Extension has created an informative tutorial that also covers part of the Google Urchin Analytics tool which can be viewed from their site

Urchin 6 Screenshot 1 Urchin 6 Screenshot 2
Urchin 6 Screenshot 3 Urchin 6 Screenshot 4

Statistics Help

NEWS: Urchin was upgraded to version 6 on 2009-03-06. CWS Documentation to replace the Urchin 5 information below is in progress. Documentation on Urchin 6 is available at the Urchin Help Center.

 

Glossary Terms

Bounce
A bounce occurs when a visitor exits a page without visiting any other page on the site.
Bytes
The quantity of network bandwidth used by the files requested during the selected date range.
Hit
A successful request to your web server from a visitor's browser for any type of file, whether an image, HTML page, or any other type. A single web page can cause many hits - one for each image included on the page, etc.
Pageview
A request from a visitor's browser for a displayable web page, generally an HTML file. Images and other embedded content, such as style sheets and javascript, are not considered to be page views.
Referral
An external URL that brought traffic to your site.
Session
A series of clicks on your site by an individual visitor during a specific period of time. As session is initiated when the visitor arrives at your site, and it ends when the browser is closed or there is a period of inactivity.

UTM vs. Standard Session Tracking

When initially setting up a site for Urchin statistics, you have a choice on the method you wish Urchin to use when tracking visitors. With standard session tracking, Urchin uses the visitor's IP address, browser and platform (e.g. Windows 2000/Internet Explorer 6.0), and a 30 minute session timeout. Standard session tracking requires no site modifications and is available for all domains. However, it is not as accurate as UTM tracking and will include robot traffic in session analysis.

UTM (Urchin Traffic Monitor) tracking utilizes javascript and cookies to track visitors. It is the most accurate tracking method and will also filter out robot traffic from session analysis. UTM also enables additional reporting on unique visitors and sessions plus visitor screen resolutions, colors, language, and more. UTM tracking does require you to modify all pages on your site and is only available for sites hosted by CWS on a oregonstate.edu domain (e.g. oregonstate.edu, smile.oregonstate.edu).

Date Range Tool

date range selectorBy default, reports are generated using data from the last 7 days. The reporting period can be changed to a single day, week, month, year, or any arbitrary date range. To view a specific day, month, or year simply click the day, month, or year of interest. To view a specific week, click the arrow to the left of the week you wish to analyze. To specify a date range, click the "Enter Range" link and select the start and end dates of your range.

Sorting Results

On most reports, you may sort by any field or collumn displayed in a table. To change the sort order, simply click one of the small up or down arrow icons next to the field you wish to sort by.

Using Filters

You may optionally apply a filter on the first column of any report that generates a sorted list of entries. Simply type the text you wish to filter, then click the plus button to include only entries matching your text. Alternatively you may click the minus button to exclude all entries matching your text. You may also use the special characters '^' and '$' in your filter text. '^' matches the beginning of an entry, while '$' matches the end of an entry. See the following examples:

Filter text Include result Exclude result
cws Only entries containing "cws" will be shown Entries containing "cws" will be excluded
^/cws Only entries starting with "/cws" will be shown Entries starting with "/cws" will be excluded
html$ Only entries ending with "html" will be shown Entries ending with "html" will be excluded

Printing Reports

A print-friendly view of any report can be generated by clicking the printer icon in the top-right of any report. The print-friendly version will open in a new window.

To quickly print an entire set of reports, click one of the "Print All with Defaults" links in the reports navigation menu. All reports in the section will be generated in a single window using the current date range and default parameters. It is not possible to customize this mass report using filters, sorting, or drilldowns. Generate each report individually if customization is desired.

Exporting Reports

Reports can be exported to Microsoft Word, Excel, and tab separated text formats. To export, simply click on the icon of the desired format. Note that the Word and Excel files do not embed any images, but rather link to the Urchin reporting website. To make the Word report more suitable for viewing off-line, you can manually embed the linked images in a Microsoft Word document using the following steps:

  1. Open the Word document report.
  2. Navigate to Edit->Links in the Word menu. This will bring up a Links dialog box.
  3. Highlight all the listed links in the window and click the Break Link button.
  4. Navigate to File->SaveAs and enter the desired File name, with Save as type of Word Document (*.doc)
  5. The saved document will contain all the required images and should load properly in Word regardless of whether the computer has access to the internet or not.

 

Note that the above method does not work in Microsoft Excel. There is currently no known workaround for embedding the external links in Excel reports.

Reports

Former WebTrends monthly report users may wish view the report equivalency table.

Traffic Reports

  • Sessions Graph
  • Pageviews Graph
  • Hits Graph
  • Bytes Graph
  • Summary Graph

Visitor & Session Reports

This set of reports is only available on profiles setup using UTM session tracking (see UTM Setup below):

  • Visitors by Day
  • Sessions by Day
  • Unique Visitors
  • Unique Sessions
  • Visitor Loyalty
  • Session Frequency
  • Summary

Page & File Reports

  • Requested Pages
  • Downloads
  • Page Query Terms
  • Posted Forms
  • Status and Errors
  • All Files by Hits
  • All Files by Bytes
  • Directory by Pages Drilldown
  • Directory by Files Drilldown
  • Directory by Bytes Drilldown
  • File Types by Hits
  • File Types by Bytes
  • Entrance Pages
  • Exit Pages
  • Bounce Rate
  • Click Paths
  • Click To and From
  • Length of Pageview
  • Depth of Session
  • Length of Session

Referral Reports

  • Referrals
  • Referral Drilldown
  • Search Terms
  • Search Engines
  • Referral Errors

Domain & User Reports

  • Domains
  • Domain Drilldown
  • Countries
  • IP Addresses
  • IP Drilldown
  • Usernames by Hits
  • Usernames by Bytes
  • Usernames by Sessions

Browser & Robot Reports

  • Browsers by Sessions Drilldown
  • Browsers by Hits Drilldown
  • Browsers by Bytes Drilldown
  • Platforms by Sessions Drilldown
  • Platforms by Hits Drilldown
  • Platforms by Bytes Drilldown
  • Combos by Sessions
  • Combos by Hits
  • Combos by Bytes
  • Robots by Hits Drilldown
  • Robots by Bytes Drilldown

Client Parameter Reports

This set of reports is only available on profiles setup using UTM session tracking (see UTM Setup below)

  • Screen Resolution
  • Screen Colors
  • Languages
  • Java Enabled
  • Javascript Version

UTM Setup

If you requested to use the optional UTM session tracking for your statistics reports, then you must modify all pages on your site that you wish to be included in Urchin's session statistics. Include the following 3 lines in all your html pages (either inside the <head> or <body> of your pages). If your site has a common header file included in all your pages, then you should only need to modify that included file.

<!-- Start Urchin Trafic Monitor code -->
<script type="text/javascript" src="/cw_tools/stats/__utm.js"></script>
<!-- End Urchin Traffic Monitor code -->

Below is an example of a webpage properly modified to use UTM.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Page Title</title>
<link rel="stylesheet" href="style.css" type="text/css" />

<!-- Start Urchin Trafic Monitor code -->
<script type="text/javascript" src="/cw_tools/stats/__utm.js"></script>
<!-- End Urchin Traffic Monitor code -->

</head>
<body>
<h1>This is a webpage</h1>
...
</body>
</html>

FAQ

All I'm seeing is "Execution of urchin.cgi timed out." What happened?!
This error condition will sometimes occur when generating reports over a large date-range for sites that see a large amount of traffic. This is due to the archiving mechanism that is used on data that is more than 2 months old. When requesting older data, it takes extra time for Urchin to retrieve and prepare it for reporting. Once prepared, the data is retained for a short while (cached) so that subsequent requests will be much faster. The workaround is simple: refreshing the page in your browser will instruct Urchin to continue processing where it left off, and will usually provide enough time to finish generating larger reports. If the report still fails to complete before the timeout, it may be necessary to shorten the date range of your requested report.
Why are Page Views higher than Downloads for some Adobe Acrobat (PDF) files?
Requested Pages reports may report higher numbers for PDFs than the Downloads report. Some web browsers make multiple requests to a multi-page PDF for a single visitor. This counts as 1 download in the Downloads report, but multiple requests in the Requested Pages report. This is explained in more detail at the official Urchin help site.
The old WebTrends reports showed some useful information. Which Urchin report can show me the same or similar information?
Most WebTrends reports have an equivalent or similar Urchin counterpart. Please see the WebTrends to Urchin report equivalency table.

Urchin Help Center

Official Urchin help and reference documents are available at the Urchin Help Center.

Statistics Reporting

Access to Urchin reports requires a Javascript enabled browser. Additionally, a valid ONID username and password is required when viewing the reports off-campus. See Web Statistics Help to learn more about using Urchin reports.

If you have ordered statistics and cannot find your site in the hierarchy below, please contact CWS. For new reports, please review our rates and then submit your request.

Note that free basic statistics for all sites hosted under http://oregonstate.edu/ are included in the OSU Home Page report below (see help on using filters).

OSU Home Page Reporting

ONID Home Pages Reporting (Note: Reporting is not available after September 2009 due to the people.oregonstate.edu move. CWS will restore this service at a future date.)

Urchin 6 Reporting Profiles

Collapse All / Expand All Collapse All / Expand All

Web Statistics - Request Form

Contact and Billing Information

Web Site Information


Is this your first request for this Web site?*


Urchin Session Tracking


What method would you like for session tracking?* (help)



Required fields have a red asterisk *

Survey Tool

Central Web Services appreciates the support of those who have used our survey application.   In looking at our resources going forward, it was decided that the Business Solutions Group provides a more updated survey tool which better meets the needs of the OSU Community.

Central Web Services discontinued this service officially July 1, 2010.

BSG Survey Tool