Update Dataset License API

[GPortas]

What this PR does / why we need it:

New Endpoint: /datasets/{id}/license

A new endpoint has been implemented to manage dataset licenses.

Functionality

• Updates the license of a dataset by applying it to the draft version.
• If no draft exists, a new one is automatically created.

Usage

This endpoint supports two ways of defining a license:

1. Predefined License – Provide the license name (e.g., CC BY 4.0).
2. Custom Terms of Use and Access – Provide a JSON body with the customTerms object.
   • All fields are optional except termsOfUse, which is required.

Which issue(s) this PR closes:

• Closes API: Set configuring licenses and custom terms for a dataset #11771

Suggestions on how to test this:

curl -H "X-Dataverse-key:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -X PUT "https://demo.dataverse.org/api/datasets/<dataset_id>/license" -H "Content-type:application/json" --upload-file <json_file_path>

To set a predefined license (e.g., CC BY 4.0), provide a JSON body with the license name:

  {
    "name": "CC BY 4.0"
  }

To define custom terms of use and access, provide a JSON body with the following properties. All fields within customTerms are optional, except for the termsOfUse field, which is required:

  {
    "customTerms": {
        "termsOfUse": "Your terms of use",
        "confidentialityDeclaration": "Your confidentiality declaration",
        "specialPermissions": "Your special permissions",
        "restrictions": "Your restrictions",
        "citationRequirements": "Your citation requirements",
        "depositorRequirements": "Your depositor requirements",
        "conditions": "Your conditions",
        "disclaimer": "Your disclaimer"
    }
  }

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

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

[coveralls]

coverage: 23.801% (+0.02%) from 23.778%
when pulling 676f834 on 11771-set-dataset-license-api
into 53bff4c on develop.

[sekmiller]

This doesn't do anything to preserve whatever has been entered for File Access Requests or Terms of Access so it will fail if the dataset has any restricted files. In the absence of restricted files would we still want to wipe out whatever may have been entered with respect to data file access?

[qqmyers]

Or the other TermsOfUseAndAccess fields (originalArchive, sizeOfCollection, ...).

[sekmiller]

@GPortas please take a look at how the setting of custom terms of will delete any entries in custom terms of access. I ended up reworking #11772 so that the api will only modify the terms of access and leave the license or custom terms of use the same as they were prior to the update. A more radical approach would have been to split the terms of use and access tables into two tables but that seemed like too much to take on here.

[GPortas]

@sekmiller Thank you for finding the problem. I have followed a very similar approach to the one you took so we do not overwrite the whole entity, but only the custom terms of use fields.

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11771-set-dataset-license-api

ghcr.io/gdcc/configbaker:11771-set-dataset-license-api

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[sekmiller]

Looks good. Thanks for the update.

[stevenwinship]

tested manually on local docker. Verified in UI and DB