Multiple logs in the same day is saved as different logs

[yyanyee]

When multiple logs are made for the same session, it is saved as separate logs. For example, when I do addlog i/S7140834E d/15 Nov 2024 l/young patient, then addlog i/S7140834E d/15 Nov 2024 l/has insomnia, followed by logs i/S7140834E, I get the following:

. As seen, there are 2 separate logs despite the same date/appointment on 15 Nov 2024. Making it inefficient in viewing logs from the same appointment.

Consider the following case: A doctor/therapist views a patient for a consultation. As the consult goes, the doctor continuously adds consult notes ie logs using the addlog command. Her doing so will result in multiple entries of logs despite it all being in the same appointment itself.

As a user, I would except addlogs to organise logs according to appointment/dates for each patient so that I can easily view all patient information by appointment.

A suggestion would be to add all logs under the l/ field to the same log but in a new line.

[nus-pe-script]

Team's Response

It seems like there is a misunderstanding in what is considered as a session log. Each log is tagged to a single therapy session, on any given day there can be multiple therapy session for a person as such, multiple logs in a single appointment date. As such these logs should not be appended.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Thank you for your response. The misunderstanding seems to have risen from the UG.

As per the user guide,

The phrase "keep track of sessions or important notes related to each session" gives the user the impression that addlog can be used for multiple notes associated with the same session. By using the plural "notes" and the phrase "related to each session," it implies that users can repeatedly use the addlog command to append additional notes for the same session. However, in actuality, the behaviour of the addlog command results in creating separate logs, which does not align with what users might reasonably expect from this description.

The User Guide does not clarify that a single "session" is strictly tied to a single addlog command or that the command is intended to create a new log for each invocation, regardless of whether it pertains to the same session or not. This lack of clarity could mislead users into believing that they can sequentially add notes to a single session log using multiple addlog commands. This discrepancy between the described functionality and the actual behaviour of the command leads to confusion and unmet user expectations. As a user, after reading the User Guide, I would have reasonably expected that I could append additional details to the same session using multiple addlog commands, rather than creating multiple distinct logs.

This leads me to believe that this should be a Functionality bug as the command behaviour differs from what is inferred from the user guide. Clarifying the intended use of the addlog command and explicitly defining what constitutes a "session" in the User Guide would help resolve this misunderstanding.

---