We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Adding a dataset via
DataToolkitBase.add(DataToolkit.Dataset, name, Dict{String, Any}("description" => description), source)
still prompts for user input on description and attributes, which is probably not intended?
Btw., is spec::Dict{String, Any} the right place to put description info?
spec::Dict{String, Any}
The text was updated successfully, but these errors were encountered:
Yea, the DataToolkitBase "julia API" probably needs a bit more love that I've been able to give it so far.
DataToolkitBase
It should definitely be able to operate noninteractively, and to answer your question spec is indeed the right place to put a description.
spec
Sorry, something went wrong.
On this topic, if anybody has ideas for a nice Julia API and a willingness to dig into the codebase, I'd love to hear them.
I'm currently overhauling this, so interactive input is gated behind the (new) REPL package.
REPL
Here's what the WIP-API looks like:
collection = DataCollection() dataset = create!(collection, DataSet, "name", "description" => desc, ...) create!(dataset, DataStorage, :filesystem, "path" => "path/to/file.csv") create!(dataset, DataLoader, :csv)
I'm wondering if for convenience it might also be worth having
collection = DataCollection() dataset!(collection, "name", "description" => desc, ...) storage!(dataset, :filesystem, "path" => "path/to/file.csv") loader!(dataset, :csv)
No branches or pull requests
Adding a dataset via
still prompts for user input on description and attributes, which is probably not intended?
Btw., is
spec::Dict{String, Any}
the right place to put description info?The text was updated successfully, but these errors were encountered: