| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1813
|
Tue May 2 22:58:48 2006 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.6.1 | Is it possible to require certain attributes for specific users (guests)? | First of all, thanks for writing and maintaining eLog.
I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
accounts.
I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
fields don't need to be required for registered accounts, since that information is available already.
Is there any way to have conditional statements act on the value of $short_name?
Thanks,
Mark |
|
1814
|
Wed May 3 00:16:42 2006 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | allow per-logfile attributes to be added/subtracted from the global settings | I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings.
For example, the [global] section of my elogd.cfg reads:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status
Extendable Attributes = Type, Category, Severity, Subject, Status
Options Category = Hardware, Software (OS and utilities), Software (Application), Network, Security, Other
Options Severity = None, Low, Medium, High, Critical
Options Status = Open, Closed, In-Progress, Suspended
Options Type = To-Do, Problem Report, Problem Fixed, Informational Note, Software Installation, Configuration, Other
Required Attributes = Type, Category, Subject, Status
I've also got an logbook for each server for hardware issues. Within those logbooks, I'd like to keep all the fields except the software fields, and add fields for memory and storage.
Adding 7 definitions to each server logbook makes the config file huge and difficult to edit, and it means that a future change to the global settings wouldn't propagate to the individual log files. I'd really like to do something like:
[server47]
-Options Category = Software (OS and utilities), Software (Application)
+Options Category = Storage, Memory
-Options Type = Software Installation
+Options Type = RAM Installation, Drive upgrade
As I see it, the initial "-" sign in front of an attribute or option would indicate that the fields listed should be deleted from the global set (if the field name is an exact match), and a leading "+" indicates that the given fields would be added to the global attribute of the same name, for that specific logbook.
The current behavior--without a leading "+" or "-" would be unchanged, so that existing config files don't change.
Thanks,
Mark |
|
1815
|
Wed May 3 08:28:05 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.1 | Re: allow per-logfile attributes to be added/subtracted from the global settings |
| Mark Bergman wrote: | | I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings. |
Sounds to me like a good idea. I will put it on the wishlist. |
|
1816
|
Wed May 3 08:31:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: Is it possible to require certain attributes for specific users (guests)? | > First of all, thanks for writing and maintaining eLog.
>
> I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
> accounts.
>
> I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
> fields don't need to be required for registered accounts, since that information is available already.
>
> Is there any way to have conditional statements act on the value of $short_name?
No, this is not implemented. The only way you have right now is to make two separate logbooks, one for guests and
one for registered users. But I know this is not an optimal solution. I will think about it. |
|
1822
|
Sat May 6 02:12:10 2006 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | suggestion for "new user registration" page | I'm testing elog, and one user was having difficulty creating a new account for himself. This problem had three reasons:
1. the user expected a "submit" button or some other way to exit the account registration screen to appear near the password boxes, at the bottom of the page.
2. I'm using the "Bottom text" option, which has a URL to execute a "find" (search) within elog for all open tickets. The user simply entered the info for their new account, and then clicked on the button at the bottom of the page--which would be the expected behavior.
3. In our environment, there are many logbooks (~100), as each computing device has it's own logbook. This isn't a problem on the main page, since the logbooks are grouped into 7 categories. However, the account registration page combines two functions--setting up a new account, and selecting which logbooks to subscribe to for e-mail notification. The logbooks are presented in a list (rather than groups), which causes the "Save" button at the top left to scroll off the screen before the user enters their password.
Suggestions for improving the registration page:
Put a "submit" button after the password entry.
Possibly supress the local "bottom text", or allow the specification of a different file for the registration page.
After the user has registered, then show a page allowing them to subscribe for e-mail notifcation. That page should be organized the same way as the main page, with groups. Users should be allowed to subscribe to entire groups, or to expand each group to select or unsubscribe from individual logbooks.
Thanks,
Mark |
|
1825
|
Wed May 10 16:14:00 2006 |
| Kevin McCarty | kmccarty@princeton.edu | Question | Linux | 2.6.1 | Email notification question | Hello,
I've just set up an ELog server for my research group. (Running on Debian, package version 2.6.1+r1642-1)
I have a question about the email notifications. I read through the config file documentation, but couldn't find the answer (maybe I am just unobservant\?) Is it possible to have the email notifications contain only the title of the log entry (as well as the usual attributes), but not the full text or any attachments? I have users who are worried about their email going over quota from ELog's emails, but who nevertheless would like some kind of notification when new log entries are posted.
Thanks in advance! |
|
1826
|
Wed May 10 16:16:33 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: Email notification question |
| Kevin McCarty wrote: | Hello,
I've just set up an ELog server for my research group. (Running on Debian, package version 2.6.1+r1642-1)
I have a question about the email notifications. I read through the config file documentation, but couldn't find the answer (maybe I am just unobservant\?) Is it possible to have the email notifications contain only the title of the log entry (as well as the usual attributes), but not the full text or any attachments? I have users who are worried about their email going over quota from ELog's emails, but who nevertheless would like some kind of notification when new log entries are posted.
Thanks in advance! |
Have a look at the option Email format = <n> |
|
1827
|
Wed May 10 16:30:45 2006 |
| Kevin McCarty | kmccarty@princeton.edu | Request | All | 2.6.1 | Feature request - site-specific ELCode markup definitions | Hi,
Here's a suggestion that you may or may not want to apply. It would be nice if there existed a config file (or a syntax in the existing elog.cfg file) that permitted sites to define their own ELCode patterns.
Let me give you a usage case. I thought it would be nice to have LaTeX expressions show up automatically on my group's ELog installation if they entered them like this: [math]x^2 + y^2 = r_0^2[/math] So in the source code file elogd.c, I hacked in the following additions to the definition of pattern_list[]:
{"[math]", "<img src = \"http://borex.princeton.edu/mimetex?"},
{"[/math]", "\" border = \"0\" align = \"absmiddle\" />"},
and recompiled ELog.
What this does is convert the LaTeX expression into a URL that uses the "mimetex" CGI program installed on my server to output a GIF file of the equation. So my users can have inline math expressions in their log entries, like this:  . Obviously this is far too site-specific to be added to the official ELog code (unless you want to embed mimetex code into the server, which I kind of doubt  ). But it would be nice if I could specify these patterns in a config file without having to edit the source code and recompile each time I want to install a new ELog version!
Presumably others could find a use for site-specific ELCode markup too (logos, custom smilies, etc.)
Thanks for your time. |
|