Remove deprecated Tag references

[avaidyam]

The following Tag keys should be removed from LAMP-dashboard. We have already discussed the migration strategy for all of these (if applicable). We will need to ensure that data can be migrated for teams who have already deployed a previous version of LAMP (server or dashboard).

• [ ] to.unityhealth.psychiatry.settings
• [ ] to.unityhealth.psychiatry.enabled
• [ ] lamp.dashboard.activity_details
• [ ] lamp.dashboard.survey_description
• [ ] lamp.name
• [ ] lamp.dashboard.welcome_dismissed
• [ ] lamp.dashboard.custom_survey_groups
• [ ] lamp.dashboard._nancy
• [ ] lamp.goals
• [ ] lamp.feed.goals
• [ ] lamp.medications
• [ ] lamp.feed.medications
• [ ] lamp.selectedActivities
• [ ] lamp.selectedSensors
• [ ] lamp.selectedStudies

---

Furthermore, many of the existing Tags can be consolidated into a single lamp.dashboard.settings Tag, as initially shared in #262:

"lamp.dashboard.settings": {
    "conversations": false,
    "prevent": true,
    "streaks": [
        "<activity_id_here>": true,
        "<activity_id_here>": false,
    ]
}

Other tags we should consider consolidating or baking into the API proper are:

• [ ] lamp.dashboard.credential_roles/.external
• [ ] lamp.dashboard.admin_permissions
• [ ] lamp.dashboard.user_type
• [ ] lamp.messaging
• [ ] lamp.automation
• [ ] lamp.dashboard.hidden_events (this may still be required by MAPNET/EPINET so it is not in the above list)
• [ ] lamp.dashboard.experimental.* (this is a prefix multiple tags)
• [ ] lamp.participant.timezone

[sarithapillai8]

@avaidyam Could you share the data format for converting the following?

lamp.dashboard.activity_details
lamp.dashboard.survey_description
to.unityhealth.psychiatry.settings
lamp.name

lamp.dashboard.activity_details/lamp.dashboard.survey_description - this one recently included streak customization data also. Also the activity icon and descriptions are part of these.

• The other 2 tags are also part of the repo. So I am not sure if these are deprecated ones.

[avaidyam]

Let's put this issue on hold for now as we need to iron out the migration strategy first.

EDIT: Another location that these Tag references need to be removed from and optimized in is this LAMP.API.Query call. as indicated in #495.