Pete R Jemian

In the [apstools package](https://github.com/BCDA-APS/apstools/blob/3f54b70303b785e59218fd9aaa3c93c7e9419678/apstools/synApps/_common.py#L34), we define `description` as connected with the `.DESC` field.

In EPICS, `.DESC` is a field common to all records.

FWIW, NeXus has a `long_name` attribute that matches this use. It is defined in many NeXus classes, such as [`NXdata`](https://manual.nexusformat.org/classes/base_classes/NXdata.html#index-15).

And, yes, NeXus also had long discussions about how to name things.

I believe `long_name` here might be misleading (by association with the ophyd object `.name`). Perhaps `long_description` would fit the original intent, without association to the the EPICS `.DESC` field?

Checking the [ao record documentation](https://epics.anl.gov/EpicsDocumentation/AppDevManuals/RecordRef/Recordref-9.html), there is the ['MLST'](https://epics.anl.gov/EpicsDocumentation/AppDevManuals/RecordRef/Recordref-9.html#HEADING9-47) field (Last Value Change Monitor Trigger Value) that is *almost* what issue describes. Changing this value changes when the PV monitors...

Oh, nevermind since MLST can't be modified from a CA client. At least we looked.

Needs an expert to weave this into the version= design.

I suggest the documentation provide this example (since the existing docs led me astray, with a call to `RE.pause()` from the plan).

@DominicOram Thanks for your response. I'm just asking so the process becomes documented (resolves any questions in the future).