ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 356 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6456 Entries

Goto page Previous 1, 2, 3 ... 355, 356, 357 ... 805, 806, 807 Next

Author Email down

Sat Jan 2 01:34:57 2010

Collapse to Last and Quick Filter

Hello,
   I feel that the filter result could be confusing and unexpected when "COLLAPSE TO LAST" is enabled: you 
filter the first entry but you show the last one. What is filtered doesn't correspond with what is shown (look 
the attached example). 

I suggest to implement an option to let the user decide which entry (first or last) should be retrieved for 
filtering (a tentative patch is attached).

Thank you 

    Gabriele

P.S. A similar behaviour occurs when you sort the logbook: it could appear as not sorted because you sort the 
first entry but the last one is shown.

Attachment 1: example.txt

Example:

Consider the Status attribute to define the progress of a task:

Attributes     =  Author, Task, Status
Options Status =  Start, Step1, Step2, End
Thread Display =  Task, Status

and logbook with three thread arranged like this:

|-- Task0, Start
|   |-- Task0, Step1
|   |-- Task0, Step2
|
|-- Task1, Start
|   |-- Task1, Step1
|
|-- Task2, Start


It is collapsed to:

+-- Task0, Step2
+-- Task1, Step1
|-- Task2, Start

Now, if you filter the Status using the "Start" value, you obtain again:

+-- Task0, Step2
+-- Task1, Step1
|-- Task2, Start

In my opinion, this is a bit confusing.

Using Step1 or Step2 values, nothing is selected (also confusing).

Attachment 2: elogd.c.patch

Index: elogd.c
===================================================================
--- elogd.c	(revisione 2280)
+++ elogd.c	(copia locale)
@@ -19539,6 +19539,19 @@
          if (status != EL_SUCCESS)
             break;
 
+         if ( getcfg(lbs->name, "Filter last entry", str, sizeof(str)) && atoi(str) == 1 ) {
+            /* search last entry in this thread */
+            if (reply_to[0]) {
+               search_last_reply(msg_list[index].lbs, &message_id);
+               size = TEXT_SIZE;
+               status =
+                   el_retrieve(msg_list[index].lbs, message_id, date, attr_list, attrib, lbs->n_attr, text,
+                               &size, in_reply_to, reply_to, attachment, encoding, locked_by);
+               if (status != EL_SUCCESS)
+                  break;
+            }
+         }
+
          /* apply filter for attributes */
          for (i = 0; i < lbs->n_attr; i++) {

66690

Mon Jan 18 02:13:19 2010

Re: Collapse to Last and Quick Filter

Hello,
   I gave it a try using the svn version n. 2283 (12 Jan 2010).  The threaded display can be collapsed only if you don't 
apply any sorting. In the latter case, if you sort in some way ( with "Sort Attributes =" or "sort=" in the url), the 
thread cannot be collapsed anymore.

Also if I apply any filter from the quick filter bar, I cannot collapse the thread anymore (also without sorting). 

As example, these are the numbers of entries I obtain with my logbook :

  http://localhost:8080/mylogbook/?mode=threaded&expand=0     => 75 entries (OK)
  http://localhost:8080/mylogbook/?mode=threaded&expand=0&sort=EventID  =>  445 entries  (WRONG it should collapsed)
  http://localhost:8080/mylogbook/?mode=threaded&expand=0&Interaction=nuCC   => 335 entries 

However (considering the bug fixed for the collapsed thread display), breaking the thread is not a confortable solution. 
I choose to show the logbook in the threaded mode, because I'm interested in grouping the entries in threads. 
In my opinion, this feature is good (and it is my favourite) and should be preserved despite any sorting or filtering. 
This is why I suggest to ask to the user which entries (first or last) better applies for sorting and filtering. 

Ciao

   Gabriele


> You are absolutely right. When doing filtering, entries shown or not shown have not much to do with the filter. 
> Rather than messing around with first and last entries, I decided to break apart threads completely when doing 
> filtering, so the entries are treated as individual entries, just like what you do when filtering in summary mode. 
> This gives then consistent filtering results. The modification is done in revision 2282.

66691

Mon Jan 18 02:14:01 2010

Stefan Ritt wrote:

deletoille wrote:

Stefan Ritt wrote:

deletoille wrote:

Hello,

We would like to use more the quick filter command on attributes.

On the other hand, when we use it, the result does not displaying entries which are in answer of another attribute. Is there a command which allow that possibility like when we select display full entries in the search mode?

Thanks in advance

Xavier

I don't understand your questions. Can you please give an example.

Sorry for my english. In fact, i found the answer by myself. But I ll explain to you.

in attachement 1, a small part of our ELOG. When I choose FBT in the quick filter "groupe incriminé". Elog respond that there is no entrie found (attachement 2)

But, with the find function, when i select display full entries and FBT in "groupe incriminé", Elog show the entrie ( attachement 3).

I found the answer. In fact, Elog respond no entrie when threaded is selected. I have to choose Full or summary for that working.

sorry

Xavier

Actually what you report is a bug. The filtering does not work in threaded display mode, only in summary and full. I fixed that bug in the current SVN version, so if you download and compile it, you can give it a try. The fix will be contained in the next official release.

Hello,

I gave it a try. See: https://midas.psi.ch/elogs/Forum/66690

Gabriele

69283

Wed Dec 16 12:41:42 2020

Simon D�ster

simon.daester+elog@gmail.com

Info

Windows

ELOG V3.1.4-a04

Re: How to increase TEXT_SIZE to address entry text limit

Hi Illam

You actually have to change the source code of elog and then recompile. Download the code from https://bitbucket.org/ritt/elog/src/master/, change the value of the variable TEXT_SIZE in the file src/elogd.h

Default ist #define TEXT_SIZE 250000

Illam Pakkirisamy wrote:

Hi,

I'm trying to increase the entry text constraint but not sure how to do this. Couldn't find it in the documentation or may be I missed it. Appreciate your help.

Thanks.
Illam

67140

Tue Nov 1 01:29:59 2011

Hi,

I'm currently trying to setup a logbook which will contain process descriptions. One of the attributes will be the resists that are used. This could be more than one resist, hence I try to use MOptions but users should also be able to add materials to the selection list. When I write the following, I get some problems though:

Required Attributes = Name, Author, Resists
MOptions Resists = Nano Copolymer EL-10, S1813
Extendable options = Resists

If a user wants to add a resist, he gets a textbox to add the new resist (which will contain what was already toggled), but there is now way to select also other resists that are already available, without saving the post and than edit it again. Previously selected resists are deselected when a new resist is added (if the user had emptied the textbox) and one can not save the newly added attribute option without saving the whole entry.

Is there a nice way to implement this (am I overlooking an obvious solution), or is this not possible at all. I guess an ideal solution would be to get some sort of ok button when one adds an attribute option and after confirming the new value that one gets back to the checkboxes without exiting the edit mode.

Regards,

Michaël

PS: This is the complete config for this logbook:

Theme = default
Page Title = $logbook - $Name
Edit Page Title = $logbook
Comment = Photolithography Processes

Quick filter = Name, Resists
Preset Author = $long_name
Reverse sort = 1

Attributes = Name, Author, Resists
Sort Attributes = Resists, Name, Author
Required Attributes = Name, Author, Resists
MOptions Resists = Nano Copolymer EL-10, S1813
Extendable options = Resists
Sort Attribute Options Resists = 1

List display = Name, Author, Resists

1895

Mon Aug 14 11:45:32 2006

Silvia Borghi

silvia.borghi@cern.ch

Question

Author in duplicate message

When I ask to duplicate a message, the author of the duplicated message is the one of the original message.
How can I put as author the name of the person that is login?
I tried to use the command Preset on Duplicate Author or Subst on Duplicate Author, but it does not work.

Here is my config:

Preset Author = $long_name
Preset on Duplicate Author = $long_name
Preset on Reply Author = $long_name
Subst on Duplicate Author = $long_name
Locked Attributes = Author

69728

Tue Feb 20 11:44:30 2024

ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer

Hi,

As there is no ELOG available in Epel repository for Rocky9, I tried to install ELOG from https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm and ended with the below error in Rocky 9.

=======================================
[root@test.com]# wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
--2024-02-20 10:11:32-- https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
Resolving elog.psi.ch (elog.psi.ch)... 192.33.120.112
Connecting to elog.psi.ch (elog.psi.ch)|192.33.120.112|:443... connected.
ERROR: The certificate of ‘elog.psi.ch’ is not trusted.
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer.
=======================================

Could someone guide me on how to install Elog in Rocky 9 securely?

69729

Tue Feb 20 11:49:19 2024

ERROR: The certificate of �elog.psi.ch� doesn't have a known issuer

Goto page Previous 1, 2, 3 ... 355, 356, 357 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6