OI redaction layer
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
* As an IAO analyst
* I want to be able to create new OI Redaction layer
* so that I can preserve the original severing
* and create a new layer to edit for managing for OI publication
**Assumptions & Scope**
What are the assumptions for this story?
OI layer can only be created once the request is in the 'Publication Review' state. See workflow: https://miro.com/app/board/uXjVNTzDPuw=/
The redline layer will be the default and will automatically be created when records are loaded into the Records Log.
Analysts will create a new layer in the menu; new layers will be based on the redaction layer.
Analysts will choose the layer from a pick list: OIPC, OI
It is possible that analysts will have more than one OIPC and OI layer and both versions will need to be retained. For example, the analyst shares a layer with OIPC and later creates and shares a new layer with OIPC.
Analysts will be able to switch between layers.
What is IN scope?
Creating/changing an OI layer
What is NOT in scope?
OIPC layers #4191
Saving the layers as PDFs are covered in, #3437, #3231.
Toggling between the Redline and Response layers, #3704.
Creating and togging between Harms and Sign Off will be in a future story
**Scenario 1: OI Layer on Redaction Layer dropdown**
* GIVEN an IAO analyst is in the Records Review app
* AND the request state is 'Publication Review'
* WHEN the analyst clicks the Redaction Layer dropdown
* THEN dropdown will open with these options in this order: Redline, Response Package, OIPC, OI
* AND the Redline layer will have no (+) as the layer is created by default
* AND the Response Package layer will have a (+)
* AND the OIPC will have a (+)
* AND the OI will have a (+)
https://jacklyn808742.invisionapp.com/console/Redaction-cla8feezv003o015h7op82c5c/cleg4xqe55wt3018ba31e3cvi/play
**Scenario 2 - Create OI Layer - Modal**
* GIVEN an IAO analyst is in the Redaction Layer dropdown
* WHEN the analyst clicks the (+) next to OI
* THEN a modal will pop up asking the user if they are sure they want to create an OI Review layer
* AND they will have the options to 'Continue' and 'Cancel'
**Scenario 3: Create OI Layer - Cancel**
* GIVEN an IAO analyst has clicked the + next to OI
* WHEN the analyst clicks Cancel in the Modal
* THEN the modal will close
* AND they will be returned to the redaction app
**Scenario 4: Create OI Layer - Continue**
* GIVEN an IAO analyst is in the Redaction Layer dropdown
* AND the OI layer has NOT been previously created
* WHEN the analyst clicks the (+) next to OI
* THEN the OI layer will now be shown and be editable in the Records Review app
* AND all comments and annotations from the redline will be included
* AND all redactions (i.e. redlines) will be applied as white blocks with the section stamp(s)
* AND all pages that are flagged Duplicate or Not Responsive will be removed
* AND all other page flags will be retained
* AND the New Layer can be filtered by the retained page flags (e.g. Partial Disclosure, Withheld in Full, Consults, etc.)
* AND the OI layer will still have a (+) in the Records Package Dropdown
**Scenario 5: Create another OI layer**
* GIVEN an IAO analyst is in the Redaction Layer dropdown
* AND the OI layer has been previously created
* WHEN the analyst clicks the (+) next to OI
* THEN the OI layer - Version 2 - will now be shown and be editable in the Records Review app
* AND all comments and annotations from the redline will be included
* AND all redactions (i.e. redlines) will be applied as white blocks with the section stamp(s)
* AND all pages that are flagged Duplicate or Not Responsive will be removed
* AND all other page flags will be retained
* AND the New Layer can be filtered by the retained page flags (e.g. Partial Disclosure, Withheld in Full, etc.)
* AND the OI layer will still have a (+) in the Records Package Dropdown
**Scenario 6: Click active OI in Redaction Layer dropdown**
* GIVEN an IAO analyst has opened the Redaction Layer dropdown
* AND the analyst is not on the OI layer
* AND a OI Layer has been created
* WHEN the analyst clicks 'OI' in the Redaction Layer dropdown
* THEN the OI layer will be displayed in the Records Review app
**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**
**Validation Rules? (If yes, list here)**
**Design**
@xxx - please link the Design here
**Definition of Ready**
1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?
**Definition of Done**
1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?
Contributor guide
Research direction
Start in the Records Review app by tracing the existing Redaction Layer dropdown and the workflow for creating and switching layers. Review the linked exclusions and existing layer behavior before mapping the OI scenarios. Done means the dropdown, confirmation modal, versioned OI layers, retained annotations and page flags, and layer switching satisfy the listed acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100