Duplicate dataset, duplicate files deposited into different dataverses, same MD5, same UNF for tabular, different DOIs should not be allowed to complete upload

[sbarbosadataverse]

https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/GYWNQG
https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/ZTPW0Y

These are the same datasets, deposited into different dataverses and they were allowed to be "uploaded and published" in the UI

need a filter to prevent this from happening.

[landreev]

Says who??
Why?
We've always allowed the same files to be parts of different studies and dataverses... The goal was not to allow duplicates within a dataset - and that we are already doing.

[sbarbosadataverse]

@landreev
These datasets are identical data and using two different DOIs. While we allow linking, we should not have two copies of the same file to be used under different DOIs...never mind this is the same exact dataset---so while I understand that people can share files---this case has some uniqueness to it. You can assign it to Gustavo as you did but it still needs discussion

[sbarbosadataverse]

I have updated the issue to capture the entire case

[pdurbin]

See "4100+ of these failures ARE ACTUALLY THE SAME FILE" at #3675 (comment) ... copies of the same file across many, many datasets. I guess we allow this.

[pdurbin]

@sbarbosadataverse can we close this issue? The business logic is by design.