[M] Spike: How to connect A&R to Park Name Data Register

[JLWade]

This ticket is to determine how to connect A&R and the data register and to develop an approach that covers all areas of A&R that may be affected.

Acceptance Criteria:

• Investigate where Park name is used and where it will be affected in A&R by connecting to an external api/the data register (ie. AR admin, exported reports, admin, keycloak)
• Document approach for how connect in bcgov/bcparks-ar-api#233

Notes

• Use bcgov/parks-data-register#97 for reference

[marklise]

• Records for each subarea and activity will need to be updated.

  {
  "pk": "0673::Backcountry Cabins",
  "sk": "201702",
  "activity": "Backcountry Cabins",
  "date": "201702",
  "isLegacy": true,
  "isLocked": true,
  "lastUpdated": "2023-04-04T21:32:34.317Z",
  "legacyData": {
  "legacy_backcountryCabinsNetRevenue": 0,
  "legacy_backcountryCabinsTotalAttendancePeople": 0
  },
  "orcs": "0116",
  "parkName": "Plumper Cove Marine Park",
  "subAreaId": "0673"
  }

• Records for each park will need to be updated:

  {
  "pk": "park::0363",
  "sk": "0189",
  "activities": {
      "wrapperName": "Set",
      "values": [
          "Backcountry Camping",
          "Day Use"
      ],
      "type": "String"
  },
  "bundle": "Sea-to-Sky",
  "managementArea": "Pemberton",
  "orcs": "0363",
  "parkName": "Joffre Lakes Park",
  "region": "South Coast",
  "roles": [
      "sysadmin",
      "0363:0189"
  ],
  "section": "Sea to Sky",
  "subAreaName": "Joffre Lakes"
  }

• Config records also need updating:

  {
  "pk": "config::0327",
  "sk": "Frontcountry Camping",
  "attendanceModifier": 3.2,
  "orcs": "0314",
  "parkName": "Porteau Cove Park",
  "subAreaId": "0327",
  "subAreaName": "Porteau Cove Walk-in"
  }

We will want to create an index against orcs/pk/sk in order to efficiently target the specific park name change. Otherwise table scan will get very expensive/slow. Index should target pk: orcs, no sk and atttribute parkName in the projection. The NoSQL Workbench file should be created/updated accordingly to show the index.

Nightly cronjob should pull details from the data register, and store that in a new table in order to determine if updates are required, and to which parks. Coupling this with the index in previous step will ensure fast and efficient updates.