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.

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

[Feature] support publicly accessible case law databases #190

Open
1 task
TimidRobot opened this issue Sep 6, 2024 · 2 comments
Open
1 task

[Feature] support publicly accessible case law databases #190

TimidRobot opened this issue Sep 6, 2024 · 2 comments
Labels
💻 aspect: code Concerns the software code in the repository 🕹 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

@TimidRobot
Copy link
Member

Problem

The information available is limited to what has been captured and made available (ex. https://legaldb.creativecommons.org/cases/1/ links to https://wiki.creativecommons.org/images/f/f6/2010-10-26_A%27cision-trib.-Nivelles-Lichodmapwa.pdf)

Description

The existing interface links to relevant PDFs, but linking to relevant publicly accessible case law databases could increase context, discoverability, etc.

Ideally, case law databases could be supported in the UX so that linking to them requires a minimal amount of information.

For example, https://legaldb.creativecommons.org/cases/2/ could link to https://www.courtlistener.com/docket/4390142/chang-v-virgin-mobile-usa-llc/

Additional research is needed to identify publicly accessible case law databases in multiple jurisdictions.

Support for publicly accessible case law databases could also aid discovery of additional cases that should be cataloged in the LegalDB.

Additional context

Implementation

  • I would be interested in implementing this feature.
@TimidRobot TimidRobot added 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 ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software labels Sep 6, 2024
@jatinder14
Copy link

hi @TimidRobot I wanna try it out can you please assign it to me

@TimidRobot
Copy link
Member Author

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

We generally don't assign issues prior to resolution. Instead of asking for issues to be assigned, do the work and submit a pull request (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
Labels
💻 aspect: code Concerns the software code in the repository 🕹 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
Status: Backlog
Development

No branches or pull requests

2 participants