| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66817
|
Thu May 13 13:31:53 2010 |
 | Eric Krise | Eric.Krise@cmicompany.com | Question | Windows | 2.7.8-2294 | Entry merging |
Is there a way to merge existing entries from several logbooks into a single logbook? |
|
66819
|
Fri May 14 16:50:53 2010 |
 | Eric Krise | Eric.Krise@cmicompany.com | Question | Windows | 2.7.8-2294 | Re: Entry merging |
| Stefan Ritt wrote: |
|
| Eric Krise wrote: |
|
Is there a way to merge existing entries from several logbooks into a single logbook?
|
Only manually: Add "Move to" to you set of commands via "Menu commands = ...", then select one or more entries, and move them to your target logbook.
|
Got it! Thanks... |
|
66820
|
Fri May 14 16:53:54 2010 |
| Eric Krise | Eric.Krise@cmicompany.com | Question | Windows | 2.7.8-2294 | Required Attributes |
Is there a way to require a certain attribute on reply, but not on an original entry? In some cases info. for these fields only exists on reply. |
|
481
|
Fri Feb 27 03:48:05 2004 |
 | Raj | Elog+rajelio@yahoo.com | Question | Windows | 2.5 | Instant Edit Link |
How I can dynamically create a link when a new submission is entered that
will have a value of <ELOG_URL$message id?=Edit>
I want the users to be able to go straight from the main page to an edit
page. This would skip 1 step to get to the edit page.
Is this possible.
If that link could use one of the icons for the src image that would be
great.
Thanks.
:-) |
|
66710
|
Tue Feb 16 04:17:24 2010 |
| Geoff Ellis | Ellis_Geoff@solarturbines.com | Question | All | 2280 | Single Button Entry |
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this? |
|
67349
|
Tue Oct 2 21:58:20 2012 |
| David Chastain | David_Chastain@sra.com | Question | Linux | 2.9.1 | Importing XML |
I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).
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? |
|
69835
|
Wed Sep 25 14:21:33 2024 |
| David Pilgram | David.pilgram@epost.org.uk | Question | Windows | 2.9.2 | Re: Looking for version update advice |
I use linux elog, and if you upgrade to v3.x.x, it's difficult to go back to v2.9.x. This is because the log files get grouped in year sub directories at v3.x.x.
In 2.9.x, the logfiles are store as (made up example) /home/logfiles/yymmdda.log
In 3.x.x they are stored as /home/logfiles/2024/24mmdda.log /home/logfiles/2023/23mmdda.log etc. I think I got the labelling of the subdirectories correct, Stefan will no doubt correct if I am wrong.
I assume the same is true for the Windows version as it would be weird for a split in the program by OS for something important but trivial to impliment for all OS.
It's a bore to sort that out if you have to revert to 2.9.x - I know, I've done it - but I don't recall any change in format in the individual yymmdda.log files with an early v3.x.x version I tried. There may be additions to the log files made in much more recent v3.1.x or so versions, but I guess you are ok with whatever they may be as you've checked the change log.
| Patrick Upson wrote: |
|
Thanks. I did eveuntaully find the change log and made the decision to upgrade the at-sea machines. So far the configuration file we update for each mission still works. I have a copy of the 2.9.2 installer that if something catostrophic happens I can remove the new version and take it back, but I don't think it'll be a problem. We archive logbooks at the end of a mission, but each mission basically starts from a fresh install like state anyway.
| Stefan Ritt wrote: |
|
If 3.1.4 runs safely on your laptop, there should be no problem to update the 2.9.2 one. But first do it on a copy of your logbooks from the at-sea. The get converted automatically into a newer format but that should be transparent.
On the other hand you don't really need a new system if your old installation works fine and you don't need any of hte new features.
The changelog ist here: https://elog.psi.ch/elog/download/ChangeLog
Stefan
| Patrick Upson wrote: |
|
I've inherited a position that includes deploying elog for an at-sea mission. Once at sea there's no gauntee of internet connection so I have to be sure things are going to work before hand. The machines I currently have (we have several backup machines) are running elog version 2.9.2 and I'm looking for a change log, or feature list to determine if it's safe to update the at-sea laptops to the latest version of elog.
On one hand, I could leave things as they are and I'm sure it will just work, on the other hand, I hate seeing things get out of date to the point that something just stops working some day and there's no ability to get support for old software.
I'm already running elog 3.1.4 on my personal machine I use for configuration development and testing and it seems to work well. The config file is pretty simple and seems to work with 2.9.2 on the at-sea machines, but I don't want to run into any suprises if there ends up being a compatibility issue at sea.
|
|
|
|
|
65767
|
Tue Mar 4 14:03:00 2008 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.3-2058 | Quick filter by ID |
Hi,
I've just upgraded from 2.6.2 to 2.7.3.
In my config file, I have
Quick filter: Date, ID.
When starting 2.7.3, across the top I now get
"Error: Attribute "ID" for quick filter not found"
followed by an entry box.
If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
I cannot see any documented change that would affect how the Quick filter works. Any clues? Thanks. |