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

Court: Docket entry format #937

Closed
28 tasks done
JessicaMarine opened this issue Feb 26, 2019 · 3 comments
Closed
28 tasks done

Court: Docket entry format #937

JessicaMarine opened this issue Feb 26, 2019 · 3 comments
Labels
Milestone

Comments

@JessicaMarine
Copy link

JessicaMarine commented Feb 26, 2019

As the Court, in order to maintain consistency across all filings in the docket record, I need the docket entry for a new document to include specific information in a specific format.

The Court currently uses a format of Concatenated Document Title (C/S 04/17/2019) (Exhibit(s)) (Attachment(s)) (Objection) (Lodged) on all external filings. Keeping the format consistent across all filings in the docket record makes it easy to read.

Pre-Conditions

  • A Party has successfully filed a document.

Acceptance Criteria

  • The docket entry is populated based on Court-provided rules [See below for sample docket entry format]
  • Document title is a hyperlink to the actual document.
  • Each docket entry should include a sequential docket entry number
  • Each docket entry has the associated event code (derived from document type)

Notes

  • Court is not bound to All caps for document title
  • Court currently uses "Exhibit" or "Exhibits" to differentiate between one or more exhibits. The Court is not bound to this current practice and "Exhibit(s)" is fine for all instances where one or more Exhibits are attached to a document. Same thing for "Attachment(s)".

Tasks

Engineering

Definition of Done

Product Owner

  • Acceptance criteria have been met

UX

  • Usability has been validated

Engineering

  • Field level and page level validation errors (front-end and server side) integrated and functioning
  • Run the browser stack scripts to verify that application is usable in Chrome, Firefox, Safari, Edge and Internet Explorer (external only)
  • No errors reported in manual a11y testing
  • All new functionality verified to work with keyboard and osx voiceover
  • Code refactored for clarity and to remove any known technical debt
  • README, other appropriate docs, and swagger/APIs fully updated - all code functions documented with jsdocs
  • UI should be touch optimized and responsive for external only(functions on supported mobile devices and optimized for screen sizes as required)
  • Library/module dependencies are up-to-date and are at the latest resolvable version
  • Code is deployed to DEV
  • Errors in sonarcloud are fixed (https://sonarcloud.io/organizations/flexion-github/projects)
  • Alerting and monitoring for new functionality in place and successfully exercised
  • Local Seed data up to date with latest changes (William 937 Update Seed Data #1463)
@JessicaMarine
Copy link
Author

JessicaMarine commented Mar 13, 2019

The format for each docket entry should be: [Title of Document] by [who filed it] [(Exhibit(s)) or (Attachment(s)), if applicable] [(Objection/No Objection)] [C/S date, if applicable]

Sample Docket Record.pdf

@tjcurington tjcurington added this to the Sprint #11 milestone Mar 20, 2019
@turnipsparkle turnipsparkle added the Design Needed Design work will be needed and development work should not start yet label Mar 28, 2019
@turnipsparkle
Copy link

Per Jessica, (LODGED) is appended to the end of the docket entry in which the file has been lodged (instead of filed).

Format: [Title of Document] by [who filed it] [(Exhibit(s))] [(Attachment(s))] [(Objection/No Objection)] [C/S date] [(LODGED)]

@klohman
Copy link

klohman commented Apr 18, 2019

Updated Docket Entry table and format

These changes applies to the docket record for all internal user views AND external users (petitioner, practitioner, respondent).

image.png

Style/Formatting

  • Docket record table is 500px height with vertical scrolling if entries exceed that height
  • Table border - ##D6D7D9;
  • Header label font - 17px, #212121, weight-600
  • Regular table font - 14px, #212121, weight- normal

Sequence Number

  • each new docket entry receives a sequential number in the record

Date

Event

Icon Column- No Label

Filings and Proceedings

  • Format for displaying filing:
    [Concatenated Document Title (C/S 04/17/2019) (Exhibit(s)) (Attachment(s)) (Objection) (Lodged)

  • Concatenated Document Title- full document name concatenated in Parties: Unique Doctype data requirements and doc name concatenation #980- displayed as link

    • For internal users, on click of link, navigate to Document Detail page
    • For external users, on click of link, open PDF document in new tab
  • C/S MM/DD/YYYY - Show ONLY if ‘yes’ to certificate of service question

  • Exhibits - Show ONLY if ‘yes’ to exhibits question

  • Attachments - Show ONLY if ‘yes’ to attachments question

  • Objection - Show ONLY if ‘yes’ to objections question

  • No Objection - Show Only if “no” to objection question

  • Lodged - Show ONLY for secondary documents and secondary supporting document

Filed By

  • Display the parties who filed the document
  • If filed by Petitioner- show Petr. [Primary Contact Name]
  • If filed by Respondent - show Resp.
  • If filed by both petitioner and respondent- show Resp. & Petr. [Primary Contact Name]
  • If filed by more than one petitioner (For party type Petitioner and Spouse and Petitioner and Deceased Spouse), show Petrs. [Primary Contact Name] [& Secondary Contact Name]

Action

  • TBD in later story

Served

  • Displays service date (TBD in later story)

Parties

  • Displays indicator of the parties being served (TBD in later story)
    • “P” - petitioner(s) only
    • “R” - respondent only
    • “B”- all parties

@klohman klohman added Ready for Engineering UX work is done and this story is ready for engineering. and removed Design Needed Design work will be needed and development work should not start yet labels Apr 18, 2019
@rachaelparris rachaelparris added Engineering Engineers have started working on this story. and removed Ready for Engineering UX work is done and this story is ready for engineering. labels Apr 19, 2019
wbyoko added a commit that referenced this issue Apr 19, 2019
#937 add number to docket record items
wbyoko added a commit that referenced this issue Apr 22, 2019
#937 add number to docket record items, include currentIndex
wbyoko added a commit that referenced this issue Apr 22, 2019
wbyoko added a commit that referenced this issue Apr 22, 2019
wbyoko added a commit that referenced this issue Apr 22, 2019
#937 display from assigned index
@klohman klohman removed the Engineering Engineers have started working on this story. label Apr 23, 2019
codyseibert pushed a commit that referenced this issue Mar 22, 2021
Remove old migrations that have already been run
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants