Versions Compared

Old Version 3

changes.mady.by.user Cynthia Schwarz (Unlicensed)

Saved on

compared with

New Version 4

changes.mady.by.user Cynthia Schwarz (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Goals

  • Discuss how the integration of library search affect both the design of library search and the website

  • Contact us form - do we want to just have one form that goes through LibAnswers and then gets directed?

  • Space entity index page - do we need an index for spaces if people can look at the list of spaces on a building page?

  • Service entity page - are there elements that we need to discuss?

  • Meeting schedule for the spring semester - should we meet more frequently? once a week, even?

...

Item

Notes

Library Search Integration

Look at MAN-33

Contact form

Do we want to direct everything through LibAnswers instead of having separate forms?Move the website to librarybeta.temple.edu

what is happening to libqa?

  • The plan right now is to move Libqa off of TUcloud and on to Linode to provide more ease of access

Question: the Blacklight team is actively developing and breaking things.

  • If the website moves to librarybeta, where can the breaking and active dev work for BL happen?

  • Do we need to have a certain level of stability for the website beta site?

Side Note: The BL team had already begun talking about wanting to make LibAnswers/LibChat more prominent on Library Search, so having that in the header across library search is a good thing.

Other considerations:

  • we need to think about how patrons will access different portions of search; i.e. direct to journals or catalog instead of using the bento

  • we need to find a home for “bookmarks” and a “logout” link for when a patron is already logged into their library account.

  • Advanced search: Right now, there is no single advanced search. The catalog has an advanced search and PCI has an advanced search. We may need to create a landing page to handle all of the options for advanced search

Top Navigation

Needs to be the topic of a separate meeting - Looking at

Questions to ponder:

  • Should the navigation links be drop-downs or single links

  • color of the links? Black or red?

  • How do we want to handle the “Chat” link? Should this be a pop-up or go to a separate page?

  • Are “research” and “services” still the best items to have in the primary navigation?

Contact form

Three forms on the current website:

  1. Contact us form in Drupal that gets sent to asktulib which creates a LibAnswers question

  2. Email form within Ask/Help link that goes to LibAnswers but has more form options.

  3. SCRC Ask SCRC contact form.

I need to follow up with Margery and Steven and figure out if we can route all traffic through LibAnswers and just have one form.

Space Entity Index page

Service Entity page

Meeting Schedule

Action items

  •  

...

We don’t need this page. If someone wants to see a list of spaces, they can go to the relevant building.

Footer

We need to have a dedicated core team meeting to discuss the quick links in the footer. I propose

Meeting Schedule

We will continue to meet on Friday afternoons for the foreseeable future.

Action items

Decisions

  • Continue meeting every Friday at 2pm.
  • Change “Buildings” to say “Libraries” - universally throughout website
  • Create a Library for SCRC
  • Eliminate Spaces index page - users can see a list of spaces by visiting the relevant library
  • Move TUpress description to a “Group”, not library
  • Remove spaces from the footer and replace with services
  • Make the quicklinks section of the footer three columns instead of four