xuang7 opened a new issue, #6394:
URL: https://github.com/apache/texera/issues/6394

   ### 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
   <img width="2788" height="1580" alt="image" 
src="https://github.com/user-attachments/assets/2497e279-1bfb-41f9-8479-8201f9ced9f6";
 />
   
   ### 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:
   <img width="946" height="637" alt="setting" 
src="https://github.com/user-attachments/assets/b215a3a8-ff8f-42e3-bd13-d04a9c5b9c78";
 />
   
   ### Affected Area
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to