1. Prototype Information Architecture

2. Key Requirements Access to data, tools, and expertise –Integrated access to spatial data –Submission of info. to OWEB –Basin and watershed reports –Communication with experts –Provide expert contact info. –Text and map-based browsing/searching

3. Design Around Requirements Task: build a compelling site that meets the requirements

4. Data Organization We want to divide information by: Themes – fish, habitat, etc. Place – what is the spatial footprint of the data I want to learn about fish I want to learn about what is happening near Siletz

5. Highlight Important Information For users: What is important Why this site exists Make them interested!

6. Stories/Top Issues Plan is to rely heavily on the upcoming Coastal Coho document from OWEB/U of O Infographics Lab

7. Req: Basin and Watershed Reports Provide a tool for learning Display maps, charts and tables Example

17. Req: Text/Map-Based Browsing Provide information by topic Browse all data related to the topic

22. Questions Is it important to select information spatially? Do you want to learn about fish or fish in a specific watershed?

23. Req: Access to Spatial Data Deliver spatial data as maps

24. Accessing Digital Spatial Datasets Propose to simple web-based mapping tools Provide some of the capabilities of desktop geographic information systems Example 1 Example 2

25. Online Mapping Tools are Good For: Making custom maps Simple exploration of map layers Simple queries

26. Key Questions for Map Tool What does the mapping tool need to do for you to use it? What map layers must be present? Do you need to add your data to the system? Do you need to get data out of the mapping tool?

27. Req: Searching Keyword and spatial searching

28. Could also add ability to restrict what is searched: documents, maps, discussions etc.

29. Req: Communicate with Experts Encourage people helping people

30. Communication with Experts Options –Listserv –Web-based bulletin board –Wiki – a web-based collaboration space

31. Listserv Email based discussion list Subscribers receive all postings to list as email Can be moderated Can search list archive

32. Web-Based Bulletin Board Post announcements and questions Can see everyone’s responses Can receive email when someone makes a post or a reply You can search posts/replies Example

33. Wiki’s Web tool for team collaboration Can create web pages and comment on pages Can function like bulletin board but with extra features Example

34. Advantages and Disadvantages Listserv – People used to reading email daily. Search facilities are poor. Bulletin Board – Needs moderators. Good search tools. Wiki – Can create web pages. May be too complex.

35. Successful Group Communication Everyone needs to join in People must respond to questions/posts Are you willing to read posts daily and respond? Can we find people to cover each watershed or topic area?

36. Req: Submit Info to OWEB Submit information into our database

37. Submitting Information to OWEB Authorized users can submit documents to a storage system (database) All users can view what is in database Example

38. Submitting Information Users will have to enter some information that describes what they are uploading –Topic keywords (i.e. fish, habitat, etc.) –Place keywords (i.e. watershed name) A person will review all submissions to ensure quality What are you going to upload?

39. Req: Provide Expert Contacts Provide info. about watershed councils only Make this a part of “Learn about your watershed” Work with OWEB to ensure contact info is always up to date

40. Summary Site must deliver required functionality Focus on actions/flow Graphical look will come last