Templates

[eaquigley]

@mheppler:

Workflow:

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.
2. For creating a template, a user will go to Edit Dataverse->Templates->Page displaying all templates for that dataverse (if any exist) otherwise, the page will prompt user to create a template to start process. There should always be a create template button.
3. Create template page: metadata fields that were selected as required previously appear and user can fill in default values here. Click save.
4. Screen with listing of templates: each template has option to clone, also need a way to determine which template is the default template

Mockups:

1. Edit Dataverse button->General Information (selecting metadata fields as required)
2. Edit Dataverse button->Templates (template page with no templates)
3. Edit Dataverse button->Templates (template page with templates)
4. Create template page (should be same as editing template screen)
5. Cloning Template (on template page)
6. Selecting template as default template (on template page)
7. Create dataset page when a template has been chosen

[kcondon]

Opening a new ticket, #858 for selecting required fields since it may not be implemented in the same time frame as the templates functionality

[mheppler]

Here are the mockups for this workflow: https://iqssharvard.mybalsamiq.com/projects/datasettemplates-dataverse40/grid

[mheppler]

Giving this to @sekmiller to move to QA when the general functionality is delivered.

[kcondon]

All major functionality has been implemented with issues opened as separate tickets. Choosing required fields was broken into separate ticket.
Closing