1 / 24

Water Wiki: Tutorial

Water Wiki: Tutorial. Brand Niemann June 30, 2008 http://waterwiki.wik.is/. Information Sharing with a Web 2.0 Wiki: Tutorial. This Gov 2.0 web-services platform pilot with a Wiki interface is for the Sustainable Water Resources Roundtable (SWRR) and their broader community of practice.

lydia-serrano
Download Presentation

Water Wiki: Tutorial

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Water Wiki: Tutorial Brand Niemann June 30, 2008 http://waterwiki.wik.is/

  2. Information Sharing with aWeb 2.0 Wiki: Tutorial This Gov 2.0 web-services platform pilot with a Wiki interface is for the Sustainable Water Resources Roundtable (SWRR) and their broader community of practice. This work is part of the EPA Ontology and Ontology for Segment Data Architecture in the EPA Enterprise Architecture Program. An ontology is the categories of interest in a domain and the relationships among them. 2

  3. MindTouch Deki Features Content Creation: An editing experience similar to what you would expect from modern word processor applications. Content Management: Hierarchical page organization: Organize content in an intuitive hierarchical manner Search: Advanced search: User can view all results or only specific subsets of the result set Attachments: Users can attach any file or image to any page. Versioning and Reversion: Page versioning: Every page retains a complete history of changes. 3

  4. MindTouch Deki Features Access Control: Restrict page editing, Restrict page viewing, Restrict hierarchies Alerts and Notifications: Watch list Feeds: Every user can create a list of pages to watch. Application Administration: Site administration: Quickly and easily manage multiple users and users' status Miscellaneous: Adherence to standards: All content is stored in XML. 4

  5. Overview • 1: Decide on Name • 2: Register Name • 3: Login • 4: Set Preferences • 5: Control Panel • 6: Design Home Page • 7: Create Subtopics • 8: Repurpose Web Content Into Wiki • 9: Attach Files • 10: Insert Images and Links • 11: Create Web Log (Blog) • 12: Set Security • 13: Monitor Users • 14: Revise/Reorganize

  6. 1: Decide on Name

  7. 2: Register Name

  8. 3: Login

  9. 4: Set Preferences

  10. 5: Control Panel

  11. 6: Design Home Page Background and Purpose

  12. 6: Design Home Page Structure and Interface

  13. 7: Create Subtopics

  14. 8: Repurpose Web Content Into Wiki

  15. 9: Attach Files

  16. 9: Attach Files

  17. 9: Attach Files

  18. 10: Insert Images and Links

  19. 10: Insert Images and Links

  20. 11: Create Web Log (Blog)

  21. 12: Set Security

  22. 12: Set Security • Public: everybody can view and edit. • Semi-Public: everybody can view, but only selected users can edit. • Private: only selected users can view and edit this page. • Note: Deki Wiki has one of the most advanced permission systems available. Deki Wiki administrators can make wikis public or private, anonymous or not. There is user groups support. Users can permission entire hierarchies to create private or non-editable workspaces or permission single pages.

  23. 13: Monitor Users

  24. 14: Revise/Reorganize • To soon for this new Wiki, but for another EPA Web 2.0 Wiki Project I did the following quickly: • Moved content from Wiki to another Wiki. • Implemented a set of topics and subtopics. • Created a new user interface. • Updated the Tutorial slides and uploaded them. Note: This shows how agile and flexible the Web 2.0 Wiki environment is to respond to requests that would be more difficult (or impossible) and time consuming with Web 1.0 collaboration technology.

More Related