Manage Dataset Templates Integration

[ChengShi-1]

What this PR does / why we need it

We have api and use cases for get/create/delete template, we are able to integrate things related to these use cases.
Collection page -> Edit button -> Dataset Templates

Which issue(s) this PR closes:

• Closes Dataset Templates Integration #907

Special notes for your reviewer:

Suggestions on how to test this:

Test Template use in dataset

Empty State

Create Dataset Template

After creating it successfully, it's supposed to jump to Edit Terms page, but because of a lack of API now, we cannot edit terms here, but I have a mock page here.

Manage Templates ( you could sort the list by name, date and usage, if you click the table's headers)
PS, make a default, edit templates are not implemented

When you click the "eye"(view) icon, there is a modal of Dataset Template Preview

When you click the Delete icon, there is a modal of Delete Template

When you click copy, it should give you a copy template and refresh the table automatically so you could see it soon.

Create a nested collection inside Root collection, you will have a Edit permission to current collection, and only view permission to root collection's templates.

Is there a release notes or changelog update needed for this change?:

Yes

Additional documentation:

Related PR for editing template #954

[coveralls]

coverage: 97.389% (-0.1%) from 97.535% — TemplateUI into develop

[ChengShi-1]

Hi @jp-tosca , it's ready for QA now, and all checks are passing

[jp-tosca]

@jggautier We had a brief meeting about this PR and would appreciate your thoughts.

[jggautier]

@jggautier We had a brief meeting about this PR and would appreciate your thoughts.

Heya @jp-tosca. Phil asked if I wanted to join a Zoom meeting today about templates, but it sounds like the meeting was over before I replied.

What about the PR should I check out?

[pdurbin]

To summarize, here is my suggestion: to use a different symbol and color for "required by the template" vs "required by the collection" (the latter is dynamic, as we saw). I was saying † (sword/dagger) or ‡ (double dagger) on the call and that's what I prefer but in this mockup I'm using a lightning bolt (it's what I could quickly find in Bootstrap 😅 ):

Also, a dagger or whatever is helpful when it's on fields that don't vary. Maybe a lab wants to always have the same contact email address or whatever.

Also, it's a long page with a lot of fields! Having a dagger on a field way down at the bottom could be useful for someone who can't remember (or never looked, if it's a different person!) what's required or not for the collection. Maybe "Funding Information" halfway down, for example, is always required and always the same (and therefore a good candidate for hard-coding in a template).

[jggautier]

Ah thanks for letting me know on Slack that this is what JP was referring to.

I haven't been watching this PR closely and I'm not really familiar with how or how well templates have been working for users of the JSF version of Dataverse, so I have more questions than suggestions 😅

But it looks we're considering changes related to how people creating and editing templates are made aware of what fields are required and when. Is that right?

[jp-tosca]

Done with this @ChengShi-1 please open the issue if you have not done so yet for the follow-up about the required fields.