Skip to content

Store reporters for each case in separate join table #40

@ProbablyFaiz

Description

@ProbablyFaiz

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    infrastructureDependency upgrades, refactors, etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions