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

Dataverse General Information: Uncheck "Metadata Elements from Parent" When another block is checked #1473

Closed
eaquigley opened this issue Feb 18, 2015 · 3 comments
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... Type: Bug a defect User Role: Curator Curates and reviews datasets, manages permissions UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF

Comments

@eaquigley
Copy link
Contributor

Currently when a user has "Metadata Elements from Parent Dataverse" selected, you cannot click on any of the checkboxes till Metadata Elements is unselected. @sekmiller could you please look into having a way for this to be overwritten when a user selects a metadata block? Thanks.

@mheppler
Copy link
Contributor

Cleaned up the Metadata Fields section. f6c0aab

@scolapasta scolapasta modified the milestones: Beta 14 - Dataverse 4.0, In Review - Dataverse 4.0, TEMP - Defer? - Dataverse 4.0 Feb 20, 2015
@eaquigley eaquigley modified the milestones: TEMP - Defer? - Dataverse 4.0, In Review - 4.0.x Feb 23, 2015
@sekmiller
Copy link
Contributor

You want to make the mdbs clickable when the dv is in "inherit" mode? Is this requirement obviated by the ability to "view" the contents of an unselected block? @eaquigley?

@mheppler
Copy link
Contributor

mheppler commented Apr 3, 2015

@sekmiller @eaquigley -- After reviewing what is currently on dvn-build, and seeing the new "View fields" changes made from Mar 25 cf4448b, I remember discussing this functionality.

What is being asked is, for a child dataverse, with "Use metadata fields from Root Dataverse" selected, allow the admin to click on the (now disabled, uncheckable) check boxes for the additional metadata blocks. Upon clicking these additional metadata checkboxes, the checkbox for "Use metadata fields from Root Dataverse" will be unselected.

This request originated from usability testing, where very few users understood that you needed to uncheck the first checkbox, before being allowed to select the disabled checkboxes for the additional metadata blocks.

If you have any questions about how to best implement this, I'm available to discuss it in further detail.

@mheppler mheppler added UX & UI: Design This issue needs input on the design of the UI and from the product owner Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... labels Jan 28, 2016
@sekmiller sekmiller removed their assignment Jan 28, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@pdurbin pdurbin added User Role: Curator Curates and reviews datasets, manages permissions and removed zTriaged labels Jun 30, 2017
@mheppler mheppler removed the UX & UI: Design This issue needs input on the design of the UI and from the product owner label Jan 3, 2019
@pdurbin pdurbin added the Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. label Oct 6, 2022
@pdurbin pdurbin added the Type: Bug a defect label Oct 7, 2023
@pdurbin pdurbin added the UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF label Oct 7, 2023
@pdurbin pdurbin closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... Type: Bug a defect User Role: Curator Curates and reviews datasets, manages permissions UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF
Projects
None yet
Development

No branches or pull requests

5 participants