Naming of Notes vs Comments vs Memos

Description

Hi Cate,

This came up in Montreal, and consistently pops up every time we discuss anything that includes any of these terms.

I suggest we do this:

• Notes (module) becomes "Comments"
• Fields that are built into a record (i.e. not in the current Notes Module), but are not exposed to patrons, are called "Notes"
• Fields that are built into a record (i.e. not in the current Notes Module) and that are exposed to patrons are called "Patron notes".

No matter what the outcome is, I just think we should centrally define this and document it somewhere, once and for all.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Filip Jakobsen February 27, 2018 at 5:54 PM

It sounds like Comments works for everyone as name for this module. Let's rename it and refer to it as such. , what's the procedure for this?

Cate Boerema December 15, 2017 at 10:42 AM

This is an interesting idea and one that came up when we initially discussed notes with the UM SIG. The reason why they felt the Comments (Notes) component as currently designed didn't work for them was that they wanted the notes to be co-located with certain fields. But if there was a way to create and view notes in a more co-located fashion while also logging them in the Comments feature, that might be cool. That said, the UM and RA SIGs also wanted to be able to configure notes to automatically "pop up" on the user record (if there is something very important that needs to be remembered/communicated). Let's gather the detailed requirements first and after that decide if there is any way the existing Comments feature could be used.

I'd like to hear what the other POs, particularly , think, as they are farther along with notes requirements than the SIGs I've been working with.

Jakub Skoczen December 15, 2017 at 10:31 AM

"Comments" sound good and fairly generic. As far as field-level notes are concerned we don't have anything implemented yet. But it would be conceptually possible to extend the current notes features with a function to scope a note to a field (or subfield) within the record and retain the existing mechanics.

Cate Boerema December 15, 2017 at 10:07 AM

Okay. I'm sold on Comments. It definitely rolls off the tongue better than Discussion.

Filip Jakobsen December 14, 2017 at 5:20 PM

I don't know if we have yet implemented any of the Patron Notes fields. It might need to be its own Module / plugin / feature.

Won't Do

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 14, 2017 at 4:24 PM
Updated June 21, 2022 at 7:37 AM
Resolved June 21, 2022 at 7:37 AM
TestRail: Cases
TestRail: Runs