How to sort on any field?, posted by John on Tue Apr 30 05:52:44 2019
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)
John |
Re: exclude access to a number of users in one logbook, posted by Stefan Ritt on Tue Apr 30 09:34:52 2019
|
You have a look here: elog:68936
| Nikolas Patronis wrote: |
|
How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?
|
|
|
Re: How to sort on any field?, posted by Andreas Luedeke on Tue Apr 30 14:20:34 2019
|
Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.
Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened. Screenshots are often very useful as well.
| John wrote: |
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)
John
|
|
Re: How to sort on any field?, posted by John on Tue Apr 30 19:07:17 2019
|
Hi Andrea and thank you soo much for your kind and prompt reply! I believe the issue will be solved as I have the information I need to proceed. I was just wanting to verify that sorting indeed is alloud on ALL fields. I cannot send the exact config as it is a work project, but I can replicate with fake fields and data if necessary in the future. I believe my errors are because I am either using field names which are 'special' to the system, or some other limitation. I will try compiling and see if that helps.
John
| Andreas Luedeke wrote: |
|
Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.
Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened. Screenshots are often very useful as well.
| John wrote: |
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)
John
|
|
|
|
Re: Last default = <n>, posted by Stefan Ritt on Wed May 1 11:06:04 2019
|
It works for me. Have you tried other values (1, 3, 7, ..)? The key is that the quick filter changes to "Last month". If it does not, there must be some trivial error, like type in elogd.cfg, you modify the wrong logbook, have a very old version of elog etc.
Stefan
| Alan Grant wrote: |
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
|
|
Re: Last default = <n>, posted by Stefan Ritt on Wed May 1 11:08:10 2019
|
You say "Show Last Default = 31". This options applies only to the "Find" page, the option "Last Default = 31" works for the quick filter. Probably you have to change "Show Last Default" to "Last Default".
Stefan
| Alan Grant wrote: |
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
|
Re: Last default = <n>, posted by Alan Grant on Wed May 1 15:28:41 2019 
|
I was just referring to "Show last default" (under Find) as a parallel example of how I assume "Last default" should function on the List page.
I also tried values 3 and 7 but "All entries" still displays in the "List period" box. A restart of elogd makes no difference.
Elog v3.1.2, Windows Server 2016 Std, 64 bit.
If you don't mind, I have attached my elogd.cfg. I realize you are quite busy so there is no rush. Thanks.
PS: I just noticed that the attached elogd.cfg indicates version 2.9.2 but it's actually 3.1.2 I have installed (just forgot to update the Welcome line).
| Stefan Ritt wrote: |
|
You say "Show Last Default = 31". This options applies only to the "Find" page, the option "Last Default = 31" works for the quick filter. Probably you have to change "Show Last Default" to "Last Default".
Stefan
| Alan Grant wrote: |
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
|
|
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 15:50:39 2019
|
I just tried your elogd.cfg, and it works fine for me. So no idea what is wrong in your case.
Stefan |
|