Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ingest Form with conditional fields #1484

Open
DonRichards opened this issue Apr 8, 2020 · 2 comments
Open

Ingest Form with conditional fields #1484

DonRichards opened this issue Apr 8, 2020 · 2 comments
Labels
Type: documentation provides documentation or asks for documentation. Type: enhancement Identifies work on an enhancement to the Islandora codebase

Comments

@DonRichards
Copy link
Member

DonRichards commented Apr 8, 2020

The ingest page needs more intuitive grouping and conditional fields.

Grouping

I'm suggesting we group the content to give context. For instance, language is a drop-down in 2 separate locations in the same form.

  • Content Model/resource type
  • Fields (title, description, etc.)
  • Behavior (viewer, parent/member of)
  • System level (language, weight, notes, table of contents)

Conditional form fields

Most importantly I think several of these fields need to be hidden when a collection vs a video content model is selected.

Screen Shot

Suggested behavior

This will probably be best experienced when both of these suggestions are applied. At the top of the form should be the content model. Once a "content model" is selected, all of the irrelevant fields should be "hidden" as a default to keep the interface clean and intuitive.

Drupal's link to applying this to a form. https://www.drupal.org/docs/8/api/form-api/conditional-form-fields

This ticket is roughly related to #932

@mjordan
Copy link
Contributor

mjordan commented Apr 8, 2020

Grouping can be done via https://www.drupal.org/project/field_group, and https://www.drupal.org/project/conditional_fields looks like it will provide a GUI for defining conditional fields.

@dannylamb
Copy link
Contributor

Hashed this out at the last Islandora 8 call and consensus was to keep all the fields, but disable most of them, leading to a more streamlined default that you can add to from already existing fields.

@kstapelfeldt kstapelfeldt added Type: documentation provides documentation or asks for documentation. Type: enhancement Identifies work on an enhancement to the Islandora codebase and removed documentation labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: documentation provides documentation or asks for documentation. Type: enhancement Identifies work on an enhancement to the Islandora codebase
Projects
Development

No branches or pull requests

4 participants