ckan / ckan/datapusher

Support generic data urls rather than just CKAN resources as input

Open
#20 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
82
Forks
157
PR merge metrics
No merged PRs in 30d

Description

[At the moment](https://github.com/okfn/datapusher/blob/master/datapusher/jobs.py#L223) it seems datapusher gets passed resource id and then looks up data url.

That is metadata pushed to a job would be:

```
'metadata': {
'url': path-to-data-csv-or-xls
'resource_id': res_id, # resource to push to (a bonus would to have this auto-created
'set_url_type': data_dict.get('set_url_type', False)
}
```

Why do this?
- It seems to be to be simpler - don't have to spend time looking up the resource url from CKAN
- More general - can support data not yet in CKAN

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.