The register command registers a CSV table into the local qsv registry.
The registry enables:
easy reference in other qsv command to CSVs/TSVs by their assigned alias/es for both CSV name and column names.
the metadata of the registered CSVs are precomputed (stats, frequency, schema) and persisted in the registry, enabling lookups not only against the CSV data, but also against its metadata
the enrich command (see #487 )
Registering a CSV will use the package (see #486 ) command to populate the registry. The registry database is TBD (sqlite?, UnQLite? Sled? turingdb?)
The qsv registry store will be interoperable with CKAN - i.e. qsv can fetch data/metadata from a CKAN catalog and upload registered packages to CKAN.
upload the CSV to a designated CKAN site or to datHere's central registry if the user does not have a CKAN site
upon upload, the CSV is added to the Datastore with DP+ and all the metadata is prepopulated. A zipsigned compressed file is also stored to facilitate easy, quick and secure retrieval from any computer by the owner and approved users/collaborators
it will now have a Datastore API and is available for remote API queries - both traditional API and qsvAPI (qsv Answering People Interface 😄 ) queries with the ask and sqlp commands
assign a qsvid to the CSV. qsvid is a UUID - the URL to the registry entry
create a checksum for the CSV and add it to the registry entry
add a comment to the first line of the CSV with some registry metadata ("#" followed by qsvid, version no, last updated, created, num rows, num columns, etc.)
The
register
command registers a CSV table into the local qsv registry.The registry enables:
enrich
command (see #487 )Registering a CSV will use the
package
(see #486 ) command to populate the registry. The registry database is TBD (sqlite?, UnQLite? Sled? turingdb?)The qsv registry store will be interoperable with CKAN - i.e. qsv can fetch data/metadata from a CKAN catalog and upload registered packages to CKAN.