Skip to content

v0.4.0

Latest
Latest
Compare
Choose a tag to compare
@stuartmcalpine stuartmcalpine released this 27 Apr 09:57
· 27 commits to main since this release
v0.4.0
c93c847
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Version 0.4.0

Version 0.4.0 focuses around being able to manipulate data already within the dataregistry, i.e., adding the ability to delete and modify previous datasets.

Changelog for developers:

  • Registrar now has a class for each table. They inherit from a BaseTable class, this means that shared functions, like deleting entries, are available for all tables. (#92)
  • Working with tables via the python interface has slightly different syntax (see user changelog below). (#92)
  • is_valid is removed as a dataset property. It has been replaced with status which is a bitmask (bit 0="valid", bit 1= "deleted" and bit 2="archived"), so now datasets can a combination of multiple states. (#93)
  • archive_date, archive_path, delete_date, delete_uid and move_date have been added as new dataset fields. (#93)
  • Database version bumped to 2.0.1 (#93)
  • dataset entries can be deleted (see below) (#94)
  • The CI for the CLI is now pure Python (i.e., there is no more bash script to ingest dummy entries into the registry for testing).
  • Can no longer "bump" a dataset that has a version suffix (trying to do so will raise an error). If a user wants to make a new version of a dataset with a suffix they can still do so by manually specifying the version and suffix (#97 ).
  • Dataset entries can be modified (see below, #100)

Changelog for users:

  • All database tables (dataset, execution, etc) have a more universal syntax. The functionality is still accessed via the Registrar class, but now for example to register a dataset it's Registrar.dataset.register(), similarly for an execution Registrar.execution.register() (#92). The docs and tutorials have been updated (#95).
  • dataset entries can now be deleted using the Registrar.dataset.delete(dataset_id=...) function. This will also delete the raw data within the root_dir. Note that the entry in the database will always remain (with an updated status field to indicate it has been deleted). (#94)
  • Documentation has been updated to make things a bit clearer. Now split into more focused tutorials (#95).
  • Certain dataset quantities can be modified after registration (#100). Documentation has been updated with examples.
Assets 2