[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] Number of "eligibles" [Was: Group premium quotes]

From: Greg Chicares
Subject: Re: [lmi] Number of "eligibles" [Was: Group premium quotes]
Date: Wed, 26 Aug 2015 15:54:48 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0

On 2015-08-18 21:41, Vadim Zeitlin wrote:
> On Tue, 18 Aug 2015 18:50:33 +0000 Greg Chicares <address@hidden> wrote:
> GC> PDF says:
> GC>   "Number of eligibles: 2"
> GC> but the count should probably be one, not two.
> GC> that the composite ledger has been counted rather than ignored.
>  Yes, you're right.

I generally feel uncomfortable about adding "+ 1" or "- 1" to fix an anomaly
(because that often indicates a fencepost error that is likely to manifest
itself in multiple ways, some of which may have eluded notice), but in this
case that's what I did (committed 20150826T1546Z, revision 6265) because the
composite isn't an additional fencepost--it's different in kind. (I tried
adding an extra member for this count, but it didn't seem cleaner that way.)

The corresponding label was "Number of eligibles", but I changed that to
"Number of participants" because that's the term the column headers use.
And I believe it's the correct term of art here: a group could contain fifty
people who are "eligible" to enroll, of whom twenty elect to "participate"
while the other thirty decline--and here we print the number of rows in the
"Participant" column, which is twenty in that example, so it is really the
number of participants (and lmi doesn't even know how many unidentified
people were "eligible" because that information isn't given).

BTW, I also removed "(s)" from the summary's "Product" field, because it
cannot be plural: different products may have different footnotes, and
therefore each quote can use only one product. "Plan Type" won't be part of
the code--it'll be entered in the "Comments" input field; end users can say
  "Plan Types: Mandatory and Voluntary"
if that's appropriate.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]