I am using handles, this may go down differently for different PID providers.
If file pid generation is enabled, and registerWhenPublished is false for the current PID provider, AbstractDatasetCommand.registerFilePidsIfNeeded() will try to register file pids immediately after upload. It will even try to register pids for all files in the dataset that do not have them.
It will then call registerFileExternalIdentifier() that calls pidProvider.createIdentifier(dataFile) that calls registerNewHandle(dataFile) which then tries to get the authority and handle from the dataFile object, which are of course empty, then sends this null/null to the handle server to register a PID, which fails.
Therefore, file pid registration always fails. What is worse, it sends one request for each file in the dataset, for each uploaded file. This compounds as more files are uploaded, making the upload ever slower.
I am using dataverse 6.9 .
I could not find any similar bugs in the bug tracker.
Did anyone have a similar problem, or should I just try to create a fix?
Last updated: Oct 02 2026 at 18:51 UTC