Waypoints: Forms

The Introduction Page

Description: The user interface for the Waypoints system is comprised of browsing and search interfaces. The introduction page for the collection allows users to select from the available artifact categories. By selecting a category, the result set is filtered to that particular artifact type. If one wishes to browse the entire collection, selecting "Browse" brings up an unfiltered list of categories.

To be developed: The "Collections" and "Site Guide" menus are currently unavailable; generating random images from collection and presenting those for each category.

Code(minus header/footer as shown in introduction page): See our Introduction Page Code here.

The Browse Page

Description: The main browse page presents a list of top-level facets along with their first layer children in the browseable hierarchy. As a selection is made, a list of photographs matching your selection is presented on the screen.

To be developed: Layout modification; search option; check boxes to allow searching of multiple categories (i.e. simultaneously selecting artwork and photographs).

Code: See our Browse Page Code here.

The Mid-Level (Midgame) Browse Page

Description: Here a mid-level (midgame) browse page shows a list of thumbnails representing the users' previous selection. The artifact name and short description are presented with the thumbnail.

To be developed: Sort by; pagination; search within option; change display (text only, thumbnail only, or both); left menu navigation (showing metadata choices in current data set).

Code (minus header/footer as shown in introduction page): See our Mid-Level Browse Page Code here.

The Ending (Endgame) Browse Page

Description: A final page in the browsing hierarchy shows a thumbnail image of the artifact along with descriptive content about the artifact. The user can choose to view a full size image (which appears in a new window) or to resume searching. Options are to begin a new browse using the tab menu, return to a previous screen using the breadcrumb trail, or choose a new category from with the available metadata list.

To be developed: Add numbers to available metadata list; display current metadata selection in left menu.

Code (minus header/footer as shown in introduction page): See our Ending Browse Page Code here.

The Search Page

Description: The basic search function returns a list of all available artifacts when the page is initially populated. From there, users can search via keyword and a result set is returned.

To be developed: Correct multiple keyword error; support Boolean queries; develop advanced search; return result set in same layout as browse screen.

Code (minus header/footer as shown in introduction page): See our Search Page Code here.

The Add New Photograph Page

Description: The add new photograph page allows users to add a new (photograph) artifact to the database. At the same time, users can add a new creator, donor, etc.

To be developed: Populate pull down menus with existing creators, donors, etc.

Code (minus header/footer as shown in introduction page): See our Add New Photograph Page Code here.

The SQL Page

Description: During development, we have used a database SQL query box to run queries against the database.

Code (minus header/footer as shown in introduction page): See our SQL Query Code here.

The Load Script

Description: In lieu of a specfic interface to load our initial assocation data into the database, we used a php script to populate the facet association tables using comma delimited text files we created separately.

Code (minus header/footer as shown in introduction page): See our Load Script Code here.

The Edit Photograph Page

Description: Our edit artifact record screen contains the logic to return and edit values in the database.

To be developed: Form UI for data query and submission.

Code (minus header/footer as shown in introduction page): See our Edit Photograph Page Code here.

Form Development

In addition to the changes noted for individual screens (above), additional usability testing needs to be completed as the interactive prototype is developed. With desired features implemented, usability testing will resume with a minimum of 2-3 iterations of think aloud testing.