To enable "datapackage.json" files to be pre-generated and edited if desired prior to upload. Current workflow without this only auto-generates a "datapackage.json" file in deposit_upload_file(). This makes describing the frictionless part of the workflow (#26) more difficult than it should be. A deposit_add_resource() method will simplify the workflow, by permitting local-only initial generation and editing of "datapackage.json", and of all metadata within there.
There will then be some overlap between deposit_fill_metadata() and deposit_add_resource(). Once a "datapackage.json" file has been generated, passing the path to that file to either of these methods should yield the same result of a client populated with the metadata in that file.
To enable "datapackage.json" files to be pre-generated and edited if desired prior to upload. Current workflow without this only auto-generates a "datapackage.json" file in
deposit_upload_file(). This makes describing the frictionless part of the workflow (#26) more difficult than it should be. Adeposit_add_resource()method will simplify the workflow, by permitting local-only initial generation and editing of "datapackage.json", and of all metadata within there.There will then be some overlap between
deposit_fill_metadata()anddeposit_add_resource(). Once a "datapackage.json" file has been generated, passing the path to that file to either of these methods should yield the same result of a client populated with the metadata in that file.