Currently departments, colleges, campuses, programs, and schools are hard coded in the database. This worked well for the need when the app was created, but since then we have had many changes, and now we have to unweed all of that. I believe that we need to simplify this area to store the item as a varchar not as id's and lookup tables. This will allow for more flexibility and will future proof that part of the app. The goal would be to match the taxonomy being set up where it is pulled in (maybe as a one a day update to some tmp table?) and we just parse out by the unit types and stored as fulltext. This should be future proof as the look up would be based on the alias of the item in the feed and presented as the official name where needed. It could just be meta data for the place/shape/map view as well.
This is just one quickly thought out solution, but the end need is to correct the fact that the departments, colleges, campuses, programs, and schools are all slightly off, along with the campuses.
Currently departments, colleges, campuses, programs, and schools are hard coded in the database. This worked well for the need when the app was created, but since then we have had many changes, and now we have to unweed all of that. I believe that we need to simplify this area to store the item as a
varcharnot as id's and lookup tables. This will allow for more flexibility and will future proof that part of the app. The goal would be to match the taxonomy being set up where it is pulled in (maybe as a one a day update to some tmp table?) and we just parse out by the unit types and stored asfulltext. This should be future proof as the look up would be based on the alias of the item in the feed and presented as the official name where needed. It could just be meta data for the place/shape/map view as well.This is just one quickly thought out solution, but the end need is to correct the fact that the departments, colleges, campuses, programs, and schools are all slightly off, along with the campuses.