Move missing files
This commit is contained in:
Luccas Mateus
@@ -0,0 +1,28 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: 'Adding data: overview'
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
One of the most valuable contributions you can make to the OpenSpending project is to add a new dataset. This section of the guide walks you through the process of adding new data.
|
||||
|
||||
A typical workflow for importing a dataset into OpenSpending involves the following steps:
|
||||
|
||||
* Gather machine-readable data from a trustworthy source.
|
||||
|
||||
* Convert the data to a CSV file in the format expected by OpenSpending, cleaning it to remove inconsistencies and errors.
|
||||
|
||||
* Publish the data to the web.
|
||||
|
||||
* Create a dataset add the published data as a new data source.
|
||||
|
||||
* Model the dataset to assign a logical role to each column in the source table.
|
||||
|
||||
* Load the data, or refine the data based on the feedback given by the platform about the data's consistency.
|
||||
|
||||
Each of these steps will be explained in detail in the following sections.
|
||||
|
||||
**Next**: [Gathering data](../gathering-data/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Create a Visualization
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
The OpenSpending platform makes it easy to create and embed visualizations of datasets. Three types of visualizations are supported: BubbleTree, TreeMap, and Table of Aggregates.
|
||||
All OpenSpending visualizations allow you to choose a series of dimensions along which to aggregate your data, drilling down into finer and finer detail. Each visualization is created the same way: by choosing the dimensions to aggregate and the order in which to drill down.
|
||||
To start creating a visualization, go to a dataset's home page and select **Create a visualization** from the *Visualizations* menu.
|
||||
|
||||
#### BubbleTree
|
||||
|
||||
The BubbleTree is an interactive visualization that presents aggregated spending data as a circle of bubbles. Each bubble represents an aggregated (sub-)total. The central bubble represents an aggregated sum, and its surrounding bubbles represent the other sums that it is made of. By clicking on any bubble, the user is shown how the sum breaks down into further sub-totals.
|
||||
|
||||
To create a BubbleTree, choose the dimensions to aggregate and the order in which to aggregate them. Choose the primary dimension from the *Level* drop-down menu. You will see the aggregated total of that dimension as the central bubble, with values of the dimension surrounding it with their own totals.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_14.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_14.png" alt="image_14" width="478" height="553" class="alignnone size-full wp-image-598" /></a>
|
||||
|
||||
To add a second level, click **Add a level** and choose a new dimension. Users will now be able to click on bubbles to "drill down" and see how the values of the first level break down into values on the second level.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_15.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_15.png" alt="image_15" width="473" height="564" class="alignnone size-full wp-image-599" /></a>
|
||||
|
||||
#### TreeMap
|
||||
|
||||
The TreeMap presents aggregated spending data as an interactive rectangle of coloured tiles. Each tile represents aggregated values for a particular dimension of the data. Clicking on the tile "zooms in" to show how it breaks down along further aggregated dimensions.
|
||||
|
||||
To create a TreeMap, simply choose the dimensions to aggregate and their order. Select the primary dimension from the *Tile* menu. You will see a TreeMap showing how the total spending breaks down across that dimension.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_16.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_16.png" alt="image_16" width="475" height="543" class="alignnone size-full wp-image-600" /></a>
|
||||
|
||||
The visualization has no useful interactivity yet. Adding further tile levels allows you to drill down to see how aggregated values decompose into smaller aggregates. To add a second level of tiles, click **Add a level** and choose a new dimension. Users can now click tiles to see how their totals break down.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_17.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_17.png" alt="image_17" width="475" height="561" class="alignnone size-full wp-image-601" /></a>
|
||||
|
||||
#### Table of Aggregates
|
||||
|
||||
The Table of Aggregates is a simple tabular view of a dataset that aggregates totals across chosen dimensions. A Table of Aggregates is specified by choosing dimensions for its columns.
|
||||
|
||||
Choosing a primary dimension via the *Columns* menu will display the data in tabular form, with aggregated amounts and percentages of the overall total. By default, the rows will be sorted by percentage.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_18-e1375889043439.png"><img src="http://blog.openspending.org/files/2013/08/image_18-e1375889043439.png" alt="image_18" width="600" height="458" class="alignnone size-full wp-image-602" /></a>
|
||||
|
||||
Adding another column by clicking **Add a level** will break down each subtotal in the first column by the aggregated sums of the new column. Note that this generally changes the percentage values and thus rearranges rows.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_19-e1375889063736.png"><img src="http://blog.openspending.org/files/2013/08/image_19-e1375889063736.png" alt="image_19" width="600" height="530" class="alignnone size-full wp-image-603" /></a>
|
||||
|
||||
**Next**: [Embed a visualisation into your website](../embed-viz)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Creating a dataset on OpenSpending
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
To begin sharing data on the OpenSpending platform, register on OpenSpending.org and create a new OpenSpending dataset. To create a dataset, simply fill in some metadata that characterizes your data and provide the URL where your data is hosted.
|
||||
|
||||
#### Creating a new dataset
|
||||
|
||||
Log in to OpenSpending.org with your user information, or register if you have not yet done so. You will arrive at the Dashboard, where you will see a blue button labeled **Import a Dataset**. Click this to begin creating a new OpenSpending dataset.
|
||||
|
||||
The next screen prompts you to provide metadata that characterizes your data. This includes the following fields:
|
||||
|
||||
* *Title*: a descriptive and meaningful name for the dataset. Can be any string.
|
||||
|
||||
* *Identifier*: a shorter title, used as part of the dataset's URL. Can only contain alphanumeric characters, dashes, and underscores – no whitespace or punctuation.
|
||||
|
||||
* *Category*: one of "Budget", "Expenditure", and "Other". See the guide section on types of financial data for details on these categories.
|
||||
|
||||
* *Currency*: the currency in which the spending described by the dataset takes place.
|
||||
|
||||
* *Countries*: a list of countries referenced in the dataset. Choice of countries is constrained by a list of valid countries.
|
||||
|
||||
* *Languages*: a list of languages used in the dataset. Choice of languages is constrained by a list of valid languages.
|
||||
|
||||
* *Description*: a characterization of the dataset in simple prose. Can be any string.
|
||||
|
||||
Fill in all of these fields. Be sure to include a Description which explains the origin of your dataset and acknowledges any changes you have introduced (for example, any cleaning you have done).
|
||||
|
||||
Once all metadata has been filled in, press **Next Step** to proceed.
|
||||
|
||||
#### Adding a new data source
|
||||
|
||||
Clicking through to the next step creates your new OpenSpending dataset and takes you to its *Manage* page. The Manage page is used to add data sources. It is also used to provide schematic information that allows OpenSpending to interpret the data, a process called "modelling" that will be covered in the next section of the guide.
|
||||
|
||||
To add a data source to a dataset, click **Add a source**. A prompt will appear, asking you for a URL. Provide the URL of the CSV file you published on the web in the previous section of the guide and click **Create**. You will see a blue text box indicating that OpenSpending is thinking about your data.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_2-e1375888360807.png"><img src="http://blog.openspending.org/files/2013/08/image_2-e1375888360807.png" alt="image_2" width="600" height="228" class="alignnone size-full wp-image-582" /></a>
|
||||
|
||||
Click **Refresh** or simply use your browser's refresh button. If OpenSpending succeeded at analyzing your data, you should see a green text box telling you that your data is ready. You should also see a correct list of your CSV's columns.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_3-e1375888381459.png"><img src="http://blog.openspending.org/files/2013/08/image_3-e1375888381459.png" alt="image_3" width="600" height="408" class="alignnone size-full wp-image-583" /></a>
|
||||
|
||||
Note that if you incorrectly provide OpenSpending with an HTML file instead of a valid CSV file, it will not complain but will simply try to analyze the HTML as if it were a CSV. The result looks like the following.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_4-e1375888407751.png"><img src="http://blog.openspending.org/files/2013/08/image_4-e1375888407751.png" alt="image_4" width="600" height="234" class="alignnone size-full wp-image-584" /></a>
|
||||
|
||||
If you added a bad data source, don't worry. You do not have to use the source in your final dataset: OpenSpending requires you to do more work on a data source before it can be published. Simply add a new, correct source and forget about the bad one.
|
||||
|
||||
**Next**: [Modelling your data in OpenSpending](../modelling-data/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: How does OpenSpending represent data?
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
OpenSpending maintains a collection of datasets, each of which represents a set of data from a separate source. Inside each dataset, individual transactions are represented by a set of entries. Each dataset has its own model that maps the structure of the data. The model encodes the properties of each dataset entry in terms of *dimensions*.
|
||||
|
||||
#### Datasets
|
||||
|
||||
The basic unit in the OpenSpending system is the dataset. Financial transactions sharing a common theme (e.g. a particular city’s spending, a budget for a particular year) are grouped together and stored as a dataset. A dataset is a collection of "entries", and each entry represents a single transaction associated with a quantity of money and a time.
|
||||
|
||||
Datasets also include metadata to characterize their contents. The metadata includes a description of the dataset, information about the source of the data, and other such information which helps users find the dataset and interpret its contents.
|
||||
|
||||
#### Models
|
||||
|
||||
The structure of each dataset is completely up to the creator of the dataset. This structure is created by specifying a *model*, which provides the dimensions along which entries can differ from one another.
|
||||
|
||||
A model consists of a set of *dimensions*. A dimension is a property that potentially differentiates one entry from another. If you imagine a dataset as a spreadsheet, each dimension can be thought of as a column. Dimensions can have more structure than an ordinary spreadsheet column, however.
|
||||
|
||||
Dimensions come in several types. The most important is the *measure* type. Measures are dimensions which can contain a single numerical value. Another important dimension type is the *time* type, which represent dates and times. Every data needs at least one each of measure and time dimensions, representing respectively the amount of money represented by the transaction and the time when it took place.
|
||||
|
||||
The remaining dimension types are used to represent other properties that entries might have, e.g. transaction numbers, labels from a classification scheme, or the names of individuals or companies involved. Such dimensions include *attributes*, which can hold a single value, and *compound dimensions*, which can hold a nested set of values. Compound dimensions are useful when a property includes several sub-properties which could each be used to aggregate the data.
|
||||
|
||||
**Next**: [Adding data: overview](../adding-data-overview/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Embed a visualization into your website
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
You can easily embed any of the visualizations created on OpenSpending on your own website. This means you can have the full interactive displays on your site.
|
||||
|
||||
Let's say you have chosen a visualization on the OpenSpending platform. Notice there's an **Embed** button at the bottom right of the webpage. Click this button and you'll be presented with the code to embed the visualization on your website and some options for the size (in pixels) of the interactive. The rest is just cutting and pasting this code into your site. If you are unsure how to paste the code correctly, contact your site administrator.
|
||||
|
||||
The reason it's possible to embed code comes down to *widgets*. In very simplified terms, a widget is a piece of code you can add into your webpage, and it pulls data – in this case, from the OpenSpending database – so you don't need to store datasets yourself.
|
||||
|
||||
**Back to top**: [OpenSpending Guide](../)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: What types of financial data can go into OpenSpending?
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
OpenSpending is very flexible in the types of financial data it supports. Although the OpenSpending project has a strong focus on government finance, this is not a technical constraint. OpenSpending supports any dataset consisting of a set of transactions, each associated with a quantity of money and a time.
|
||||
|
||||
Most of the data currently hosted on OpenSpending can be categorized as either transactional or budgetary data. The main difference between these is their level of granularity. Transactional data tracks individual transactions, whereas budgetary data aggregates transactions into categories.
|
||||
|
||||
#### Transactional spending data
|
||||
|
||||
Transactional data, or simply "spending data", tracks individual financial transactions. Each payment from one entity to another on a given date and for a specific purpose (e.g. a project or service) is listed individually. Transactional spending data includes various types of records, including information on government grants, commitments, and actual expenditure.
|
||||
|
||||
Aggregate information (e.g. subtotals) should not be included in transactional data. Data that has been partially or completely aggregated calls for a different mode of analysis and should be treated as budgetary data rather than transactional data. This does not mean, however, that several "physical" payments which amount to a single “logical” transaction cannot be represented by a single transaction in transactional data.
|
||||
|
||||
Transactional data on OpenSpending includes:
|
||||
|
||||
* [DC Vendors and Contractors](http://openspending.org/dc-vendors-contractors)
|
||||
|
||||
* [Austrian Development Agency](http://openspending.org/ada/)
|
||||
|
||||
Another related type of data deals with the public procurement procedures. Public Procurement data is data about public tenders: what was tendered, for how much, and who won the tender. It can be seen as a subset of transactional data.
|
||||
|
||||
Procurement data on OpenSpending includes:
|
||||
|
||||
* [Marchés publics au Sénégal](http://openspending.org/marches-publics-senegal/views/liste-des-attributaires)
|
||||
|
||||
* [Marchés publics France 2011](http://openspending.org/marches-publics-france-2011)
|
||||
|
||||
#### Budgetary data
|
||||
|
||||
In budgetary data, expenditures and incomes are aggregated into categories. The goal of this aggregation is to aid the reader in understanding the budget, which is typically a policy document that is used to provide readers with an overview of the government’s most important financial choices. Allocation is typically structured by a classification scheme rather than by the actual recipients of funds.
|
||||
|
||||
Budgetary data often jointly presents data on past outcomes and appropriations for a future period. In such a presentation, amounts spent in previous years on a particular sector are used to inform how much should be allocated for the coming budgeting period. Budget information is often based on aggregated data and statistical estimates.
|
||||
|
||||
Different regions make different types of budgetary information available, including: Pre-Budget Statements; Executive Budget Proposals; Enacted Budgets; and Citizen's Budgets (simplified versions of the budget for the benefit of citizens).
|
||||
|
||||
Budgetary data on OpenSpending includes:
|
||||
|
||||
* [Berlin Budget](http://openspending.org/berlin_de)
|
||||
|
||||
* [Seville Spending Budget](http://openspending.org/seville-budget)
|
||||
|
||||
**Next**: [How does OpenSpending represent data?](../data-model/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Formatting data
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
OpenSpending expects all data to be in a simple format.
|
||||
|
||||
#### CSV
|
||||
|
||||
OpenSpending accepts data in a single file format, the Comma-Separated Values (CSV) file. A CSV is a plain text file that represents data as a table, which is similar to a spreadsheet. In a table, each data point is represented by a row, and each data point's properties are represented by a column. CSV files encode tables by giving each row a line in the text file and by separating columns with commas.
|
||||
|
||||
CSVs accepted by OpenSpending do not save space by removing redundant values. If your spreadsheet omits any repeated values, those omitted values must be filled in before OpenSpending can use your data. OpenSpending-ready CSVs are also *rectangular*, meaning that they have exactly the same number of columns in each row.
|
||||
|
||||
#### The OpenSpending format
|
||||
|
||||
CSVs for OpenSpending must have the following properties.
|
||||
|
||||
1. One header row. The first row of the CSV file should contain the names of the columns, separated by commas. All other rows are treated as data rows.
|
||||
|
||||
2. At least three columns. The bare minimum of columns are an amount, a date (which could be just a year), and a spender or a recipient (which could just be the name of an account).
|
||||
|
||||
3. Consistent columns. Each column must consistently represent a single type of value for all rows. (There can be no subheader rows, for example.)
|
||||
|
||||
4. Rows are single data points. Rows should contain *only one* transaction or one budget line. Each row must represent a maximum of one time period.
|
||||
|
||||
5. No blank rows or cells. Each row should be completely filled in. Some spreadsheets leave redundant data cells blank or have other ways of saving space, but OpenSpending requires each row to be complete on its own.
|
||||
|
||||
6. No pre-aggregated totals (e.g. sub-totals or "roll-ups"). OpenSpending will do the maths and compute these automatically.
|
||||
|
||||
7. Rows have values that uniquely identify them. Each row must have some column (or combination of column) whose value(s) can be used as an "ID" for the row. Each row's ID must be unique. For example, your data could have a column named "ID" which contains a different number for each row. An easy way to create such an ID column in Excel is to add a new column, write "1" in the top cell of the column, write "2" in the second cell from the top, select both cells, and then click and drag the lower right corner of the selection to the bottom of the spreadsheet.
|
||||
|
||||
8. Dates in the correct format. Dates must be in the format "yyyy-mm-dd".
|
||||
|
||||
9. Numbers in the correct format. Numbers must contain only digits and an optional period—no commas! (Readable numbers like "12,345.67" should be converted to numbers like “12345.67”.)
|
||||
|
||||
The OpenSpending community has gathered some [example spreadsheets](https://drive.google.com/a/okfn.org/#folders/0B_dkMlz2NopEbmRoTExsMDFMR2M) in order to illustrate what "good" and “bad” tabular data looks like. Here are some examples of badly formatted spreadsheets:
|
||||
|
||||
* [Many blank cells](https://docs.google.com/a/okfn.org/spreadsheet/ccc?key=0AvdkMlz2NopEdEtIMFlEVDZXOWdDUEthUTQ0c21aV2c#gid=0) (probably redundant info omitted)
|
||||
|
||||
* [Multiple transactions, one row](https://docs.google.com/a/okfn.org/spreadsheet/ccc?key=0AvdkMlz2NopEdG5kR0kzQ0E5V3BuTS16MndBT3dMdEE#gid=0) (multiple years on one row)
|
||||
|
||||
* [Bad numbers](https://docs.google.com/a/okfn.org/spreadsheet/ccc?key=0AvdkMlz2NopEdEo1Y2p2R0VvdnJvRXMwUVREbHRoLXc#gid=0) (numbers have commas for readability)
|
||||
|
||||
Here is a good spreadsheet:
|
||||
|
||||
* [Washington, DC](https://docs.google.com/a/okfn.org/spreadsheet/ccc?key=0AvdkMlz2NopEdDhrZnRkWl9ZX2ZZNVptTzdueWw3emc#gid=0)
|
||||
|
||||
**Next**: [Publishing data on the web](../publishing-data)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Gathering data
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
To add a dataset to OpenSpending, you must first have some data. If you already have it, you can proceed. If not, you need to find it.
|
||||
|
||||
Begin your search for data by consulting esources such as the[ School of Data](http://schoolofdata.org/handbook/courses/finding-data/) and the[ Data Journalism Handbook](http://datajournalismhandbook.org/1.0/en/getting_data.html). You can also get ideas on how to go about your search by visiting the[ OpenSpending group](http://datahub.io/group/openspending) on datahub.io, and you can ask questions on the #openspending IRC channel on Freenode.
|
||||
|
||||
The data you find will hopefully be in a "machine-readable" format, for example in the form of an Excel spreadsheet or a CSV file. If you find data in a format like PDF or a Word document, it will be very hard to work with, and you might consider simply trying different data!
|
||||
|
||||
**Next**: [Formatting data](../formatting-data/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
25
examples/openspending/content/help/guide/en/index.md
Normal file
25
examples/openspending/content/help/guide/en/index.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: The OpenSpending Guide
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
The OpenSpending Guide is the manual for OpenSpending, covering the entire process of finding, adding, and using data with OpenSpending in detail.
|
||||
|
||||
* Introduction
|
||||
* [What is OpenSpending?](en/what-is-openspending)
|
||||
* [What types of financial data can go into OpenSpending?](en/financial-data-types)
|
||||
* [How does OpenSpending represent data?](en/data-model)
|
||||
* Adding Data to OpenSpending
|
||||
* [Overview](en/adding-data-overview)
|
||||
* [Gathering data](en/gathering-data)
|
||||
* [Formatting data](en/formatting-data)
|
||||
* [Publishing data on the web](en/publishing-data)
|
||||
* [Creating a dataset on OpenSpending](en/creating-dataset)
|
||||
* [Modelling your data in OpenSpending](en/modelling-data)
|
||||
* Visualizations
|
||||
* [Create a visualization](en/create-viz)
|
||||
* [Embed a visualization on your website](en/embed-viz)
|
||||
|
||||
**Up**: [OpenSpending guides](/help)
|
||||
@@ -0,0 +1,76 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Modelling your data in OpenSpending
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
To load data into OpenSpending, you must build a *model* of your data. A model specifies how your data translates into terms OpenSpending understands. OpenSpending represents the properties data in terms of *dimensions*. Modelling data consists of listing the dimensions you would like the target OpenSpending dataset to have and specifying how they relate to columns in the source data.
|
||||
|
||||
#### Mandatory dimensions: amount and time
|
||||
|
||||
Every model needs to have at least two dimensions: an amount and a time. These specify the size of the transaction and the time when the transaction took place. The amount and time are associated with special types of dimensions. An amount is represented by a *measure* dimension, and a time is represented by a *date*. Generic dimensions cannot represent these special values.
|
||||
|
||||
When modelling your data, it's not a bad idea to start with the mandatory dimensions. To begin, click the **Dimensions & Measures** tab within your dataset's **Manage the dataset** page.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_5-e1375888673131.png"><img src="http://blog.openspending.org/files/2013/08/image_5-e1375888673131.png" alt="image_5" width="600" height="232" class="alignnone size-full wp-image-587" /></a>
|
||||
|
||||
Next, click **Add Dimension** to bring up the *Add new dimension* panel. Click the radio button labeled *Date*. You will see the *Name* box automatically fill with "time", as shown below. Click the green **Add** button.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_6-e1375888703851.png"><img src="http://blog.openspending.org/files/2013/08/image_6-e1375888703851.png" alt="image_6" width="600" height="428" class="alignnone size-full wp-image-589" /></a>
|
||||
|
||||
The next screen you see will provide you some information about the meaning of time. In the drop-down box next to *Column:*, select the column of your data which represents the time value.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_7-e1375888730762.png"><img src="http://blog.openspending.org/files/2013/08/image_7-e1375888730762.png" alt="image_7" width="600" height="257" class="alignnone size-full wp-image-590" /></a>
|
||||
|
||||
Once you identify the time column, click **Add Dimension** once again to add the amount. This time, select the radio button labeled *Measure*, which will automatically fill in the name "amount", and click **Add**. Choose the column representing the value of the transaction from the drop-down box next to *Column*.
|
||||
|
||||
#### The key and compound dimensions
|
||||
|
||||
Only one additional dimension is necessary to make the model sufficient: the dimension (or set of dimensions) whose value uniquely identifies each data point, the *key*.
|
||||
|
||||
A data point does not need to be identified by the value of a single column. It can be identified by the combination of several in a *compound dimension*. Because keys *can* be compound, the compound dimension type *must* be used to represent them, even if your particular key is not compound.
|
||||
|
||||
To add the key dimension, click **Add Dimension** and select the *Dimension* radio button. Enter a name for your key, such as "key", in the name box. Click **Add**. Check the box labeled *Include in unique key* to identify this dimension as part of your key.
|
||||
|
||||
Next, take a look at the list of **Fields**, which contains two rows labeled *name *and *label*. A compound dimension can contain an arbitrary number of *fields*, each of which has a name and a type and each of which can be associated with a column in your data. This is the sense in which these dimensions are "compound": they group multiple columns from the source data into a single property of the target dataset.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_8-e1375888755790.png"><img src="http://blog.openspending.org/files/2013/08/image_8-e1375888755790.png" alt="image_8" width="600" height="378" class="alignnone size-full wp-image-591" /></a>
|
||||
|
||||
A compound dimension requires at least two fields, *name* and *label*, which must respectively be of type *id* and *string*. The dimension's name is used to provide it with a working URL, and the label is used to present it in the user interface.
|
||||
|
||||
To create a minimal compound dimension, simply associate the same column of the source data with both *name* and *label*. Choose the appropriate column for each and leave the default types unchanged.
|
||||
|
||||
#### Measures and other dimensions
|
||||
|
||||
With an amount, time, and key, your model is sufficiently rich. A really complete model, however, will include dimensions for every meaningful property of the source data. Following certain conventions makes this more convenient.
|
||||
|
||||
A common pattern in source data is spreading information that identifies entities – groups, accounts, and so on – across multiple columns. Information about an account associated with a transaction may be divided into an "Account" column with an identifying number and an "Account description" column with a verbal description, for example. "Head-account" and "Sub-account" in the image below exhibit this pattern.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_9.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_9.png" alt="image_9" width="533" height="403" class="alignnone size-full wp-image-592" /></a>
|
||||
|
||||
OpenSpending's compound dimensions are designed to model this kind of scattered information. To do so, add a new compound dimension and associate each column to one of the dimension's fields. Try to match a human-readable column to *label* and a more terse column to *name*. In the image below, "Head-account" is matched to *name* and "Head-account description" to *label*.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_10-e1375888789463.png"><img src="http://blog.openspending.org/files/2013/08/image_10-e1375888789463.png" alt="image_10" width="600" height="371" class="alignnone size-full wp-image-593" /></a>
|
||||
|
||||
Some columns of your data are more self-contained, representing particular attributes of each data point. A column which sorts each transaction into some category, for example, is of this type. In the image below, the Reporting Type, Revenue/Expenditure, and Recurrent/Investment columns are like this.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_11.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_11.png" alt="image_11" width="609" height="378" class="alignnone size-full wp-image-594" /></a>
|
||||
|
||||
Self-contained columns specifying attributes or categories are best modeled with *attribute* dimensions. An attribute is essentially a dimension with only a single field, which may have any type. To create an attribute, simply select the *Attribute* radio button when adding a dimension.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_12-e1375888823415.png"><img src="http://blog.openspending.org/files/2013/08/image_12-e1375888823415.png" alt="image_12" width="600" height="472" class="alignnone size-full wp-image-595" /></a>
|
||||
|
||||
#### Wrapping up: saving and loading
|
||||
|
||||
When every dimension has been specified and linked to columns in the source data, click **Save Dimensions** to save the model. If anything is wrong with the model, an error message will appear, prompting you to correct its parameters. Otherwise, a message will appear inviting you to return to the dashboard, where you can proceed to load your data.
|
||||
|
||||
Once the data has been loaded, the model you have created will be fixed and editing will be disabled. You may therefore wish to test the model before you load. To do this, click **Test a sample** in your data source's row in the dashboard. Wait a few seconds, then reload the page. If you see a message saying COMPLETE with a green background, your model is ready to go. If you see ERRORS, repairs are needed.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_13-e1375888848457.png"><img src="http://blog.openspending.org/files/2013/08/image_13-e1375888848457.png" alt="image_13" width="600" height="279" class="alignnone size-full wp-image-596" /></a>
|
||||
|
||||
If your model is free of errors, click **Load** to load the source dataset and apply the model. You may then return to the dataset's home page by clicking its name at the top of the screen, where you can proceed to construct visualizations and otherwise play with your data.
|
||||
|
||||
**Next**: [Create a Visualization](../create-viz/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: Publishing data on the web
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
Data cannot (yet) be uploaded directly to OpenSpending. In order to be added to the OpenSpending database, data must first be made accessible from the web. This section introduces two convenient ways to publish sets of data online.
|
||||
|
||||
#### Google Drive
|
||||
|
||||
You can make your data accessible on the web by turning it into a Google Drive spreadsheet.
|
||||
|
||||
1. Import your data. Create a new Google Drive spreadsheet, then select *Import...* from the File menu. Select *Replace Spreadsheet*, click **Choose File**, and navigate to your CSV file.
|
||||
|
||||
2. Make sure Google Docs doesn't mis-format your data's dates. Select the column that contains dates. Click the *Format* menu and select *Number* -> *More formats* -> *2008-09-26*. Your dates should appear in the prescribed **yyyy-mm-dd** format.
|
||||
|
||||
3. Click the *File* menu and select *Publish to the web...*. In the box that appears, click **Start publishing**. Beneath *Get a link to the published data*, select **CSV (comma-separated values)**.
|
||||
|
||||
<a href="{{ site.baseurl }}/img/blog/2013/08/image_0.png"><img src="{{ site.baseurl }}/img/blog/2013/08/image_0.png" alt="image_0" width="596" height="578" class="alignnone size-full wp-image-577" /></a>
|
||||
|
||||
The URL at the bottom of the box now points to your data.
|
||||
|
||||
#### Gist
|
||||
|
||||
GitHub Gist is a convenient way to host small quantities of text, including CSV files.
|
||||
|
||||
1. Log in to GitHub (or register if you haven't already done so), then navigate to[ gist.github.com](https://gist.github.com/).
|
||||
|
||||
2. Click and drag your CSV file from your operating system's file manager onto the GitHub Gist page of your browser. The file's name and contents will appear.
|
||||
|
||||
3. Click **Create Public Gist** to be taken to the homepage of your new gist. The raw URL of your data is accessible through the "angle brackets" button in the top right corner of the file.
|
||||
|
||||
<a href="http://blog.openspending.org/files/2013/08/image_1-e1375888253802.png"><img src="http://blog.openspending.org/files/2013/08/image_1-e1375888253802.png" alt="image_1" width="600" height="141" class="alignnone size-full wp-image-578" /></a>
|
||||
|
||||
**Next**: [Creating a dataset on OpenSpending](../creating-dataset/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
section: help
|
||||
lead: true
|
||||
title: What is OpenSpending?
|
||||
authors:
|
||||
- Neil Ashton
|
||||
---
|
||||
OpenSpending is a data sharing community and web application that aims to track every government and corporate financial transaction across the world and to present that data in a useful and engaging form. OpenSpending is an open project maintained by a community of contributors. Anyone interested in spending data of any kind is invited to contribute data to the OpenSpending database, create visualizations using the OpenSpending software, and use the OpenSpending API.
|
||||
|
||||
This chapter introduces new OpenSpending contributors to the core concepts of the system. It describes the kind of financial data that OpenSpending supports, and it explains how OpenSpending represents that data.
|
||||
|
||||
**Next**: [What types of financial data can go into OpenSpending?](../financial-data-types/)
|
||||
|
||||
**Up**: [OpenSpending Guide](../)
|
||||
Reference in New Issue
Block a user