Takeaways from the City's Draft Open-Data Policy - Voice of San Diego

Government

Takeaways from the City's Draft Open-Data Policy

The draft has a few visible flaws, but could go a long way toward making government data more accessible.

Councilman Mark Kersey showed off the fruits of a bipartisan push for more open data citywide Wednesday: a draft policy that, if approved by the City Council, would go into effect on Jan. 1, 2014.

Here are the five big takeaways:

The city’s first chief data officer would help agencies put the policy into practice.

The policy would enable the mayor to appoint a chief data officer, who would be in charge of “all facets” of the policy.

The policy would make this person responsible for developing a technical manual for agencies to follow when trying to put their information into machine-readable form.

Machine-readable form means that you would be able to view and analyze the information with a variety of computer software programs, many of which are free.

The chief data officer would also help agencies identify what kinds of information they could release easily and what kinds would take more time to prepare.

You would be able to download data from an online library linked to the city’s main website.

Not all data would be open.

Public-records laws generally include a list of circumstances that agencies can cite when they don’t think they should release information.

Under this policy, you would not be able to access data if an agency invoked one of seven exemptions. These exemptions fall into a few broad categories:

• Other laws would prohibit the city from releasing the data

• The information is sensitive, confidential or related to ongoing legal matters

• The information is considered purely internal and, in theory, would have no value to the public

One exemption sticks out: Data that exists “solely on an agency-owned personal computing device” or “on a portion of a network that has been exclusively assigned to a single agency employee” would not be considered public.

This provision could potentially be abused if an official decided to keep information that should be public on city-issued cell phones or tablet computers.

On the other hand, it would also allow officials to protect information that should be confidential.

The city will ease into the process.

Agencies would start by taking information that they’ve already released publicly and putting it into a form that is easier to analyze. From there, they would move to information that should be public but hasn’t been released yet.

This will take a while.

The deadline for transforming all public information into data would be Dec. 31, 2018.

The chief data officer would post a data-release schedule online.

Accuracy is not guaranteed.

While the chief data officer would urge agencies to put complete and accurate data online, the official would have no power to punish agencies for not complying with the policy.

This is perhaps the policy’s biggest flaw.

Nothing would prevent the chief data officer from telling the public about gaps and problems he or she sees in the data. But if there are no penalties for failing to comply with the policy, then agencies may release data in a way that favors officials’ careers over the public interest.

Input is welcome.

Kersey has posted the draft policy online, and his office is accepting comments from the public before the policy goes up for a Rules Committee vote in late October or early November.

Much of the policy is technical — and it has to be — but this is your chance to tell the city what information you would like to access easily in the future.

Show Comments
Loading

We’re striving for the best possible discussion and may delete comments using our editorial judgment. All comments containing links will be reviewed by VOSD staff before they are published.
Read our full comment policy.
For longer comments, consider submitting an op-ed to Voice of San Diego.
Read the guidelines here.

We have recently updated our commenting system. If you are unable to submit a comment, please clear the cache and cookies in your browser, or use a private browsing window. Click here for detailed instructions.