Discussion: Ideas for file uploading about jkan

[mheadd]

My vote would be to keep JKAN as a directory, rather than a repository, unless there is a compelling reason to do so.

Google Drive, Dropbox and some other services that make it easy to set up FTP servers should meet most people's needs. And this allows you to keep JKAN simple and easy to use.

[JJediny]

Agree with @mheadd best to keep it simple and avoid offering an uploader via JKAN... as users can use any publically hosted file as a source, but it might make sense to offer a JS lookup of files in a specific directory within the repo like files. This would allow users to associate/link to an already available file in the repo?

This would also make it easier to re-associate/test/reconstruct links (independent of forks) while simplifying the experience for the user with a dropdown list?

[waldoj]

I don't have any clever ideas to contribute about how to do this, I just want to say that I think that this is a fine idea, but one that I'd hold off on for a v2.0. Right now, JKAN is a catalog instead of a repository (a distinction, BTW, that I'd never seen articulated before), and if was me, I'd focus on being a great catalog first. This seems like it could be a big time sink.

[timwis]

Good points guys, thanks. Just want to add in @aborruso's comment from #34 as it's quite relevant here:

About github and publishing using "official" open data schema I think it's useful to look ad git-data-publisher

Example generated data page

[iltempe]

Actually i link filetto that i store in another github dataset. I prefer separate data from website...

[mheadd]

@timwis Git Data Publisher looks pretty boss. I will say that the auto generated datapackage.json is a nice benefit as well. makes it super easy to push to a full data portal with API if desired.