I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:

Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"

Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' -To 'alangrant@mts.net' -Subject 'New meter entry' -Body 'TEST' -Priority High -DeliveryNotificationOption OnSuccess, OnFailure -SmtpServer 'citygw') works fine and the email is received when running it from the Powershell ISE app directly from the same elog vm server but not from within Elog with the above statement.

I'd like to first confirm that the syntax of the line Execute New = is correct, ie, double quoting the entire command. Can anyone please confirm.

Hi Team,

Can you please guide me how to export and import the documents from the one elog to the another elog server also I like to know how to backup the server.

Thanks

Stan

See https://elog.psi.ch/elog/config.html#mirroring

and

https://elog.psi.ch/elog/userguide.html#access

(use "find" with "Export to" "Raw".)

Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in that tab.

I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way anyone knows of that I can use to parse a log file DIRECTLY to view the older data, without using the Elog GUI?

Hi Al; if I understand your situation correctly you want to access Elog db (logbooks) via another way. There are many ways depending on your knowledge, type of work needed, and ease of use. I have found that accessing whatever I need via Elog gui is satisfactory in many situations-- by simply exporting. THEN take the raw csv/xml  file and manipulte it more easily from there. There are MANY free web sites that will take your data then, and put it in still another format that you choose (usually manipulating the rows/columns to your liking or doing mail-merge type work on your data). BTW WPS (Windows Office clone) is awesome at further 'mail-merg'  techniques. THEN at that point you may have close to what you are trying to accomplish. I've also used PHP alot in this type of situation and have replicated Elog's data format for it's db (logbooks)..; so PHP is great in this maner, although of course it takes time to 'get-it-right' if you are not well versed in it. If you go into detail more of what type of format you want as the finalized product, maybe  more suggestions will be made.

Happy belated New Years everyone,

John

Hi John. The problem with using the Find-->Export method is that some of the Attributes for the older data are no longer shown on that screen because the Config file has since changed. That's why I'm contemplating somehow parsing the log files directly instead.

Well, you could put the old options back to the config file, do the export, then remove them again.

But have a look at the Elog database files ZZMMDDa.log in your logbook directory, they are pure ASCII files, which are relatively simple to parse.

Hi,

I had similar needs (access and parse logs ) so I'm  a small library in cpp. Have a look on https://github.com/flagarde/elogpp maybe it could be usefull for you too.