You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
documenting for future reference; no action needed
some QA lookups are expressed as search boxes; some are dropdown lists.
if you try to use both kinds in one field, there are unexpected results.
example of a field configured to have authorities "illustrative content" (dropdown) and "Geonames Area" (usually a search). with both of these in the same field, Geonames Area appears in the dropdown as the name of an authority but with nothing listed (as expected since it would be too long to list out)
another experiment was to include the same two authorities but reverse the order, so that in template configuration, the searchable authority is listed first. now both authorities show as searchable, but when trying to see the results for the "dropdown-style" authority, you get an error message:
yes, it may be unlikely that a template creator would mix and match these, but in case it comes up it is now documented.
The text was updated successfully, but these errors were encountered:
documenting for future reference; no action needed
some QA lookups are expressed as search boxes; some are dropdown lists.
if you try to use both kinds in one field, there are unexpected results.
example of a field configured to have authorities "illustrative content" (dropdown) and "Geonames Area" (usually a search). with both of these in the same field, Geonames Area appears in the dropdown as the name of an authority but with nothing listed (as expected since it would be too long to list out)
another experiment was to include the same two authorities but reverse the order, so that in template configuration, the searchable authority is listed first. now both authorities show as searchable, but when trying to see the results for the "dropdown-style" authority, you get an error message:
yes, it may be unlikely that a template creator would mix and match these, but in case it comes up it is now documented.
The text was updated successfully, but these errors were encountered: