I’m planning to track store locations in Busabase, and several stores may belong to the same brand. Using only the brand name could make it easy to link the wrong store, but very long names would be difficult to read. What is a practical naming convention? Which details—store code, city, or address—should be included in the record name, and which should stay in separate fields?
How should I name records so similar entries are easy to distinguish when linking?

Use a short, stable store code plus the location detail people recognize. For example, Northstar · TPE-017 · Xinyi is easier to choose than three records all named Northstar, and easier to scan than a full street address. In Busabase, the linked-record picker shows and searches the target Base's primary display field, so put the distinguishing part there.
Keep Brand, Store Code, City or District, and full Address in separate fields too. The display name helps a person select the right record; the store code is the identifier to check for duplicates and imports. Avoid using only a changeable name, and do not put private contact details into the display name. When two locations still look alike, open the record and verify its address before linking it.
If you already have a store code used in another system, reuse it. Otherwise, agree on one code format and test it with a few same-brand locations before renaming the whole Base. Are your store codes unique across all brands, or only within each brand?
Your reply
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in