| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65897
|
Mon Jun 2 23:41:15 2008 |
 | Dennis Seitz | dseitz@cosmology.berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | OK, now I realize how stupid I sound here. To partially answer my own question: $entry time is a string and Last Edit is now a number since I have changed it to the datetime type so that it will sort properly.
So I can't make Last Edit = $entry time. Is there some way I can access the entry time in datetime format so that I can set Last Edit equal to that? |
Ok, now I got your point. Sorry for the late reply, but I was extremely busy the last few weeks. I added the missing functionality to elog revision 2108, so the 'subst on edit Last Edit = $entry date' does now work. |
Thanks! Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference)
Anway, thank you! |
|
65900
|
Thu Jun 5 01:36:07 2008 |
| Dennis Seitz | dseitz@cosmology.berkeley.edu | Request | All | | Re: Make Email All = <list> override Suppress Email checkbox |
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
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.
|
If I make "Email all" override the suppress email checkbox, some uses would complain "I check the supporess box, but my admin still gets email, what am I doing wrong here?". So while this works for you, it will not be desired for everybody. I would have to add another parameter just for this request. Couldn't you instead use the RSS feed functionality? This way you well see all entries, independent of the email notification. You can use special RSS feed readers (your browser and email client probably support this already).
|
Hmm, I see your point, but wouldn't using the RSS feed have the same effect? Or are you saying the users just wouldn't know about it, so they wouldn't complain? 
I haven't explored the RSS feed options yet. I'll study them.
|
The RSS feed you have to "pull" actively with a client (which of course can be periodically in an automatic way). So no pull, no notification, happy users 
|
Hmm. Is there some way to set up a private RSS feed for me only?
If not, I would humbly  ask that you add an option. I don't want to generate unnecessary email to users, but I need to always be notified for some logbooks. I'm responsible for some hardware on our project and I want to know any time someone reports a problem. The best solution is to still let users decide whether they want to subscribe to logbooks, and whether entry notification should be suppressed or not, but also have an admin override privilege. There could be a disclaimer "admin is automatically notified of all entries" at the top of the edit page.
If this can be done with a private RSS feed to me only, then that's fine. I still don't use or understand RSS feeds very well, sorry. I'd rather all users did not have the option to be alerted to every new entry, when email suppression is enabled. That would be contradictory, I think.
Thanks for listening!
|
|
65901
|
Thu Jun 5 01:38:17 2008 |
| Dennis Seitz | dseitz@cosmology.berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? |
| 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! |
|
2229
|
Thu May 17 02:12:52 2007 |
 | Dennis Seitz | dseitz@berkeley.edu | Question | All | | Summary view: View only most recent entry for all values of a given attribute? | We are using Elog to track status of hardware assemblies. One attribute we've created is the serial number of an assembly. Other attributes are items like "location" and "status". We have set up these latter attributes with presets to make entry easy and keep entries consistent.
I would like to filter the summary view so it only shows me the most recent entry for every value in the serial number attribute. This would be very useful for quickly viewing the present status and location of every assembly, for example.
I can't find a way to do this in the documentation. Is it possible? If not, may I submit a request for this feature?
I am very impressed with the Elog and it has become an essential part of our record keeping. Thank you for a very useful and well implemented application! |
|
2231
|
Fri May 18 02:15:41 2007 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | | Re: Summary view: View only most recent entry for all values of a given attribute? |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | | I would like to filter the summary view so it only shows me the most recent entry for every value in the serial number attribute. This would be very useful for quickly viewing the present status and location of every assembly, for example. |
I don't know if that is what you want, but have you tried clicking on the column headings in the summary view to sort the table according to that attribute:
 |
Rather than simply sorting, I would like to actually reduce the number of entries listed to show only the most recent entry for each serial number. In this way, I can see at a glance what the present status of each serial number is. This is similar to Quick Filters but would be a "Most Recent" filter that could be applied conditionally, for example: "Most Recent" -> "By Serial".
Here is the display now:
Here is what I'd like to have the option to view (I used a graphic editor to fake it):
It would also be nice to have the option to then sort the resultant view, for example, to group together all serial numbers that have the same status.
Is this a little clearer? It's just a suggestion - this is not terribly important, but if it were possible I think it would be useful.
Thanks! |
|
2233
|
Fri May 18 16:07:31 2007 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | | Re: Summary view: View only most recent entry for all values of a given attribute? |
| Stefan Ritt wrote: | Ok, now I understand. Well, your request is very special for your case. Usually I implement things only if several independent people ask for it. What you can try is to save your logbook in CSV format, import it into Excel or another spreadsheet program, and achieve the filtering there.
Best regards,
Stefan |
OK, I've done that before and it works fine. I'd rather be able to do it in Elog but I understand if it's not worth the effort. It never hurts to ask!
Cheers,
Dennis |
|
65716
|
Tue Jan 29 04:25:11 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | | 2.7.0 | Possible to sort attribute chronologically? | Hi,
We've defined a "LastEdit" attribute for some of our logs so that we can indicate that an entry has been revised, and when that was done.
From our config:
Attributes = Last Edit, etc etc
.
.
.
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
This works fine, but when we sort the LastEdit column, the dates are sorted alphabetically. Is there a way to tell Elog to treat this particular attribute
as a date when sorting? |
|
65725
|
Thu Feb 7 01:33:03 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | | 2.7.0 | Re: Possible to sort attribute chronologically? | > > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
>
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.
Thanks for the help and the bug fix. I have a colleague who keeps our installation up to date, so I'll ask him to install it. |
|