Review LS Web Content

Page Responsibilities 

---

Preparation behind the scenes

• List of files on LS Web
  
• Compare
• Page Responsibilities Spreadsheet

Organize/Remove extraneous files

---

Process to follow

• MP defines
  
• Sends to Reviewers
• Reviewers
• Reviewers send OK or suggestions ☑

AY19 LS Web Redesign

AY18-19 Redesign - See MindMap

Overview

• ACC Web New Look
• Launch Mar 2018
• New Drupal template
• No direct link to Library from
• ACC home
• From Student
• From Faculty
• No longer a 2nd Tier page (See Other Options below)

Objectives

• Emulate ACC Web Site Look
• Incorporate ACC looks when possible
• CSS driven
• Use collapsible menu similar to student page??
• Make the Library Web Site Easy to Use
• For Students
• For Faculty
• For IL purposes
• Make the Library Web Site Attractive
• For Students
• For Faculty
• Make all pages responsive via CSS

Surveys/Focus Groups

Tashley idea (email : Sunday, February 8 2009 08:33 am )
I had a dream about doing a survey recently (probably after my Faculty and Staff Evaluation Committee meeting on Friday).

In the dream, we had a focus group in our Instruction Area at Northridge, using laptops and clickers to complete a survey. I guess I was remembering that clickers are eventually going to be used for faculty evaluations--that item was on Friday's agenda.

Another idea from the meeting: Don't offer incentives to survey participants. Terry Moucheyleh was warned about offering incentives when she needed people to do a survey for her dissertation. Incentives skew the results, mainly by attracting only participants who are interested in the type of incentive offered.

• Need general info
• See attached file(s): Student Input.xlsx
• What Students want?
• What Faculty need?
• What LSstaff want?
• Need Feedback re: mockups
• Students
• Faculty
• Librarians
• Testing final draft

Strategy

• Get ideas from all pertinent groups
• Consider Best Practices
• See document(s): 7 Best Practices (Ebsco)
• See document(s): 25 Webiste Problems - LS Compare
• Explore other web examples
• Best College Websites
• See document(s): https://tinyurl.com/BestAcadWeb
• Develop test pages from ideas
• Work with appropriate teams or groups to get feedback
• Solicit help where appropriate
• Develop deployment priorities
• See also: Launch Strategy

Advertising Strategy

• Consult with LS PR early Summer
• Involve Teaching Team

Launch Strategy

• To be determined

Steps Independent of other Actions

Although group decisions will affect content and sometimes layout, we need to start somewhere.

• Create Standard
• Header
• Footer
• Create draft example pages
• Home
• Major second tier
• Create draft templates
• Caveat: Will have to strip current content pages of their embedded styles.
• Create appropriate styles for tier pages if necessary

Other Options

• Let TLED do it.
• Seek another host.
• Demo Ebsco Stacks
• See Eval Rubric
• See document(s): Web Site Hosting Product Rubric.docx

Schedule Timeline

• Initial input from Web Advisory Group
• Start Date: 2/9/2018[2018,02,09] Due Date: 2/23/2018[2018,02,23] Duration: 11 day(s)
• Review by Group
• See document: https://tinyurl.com/AccessPoints1
• Start Date: 2/27/2018[2018,02,27] Due Date: 3/5/2018[2018,03,05] Duration: 5 day(s)
• Get Input on Access Points (links) from Librarians
• See document: https://tinyurl.com/AccessPoints2
• Start Date: 4/6/2018[2018,04,06] Due Date: 4/30/2018[2018,04,30] Duration: 17 day(s)

Stopped here by Dean/AVP =============================

• Determine what Access Links point to
• Start Date: 5/1/2018[2018,05,01] Due Date: 5/31/2018[2018,05,31] Duration: 23 day(s)
• We were asked to put a hold on further work until it was determined how we fit into the TLED web environment.

☒ Put on hold.  May continue Spring 2019.

• Student Input
• See attached file(s): Student Input.xlsx
• Want?
• Need?
• Develop templates
• Create style sheets
• Home
• All fonts in %
• Max width code
• Page Level 2
• Possible Level 3
• Create level looks
• Initial input from Students/Faculty
• Incorporate ideas into test pages
• Get Feedback on Test pages
• Incorporate feedback into pages

Spanish Language LS Web Pages

Identify -spi pages

https://library.austincc.edu/gen-info/Lending-about-spi.php

[X] https://library.austincc.edu/gen-info/stud-Lending2-spi.php [done]

https://library.austincc.edu/gen-info/Services/copy-about-spi.php

https://library.austincc.edu/gen-info/Services/groupstudy-about-spi.php

https://library.austincc.edu/gen-info/Services/printing-about-spi.php

https://library.austincc.edu/Help/FAQs/FAQ-comp-use-spi.php

https://library.austincc.edu/Help/FAQs/FAQ-payfines-spi.php

https://library.austincc.edu/Help/FAQs/FAQ-privacy-spi.php

⭐https://library.austincc.edu/Help/FAQs/FAQ-renew-spi.php [done]

       ⟹ link needed to this from Eng page (also identify other Eng pages also need)
https://library.austincc.edu/Help/FAQs/FAQ-rq-a-book-spi.php

https://library.austincc.edu/Help/FAQs/FAQ-Unattended-spi.php

Decision needed

Still needed?

Yes (no symbol)

 No [X] 

Changes needed?

✪ Minor

⭐Major Redo

✪  Minor Changes

✏ Fix wording

⭐ Major Changes

🔨 Use Google Translate for first draft

👀 Have Lynda Infante review for wording changes.

✏  Fix wording                          ↓

📝 Create new needed pages/files.

LoanPeriodsFinesFees-spi.php [done]  ↑
FinesFeesXX-spi.php [done]
SeeAddResources-Loan-spi.txt [done]

Using relative links for PHP includes

=============================================================
 Using include $_SERVER["DOCUMENT_ROOT"]
=============================================================
Note: The Library Web Server administrators have requested that we change our PHP includes links (especially for the Banner (Header) and Navigation Bar (NavBar) to relative ones as an effort to prevent web server crashes.  In order to do that, this is the plan outline. --mp

-------------------------------------------------------------
1 Basic element
-------------------------------------------------------------

1.1 include($_SERVER["DOCUMENT_ROOT"] . '/xxx/xyxyxy.php');

-------------------------------------------------------------
2 From one folder down (This works.)
-------------------------------------------------------------

2.1 Example: https://library.austincc.edu/eresources/testing.php
2.2 Page element:
<div id="hang">
<?php include($_SERVER["DOCUMENT_ROOT"] . '/hang.html'); ?>
</div><!-- end of hang -->

-------------------------------------------------------------
3 From one folder down  (This works.)
-------------------------------------------------------------

3.1 Adding the header to the same file "testing.php"
3.2 Page element:
<!-- This next section contains a header file in the includes folder. -->
<?php include($_SERVER["DOCUMENT_ROOT"] . '/includes/header.php'); ?>

-------------------------------------------------------------
4 From two folders down  (This works.)
-------------------------------------------------------------

4.1 TestA:
https://library.austincc.edu/eresources/testA/testA.php
4.1.1 Previous includes with doc_root still works.
4.2 TestB with HeaderNavZ:
https://library.austincc.edu/eresources/testA/testB.php
4.2.1 Previous includes with doc_root still works.
4.2.2 Page elements (HeaderNavZ.php):
<?php include("header.php"); ?>
<?php include("navbar.php"); ?>

-------------------------------------------------------------
5 Next Step
-------------------------------------------------------------

5.1 At the end "HeaderNavZ.php" = "HeaderNav.php" (or maybe not necessary to rename)
5.2 Replace
  5.2.1 <?php include("https://library.austincc.edu/includes/TopScripts.txt"); ?>
   5.2.1.1 With✔done
      <?php include($_SERVER["DOCUMENT_ROOT"] . '/includes/TopScripts.txt'); ?>
  5.2.2 <?php include("https://library.austincc.edu/includes/HeaderNav.php"); ?>
    5.2.2.1 With✔done
      <?php include($_SERVER["DOCUMENT_ROOT"] . '/includes/HeaderNavZ.php'); ?>
  5.2.3 <?php include("https://library.austincc.edu/includes/footer-LSphp"); ?>
    5.2.3.1 With✔done
      <?php include($_SERVER["DOCUMENT_ROOT"] . '/includes/footer-LS.php'); ?>
  5.2.4 <?php include("https://library.austincc.edu/includes/ReadThumbs.php"); ?>
    5.2.4.1 With✔done
      <?php include($_SERVER["DOCUMENT_ROOT"] . '/includes/ReadThumbs.php'); ?>

-------------------------------------------------------------

6 Next Step for the php files in the Root folder ✔done

------------------------------------------------------------- 11/25/17

6.1 No need for the DocRoot script in the Root folder
6.2 Replace
  6.2.1 https://library.austincc.edu/includes/
   6.2.1.1 With
      includes/
  6.2.2 So <?php include("https://library.austincc.edu/includes/xcxcx.php"); ?>
          Becomes 
               <?php include("includes/xcxcx.php"); ?> 

LS FAQs and the LibraryH3lp Knowledge Base

=============================================================

 LS FAQs  -  LibraryH3lp Knowledge Base

Note: LS FAQs reside on

o   The Library Web Site (https://library.austincc.edu/help/FAQs/)

o   Within our live chat vendor site in the Knowledge Base as part of our subscription (https://austincc.ask.libraryh3lp.com/)

Questions:
Do we replace the Web Site FAQs with the Knowledge Base?
Do we stop using the Knowledge Base?
Do we maintain both?
If we maintain both, what do we link to on the Library Web Site?

-------------------------------------------------------------

1 Create working lists

-------------------------------------------------------------

1.1 Create a list of FAQs on LS Web

1.2 Create a list of Knowledge Base FAQs

-------------------------------------------------------------

2 Review lists

-------------------------------------------------------------

2.1 Mark LS-FAQs if on Knowledge Base

2.2 Check Knowledge Base for accuracy

2.3 Decide on additions to Knowledge Base

-------------------------------------------------------------

3 Decide how / what to link

-------------------------------------------------------------

3.1 Notes:

3.1.1 Searching better for users on Knowledge Base

3.1.2 Are all current LS FAQs appropriate for the Knowledge Base?

3.1.3 Knowledge Base easier for our Ref Librarians to use while on chat service.

3.2 LS Web Sole Link

3.2.1 LS Web links to Knowledge Base only.

3.2.2 Link from Knowledge Base to LS Web FAQs

3.3 Keep Both Knowledge Base & Web Site FAQs

3.3.1 LS Web Site FAQs searchable from LS Web & ACC Web Search

3.3.2 Knowledge Base not searchable from LS Web & ACC Web Search