Follow up for #1801304-211: Add Entity reference field

Problem/Motivation

It is not discover able that you will need "Entity reference" to be able to select Content, Users, Files, Terms etc. The discover ability you need such an abstract term to get a field with users, is a big issue. Surely there are some name space conflicts, but core should use the most sensible label.

list-types-of-references-2013-01-31_1717.png

Proposed resolution

Have "User reference, Content reference, File reference" as options and simply keep the config options under a Config reference with a dropdown.

Remaining tasks

Discuss if this is a good idea
Discuss how to implement it

User interface changes

No new UI patterns.

API changes

maybe, TBD

Original report by @Bojhan

Fundamentals

It is not discover able that you will need "Entity reference" to be able to select Content, Users, Files, Terms etc. I'd much rather have "User reference, Content reference, File reference" as options and simply keep the config options under a Config reference with a dropdown. I think the discover ability you need such an abstract term to get a field with users, is a big issue. I'm sure there are some name space conflicts, but core should use the most sensible label.

Why are we introducing the word "Entity" here, although I am sure it has useful qualities, as @yoroy already mentions its another abstraction label people won't get and in this case its not really necessary. We can just use the word "Reference" which makes it much less scarier to select

Comments

StatusFileSize
new101.96 KB

Oh maybe that was kind of done.

Perhaps the todo is to remove the word entity.

Here on the global field settings the tar type can be selected.

target-type-2013-01-31_1733.png

This isn't a related comment, sorry, but...

Am I correct in thinking that that is the new Admin Toolbar in Drupal 8?

@timothystock yep. :)

Assigned:Unassigned» agentrickard

Sprinting on this one today.

Were the 'Remaining tasks' from the issue summary discussed somewhere outside the issue queue? :)

Discuss if this is a good idea
Discuss how to implement it

If you plan to implement comment #1, we have #1953438: Don't expose the term 'Entity' to users for that..

Also note that the term 'Entity' is pretty much accepted in D8's UI, per #2030569-23: [policy] Decide how to refer to "entities" and "bundles" in D8 UI and #1953438-26: Don't expose the term 'Entity' to users.

Sorry for spamming, but I wouldn't want you to waste time on an issue that should probably be closed as 'won't fix'.

Assigned:agentrickard» Unassigned
Status:Active» Closed (duplicate)

Right, I worked on #1963340: Change field UI so that adding a field is a separate task instead. Closing this as a duplicate. Thanks!