Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature] Improve on the case table #227

Open
1 task done
webbunivAdmin opened this issue Oct 15, 2024 · 7 comments · May be fixed by #242 or #245
Open
1 task done

[Feature] Improve on the case table #227

webbunivAdmin opened this issue Oct 15, 2024 · 7 comments · May be fixed by #242 or #245
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@webbunivAdmin
Copy link

webbunivAdmin commented Oct 15, 2024 •
edited
Loading

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.
@webbunivAdmin webbunivAdmin added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Oct 15, 2024
@TimidRobot TimidRobot added 🧹 status: ticket work required Needs more details before it can be worked on 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 💻 aspect: code Concerns the software code in the repository labels Oct 15, 2024
@TimidRobot

This comment was marked as outdated.

Sign in to view
@webbunivAdmin

This comment was marked as outdated.

Sign in to view
@TimidRobot TimidRobot added help wanted Open to participation from the community 🏁 status: ready for work Ready for work and removed 🧹 status: ticket work required Needs more details before it can be worked on labels Oct 16, 2024
@TimidRobot
Copy link
Member

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)

@webbunivAdmin

This comment was marked as outdated.

Sign in to view
@SisiVero

This comment was marked as outdated.

Sign in to view
@webbunivAdmin

This comment was marked as outdated.

Sign in to view
@webbunivAdmin webbunivAdmin linked a pull request Oct 19, 2024 that will close this issue
Open
7 tasks
mailsg added a commit to mailsg/legaldb that referenced this issue Oct 21, 2024
@mailsg
Fix issue creativecommons#227 - Improve the case table with sorting a…
7c1d9e6 
…nd pagination
@mailsg mailsg linked a pull request Oct 21, 2024 that will close this issue
Open
7 tasks
@TimidRobot
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Applications
Status: Backlog
Milestone
No milestone
3 participants
@TimidRobot @SisiVero @webbunivAdmin