// ----------------------------------------
// Welcome to the code that defines page names and
// content categories dynamically within the WSS code
// that is physically resident in all of the megasite
// footers. 
// ----------------------------------------
// By: Carl R. Bach
// Created:  March 4, 2002
// Modified:  March 6, 2002
//               Added comments within the code.
//	      March 27, 2003
//		 Made this version of only Academic.
// ----------------------------------------
// This assigns str to equal the directory name
// that follows the lexisnexis.com in the URL
// of the page on which it is loaded
// ----------------------------------------
var str=location.pathname
str=str.substr(1, str.length)
var pos=str.indexOf("/")
str=str.substr(0, pos)
// ----------------------------------------
// Here is where we are assigning a content category
// for use in the code that is determined based upon
// what the str, or directory, in the URL is
// ----------------------------------------
switch (str)
{
// ----------------------------------------
// Here is where we assign a content category depending
// on what the directory is in which the page being loaded
// resides.  Content categories are used to organize our 
// tracking statistics within the WSS reporting area. 
// Each WSS code can have a single content category
// up to 8-levels deep.  
// ----------------------------------------
// See Amy if you have a question about
// what content category should be assigned to a specific
// directory within megasite.  For the most part, we have 
// broken them down fairly logically.  However, if a page(s)
// is considered to be both NALM and CFM, we are defaulting
// to the NALM content category. 
// ----------------------------------------
// If you ADD a directory, such as a campaign, directly
// off of lexisnexis.com, you must edit this document by
// locating the correct area below by content category
// and inserting the appropriate 3-lines of code for your
// new directory.  The CASE line is the name of the directory
// that appears in the URL.  The contentcategory line is 
// defining the content category for that directory. 
// The break line is simply instructing the code to move
// on if it hasn't found the directory or to stop processing
// if it has found it.  
// ----------------------------------------
// NOTE:  NO spaces can ever be placed within a 
// content category.  Instead, if necessary, use the 
// + sign to represent a space.
// ----------------------------------------
// By the same token, if we retire a directory and/or a
// campaign ends, you must edit this document by 
// REMOVING the appropriate 3 lines of code. 
// ----------------------------------------
// BEGIN DEFINING CONTENT CATEGORIES
// ----------------------------------------
// If the directory is nothing, it will get a 
// mega rootlevel content category.  An example
// is offices.shtml or the main page - things not
// in a separate directory off of lexisnexis.com. 
// ----------------------------------------

case "academic":
  contentcategory = "/Mega/Community/Academic"
  break;
case "Academic":
  contentcategory = "/Mega/Community/Academic"
  break;
case "ACADEMIC":
  contentcategory = "/Mega/Community/Academic"
  break;
// ----------------------------------------
// The following is the default content category if 
// none of the above define one for a specific directory. 
// This content category is ALERT and it should be monitored
// on a regular basis within the reporting tool as any pages 
// receiving this content category would be an indication that
// its directory is not included in the above code and it 
// more than likely should be.  Basically, a catchall to notify
// us of any missed directories.  
// ----------------------------------------
default:
  contentcategory = "/ALERT";
}
// ----------------------------------------
// The following piece of code is defining what the page
// name will be in the reporting tool for WSS.  This code
// is taking everything after lexisnexis.com, including 
// directories and file names that display in the url.  
// There is still work to do here because if the url accessed
// simply ends with a directory name and has the default
// page loading without it displaying in the URL/Address Line
// of the browser, the page will get the Unknown Pages 
// page name.  This will be worked on so as to generate a 
// better page name in these instances at some time in the
// future.  See Carl if you have any problems. 
// ----------------------------------------
pagename = (location.pathname)