When string-based attributes (String, List, Set) are shown as key attributes, once discrete values are added to the attribute these are all shown via a pop-up list via the triangular icon at the right end of the attribute value edit box. For fast entry, autocompletion using matched list items is also possible. However, do bear in mind limitations on the length of and number of entries in these lists.
If the list of likely values is known in full (or part) before the main data is added to the document, it is easy to pre-populate the attributes value list via suggested box on the relevant Inspector for User and (some) System attributes.
Enter the list of values as a semi-colon delimited list without any enclosing quotes. To pre-populate an attribute with values 'Ant', 'Bee' and 'Cow' the unquoted string to enter into the Inspector's suggested box is Ant;Bee;Cow. A terminating semi-colon may be used but is not required. It can be helpful to prepare the list in another note if it is long and will extend beyond the visible portion of the suggested box.
If adding a list to a document that already has values, it may be useful to first test the new list in a new document to ensure the correct values show up in a key attribute pop-up. Indeed, this method does not prevent new values (not in the suggested list) being used. If trying to assert a fixed list of values and new values are seen in the pop-up list, note the new value(s) and use an agent to find and correct the notes with the unwanted values.
For post v6.4.0 use, or if updating pre-v6.4.0 documents, use the Inspector-based method described above. Otherwise consider the methods below. If the older method of seed notes is already in use, it it recommended to move their values to the Inspector (as above) and then delete the value seed note(s).
Below is for pre-v6.4.0 use only!
Use seed notes. The number required will depend on the type of attribute:
- Lists/Sets. To a single note, add every known value you wish to use. These will instantly be available to all other notes for use.
- Strings. As above, but because the strings are discrete per-note values, a note is needed for each 'seeded' value (unlike using one note for a List, etc.); thus a 20 value list would need 20 notes.
Pitfalls to avoid, when planning this sort of use:
- Consider placing the seed note(s) in a part of the document away from actual content.
- Make sure if counting notes using values in this attribute and the 'seed' note(s) are excluded. Another way to exclude them is to assign all such seed notes a prototype seed making it easy to apply a document wide filter (i.e.
$Prototype!="Seed") - If using action-based linking based on attribute values, again ensure these note(s) are excluded from the scope of queries.