Parties: Unique Doctype data requirements and doc name concatenation

[mariahkannenberg]

As a Petitioner, Practitioner and IRS Attorney, in order to provide unique supporting data for specific doc types, I need the ability to add specific data based upon which document I am uploading.

In certain circumstances, more document metadata is required for an external filing than in a typical filing. When specific data is required for an external filing, the user needs to be prompted to enter that data. For all of these special circumstances, the additional

https://docs.google.com/document/d/1vg6F3-mZzhfMfjyYgYz69JzVZZR6kTn4y3CdHxeF36k/edit?usp=sharing

Pre-Conditions

• Party has the need to upload a document for which the court requires specific doc-related data to be collected.

Acceptance Criteria

• Every document selection should have a title and related code.
• If a Nonstandard A document is selected (e.g. Opposition to", "Redacted," "Response to," "Reply to" and "Unredacted), the user is required to select which previously filed document they are filing the document for, AND the document name must concatenate the document type and the name of the previously filed document (e.g. Reply to Motion to Dismiss).
• If a Nonstandard B document is selected (e.g. Application to Take Deposition of [Name]), then the user is required to enter additional text AND the document name must concatenate the document type and the additional text (e.g. Application to Take Deposition of John Smith).
• If a Nonstandard C document is selected (e.g. Affidavit Of [Name ] in Support Of [Document Name]), then the user is required to enter additional text and to select which previously filed document they are filing for, AND the document name must concatenate the document type and additional text and previously filed document (e.g. Affidavit of John Smith in Support of Motion to Dismiss).
• If a Nonstandard D document is selected (e.g. "Certificate of Service") is selected, user must indicate which previously-filed document they are providing a certificate for and indicate a service date, AND the document name must concatenate the document type, previously filed document and date of service (e.g. Amended Certificate of Service of Motion for Continuance 03/30/2017)
• If a Nonstandard E document is selected (e.g., Motion to Change Place of Trial [place]), then the user is required to select a trial location applicable to their case procedure type, AND the document name must concatenate the document type and the trial location (e.g. Motion to Change Place of Trial Birmingham, AL)
• If a Nonstandard F document is selected (e.g.[First, Second, etc.] Amendment to [Document Name]) , then the user is required to select which ordinal number of the filing and to select which previously filed document this is for, AND the document name must concatenate the ordinal number and the document type and the previously filed document (e.g. Second Amendment to Motion to Dismiss).
• If a Nonstandard G document is selected (e.g. {First, Second, etc.] Stipulation of Facts), then the user is required to select the ordinal number of the filing AND the document name must concatenate the ordinal number and the document type (e.g. First Stipulation of Facts).
• If a Nonstandard H document (“Motion for Leave to File” or "Motion for Leave to File Out of Time") is selected, the user is required to select a secondary document for which they are requesting leave to file AND the document name must concatenate the document type and the secondary document name (e.g. Motion for Leave to File Motion to Dismiss)
• The secondary document name must concatenate using the same pattern as described above depending on the document scenario (e.g. Nonstandard A).

Notes

• Do we need to do anything with unique document codes? Referenced on pg. 55 and 84. Yes, for internal users only. Parties don’t need to know the codes. However, we need to tie the codes to the doctypes when we load them into the database.
• Do we need to do anything with e-Lodging? Referenced in "Motion for leave to file" section of the e-guide. Yes, Docket felt this was important to maintain. Jessica met with Designers in DC to go over this in detail
• Are there any other situations where we should be adding text to a document name that’s not part of the original doc type data or data fields? Possibly, but maybe the example in efiling doc was incorrect
• When users selects the name of a previously filed document, is there any limit to what the user can select? Yes, Only documents that have already been filed in the case
• When users selects the name of a previously filed document, are they referring to a list of doc types or are they referring to a list of documents that were actually filed? Same answer as above
• Are there any situations when we concatenate a document name that we’re not using the actual name from the dropdown or from a field?
• Are the doc types listed in the e-filing guide the actual doc types in the list? For example Supplemental and Supplements To, are those actual doc types? Not necessarily. Still need to identify the actual doctype that will trigger the logic
• Other than the unique naming conventions above, are there any other doctypes that require special naming conventions?
• For documents that reference a previously filed document, is there any hierarchical relationships between the two documents (other than the name)? No, it appears as just another docket entry

Tasks

• Design scenario for selecting a secondary document and secondary supporting documents for appropriate documents
• Design scenario for selecting document ordinal (first, second, third) for appropriate documents
• Code: Tweak the script that generates externalFilingEvents.json (kris, 980: update field names to use all camelCase #1317 )
• Code: GenerateDocumentTitle use case, using externalFilingEvents.json (kris 980: generate filing document titles #1320)
• Code: Comprehensive tests for document scenario options
• Code: Create React views for each of the document scenarios and load them when their respective document types are selected (Rachael 980: initial UI work #1321, 980: file document computed tests; remove STIN from prev docs #1327)
• Code: Create Entities / UseCases / Actions / Sequences for validation (William 980 External Document Factory/Validation #1319)
• Code: Create Actions / Sequences for title generation (William 980 E2E Taxpayer Files Document / Generate Title #1332)
• Code: Show Nonstandard view again if secondary doc type is a nonstandard scenario (Rachael 980: add secondary nonstandard form to UI  #1329)
• Code: Create React view for File a Document form with read-only document title (also probably should rename old FileDocument view to something else) (kris 980 Views #1339)
• Code: E2E Journey Test (William, Rachael 980 E2E Taxpayer Files Document / Generate Title #1332)
• Code: Remove Nonstandard H documents from secondary document dropdown (Rachael 980: remove Nonstandard H documents from secondary document type dropdown #1338)
• Code: Integrate view code with Sequences (William 980 UI Integration #1343)
• Code: Clear properties when editing or category/type is selected.

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

[klohman]

@JessicaMarine @mariahkannenberg

Proposed Updated Acceptance Criteria

• If a Nonstandard A document is selected (e.g. Opposition to", "Redacted," "Response to," "Reply to" and "Unredacted), the user is required to select which previously filed document they are filing the document for, AND the document name must concatenate the document type and the name of the previously filed document (e.g. Reply to Motion to Dismiss).
• If a Nonstandard B document is selected (e.g. Application to Take Deposition of [Name]), then the user is required to enter additional text AND the document name must concatenate the document type and the additional text (e.g. Application to Take Deposition of John Smith).
• If a Nonstandard C document is selected (e.g. Affidavit Of [Name ] in Support Of [Document Name]), then the user is required to enter additional text and to select which previously filed document they are filing for, AND the document name must concatenate the document type and additional text and previously filed document (e.g. Affidavit of John Smith in Support of Motion to Dismiss).
• If a Nonstandard D document is selected (e.g. "Certificate of Service") is selected, user must indicate which previously-filed document they are providing a certificate for and indicate a service date, AND the document name must concatenate the document type, previously filed document and date of service (e.g. Amended Certificate of Service of Motion for Continuance 03/30/2017)
• If a Nonstandard E document is selected (e.g., Motion to Change Place of Trial [place]), then the user is required to select a trial location applicable to their case procedure type, AND the document name must concatenate the document type and the trial location (e.g. Motion to Change Place of Trial Birmingham, AL)
• If a Nonstandard F document is selected (e.g.[First, Second, etc.] Amendment to [Document Name]) , then the user is required to select which ordinal number of the filing and to select which previously filed document this is for, AND the document name must concatenate the ordinal number and the document type and the previously filed document (e.g. Second Amendment to Motion to Dismiss).
• If a Nonstandard G document is selected (e.g. {First, Second, etc.] Stipulation of Facts), then the user is required to select the ordinal number of the filing AND the document name must concatenate the ordinal number and the document type (e.g. First Stipulation of Facts).
• If “Motion for Leave to File” or "Motion for Leave to File Out of Time" is selected, the user is required to select a secondary document for which they are requesting leave to file AND the document name must concatenate the document type and the secondary document name (e.g. Motion for Leave to File Motion to Dismiss)
• The secondary document name must concatenate using the same pattern as described above depending on the document scenario (e.g. Nonstandard A).
The secondary document must display on the docket record as "LODGED"

[klohman]

Once a primary document type is selected from the Document Type dropdown, the additional required field (if any) for the selected document type will display.

The required fields displayed are dependent on the selected document type- below are the possible scenarios.

Standard

• On select of a Standard document type, the "Continue" button is shown.
• On click of "Continue" button, display the File a Document form page

Nonstandard A

• If Nonstandard A document type is selected, show the Dropdown field- Previous Document from record
• Dropdown field is required
  • Dropdown is populated with all previously filed documents in the case docket record
  • See GoogleSheet for the dropdown field label text for each document type
• On select of previous document from Dropdown, show the "Continue" button
• Concatenated title should read "Document type [previous filed document name]"

Nonstandard B

• If Nonstandard B document type is selected, show Text Field
• Text field is required
  • See GoogleSheet for the text field label text for each document type
• If text is entered in Text field, show "Continue" button
• Concatenated document name will be "Document Type [text field]"
  • Insert text field in the appropriate place - shown in document type title

Nonstandard C

• If Nonstandard C document type is selected, show Text Field and Dropdown field
• Text field is required
  * See GoogleSheet for the text field label text for each document type
• Dropdown field is required
  * Dropdown is populated with all previously filed documents in the case docket record
  * See GoogleSheet for the dropdown field label text for each document type
• If text is entered in Text Field and document has been selected from Dropdown, show "Continue" button
• Concatenated document name should read "Document Type [text field] [previously filed document name] with text field inserted in the appropriate place - shown in document type title

Nonstandard D

• If Nonstandard D document type is selected, show Dropdown field and Date field
• Dropdown field is required
○ Dropdown is populated with all previously filed documents in the case docket record
○ See GoogleSheet for the dropdown field label text for each document type
• Date Field is required
○ Date validation should follow our standard validation rules (format, not in future)

• If document is selected from Dropdown field AND valid date is entered in Date field, show "Continue button"
• Concatenated document name should ready " Document Type [previously filed Document Name] [date]

Nonstandard E

• If Nonstandard E document type is selected, show Requested Trial Location dropdown
• Dropdown field is required
○ Dropdown is populated with the list of trial locations based on case procedure type (small or regular)

• If location is selected from dropdown, show "Continue" button
• Concatenated document name should read "Document Type [trial location]"

Nonstandard F

• If Nonstandard F document type is selected, show Dropdown field and Ordinal field
• Dropdown field is required
○ Dropdown is populated with all previously filed documents in the case docket record
○ See GoogleSheet for the dropdown field label text for each document type
• Radio set field is required

• If document is selected from dropdown AND ordinal is selected, show "Continue" button
• Concatenated document name should read "[Ordinal Number] Document Type [previously filed document name]"

Nonstandard G

• If Nonstandard G document type is selected, show Ordinal field
• Ordinal field is required

• if Ordinal radio is selected, show "Continue" button
• Concatenated document name should read "[Ordinal Number] Document Type"

Nonstandard H

• If Nonstandard H document type is selected, show secondary document category field and document type field and secondary "Select" button

• secondary Document Category field and document type field is required

• Document Type field is populated with documents within the selected category
  • "Motion for Leave to File" and "Motion for Leave to File Out of Time" should not be selectable as a secondary document
  • The required fields for the secondary document should follow the same pattern as described above for Nonstandard Documents.

• on click of secondary select, show "Read only" view displaying both primary and secondary documents

File a Document Form

On click of "Continue" button, open the File a Document Form, with selected document name displayed read-only

• on click of Edit link, return user to the File a Document page (previous page)

[rachaelparris]

Adding this Event Codes doc link here because I keep losing it. I don't see it anywhere else on this story. Useful for reference.
https://docs.google.com/spreadsheets/d/1RYGSnHJDP8_sg8aFjPQb_BAji-TQjKlTq2yTebLV7R4/edit?usp=sharing

[JessicaMarine]

QA comments:
(1) for Miscellanous/Amended Certificate of Service -- it should follow the same pattern for Non-Std D and have a date field;
(2) I can't really test this out, but I want to be clear that, if someone picks Miscellaneous and then Amended, whatever document they pick next to amend needs to follow the same logic as is programmed for the document if it was a stand-alone
(3) Motion to Withdraw Counsel (filed by petitioner) -- the "filed by petitioner" language is really meant to be helper text and should not concatenate into the title