Description:
Restructure uvlhub so that it is no longer focused on UVL datasets, but another type of specic data.
The goal is to transform it into a [datatype]hub, where different data domains can have their own logic without duplicating the platform. For instance, a UMLhub for UML models, a BPMHub for BPM models, a GenomicHub for genomic datasets.
Details:
- Each dataset type defines its own model (e.g.,
UVLDataset, ImageDataset, TabularDataset), inheriting from a common base class (BaseDataset).
- Each model includes its own validations and business logic, avoiding a single bloated model with conditionals.
- Upload/edit workflows and forms are defined per module (e.g., one form for UVL, another for tabular datasets).
- The versioning system is applied across all types, but each dataset type can extend it with custom behavior.
- The explorer and dataset detail page are built in a modular/extensible way:
- Common fields (title, authors, community, DOI, downloads).
- Specific blocks depending on dataset type (e.g., UVL tree view, tabular preview, image gallery).
Description:
Restructure uvlhub so that it is no longer focused on UVL datasets, but another type of specic data.
The goal is to transform it into a [datatype]hub, where different data domains can have their own logic without duplicating the platform. For instance, a UMLhub for UML models, a BPMHub for BPM models, a GenomicHub for genomic datasets.
Details:
UVLDataset,ImageDataset,TabularDataset), inheriting from a common base class (BaseDataset).