moving eLog to another computer, posted by Ekaterina Korobkina on Wed Sep 30 18:57:44 2020
|
Our Unix server died, so we decided to move our old eLog to the new server, running Mac OSX. Elog version is earlier then 2013, I can not say
I read that on OSX eLog must be intalled through "make" command
if I need to install eLog first, how to add all old information later? |
Re: moving eLog to another computer, posted by Andreas Luedeke on Sat Oct 3 11:08:27 2020
|
you need to copy your logbooks into the "logbooks" directory.
you need to copy your elog.cfg logbook config file to the
new elog folder and reference it at start-up (something like "elogd -c /usr/local/elog/elogd.cfg ...")
Some people modify other
stuff (CSS, java scripts) but if you had you would know what you did. |
Is it possible to visually group attributes with border, posted by Daniel Sajdyk on Thu Oct 8 12:29:55 2020 
|
Hello,
I'm working on new logbook and in one category I'll have many attributes (many more than in attached screenshot).
So here is my question. Is it possible to visually group such attributes with some border, or something like that? |
|
Re: Is it possible to visually group attributes with border, posted by Stefan Ritt on Thu Oct 8 12:40:52 2020
|
Nope, this is not possible. Sorry.
Stefan
Daniel |
|
Up-to-date windows-version, posted by Sergei Gavrilov on Sun Oct 18 16:59:38 2020
|
Dear colleagues,
Can someone compile an up-to-date windows-version or write a manual how to do it in Windows without compiling errors?
Thank you. |
|
Upload attachment with py_elog, posted by Bruno Schuler on Tue Oct 20 16:05:40 2020
|
Hello,
How can one add an attachment to a new or existing entry with py_elog?
E.g. if I want to upload an image. |
|
From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 15:08:17 2020
|
I'm running Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload
all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit
not allowed. |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 17:50:50 2020
|
Update: I tried switching the logbook to no authentication reqiured, and still get the "command Submit not allowed" response.
David
Wallis wrote:
I'm running Elog version V3.1.4-ba84827 on Red Hat |
|
Re: From command line: "command Submit not allowed", posted by Stefan Ritt on Tue Oct 20 18:02:42 2020
|
"submit not allowed" you typically get if there is a "guest menu" for read-only access and you are not logged in. I never tried the
elog program with PAM authentication, but you said that your turned authentication off. What I would do is to strip down your elogd.cfg to a very simple
form until the elog utility works, then figure out which configuration makes the trouble. |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 18:26:26 2020
|
Hmmm... I added "New" to the Guest menu list, and the button showed up for a guest user. But when I submitted the new ticket, I got the message Error:
Command "Submit" is not allowed for user ""
Stefan |
|
Re: From command line: "command Submit not allowed", posted by Stefan Ritt on Tue Oct 20 18:40:05 2020
|
Giving up. Send me your config file and I will debug it.
Stefan
David |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 20:44:03 2020
|
I've been able to work around this by completely turning off authentication, and adding New to the Guest menu list.
One additional question: since I'm uploading historical logbook entries, is it possible to set the entry creation date via the command line?
It seems that elogd is overriding the attribute "Date". |
|
Re: From command line: "command Submit not allowed", posted by David Dunne on Wed Oct 21 03:08:21 2020
|
FYI, I had problems a few weeks ago trying to get the command line elog working, blamed everybody and everything but myself.
In my case it was command line syntax errors and eventually got it going as part of a nightly script
While testing I ran the Elog Server from the command line in verbose mode to see if that helped determine the problem. |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Wed Oct 21 15:14:13 2020
|
Hi David, thanks for your input!
This logbook has been around for almost 10 years, and has evolved from file-based authentication, to LDAP, and finally to PAM (that can use any
of local password files, LDAP, and Active Directory), and I'm thinking that might be the root of this problem. There are old account entries from the |
Field values dependent on other selections, posted by Anthony Krishock on Tue Oct 20 02:34:46 2020
|
All,
I would like to know if there is a way in elog to populate a field based on the value of another field. What I want to do is have a field with
a few selections (a menu) and another text field that populates based on what I select from the menu. |
|
Re: Field values dependent on other selections, posted by Stefan Ritt on Tue Oct 20 08:24:20 2020
|
Look in the manual under "conditional attributes"
Stefan
Anthony |
|
Re: Field values dependent on other selections, posted by Anthony Krishock on Wed Oct 21 02:27:43 2020
|
Thanks for your suggestion. Right now, my log is configured as follows:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Pentax = 5mm, 20mm, 30mm |
|
Re: Field values dependent on other selections, posted by Andreas Luedeke on Fri Oct 23 15:10:54 2020
|
Instead of using three different options you could use the same:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Form = 5mm, 20mm, 30mm |
|
MEG style elog configuration, posted by Daniel Kohl on Sun Oct 25 06:26:49 2020
|
Hello,
I'm new to elog software and I could not find a solution to my configuration issue. I would like to setup a configuration file similar to |
|
Re: MEG style elog configuration, posted by Stefan Ritt on Mon Oct 26 11:42:53 2020
|
It was done using the "groups" feature:
https://elog.psi.ch/elog/config.html#groups
Stefan |
|
Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:00:03 2020
|
I'm converting our on-call logbook, with 25 years of history, to elog. Is there a way to override the current date/time for the Date field with the
creation date/time of the original logbook entry? |
|
Re: Create entry from command line - override Date?, posted by Stefan Ritt on Tue Oct 27 16:15:26 2020
|
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!! |
|
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:37:07 2020
|
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date",
upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan |
|
Re: Create entry from command line - override Date?, posted by Stefan Ritt on Tue Oct 27 16:49:53 2020
|
"Date" must be on the first line on each entry and it must be named "Date".
Stefan
David |
|
Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 17:07:00 2020
|
You could transform your entries into the ELOG file format (either XML or CSV) and then use the import function. That would upload the correct dates
from your entries.
If you use the "Orig Date" trick you've proposed, you'll see that datetime fields are stored as seconds of the epoch (since |
|
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 17:45:29 2020
|
Hi Andreas,
Thanks for your input! After a little testing, it appears that if I make "Orig Date" the first field, it will fall under the Date field
in the logbook file. I can then do a global delete of Date:, and replace Orig Date: with Date:, leaving it as the first field in the entry. Then I can |
|
Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 21:59:03 2020
|
Hi David,
correct. And in addition you will need to convert "Orig Date" from seconds-of-the-epoch into a properly formated date string (see example
below from Stefan) ... |
|
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 22:24:18 2020
|
Hi Andreas,
It was actually easier than that. The time stamps in the old system were in epoch format, so when I created the new record, (my conversion program
was written in Python), I simply formatted that value in the format Stefan pointed out below, and defined the Orig Date field as text. Then I was able |