Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom remotes #2

Open
pwalsh opened this issue Jun 12, 2015 · 3 comments
Open

Custom remotes #2

pwalsh opened this issue Jun 12, 2015 · 3 comments

Comments

@pwalsh
Copy link
Contributor

pwalsh commented Jun 12, 2015

User should be able to pass in a custom remote. Default remote is CKAN 3.

To do this we might need to change the structure of the remote config object a bit.

@gvidon
Copy link
Contributor

gvidon commented Jun 12, 2015

@pwalsh we could do this by allowing user passing in optional callback which will be used for data mapping instead of datapackage-remote-js internal config. But this way the only role of datapackage-remote-js is just to download data and perform user callback over it — it's hard to believe that anyone will us it like this. I may be wrong and miss some points.

@pwalsh
Copy link
Contributor Author

pwalsh commented Jun 14, 2015

@gvidon I see your point.

The reason I have datapackage-from-remote as a distinct library is to include more "builtin remotes", like the one we have for ckan 3. So for example, we may add a "socrata" remote, or an "openspending 1.0" remote.

So then, the utility of the library is that it is aware of all the major open data portals, and has built-in mapping from those various formats, into Data Package format (and specifically, a particular Data Package Profile, like base, tabular, etc).

So, when I'm also suggesting we allow the user to add a custom remote, it is in the context of seeing this library developing to support a range of data portals so we can migrate that data into Data Package, but also allowing a user to add their own remote if there is one we don't have.

@gvidon
Copy link
Contributor

gvidon commented Jun 14, 2015

@pwalsh ok, I see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants