Team's Response

No response provided.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

delete function can be improved for fast typists

by inputting the indexes instead of the student matriculation number,
it is quite a hassle to delete a person./multiple persons

---

_{[original: nus-cs2103-AY2021S2/pe-interim#1345] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

If the student list has 35000 students (size of NUS population), if a student is at index 28000, this will not prove faster as I will not know the index of the student unless I scroll down 28000 entries. I will have to find the student first, then delete index 1 which will require 2 steps. By deleting by matriculation number, the user (UHC staff) can delete the student in 1 step assuming the user knows the matriculation number of the student to delete.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: I think there is still 1 key concern from this delete by matriculation number approach to address here:

The use of editing/deleting by matriculation number is inconsistently applied. Based on the UG:

• Editing a student record is done by INDEX
• Editing an appointment and deleting a student record and deleting an appointment is done by MATRICULATION NUMBER

I do not think it is fair to expect that the staff using the app would remember to switch between INDEX and MATRICULATION NUMBER without having to refer back to the user guide or calling the help command.

from pe.