Implement datasetType metadata block support (at global level)

[cmbz]

Overview

• See HDV Task: GREI 6 - Initial Dataset Type Support dataverse-pm#307 and Proposal: Supporting Multiple Dataset Types in Dataverse for details

Scope of Work

• Designate specific metadata fields for a specific datasetType

Depends on

• dataset types (software, workflow, etc.) - initial support #10694
• Implement a global setting and/or API for dataset types #10518

See also

• HDV Task: GREI 6 - Initial Dataset Type Support dataverse-pm#307

[pdurbin]

As discussed at tech hours yesterday, I pulled this into FY25 Sprint 5 two weeks ago without realizing how poorly defined this issue is and without grasping that the proposal, as written, implies a lot of work on the JSF code, which we intend to dispose of. 🗑️

I liked the suggestion from @qqmyers that a possible direction would be to create a series of superuser-only APIs that allows an installation to be configured to associate a dataset type with metadata fields. However, what should the JSON look like that will ultimately be used by the SPA? Should we hide this output behind the "admin" API for now and check in with the frontend team (when they are ready) to see if the JSON is agreeable? In short, there would be no value to the end user yet, but we could make progress on database tables and business logic.

@scolapasta suggested that a smaller group (than all of tech hours) could discuss this issue further and unblock it. Meanwhile, perhaps the size should be removed and it should go back into "need sizing" for this discussion to happen (heads up to @cmbz).

[cmbz]

2024/09/25:

• Possible option for SPA Q4 work. @GPortas will add as task to SPA Q4 proposal for evaluation.
• @qqmyers @scolapasta @pdurbin and @cmbz will meet (coord via Slack) to follow up