And while we're on the subject of confusing terminology (see #610054: Confusing terminology: Automatic vs. Manual), I'm not sure why the decision was made to rename "Foreign key" to "Available key". IMO, we can assume some level of database familiarity with the users of this module, so you should call this what you mean. Even the column is called "availablefk." :)

Can we please stick "Foreign" in the name somewhere so it's obvious what you're being asked to identify here?

Comments

moshe weitzman’s picture

moshe weitzman commented

The word available is useful in conveying that more stuff becomes available to you use in Views. You get more relationships/tables available when composing the view. I have no strong opinion about whats the better terms.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

As mentioned in #610054: Confusing terminology: Automatic vs. Manual, we can't count on Table Wizard users being database-literate. That being said, throwing the phrase "foreign key" in there somewhere will allow the db-literate to instantly understand what's going on...

Any thoughts for better terminology for the non-db-literate? The word "key" isn't really meaningful to them anyway...

Thanks.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

P.S. Only the db-literate will notice that the column is named "availablefk":-).

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Hmmm... I guess what we really want to convey here is, "Make this column available to use when forming relationships." Too bad that table header can't be 50 feet wide. ;)

I'll give it some thought. It might also be too that some strategic application of contextual Advanced Help could solve this for all parties.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Fixed

Header renamed to "Foreign key".

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.