Configure default time range in 'Find', posted by Eoin Butler on Fri Jan 16 13:41:18 2015
|
Hello,
We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog
for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks |
Re: Configure default time range in 'Find', posted by Stefan Ritt on Fri Jan 16 14:29:58 2015
|
Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
Eoin
Butler wrote:
Hello, |
|
Re: Configure default time range in 'Find', posted by Eoin Butler on Mon Jan 19 11:09:31 2015
|
Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally
takes a long time. It would be much better if one could configure it to default to something "fast".
Stefan |
Re: Configure default time range in 'Find', posted by David Pilgram on Mon Jan 19 17:17:32 2015
|
Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated)
"All time" to "Day", and added back in an "All Time" option at the very bottom. This gives a default of searching the
last day, and one has to think and select the period of time to search back on. |
Re: Configure default time range in 'Find', posted by David Pilgram on Tue Jan 20 00:58:58 2015
|
It has just occurred to me that you may also have to check the non-English files, (./resorces/eloglang_xxxx) as this change introduces a new term "All
time" that would need translation into the other lexicons.
|
|
Re: Configure default time range in 'Find', posted by Stefan Ritt on Thu Jan 22 16:30:07 2015
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good
idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so
if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT |
|
Re: Configure default time range in 'Find', posted by Eoin Butler on Thu Jan 22 17:04:03 2015
|
This looks like exactly what I wanted, thanks!
Stefan
Ritt wrote:
I added a new optoin "Show last default = <days>", where |
|
Re: Configure default time range in 'Find', posted by David Pilgram on Thu Jan 22 17:32:16 2015
|
If my coding had been up to it, I would have done this and submitted... thanks Stefan.
Stefan
Ritt wrote:
I added a new optoin "Show last default = <days>", where |
|
Re: Configure default time range in 'Find', posted by David Pilgram on Sun Mar 15 16:41:49 2015
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive
many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets |
|
Re: Configure default time range in 'Find', posted by David Pilgram on Sun Mar 15 17:53:44 2015
|
Law of unintended consequences came into play. If you use 0, then on the results page it says "Restricted search to last 0 Days".
So that also needs tweeking, and that's really put my c coding (or lack of it) to the test. But I've changed that phrase to "Unrestricted
search" followed by blank for when the parameter "last" is 0. |
Re: Configure default time range in 'Find', posted by Andreas Luedeke on Mon Mar 16 07:16:56 2015
|
Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It
is at least in my logbook.
Cheers
Andreas
David Pilgram wrote:
Hi Stefan, |
|
Re: Configure default time range in 'Find', posted by David Pilgram on Mon Mar 16 13:51:11 2015
|
Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration
file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default |
|
Re: Configure default time range in 'Find', posted by Andreas Luedeke on Tue Mar 17 07:04:44 2015
|
Hi David,
I was confused because one normally does not need to include a line in the configuration to set a default value. A default
is exactly what you get if you don't specify anything in the configuration
But I think I've figured it out: you were overriding the default in the global section for all logbooks and |
|
Re: Configure default time range in 'Find', posted by Stefan Ritt on Tue Mar 24 15:49:28 2015
|
Show last default = 0
always worked, even in my original code. It was just not documented. I added that.
Andreas |
|
How to change configuration already set properly, posted by Banata Wachid Ridwan on Wed Mar 18 04:25:14 2015
|
Hello, I have configuration file that already set on running logbook
but I want to change for example category and Atributes, and some other setting to match our language
If I just simply change category, or other option, when I log in on logbook, It wont show as I though. When I change back to original setting, |
|
Re: How to change configuration already set properly, posted by Andreas Luedeke on Wed Mar 18 09:34:46 2015
|
ELOG does not provide you with a simple mechanism to rename attributes in existing entries.
If you rename an attribute in the configuration,
then you need to adapt all existing entries by replacing the name in all *a.log files on the server.
Or you could set-up a second logbook
with the renamed attributes, export all entries from the first logbook (use "Find") and import these entries in the second logbook.
|
|
Re: How to change configuration already set properly, posted by Banata Wachid Ridwan on Fri Mar 20 08:11:15 2015
|
ok.
what *a.log ? is it all database from elog? so I need to open it with text editor and replace all . am I Correct?
|
|
Re: How to change configuration already set properly, posted by Andreas Luedeke on Fri Mar 20 09:23:57 2015
|
ELOG is storing all entries as text files. Open text files and use search and replace in text editor. Or instead: export with Find and import in another
ELOG with renamed attributes.
Banata |
|
Is it possible to only send an email based on the value of multiple attributes?, posted by Darren Hollinrake on Mon Mar 9 17:03:38 2015
|
My current setup notifies users if downtime = yes.
[CODE]Email Downtime Yes = user1@xyz.com, user2@xyz.com[/CODE]
|
|
Re: Is it possible to only send an email based on the value of multiple attributes?, posted by Stefan Ritt on Mon Mar 9 17:24:42 2015
|
[quote="Darren Hollinrake"]My current setup notifies users if downtime = yes.
[CODE]Email Downtime Yes = user1@xyz.com, user2@xyz.com[/CODE]
|
|
Re: Is it possible to only send an email based on the value of multiple attributes?, posted by Andreas Luedeke on Thu Mar 12 09:53:57 2015
|
[quote="Darren Hollinrake"]My current setup notifies users if downtime = yes.
[CODE]Email Downtime Yes = user1@xyz.com, user2@xyz.com[/CODE]
|
|
Elog stability with multiple users, posted by Alan Grant on Wed Feb 18 04:57:32 2015
|
Are there any known or reported daemon stability issues with an increase of concurrent users logged in to view and search entries, while the elog client
is also adding 5 to 10 new entries every minute during a peak 2-hour period each day? |
|
Re: Elog stability with multiple users, posted by Stefan Ritt on Thu Feb 26 10:39:58 2015
|
By desing, there is no collision between different users, since all requests are executed in sequence (single thread). The only problem is that the server
becomes unavailable for others if it executes a long search. This is why most users of large lobooks restrict their search to let's say the last month
or so by default. This speeds up the search and limits the dead time for others. This can be done via the show |
|
Re: Elog stability with multiple users, posted by Alan Grant on Fri Feb 27 23:06:53 2015
|
We have reduced entries for Search reasons by removing older text files and that seems to speed up things.
However, a recurring problem persists during peak period where the service connection is lost (site says "Not
found" on both client and directly on server), and it cannot be restarted or killed. Only a reboot of the 2010
|
|
Re: Elog stability with multiple users, posted by David Pilgram on Sat Feb 28 14:08:43 2015
|
I grant that this may be a complete red herring, but your description below - not available and having to reboot -
might have another explanation. At least in Linux.
|
|
Re: Elog stability with multiple users, posted by Stefan Ritt on Mon Mar 2 08:06:38 2015
|
Being not able to kill a server running in an endless loop seems strange to me. If you put any program artificially into an endless loop, you can kill it
via "kill -9 <pid>". Have you tried that? The only exception I
can imagine is if there is a problem in the file system, like your elog logbooks are mounted via NFS or some other remote filesystem, and you have a problem |
|
Enter past date for logbook, posted by Banata Wachid Ridwan on Wed Feb 25 03:28:24 2015
|
Is it possible to enter past date in logbook
I forgot to enter log yesterday, is it possible to add up now? |
|
Re: Enter past date for logbook, posted by Stefan Ritt on Wed Feb 25 07:52:21 2015
|
No. The date/time tag is there to actually document the time when the log was made. If you are late, you are late.
Banata
Wachid Ridwan wrote:
Is it possible to enter past date in logbook |
|
Re: Enter past date for logbook, posted by Andreas Luedeke on Wed Feb 25 08:41:59 2015
|
As an administrator of the logbook you could add an additional attribute, e.g. "when" of type datetime.
Each entry would then have the unchangeable entry time and an addtional time, e.g. of the event you are describing in the entry.
For more details look here: elog:67712 |
|
maximum attributes for drop down menu., posted by rob on Fri Feb 20 11:04:03 2015
|
We use a servername field to be able to select a server.
When i entered my entire serverlist (574 entries), only 250 of them show up.
|
|
Re: maximum attributes for drop down menu., posted by David Pilgram on Fri Feb 20 16:18:36 2015
|
Hi Rob,
I don't think the default number of 100 has ever changed. However, you can change the number in the source
|
|
Fail to install in mac, posted by Alex on Fri Feb 13 16:43:00 2015
|
Hi
I am trying to install to mac 10.10.2 - everything works almost fine, but when I issue the sudo make install I get |
Re: Fail to install in mac, posted by Stefan Ritt on Fri Feb 13 19:47:43 2015 
|
Sorry I forgot to include the elogd.plist file in the distribution. I attached it to this entry, so just copy it into the elog root directory and run
again "make install".
/Stefan |
|
Re: Fail to install in mac, posted by Alex on Fri Feb 13 20:36:59 2015
|
Thanks! now install works fine - but I cannot find how to open and start writing- I do
/usr/local/sbin/elogd |
|
Re: Fail to install in mac, posted by Stefan Ritt on Fri Feb 13 21:18:46 2015
|
Point your browser to http://localhost:8080 as written in the documentation
Alex
wrote:
Thanks! now install works fine - but I cannot find how to open and start |
|
Link to full resolution image attachments, posted by Eric Quintero on Mon Jan 26 23:13:47 2015
|
Hi all,
It's possible my question is entirely within the domain of CKeditor, but I figure it may also have something to do with how it's plugged
into ELOG. |
|
Re: Link to full resolution image attachments, posted by Stefan Ritt on Tue Jan 27 17:03:53 2015
|
Strange. If I attach a big image to this post (see below), I see the thumbnail, but when I click on it it, I get redirected to the full resolution image.
No idea why it is not working for you.
Eric |
|
Re: Link to full resolution image attachments, posted by Eric Quintero on Wed Jan 28 17:18:08 2015
|
Stefan Ritt
wrote:
Strange. If I attach a big image to this post (see below), I see the thumbnail,
but when I click on it it, I get redirected to the full resolution image. No idea why it is not working for you. |
|
Re: Link to full resolution image attachments, posted by Eric Quintero on Fri Jan 30 22:45:02 2015
|
Since I am unable to attach an image to this logbook, I made a post over the the Linux Demo logbook showing an image that was uploaded with the CKeditor
toolbar "Image" button that doesn't link to the full resolution image.
Incidentially, Dario Milicic's recent commit to the git repository (83a10a5), adds the exact functionality I'm looking for to drag-and-drop |
|
Re: Link to full resolution image attachments, posted by Andreas Luedeke on Mon Feb 2 10:40:38 2015
|
If you add the picture in the HTML editor, then you can add any link you like.
I don't see why the specific link to the full resolution
picture should be the default.
If you want to have it, why not just add it by hand?
I took the liberty to edit your Linux Demo
post accordingly.
For attachments that is a completely different story, since you cannot add any links there, only ELOG can do this |
|
Re: Link to full resolution image attachments, posted by Eric Quintero on Wed Feb 4 08:51:37 2015
|
You make a valid point!
My perspective is from my lab's specific use case, in which we often post plots of data in the body of the text, and it is useful for the
ELOG-generated thumbnails to link to the full resolution plot. In previous versions, I believe this was the behavior. It would be convenient for my users |
|
Re: Link to full resolution image attachments, posted by Stefan Ritt on Wed Feb 4 13:32:21 2015
|
I put the functionality you requested into the current GIT version of ELOG. It works now with Drag & Drop, but not (yet) with the toolbar uploader.
Eric
Quintero wrote:
You make a valid point! |