ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66589
|
Tue Nov 10 13:20:43 2009 |
| Michael Dannmeyer | michael.dannmeyer@solvias.com | Question | Windows | 2.7.5-2130 | Extend fields in ELOG |
I want to extend the usage of ELOG and have 2 Questions:
1. Is it possible to have Fields which only appears if another selection is done? e.g. I create a new entry. This new entry has a type field. If I chose the Type "ABC" another field appears where the departemnt could be choosen. If I select Type "DEF" the Department field does not appear.
2. I have a field Status. This is a predefined field with 3 entries (New, under progress, closed). If i change the status field time, date old and new status should be logged or written in the text field. I can log this with the answer field with a new ID. But is there any other way to log it in the text field or log it with no new ID?
Can i implement the wishes above? If yes how does it work?
Thanks for your help
Michael |
66588
|
Tue Nov 10 13:06:26 2009 |
| Michael Dannmeyer | michael.dannmeyer@solvias.com | Question | Windows | 2.7.5-2130 | Re: Export Text to a csv File |
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else.
|
Thanks for your fast answer. |
66587
|
Tue Nov 10 12:54:47 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Export Text to a csv File |
Michael Dannmeyer wrote: |
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else. |
66586
|
Tue Nov 10 12:50:48 2009 |
| Michael Dannmeyer | michael.dannmeyer@solvias.com | Question | Windows | 2.7.5-2130 | Export Text to a csv File |
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
66585
|
Mon Nov 9 11:50:05 2009 |
| Eddy Berends | eddy.berends@stratosglobal.com | Bug report | Linux | 2.7.7 | Reply on item not allowed moving item to other logbook |
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |
66584
|
Mon Nov 9 09:32:19 2009 |
| Diogo Alves | diogomiguelalves@gmail.com | Question | Linux | Windows | 2.7.5 | Re: Problems with SSL and Synchronization |
Stefan Ritt wrote: |
Mark Langkau wrote: |
I installed ELOG on a Linux server (CentOS 5.2) and a WinXP laptop.
- If I set both servers to non-SSL, I can synchronize with no problems.
- If I set both servers to use SSL, synchronization fails with "Error code: ssl_error_rx_record_too_long"
- If I set one to ssl and the other non-ssl, synchronization fails with "Remote server is not an ELOG server"
Is anyone synchronizing or mirroring two ELOG servers with SSL? When either or both servers are set to use SSL, I can use either site. but I can't synchronize.
|
Synchronization with SSL does not yet work. I have to find some time to implement it. Since you are already the second one mentioning this, it slipped higher on my to-do list
|
Count me also in for the to-do list climbing :-D |
66583
|
Sun Nov 8 23:29:35 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.7 | Re: Automatically generated incrementing tags (#) |
soren poulsen wrote: |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren
|
This can be solved with something like "Subst <attr> = $shell(cmd...) where cmd calculates a new value of attr, as a function of #, when attr does not already have a value. This thread is closed.
Soren
|
66582
|
Sun Nov 8 23:25:25 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
Chuck Brost wrote: |
Stefan Ritt wrote: |
Chuck Brost wrote: |
Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet. They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients". So you see why I find it amusing. I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin). First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy. Please let us know.
|
I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer.
|
Trust me, I don't want them getting old data either.. that would be a nightmare..
of course, the little voice at the back of my head (note, not IN the back of my head) has offered up this tidbit for you to consider.
Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.
The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Hopefully there are no other side effects to this change.
|
You can also try to use a different browser.
Soren |