Follow up for #1801304-313: Add Entity reference field Task C

Problem/Motivation

Click it and get a modal. in Modal, still autocomplete widget message problem. Still says search fields. I don't really understand what "Search field" means. It seems to think I know more about how this is implemented under the hood than I currently do. Can you explain this, and we can try and come up with a better word?

Proposed resolution

Correct "autocomplete" wording.
Also, come up with better word for Search fields.

Remaining tasks

Discuss wording options.

User interface changes

No UI pattern changes.

API changes

No API changes expected.

Original report by @webchick

#1801304-199: Add Entity reference field 9.

FEEDBACK:
(minor) This is not an autocomplete widget; it's a select list. So the description is incorrect.

I don't really understand what "Search field" means. It seems to think I know more about how this is implemented under the hood than I currently do. Can you explain this, and we can try and come up with a better word?

Comments

swentel’s picture

Component: field system » entity_reference.module

Moving to right component

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jibran’s picture

Component: entity_reference.module » entity system
Issue summary: View changes

Moving to right component

tkoleary’s picture

@jonathanshaw (commented in a duplicate issue)

They control what fields on the entity are queried to match the entered text. See drupal/core/modules/views/src/Plugin/views/display/EntityReference.php ->query() for how they are used.

Currently no settings on the view affect what is displayed in the autocomplete (it's hardcoded to show only label), but this is fixed by #2174633: View output is not used for autocomplete display.

Either way the label is completely opaque, as is the descriptive text:

Select the field(s) that will be searched when using the autocomplete widget.

The concepts it needs to convey are:

  1. The setting controls the scope of the data that is queried
  2. The purpose of the setting is to exclude data that is not relevant
  3. The data queried is the contents of fields on entities already created by others
  4. The person filling in the field will be the author of the content
  5. The results of the query are shown as the author types

Proposed text:

[Label]
Narrow autocomplete results to specific fields

[description]
As the author types the system will show matching results from within existing content. Select fields from the entity type that are likely to contain information that will help the user identify the piece of content.

This wording does a few things:

  1. It puts the purpose (narrowing results) over the action (searching fields).
  2. It disambiguates the entity type from the individual piece of content of that type
  3. It disambiguates the field from text entered in that field ('select fields... contain information')
  4. It clarifies who will be using the field (the author)
  5. It clarifies the benefit of the setting (making it easier for authors to find content to reference)