[Feature] Improve on the case table

Question

[Feature] Improve on the case table

Opened this issue 2 months ago · 7 comments

webbunivAdmin commented 2 months ago

Problem

I would want to improve on the case table such that it can accommodate much data
but not consuming space on the page which i believe that it can make the case page not be overcrowded ie
https://legaldb.creativecommons.org/cases/

Description

To address this issue, I propose implementing an interactive and dynamic table that can accommodate large datasets more effectively without occupying excessive space. Features like pagination, search functionality, and sorting will allow users to view and navigate the data more easily. This will help avoid overcrowding while maintaining a professional and streamlined design.

Alternatives

There are various methods and libraries that could solve this issue. Depending on the development environment and needs, different solutions can be implemented to achieve a dynamic and flexible table. The goal is to improve the usability and scalability of the case table, regardless of the specific tool or library used.

Additional context

Implementation

I would be interested in implementing this feature.

Answer 1 · 2024-10-15T17:37:45.000Z

@webbunivAdmin please update the description to provide more detail

Answer 2 · 2024-10-16T07:26:02.000Z

@webbunivAdmin please update the description to provide more detail

i have updated it

Answer 3 · 2024-10-16T14:26:01.000Z

Please note:

Search (with filtering) is already implemented
Pagination must be implemented in Django (Python and HTML)
Sort must also be implemented in Django (so that the entire table is sorted, regardless of pagination)

Answer 4 · 2024-10-16T20:31:00.000Z

ok assign this to me

Answer 5 · 2024-10-17T15:16:08.000Z

ok assign this to me

Hi, you don't need to be assigned. You can go ahead and work on it since it has already been set 'ready for work".

Answer 6 · 2024-10-19T15:02:12.000Z

ok let me do it

Answer 7 · 2024-10-21T17:49:24.000Z

Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and pull requests (PRs).

We generally don't assign issues prior to resolution. Instead of asking for issues to be assigned, do the work and submit a PR. Even if multiple people submit PRs for the same issue, multiple ideas and implementations strengthen the final product.

For work program applicants, each can all list their own PRs on their application. It is the quality of work that is important, not whether it is merged.