Correct propagation of delete

[elizoller]

• When a user chooses to delete a record, they will be prompted to ask if they are sure they want to do so. Users will also have the option to move the record to the Shared Repository.
• When a user chooses to delete a record which is an ography, they will be prompted to ask if they are sure want to do so, they will also be warned that this may break files which reference this one. Users will also have the option to move the record to the Shared Repository (this will likely break associations though).
• When a user chooses to delete a collection, they will be prompted to ask if they are sure they want to do so, they will also be informed that records which belong to this collection will be moved to the project's default collection or give the user the option to move to a different collection (Note: there is no sense of a default collection at this point - this will need to be created. Also if deleting the default collection then should the user be prompted to delete the children records or move them to the Shared Repository?)
• When a user chooses to delete a project, they will be prompted to ask if they are sure they want do so, they will also be warned that deleting a project deletes its children collections and records. The user should have the option to choose to move the records into the Shared Repository (this will remove collection structure and any permissions).

(TBD if this will truly delete, or more like tombstone)
(These tasks/specifications were taken from the spec document on 1/17/17)