Dataset Type selection step in Create Dataset page

[g-saracca]

What this PR does / why we need it:

Following up on @pdurbin's work in #845, this PR updates how users select the dataset type in the dataset creation flow.

For now, we’ve hardcoded the dataset type descriptions (“dataset” and “review”) as a temporary solution until the new field is added. Update: this was fixed in 7c355f4.

This is the first step toward supporting dataset types in the SPA, more enhancements coming soon.

Storybook links:

• Create Dataset page with Dataset Type selector
• Edit Dataset page with readonly Dataset Type field.

Which issue(s) this PR closes:

• Closes Allow for the creation of various dataset types #797
• Closes Dataset Type facet doesn't work, no matches #809

Depends on

This PR depends on the following backend PR:

• Review Datasets dataverse#11753

Special notes for your reviewer:

Suggestions on how to test this:

Pre-requisites for testing this.

As mentioned in IQSS/dataverse#11753:

Do all the setup at https://dataverse-guide--11753.org.readthedocs.build/en/11753/admin/dataverses-datasets.html#review-datasets-setup

1. Login within the SPA and navigate to the Create Dataset page.
2. By default only one dataset type exists('dataset' type) so you won't see a Dataset Type selector.
3. Add a new dataset type with:

curl -H "X-Dataverse-key:$API_TOKEN" -H "Content-Type: application/json" "http://localhost:8080/api/datasets/datasetTypes" -X POST -d '{"name":"review","linkedMetadataBlocks":["geospatial"]}'

4. Navigate again to the Create Dataset Page and now you will see a Dataset Type selector.
5. Select "Review" and create the dataset.
6. Go to edit the recently created dataset and you will se a Dataset Type readonly field with the value of "Review".

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Yes.

The "Create Dataset" page now has a Dataset Type dropdown. See the latest screenshots here: #876 (comment)

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

Not for now, might be good to add it after work related to dataset types is done.

Additional documentation:

[coveralls]

coverage: 97.296% (-0.04%) from 97.339% — 797-dataset-type-selection-step into develop

[pdurbin]

As a reminder, in the frontend (this PR) these descriptions are currently hard-coded to the values in the screenshot below. They should be retrieved dynamically from the backend instead.

I just fixed this in 7c355f4. It looks like this after running mvn test -Dtest=DatasetTypesIT#testCreateReview, which doesn't add descriptions or dataset types it adds for testing:

[pdurbin]

Here are updated screenshots as of IQSS/dataverse@be670d4 where @scolapasta and I decided to make some changes to the backend.

We're now using the linkedMetadataBlocks features and setting itemReviewedUrl and itemReviewedType as required=true in the tsv.

In the collection below, we are allowing both "Dataset" and "Review" under "Dataset Type".

Here is the creation of a review dataset. Note that the "Review Metadata" metadata block is present, which is what we want, of course.

Here is the creation of a regular dataset. Note that the "Review Metadata" metadata block is absent. This is what we want because having "Item Reviewed" as a required field doesn't make sense for a dataset.

[pdurbin]

The PR was on hold because we were waiting for the backend code to be merged, which happened yesterday.

• #11753

I moved it to "ready for review".