UCSF asked us to order our sidebar subcategories by a defined order that they sent us. Our CategoryRelationship table has a "child_priority_rank" field that I set for the child categories returned by our Ucsf-ipv parent category. I then use this order to sort the categories returned by Algolia.
This PR also removes some of the static eligibilities from the IPV constant eligibility list defined on the f/e. These eligibilities are not used for now. Speaking of which, maybe we should create a CategoryEligibility table similar to the CategoryRelationship table that will allow us to define eligibilities to be associated with a given parent category in the DB.
UCSF asked us to order our sidebar subcategories by a defined order that they sent us. Our CategoryRelationship table has a "child_priority_rank" field that I set for the child categories returned by our
Ucsf-ipvparent category. I then use this order to sort the categories returned by Algolia.This PR also removes some of the static eligibilities from the IPV constant eligibility list defined on the f/e. These eligibilities are not used for now. Speaking of which, maybe we should create a CategoryEligibility table similar to the CategoryRelationship table that will allow us to define eligibilities to be associated with a given parent category in the DB.