Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Group


Published on

1. Background:
1.1 Supporting EPA's Top Priorities
1.2 An EPA EA Roadmap
1.3 Solution Architecture 2010
1.4 My List of Action Items
1.5 EPA’s OGD Workgroup
1.6 EPA’s New Social Media Policy
2. EPA’s One Wiki:
2.1 Initial Impressions
2.2 The Environment in Wikipedia
2.3 Web 2.0 Whitepaper Pilot Wiki
2.4 Information / Data Model
2.5 Sheetster for
3. Recommendations

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Group

  1. 1. Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Group Brand Niemann Senior Enterprise Architect US EPA February 4, 2010
  2. 2. Overview <ul><li>1. Background: </li></ul><ul><ul><li>1.1 Supporting EPA's Top Priorities </li></ul></ul><ul><ul><li>1.2 An EPA EA Roadmap </li></ul></ul><ul><ul><li>1.3 Solution Architecture 2010 </li></ul></ul><ul><ul><li>1.4 My List of Action Items </li></ul></ul><ul><ul><li>1.5 EPA’s OGD Workgroup </li></ul></ul><ul><ul><li>1.6 EPA’s New Social Media Policy </li></ul></ul><ul><li>2. EPA’s One Wiki: </li></ul><ul><ul><li>2.1 Initial Impressions </li></ul></ul><ul><ul><li>2.2 The Environment in Wikipedia </li></ul></ul><ul><ul><li>2.3 Web 2.0 Whitepaper Pilot Wiki </li></ul></ul><ul><ul><li>2.4 Information / Data Model </li></ul></ul><ul><ul><li>2.5 Sheetster for </li></ul></ul><ul><li>3. Recommendations </li></ul>
  3. 3. 1.1 Supporting EPA's Top Priorities <ul><li>During the SES Conference, the Administrator also asked that we work as “One EPA” in finding ways to think and act in much broader, cross-organizational and collaborative ways. I fully support this vision and view it as the foundation of our work and the culture of OEI. I believe it is the nature of our business to embrace collaboration and the essence of our mission is to seek innovation. In closing, I am proud of your work, and appreciate your continued commitment to finding creative solutions and innovative ways to improve our day to day business. </li></ul><ul><ul><li>Linda A.Travers, Principal Deputy Assistant Administrator, Office of Environmental Information, Environmental Protection Agency, January 22, 2010, Email to All. </li></ul></ul>
  4. 4. 1.2 An EPA EA Roadmap Source: Brand Niemann, January 18, 2010. Alternative analyses, etc. Cloud Computing Desktop / Mobile Apps Agency & Cross-Agency Innovations Regions 4 & 7, etc. Reusable Component Services Program Offices & Regions Solutions Segments, etc. Business-as-Usual OMB Compliance Clients How? Who? What?
  5. 5. 1.3 Solution Architecture 2010 Note: For methodology and results see Implement Cloud Computing Desktop Recent Meetings Enterprise Tools Implement Enterprise Data Architecture Recent Assessment Enterprise Data Architecture Implement Model-Driven Architecture IMPART Pilot with Troux for Water EA Tools Actions Current Activity
  6. 6. 1.4 My List of Action Items <ul><li>Task 1: Work with Eric Marks (not an EPA contractor, but a member of our federal cloud computing team) to get his Cloud Computing Reference Model into Troux (like the FEA E-Gov Module) so we can use it in IMPART to do Cost Alternative Analyses as required by OMB this year. </li></ul><ul><li>Task 2: Update my Target Architecture 3.0 to includes Eric's Cloud Computing Reference Model and the Open Government Directive work I am doing for the Office of the Administrator / Office of Environmental Innovation and the CIOC Best Practices Committee in support of the recent Open Government Directive Workshop and CIOC Boot Camp Training, respectively. </li></ul><ul><li>Task 3: Work to mentor others in becoming Solution Architects by creating a training module based on a SOA with web-services - reusable component services for each EPA Region (patterned after the current work for Regions 4 and 7) for the upcoming workshops in February and March. I already have tutorials of the Solution Architecture work that I have done for Region 4 and the two segments (Lisa and Vince). As we discussed, this interfaces with Kevin's work on Data Architecture using the four layer model (Information Architecture - topic and subtopic and Data Architecture - data table and data element). </li></ul>
  7. 7. 1.4 My List of Action Items <ul><li>I am hoping that all of this will help sell this to management - as we discussed in the planning session - the fact that I had already done so much of this and as our facilitator said &quot;little or no new resources&quot; would be needed! I have materials for each of these three tasks that would help us in doing that since I have been implementing SAs since I was selected to be a member of the original Federal SAWG (Solution Architects Working Group) by the first OMB Chief Architect, Bob Haycock, in 2002. Those solution architectures are all posted on the Web to be used and re-used. </li></ul><ul><ul><li>See and </li></ul></ul>
  8. 8. 1.5 EPA’s OGD Workgroup <ul><li>Meeting Agenda, January 28, 2010: </li></ul><ul><ul><li>Welcome and Updates </li></ul></ul><ul><ul><li>Status of Key Actions </li></ul></ul><ul><ul><ul><li>OMB Open Government Meeting </li></ul></ul></ul><ul><ul><ul><li>Open Government Dashboard </li></ul></ul></ul><ul><ul><ul><li>Accomplishments </li></ul></ul></ul><ul><ul><ul><li>Open Government Web Site </li></ul></ul></ul><ul><ul><li>Plan and Wiki Demonstration </li></ul></ul><ul><ul><li>Next Steps </li></ul></ul>
  9. 9. 1.5 EPA’s OGD Workgroup <ul><li>Meeting, January 28, 2010: </li></ul><ul><ul><li>Comments and Followup: </li></ul></ul><ul><ul><ul><li>Lisa Schlosser – exceeds expectations and address criticisms in the Washington Post (1) </li></ul></ul></ul><ul><ul><ul><li>Pat Bonner – make this a more open and collaborative process (2) </li></ul></ul></ul><ul><ul><ul><li>Dalroy Ward – make this work on mobile devices (3) </li></ul></ul></ul><ul><ul><ul><li>David Eng – help with design on the EPA One Wiki (4) </li></ul></ul></ul><ul><ul><ul><li>Jeffrey Levy – EPA’s New Social Media Policy (5) </li></ul></ul></ul><ul><ul><ul><li>Andrea DiMaio (Member of Gartner Blog Network) - US EPA Social Media Policy: One Step Forward, Two Steps Back (6) </li></ul></ul></ul><ul><ul><ul><li>Tom Lee (Sunlight Foundation) – Data Quality Needs to be Tackled on its Own (7) </li></ul></ul></ul><ul><ul><ul><li>Author – Why Not Integrate Your OGD Plan, Website, Dashboard, and Data Publishing Like We Did in the EPA Web 2.0 Whitepaper and Subsequent Activities? (8) </li></ul></ul></ul><ul><ul><ul><li>OMB – agencies need to move towards “self-actuating data sets” (9) </li></ul></ul></ul>See next slide for explanation of footnotes.
  10. 10. 1.5 EPA’s OGD Workgroup <ul><li>(1) Info released under Obama transparency order is of little value, critics say , Washington Post, January 28, 2010. </li></ul><ul><li>(2) EPA’s Public Involvement Policy (2003) </li></ul><ul><li>(3) Several recent emails with author. </li></ul><ul><li>(4) These slides for meeting on February 4, 2010. </li></ul><ul><li>(5) Guidance : Representing EPA Online Using Social Media, Jeffrey Levy, January 29, 2010. </li></ul><ul><li>(6) US EPA Social Media Policy : One Step Forward, Two Steps Back, Andrea DiMaio, January 29, 2010. </li></ul><ul><li>(7) Data Quality Needs to be Tackled on its Own , Tom Lee, January 28, 2010. </li></ul><ul><li>(8) EPA Web 2.0 Whitepaper , February 2008. </li></ul><ul><li>(9) Self-actuating data sets (e.g. RDF ) </li></ul>
  11. 11. 1.6 EPA’s New Social Media Policy <ul><li>This policy seems to suggest that engagement in social media is only a part of communication strategy, and little else. But, as I said a while ago, engagement and communication are on a collision course. So what the EPA and other agencies also need is not a policy (codes of conduct and ethical programs usually suffice) but an engagement strategy based on letting employees engage by leveraging rather than fighting the unavoidable blurring of their personal and professional personas. </li></ul><ul><ul><li>US EPA Social Media Policy : One Step Forward, Two Steps Back, Andrea DiMaio, January 29, 2010. </li></ul></ul>
  12. 12. 2. EPA’s One Wiki
  13. 13. 2.1 Initial Impressions <ul><li>It won’t equal Wikipedia’s content and organization on the Environment, etc. so develop a strategy to link to Wikipedia and just post what is unique EPA content. </li></ul><ul><li>The current interface is too busy/complicated. </li></ul><ul><li>There needs to be an Information / Data Model for ease of use and standardization of content. </li></ul><ul><li>I suggest the pilot I did for the EPA Web 2.0 Whitepaper as an example to follow. </li></ul>
  14. 14. 2.2 The Environment in Wikipedia http://
  15. 15. 2.2 The Environment in Wikipedia <ul><li>Wikipedia  is a multilingual, web-based, free content encyclopedia project with over 2,000,000 articles in English. There are  two ways  to look things up in Wikipedia: by searching or by browsing. Some initial browsing results of interest to EPA are as follows: </li></ul><ul><ul><li>EPA   </li></ul></ul><ul><ul><li>Environment or Environmental  (see next slide) </li></ul></ul><ul><ul><li>Environmental Issues  (16 topics and 70 subtopics) </li></ul></ul><ul><ul><li>Environment topics  (alphabetical - being considered for deletion) </li></ul></ul><ul><ul><li>Environment Categories  (38 subcategories and 136 pages) </li></ul></ul><ul><ul><li>Environmental organizations  (article or section is incomplete) </li></ul></ul><ul><ul><li>Portal   </li></ul></ul>
  16. 16. 2.2 The Environment in Wikipedia <ul><li>Wikipedia:  Disambiguation : </li></ul><ul><ul><li>When an article title could refer to several things, a disambiguation page is needed. When the title usually means one thing but also has other meanings, add disambiguation links to the primary topic's article. </li></ul></ul><ul><ul><li>Disambiguation in Wikipedia is the process of resolving conflicts in article titles that occur when a single term can be associated with more than one topic, making that term likely to be the natural choice of title for more than one article. In other words, disambiguations are paths leading to the different article pages that could use essentially the same term as their title. </li></ul></ul><ul><ul><li>For example, the word &quot;Mercury&quot; can refer to several different things, including: an element, a planet, an automobile brand, a record label, a NASA manned-spaceflight project, a plant, and a Roman god. Since only one Wikipedia page can have the generic name &quot;Mercury&quot;, unambiguous article titles must be used for each of these topics: Mercury (element), Mercury (planet), Mercury (automobile), Mercury Records, Project Mercury, Mercury (plant), Mercury (mythology). </li></ul></ul>
  17. 17. 2.3 Web 2.0 Whitepaper Pilot Wiki http:// /
  18. 18. 2.4 Information / Data Model <ul><li>Information: </li></ul><ul><ul><li>Topic </li></ul></ul><ul><ul><li>Subtopic </li></ul></ul><ul><ul><li>Sub-subtopic (if needed for document table of contents) </li></ul></ul><ul><li>Data: </li></ul><ul><ul><li>Data Table </li></ul></ul><ul><ul><li>Data Elements (metadata) (Note: This can be combined / integrated with the Data Table) </li></ul></ul>See
  19. 19. 2.4 Information / Data Model http:// Site Map: Automatically Generated! Also Simplified Left-hand Pane for Ease-of-Navigation
  20. 20. 2.4 Information / Data Model <ul><li>Standarized Metadata Elements: </li></ul><ul><li>Title </li></ul><ul><li>Headnote </li></ul><ul><li>Table </li></ul><ul><li>Symbol </li></ul><ul><li>Footnote </li></ul><ul><li>Source </li></ul><ul><li>For More Information </li></ul>Integrated with the Data and Exposed as an RSS Feed and Web-Service!
  21. 21. 2.5 Sheetster for http://
  22. 22. 2.5 Sheetster for
  23. 23. 2.5 Sheetster for )
  24. 24. 3. Recommendations <ul><li>We did an OGD-like Plan, February 2008: </li></ul><ul><ul><li>EPA Web 2.0 Whitepaper. </li></ul></ul><ul><li>We did an OGD-like Plan Implementation, December 2007: </li></ul><ul><ul><li> MindTouch Deki Wiki, that evolved to a web-services platform, and now is an Internet operating system cloud desktop / mobile app store. </li></ul></ul><ul><li>We did a –like Implementation (July 2008): </li></ul><ul><ul><li> that used the EPA Report on the Environment content (text, metadata, and spreadsheets). </li></ul></ul><ul><li>We suggested this be done by individuals, December 2009: </li></ul><ul><ul><li> suggested Putting Your Desktop in the Cloud in Support of the OGD and </li></ul></ul><ul><li>Now we are showing how this can be applied to the agency’s OGD Plan, Website, Dashboard, and Publication of Three Data Sets! </li></ul><ul><ul><li>Integrate Your OGD Plan, Website, Dashboard, and Data Publishing. </li></ul></ul>
  25. 25. 3. Recommendations <ul><li>Some specific examples: </li></ul><ul><ul><li>Topic: </li></ul></ul><ul><ul><li>Subtopic: </li></ul></ul><ul><ul><li>Sub-subtopics: </li></ul></ul><ul><ul><li>Etc. </li></ul></ul><ul><ul><li>Data Table:’s_Resources_by_Appropriation </li></ul></ul><ul><ul><li>Data Elements: Same as above but could be separate page with links from Data Element Column Names </li></ul></ul><ul><li>See Wikify Your Metadata: </li></ul><ul><ul><li> </li></ul></ul>
  26. 26. 3. Recommendations <ul><li>Now each page has metadata in the following ways: </li></ul><ul><ul><li>(1) Use of well-defined URLs (automatic, but requires some forethought and organization to take full advantage of): </li></ul></ul><ul><ul><ul><li>See </li></ul></ul></ul><ul><ul><li>(2) Use of comments at bottom of page (let others help you): </li></ul></ul><ul><ul><ul><li>See http:// / at bottom of page </li></ul></ul></ul><ul><ul><li>(3) Use of tags for each page (a little work) </li></ul></ul><ul><ul><li>(4) Use of a template for each page (e.g. Dublin Core!) (more work as we all know) </li></ul></ul><ul><li>Note: For Items (3) and (4) see: </li></ul><ul><ul><li> and </li></ul></ul><ul><ul><li> , respectively. </li></ul></ul><ul><li>Try a Google Search Like: epa wiki Collaboration Practitioners Network (EPA Wiki Budget is too new for Google to have indexed it yet - but try this in a week or less) </li></ul>