-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Description
Description
This feature request proposes adding a transpose option to the existing database table view that allows users to switch between the standard layout and a transposed layout where properties become rows and records become columns.
Key Features:
- Toggle Option: A transpose button/option within the table view interface to switch between standard and transposed layouts
- Same Data, Different Perspective: Properties displayed as row headers, records as column headers in transposed mode
- Seamless Integration: Built into the existing table view rather than as a separate view type
- Enhanced Comparison: Side-by-side record comparison capabilities in transposed mode
- Consistent Functionality: All existing table features (editing, filtering, sorting) work in both layouts
- Responsive Design: Optimized for both desktop and mobile experiences
Technical Implementation:
- Transpose toggle integrated into existing table view controls
- Dynamic layout switching without data reloading
- Optimized rendering for wide tables with horizontal scrolling
- Full compatibility with existing filtering and sorting operations
- Mobile-responsive design with touch-friendly interactions
Benefits:
- Flexible Data Visualization: Users can choose the most appropriate layout for their data analysis needs
- Improved Record Comparison: Enhanced ability to compare multiple records across properties
- Space Efficiency: Better utilization of screen space for datasets with many properties but fewer records
- User Choice: Accommodates different data viewing preferences without changing the core table functionality
Known Limitations:
- Grouped Entry Creation: When entries are grouped by column values, adding new entries presents challenges in determining the appropriate group assignment. This limitation exists in both the standard and transposed table views and is not specific to the transpose functionality.
Use case
This feature would benefit users in scenarios where the transposed view provides better data analysis capabilities:
-
Data Analysis: When comparing multiple records across many properties, the transposed view makes it easier to scan values horizontally for each property.
-
Record Comparison: Comparing profiles, specifications, or metrics across different entities (people, products, projects) becomes more intuitive when entities are columns.
-
Property-Focused Analysis: When the focus is on understanding how different records perform across specific properties rather than reviewing all properties of individual records.
-
Wide Dataset Management: For databases with many columns that cause horizontal scrolling issues in standard view.
-
Presentation and Reporting: When preparing data summaries or reports where the transposed layout provides clearer insights.
The transpose option is particularly valuable when:
- The dataset has many properties but relatively fewer records
- Users need to focus on comparing specific attributes across multiple records
- The standard table view becomes too wide and difficult to navigate
- Different team members prefer different data layout orientations for analysis
Anything else?
Implementation Status:
This feature has been successfully implemented and tested in a fork of AFFiNE:
- Repository: https://github.com/ntexier-belenos/AFFiNE/
- Issue tracking: [Feature Request] Add Horizontal Table View for Databases ntexier-belenos/AFFiNE#4
- Status: ✅ Completed and production-ready
Technical Details:
The implementation includes:
- Integration with existing table view infrastructure
- Transpose toggle control in the table view interface
- Dynamic layout switching capabilities
- Full preservation of existing database operations
- Responsive design for both desktop and mobile platforms
Known Technical Limitations:
- Entry Creation with Grouping: When entries are grouped by column values, the addition of new entries can be problematic as it's unclear which group the new entry should belong to. This limitation is present in both the classic table view and the transposed view, and is not related to the transpose functionality itself.
Research Conducted:
A comprehensive search of the official AFFiNE repository confirmed that no similar feature request or implementation exists, making this a unique contribution opportunity.
Community Value:
This feature enhances the existing table view functionality without disrupting current workflows, providing users with more flexibility in how they visualize and interact with their database content.
Contribution Readiness:
The complete implementation is available and ready to be contributed back to the main AFFiNE repository through a pull request, following the project's contribution guidelines.
Are you willing to submit a PR?
- Yes I'd like to help by submitting a PR!
Metadata
Metadata
Assignees
Labels
Type
Projects
Status