Changing file metadata doesn't force a major version update, which is required to cause update of file DOIs

If files are added or deleted from a version, we detect it and force the user to do a major /whole number version update. However, if file metadata, such as the name/path/tags are changed, the user can still select a minor version update. One consequence of this when File PIDs are enabled is that, since file PIDs are not updated for minor versions, the file PIDs don't get updated in that case. (I'm not sure if there are other differences.)

As this is pretty minor, and checking for all filemetadata changes could be expensive (unless we track changes with a last modified date or something), I don't currently have any plan to fix it - adding the issue so we're aware/others can decide whether to prioritize.

• What did you expect to happen?
  Editing file metadata could force a major version update (since it could be a file name change or path which looks like a data change), but alternately, changing publication to update file DOIs for minor version changes (if changes were made) could make sense as well (the file contents can't change so editing file metadata is still a metadata change)- as long as the PIDs are updated, major or minor version change doesn't matter so much.

Which version of Dataverse are you using?
6.2/develop

No source file, test, or entry point is named. Start by tracing version validation for added, deleted, and changed file metadata, then inspect how file PIDs are handled during publication; done requires an agreed behavior for metadata changes and tests covering the selected version and PID outcome.