Refactor the Dataset Detail Page into a Tab-Based Layout
- Dominant language
- Scala
- Stars
- 314
- Forks
- 187
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 214
Description
### Feature Summary
As more dataset-related features have been added, the dataset detail page has become crowded. Currently, dataset metadata, statistics, version management, upload history, and settings are all displayed on a single page. While the current layout is functional, it is becoming harder to navigate and leaves limited room for future expansion.
Refactor the dataset detail page into a tab-based layout to better organize related functionality.
Current dataset page
### Proposed Solution or Design
Refactor the dataset detail page into a tab-based layout so that related information and actions are grouped into clear sections.
The page can be organized into the following tabs:
#### Data Card
Displays the main dataset information, including:
* Dataset overview
* Metadata
* Statistics
* Tags, owner, and visibility
#### Uploads & Versions
Contains dataset upload and version-related functionality, including:
* Upload history
* Dataset versions
* Version details and management actions
#### Settings
Contains dataset configuration and administrative controls, including:
* Dataset management actions
* Access control
* Other dataset-related settings
The refactor should preserve the existing functionality while improving navigation and reducing visual clutter. The tab structure should also make it easier to add new dataset features in the future without further crowding the page.
Sample:
### Affected Area
_No response_
Contributor guide
Research direction
The issue names the dataset detail page but no files, tests, or entry points. Start by locating that page and its existing metadata, statistics, upload/version, and settings sections; compare them with the proposed Data Card, Uploads & Versions, and Settings tabs. Done means existing functionality is preserved and the three groups are navigable without the current crowding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100