recommended reading

Do we need a governmentwide wiki?

Government wikis such as the State Department’s Diplopedia and the intelligence community’s Intellipedia aim to be go-to resources for federal employees to get information about internal or external matters, such as how to organize a particular report or where colleagues in a reorganized bureau landed.
One of the greatest benefits of government wikis, though, may come if and when they’re opened up beyond the agency level so that employees can investigate how other offices handle similar processes and programs, Peter Meyer, who helped develop Statipedia for the Bureau of Labor Statistics, said Friday.
Meyer was speaking at the State Department’s tech@state conference on government wikis.
“I had always thought that a broad cross-government wiki would be better and that we’d get there by one of these expanding to be available to everyone,” he said. “It isn’t happening yet . . . The path the U.S. structure is on leads to more and more wikis, which means more and more administrators, more and more domain spaces, and more and more battles over what software should be brought in and how.”
When Meyer was working on a social media team at BLS, he solicited information from other agencies about their policies for updating Wikipedia pages that dealt with areas of agency expertise.
“I discovered after posting a page inviting comment on this issue that [the Environmental Protection Agency] has a good set of rules and [the National Institutes of Health] has a good set of rules,” he said. “These are good examples for us. For an agency that doesn’t wish to lead on a particular subject it helps a lot to have a library of what other agencies are doing.”
A governmentwide wiki could offer precisely that sort of information, he said.
Ryan Androsoff runs GCPedia, the Canadian government’s governmentwide wiki, which launched in 2008. He said employees frequently seek out their counterparts or people with particular expertise in another agency.
are defined by online content that’s updated and edited by a group of people rather than a single administrator. Their content can be broad, as the model Wikipedia, or narrow as Diplopedia. 
Most government wikis exist at the agency level and are closed off to other agencies and the public.
Diplopedia, which is among the most long-standing government wikis, focuses on “persistent, evolving knowledge,” said Tiffany Smith. She works in State’s eDiplomacy office, which manages the site.
For instance, the department used to publish post reports, which were extensive descriptions of life in particular countries that diplomats could browse through as they considered their next assignment.
The reports could become quickly outdated in physical form, Smith said. When transferred to Diplopedia, they’re not only current, but they can be updated on the fly by diplomats on the ground when something changes.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.


When you download a report, your information may be shared with the underwriters of that document.