Export plugins

[kayakr]

Desired Behaviour

As a developer
I want to be able to define export targets using a JSON definition
So that I don't have to compile Data Curator to target CKAN, Fedora, etc.

That way, I can export to a Data package, but I could specify other destinations in a discoverable way using a JSON definition file dropped into an export plugins directory(?) including credentials if needed.

[ghost]

Hi @kayakr
Yes it's a good idea. There was some discussion about what could be done here, that eventually did not get approved.
I take it that the idea is that it means instead of just offering to zip a package on the local filesystem, you could send the zip via an API with credentials that you could load in say preferences and choose so that there is a default export behaviour. Have I got that right?

[kayakr]

@mattRedBox I figure each data platform has its own APIs and quirks, but perhaps the ability to push a datapackage to a URI would at least create a nice workflow for curators (perhaps with some kind of success/fail reporting). This would depend on receiving systems being configured to support ingest of datapackages, but that should be feasible...

[ghost]

OK, thanks @kayakr. That sounds reasonable.

[ghost]

Seems similar to #787