Re: Pre-fill Attribute with last entry, posted by Stefan Ritt on Wed Mar 24 19:45:41 2021
|
That would actually be my recommendation. There is a "execute new" which you can call when submitting a new entry.
Stefan
| Dominic Schneider wrote: |
|
Hi Stefan, hi Sebastian,
thank you for your help. Ok I see its not that simple.
Is there maybe a way of executing a Script on submitting, writing the values of the Attributes into an temporary file and loading the values from this file via a preset shell script when opening a NEW entry?
Best wishes & thanks in advance
| Sebastian Schenk wrote: |
|
Sorry Stefan, but it is possible as you have the scripting ability.
The idea is to use "Preset Test_Attribute = $shell(script_to_get_the_last_entry)", where the script asks elog about the details and parses them.
The problem here is, that the elogd already is working to resolve the click on "new entry" request (or similar) and the script can't call elogd until the page is delievered, what is to late.
(If it would, the elogd will hang.)
So the script either has to directly parse all the entry.log files in the logbook folder or you need a second elogd running, which can answer the request from the script.
This second elogd could run on a different port and it doen't need to be public as it only answers internal requests and could use the same config as the "primary" elogd.
My idea for the script uses the python elog module to establish the connection and do the parsing.
I hope this helps as a workaround.
Best wishes,
Sebastian
| Stefan Ritt wrote: |
|
Nope, there is no way to acces the last value of an attribute. Sorry.
Stefan
| Dominic Schneider wrote: |
|
Hi all together,
I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook.
I know I have to go with Preset, tried a view hours and searched the forum but i didn't find a thing. Am I overlooking a flag, an option or whatever, or is there just not such a functionality (which I dont believe)?
I thought about:
Preset Test_Attribute = $Test_attribute
Preset Test_Attribute = Re:$Test_attribute
Preset Test_Attribute = $shell(Command to somehow get last entry and this attributes value)
Not succesful though.
I would be very thankful for help, thanks in advance.
|
|
|
|
|
|
Re: auto pre-fill fields issue, posted by Stefan Ritt on Fri Apr 9 17:54:42 2021
|
You need user-level access control, using
Password file = ...
Stefan
| Gys Wuyts wrote: |
|
Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host
Subst Email = $user_email
in the elogd.cfg file does not seem to work.
(I see it works here on this platform)
Tnks
G
|
|
|
Re: auto pre-fill fields issue, posted by Stefan Ritt on Mon Apr 12 13:57:18 2021
|
"Subst xxx" replaces after you submit an entry, while "Preset xxx" replaces before you create an entry. I believe you want the second one.
Stefan
| Gys Wuyts wrote: |
|
[global]
port = 8080
ssl = 0
Password file = passwords.txt
Admin user = user1
SMTP host = smtp. mail.com
SMTP port = 25
SMTP username = user1@mail.com
SMTP Password = GIwbx7UbmkWs5J0P8lVztX7Anje0/21BU/Tmk0aPm.
Logfile = ELog_log.txt
Logging level = 3
[Server]
Logbook dir = Server
Theme = default
Comment = Server Change Log
Attributes = Author, Email, Type, Category, Subject
Subst Author = $long_name from $remote_host
Subst Email = $user_email
Options Type = SRV 1, SRV 2, SRV Sup, BMS content, BMS setpoints, BMS new
Options Category = Config, User, Access, Connection, Change, New, Delete
Extendable Options =
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
| Andreas Luedeke wrote: |
|
If you would post a minimal config file where the problem occurs, then we could look what the problem is.
| Gys Wuyts wrote: |
|
Thank you but that is already in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.
tnks
g
| Stefan Ritt wrote: |
|
You need user-level access control, using
Password file = ...
Stefan
| Gys Wuyts wrote: |
|
Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host
Subst Email = $user_email
in the elogd.cfg file does not seem to work.
(I see it works here on this platform)
Tnks
G
|
|
|
|
|
|
|
Re: segfault in auth.c:366, posted by Stefan Ritt on Fri Apr 23 16:21:05 2021
|
Well, if you find a solution with works for everybody, I'm happy to commit it to the main repository. But unfortunately I cannot test it because I don't have LDAP here, so I'm flying blind.
Stefan |
|
Re: Drop attachments here..., posted by Stefan Ritt on Tue Jun 29 20:20:38 2021
|
Looks good, I merged the pull request. |
|
Re: Large log file size, posted by Stefan Ritt on Mon Aug 30 08:41:14 2021
|
If the logbook files are getting big, searching text in entries can take quite some time. But if you have a log file logging all activities, that should not slow down elog since the server just appends at the end of that file which is a quick operation.
| Alan Grant wrote: |
|
Can the size of the application log file affect performance?
|
|
|
Re: How to lock a specific entry?, posted by Stefan Ritt on Tue Sep 14 18:18:03 2021
|
You can either lock all entries or none. So I would propose you set up two logbooks, one for technical changes which is not locked and one for what experimentalists are doing which is locked. Locking can be done a certain time after an entry has been made (like 1h, 1d, 1 month etc.). Or you simply make the logbook read-only.
Stefan
| Manoel Couder wrote: |
|
Hi All,
I am using elog to track technical changes in an experiment but also to log what experimentalist are doing during an experiment. For the latter, I would like to be able to lock those entries from being further edited after the expertiment if finished. Is there a way to do that?
Thanks,
Manoel
|
|
|
Re: How to access PSI Elog data from other web clients , posted by Stefan Ritt on Wed Oct 13 08:17:23 2021
|
When elog has been developed, REST did not yet exist. The closest you can get is the RSS API. Just try https://elog.psi.ch/elogs/Forum/elog.rdf and you see the result for this forum. To write to elog, you can use teh HTTP/HTML interface and mimic a browser. See for example elog:69209
Stefan
| Lin Wang wrote: |
|
We want to develop separate mobile web pages for the web applications deployed at CSNS accelerator, including the PSI Elog.
In Elog, is there RESTful API or HTTP/JSON or HTTP/XML interface for other web clients to access?
Or is there any workaround?
|
|
|