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

Store reporters for each case in separate join table #40

Open
ProbablyFaiz opened this issue Dec 21, 2021 · 0 comments
Open

Store reporters for each case in separate join table #40

ProbablyFaiz opened this issue Dec 21, 2021 · 0 comments
Labels
infrastructure Dependency upgrades, refactors, etc.

Comments

@ProbablyFaiz
Copy link
Member

ProbablyFaiz commented Dec 21, 2021 •
edited
Loading

Right now, we just store an arbitrary reporter's (except that U.S. reporters are prioritized) string representation in the Cluster table, but this is somewhat stupid for a number of reasons. CourtListener's data often has several reporters for each Cluster in its constituent parts, and we should mirror that structure to an extent.
@ProbablyFaiz ProbablyFaiz added the feature New feature or request label Dec 21, 2021
@ProbablyFaiz ProbablyFaiz added infrastructure Dependency upgrades, refactors, etc. and removed feature New feature or request labels Dec 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure Dependency upgrades, refactors, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ProbablyFaiz