`allowHarvestingMissingCVV` value not updated via PUT `/api/harvest/clients/{nickName}` endpoint

Description

When updating a harvesting client via the PUT endpoint /api/harvest/clients/{nickName}, the allowHarvestingMissingCVV field is not being retrieved from the JSON request body and therefore not persisted in the database.

Steps to Reproduce

1. Create a harvesting client via the API or UI
2. Attempt to update the client using PUT /api/harvest/clients/{nickName} with allowHarvestingMissingCVV set to a different value
3. Retrieve the client configuration and observe that allowHarvestingMissingCVV has not been updated

Expected Behavior

The allowHarvestingMissingCVV value should be retrieved from the JSON request body and updated in the harvesting client configuration.

Actual Behavior

The allowHarvestingMissingCVV value is ignored during the PUT request. The field value remains unchanged.

Root Cause Analysis

In HarvestingClients.java, the modifyHarvestingClient() method does not extract the allowHarvestingMissingCVV value from the incoming JSON object, unlike other fields such as harvestUrl, archiveUrl, etc.

Version

• Dataverse 6.9

Relevant Code

• File: src/main/java/edu/harvard/iq/dataverse/api/HarvestingClients.java
• Method: modifyHarvestingClient() (PUT handler)

Are you thinking about creating a pull request for this issue?

No fix is currently planned by the team.

Start in src/main/java/edu/harvard/iq/dataverse/api/HarvestingClients.java, at the modifyHarvestingClient() PUT handler, and compare its JSON field extraction with the other harvesting client fields. Verify the endpoint with a request that changes allowHarvestingMissingCVV, then confirm the updated value is persisted and returned in the client configuration.