Skip to content

Break down summary into multiple components. #112

@maxachis

Description

@maxachis

Enhancement

What needs done

Modify summary queries such that results are broken down into a consistent json file format containing the following keys:

  • "paragraph_summary": A paragraph-length summary of the bill, more or less equivalent to the summaries as they are given now, absent where information in those summaries are presented in the other sections
  • "sentence_summary": A single-sentence summary for quick perusal.
  • "takes_effect": When the bill takes effect (for example, 60 days after being passed)
  • "legislation_affected": What, if any, existing legislation is impacted by this legislation.

Why it needs done

Summaries at present reliably include a regular set of information: Who introduced the bill, when it takes effect, what (if any) existing legislation it affects, and its overall purpose. Breaking these components into separate components will aid search and perusal of information.

Additionally, a one-sentence summary would likely be useful in addition to a more in-depth paragraph-length summary, as it can allow people to examine the summary at a glance. An even shorter "summary title" might be useful, although this may overlap too much with a single-sentence summary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions