ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 80 of 238

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

1898 Entries

Goto page Previous 1, 2, 3 ... 79, 80, 81 ... 236, 237, 238 Next

XML import Error, posted by Donald on Thu Feb 27 15:15:55 2014

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

Re: XML import Error, posted by Andreas Luedeke on Mon Mar 3 15:42:29 2014

Donald wrote:

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

Hi Donald,

yes, the import function gave me some headache in the past, too.

Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.

(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)

In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.

My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

Re: XML import Error, posted by Donald on Tue Mar 4 19:48:02 2014

Andreas Luedeke wrote:

Donald wrote:

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

Hi Donald,

yes, the import function gave me some headache in the past, too.

⇄

English (auto-detected) » English

Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.

(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)

In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.

My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

Hi Andreas

That worked, thank you so much. now I'm on to a new error.

Now every time i try to do the import it crashed the elogd.

OS is windows server 2008 R2. I have the elogd installed as a service.

here is the even log:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86

I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?

Re: XML import Error, posted by Donald on Tue Mar 11 15:17:36 2014

Donald wrote:

Andreas Luedeke wrote:

Donald wrote:

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

Hi Donald,

yes, the import function gave me some headache in the past, too.

⇄

English (auto-detected) » English

Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.

(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)

In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.

My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

Hi Andreas

That worked, thank you so much. now I'm on to a new error.

Now every time i try to do the import it crashed the elogd.

OS is windows server 2008 R2. I have the elogd installed as a service.

here is the even log:

I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?

Anyone have any luck reproducing the error? or have suggestions on how to fix it?

Author drop-down menu length, posted by Kay Graf on Mon Mar 10 12:15:07 2014

I am handling several ELOGs for medium-sized collaborations (scientific experiments) with a large number of authors (~250) and chose to have single-user access and entries for every author - in the config file, the "Options Author"-List contains ~150 name for now.

However, the Author drop-down menu stops after ~100 names - is that a ELOG-webserver hard limit? I checked there is nothing strange in the author names following (no strange character, etc.).

I tested it on Firefox, Chrome, Safari - it does not seem to be a browser issue.

Any help would be highly appreciated.

Re: Author drop-down menu length, posted by Andreas Luedeke on Mon Mar 10 15:18:51 2014

Kay Graf wrote:

However, the Author drop-down menu stops after ~100 names - is that a ELOG-webserver hard limit? I checked there is nothing strange in the author names following (no strange character, etc.).

I tested it on Firefox, Chrome, Safari - it does not seem to be a browser issue.

Any help would be highly appreciated.

Hello Kay,

I had to look it up in the source code: yes, you are right, it is hard-coded in elogd.h

elogd.h:#define MAX_N_LIST 100

You can of course change the limit and recompile.

As an alternative, you could have sub-menus with less than 100 entries (disclaimer: the following is untested example):

Attributes = author_range, author, ...

options author_range = A-K{1}, L-Z{2}

{1} options author = Andi, Bob, Camilla, Dennis, ..., Kay

{2} options author = Lily, Max, Norbert, Oscar, ..., Zeta

Cheers

Andreas

Re: Author drop-down menu length, posted by Kay Graf on Tue Mar 11 09:19:06 2014

Andreas Luedeke wrote:

Kay Graf wrote

Hello Kay,

I had to look it up in the source code: yes, you are right, it is hard-coded in elogd.h

⇄

English (auto-detected) » English

elogd.h:#define MAX_N_LIST 100

You can of course change the limit and recompile.

As an alternative, you could have sub-menus with less than 100 entries (disclaimer: the following is untested example):

Attributes = author_range, author, ...

options author_range = A-K{1}, L-Z{2}

{1} options author = Andi, Bob, Camilla, Dennis, ..., Kay

{2} options author = Lily, Max, Norbert, Oscar, ..., Zeta

Cheers

Andreas

Hello Andreas,

thanks a lot for your quick reply - both options are valid and working. For simplicity (the author list is generated automatically from a shell script) I opted for the first one.

Best regards,

Kay

How to upload several images at once, posted by Alejandro Gomez on Wed Mar 5 03:58:51 2014

I just want to know if there is a way to upload a bunch of images at once. I need to upload ~50 images per day and of course it is really tedious.

Thanks!!

Re: How to upload several images at once, posted by Stefan Ritt on Wed Mar 5 07:53:01 2014

Alejandro Gomez wrote:

I just want to know if there is a way to upload a bunch of images at once. I need to upload ~50 images per day and of course it is really tedious.

Thanks!!

The "standard" HTML protocol does not allow multiple selection of images. You can use the "elog" command-line utility to upload images from the terminal window. We plan in the summer this year a switch to HTML5, which does allow upload of multiple images plus a drag-and-drop functionality.

/Stefan

Google Places API AutoComplete, posted by Garret Delaronde on Fri Apr 26 19:00:07 2013

G'day everyone.

Looking for some input on this idea.

I work for an organization which uses elog extensively for day to day operations.

In several of our logbooks we use a "location" attribute where we would enter an address or intersection.

I am working with the google places api and am able to create the auto complete form in a separate html page, but am interested if anyone has a good direction how i could change the input box into the google map autocomplete search box.

I have the code already for the api search box. but when i add it to the config it doesn't really do anything different.

Attached is the html file i setup with the api code.

the autocomplete works great, now i just want it to work in elog.

Any help is much appreciated!

And perhaps the Elog Powers that be might be interested in making it a function down the road? :)

Re: Google Places API AutoComplete, posted by Stefan Ritt on Fri Feb 21 13:43:03 2014

Garret Delaronde wrote:

G'day everyone.

Looking for some input on this idea.

I work for an organization which uses elog extensively for day to day operations.

In several of our logbooks we use a "location" attribute where we would enter an address or intersection.

I have the code already for the api search box. but when i add it to the config it doesn't really do anything different.

Attached is the html file i setup with the api code.

the autocomplete works great, now i just want it to work in elog.

Any help is much appreciated!

And perhaps the Elog Powers that be might be interested in making it a function down the road? :)

Looks like a nice idea. You can sneak in any JavaScript code into elog pages with the "Top text" option. Like

Top text = <script>window.onload = function() {...}</script>

Then you parse the DOM tree to find your input field for the location, and attache your JS code to it. All the input fields have the "name" attribute in the HTML code set, so it should be easy to find the input field in the DOM tree.

/Stefan

Export entries to XLS or CSV?, posted by scogordo on Wed May 15 17:24:12 2013

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,

Scott

Re: Export entries to XLS or CSV?, posted by Andreas Luedeke on Wed May 15 23:31:30 2013

scogordo wrote:

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,

Scott

Hi Scott,

yes, every user can export entries using the "find" command.

Just select the export format in the first line

Export to: CSV ("," separated) CSV (";" separated) XML Raw

I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.

I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.

There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.

Re: Export entries to XLS or CSV?, posted by Jim Tinlin on Thu May 30 22:52:51 2013

Andreas Luedeke wrote:

scogordo wrote:

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,

Scott

Hi Scott,

yes, every user can export entries using the "find" command.

Just select the export format in the first line

Export to: CSV ("," separated) CSV (";" separated) XML Raw

I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.

I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.

There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.

I tried EXPORTING logbooks as .csv but have not been fully successful. Elog seems to only export the data entered for various fields with the exception of the text field.

Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields...

Thanks in advance!

"Message ID","Date","Author","Type","Status","Priority"

107,Thu 30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"

106,Thu 30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"

105,Thu 30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

104,Thu 30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

103,Wed 29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

102,Wed 29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

Re: Export entries to XLS or CSV?, posted by Andreas Luedeke on Fri May 31 11:41:48 2013

Jim Tinlin wrote:

Andreas Luedeke wrote:

scogordo wrote:

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,

Scott

Hi Scott,

yes, every user can export entries using the "find" command.

Just select the export format in the first line

Export to: CSV ("," separated) CSV (";" separated) XML Raw

I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.

I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.

There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.

I tried EXPORTING logbooks as .csv but have not been fully successful. Elog seems to only export the data entered for various fields with the exception of the text field.

Thanks in advance!

"Message ID","Date","Author","Type","Status","Priority"

107,Thu 30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"

106,Thu 30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"

105,Thu 30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

104,Thu 30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

103,Wed 29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

102,Wed 29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

Yes, you're right: the text field is only exported in XML and Raw mode.

It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.

But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.

I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.

(This string has not yet been added to the localization.)

As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.

Of course the spreadsheet programs just display the HTML source.

Stefan, do you think this should be added to the official branch?

Re: Export entries to XLS or CSV?, posted by Stefan Ritt on Tue Jun 4 12:38:01 2013