In CRUD-like applications, you often have tables that contain very few records, and only exist to assign a name to an id value (they have a one-to-many or many-to-many relationship to the "primary" data).
For example, if your application shows real estate listings, you'd have a primary table for the houses being sold, and maybe another table for various "attributes" that could be assigned to the listing (e.g. "gas", "sewer", "zoned for commercial"). Then there could be a many-to-many relationship between the houses and the attributes.
In the admin interface (for people who manage the data -- not the end-users who are viewing it), admin users can add new houses to the listing and choose from the available list of attributes that apply to the new house.
But... there is also tucked away somewhere, a "master list" of those attributes -- which is how the UI for the "add new house" admin screen populates the available choices. This is not changed too often, so I like to put it out of the way. And I like to put all of these lists in one place (because there's often more than one of them).
My question is: what is a good general term for these kinds of things? The best I can think of is "Option Lists"... but I wonder if there's something more intuitive to non-technical users.