{"action":"closed","issue":{"url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/128","labels_url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/128/labels{/name}","comments_url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/128/comments","events_url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/128/events","html_url":"https://github.com/openspending/fiscal-data-package/issues/128","id":128778355,"number":128,"title":"Can one column be mapped to more than one dimension?","user":{"login":"danfowler","id":772616,"avatar_url":"https://avatars.githubusercontent.com/u/772616?v=3","gravatar_id":"","url":"https://api.github.com/users/danfowler","html_url":"https://github.com/danfowler","followers_url":"https://api.github.com/users/danfowler/followers","following_url":"https://api.github.com/users/danfowler/following{/other_user}","gists_url":"https://api.github.com/users/danfowler/gists{/gist_id}","starred_url":"https://api.github.com/users/danfowler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danfowler/subscriptions","organizations_url":"https://api.github.com/users/danfowler/orgs","repos_url":"https://api.github.com/users/danfowler/repos","events_url":"https://api.github.com/users/danfowler/events{/privacy}","received_events_url":"https://api.github.com/users/danfowler/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/openspending/fiscal-data-package/labels/Discussion","name":"Discussion","color":"5319e7"}],"state":"closed","locked":false,"assignee":{"login":"danfowler","id":772616,"avatar_url":"https://avatars.githubusercontent.com/u/772616?v=3","gravatar_id":"","url":"https://api.github.com/users/danfowler","html_url":"https://github.com/danfowler","followers_url":"https://api.github.com/users/danfowler/followers","following_url":"https://api.github.com/users/danfowler/following{/other_user}","gists_url":"https://api.github.com/users/danfowler/gists{/gist_id}","starred_url":"https://api.github.com/users/danfowler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danfowler/subscriptions","organizations_url":"https://api.github.com/users/danfowler/orgs","repos_url":"https://api.github.com/users/danfowler/repos","events_url":"https://api.github.com/users/danfowler/events{/privacy}","received_events_url":"https://api.github.com/users/danfowler/received_events","type":"User","site_admin":false},"milestone":{"url":"https://api.github.com/repos/openspending/fiscal-data-package/milestones/1","html_url":"https://github.com/openspending/fiscal-data-package/milestones/v0.3","labels_url":"https://api.github.com/repos/openspending/fiscal-data-package/milestones/1/labels","id":1391691,"number":1,"title":"v0.3","description":"","creator":{"login":"rgrp","id":180658,"avatar_url":"https://avatars.githubusercontent.com/u/180658?v=3","gravatar_id":"","url":"https://api.github.com/users/rgrp","html_url":"https://github.com/rgrp","followers_url":"https://api.github.com/users/rgrp/followers","following_url":"https://api.github.com/users/rgrp/following{/other_user}","gists_url":"https://api.github.com/users/rgrp/gists{/gist_id}","starred_url":"https://api.github.com/users/rgrp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rgrp/subscriptions","organizations_url":"https://api.github.com/users/rgrp/orgs","repos_url":"https://api.github.com/users/rgrp/repos","events_url":"https://api.github.com/users/rgrp/events{/privacy}","received_events_url":"https://api.github.com/users/rgrp/received_events","type":"User","site_admin":false},"open_issues":8,"closed_issues":46,"state":"open","created_at":"2015-11-03T16:53:12Z","updated_at":"2016-01-28T14:40:36Z","due_on":"2016-01-30T21:00:00Z","closed_at":null},"comments":3,"created_at":"2016-01-26T10:03:00Z","updated_at":"2016-01-28T14:40:36Z","closed_at":"2016-01-28T14:40:36Z","body":"Part of the motivation behind the Fiscal Data Package specification is to require as little modification to the source data as possible.  It accomplishes this through the `mapping` object which allows columns in the \"physical\" model (source CSV) to be mapped to various attributes of dimensions in the \"logical\" model.  In the [BOOST Moldova dataset](https://github.com/openspending/fiscal-data-package-demos/tree/master/boost-moldova), we have data like this:\r\n\r\n| year | admin1 | admin2 | amount |\r\n|---|---|---|---|\r\n| 2014 | Local | District Council Floresti | 1000 | \r\n\r\nIn this case, `admin1` and `admin2` naturally map as attributes of an `administrative` dimension.  However, `admin2` also provides information that could naturally map to an attribute in the `location` dimension for e.g. geographic visualization.  Should we allow one column to be mapped to more than one dimension?"}}