We often segment our data by using the campus field in the Education Relationship record. However, this is not currently a table which makes it very difficult to query allows too much room for human error (typos, variant spellings/formats etc).
I wholeheartedly agree...currently this is setup where you can base the field on a lookup table (for data consistency), but this would work much smoother if the field could appear as a drop-down in data entry, queries, and exports.
It seems like an easy "fix" to make campus a table. Right now you can't even globally change a campus name. What happens when a college renames a campus after a benefactor? Are we supposed to change the campus names oneecord at a time?
Ditto to Lance's comment!
I wholeheartedly agree...currently this is setup where you can base the field on a lookup table (for data consistency), but this would work much smoother if the field could appear as a drop-down in data entry, queries, and exports.
It seems like an easy "fix" to make campus a table. Right now you can't even globally change a campus name. What happens when a college renames a campus after a benefactor? Are we supposed to change the campus names oneecord at a time?