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

Thanks,

Scott

Yes, adding a new attribute in a logbook is not straight forward.

But it is doable: that is one of the things that I write SED scripts for. You just need to add the attribute in all old entries, and in this specific case you can use the entry time to initialise the "when" attribute.

Of course I would only do that on a copy of my data and run a separate elogd server on that data to see if anything is screwed up :-)

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

 

 Does anyone have a success story with kerberos on windows?

Here's the global section and the logbook section for one of the logbooks affected.  Of note, the 'demo' logbook works
fine and does not have this issue.

[global]
port = 8080
SMTP host = localhost
Welcome title = Welcome
Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

[WINTER]

;*****Look and Feel*****
Page title = Winter Weather
List page title =  Winter Weather
Edit page title = Winter Weather
Theme = default
CSS = default.css
Comment = Winter Weather
Title image =

;*****Email*****
Use Email From = me@me.com
Suppress Email to users = 1
Display Email recipients = 0
Email Encoding = 4
Suppress Email on edit = 1

;*****Settings*****
Entries per page = 30
;Reverse sort = 1
Expand default = 2
Display mode = SUMMARY
Mode command = 0
Time format = %d%B%Y-%H:%M
Summary lines = 15
Show top groups = 0
Message height = 8
Message width = 38
Default encoding = 1
Mode commands = 0
Suppress default = 2
Resubmit default = 2
Back to main = 1
RSS Title = $entry time - $Event

;*****MENU*****
List Menu commands = New, Find
Menu commands = List, New, Edit, Find, Reply, Delete

 If they have admin rights, the add user button cannot be removed as far as I know.

But even if they can add a user, they only have ability to add a user to the single logbook they are an admin on so they wouldn't be able to add users to other peoples logbooks.

Not sure it helps but that's about all I can really speak to.

> On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
> link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
> But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
> "back" submit button.  I can't seem to figure out how to address it.  Suggestions?

Can you show us your config? I had this issue when i was initially trying to integrate elog with apache.

 I haven't found a specific way to block viewing a log book. 

I use the top groups settings to keep users in the logbooks they only need access to.

Example

Top Group = Logbook Group1, Logbook Group 2

Group Logbook Group 1 = Logbook1, Logbook2

Group Logbook Group 2 = Logbook3, Logbook4

Then only assign users for logbook1 and logbook2 that you wish to view those logbooks only. They would have to go to the specific top group url in order to view the logbooks.

Then you can go to http://elogurl/(top group)/

And essentially just have the users view the only logbooks they are assigned to.

 The only way I find for this trouble is using the "Login user". But we have something best?