Tag Archives: DC

Open government advocates: terms and conditions mean DC open data is fauxpen data

Posted on by

1

500px-WilsonbldgEarlier this summer, this blog covered the launch of District of Columbia’s executive order on open government, open data policy, open data platform and online FOIA portal. Last week, the Sunlight Foundation laid out what DC should have done differently with its open data policy.

“The evolution of open data policies since 2006 provides a chance for stakeholders to learn from and build on what’s been accomplished so far,” wrote policy associate Alisha Green. “This summer, a new executive directive from Mayor Vincent Gray’s office could have taken advantage of that opportunity for growth, It fell far short, however. The scope, level of detail, and enforceability of the policy seem to reveal a lack of seriousness about making a significant improvement on DC’s 2006 memorandum.”

Green says that DC’s robust legal, technology and advocacy community’s input should have helped shape more of the policy and that “the policy should have been passed through the legislative, not executive, process.” Opportunities, missed.

Yesterday, civic hacker and Govtrack.us founder Joshua Tauberer took the critique one step further, crying foul over the terms of use in the DC data catalog.

“The specter of a lawsuit hanging over the heads of civic hackers has a chilling effect on the creation of projects to benefit the public, even though they make use of public data released for that express purpose,” he wrote. “How does this happen? Through terms of service, terms of use, and copyright law.”

The bottom line, in Tauberer’s analysis, is that the District oF Columbia’s open data isn’t truly open. To put it another way, it’s fauxpen data.

“Giving up the right to take legal action and being required to follow extremely vague rules in order to use public data are not hallmarks of an open society,” writes Tauberer. “These terms are a threat that there will be a lawsuit, or even criminal prosecution, if civic hackers build apps that the District doesn’t approve of. It has been a long-standing tenant that open government data must be license-free in order to truly be open to use by the public. If there are capricious rules around the reuse of it, it’s not open government data. Period. Code for DC noted this specifically in our comments to the mayor last year. Data subject to terms of use isn’t open. The Mayor should update his order to direct that the city’s “open data” be made available a) without restriction and b) with an explicit dedication to the public domain.”

In the wake of these strong, constructive critiques, I posted an update in an online open government community wondering what the chances ar that DC public advocates, technologists, lawyers, wonks, librarians and citizens will go log on to the DC government’s open government platform, where the order is hosted, and suggest changes to the problematic policy? So far, few have.

The issue also hasn’t become a serious issue for the outgoing administration of Mayor Vincent Gray, or in the mayoral campaign between Muriel Bowser and David Catania, who both sit on the DC Council.

The issues section of Bowser’s website contains a positive but short, vague commitment to “improved government”: “DC needs a government that works for the people and is open to the people,” it reads. “Muriel will open our government so that DC residents have the ability to discuss their concerns and make suggestions of what we can do better.”

By way of contrast, Catania published a 128 page platform online that includes sections on “democracy for the District” and “accountable government.”(Open data advocates, take note: the document was published on Scribd, not as plaintext or HTML.) The platform includes paragraphs on improving access to government information, presenting information in user-friendly formats, eradicating corruption and rooting out wasteful spending.

Those are all worthy goals, but I wonder whether Catania knows that the city’s current policy and the executive order undermines the ability and incentives for journalists, NGOs, entrepreneurs and the District’s residents to apply the information he advocates disclosing for the purposes intended.

Last week, I asked Bowser and Catania how their administrations would approach open data in the District.

To date, I’ve heard no reply. I’ve also reached out to DC’s Office of Open Government. If I hear from any party, I’ll update this post.

Update: In answer to a question I posed, the Twitter account for DC.gov, which manages DC’s online presence and the open data platform in question as part of the Office of the Chief Technology Officer, indicated that “new terms and conditions [were] coming shortly.” No further details were offered.

DC city government issues executive order on open data, FOIA portal and chief data officer

Posted on by

6

Today, the District of Columbia launched a new online service for Freedom of Information Act requests and Mayor Vincent Gray issued a transparency, open government and open data directive. DC city government has come under harsh criticism from the ACLU for its record on FOIA and transparency and has a spate of recent corruption scandals, albeit not one that appears to be worse than other major American cities.

“This new online FOIA system is a key part of our strategy to improve government transparency and accountability,” said Mayor Gray, in a statement. “In addition, the executive order I am issuing today sends an important message to District government agencies and the public: Everyone wins when we make it easier for the public to understand the workings of the District government. I also look forward to seeing the exciting applications I hope the District’s technology community will develop with the government data we will be putting online.”

Here’s what Mayor Gray has instructed DC government to do:

1) Within 30 days from today, the DC chief technology officer (currently Rob Mancini) must create “a common Web portal” that “will serve as the source for District-wide and agency activities related to this Transparency and Open Data Directive.” Translation: OCTO must create a new website that aggregates information related to this directive.

2) OCTO will publish technical standards for open data by November 1, 2014. DC government could refer to the Sunlight Foundation’s Open Data Guidelines as a useful reference, or the canonical 8 principles of Open Government Data.

3) Within 120 days from today, the DC City Administrator and each deputy mayor must identify at least 3 new high-value datasets to publish to the DC Data Catalog that are either not currently available or not available in an exportable format.

4) Starting on October 1, 2014, and continuing annually, each DC agency will develop and publish an “Open Government Report” that will “describe how the agency has or will enhance and develop transparency, public participation, and collaboration. Each agency shall include in its open government report a description of the information (including data) that will be made available to the public, formats in which information and data will be made.”

Translation: city agencies will report on how they’re doing complying with this mandate. Hopefully, the DC Office of Open Government will be an effective ombudsman on that progress, along with directly engaging on Freedom of Information Act disputes and processes, and will do more public engagement around open government or open data than @OCTONEWS has to date.

Unfortunately, and not a little bit ironically, the directive was published online as a scanned-in PDF that is neither searchable nor accessible to the blind, itself embodying the way not to release text online in the 21st century. Below, I have summarized the main deliverables mandated in the directive and converted the images to plain text. Following the order is criticism from open government advocate, civic hacker, and DC resident Josh Tauberer.

GOVERNMENT OF THE DISTRICT OF COLUMBIA

ADMINISTRATIVE ISSUANCE SYSTEM

Mayor’s Order 2014-170
July 21, 2014

SUBJECT: Transparency, Open Government and Open Data Directive

ORIGINATING AGENCY: Office of the Mayor

By virtue of the authority vested in me as Mayor of the District of Columbia by section 422(2) and (11) of the District of Columbia Home Rule Act, approved December 24, 1973, 87 Stat. 790, Pub. L. No. 93-198, D.C. Official Code § 1-204.22(2) and (11) (2012 Repl.), and section 206 of the District of Columbia Freedom of Information Act, effective March 25, 1977, D.C. Law 1-96, D.C. Official Code § 2-536 (2012 Repl.), it is hereby ORDERED that:

SECTION 1: Introduction.

a. Background. The District of Columbia government (“District”) is committed to creating an unprecedented level of openness in government. Agency heads will work together and with the public to ensure public trust, and an open and effective government by establishing a system of transparency, public participation, collaboration, and accountability that increases the public’s confidence in their government. The goal of this directive is to provide a tool for prescribing and institutionalizing change within all departments and agencies.

The District has been a leader in government transparency and open data policy in the United States. In 2001, the Freedom of Information Act was amended to require that certain public records be published online. Since 2006, the District has been making data publicly available on the Internet. In January 2011, Mayor’s Memorandum 2011-1, entitled Transparency and Open Government Policy, was issued, recognizing that the District government needed to continue to proactively provide information to citizens, and thereby reduce the need for information requests. This directive implements Mayor’s Memorandum 2011-1, to require District government departments and agencies to take the following
steps to achieve the goal of creating a more transparent and open government:

b. Definitions.

  1. “Chief Data Officer” (“CDO”) means the Chief Technology Officer or a Chief Data Officer designated by the Chief Technology Officer.
  2.  “Data” means statistical, or factual, quantitative, or qualitative information that are regularly maintained or created by or on behalf of a District agency, and controlled by such agency in structured formats, including statistical or factual information about image files and geographic information system data.
  3. “Dataset” means a named collection of related records, with the collection containing data organized or formatted in a specific or prescribed way, often in tabular form.
  4. “Open Government Coordinator” means agency personnel designated by an agency head, in coordination with the Office of the Chief Technology Officer (“OCTO”) or the CDO as appropriate, to ensure that the information and data required to be published online is published and updated as required by this Order.
  5. “Protected data” means (i) any dataset or portion thereof to which an agency may deny access pursuant to the District of Columbia Freedom of Information Act, effective March 25, 1977 (D.C. Law 1-96; D.C. Official Code § 2-531 et seq.)(“FOIA”), or any other law or rule or regulation; (ii) any dataset that contains a significant amount of data to which an agency may deny access pursuant to FOIA or any other law or rule or regulation promulgated thereunder, if the removal of such protected data from the dataset would impose an undue financial or administrative burden on the agency; or (iii) any data which, if disclosed on the District of Columbia Data Catalog, could raise privacy, confidentiality or security concerns or jeopardize or have the potential to jeopardize public health, safety or welfare.

C. Scope.

a. The requirements of this Order shall be applied to any District of Columbia department, office, administrative unit, commission, board, advisory committee or other division of the District government (“agency”), including the records of third party agency contractors that create or acquire information, records, or data on behalf of a District agency.

b. Any agency that is not subject to the jurisdiction of the Mayor under the Freedom of Information Act or any other law is strongly encouraged to comply with the requirements of this Order.

SECTION 2: Transparency and Open Government Policy.

a. Publish Government Information Online. To increase accountability and transparency, promote informed public participation, and create economic development opportunities, each District agency shall expand access to information by making it proactively available online, and when practicable, in an open format that can be retrieved, downloaded, indexed, sorted, searched, and reused by commonly used Web search applications and commonly used software to facilitate access to and reuse of information. Examples of open format include HTML, XML, CSV, JSON, RDF or XHTML. The Freedom of Information Act creates a presumption in favor of openness and publication (to the extent permitted by law and subject to valid privacy, confidentiality, security, or other restrictions).

b. Open Government Web Portal: Within 30 days from the date of this Order, the Chief Technology Officer shall establish a common web portal that will serve as the source for District-wide and agency activities related to this Transparency and Open Data Directive. The Chief Technology Officer, in his or her discretion, may build upon an existing web portal, or may establish a new portal. Each agency shall be responsible for ensuring that the information required to be published online is accessible from the agency’s designated Open Government and FOIA webpage. The required information shall include, but is not limited to, where applicable:

  1. Means for the public to submit and track Freedom of Information Act requests online;
  2. The information required to be made public under this Directive and D.C. Official Code § 2-536, including links to:
    A. Employee salary information;
    B. Administrative staff manuals and instructions that affect the public;
    C. Final opinions and orders made in the adjudication of cases;
    D. Statements of policy, interpretations of policy, and rules adopted by the agency;
    E. Correspondence and other materials relating to agency regulatory, supervisory or enforcement responsibilities in which the rights of the public are determined;
    F. Information dealing with the receipt or expenditure of public or other funds;
    G. Budget information;
    H. Minutes of public meetings;
    I. Absentee real property owners and their agent’s names and mailing addresses;
    J. Pending and authorized building permits;
    K. Frequently requested public records; and
    L. An index to the records referred to in this section;
  3. Freedom of Information Act reports;
  4. An organizational chart or statement of the agency’s major components;
  5. Links to high-value datasets (as defined in section 3(a)(4);
  6. Public Meeting Notices and minutes required to be published under the Open Meetings Act and Freedom of Information Act; and
  7. A mechanism for the public to submit feedback on the agency’s Open Government Report or other agency actions.

c. Open Government Report. To institutionalize a culture of transparent and open government, accountability, and to expand opportunities for resident participation and collaboration, beginning October 1, 2014, and each year thereafter, each agency shall develop and publish an Open Government Report that will describe how the agency has or will enhance and develop transparency, public participation, and collaboration. Each agency shall include in its open government report a description of the information (including data) that will be made available to the public, formats in which information and data will be made available, a schedule for making the information available, the dates for which information and datasets will be updated, and contact information for agency Open Government Coordinators. The Open Government Report shall address the following topics, and be transmitted to the Mayor and Director of the Office of Open Government:

  1. Transparency: The Open Government Report shall reference statutes, regulations, policies, legislative records, budget information, geographic data, crime statistics, public health statistics, and other public records and data, and describe steps each agency has taken or will take to:A. Meet its legal information dissemination obligations under Freedom of Information Act and Open Meetings Act;
    B. Create more access to information and opportunities for public participation; and
    C. Conduct its work more openly and publish its information online, including a plan for how each board and commission subject to the Open Meetings Act will ensure that all of its meetings are, where practicable, webcast live on the Internet.
  2. Participation: To create more informed and effective policies, each agency shall enhance and expand opportunities for the public to participate throughout agency decision-making processes. The Open Government Report will include descriptions of or plans to provide:A. Online access to proposed rules and regulations;
    B. Online access to information and resources to keep the public properly informed (such as frequently asked questions, contact information of city officials’ and departments, and other supportive content);
    C. Opportunities for the public to comment through the Web on any proposed rule, ordinance, or other regulation;
    D. Methods of identifying stakeholders and other affected parties and inviting their participation;
    E. Proposed changes to internal management and administrative policies to improve participation;
    F. Links to appropriate websites where the public can engage in the District government’s existing participatory processes;
    G. Proposals for new feedback mechanisms, including innovative tools and practices that create new and more accessible methods for public participation; and
    H. A plan that provides a timetable for ensuring that all meetings of boardsand commissions that are subject to the Open Meetings Act are webcast live and archived on the Internet.
  3. Collaboration: The Open Government Report will describe steps the agency will take or has taken to enhance and expand its practices to further cooperation among departments, other governmental agencies, the public, and non-profit and private entities in fulfilling its obligations. The Report will include specific details about:A. Proposed changes to internal management and administrative policies to improve collaboration;
    B. Proposals to use technology platforms to improve collaboration among District employees and the public;
    C. Descriptions of and links to appropriate websites where the public can learn about existing collaboration efforts; and
    D. Innovative methods, such as prizes and competitions, to obtain ideas from and to increase collaboration with those in the private sector, non-profit, and academic communities.

SECTION 3: Open Data Policy.

a. Agency Requirements.

  1. Each agency shall, in collaboration with the Chief Data Officer and OCTO, make available through the online District of Columbia Data Catalog all appropriate datasets, associated extensible metadata, and associated documented agency business processes under the agency’s control. Each agency, in collaboration with OCTO, shall determine the frequency for updates to a dataset, and the mechanism to be utilized. To the extent possible, datasets shall be updated through an automated process to limit the additional burden on agency resources. The publication of an agency’s datasets shall exclude protected data.
  2. Datasets under paragraph (4) shall be made available in accordance with technical standards published by OCTO not later than November 1, 2014 that ensure that data is published in a format that is machine readable, and fully accessible to the broadest range of users, for varying purposes. Datasets shall be made available to the public on an open license basis. An open license on a dataset signifies there are no restrictions on copying, publishing, further distributing, modifying or using the data for a non-commercial or commercial purpose.
  3. For the purposes of identifying datasets for inclusion on the District of Columbia Data Catalog, each agency shall consider whether the information embodied in the dataset is (i) reliable and accurate; (ii) frequently the subject of a written request for public records of the type that a public body is required to make available for inspection or copying under FOIA; (iii) increases agency accountability, efficiency, responsiveness or delivery of services; (iv) improves public knowledge of the agency and its operations; (v) furthers the mission of the agency; or (vi) creates economic opportunity.
  4. Within 120 days of the date of this Order, the City Administrator and each Deputy Mayor shall, collaborating with their cluster agencies, and OCTO, identify at least 3 new high-value datasets to publish to the Data Catalog, in accordance with OCTO’s open data standards. The identified high-value datasets will not be currently available, or not available in an exportable format. For the purposes of this section, “high-value dataset” includes agency outcome data, agency caseload data, data reported to the federal government outcome data, agency caseload data, data reported to the federal government by the agency, agency data reported as part of the performance measurement process, and any data that is tracked by the agency that is not protected data.

b. Chief Data Officer.

  1. The Chief Technology Officer shall designate a Chief Data Officer (“CDO”) for the District of Columbia to coordinate implementation, compliance and expansion of the District’s Open Data Program, to facilitate the sharing of information between departments and agencies, and to coordinate initiatives to improve decision making and management through data analysis. The Chief improve decision making and management through data analysis. The Chief Data Officer shall report to the Chief Technology Officer.
  2. The Chief Data Officer shall:
    A. Identify points of contact, which may include agency open government coordinators within departments, on data related issues who will be responsible for leading intra-departmental open data initiatives;
    B. Emphasize the culture behind open data and the benefits to ensure that opportunities to increase efficiency through open data practices can be obtained from those with the most direct expertise;
    C. Work together with District agencies to develop a methodology and framework that supports the collection, or creation of data in a way that assists in downstream data processing and open data distribution activities;
    D. Identify and overcome challenges with agency proprietary business systems; create and/or leverage opportunities through procurement or other means to upgrade legacy systems to one of an open data architecture; and
    E. Function as a data ombudsman for the public, fielding public feedback and ensuring the policy is included into a long-term data strategy.

c. District of Columbia Open Data Catalog.

  1. A single web portal, or integrated set of websites, shall be established and maintained by or on behalf of the District of Columbia. The Chief Data maintained by or on behalf of the District of Columbia. The Chief Data Officer, in collaboration with OCTO, may build upon previous open data initiatives, or may establish a new portal for managing and delivering open data benefits to constituents.
  2. Any dataset made accessible on the District of Columbia Data Catalog shall use an open format that permits automated processing of such data in a form that can be retrieved via an open application programming interface (API), downloaded, indexed, searched and reused by commonly used web search applications and software; (ii) use appropriate technology to notify the public of updates to the data; and (iii) be accessible to external search capabilities.
  3. OCTO shall (i) post on the portal a list of all datasets available on such portal; and (ii) establish and maintain on the portal an online forum to solicit feedback from the public and to encourage public discussion on open data policies and dataset availability.

d. Open Data Legal Policy.

  1. The District of Columbia Data Catalog and all public data contained on such portal shall be subject to Terms of Use developed by OCTO. Such Terms of Use shall be posted by OCTO in a conspicuous place on the District ofColumbia Data Catalog.
  2. Public data made available on the District of Columbia Data Catalog shall be provided as a public service, on an “as is” basis. Although the District will strive to ensure that such public data are accurate, the District shall make no warranty, representation or guaranty of any type as to the content, accuracy, timeliness, completeness or fitness for any particular purpose or use of any public data provided on such portal; nor shall any such warranty be implied, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose. The District shall assume no liability for any other act identified in any disclaimer of liability or indemnification provision or any other provision set forth in the Terms of Use required under subsection (d)(1) of this section.
  3. The District shall reserve the right to discontinue availability of content on the District of Columbia Data Catalog at any time and for any reason. If a dataset is made accessible by an agency on the District of Columbia Data Catalog and such agency is notified or otherwise learns that any dataset or portion thereof posted on the Data Catalog is factually inaccurate or misleading or is protected data, the agency shall, as appropriate, promptly correct or remove, or cause to be corrected or removed, such data from the Data Catalog and shall so inform the Chief Data Officer.
  4. Nothing in this Order shall be deemed to prohibit OCTO or any agency or any third party that establishes or maintains the District of Columbia Data Catalog on behalf of the District from adopting or implementing measures necessary or appropriate to (1) ensure access to public datasets housed on the Data Catalog; (ii) protect the Data Catalog from unlawful use or from attempts to impair or damage the use of the portal; (iii) analyze the types of public data on the Data Catalog being used by the public in order to improve service delivery or for any other lawful purpose; (iv) terminate any and all display, distribution or other use of any or all of the public data provided on the Data Catalog for violation of any of the Terms of Use posted on the Data Catalog pursuant to subsection (d)(1) of this section; or (v) require a third party providing the District’s public data (or applications based on public data) to the public to explicitly identify the source and version of the public dataset, and describe any modifications made to the public dataset.
  5. Nothing in this Order shall be construed to create a private right of action to enforce any provision of this Order. Failure to comply with any provision of this Order shall not result in any liability to the District, including, but not limited to, OCTO or any agency or third party that establishes or maintains on behalf of the District the Open Data Services Portal required under this Order.

Section 4. Open Government Advisory Group.

a. The Mayor shall convene an Open Government Advisory Group to be chaired and convened by the Mayor’s designee, CDO, and the Director of the Office of Open Government within the Board of Ethics and Government Accountability.

b. The Open Government Advisory Group shall:

  1. Evaluate the District’s progress towards meeting the requirements of this Order and make specific recommendations for improvement; and
  2. Assist the Mayor and CDO in creating policy establishing specific criteria for agency identification of protected data in accordance with FOIA, maintenance of existing data, and the creation of data in open formats.

c. The CDO shall publish the evaluation and recommendations on the Open Government Web Portal or create an Open Government Dashboard that will provide the public with both graphic and narrative evaluation information.

Section 5: EFFECTIVE DATE:

This Order shall be effective immediately.

VINCENT C. GRAY
MAYOR

ATTEST:
CYNTHIA BR CIS-SMITH
SECRETARY OF THE DISTRICT OF COLUMBIA

After the order was published online, GovTrack.us founder Josh Tauberer issued a series of critical tweets and extended his thoughts into a blog post, holding that DC city government adopted the mistakes made by the White House:

There is a strong American tradition — or at least a core American value — that the government does not get in the way of the dissemination of ideas. We don’t always live up to that ideal, but we strive for it. Access to information about the government that comes with restrictions on what we can say when we use it (e.g. attribution & explanation), a waiver of rights or a commitment to indemnify, etc. are all an anathema to accountability and transparency and respect for the public.

District of Columbia to experiment with collaborative lawmaking online

Posted on by

1

Residents of the District of Columbia now have a new way to comment on proposed legislation before the City Council, MadisonDC. Today, David Grosso, a DC Councilman-at-Large, introduced the new initiative to collaboratively draft laws online in a release and video on YouTube.

“As we encourage more public engagement in the legislative process, I hope D.C. residents will take a moment to log onto the Madison project,” said Councilmember Grosso. “I look forward to seeing the public input on my proposed bills.”

MadisonDC has its roots in the first Congressional hackathon, back in 2011. The event spawned a beta version of the Madison Project, an online platform to where lawmakers could crowdsource legislative markup. It was deployed first by the office of Representative Darrell Issa, crowdsourcing comments on several bills. The code was subsequently open sourced and now has been deployed by the OpenGov Foundation as a way to publish municipal codes online, along with other uses.

“We are excited to support Councilmember Grosso’s unprecedented efforts to welcome residents – and their ideas – directly into the local lawmaking process,” said Seamus Kraft, co-founder & executive director of The OpenGov Foundation, on the nonprofit organization’s blog. “But what really matters is that we’re going to produce better City Council bills, with fewer frustrations and unintended consequences. These three bills are only a start. The ultimate goal of MadisonDC is transforming D.C.’s entire policymaking machine for the Internet Age, creating an end-to-end, on-demand collaboration ecosystem for both citizens and city officials. The possibilities are limitless.”

The first three bills on MadisonDC are the D.C. Urban Farming and Food Security Act of 2014, the Marijuana Legalization and Regulation Act of 2013, and the Open Primary Elections Amendment Act of 2014.

The DC Open Government Office at the city’s Board of Ethics and Government Accountability, commended the effort with a tweet:

Councilman Grosso further engaged the public on Twitter this afternoon, inviting public comment on his proposed legislation.

This post has been updated to include more statements and social media updates.

Code for DC launches OurDCSchools.org, an open government platform for proposed school policy

Posted on by

0

ourdcschools

Parents, students and other members of the public can now easily see the effect of a href=”http://www.washingtonpost.com/local/education/dc-releases-proposed-school-boundaries-and-far-reaching-student-assignment-policies/2014/04/05/368521e0-bc46-11e3-96ae-f2c36d2b1245_story.html”>new proposals for elementary school boundaries and far-reaching student assignment policies in the District of Columbia using a civic app called Our DC Schools.
The new website, built by volunteers at from Code for DC, a local open government group, makes it easier for the public to understand how important changes to the boundaries of DC school districts would affect a given address, rate the assignment policies proposed by the DC government, and forward that feedback to the Deputy Mayor for Education.

According to Code for DC, their team will published all responses collected, after the street addresses are excluded, on OpenDataDC, “a public catalog of civic data built by and for the people of Washington.”  The group will continue to collect responses until mid-May 2014, sharing them with the Boundary Review Advisory Committee, the relevant government entity entrusted with working on the proposals. You can find more a bit more context about the app and the issues at WAMU.org.

Our DC Schools builds upon the data behind the Washington Post’s interactive news app, which also enables people to perform a similar geographic search, and then goes one step further than the newspaper, giving people tools to rate proposed changes and send it on to local government.

 

code-for-dc-logoAccording to Code for DC, the idea for the civic app came from Chris Given, when he saw how much data was available regarding the issue

“I attended a public working group meeting at Dunbar High School and while I was impressed by the dedication of the Deputy Mayor for Education and DC Public Schools staff, I was just bowled over by the scale of the challenge of getting meaningful feedback from everyone these policies affect,” said Given, in a statement. “I wanted to create an on-ramp for engaging with a really complex issue.”

In personalizing and visualizing the school district changes, unpacking these proposals for assignment and connecting feedback concerned citizens affected by the proposals to policy makers at local government, these volunteers are demonstrating how open government data and the World Wide Web can inform residents and stimulate citizen engagement in matters of great public interest.

Notably, the civic app came to life through a collaboration between Code for DC and the office of the district’s Deputy Mayor for Education (DME). It’s an effort to use modern technology to better engage the people of DC in their government.

“The Our Schools DC app is an example of what can be achieved when government collaborates with citizens to find solutions to common problems. In addition to providing valuable information, it’s a means of public engagement that will help city leaders better meet the educational needs of communities throughout the district,” said Traci L. Hughes, Director of the District of Columbia Office of Open Government, in a statement.

 

A tale of 42 tweets: Highlights from my first Social Media Week in DC

Posted on by

0

Last week was “Social Media Week” here in DC. The week featured speakers, panels, workshops, events, and parties all across the District, celebrating tech and social media in the nation’s Capital, including a special edition of the DC Tech Meetup. I moderated four panels, participated in a fifth and attended what I could otherwise. I found the occasion to be a great way to meet new people around the District. Following is a storify of some of my personal highlights, as told in tweets and photographs. This is by no means representative of everyone’s experiences, which are as varied as the attendees. It’s solely what I saw and what lingered from the social media week that was.

http://storify.com/digiphile/selected-highlights-of-my-2012-social-media-week-i.js[View the story “Selected Highlights of my 2012 Social Media Week in DC” on Storify]

International Open Data Hackathon on December 3, 2011

Posted on by

0

It’s time to think different about hacking.

Building upon the success of an international civic hackathons around the world in 2010, there will be Random Hacks of Kindness and International Open Data Day hackathons on six different continents on December 3rd, 2011. If you’re interested in volunteering for a different kind of public service, check out the wiki to see if there’s an event near you.

The International Open Data Hackathon in DC will be held at the Martin Luther King Jr. Memorial Library. The organizers encourage attendees to “bring ideas, your laptop, and help create solutions to make data more open and make better use of open data.” The list of attendees is already filling up with interesting people, including members of Washington’s open government and technology communities. The DC open data hackathon is hosted by Wikimedia DC and sponsored by civic startup PopVox.

The 411 on Digital Capitol Week on 1.1.11: 11.4.11 through 11.11.2011

Posted on by

0

Digital Capital Week is coming back to the United States Capital on November 4th, 2011. In a livestream today, the organizers of the inaugural 2010 event announced the data and opened the gates for DC Week registration and ideas for … Continue reading →

Social media, local government and elections: reflections on COGEL and @DCBOEE

Posted on by

0

This week, I was proud to be one of two speakers for a session on social media and government at the Council on Governmental Ethics Laws (COGEL) conference in Washington, D.C. I delivered an adapted version of the talk on social media and government I gave the Social Security Administration’s Open Government Awareness Day earlier this year, focusing on the elements that would be of greatest interest to a group of lawyers, regulators and academics. The presentation is embedded below:

Social Media and Government 2.0http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=socialmedia-govt-ssa-abh-100714112613-phpapp01&stripped_title=social-media-and-government&userName=digiphile

The speaker that followed me, however, was able to share a fascinating view of what social media looks like from inside of government, specifically in the District of Columbia. Alysoun McLaughlin, the public affairs manager for the District of Columbia Board of Elections and Ethics. Here’s her bio, from the COGEL session description:

She joined the District last year, just in time to implement a long list of reforms for the 2010 election including new voting equipment, early voting and same-day registration. Prior to becoming an election official, she was a project manager for Election Initiatives at the Pew Center on the States. She previously spent a decade as a Washington lobbyist, focusing on election issues for the National Conference of State Legislatures and the National Association of Counties. She is here today to share her experience with social media during the 2010 election.

And share she did. Over the course of half an hour, she talked about Facebook, Twitter, local media, citizen engagement and much more. I captured most of her presentation on my iPhone (sorry about the unsteady hand) and have embedded her presentation, “To Tweet or not to Tweet: Engaging the Public through Social Media,” below.

To Tweet or Not To Tweet DCBOEEhttp://static.slidesharecdn.com/swf/ssplayer2.swf?doc=totweetdcboeerev-101208130253-phpapp02&stripped_title=to-tweet-or-not-to-tweet-dcboee&userName=alysoun

View more presentations from alysoun.

If you want an excellent, practical perspective of the local government side of social media, these are worth watching. A couple of key takeaways from her presentation:

  • How can governments get insights from Twitter without using it? “Just type in the name of your agency and see what they’re saying.”
  • On D.C. elections: “We know there are going to be lines. Come to the website to see what they are.”
  • Don’t trust this to an intern. You “need someone skilled in crisis communications.”
  • “The days that I’m heavy on Twitter are the days my phone rings less.”
  • Viral tweets can raise awareness: “…and we just confirmed that a voter used a write-in stamp. on a touch screen.”

Part 1: Introductions

Part 2: Reflections on Twitter and Facebook

Part 3: Twitter and the 2010 DC Election

Part 4: Who follows @DCBOEE

Part 5: Listening and using social media in government

Washington, D.C. publishes its first digital divide strategy

Posted on by

2

The digital divide in D.C. is an issue that has been receiving increased sunlight under the District’s chief technology officer, Bryan Sivak. As the Kojo Nnamdi Show episode on the D.C. digital divide reported, “a 2009 study by the OCTO found that the digital divide runs very deep in the city – 90% of residents in Northwest D.C. have high-speed internet access in their homes, but in Southeast, that figure falls to just 36% – 40%.”

Earlier this year, Washington became the recipient of stimulus funding for a digital divide initiative. This summer, the city turned on free wifi in many neighborhoods, which can be viewed at DC.wifi.gov. Today, Sivak announced D.C.’s first digital divide strategy:
.bbpBox12514372882534400 {background:url(http://s.twimg.com/a/1291760612/images/themes/theme1/bg.png) #C0DEED;padding:20px;} p.bbpTweet{background:#fff;padding:10px 12px 10px 12px;margin:0;min-height:48px;color:#000;font-size:18px !important;line-height:22px;-moz-border-radius:5px;-webkit-border-radius:5px} p.bbpTweet span.metadata{display:block;width:100%;clear:both;margin-top:8px;padding-top:12px;height:40px;border-top:1px solid #fff;border-top:1px solid #e6e6e6} p.bbpTweet span.metadata span.author{line-height:19px} p.bbpTweet span.metadata span.author img{float:left;margin:0 7px 0 0px;width:38px;height:38px} p.bbpTweet a:hover{text-decoration:underline}p.bbpTweet span.timestamp{font-size:12px;display:block}

Proud to announce the release of DC’s first ever strategic plan for addressing the digital divide: http://octo.dc.gov/octostrategyless than a minute ago via Chromed BirdBryan Sivak
BryanSivak

It’s embedded below in the post. Interestingly, the digital divide strategy announcement at the Office of the Chief Technology Officer of D.C. indicated that it would be a “living document,” much like the Web itself:

OCTO is pleased to release a public draft of the District of Columbia’s first ever strategic plan to address the digital divide. This is intended to be a living document, updated quarterly or bi-annually as conditions warrant, and will reflect the current high-level vision of the District Government as it relates to tackling this important issue. Feedback is welcome so please feel free to share your thoughts and help us bridge this gap.

Digital Divide Strategy http://d1.scribdassets.com/ScribdViewer.swf?document_id=44785273&access_key=key-1zhdaz8pu43c1e8pmwzj&page=1&viewMode=list

For a feel for the thinking of the DC CTO on this count, watch Sivak’s closing statement from the District of Columbia’s first-ever “Community Broadband Summit” (DC-CBS) is embedded below. The summit was a public forum designed to address the city’s digital divide.

Bryan Sivak – Closing Remarks from DCNET Multimedia on Vimeo.

It’s not clear whether Sivak will stay on under incoming Mayor-Elect Vincent Gray’s administration. If not, here’s hoping his replacement works with the D.C. tech community to connect more citizens to the Internet. Online access has become a vital link for information, services, access to jobs, education and communication with family, friends, teachers and coworkers in the 21st century. The District should be commended for continuing to working to bridge it.

What do you think of the strategy? Leave your thoughts in the comments.

Data BBQ features District tech entrepreneurs, passion and tasty open data.

Posted on by

5

“Get off your index and build your Rolodex,” read the invite to last night’s Data BBQ in Washington, D.C.

And last night, that’s exactly what over a hundred people from around D.C.’s growing tech scene did, spilling out of the revamped officers of Insomniac Design in Bladgen Alley, near Mount Vernon Square.

The crowd was leavened with many attendees from the ongoing mHealth Summit 2010, manyof DC’s open data geeks and supporters and. Expert Labs’ Gina Trapani and Waxy.org’s Andy Baio came by from the FCC’s Open Developer Day to mix and mingle too. The highlight of the Data BBQ was the lightning talks, where attendees pitched projects, ideas, jobs or even spare rooms to the crowd. The talks are embedded below:

Many of the mHealth conferees no doubt know about the Health 2.0 Developer Challenge from the Department of Health and Human Services, where health data is being mashed up into new applications.

And, judging by the show of hands, many of the Data BBQ’ers had also heard about the World Bank’s Global Apps for Development Competition, which is looking to the development and practitioner communities to create innovative apps using World Bank data.

What might have been new to a few, at least, was the upcoming Apps for Army competition for the public, where the successful apps competition that Peter Corbett and iStrategy Labs helped the Army run will be rebooted for wider participation.