elog perl script and the command prompt and eof, posted by Arno Teunisse on Thu Sep 7 22:06:00 2006 
|
hello
Just wrote a quick and dirty perl script ( See Attachment ) that let's you enter a record into the database. Put it into the directory where the config file is located. It look's at the "attributes = " and the "required attributes = "
within a section in the elog configuration file. The script is using elog.exe to accomplish this.
One problem with the script is that you must press Control_Z ( ^Z ) to store the data into the database.
Does anybody know how to prevent this ? It works also when redirecting the data into the script with a file input.txt. ( add2elog.pl confgi.cfg logbook < input.txt )
I Know this is NOT an elog question but maybe someone is happy with the script and has the answer for me. |
|
Re: Date format in Threaded display, posted by deletoille on Thu Oct 19 12:42:42 2006
|
IT WORKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANKS A LOT |
|
Spell check, posted by David Egolf on Mon Nov 6 17:13:19 2006
|
Sorry if this has been asked.
Is there a spell check that can be implemented in Elog or any recommended add on spell check?
Thanks,
David Egolf |
|
Re: Email notification (bug tracking system), posted by Bertram Metz on Thu Nov 30 16:07:54 2006
|
| Stefan Ritt wrote: |
| Bertram Metz wrote: | Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
I implemented the attribute type useremail for you. This can be used like:
Attributes = Author, Catorory, AssignedTo
Type AssignedTo = useremail
Email Category Bug Report = $AssignedTo
You will see only the email address of the people in the list, but since the email address usually contains the name this might be enough. A different system would have been too difficult to implement. The new feature is contained in SVN revision 1754. |
Thank you very much Stefan,
that works fine for me!
Bertram |
|
Group definition under top group, posted by Exaos Lee on Sat Jan 13 17:47:45 2007
|
Hi, I think, if we can put the "Group xxx = xxx" under some "global xxxx" sections, the configure file will be more clean. Don't you think so? In fact, if the "Group XXX" sections are put under "global XXX" section, the "Top Group XXX" can be ignored. I also found that some options (e.g. "Logbook dir =") under "global" don't work under "global XXX".
Maybe the configure file can be defined more flexible, such as this way:
[global]
Port = 8080
Top configuration = yes
[global Group1]
Group config = group1.cfg
[global Group2]
Group config = group2.cfg
The "group1.cfg" looks like this:
[global]
Top configuration = no
Password file = group1.pwd
Group Linux PCs = Red Hat, Debian, Gentoo
Group Windows PCs = 98, ME, XP, Vista
Group Vista = Home, Pro, Media Center
[Red Hat]
...
|
|
Global "MOptions", posted by Fergus Lynch on Mon Mar 26 11:45:07 2007
|
Hi,
We have ELOG configured for virtually every conceivable use in our IT Operation dept and it is fantastically useful and easy to use. One result of this - naturally! - is that we have quiet a few logbooks.
Many of these logbooks share the same attributes - especially Moptions for equipment lists - which is fine but requires manually copying and pasting Moption lists into multiple logbooks to keep everything synchronized.
Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks?
Just an idea -
Cheers
Fergus |
|
Re: Multiple ideas for multiple logbooks, posted by Yoshio Imai on Tue Apr 3 17:55:21 2007
|
| Stefan Ritt wrote: | Well, you didn't realize, but you were my beta-tester for the keyboard shortcuts  . I didn't yet publish it, so you must have gotten this brand new feature from SVN. |
You should really have told me  . Actually, I found out about the <Ctrl-C> issue while using this logbook.
| Stefan Ritt wrote: | | So get the SVN update, and let me know what you think |
Did so, we are running now -1826. I think it is very usable, with maybe one exception (this might be a browser issue, however): When using the shortcuts and/or the ELCode buttons, sometimes the code is generated and the cursor in between the [XX] and [/XX] directive, but sometimes, the whole code directive is selected as if for editing
which prevents from immediately continuing to type (which, I guess, was the idea behind the shortcuts). The behaviour is not completely reproducible, and I have even seen it change during one and the same browser (=firefox) session while working on the same entry (*). I also had it once that the browser out of a sudden completely ignored the ELCode meaning, and instead used <Ctrl-I> for page info and <Ctrl-B> for the history.
(*) It just happened again!
BTW, there are (of course ) two other issues. They are still present in -1826
- one bug was reported by a logbook user: when using the "find" function in a logbook, and selecting one value from the "Author" drop-down list and another from the "Category" drop-down list, the elogd reports no entries found, but when specifying only the "Author" and leaving "Category" blank, many entries are found, including those with the "Category" being looked for. When specifying only the "Category" and leaving the "Author" blank, the elogd also reports no entries found. Has anyone reported a similar behaviour?
- We have one logbook top group for the beamtimes. Under certain conditions, a preset text is to be displayed.
{2&a} Preset Text = resource/text_1.txt
{2&b} Preset Text = resource/text_2.txt
However, the definitions of these conditions have to be repeated for every logbook in the group (putting it only under [global beamtimes] doesn't do it), otherwise they are ignored.
Any idea on these? |
|
Add date and time stamp to file upload, posted by Fergus Lynch on Thu Oct 4 12:03:30 2007
|
Hi,
Been using ELOG for a couple of years now and I am very impressed with its functionality.
I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments.
Many Thanks in Advance
Fergus |
|