Just to check precisely what you intend. In the resource form, the different creator types (author, editor, translator etc.) each have a select box populated by all creators regardless of their role. This is because any one person can have multiple roles (e.g., I work as an author, an editor, and a series editor) and so the creator name is dire ctly related to the person not th eperson's role (e.g., there should not be multiple Grimshaw-Aagaards depnding on my role).
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my jargon a (multi-)selector is a combined widget or control for selecting an entity that must be linked (relation) an other entity. The linked entity is complex and need a search screen or has too much values for an HTML select.
The widget has:
A label to display the title of the selected entity.
A hidden input which keep the value of the selected entity.
Buttons to select (edit) or deselect (delete) an entity.
Selection is happening inside a popup opened by the edit button
Optional : add button to select more than one entity value
Optional : a select input to qualify the type of relation
By default, values of this widget are submitted with the form associated.
Optionaly, the widget is it's own form
Just to check precisely what you intend. In the resource form, the different creator types (author, editor, translator etc.) each have a select box populated by all creators regardless of their role. This is because any one person can have multiple roles (e.g., I work as an author, an editor, and a series editor) and so the creator name is dire ctly related to the person not th eperson's role (e.g., there should not be multiple Grimshaw-Aagaards depnding on my role).
Mark
In my jargon a (multi-)selector is a combined widget or control for selecting an entity that must be linked (relation) an other entity. The linked entity is complex and need a search screen or has too much values for an HTML select.
The widget has:
By default, values of this widget are submitted with the form associated.
Optionaly, the widget is it's own form
In attachment a sketch of selectors.
Interesting. So, in the case of the resource form, it's an enhancement of the widgets (if I can call them that) already there for the creators?
Mark
Yes, all the features are bundled together and played with a snippet of JS.
Creating an entity happens inside the search dialog.
The widget is made to be reusable and can be adapted form many entities.
Fine. Let's see what you come up with then!
Mark