Revision of status attribute

[danieltruong]

Status in our current data model can either be "old" or "current". This needs to be updated to reflect our current understanding of protected area statuses. The following dictates how our the attribute status should function:

• If a given record has an SK of "Details", the record can have a status of "established". This is if the protected area is established.
• If a given record has an SK of "Details", the record can have a status of "repealed". This is if the protected area is repealed. A protected area in a repealed state is at a dead end. This means, no further changes can be performed and you are not able to add anything to the change log.
• If a given record has SK as a date, this implies that the status attribute is "historical". This can be overloaded in the future to track other types of changes to the protected area.

Acceptance Criteria

• Data importer is updated
• Endpoints that filter via status are updated
• Endpoints that add/edit protected areas are updated
• Attribute name type with value protectedarea exists on protected area objects in database
• Update DUP and A&R to use the new status attribute

Notes

This ticket is blocked by #138 and #26. Doing this change while these tickets are active would cause conflict.

This ticket blocks #28, #30, #27, #132 and #133 and also #59 . The attribute status is needed for these front ends to make sense. Updates to the front end service layer will be required once this ticket is done.

[cameronpettit]

Park Name GET endpoints will need to be updated to reflect the new statuses FYI

[JLWade]

@meredithom is #26 still blocking this ticket? Since our chats about the filters sounds like we may be able to move this one to to-do?

[manuji]

Tested on TEST env: Failed

• I am still getting records with sk set to "Details" with the status "current"

[manuji]

Tested on TEST using Postman and DynamoDB: Completed.

• Verified when sk equals to Details, the possible statuses are only "established" and "repealed"
• Verified when the sk equals to a date, the status is "Historical.
• Verified the PUT action for minor, major, and repeal updateTypes and confirmed that the statuses and the sk get updated accordingly.
• Verified that for a minor change, no new records get created in DynamoDB, but for repeal and major a new record get created.
• Verified that minor or major updates cannot be done on a record that has a status repealed.
• Verified that PUT action cannot be performed on records that do not exist in DynamoDB
• Verified the PUT action does not work if the updateType is not one of from minor, major or repealed.
• Verified that DUP get updated correctly.
• Issue with the A&R reported here -> https://github.com/bcgov/bcparks-ar-admin/issues/285
• Passing this to PO review.

[JLWade]

@cameronpettit can you add estimated story points to this one.

Moving to done