Let the user decide which columns should be displayed, posted by Sarah Kuckuk on Thu Jan 18 13:56:59 2024
|
Hello
I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot
of fields and it would help the usefulness of our elog a lot. |
Re: Let the user decide which columns should be displayed, posted by Stefan Ritt on Mon Jan 22 12:15:26 2024
|
There is a general display option "List display", but that applies for all users. For the download, you can load the CSV file into a spreadsheet
program and then delete some columns.
Stefan |
Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 11:06:49 2024
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks! |
|
Re: Maximum number of attributes, posted by Stefan Ritt on Mon Jan 8 11:08:14 2024
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than
100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best, |
|
Re: Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 11:42:08 2024
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best, |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 15:56:40 2024
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix
"I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a
number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. |
|
Re: Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 16:18:45 2024
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow
their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but
maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome. |
|
Re: Maximum number of attributes, posted by Stefan Ritt on Mon Jan 8 16:25:05 2024
|
Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in
full text search.
Stefan |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 17:30:42 2024
|
Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would
increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
Stefan |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 21:08:43 2024
|
As for my suggestion earlier, now I'm at my computer with working elog. I think that the following four lines (three I guess already there but need
alteration for this) need to appear in your elogd.conf file. The first three should also include any other thing you need to display etc. I've
cut this down to the bear bones, and ... means anything else you want to add. |
|
Restricting entries view by user, posted by Leonardo Tacconi on Thu Nov 2 11:38:36 2023
|
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements. |
|
Re: Restricting entries view by user, posted by Stefan Ritt on Thu Nov 2 11:46:42 2023
|
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
Leonardo |
|
Re: Restricting entries view by user, posted by Matteo Mannini on Tue Nov 7 22:07:24 2023
|
Dear Stefan,
thanks to the answer you gave to my colleague.
Now, attempting to follow your suggestion... If we will create several logbooks, one for each user, |
|
Re: Restricting entries view by user, posted by Stefan Ritt on Thu Nov 30 14:28:12 2023
|
Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict
edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.
Stefan |
|
Cannot send Emails, posted by John on Mon Oct 23 20:35:54 2023
|
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending
to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years
with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. |
|
Re: Cannot send Emails, posted by Stefan Ritt on Tue Oct 24 08:12:38 2023
|
ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince
your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.
Stefan |
|
Fail to upload enclosure in ELOG , posted by Laurent Jean-Rigaud on Mon Jan 16 20:18:12 2023
|
Hi,
I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to
use it on Synology NAS server, associated with local LDAP server. |
|
Re: Fail to upload enclosure in ELOG , posted by Laurent Jean-Rigaud on Wed Oct 11 23:09:36 2023
|
Ok, i reply to myself as i could resolve the problem by changing the alpine Linux image to Debian light.
After debugging, the problem seems to be the compilation option used for alpine packets, which is not fully compatible when running on NAS Intel
cpu. |
link to attachment within html editor, posted by Celeste Torkzaban on Mon Oct 9 10:43:46 2023 
|
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to
work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the |
|
Re: link to attachment within html editor, posted by Stefan Ritt on Mon Oct 9 12:30:44 2023
|
You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG
But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry
has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in. |
Re: link to attachment within html editor, posted by Celeste Torkzaban on Mon Oct 9 16:43:06 2023
|
thank you!
Stefan
Ritt wrote:
You can always insert the full link to the attachment like this one: |
|
Filtered browsing, posted by Michael on Fri Oct 6 11:19:34 2023
|
Hi,
is there a trick to get "Filtered browsing" working?
If i am on the first entry and i checked the checkbox of one Attribute, the next entry is still the second one and not the next with the |
elog server crashed due to cookies send by client, posted by Heinz Junkes on Mon Sep 18 13:49:05 2023
|
Our elog instance (elogd 3.1.4 built Jan 13 2021, 20:44:20 revision ce2a48e9) has been running for years without any problems.
We have a new user who consistently crashes the elog:
GET /Omicron-STM-XPS/?rsort=Record%20date HTTP/1.1 |
|
Re: elog server crashed due to cookies send by client, posted by Heinz Junkes on Tue Sep 19 10:58:14 2023
|
The server is crached because the author field was accidentally filled with a long string due to an automated (remote) script:
“
Author: The ion getter pump has successfully recovered and appears to be operating steadily once more. Consequently, I proceeded with sputtering |