diff --git a/usecasesv1.html b/usecasesv1.html
index 7d4f542..4d47823 100644
--- a/usecasesv1.html
+++ b/usecasesv1.html
@@ -583,40 +583,97 @@ Dados.gov.br
(Contributed by Yasodara)
URL: http://dados.gov.br/
Dados.gov.br is the open data portal of Brazil's Federal Government.
- The site was built by a community network pulled together by three
+ The site was
+
+ built by a community network pulled together by three
technicians from the Ministry of Planning. They managed the group from
- INDA or
- "National Infrastructure for Open Data." CKAN was chosen because it is
- free software and presents independent solutions for the placement of
+ INDA or
+ "National Infrastructure for Open Data."
+ CKAN was chosen because it is free
+ software and presents independent solutions for the placement of
a data catalog of the Federal Government provided on the internet.
Elements:
- - Domains: federal budget, addresses, Infrastructure
- information, e-gov tools usage, social data, geographic information,
- political information, Transport information.
+ - Domains: federal budget, expenditure, procurement,
+ contracts, agreements, consumer protection, infrastructure
+ information, government property, e-gov tools usage, social data,
+ geographic information, political information, financial data,
+ performance indicators, environment data, transport information,
+ and others.
- Obligation/motivation: Data that must be provided to
the public under a legal obligation, the called LAI or Brazilian
- Information Access Act, edited in 2012.
- - Usage: Data that is the basis for services to the
- public; Data that has commercial reuse potential.
- - Quality: Authoritative, clean data, vetted and
- guaranteed.
+ Information Access Act, enacted in 2011, in effect since 2012.
+ - Usage: Enable government entities to publish data
+ in one place where citizens can find data they need; Data that is
+ the basis for services to the public; Data that has commercial
+ reuse potential.
+ - Quality: Much of the data is realized properly,
+ with complete or near complete metadata. However, some data
+ imported from National Infrastructure of Spatial Data, an earlier
+ initiative for geospatial data, lack proper metadata or have
+ unavailable resources.
- Lineage/Derivation: Data came from various
publishers. As a catalog, the site has faced several challenges, one
of them was to integrate the various technologies and formulas used
by publishers to provide datasets in the portal.
- - Type/format: Tabular data, text data.
+ - Type/format: At the time of writing: HTML (925),
+ CSV (889), ESRI Shapefile (740), GeoJSON (740), KML (740),
+ XML (279), JSON (271), XLS (15) xlsx (7), ods (4),
+ RDF-based formats (2)
- Rate of change: There is fixed data and data with
high rate of change.
Challenges:
- Data integration (lack of vocabularies).
- - Collaborative construction of the portal: managing online sprints
- and balancing public expectatives.
+ - Collaborative construction of the portal: managing online
+ sprints, constant influx and absenteeism of volunteers
+ and balancing public expectations.
- Licensing the data of the portal. Most of data that is in the
portal does not have a special licence so there are types of license
applied to different datasets.
+ - Promoting organizational change (as organizational culture tends
+ to resist open data)
+ - Getting the word out about open data to build understanding and
+ engagement both inside government and in civil society, as the
+ concept of open data is not yet wide spread in Brazil even after
+ years of implementation on many different levels of government
+ - Improving the legal framework for making open data ubiquitous
+ - handling (collaboration, standardization, agreements, etc.) of
+ open data policies across different levels (national, state,
+ municipal) and powers/branches (executive, legislative, judicial)
+ which are constitutionally independent
+ - Securing proper resources (human, funding), especially under a
+ government financial crisis, for open data activities both at central
+ policy level and for projects within organizations
+ - Getting the government organizations that still resist to work
+ with open data to start releasing/cataloguing/documenting open data
+ - Improving the quality of already released open data
+ - Keeping already released open data up-to-date
+ - Improving the quality and accuracy of metadata and documentation
+ about already released open data
+ - Breaking down resistance set up by public IT companies that have
+ a business model of charging for access to data
+ - Getting private businesses to harness the potential of open data
+ to reach new markets and build new or improve upon existing business
+ models
+ - Improving data literacy skills among journalists and the general
+ population
+ - Fostering further usage of already released open data by civil
+ society
+ - Educating prospective users of open data on often esoteric
+ subjects of government activities that are released as open data
+ (such as budget)
+ - Rresearching/developing/applying visualization tools and create
+ data stories to make open data easier to comprehend for lay people
+ - Fostering new research, while also helping spread the word about
+ and applying existing academic research about open data
+ - Experimenting with and developing methodologies for harnessing
+ the benefits of civil society participation in digital government
+ policy design and implementation (including prioritising datasets,
+ building plans, etc.)
+ - Getting a feedback loop to happen between data publishers and
+ data users, and use this to improve the data
Requires: R-AccessLevel,
R-DataLifecyclePrivacy, R-DataLifecycleStage,