ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65873
|
Wed May 7 17:10:07 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | latest | $entry time not readable by Subst, else not datetime type? |
I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:
Thank you for pointing out the method to identify an attribute as a datetime type so that it will sort properly. I now have created my "Last Edit" attribute in several
preexisting logbooks.
I want to use
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit.
However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.
I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry.
I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to
another's? To reiterate, I want to initialize Last Edit = $entrytime for all entries that have not been re-edited.
Thanks |
65888
|
Wed May 21 21:06:38 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | | Make Email All = <list> override Suppress Email checkbox |
I would like to be notified by email of some logbook entries regardless of whether the user has chosen to suppress email or not.
This way I will always be aware of new entries, and users will still have the option of notifying a larger group of other users, or not.
As far as I can tell, presently the Suppress Email checkbox overrides Email All. |
66040
|
Mon Nov 10 19:40:43 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Bug report | | 2.7.3-2109 | Show/Hide links are displayed but don't work if Show attachments = 0 |
If I add this statement to a logbook config file:
Show attachments = 0
When viewing and individual entry, attached images are not displayed, which is as intended, but the links Show/Hide and Show All/Hide All are still displayed although they do nothing when clicked except switch between Show and Hide. Clicking on an image opens it in a separate window.
Could you make show/hide and show/hide all work? This way, by default the images are not displayed, but the default could be overridden on a case by case basis as desired, and the images displayed inline in the same window with the entry.
Thanks!
|
66069
|
Fri Nov 21 18:21:36 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
Dennis Seitz wrote: |
Stefan Ritt wrote: |
Dennis Seitz wrote: | Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference) |
Yes, of course I mean '$entry time', sorry for the misspelling. |
Well, we really appreciate the way you keep adding features and making improvements. I thought you might have slipped a new one in! |
FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
66080
|
Tue Nov 25 17:01:55 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.3 | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
Stefan Ritt wrote: |
Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
 |
Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome. |
66102
|
Tue Dec 9 00:22:41 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.5 | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
Dennis Seitz wrote: |
Stefan Ritt wrote: |
Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
 |
Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome. |
Everything works fine with 2.7.5, thanks! |
66103
|
Tue Dec 9 00:25:52 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.5 | Please add Subst on Duplicate |
I would like to be able to substitute some attribute values when an entry is duplicated. I don't see Subst on Duplicate available in the cfg file syntax. Can you add that?
Thanks |
66105
|
Wed Dec 10 03:11:01 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.5 | Re: Please add Subst on Duplicate |
Stefan Ritt wrote: |
Dennis Seitz wrote: |
I would like to be able to substitute some attribute values when an entry is duplicated. I don't see Subst on Duplicate available in the cfg file syntax. Can you add that?
|
Subst on Duplicate does not make sense. Subst always works after you submit an entry, while Preset works before you enter the entry. When you Duplicate an entry, it looks like a new one, just with attributes and text from another entry. So when you submit that one, the system cannot distinguish if you entered a new one by yourself or if this is based on a copy of another entry. So what you probably need is Preset on duplicate.
|
Thanks for explaining.
I thought Preset would work with Duplicate since Duplicate creates a new entry, but it didn't. Then I tried Subst because Duplicating an entry opens it in Edit mode, so you are in effect Duplicating, and then Editing the entry. It just didn't occur to me to look for Preset on Duplicate. |