A new DataDeck version is out. In DataDeck v0.4.0 I implemented quite all the additions I developed in dpm library. In this release I focused on packages. Because DataDeck searches and downloads packages from The Data Hub, it makes sense to have those packages organized and easily managed.
Therefore, DataDeck now has a Package Library (or a local workspace):
The Library provides a unique and easy way to see which packages are locally installed. Extended information on local packages can be retrieved. Of course, local packages may be deleted from disk if necessary.
Notice anything else new? A package can also be edited and saved. There is a new Create panel for this:
Because of other recent dpm modifications I proposed and developed, I took the occasion to let users create packages from scratch. Those packages may also be stored in the Library, too.
This is just a little step: we must still let users add resources to packages and upload packages to The Data Hub. But I am very satisfied about the development so far.
Here is the changelog for DataDeck v0.4.0:
- All functionalities can be reached from the main GUI (tabbed GUI style)
- Three main parts: Library, Search and Create
- Library is a unique workspace of Packages in which downloaded, created and modified packages are stored or deleted.
- Search was already present in previous versions: it gives the user the possibility to search (and download) packages in thedatahub.org
- Create is the addition and modification of Packages: ex-novo or from already existant packages
- For guiding the user, the relevant buttons are enabled/disabled when necessary
- The installation of dpm is detected at program start, user is warned if it is missing
- The configuration is created on first program start, user is warned to set a Package Library path
- Many internal functions have been rewritten from scratch to ensure better performance.
- Many bugs fixed
What will be next?
- As soon as dpm.lib implements adding, modifying and deleting resources of a package, DataDeck will also follow it.
- Pushing a package and its resources to The Data Hub
- Forking a package is already possible but can be better presented in the GUI
- Finalizing integration with Sofa Stats