Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 308 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66085   Thu Nov 27 08:21:40 2008 Reply mike ciancimike2.cianci@comcast.netQuestion  Re: Sort Attributes

mike cianci wrote:

I am tring to sort  the attribute, subject, but it sorts with Z on top and A on the bottom. Is there anyway to reverse sort?

 Sorry, to bother you. Solved my own problem   " Reverse sort = 0"

  67451   Thu Feb 21 20:32:54 2013 Agree Garret Delarondegarret.delaronde@gmail.comQuestionWindows2.9Re: Sort Attribute = 0

Garret Delaronde wrote:

Hello All,

The subject is roughly what i'm asking about so here are the details. I have combed through the forums for an answer and didn't come up with anything regarding what i need.

Issue:

Below is what the logbook is setup as. However once there are more than 10 entries on the page, when a user views the logbook, elog automatically puts them to the higher value page # (ie entry number 11 is on page 2).

As I am sorting the entries by status and by Dist or Beat to organize entries for quicker viewing and access, I would prefer that elog always shows on page 1 when a user views the log book. The statuses are setup for sorting properly but when reverse sort is turned on, status "3-Closed" appears at the top instead of status "1-Open" to appear at the top, Status "2-Sent to Next Shift" next, then "3-Closed" after that.

Is there a to just view page 1 without doing the reverse sort?

 

Theme = default
Page Title = ELOG - $logbook
Entries per page = 10
Attributes = Entered By, Call Type, Date/Time Reported, Customer Name, Customer Phone Number, Location, Dist or Beat, Description, Badge, Updated By, Action Taken, Report Time, Status
List Display = Entered By, Call Type, Date/Time Reported, Customer Name, Location, Dist or Beat, Description, Badge, Updated By, Status
Locked Attributes = Entered By, Updated By
Preset Entered By = $long_name
Preset on edit Updated By = $long_name
Options Status = 1-Open, 2-Sent to Next Shift, 3-Closed
Preset Status = 1-Open
Cell Style Status 1-Open = background-color:red
Cell Style Status 2-Sent to Next Shift = background-color:yellow
Cell Style Status 3-Closed = background-color:green
Type Date/Time Reported = Datetime
Type Customer Phone Number = numeric
Type Report Time = Datetime
Sort Attributes = Status, Dist or Beat
Reverse sort = 0
Use Lock = 0
Summary lines = 0
Self Register = 0

Thanks in advance.

 

G

 

 Well it would appear i answered my own problem.

Start page = page1

 

  1442   Mon Oct 10 14:09:49 2005 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.6.0beta5Re: Some spell mistakes

Exaos Lee wrote:
I find some new strings from the warnings like this:

Quote:
Language error: string "HelpELCode" not found for language "chinese"


I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink".


Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much.
  1445   Mon Oct 10 19:26:35 2005 Reply Exaos LeeExaos.Lee@gmail.comRequestAll2.6.0beta5Re: Some spell mistakes

Quote:
Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much.

Sorry. Wink I will mail you first next time.
  69537   Sat Jul 2 14:39:41 2022 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.2Re: Slow performance

We have 68 logbooks and currently 60 GB data total. We run it as well on a VM, in our case with 8GB RAM.
The speed of ELOG is mostly given by the filesystem: when we had AFS it was very slow. With NFS it was better. But we now use a local disk on the VM: that is much better.
If you want to have the best performance (upload of large files can still slow down all users) then I would recomment local SSD for the file system of elogd.

You might talk to your system administrator: they can likely provide a local SSD on the VM server host.

Alan Grant wrote:

We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.

Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this?

 

  66714   Thu Feb 18 18:50:57 2010 Reply Yoshio ImaiQuestionAll2280Re: Single Button Entry

Geoff Ellis wrote:

For our application we have a lot of very common events we would like to log.  It would be preferable that for certain events/entries we could setup a single button / quick entry method.  Is there away to accomplish this?

You could write a script/program that calls the ELOG client with the necessary attributes to submit the entry (see the user's guide).

  66725   Sun Feb 28 07:25:10 2010 Reply Capt. Ben Smithben@maperl.comQuestionAll2280Re: Single Button Entry

Geoff Ellis wrote:

For our application we have a lot of very common events we would like to log.  It would be preferable that for certain events/entries we could setup a single button / quick entry method.  Is there away to accomplish this?

 This would be of value for me as well. I'm trying to develop a event log for a research ship. Thanks. -ben

  66727   Wed Mar 3 14:29:08 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2280Re: Single Button Entry

Capt. Ben Smith wrote:

Geoff Ellis wrote:

For our application we have a lot of very common events we would like to log.  It would be preferable that for certain events/entries we could setup a single button / quick entry method.  Is there away to accomplish this?

 This would be of value for me as well. I'm trying to develop a event log for a research ship. Thanks. -ben

There are several ways:

1) Use conditional attributes (see https://midas.psi.ch/elog/config.html#conditional). If you have several standard entries, put the into the option list of a "type" attribute. Then depending on that value, you can pre-populate other attributes/options. This is then not a single-button solution, but a single-click plus one selection from a drop-down list solution which should be pretty close.

2) You can make a bookmark in your browser. Take the URL of the logbook, add "?cmd=New" and then for each attribute you can select a preset value using "&p<attribute>=<value>". So for example on the demo logbook you can use

https://midas.psi.ch/elogs/Linux+Demo/?cmd=New&ptype=Routine&pcategory=General&pauthor=Ellis 

which opens the new entry dialog, and pre-set values for Type, Category and Author. Then you can make several bookmarks for different standard entries.

- Stefan

ELOG V3.1.5-3fb85fa6