Attribute option "+x" not searcheable, posted by Stefano Lacaprara on Mon Oct 23 11:47:50 2017
|
Dear experts,
I have an elog with an attribute with fixed values, like this:
Attributes = Half
Options Half = +x, -x, both
It works fine, but I would like to find (or quick filter) all entries with Half=+x .
If I go to the search form, I can select +x from the dropdown menu for Half, but the search returns no result, even if I do have a number of entries with Half=+x. Likewise if I try to do the same with Quick filter.
I believe that this is due to the fact that the search uses regex, and "+" is reserved. I've tried to perform a search by entering manually and escaped "\+x", and it works as intended.
https://.../?mode=summary&reverse=0&reverse=1&npp=20&Half=%5E%5C%2Bx%24
However, since this attribute has a list of fixed values, it is not possible to entry manually something different "\+x" than what is defined in the config, that is "+x".
Is there a solution for this problem?
I would rather not change the attributes options (to, say, positive/negative), since that would mean changing manually a non negligible number of entries.
thanks,
Stefano |
Re: Attribute option "+x" not searcheable, posted by Andreas Luedeke on Sat Oct 28 09:12:32 2017
|
Hi Stefano,
you could try to html encode the "+" and "-" sign in the option list
Options Half = +x, -x, both
Allow HTML = 1
But of course then you would need to change all existing entries.
It is just an idea; I did not try this out, it might not work anyway.
Cheers
Andreas
> Dear experts,
> I have an elog with an attribute with fixed values, like this:
>
> Attributes = Half
> Options Half = +x, -x, both
>
> It works fine, but I would like to find (or quick filter) all entries with Half=+x .
>
> If I go to the search form, I can select +x from the dropdown menu for Half, but the search returns no result, even if I do have a number of entries with Half=+x. Likewise if I try to do the same with Quick filter.
>
> I believe that this is due to the fact that the search uses regex, and "+" is reserved. I've tried to perform a search by entering manually and escaped "\+x", and it works as intended.
>
> https://.../?mode=summary&reverse=0&reverse=1&npp=20&Half=%5E%5C%2Bx%24
>
> However, since this attribute has a list of fixed values, it is not possible to entry manually something different "\+x" than what is defined in the config, that is "+x".
>
> Is there a solution for this problem?
>
> I would rather not change the attributes options (to, say, positive/negative), since that would mean changing manually a non negligible number of entries.
>
> thanks,
> Stefano |
Re: Attribute option "+x" not searcheable, posted by Andreas Luedeke on Tue Oct 31 16:56:24 2017
|
Hi Stefano,
I've tested it: it does not work.
Neither in edit nor in list view the HTML encoded characters show correctly.
Only in the "Quick filter" menu they show as they should!
But then selecting them in the quick filter will not find any entries :-(
So the short answer:
avoid characters with a special meaning for regular-expressions in attribute values, in particular if you want to use quick filters.
Cheers
Andreas
> Hi Stefano,
> you could try to html encode the "+" and "-" sign in the option list
> Options Half = +x, -x, both
> Allow HTML = 1
>
> But of course then you would need to change all existing entries.
>
> It is just an idea; I did not try this out, it might not work anyway.
>
> Cheers
> Andreas
>
> > Dear experts,
> > I have an elog with an attribute with fixed values, like this:
> >
> > Attributes = Half
> > Options Half = +x, -x, both
> >
> > It works fine, but I would like to find (or quick filter) all entries with Half=+x .
> >
> > If I go to the search form, I can select +x from the dropdown menu for Half, but the search returns no result, even if I do have a number of entries with Half=+x. Likewise if I try to do the same with Quick filter.
> >
> > I believe that this is due to the fact that the search uses regex, and "+" is reserved. I've tried to perform a search by entering manually and escaped "\+x", and it works as intended.
> >
> > https://.../?mode=summary&reverse=0&reverse=1&npp=20&Half=%5E%5C%2Bx%24
> >
> > However, since this attribute has a list of fixed values, it is not possible to entry manually something different "\+x" than what is defined in the config, that is "+x".
> >
> > Is there a solution for this problem?
> >
> > I would rather not change the attributes options (to, say, positive/negative), since that would mean changing manually a non negligible number of entries.
> >
> > thanks,
> > Stefano |
Date must be between 1970 and 2037??, posted by Tim Schelfhout on Wed Oct 11 15:55:02 2017
|
Hey there,
Trying to record birthdates in ELOG ... field type being date results in error:
Date must be between 1970 and 2037 |
Can this be avoided? I like the fact that one can use the date picker to enter birthdate |
Format Form, posted by Tim Schelfhout on Mon Oct 2 12:55:18 2017
|
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using "Format Leeftijd=1, attribname, 3, 3", which solves the field title
but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
Re: Format Form, posted by Stefan Ritt on Mon Oct 2 14:58:32 2017
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width, number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript.
Stefan
Tim Schelfhout wrote: |
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using this (Format Leeftijd=1, attribname, 3, 3), but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
|
Re: Format Form, posted by Tim Schelfhout on Mon Oct 2 15:20:04 2017
|
Thankx 4 the quick reply Stefan. The link you provided does not work .... could you point me again in the
right direction? Where can I find more info on this ability?
Thankx
Stefan Ritt wrote:
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width, number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript.
Stefan
Tim Schelfhout wrote: |
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using this (Format Leeftijd=1, attribname, 3, 3), but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
|
|
Re: Format Form, posted by Stefan Ritt on Mon Oct 2 15:53:39 2017
|
The link does now work in the email, but if you go to the web interface of the forum it does work.
Anyhow, you can go directly to https://midas.psi.ch/elogs/Forum/66909
Stefan
Tim Schelfhout wrote: |
Thankx 4 the quick reply Stefan. The link you provided does not work .... could you point me again in the
right direction? Where can I find more info on this ability?
Thankx
Stefan Ritt wrote:
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width, number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript.
Stefan
Tim Schelfhout wrote: |
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using this (Format Leeftijd=1, attribname, 3, 3), but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
|
|
|
Email fields - accept semicolons too, posted by Ben Shepherd on Wed Sep 20 16:34:18 2017
|
My elog has a field for entering a list of email addresses, which goes into the "Email All" attribute. They need to be comma-separated, and an error is thrown if semicolons are used instead. Would it be possible to automatically change semicolons into commas before attempting to send the mail via SMTP? Neither character is allowed in email addresses so it shouldn't break anything to just do that silently. Thanks! |
Elog System Requirements, posted by Alan Grant on Fri Sep 15 00:56:38 2017
|
In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome. |
Re: Elog System Requirements, posted by Andreas Luedeke on Fri Sep 15 15:16:42 2017
|
Hi Alan,
we run our ELOG server (38 GB Logbook data in about 50 logbooks dating back up to 16 years) on a virtual Linux box.
The memory is important, since ELOG scans through all entries and creates an index at start-up. But we have only about 6% used out of 2GB: ELOG is not very demanding. If you have many and large pictures attached, then "convert" needs a bit of memory to work with.
Since "elogd" is a single task, you will not gain much from many CPUs. File IO is often a limiting factor: we've tried a while to run the logbook data on an AFS directory, and that did not turn out well. A local disk is best, an NFS disk works fine as well (in our case).
Cheers, Andreas
Alan Grant wrote: |
In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome.
|
|
javascript?, posted by Tim Schelfhout on Mon Sep 4 11:56:47 2017
|
Is there anyone out there who can help me get started using javascript in elog ? Is there an example somewhere ... i suppose you put the code in the
scripts folder?
Basically I am trying to calculate age of an added person in the database and display it after the birthdate field. I want to do other stuff, but once I know how
the interaction is done I can proceed.
Thankx heaps
Great job btw with this ELOG ... been using it for years now. I see you can add forms with html also, this might interest me for the future.
|
Re: javascript?, posted by Andreas Luedeke on Mon Sep 4 13:19:33 2017
|
This logbook, the forum, provides some javascript code. The code is simply referenced in the footer (Bottom text = <file> | <string> ).
<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.6.0/styles/default.min.css"><script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.6.0/highlight.min.js"></script><script>hljs.initHighlightingOnLoad();</script>
There's another example under elog:contributions/39
Cheers, Andreas
Tim Schelfhout wrote: |
Is there anyone out there who can help me get started using javascript in elog ? Is there an example somewhere ... i suppose you put the code in the
scripts folder?
Basically I am trying to calculate age of an added person in the database and display it after the birthdate field. I want to do other stuff, but once I know how
the interaction is done I can proceed.
Thankx heaps
Great job btw with this ELOG ... been using it for years now. I see you can add forms with html also, this might interest me for the future.
|
|
edit elog config via elog web interface, posted by Tim Schelfhout on Mon Sep 4 11:22:05 2017
|
Hello,
Is it possible to edit the entire elog config file via the elog frontend? I see the config button
on some screens but it only allows me to change user and password??
Thankx |
Re: edit elog config via elog web interface, posted by Andreas Luedeke on Mon Sep 4 13:08:35 2017
|
On the right side of "Change password" you should find "Change config file".
But you'll only see this, if the user has admin priviledges defined in the config file: "Admin user = <user>"

Then you can edit the configuration of that logbook. At the top you'll have a button "Change [global]" to edit the global part of the configuration - if you have the relevant priviledges to do so.
Tim Schelfhout wrote: |
Hello,
Is it possible to edit the entire elog config file via the elog frontend? I see the config button
on some screens but it only allows me to change user and password??
Thankx
|
|
Problems with german_UTF8 language, posted by Andreas Luedeke on Mon Aug 21 11:22:09 2017 
|
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas |
Re: Problems with german_UTF8 language, posted by Andreas Luedeke on Wed Aug 23 15:11:32 2017
|
Just an update: I've re-compiled, reinstalled and restarted elogd for other reasons and now the corrupted strings are all gone. Everthing looks fine now.
But I never worry when a problem goes away before I could understand it: I'm confident that I will have plenty of time later, when the problem magically re-appears - likely I'll be called on a Friday night :-)
Andreas Luedeke wrote: |
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas
|
|
|