ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67894
|
Mon May 11 22:42:44 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 310.3 | Re: Preloading Options or Moptions from a text file or CSV |
> > > Title says all :)
> > >
> > > Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
> > >
>
> So basically, I have a list of 5-10 workers. I'll have to choose one for each entry I make into the logbook. But these workers will change from time to time
> (students) and I don't want the staff to manipulate the config file manually..("Extendable options" is not an option as I will get to many "Darth Vader" entry for
> sure..)
>
> I asked if I could populate that option box from another logbook attribute and Andreas told me only possible via external scripts.
> https://midas.psi.ch/elogs/Forum/67877
Hi Francois.
if those worker lists do change rather infrequently, then I would have an idea how to do it:
You could have an application that updates the Options or MOptions lists in the elogd.cfg file at midnight,
and in case they actually did change the application restarts the elogd process afterwards.
I use such a mechanism to update my user list from our companies LDAP service every second Monday of a month at midnight.
This avoids misspelled user names or wrong email addresses and takes care that all employees (~2000) can log-in to our ELOG.
The passwords are handled anyway by kerberos authentication.
But I admit that it would be a cool feature to have "includes" in the configuration file for dynamic data sources.
Shell scripts of course are useless for "Option" definitions: they would only be executed at start-up anyway,
and that can be accomplished as well by the above mentioned automatic changes to the config file.
Kind Regards
Andreas |
67895
|
Mon May 11 22:51:44 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1 | Re: Remote entries with empty messages possible? |
Hi Edmund,
Stefan already supplied a fix, but you could as well use a workaround: provide an empty file as text. The following works for Linux:
elog -h elog-server-adress -l EO -a Fill=111 -m /dev/null
Cheers
Andreas
Edmund Hertle wrote: |
Hey,
I want to submit an entry to elog remotley using the "elog" command. For example:
elog -h elog-server-adress -l EO -a Fill=111
But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:
elog -h elog-server-adress -l EO -a Fill=111 "test"
also using an empty string does not work:
elog -h elog-server-adress -l EO -a Fill=111 ""
I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.
To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.
|
|
67902
|
Wed May 13 22:03:37 2015 |
| Ferdinand Gassauer | f.gassauer@chricar.at | Question | Linux | 3.1 | csv import timestamp |
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
67904
|
Thu May 14 02:19:53 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1 | Re: csv import timestamp |
Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm. Did you have any problems doing it?
Cheers
Andreas
Ferdinand Gassauer wrote: |
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
67906
|
Thu May 14 02:35:15 2015 |
| Francois Cloutier | Francois@fcmail.ca | Question | Windows | 3.1.0 | Elogd synchronisation with remote server |
I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
elogd mention "-m" and "-M" ... not elog but elogd... with that description :
synchronize logbook(s) with remote server
Does it sync all logbooks ? is there any examples somewhere or advice ?
Thanks :) |
67909
|
Thu May 14 05:13:34 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.0 | Re: Elogd synchronisation with remote server |
> I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
> elogd mention "-m" and "-M" ... not elog but elogd... with that description :
> synchronize logbook(s) with remote server
If you would have followed the shown link to the "elogd.cfg syntax page", you would have found the chapter Mirroring:
https://midas.psi.ch/elog/config.html#mirroring
> Does it sync all logbooks ?
Not necessarily, but that is the default.
> is there any examples somewhere or advice ?
See above: you'll find examples under #mirroring
> Thanks :)
You're welcome. |
67910
|
Thu May 14 07:01:23 2015 |
| Ferdinand Gassauer | f.gassauer@chricar.at | Question | Linux | 3.1 | Re: csv import timestamp |
Thanks
what is the format of the Date field in the csv file ?
My Date is date and not datetime.
Andreas Luedeke wrote: |
Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm. Did you have any problems doing it?
Cheers
Andreas
Ferdinand Gassauer wrote: |
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
|
67911
|
Thu May 14 22:16:03 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1 | Re: csv import timestamp |
Hi Ferdinand,
"import" is meant to be used for files that have been exported with "find". Therefore it is not very flexible with the date format.
Todays date should look like that: "Thu 14 May 2015 22:12:00 +0200".
You have to convert your file that the date matches this format (BTW: I found this out by using the find - export feature; it may depend on a local configuration.)
Cheers
Andreas
Ferdinand Gassauer wrote: |
Thanks
what is the format of the Date field in the csv file ?
My Date is date and not datetime.
Andreas Luedeke wrote: |
Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm. Did you have any problems doing it?
Cheers
Andreas
Ferdinand Gassauer wrote: |
I have to import a csv with a date field, which represents the creation date
this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp
|
|
|
|