When files are moved to the remotely deleted folder they are added to the root. This has at least 2 consequences greatly reducing the utility of these archived files:
- Name collision: if files in different library folders share a name and both are deleted there would be a name collision. This could be resolved in a number of ways but could ultimately lead to a jpeg and raw file pair being renamed differently and, therefore, no longer readily identifiable as a pair.
- Loss of organizational structure: If a top-level folder is unintentionally deleted, all leaf files will be flattened into a single organizational structure. While the photos are recoverable in some form, the context captured in the folder structures is completely lost.
Ideally, when a file (i.e. folder 1/folder 2/file a.jpeg) is deleted it would be moved to the deleted_remotely folder while maintaining the original folder structure (i.e., deleted_remotely/folder 1/folder 2/file a.jpeg). This makes the image easily discoverable and easily recoverable while also significantly reducing, though not entirely eliminating. the risk of name collisions