[likely late Y7/Y8] Consider how HTAN 1.0 vs 2.0 data are displayed in the portal

[aclayton555]

This ticket emerges during the closure of our final HTAN data model sprint in HTAN 1.0 in September 2024 (https://github.com/orgs/ncihtan/projects/4?pane=issue&itemId=74531931). Going into HTAN 2.0, we know that there will be changes to the data model, which will have an expected impact on how users engage with data on the HTAN Data Portal.

Considerations:

• The HTAN DCC will likely be partitioning HTAN 1.0 data from HTAN 2.0 data from an infrastructure perspective. HTAN 2.0 data will be submitted under a new, evolved data model. The curation effort of transforming HTAN 1.0 data to an HTAN 2.0 data model is likely out of scope, but we should understand how we map data between project phases
• From an HTAN Data Portal user perspective (especially non-HTAN community members), they will likely engage with the portal as "HTAN data," and not consider the different phases of the project.
• The portal already can display columns across different data types in the File explorer. So there is flexibility here if both HTAN 1.0 and 2.0 data are displayed (there would likely be several blank columns)

Suggested approach [to be part of data model design in Q4 2024, but may not be fully informed until 2025 as HTAN 2.0 data start to come in]:

• Opportunity for us to think about a minimal attributes that map across phase 1.0 and 2.0, and/or think about how we flag 1.0 vs 2.0 data. Nothing will break the portal immediately, but this will get complicated if we implement a more granular hierarchal structure. Based on the data types we are starting to expect in phase 2.0, a hierarchal model may be needed to adequately capture the complexities and contextual information (while balancing minimal elements and low barrier to entry). Take this into consideration in design doc planning.