What would _you_ call it?

[drwex]

Here's a quickie. I need a name for something. You're restricted to two relatively common words, though jargon is allowed. For now we'll call it $NAME

You have a number of values in a table. These values came from us, the software supplier, and from you, the customer. Periodically we'll give you an upgrade to your data, including replacement values for things in this table. We also give you a flag, $NAME. If $NAME is true/on/set then at the next upgrade whatever the associated data value is, it'll be overwritten by a new value we supply. If it's false/off/unset then the data will be preserved. If you set this flag on your own data it has no effect.

So the cases are:
1. Our data, flag set -> overwrite at upgrade time
2. Our data, flag unset -> leave alone at upgrade
3. Your data, flag any value -> leave alone at upgrade

So, dear readers, what would YOU call $NAME? (Remember you're limited to two words, and no German so upgradenflaggensetten is right out.) I'd tell you what we call it now but that would probably bias responses too much.

Comments

[ariesd.livejournal.com]

hmmmm, "UPDATE_TABLE" is short and to the point. Clear enough, is the length of the name in issue?

[drwex]

Yeah, except it's not the table that's being updated, it's the data value(s) shown in the form, which might be spread across multiple tables. So the effect of the checkbox applies to one or more rows in one or more tables, which might change with the next schema upgrade.

[ariesd.livejournal.com]

ah ok, I thought looking at it was still backend looking at it, not at the API level. I think the choice "Upgrade Allowed" is simple enough and user friendly.

So curious what the old name was that you couldn't have too long of a name w/o modifying the input boxes.

[drwex]

It's currently called "system lock"

[ariesd.livejournal.com]

yeah It could be improved. :)