Data Migration

Description:

• Short Description of the needed Epic in the below format

• As an IAO analyst
• I want to be able to search for historical requests
• so that I can compare similar requests, see and applicants request history, or respond to an investigation.

• What are the most critical features being built as part of this Epic

• Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.

• The legacy system must be decommissioned to save costs on data storage and backups

• Historical request details for every request are already stored in the new data warehouse for reporting in Redash

• Historical request documents, including from the correspondence log and document management, has not be migrated from AXIS data storage (i.e., KINDLING)

• Historical requests with all related documentation are required to be retained for 5 years

• The majority of documents stored in KINDLING were created in the past 5 years

• Historical request documents will be migrated and stored in Object Storage

• FOI Flow has a transactional relational database; migrating all the historical requests into the Flow DBs will slow the app performance

• FOI Reporting (i.e., Redash) as non-relational database; a high number of requests will not impact the app performance

• Strategy is to archive historical requests after a certain date (e.g. 12 months old??); these requests will be searchable from Redash

• Archived request documents will be downloadable from Redash

• Non archived requests (i.e. closed within the past 12 months?) will be searchable from the Flow app

• Non archived request documents will be downloadable from the Flow app

• Documents migrated from KINDLING into the Flow and app will be accessible in the Attachment Log for the request and tagged so that only IAO can access the documents

• New customization will be required in Redash for IAO user only to access documentation from archived requests.

Sizing

• T-shirt size:

[ ] S
[ ] M
[ ] L
[ ] XL

(S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints).

• Risks and Assumptions*

1. What are assumptions?
2. What are the risks?
3. Have we done an RFC on a technical approach?
4. Are the dependencies (technical, business, regulatory/policy) known?
5. Has work on this Epic been prioritized with key stakeholders?

No files, tests, or implementation entry points are named. Start by reviewing the Flow app, Redash, KINDLING, the data warehouse, and Object Storage responsibilities, then resolve the missing technical approach, dependencies, risks, retention rules, and access requirements. Done means an agreed migration design and scoped implementation work.