| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69310
|
Wed Feb 24 08:44:42 2021 |
 | Martin Neumann | elog.20.beazy@spamgourmet.com | Question | Linux | V3.1.4-80633ba | Re: Date conversion |
I don't feel comfortable allowing the elog daemon to execute random shell scripts. Is there no other way?
| Andreas Luedeke wrote: |
|
If you define a field as "datetime" then you'll get the standard ELOG input field for datetime. It will be stored as seconds of the epoch (seconds since 1.1.1970).
You can define a field as a default string input, then it is stored as a string. But you can convert that string by a shell scripts into seconds of the epoch. See "subst" command in the documentation of the elog syntax:
|
|
|
69312
|
Tue Mar 2 15:17:56 2021 |
| Sebastian Schenk | sebastian.schenk@physik.uni-halle.de | Question | Linux | V3.1.4-80633ba | Re: Date conversion |
One other way would be to do the conversion on the client-side using javascript.
Overwrite the complete datetime input cell and add an event listener to either onChange of this input or the submit event, to trigger the conversion before submitting, so elog would get the converted time.
In out elog some entries get additional information added in this way.
| Martin Neumann wrote: |
|
I don't feel comfortable allowing the elog daemon to execute random shell scripts. Is there no other way?
| Andreas Luedeke wrote: |
|
If you define a field as "datetime" then you'll get the standard ELOG input field for datetime. It will be stored as seconds of the epoch (seconds since 1.1.1970).
You can define a field as a default string input, then it is stored as a string. But you can convert that string by a shell scripts into seconds of the epoch. See "subst" command in the documentation of the elog syntax:
|
|
|
|
69316
|
Wed Mar 10 17:30:23 2021 |
| Stefan Ritt | do stefan.ritt@psi.ch | Question | Linux | V3.1.4-80633ba | Re: Date conversion |
Do you actually need to convert the date into the internal format? Why not keeping simply the full string YYYY-MM-DD HH:MM. If the use is disciplined enough to always use the correct format, there should be no issue. I invented the datetime format to "force" all date/time inputs to have the correct format. If you have a proper YYYY-MM-DD HH:MM format, even sorting (now by string) should work correctly.
| Martin Neumann wrote: |
|
Hi,
I am trying to figure out how ELOG works and I have a problem.
I have one datetime attribute, where I want the user to be able to enter the time in ISO8601 format (YYYY-MM-DD HH:MM) instead of the buttons.
How do I manage that this input is converted correctly into the internal format?
I tried adding a hidden locked Attribute called IntDate and use "Subst IntDate = $start" but the result is dates in 1970, even though I have set the Time Format to "%F %H:%M"
|
|
|
1819
|
Fri May 5 07:58:53 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.1-1668 | Re: Date automatically generated by another one |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
|
1820
|
Fri May 5 09:01:04 2006 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.6.1-1668 | Re: Date automatically generated by another one |
| Stefan Ritt wrote: |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
OK! Thank for your response. |
|
65633
|
Thu Oct 25 20:15:46 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.6.5:1946 | Re: Date attribute in Quick filter |
| Peter Rienstra wrote: | I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:
Error: "Attribute "Date" for quick filter not found", see attachment.
In the configfile I have: Quick filter = Date
A bug? |
Yep. Fixed in V2.6.5-1951. |
|
1022
|
Thu Mar 24 21:17:28 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Database type logbook entry creation |
> I would like to create a paper waste logbook. I need to have a column that
> shows a weight in pounds and another column with a calculation from those
> pounds to dollars. pounds x $4.00 = cost I was wondering if this was
> possible?
>
> All other fields would be just Date, Batch#, Operator, Reason, Process
> Operator, Manager, Lbs, and Cost, I would also like to total this cost if
> possible, on a search selected basis. Similar to Excel.
Unfortunately not. But your request is on the wishlist since some time, I added
your vote. |
|
66337
|
Thu Apr 30 08:48:01 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2185 | Re: Database Like - ELOG Format |
| mike cianci wrote: |
|
Stefan,
I am using the Database Like - ELOG format and on the list page, the the last two columns (on the right side) are, "Text" and "Attachments (the paperclip)".
Both of which I have deleted from the input page.
Is there anyway to remove them from the List page?
Thanks, Mike
|
You need:
Show text = 0
Enable Attachments = 0
to supress the text entry box and the attachment field.
Display search = ID, Type, Location, Status
to show only the attributs of interest in the list display (your attributes could be different)
Summary lines = 0
to supress the text in the list display. At the moment, this still shows the paperclip colum, but I want to fix this in the next version.
|