Security Certificate (SSL) -- LSProxy

What is SSL:

• An SSL certificate is a bit of code on your web server that provides security for online communications. When a web browser contacts your secured web site, the SSL certificate enables an encrypted connection.
• [https://www.thawte.com/resources/getting-started/ssl-faq/]

Melanie Dickerman has secured a license for a "trusted" security certificate (SSL).  For the encryption to be effective, we need to change the proxied links from http://lsproxy... to https://lsproxy...  This affects several areas of Library Services.  (See Chart.)
To Be Done: Change http://lsproxy to https://lsproxy

Where	Process Owner	Start	Due
ERM	Adrian	9 Jun 15	31 Jul 15
Catalog 856	Adrian / Linda B	9 Jun 15	31 Jul 15
Catalogers change macro	Linda B	9 Jun 15	31 Jul 15
Admin settings permalink DBs	Adrian	9 Jun 15	31 Jul 15
Direct links IL tutorials	IL Team	11 Jun 15	31 Jul 15
LibGuides	Courtney (librarians)	11 Jun 15	31 Jul 15
LivePerson Scripts	Steve	9 Jun 15	31 Jul 15
Misc pages LS Web	Margaret	9 Jun 15	31 Jul 15
config.txt	Margaret	9 Jun 15	After all else

Project progress can be found on the google document created for process owners.

Research Guides New Banners

After several options were viewed by the Campus Guides Advisory Group, they settled upon those on this test page:   http://researchguides.austincc.edu/newbanner

Courtney Mlinar, Campus Guides Facilitator, asked me to deploy the new banners and to add a revision date to the current footer.

==== PLAN ====

• Clean up the code on the banners for each group.
• Landing Page, i.e., the Research Guides home page
• Library Guides
• Subject Guides
• Class Guides
• Information Plus Guides
• Faculty Staff Page
• Make slightly smaller
• ACC Logo
• LS logo -- Make "Library Services" clearer
• Pad the ACC Logo a little more top and left
• Add the revision date to the footer -- done on the home page system settings
• Add the new banner code to each existing group

Making Library Web Pages More Accessiblle Continued

Some tools for checking accessibility:

Wave

AChecker.ca

508checker.com

One thing I know is inconsistent -- tagging images.

 Plan of Action

• Select sample pages from each folder.
• Run a check from each of the tools listed above.
• Note issues that are probably on most pages, e.g., 
• alt tag images that appear everywhere;
• common phrases or coding that appear everywhere.
• Determine if  can do global fix with Textcrawler.
• Use the same chart as before to guide any fixes.
• Do miscellaneous fixes that cannot be done globally.

•  Some global things:
•  replace ---  b> with strong>

Folders to do global replace  b> with strong>

Folder	# Files	Done
/includes Eres	6	6/4/15
/includes-GenInfo	12
/includesAUP	0
/includesChallenge	0
/includesCommunity	4
/includesDIR	14
/includesLaptop	2
/includes-svc	28
Vote	12

Tentatively finished with all email forms

The object is to transition the old forms, using Captcha to eliminate spam from robot emailers, to the IRT forms template which contains a "bot trap."

The IRT forms template has these features:

• a web page form
• a form processor for each form
• a general immediate response form (response-ls.php)
• emails sent to
• the requester listing what they filled out
• the appropriate recipient for the particular form, e.g.,
• AskDL goes to lkilman@austincc.edu,acarr@austincc.edu,lindsey.watson@austincc.edu,toyya.cisneros@austincc.edu
• AskLS goes to library@austincc.edu

I have completed all the forms with the exception of one form that had been requested but not ever implemented.  (III problems)  This form exists on the wiki only in Word Doc format.  The issue is that the form is designed to be attached to an email to be sent to the appropriate person from the Who [sic] To Call page.  The current template does not provide the code to specify that a particular person be chosen to be emailed.  So, I've placed this form on hold until that can be resolved. [Note: I have been able to resolve this issue and have created the appropriate form. 5/6/15mp]
Updated list:

New Email Form	New Form Processor	Replaced / Retired
AskDL.php	formprocessorDL.php	DLaskEmail.php
AskEresTrial.php	formprocessorTrial.php	askEmail-ERES1.php
AskFeedback.php	formprocessorFeedback.php	FeedbackEmail.php
AskLS.php	formprocessorAsk.php	askEmail-new.php
askOutreach.php	formprocessorOutreach.php	askOutreach.php
AskPurchase.php	formprocessorSuggest.php	PurchaseItem.php
DemoFeedback.php	formprocessorDemo.php	DemoFeedback.php
EmailRq-AV.php	formprocessorAVX.php	EmailRq-AV.php
ILS-Problem.php	formprocessorProb.php	n/a
ILLrqEmailArticle.php	formprocessorILL-art.php	ILLrqEmailArticle.php
ILLrqEmailBook.php	formprocessorILL-Bk.php	ILLrqEmailBook.php
ILSpwd-Email.php	formprocessorPWD.php	ILSpwd-Email.php
ILSpwd-Delete.php	formprocessorILSdelete.php	ILSpwd-Delete.php
MPaskEmail.php	formprocessorMP.php	MPMail.htm
response-ls.php	n/a	n/a
TXrqEmail.php	formprocessorTxShare.php	TXrqEmail.php
n/a	n/a	EmailRq-IL-googleReplaced.php
n/a	n/a	ILconsultation-retired.php
n/a	n/a	workshopRq-retired.php

Making the LS Web Pages more accessible

I recently discovered that the basic template that IRT created for LS did not have the simple code we always had before for Screen Readers.

<div id="skip"><a href="#contentarea">Skip to
Main Content</a></div>

Here is the process I followed to add the code to all pages with the php extension -- that is all the public pages on the site.

1. Backed up the site to an external drive.
2. Identified a division that should exist on all of these pages to send screen readers to as the main content.  <section class="content"  id="LScontent">
3. Identified all pages that did not have that exact division.  See spreadsheet below
4. Used a textcrawler (batch converter) to replace <section class="content"> with <section class="content"  id="LScontent"> in the appropriate folders and subfolders.
5. Overwrote the pertinent files on the server with the changes.
6. Added a style to extra-LS.css  to hide skip command from page viewers, i.e. make it invisible.
7. Added this skip code to the top of HeaderNav.php so the the screen reader would skip over all the navigation bar menus and go straight to main content, i.e., LScontent, on LS web pages.

<div id="skip"><a href="#LScontent">Skip to
Main Content</a></div>

 

Folder	Subfolder	# Files	# with	# to fix
Eresources		23	15	0
GenInfo		38	30	0
	AUP	6	6	0
	Challenge	5	4	0
	Community	7	7	0
	Dir	16	3	13
	Laptops	5	5	0
	Services	43	43	0
Help		63	43	20
	APA	2	2	0
	CSE	4	4	0
	FAQs	85	85	0
	MLA	3	3	0
	Turabian	6	6	0
Loc		6	6	0