Support Excluding the Recycle Bin from Duplicate Name Detection

[pierre.michel.schuhmacher]

Hi Team, 
In a future update, provide an option to exclude the Recycle Bin folder when detecting duplicate names.

Many Thanks

PM

[ihayesjr]

@pierre.michel.schuhmacher 

Thank you for posting the idea.

If we exclude the recycle bin from the duplicate name detection, what do you want to happen if a user needs to restore the duplicate file name from the recycle bin?

[pierre.michel.schuhmacher]

Hi @ihayesjr 

In my opinion, restoring a file from the recycle bin should follow the same behavior as windows when a naming conflict exists:

• If a file with the same name already exists, Vault should notify the user and offer options such as:
  • Restore the file with a new name.
  • Restore it to another location.
  • Cancel the restore operation.

The main goal of this idea is to prevent deleted files that remain in the recycle bin from unnecessarily blocking the creation or renaming of active files. Files in the recycle bin are effectively inactive, so they should not participate in duplicate name detection until a restore is attempted.

[ihayesjr]

@pierre.michel.schuhmacher 

The Trash Bin is not the same as Windows. First, a user cannot create a file in the same folder as the file in the trash bin. Vault prevents this. It can happen that a file with the same name is created in a different folder.

Therefore, a restore into the same folder is still possible because it is the only file with that name in that folder.

We could allow the restore and just inform the user that there is a duplicate file in another location.

Would that be enough?

[pierre.michel.schuhmacher]

@ihayesjr 

Yes, i think that would be sufficient.

A message box informing the user that a file with the same name exists in the " XXX folder" in the vault would be helpful. It may also be useful to indicate that, if necessary, one of the files should be renamed.