Bug #13338

Problem: Term deletion warning is not specific enough

Added by Peter Van Garderen 5 months ago. Updated 4 months ago.

Status:VerifiedStart date:05/29/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Taxonomy / Term
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

PROBLEM STATEMENT:
When a user attempts to delete a Term (e.g. Subject) they are presented with a warning which reads: "Are you sure you want to delete [TERM]? This term is used in [X] descriptions. The term will be deleted from these descriptions."

This seems to imply that X is referring to "archival descriptions". However, it represents a total of both linked archival description and authority records. In the attached screencap. It reads "Are you sure you want to delete Chemistry? This term is used in 17 descriptions. The term will be deleted from these descriptions." In this case the Subject Term "Chemistry" is linked to 14 authority records and 3 archival descriptions.

PROPOSED SOLUTION:
The warning should either explicitly break down how many separate archival descriptions and authority records the Term is linked to or it should use a more generic term.

i.e. "Are you sure you want to delete Chemistry? This term is used in 3 archival descriptions and 17 authority records. The term will be deleted from these records." Note that in this scenario ideally "archival descriptions" and "authority records" are replaced by their user interface labels. However, these are singular, e.g. "archival description", so this doesn't really work.

Therefore, the best solution is the simplify the warning statement to read: "Are you sure you want to delete [TERM]? This term is used in [X] records. The term will be deleted from all these records."

History

#1 Updated by Mike Cantelon 5 months ago

  • Status changed from New to Code Review
  • Assignee deleted (Mike Cantelon)

#2 Updated by Mike Cantelon 5 months ago

  • Status changed from Code Review to QA/Review
  • Assignee set to Peter Van Garderen

Merged into qa/2.6.x.

#3 Updated by Peter Van Garderen 5 months ago

  • Status changed from QA/Review to Deploy

Fixed.

#4 Updated by Dan Gillean 4 months ago

  • Status changed from Deploy to Verified
  • Assignee deleted (Peter Van Garderen)

Also available in: Atom PDF