Project
Proposal for Information Architecture Evaluation and Redesign for LANIC Website
Team Members: Diana Miranda, Kam McEvoy, Norma Palomino, Tabassum Khan, Verónica Parsiale
1.
Introduction
The Latin American Network Information Center’s (LANIC) (http://www.lanic.utexas.edu) mission is “to facilitate access to Internet-based information to, from, or on Latin America.” Its main audience includes people living in Latin America, as well as those around the world who have an interest in the region. While its website is designed to facilitate academic research, the site has also become an important gateway to Latin America for about anyone looking for information on this region.
LANIC reviews, evaluates, and compiles a broad directory of links to Internet resources on and from Latin America, available in English, Spanish, and Portuguese.
After several years, the site grew in pages, links, and information, making it difficult to navigate, to maintain consistency across different pages, resulting in many cases in overlapping information.
2.
The Project
2.1
Purpose
This project constitutes an attempt to analyze, evaluate, and offer an alternative design for LANIC’s website. The final product will be a proposal document and key web pages templates to be submitted to LANIC’s site managers for consideration.
2.2
Objectives
a) To gather data about the content, context, and users of the site regarding its current design and usability.
b) To assess the strengths and weaknesses of the site considering LANIC’s mission, goals, organizational structure, and users’ profile.
c) To develop an information architecture strategy for redefining the site.
2.2.1 Critical Success Factors
These factors are twofold. First, the collaboration of the site’s internal and external users in the process of evaluation, as well as the availability of the documentation by LANIC’s managers. Overcoming research resistance constitutes the most important factor because this project is actually assessing and redefining an existent site, which holds an established culture of using related to it. The second is creativity, given the limited budget and human resources available.
2.3 Assumptions
2.4 Constraints
2.5 Risks
2.
There is also the possibility of undermining Latin American user’s
needs (i.e. external users) by following the demands of the internal users (LANIC
managers, researchers, etc.).
3.
A third risk is related to the implementation of a site with limited
technological resources, because it can contrast with the general informational
architecture of most sites at UT-Austin.
2.6
Team Members
Tabassum Khan, tabassum@mail.utexas.edu
Kam McEvoy, kamcevoy@mail.utexas.edu
Diana
Miranda, diana@correo.co.cr
Norma
Palomino, norpa@gslis.utexas.edu
Verónica
Parsiale, parsiale@gslis.utexas.edu
2.7
Team Responsibilities
|
Team
members |
Group
Responsibilities |
Individual
Responsibilities |
|
Diana Miranda |
|
Interact with the LANIC team and content analysis Work on site redesign |
|
Kam McEvoy |
Work on site redesign and graphics. Redesign help features for the site. |
|
|
Norma Palomino |
Interaction with the LANIC team for feedback and other inputs. Work on site redesign |
|
|
Tabassum Khan |
Identify the technology that can be used for the project. Develop prototypes and design templates. Identify existing search techniques and suggest improvements. |
|
|
Verónica Parsiale |
Gather inputs from LANIC team. Work on workflow for the site. |
3.
Project Planning
3.1
Project Scope
· Evaluation the site as a whole
· Focus on pages with main architectural problems. Development of page templates addressing current problems and proposed solution.
3.2
Deliverables
· Page templates evidencing proposed solutions for main problems identified in the site’s evaluation phase.
· Documentation:
The group shall maintain the following details collectively: -
Project proposal
Project Plan
Requirements study results
Information Architecture methodology
Design templates/ Project prototype
Feedback from LANIC team
3.3
Timeline for Deliverables
The timelines as detailed here shall be maintained :
|
Tasks |
Original
Start date |
Original
End date |
Actual
Start date |
Actual
End Date |
Modified
by |
Comments |
|
Prepare
Project Proposal |
9/15/2002 |
9/23/2002 |
9/15/2002 |
9/23/2002 |
|
This
shall be updated as the project progresses |
|
Identify
key people a LANIC for inputs on the project. |
9/20/2002 |
|
|
|
|
Norma interviewed Kent Kent Norsworthy, Content Director- LANIC Also
starting with a comparative analysis with similar Latin American sites |
|
Analysis
of User Requirements |
9/23/2002 |
10/1/2002 |
|
|
|
|
|
Identify user groups(including people accessing the site and those
administering the site) |
|
|
|
|
|
|
|
Study the existing problems in design based on feedback received from
users (through the ‘comments form’ on the site. |
|
|
|
|
|
|
|
Identify the key people involved in site content management and
administration. |
|
|
|
|
|
|
|
Interact with the LANIC group to identify future developments planned
for the site. |
|
|
|
|
|
|
|
Identify the technologies in use currently-search engine, website
publishing and maintenance, databases the site has access to. |
|
|
|
|
|
|
|
Study the search needs of user vis-a vis what the site offers
currently. |
|
|
|
|
|
|
|
Evaluate
design options |
10/1//2002 |
10/10/2002 |
|
|
|
|
|
Evaluate
providing a site index for the site, search features |
10/1//2002 |
10/10/2002 |
|
|
|
|
|
Improvements
of browsing features on the site |
10/1//2002 |
10/10/2002 |
|
|
|
|
|
Draft
design prototype for review by LANIC team |
10/10/2002 |
11/10/2002 |
|
|
|
|
|
Incorporate
feedback received on the draft prototype. |
11/10/2002 |
11/20/2002 |
|
|
|
|
|
Final
Design prototype for submission |
|
|
|
|
|
|
|
Group
presentation of Information Architecture design for LANIC site. |
10/30/2002 |
12/3/2002 |
|
|
|
The
presentation shall be finished 5 days in advance to the delivery date. |
3.4
General content specifications
LANIC’s
website consists primarily in pages with links to relevant resources on or from
Latin America.
3.4.1
Existing content and design
Links
are organized in two main categories: Countries and Subject areas. Within each
country page, links are divided into main subject areas subcategories. Likewise,
within each subject area, links are broken into country, regional, and
international resources subcategories.
Example:
Country page: Brazil
Subcategories:
Academic Research Resources, African Diaspora, Agriculture & Ranching,
Architecture, Arts & Humanities, … Health, etc.
Subject page: Health & Medical Sciences
Subcategories:
Argentina, Bolivia, Brazil, … Regional Resources, Subject Areas (Aids, Cancer,
Pharmaceuticals, etc.)
LANIC’s
architectural design is based on the principle of simplicity, partly because of
the weak technological communications infrastructure available in Latin America.
The graphics are kept to a minimum because of the bandwidth and connectivity
constraints faced by users in Latin American countries. However, this approach
produces a lack of consistency among the different pages categories and
subcategories.
On
the other hand, the huge amount of links and their unstable nature, impedes the
development of certain tools that would enhance consistency, such as an index.,
but we believe other solutions are available.
One of the main problems
with the existent architecture design is that the links under Brazil-Health, and
Health & Medical Sciences-Brazil, for example, won’t be the same.
Therefore, if a researcher looks for information under Brazil-Health, but
doesn’t look under Health & Medical Sciences-Brazil, he will probably miss
important links. Even though for LANIC’s web authors there is a
difference between the content of country pages and the content of subject
pages, it may not be clear to the end user.
According to Kent
Norsworthy, who is the person in charge, the idea is that the
“Brazil-Health” page must have the general links about health in that
country and the “Health and Medical Sciences-Brazil” page must have the
specific links related to the topic in Brasil.
This is a good argument but it means that an important part of the
project should be to think how to make clear to the end user this difference
between categories.
The index page for the
site fails to introduce to a new user some good features offered by the site
like access to twelve specific databases, site map, site tour and so on.
3.4.2
New Content and Design
This project proposes to keep the same content available but to change the architecture and design. The main idea is to improve the web site’s users usability and increase the team productivity.