Add all required fields to the Create Dataset Form

[GPortas]

Overview of the Feature Request

Add all required fields to the Create Dataset Form. This is only the UI, so no API connected.

These changes will be added to the boilerplate created on #231, so we need to wait for PR #251 to be accepted.

What kind of user is the feature intended for?

All of them

What inspired the request?

• Set up the boilerplate for the Create Dataset Form #231

What existing behavior do you want changed?

None

Any brand new behavior do you want to add to Dataverse?

Include the required fields to the Create Dataset Form

Any open or closed issues related to this feature request?

• Set up the boilerplate for the Create Dataset Form #231
• Feature/231 create dataset boilerplate #251

[GPortas]

Should this issue be tagged with the waiting tag until the create dataset boilerplate PR is closed? I think the changes to be developed in this issue depend on the page boilerplate resulting from the PR.

@pdurbin I see you moved the issue to in progress, I'm not sure if I'm missing something.

@M27Mangan

[GPortas]

As discussed in standup.

Moved the issue back to This Sprint column and added the waiting tag due to dependency with #251

[pdurbin]

Weird, I don't remember moving it but a lot of issues got moved in the transition from project 2 to 34. 😅

[M27Mangan]

@gporta, @MellyGray, @ekraffmiller Who should I talk to regarding the dynamic creation of Form Fields, and what rules govern when certain fields are visible?

[MellyGray]

@M27Mangan, we discussed this last Monday during the post-standup meeting. I believe @GPortas had an approach for this. There are some config files that need to be read to display the form fields, and these would be obtained via API

[GPortas]

As stated here #252 (comment), this issue has a "Waiting" tag. Could you please start another issue that doesn't have the Waiting tag? @M27Mangan

[GPortas]

@M27Mangan

I have moved this issue back to sprint ready, as its implementation should be wait for #251 to be merged.

I have created a new analysis issue, to include in this new sprint, considering your interest in yesterday's standup in analyzing the implementation of the form fields: #282. We don't need to wait for the analysis issue, as it does not require code changes.

I have sized the issue with a 10, but feel free to resize it as you consider.

[MellyGray]

I'm removing the "Waiting" tag, as #251 is now in "Ready for QA", and we believe it's unlikely that the code will change at this stage on the board. It seems better to potentially have some changes from QA and need to pull from that branch, rather than continue to block the development of this feature

Also we've done this in the past with other issues with the Waiting tag, we removed it once the blocking issue was in Ready for QA

[GPortas]

Deprioritized and moved back to SPA backlog in order to focus on File Page issues.

We will prioritize issues for "Create Dataset" once we finalize the File Page work.

@cmbz

[GPortas]

Waiting for: #316

[MellyGray]

Closing this issue because the required fields were already added in the scope of

• Create functional create dataset form with "hardcoded" citation metadata fields #316

We'll continue working on the rest of the fields in:

• Dynamically render Create Dataset Form fields based on the backend configuration #336