Transcript Document 7572806

Library Research Roundtable
(LRRT) Mentor Web Site
i-Team
INFO 652 Internet Resource Design
16 May 2007
Presentation Overview
•
•
•
•
•
LRRT & customer requirements (Dick)
Content (Beth)
Site design (Karin)
Technical (Megan)
Usability (Bob)
Role of the Project Manager
• To Listen With a “Third Ear”
• To Provide a Clear Channel of
Communication Between the Client & The
Team
• To Be Aware of & Sensitive To The Needs
of Both Parties
• To Broker Thoughtful Compromises if
Necessary
Customer Requirements
• Submit Mentor Applications
• Submit Mentee Requests
• Links to External Resources
• Success Stories
• LRRT / Conference Information
Content
Homepage
- program overview
Mentors
-expectations
Mentees
-expectations
Email
-contact info
-research
conducted
-areas of
expertise
-C.V.
Email
-contact info
-research
concerns
-areas of
interest
LRRT
-overview
-links
Useful
Resources
-citation formats
-sample size
-publication
advice
Future
-success
stories
-completed
projects
Mentor Page
Want to be a part of an interesting and satisfying
learning experience?
We are looking for committed and responsible people to act
as volunteer mentors. As a mentor you will be a friend,
guide, teacher, helper, and an adviser to a mentee.
Benefits:
•A way to acquire further leadership skills
•Be a part of the development of the research
skills of a colleague
•Good networking opportunity
•Excellent way to get to know new people in the field
Mentor--Email
1. What types of research do you conduct? (Options Provided)
2. What are your areas of expertise? (Options Provided)
3. With what types of populations do you work? (Options Provided)
4. In what capacities would you like to serve as a mentor?
(Options
Provided)
5. Please describe your current research interests using about four or
five keywords or phrases. (For example, the following phrases
would enhance, rather than repeat, the rest of the profile:
"information seeking behavior," "in-depth interviewing," "community
profiles," or "public libraries.")
6. Finally, please provide your name, job title, institutional affiliation,
phone number, and preferred email address as you would like them
to appear in the LRRT Research Mentor database
Site Design
Site Design
Technical
As of Now: Facing a Few Obstacles
• Thus far client has identified content needs,
but no design suggestions.
• Dreamweaver tried to kill my laptop.
• Two major challenges await the coding
process.
Challenges
• Challenge 1: Site will exist outside of
the ALA structure
Response: Create a simplistic CSS that
resembles the ALA design in
color, structure, and
organization.
 Client has informed us that it is not necessary to
directly link to ALA.
Challenges
• Challenge 2:
Because the site will not be supported
by ALA, it will not be supported by a server
 Forms will not be possible without a server to respond to requests or
a server-side script to format the submission.
Response:
I’ve identified two options:
1. Utilize the basic HTML "Mailto" feature (Question of reliability)
2. Rely on a remotely hosted CGI script (Pending client approval)
 Ex: Response-o-Matic( http://www.response-o-matic.com )
Goals
• Ensure a smooth transition from our hands to
the client
• Create a refined and efficient web site that
allows minimal user interaction without need for
elaborate coding
• Meet and exceed expectations of the client out
of sheer resourcefulness and possibly some
divine favors
Usability
• Site needs to be tailored to intended users
– Get demographic information about typical users
– Develop user profile information to guide design choices
– Provide requirements/guidelines to Site Design &
Technical managers
• Site needs to be usability tested to ensure that it
works
– Prototype testing with hybrid “beta” site & paper
prototype
– W3C compliance using “Bobby” tool
Demographic Considerations
• Who will use the site?
–
–
–
–
Education level
Involvement with LRRT
Familiarity with computers
Primary language
• How will they interact with it?
– Frequent reference vs. occasional browsing
– Type of computers / browsers & connection (dial up vs. highspeed)
– Stand-alone sessions vs. close coupling with rest of LRRT web
site
• What special needs do the users have?
Intended User Matrix
User profile
Design implications
Age range:
college to
retirement
Site must use large font (at least 12-14 pt) and have high
contrast for visibility to suit users with moderate eyesight
Knowledge level:
LRRT &
prospective
members,
education BS+
Site can use some specialized language of the profession.
Site does not have to be designed for “general public”.
Frequency of use:
Once of twice a
year
Infrequent visits mean that site must be extremely easy to
navigate. Shortcuts and time-saving navigation routes for
site experts not necessary.
Computing skills of Can take advantage of knowledge of users by integrating
users: Most users e-mail in site as mechanism for sending data to site
familiar with
owners.
communication via
web & e-mail
Intended User Matrix (cont.)
User profile
Design implications
User language:
English
Considerations for foreign-language users not necessary.
Consideration for foreign-country usability minimal.
ADA Accessibility:
TBD
Not mandated by site sponsors. However, ALA’s
emphasis on ADA accessibility makes compliance of site
with W3C guidelines highly desirable.
Integration with
main site: not
required
Site will be stand-alone, with just links to main LRRT site.
Therefore, interoperability issues and navigation external
to mentor site not a major design driver.
Computing
hardware
High-speed connection not guaranteed. Site should be
compatible with a variety of browsers and load quickly
using dial-up (e.g. no graphic-intensive content).
Usability Testing
• Plan to conduct usability testing with 3-5 users
– Target audience = LRRT members or MLIS students
with interest in research
• Will devise scenarios for users to step through (specific
tasks)
– Tasks will focus on most likely use of site (e.g.
mentees looking for mentors)
• Testing will utilize combination of beta web site and
paper prototype pages for sections not coded yet
• Site will be evaluated for ADA compliance using “Bobby”
THE END