Section 7: Ancestral Remains - Data cleanup and ETL - Details View

1. This ticket specifies the rules to populate the data into each column/field:
- Type, Status, Remarks, Multiple Burials, Minimum # of Individuals, Repository, Restricted Ancestral Remains Remarks, Entered On, Entered By

2. Link to the Spreadsheet to refer to the field types- [@BCAP Tabular Data Fields](https://bcgov.sharepoint.com/:x:/r/teams/06659/Shared%20Documents/BCAP%20Shared%20Team%20Files/Build%20Requirements/Arch%20Branch%20working%20documents/@BCAP%20Tabular%20Data%20Fields.xlsx?d=w589e9d01689846afa44036784c156137&csf=1&web=1&e=UtBiw6)

3. Additional Notes from SMEs:
a. For HRIA Ancestral Remains data coming from TFM_ANCESTRAL_REMAINS (second row in this mockup table):
- Migrate all rows from TFM_ANCESTRAL_REMAINS.
- There is no “TYPE” field in TFM_ANCESTRAL_REMAINS. In BCAP, populate “Type” field with the HRIA data’s associated Site Typology (TFM_TYPOLOGY) Descriptor (SITETYPEDESCRIPTOR), but only if the Descriptor matches a picklist value from the BCAP “Type” field picklist (see spreadsheet - picklists tab).
- If the associated Descriptor doesn’t match a picklist value, then populate ‘Type’ field with “Other”.

Start by locating the existing Ancestral Remains ETL and Details View, then compare their field handling with the BCAP Tabular Data Fields spreadsheet and its picklists tab. Trace TFM_ANCESTRAL_REMAINS and the associated TFM_TYPOLOGY descriptor mapping. Done means the listed fields are populated and unmatched descriptors produce “Other” as specified.

Written by the indexing model from the issue text.