UX: Pattern for Delete (Including for Undeletable Records)

Purpose: For UX to come up with a pattern for deletion.

• For a single record view (e.g. Locations, Fixed Due Date Schedules, Loan Policies, Orders):
  • Where does the delete option live?
  • What does the delete option look like when the record is in use and can't be deleted (usually just when the record is required in the record in which it's used)
  • What does the delete option look like/do when the record is in use but CAN be deleted (because it's not a required element in the record in which it's used). Usually in this case, you should be permitted to delete the record but given a warning that it is in use.
• For a page with multiple records (e.g. controlled vocab pages like Settings > Patron groups, Resource types, Material types etc):
  • What does the delete option look like when the record is in use and can't be deleted (usually just when the record is required in the record in which it's used). Note:
    • My understanding from Mark Deutsch is that,due to performance issues, is NOT possible to query the back end in advance of a delete attempt for some controlled vocab pages (esp. those related to inventory). In these cases, a delete needs to be attempted before the system can deny
    • That said, some other controlled vocab CRUD pages (e.g. patron groups) can query the backend in advance to do things like hide or inactivate the delete icons.
  • What does the delete option look like/do when the record is in use but CAN be deleted (because it's not a required element in the record in which it's used). Usually in this case, you should be permitted to delete the record but given a warning that it is in use.

Related issues (some good stuff may be found in comments):

• UIORG-86