03 May 2016

Changing FIND BOOKS, ARTICLES, VIDEOS to Find Books, Articles, and More

Changing FIND BOOKS, ARTICLES, VIDEOS to Find Books, Articles, and More

Involves changing several files both on the web site and other places

LS Web Site:

  • Home Page -- Header in middle of home page 
    • (includes/FindSearch.txt)
  • Navigation Bar (these includes files:
    • HeaderNav.php
      • navbar.php
      • nav-minimal.php
    • and /includes/NavPages/BksArt.txt

  • eresources/searchall.php is taken care of with  (includes/FindSearch.txt)
CMS LibGuides:

  •  navigation bar
  • possible guide pages
IL Tutorials
  • Finding Articles 
  • ? others
Handouts (Reference, Workshops, IL sessions)


21 January 2016

Documenting the LivePerson fix for mobile devices.

This was an hours long process and I'm tired so want to document what was done before I forget.


  1. Steve and Cary were testing facets of LivePerson/LiveEngage when they noticed that the chat links were not working for Steve's iPhone.
  2. They reported that to me and I verified the links wouldn't work on my android phone either.
  3. I asked Toyya to notify our LP representative and have a technician get in touch with me by email with a suggested solution.
  4. Thus began a tortuous process which, with a little thought, could have been resolved hours earlier.
Note:  There are some behind the scenes -- on the LP server -- scripts that we cannot access. What I am documenting are those client side (our web site) scripts for which we have some control -- not much.

Throughout the day, I received bits of scripts to make all three links on the Library Home Page work both for desktop computers and for mobile devices.  Here is a summary of the scripting that works.

Basic LivePerson script to be on every page:

<?php include("http://library.austincc.edu/includes/LivePerson-script.txt"); ?>

Added:
  • <script src="http://library.austincc.edu/bower_components/jquery/jquery.min.js"></script> to the top of the script
    • Note: This particular script is already in the "footer-LS.txt" file but must be in that place for all three of the links on the homepage to work.
    • Note2: This script in its new location somehow interferes with the slider scripts on the Tutorial page and on the LS Staff Directory pages.
      Solution: Created a second LivePerson script without that line -- LivePerson-script2.txt -- to be used on those pages only since this does not affect the navigation bar only additional chat links on a page.
  • Three sets of code to embed different actions for the 3 different links on the home page.
    <a class="lebtn"><div id="LP_DIV_1453394743202" style="display:none;"></div></a>
    <a class="lebtn2"><div id="LP_DIV_1445611073120" style="display:none;"></div></a>
    <a class="lebtn3"><div id="LP_DIV_1445609128908" style="display:none;"></div></a>

Navigation Bar at the top of every page "navbar.php"

Changed:
The Chat link under Get Help/Chat to <a id="ex1" style="cursor:pointer;"><img alt="Chat with a Librarian" src="http://library.austincc.edu/img/chat2_32x32.png">Chat</a>
Note: the "ex1" refers to the first "lebtn" division - "LP_DIV_1453394743202" -- code not totally available to us.

For Students content file "ForStudents.txt"

Changed:
The Chat link to <a id="ex2" style="cursor:pointer;">Chat with a Librarian</a>
Note: the "ex2" refers to the "lebtn2" division - "LP_DIV_1445611073120" -- code not totally available to us.

Virtual 24/7 content file "VirtualHelp.txt"

Changed:
The Chat link to <a id="ex3" style="cursor:pointer;">Chat with a Librarian<img src="http://library.austincc.edu/img/chat_32x32r.png" border="0" style="vertical-align:super;" alt="Chat Live with Librarians"></a>
Note: the "ex3" refers to the "lebtn3" division - "LP_DIV_1445609128908" -- code not totally available to us.

Footer at the bottom of each page "footer-LS.php"

Added:
Three scripts that control the action of the 3 different links:
<script>
$("#ex1").click(function() {
$(".lebtn div").trigger("click");
});
</script>
<script>
$("#ex2").click(function() {
$(".lebtn2 div").trigger("click");
});

</script>
<script>
$("#ex3").click(function() {
$(".lebtn3 div").trigger("click");
});

</script>

05 November 2015

Preparing for LiveEngage

We have met with LiveEngage, i.e., LivePerson, representative (Kyle Murray) and implementation tech (Mark Washburn) to discuss what will happen as we implement LiveEngage a new totally web-based platform.  This post addresses only the client side changes, i.e., what the user/students see.
  • Questions we asked
  • Scripts we were sent
    • For some reason they insisted upon styling our links and that styling is embedded in the script somewhere.  
    • I also had to add two lines of css styling to our style sheet (extra-LS.css)

Steps Taken to Transition:

  • Parsed the instructions sent for scripts and code. []
    • Created a script file to be included via a php include in the head of pages/templates on the LS Web Site. 
    • Noted the code needed within pages
      • link with chat image
      • link without chat image
  • Created test pages to include the scripts and code for chat links.  []
  • Installed the LiveEngage Preview extension in Chrome to emulate final implementation. []
    • Without this extension, you cannot see the new chat window at this time.
      • Tested two pages listed above.  
        • Note: first code sent did not work correctly.  Code was revised and works well.
      • Created a libguide with added javascript in the head to test there. []

Steps to be taken to make it live:

  • Staff to be trained (Toyya lead)
  • Meet with Courtney to discuss how to deploy in CMS.
    • Suggest we do a minimal nav bar with Chat link.
  • Review all chat windows for needed changes.
    • Note:  Find out about the chat window when all agents logged off.
  • On deployment day:
    •  Put LivePerson JS script above </head> on each page
      • Create a script file to put into the root /includes/ folder
      • Create a PHP includes statement to invoke the script
      • Use TextCrawler to insert the PHP includes above the </head> in all pertinent files.
    • Rename /includes/ ...LP files to standard file names.
      • ForStudents-LP.txt
      • VirtualHelp-LP.txt
      • footer-LP.php
      • navbar-LP.php 
    • Rename /help/includes/ask-incl-LP.htm to standard file name.
    • Do whatever CMS change needs to be made.
      • Add LivePerson JS script to system page
      • Add new custom Header to Look/Feel system
      • Redo Info/Alert Box to include new Chat code.
      • Note: per CM deleted all group banners and implemented system custom header.
  • Post-Installation
    • Test for operations
    • Test for look/feel
      • Offline window had issues because the "header" was too long and I could not edit it to correct the Ask Academic link. (note: Mark corrected it.)
      • Went into campaigns area to edit Chat window to change bubbles font and background colors. Changed image to a different picture.
      • Cannot use our own image because we have no secure server to host the image.
      • Asked if they could include non-person images in their gallery.
    • Remove the LiveChat Agent from Ref Desk PCs

15 October 2015

RSS Feeds - Change to IRT scripts

What's New Column - RSS Feeds


RSS feeds on the home page:
  • What's New Blog latest entry and the 
  • Spotlight on ... latest two entries
We have been using an external script from FeedRoll to bring these into the right column on the Library Home Page.  Although this has been working just fine, there is often a lag time before the items display.

Upon consulting Maria Youngman and Robert Ferguson from IRT, I learned that Maria had developed some scripts from earlier ones by Robert to do news feeds on the Copyright site.  Using these as a base, I was able to change and modify these to suit our needs.
  1. Two separate javascripts were needed.
    1. app.js
      1. Modifications:  ** After much experimentation...**
        1. comment out the for statement and closing bracket
        2. change the variable entry from [ i ] to [ 0 ]
        3. Note: This enabled the display of only the latest blog entry.
    2. appSpot.js 
      1. Modification:   ** After much more experimentation and help from EVC IRT folks.**
        1. change the for statement to delete the indeterminate variable increment
        2. insert a direct counter in the for statement  -- i < 2; i++
        3. Note: This enabled the display of the 2 latest blog entry.
  2. Links to the scripts had to be added to the bottom of the footer-LS.php includes file.
  3. Changes were needed for the whatsnewcol.txt includes file.
    1. Remove the feedroll scipts. Note: change related page in wiki.
    2. Replace with new javascripts.
    3. Organize and style to fit script output.  Do a little cleanup for that column.


09 October 2015

CSS Clean-up Project

Changing to a CSS class - Is it worth it?

When there are multiple inline styles on a word or phrase, it may be worth it to change to a Span class. Example: <span class="strong em">.

Theoretically, we should always do this even with one word changes.
For example, even if we had something like <b>someword </b> and it would appear wordier (more characters) to have <span class="strong">someword </span>, we should remove the inline deprecated html.

HTML should provide content structure; CSS should provide style.