Re: Importing XML, posted by Andreas Luedeke on Thu Oct 4 11:35:12 2012
|
| David Chastain wrote: |
|
[...] Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck. Any thoughts or ideas?
|
I've successfully imported a large amount of entries from old non-ELOG logbooks via XML.
The only problem that I did run into was the date format: ELOG is very restrictive on the imported format; it has to be either "MM/DD/YY(YY) (HH:MM:SS)" or "DD.MM.YY(YY) (HH:MM:SS)".
When you export entries ELOG honours the "Date format" that you've specified in your elogd.cfg, therefore you cannot import the exported file until you reformat the date in the file.
Andreas |
Locking a Thread, posted by Hal Proctor on Wed Feb 13 15:39:07 2013
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books. |
Re: Locking a Thread, posted by Stefan Ritt on Wed Feb 13 16:27:18 2013
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation. |
|
Re: Locking a Thread, posted by Hal Proctor on Wed Feb 13 16:56:40 2013
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it. |
|
Re: Locking a Thread, posted by Stefan Ritt on Wed Feb 13 16:59:06 2013
|
| Hal Proctor wrote: |
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it.
|
That's a different meaning. The "Locked by" flag gets set when one user edits an entry. During the editing the entry gets "locked", which means that no one else can change it during that time. This should prevent one person to overwrite the edits of another if they are editing the same entry at the same time. Your "locking" means the locking of threads, which elog doe not "understand", it's just your definition of an attribute in your logbook. |
|
trouble ticket systems w/ elog?, posted by Miles Fidelman on Mon Jan 7 01:45:10 2013
|
Updating my toolbox. Starting to use elog as, well, a logbook. Kind of liking the short, sweet, to the point capabilities.
Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?
Thanks!
Miles Fidelman
|
|
Re: trouble ticket systems w/ elog?, posted by David Pilgram on Wed Jan 9 11:19:50 2013
|
| Miles Fidelman wrote: |
|
Updating my toolbox. Starting to use elog as, well, a logbook. Kind of liking the short, sweet, to the point capabilities.
Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?
Thanks!
Miles Fidelman
|
I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files. Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.
I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook. [This is possible via their elog entry number, and which logbook it is in]. The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ". Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.
On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes). Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.
|
|
Re: trouble ticket systems w/ elog?, posted by Miles Fidelman on Wed Jan 9 18:20:41 2013
|
| David Pilgram wrote: |
|
| Miles Fidelman wrote: |
|
Updating my toolbox. Starting to use elog as, well, a logbook. Kind of liking the short, sweet, to the point capabilities.
Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?
Thanks!
Miles Fidelman
|
I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files. Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.
I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook. [This is possible via their elog entry number, and which logbook it is in]. The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ". Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.
On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes). Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.
|
By "ticket number" are you referring to the Message ID, or is there some additional trouble ticket functionality buried away? And... can you point me to the documentation that's "buried away under Subst <attribute> = <string>? Thanks! |
|