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

Edit Dataverse: Select which fields are required in each metadata block #858

Closed
kcondon opened this issue Aug 25, 2014 · 6 comments
Closed
Assignees
Labels
Type: Feature a feature request UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@kcondon
Copy link
Contributor

kcondon commented Aug 25, 2014

This is from the initial templates ticket, #755

Breaking out as a separate ticket since it may not be implemented in the same time frame:

  1. When creating a dataverse, a user can select metadata blocks that are appropriate for that dataverse and the data that will be contained in it. When selecting metadata blocks, a user can also determine which fields are required.
@kcondon kcondon added this to the In Review - Dataverse 4.0 milestone Aug 25, 2014
@kcondon kcondon mentioned this issue Aug 25, 2014
@eaquigley eaquigley modified the milestones: Beta 7 (Permissions & Auth Branch) - Dataverse 4.0, In Review - Dataverse 4.0 Sep 24, 2014
@sekmiller
Copy link
Contributor

Functionality for selecting required fields has been added. Available in current build

@sekmiller sekmiller assigned kcondon and unassigned sekmiller Oct 24, 2014
@kcondon kcondon assigned esotiri and unassigned kcondon Oct 24, 2014
@esotiri esotiri assigned sekmiller and unassigned esotiri Oct 31, 2014
@esotiri
Copy link
Contributor

esotiri commented Oct 31, 2014

Please can you send it back when done.

mheppler added a commit that referenced this issue Nov 3, 2014
@mheppler
Copy link
Contributor

mheppler commented Nov 3, 2014

Cleaned up the UI for the hide/require widget on the Dataverse General Information create/edit view. Removed the example metadata field list.

@sekmiller
Copy link
Contributor

this is a parent ticket. can we close it and deal with any implementation issues separately

@sekmiller sekmiller removed their assignment Nov 4, 2014
@esotiri
Copy link
Contributor

esotiri commented Nov 4, 2014

ok, closing this.

@esotiri esotiri closed this as completed Nov 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature a feature request UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

6 participants