Report definition options incomplete

[therden]

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

[dagraham]

From the user manual:

Groupby setting <#groupby-setting>

A semicolon separated list that determines how items will be grouped and sorted. Possible elements include/date specifications/and elements from

*

c: context

*

f: file path

*

k: keyword

*

t: tag

*

u: user

A/date specification/is either

• w: week number

or a combination of one or more of the following:

*

yy: 2-digit year

*

yyyy: 4-digit year

*

MM: month: 01 - 12

*

MMM: locale specific abbreviated month name: Jan - Dec

*

MMMM: locale specific month name: January - December

*

dd: month day: 01 - 31

*

ddd: locale specific abbreviated week day: Mon - Sun

*

dddd: locale specific week day: Monday - Sunday

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.

[therden]

Hello Dan,

I'm sorry that I wasn't clearer. I understood that the Report engine was/is working as designed; it was my intention to ask that the elements I listed be added to those recognized by it for grouping and sorting (and, I think, filtering -- right?).

My reason for asking is that I'm not otherwise seeing any way of even identifying all the items (among those in currently selected Calendars within etmTk) which have an alert set, have a "go to" file defined, are part of a task group, share a location, have an associated memo, or are assigned a priority. If the capability's there and I've missed it, please let me know.

Otherwise, thank you for considering yet another request from this particular "squeaky wheel."

-Thomas

On Sun, May 4, 2014 at 7:12 PM, dagraham notifications@github.com wrote:

From the user manual:

Groupby setting <#groupby-setting>

A semicolon separated list that determines how items will be grouped and sorted. Possible elements include/date specifications/and elements from

*

c: context

*

f: file path

*

k: keyword

*

t: tag

*

u: user

A/date specification/is either

• w: week number

or a combination of one or more of the following:

*

yy: 2-digit year

*

yyyy: 4-digit year

*

MM: month: 01 - 12

*

MMM: locale specific abbreviated month name: Jan - Dec

*

MMMM: locale specific month name: January - December

*

dd: month day: 01 - 31

*

ddd: locale specific abbreviated week day: Mon - Sun

*

dddd: locale specific week day: Monday - Sunday

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.

— Reply to this email directly or view it on GitHubhttps://github.com/dagraham/etm-tk/issues/3#issuecomment-42150299 .

[dagraham]

Hi Thomas,

Somehow I didn't realize that you were the source of this post. Simultaneous submissions - impressive!

Groupby for alerts would show you every item with a 30 minute sound alert, every item with a 30 minute display alert, every item with a 25 minute sound alert, and so forth. I doubt this is actually what you have in mind. Perhaps a list of items that have @a fields?

More generally, maybe a "fields view" that would list all items with @a fields under the branch @a, all items with @b fields under @b and so forth? In each case, this would be a list of items and not instances so, like path view, only one instance of a repeating item would be shown with the "relevant" date/time displayed. I'm thinking @s, @e, @c, @k, @t, @u and perhaps some others should be omitted? Is this more like what you have in mind?

I agree that location is a candidate for groupby, since someone might actually want to group by the actual location, Arbys, Burger King, or whatever.

-Dan

therden mailto:notifications@github.com May 4, 2014 at 9:18 PM Hello Dan,

I'm sorry that I wasn't clearer. I understood that the Report engine was/is working as designed; it was my intention to ask that the elements I listed be added to those recognized by it for grouping and sorting (and, I think, filtering -- right?).

My reason for asking is that I'm not otherwise seeing any way of even identifying all the items (among those in currently selected Calendars within etmTk) which have an alert set, have a "go to" file defined, are part of a task group, share a location, have an associated memo, or are assigned a priority. If the capability's there and I've missed it, please let me know.

Otherwise, thank you for considering yet another request from this particular "squeaky wheel."

-Thomas

On Sun, May 4, 2014 at 7:12 PM, dagraham notifications@github.com wrote:

From the user manual:

Groupby setting <#groupby-setting>

A semicolon separated list that determines how items will be grouped and sorted. Possible elements include/date specifications/and elements from

*

c: context

*

f: file path

*

k: keyword

*

t: tag

*

u: user

A/date specification/is either

• w: week number

or a combination of one or more of the following:

*

yy: 2-digit year

*

yyyy: 4-digit year

*

MM: month: 01 - 12

*

MMM: locale specific abbreviated month name: Jan - Dec

*

MMMM: locale specific month name: January - December

*

dd: month day: 01 - 31

*

ddd: locale specific abbreviated week day: Mon - Sun

*

dddd: locale specific week day: Monday - Sunday

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.

— Reply to this email directly or view it on GitHubhttps://github.com/dagraham/etm-tk/issues/3#issuecomment-42150299 .

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3#issuecomment-42153252.

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.

[dagraham]

I've posted my wish list to https://groups.google.com/forum/#!topic/eventandtaskmanage with some refinements. For bug reports, I guess github is best, but would prefer the group for more general stuff since many/most of the members there won't look at github.

Thanks again for all your help, Dan

therden mailto:notifications@github.com May 5, 2014 at 8:22 PM Good evening Dan.

On Mon, May 5, 2014 at 6:37 AM, dagraham notifications@github.com wrote:

Hi Thomas,

Somehow I didn't realize that you were the source of this post. Simultaneous submissions - impressive!

Groupby for alerts would show you every item with a 30 minute sound alert, every item with a 30 minute display alert, every item with a 25 minute sound alert, and so forth. I doubt this is actually what you have in mind. Perhaps a list of items that have @a fields?

Yes, that's what I had/have in mind.

More generally, maybe a "fields view" that would list all items with @a fields under the branch @a, all items with @b fields under @b and so forth? In each case, this would be a list of items and not instances so, like path view, only one instance of a repeating item would be shown with the "relevant" date/time displayed. I'm thinking @s, @e, @c, @k, @t, @u and perhaps some others should be omitted? Is this more like what you have in mind?

Yes! Such a View would be much preferred to the enhanced reporting capability I'd requested.

And Yes again -- "items" and not "instances" are the focus. I agree that fields which already form the basis for an existing View (or, in the case of @c, a section of the Agenda View) would not be useful to include in what I'm thinking of as this "data maintenance" view that we're discussing.

From your list of proposed exclusions, I would disagree about leaving @u out since, at present, I don't know how else one can see/access all the items which use that key and the values its assigned for each.

For the fields which are included, I'm visualizing a tree with level 1 being the keys (@u, @l, @p), level 2 showing a branch for each value assigned to each key, and level 3 showing the items associated with each value. Is that also what you have in mind?

I agree that location is a candidate for groupby, since someone might

actually want to group by the actual location, Arbys, Burger King, or whatever.

-Dan

therden mailto:notifications@github.com May 4, 2014 at 9:18 PM

Hello Dan,

I'm sorry that I wasn't clearer. I understood that the Report engine was/is working as designed; it was my intention to ask that the elements I listed be added to those recognized by it for grouping and sorting (and, I think, filtering -- right?).

My reason for asking is that I'm not otherwise seeing any way of even identifying all the items (among those in currently selected Calendars within etmTk) which have an alert set, have a "go to" file defined, are part of a task group, share a location, have an associated memo, or are assigned a priority. If the capability's there and I've missed it, please let me know.

Otherwise, thank you for considering yet another request from this particular "squeaky wheel."

-Thomas

On Sun, May 4, 2014 at 7:12 PM, dagraham notifications@github.com wrote:

From the user manual:

Groupby setting <#groupby-setting>

A semicolon separated list that determines how items will be grouped and sorted. Possible elements include/date specifications/and elements from

*

c: context

*

f: file path

*

k: keyword

*

t: tag

*

u: user

A/date specification/is either

• w: week number

or a combination of one or more of the following:

*

yy: 2-digit year

*

yyyy: 4-digit year

*

MM: month: 01 - 12

*

MMM: locale specific abbreviated month name: Jan - Dec

*

MMMM: locale specific month name: January - December

*

dd: month day: 01 - 31

*

ddd: locale specific abbreviated week day: Mon - Sun

*

dddd: locale specific week day: Monday - Sunday

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.

— Reply to this email directly or view it on

GitHub<https://github.com/dagraham/etm-tk/issues/3#issuecomment-42150299

.

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3#issuecomment-42153252.

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.

— Reply to this email directly or view it on GitHubhttps://github.com/dagraham/etm-tk/issues/3#issuecomment-42176029 .

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3#issuecomment-42256306.

therden mailto:notifications@github.com May 4, 2014 at 6:45 PM

Whereas using the report definitions "c t", "c u", and "c c" will generate reports with items listed by Tag, User, and Context, respectively, attempting to use "c a", "c g", "c j", "c l", "c m", "c n", and "c p" (among others; I didn't try all possible values) results in the error message ['invalid grpby setting'].

— Reply to this email directly or view it on GitHub https://github.com/dagraham/etm-tk/issues/3.