Re: pre defined Find as Home page, posted by Andreas Luedeke on Thu Apr 6 11:01:30 2017
|
It's very simple, no need for the find command. E.g.: Start page = ?Author=luedeke&Category=Question&mode=summary
in this forum would do https://midas.psi.ch/elogs/Forum/?Author=luedeke&Category=Question&mode=summary
| Paraic Fahey wrote: |
|
This command makes the Homepage a FIND page: Start page = ?cmd=Find
My question is: can we pre-populate some of the search fields and execute the search so that the homepage becomes the SEARCH RESULTS
|
|
Re: rename menu commands , posted by Andreas Luedeke on Tue Apr 11 22:44:40 2017
|
Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):
Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:
- New - Enter new logbook entry
- Edit - Edit current logbook entry
- Delete - Delete current logbook entry
- Reply - Submit a reply to current entry
- Duplicate - Duplicate the current entry with the possibility to change some values
- [...]
- Copy to - Copy entry to other logbook
- [...]
The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:
Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
| Francois Cloutier wrote: |
|
Hi !
I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).
I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ?
Thanks for your help !
|
|
|
Re: Limiting search data, posted by Andreas Luedeke on Fri Apr 28 11:59:30 2017
|
I think I understand the question (although I have no answer):
When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.
If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.
In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.
| Stefan Ritt wrote: |
|
I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?
| Alan Grant wrote: |
|
I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.
|
|
|
Re: inactive users, posted by Andreas Luedeke on Wed May 31 13:28:51 2017
|
> Hi,
> I reopen this old thread since I'm having a similar problem.
>
> I'm running ELOG V3.1.1-0767eb0 on ubuntu with webserver authentication, and I'd like to remove 'active' checkbox as well.
>
> The problem that we found is that if any user click on the [Set None] button at the bottom of the Config page in order to unsubscribe from all mail notification,
> *all* the checkbox are toggled, not only those for the email notification. And this includes also the "active user" as well.
I can confirm that this bug is present even in this forum and in my current version (ELOG V3.1.3-aded4ae).
And I am positive that this is a bug: it was certainly not the intended behaviour. |
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 08:50:16 2017
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
Re: Weird behaviour of category filter, posted by Andreas Luedeke on Wed Jul 19 08:58:51 2017
|
Hi Daniel,
I agree: it should. And it does in my case; it works perfectly fine for my logbooks. Maybe you should have a closer look for special characters in you configuration? Otherwise I don't know why it does not work for you.
If you haven't figured it out already you would need to send a working snippet of your logbook configuration together with a minimal collection of entries that are filtered wrongly.
Cheers, Andreas
| Daniel Sajdyk wrote: |
|
Hello.
Today I noticed that when I use category filter in the top, right of Elog I got different results, that depends on that if I select Category and Subcategory or just Subcategory option.
What I mean.
- When I select category Software (in Polish "Oprogramowanie") and subcategory Antywirus I got results that have only this subcategory specified (screenshot Category-Software_and_Subcategory-Antywirus.png)
- But when I write by myself Antywirus (which is subcategory of Software) in subcategory option (category leave as default), then I got results that have this, and other subcategories specified (screenshot Subcategory-Antivirus.png).
In my opinion in first example Elog shoud also displays all entries that have Antywirus subcategory specified. Not only when it is the only subcategory.
Sorry, for my english, but I have hope that you can understand what I mean.
Daniel
|
|
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 10:14:44 2017
|
If that is your command then it is obvious why no email is send:
you do set "Type=Type", but only for "Type=Problem(s)" and "Category=TDAQ" you would send an email.
Instead of writing "-h host" you should as well define the actual hostname, like "-h midas.psi.ch", likewise for all other parameter.
| Phil Rubin wrote: |
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text. The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.
For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.
Sorry for forgetting these details: bash shell; linus version 2.6.32-696.el6.x86_64
| Andreas Luedeke wrote: |
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
|
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 13:37:33 2017
|
Okay, I can confirm that this does not work. It is likely related to the disclaimer in the ELOG documentation (https://midas.psi.ch/elog/config.html#conditional)
Conditional attributes are usually only used for change items in the entry form.
I guess that the "Email" command never worked with conditional attributes. I use the "Email" command and conditional attributes extensively, but I've never tried before to use "Email" in a condition.
I've tested the functionality with the following minimal configuration for the latest ELOG version 3.1.3-aded4ae :
Attributes = A, B
Options A = X{1}, Y{2}
Options B = N, M
{2} Email B M = andreas.luedeke@psi.ch
The following elog command creates the desired entry, but does not send out an email. Creating the identical entry via the web form does initiate the email.
elog -u <user> <password> -h <host> -p 80 -l <logbook> -a "A=Y" -a "B=M" -n 1 "entry by elog cmd"
Thank you Phil for pointing out the problem.
Cheers, Andreas
| Phil Rubin wrote: |
|
I didn't realize you required every detail of the command, since the entry is being logged, but here is an example (only the user information is blanked out):
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author=Rubin -a Type=Problem\(s\) -a Category=Elog -a Subject="Client Initiated E-mail Notification" "Tests"
From elogd.cfg:
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = Access, Beam, CHANTI, CHOD, Computer/Network, DCS/DSS, Elog,
GTK, HASC, IRC/SAC, KTAG, LAV, LKr, MUV, NewCHOD, Online Monitor, RICH, Run, Run
Control, Shift, STRAW, TDAQ
{1} Email Category Elog =
{2} Email Category Elog = Philip.Rubin@cern.ch
{3} Email Category Elog =
The TDAQ-category command that is misbehaving is essentially identical:
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author="Run Control" -a Type=Problem\(s\) -a Category=TDAQ -a Subject="Board Reload" "KTAG4"
| Andreas Luedeke wrote: |
|
If that is your command then it is obvious why no email is send:
you do set "Type=Type", but only for "Type=Problem(s)" and "Category=TDAQ" you would send an email.
Instead of writing "-h host" you should as well define the actual hostname, like "-h midas.psi.ch", likewise for all other parameter.
| Phil Rubin wrote: |
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text. The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.
For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.
Sorry for forgetting these details: bash shell; linus version 2.6.32-696.el6.x86_64
| Andreas Luedeke wrote: |
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
|
|
|
|