Bridge Expansion for SDPR API

[CarlyCotton]

User Story
As a system, SIMS needs to be able to provide up to seven years of application data. This will include SFAS information and we need to include that in the current SFAS to SIMS bridge file.

Acceptance Criteria

• SFAS to SIMS Bridge V2.3 DRAFT

• New Record Types:

  • SFAS Applicant Dependant (302)
    • Unique Dependant Key
    • Unique Application Key
    • Dependent Name
    • Date of Birth
  • SFAS Disbursement Data (303)
    • Unique Disbursement Key
    • Unique Application Key
    • Funding type/Program code
    • Funding Amount
    • Funding Date
    • Date Issued

• Additional Fields for Individual Records (200) at end of record

  • Initials
  • Address Line 1
  • Address Line 2
  • City
  • Province or State
  • Country
  • Phone Number
  • Postal or Zip Code
  • LMPT Award Amt
  • LMPU Award Amt

• Additional Fields for Application Records (300) at end of record

  • Application No.
  • Living Arrangements
  • Marital Information
  • Date of Union
  • BC Residency flag
  • Permanent Residency flag
  • Gross Income for previous year
  • Institution Code
  • Status Code
  • Education Period Weeks
  • Course Load
  • Assessed Costs – Living Allowance
  • Assessed Costs – Extra Shelter
  • Assessed Costs – child care
  • Assessed Costs – Alimony
  • Assessed Costs – Local Trans
  • Assessed Costs – Return Trans
  • Assessed Costs – Tuition
  • Assessed Costs – Book/Supplies
  • Assessed Costs – Exceptional
  • Assessed Costs – other
  • Assessed Costs – discretionary
  • Withdrawal Date
  • Withdrawal Reason
  • Withdrawal Active Flag

Technical
Note: Currently for SFAS data import, every record type except header has a sims table where it is imported into.

• The extension to the bridge must be implemented with backward compatibility. i.e. if none of the new records(record types) or new fields are missing in the sfas file, still the import must be happening in the same way as it happens today.
• DB Migration to create new tables for record type 302 and 303. Table names could be sims.sfas_application_dependents(302) and sims.sfas_application_disbursements(303) and the related models.
• DB migrations to add new columns to sims.sfas_individuals and sims.sfas_applications the related models. All the new fields must be nullable ensuring the backward compatibility.
• Adapting the framework, create data-importers and related objects for new record types.
• E2E Tests
  • E2E test for extended bridge.
  • Ensure the existing E2E tests are not breaking ensuring the backward compatibility.

[CarlyCotton]

@dheepak-aot Updated the file link and the ACs to show that SAIL app data records wont be changing and dependant data (302) / disbursement data (303) are now different.

[dheepak-aot]

@CarlyCotton for the new record types, SFAS Applicant Dependant and SFAS Disbursement Data we must have it's own unique identifier to identify that particular record.

[CarlyCotton]

@dheepak-aot Updated the ACs and attached the new V2.3 doc with unique keys.

[dheepak-aot]

@ninosamson @CarlyCotton Bulk file from SFAS has been successfully imported in DEV(Please remember that all 9999999 were replaced by 0999999 in the file to ensure money values are not having junk data).

Values loaded into new fields: