| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1547
|
Tue Dec 13 20:34:39 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
| Yoshio Imai wrote: | Is it possible to implement aliases for logbooks? We would like to use a new logbook for every beamtime, but many services need to read/write to the respective current beamtime logbook. It would therefore be nice to have logbook "aliases", so that e.g. a "virtual" logbook beam could be defined to be an alias/redirection to the current beamtime logbook, and all services could refer to that one instead of having to be reconfigured for each beamtime.
This could also help to make sure everyone on shift writes the entries to the correct logbook ... 
|
You can do that already with the current version: At the end of a beamtime, create a new logbook, take the current logbook as a template, to make sure it has the same settings. Then move all entries from the current logbook to the new beamtime logbook, either with
- the "move to" command from the menu (which you first have to enable. While this works fine for individual entries, I never tried this with a whole logbook (click on "all", then "select all", then move to). So better try this first on a backup
- moving the logbook entries on the file level. Go to the elog root, then enter "mv logbooks/<current>/* logbooks/<beamtime>/ where <current> is your current (online) logbook and <beamtime> is the new one you just created. You have to restart elogd so that it realizes the moved files
After that, your current logbook is empty again and ready for the new beamtime  . |
|
1548
|
Wed Dec 14 11:40:54 2005 |
 | Yoshio Imai | | Request | Linux | 2.6.0beta5 | Re: Logbook aliases | Ok, we will try this.
In our case, the "symlink"-type logbook might have been nice because of our daily backup routines. If we move the data of the old logbook to the newly created one, the backup process would first need to upload all logbook data to the backup server under the new directory name and then delete those under the old name.
In our case this is not so much of a problem, because the logbooks are small (100MB), but maybe you can add this to the wishlist if others request the same... (We could try to adjust the backup procedure, but I don't know how well this would work).
Anyway, thanks for the work!
P.S. What do you think about the idea of a "Go to page"-button for the single entry view? |
|
1549
|
Wed Dec 14 11:48:37 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
| Yoshio Imai wrote: | | but maybe you can add this to the wishlist if others request the same... |
Ok, I will do that.
| Yoshio Imai wrote: | | P.S. What do you think about the idea of a "Go to page"-button for the single entry view? |
I plan to make it even better (when I get some time, we have beam time right now as well  ). If you click "List" on the single entry page, it takes you by default to the listing page. I guess that would be a feature of general interest. I just need some time to implement it... |
|
1550
|
Wed Dec 14 15:45:29 2005 |
| Yoshio Imai | | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
| Stefan Ritt wrote: | | If you click "List" on the single entry page, it takes you by default to the listing page. |
I also think this is the best way to do it.
BTW, now that everyone here got used to the current elog look&feel, I think we no longer need the conditional hiding of attributes (don't hit me... ). I hope you didn't invest too much time in that already.
Thanks, and happy beamtime!
Yoshio |
|
262
|
Wed Apr 2 21:45:18 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Logbook Title bar | > Is there a way to change the title entry for individual log books, and
> forms ive completely rebranded our system but ut stil says ELOG ENTRIES on
> the summary screen
I changed the default title recently to "ELOG - <logbook>" where <logbook>
is the name of the current logbook. For the individual messages, the
title "ELOG" can be changed with the elogd.cfg option "Page title". This
title can even contain attributes from the logook entry like:
Page title = ELOG - $subject
where $subject gets replaced by the subject of the logbook entry. |
|
263
|
Thu Apr 3 09:40:45 2003 |
| nick | nick@nick.com | Info | | | Re: Logbook Title bar | > > Is there a way to change the title entry for individual log books, and
> > forms ive completely rebranded our system but ut stil says ELOG ENTRIES
on
> > the summary screen
>
> I changed the default title recently to "ELOG - <logbook>" where <logbook>
> is the name of the current logbook. For the individual messages, the
> title "ELOG" can be changed with the elogd.cfg option "Page title". This
> title can even contain attributes from the logook entry like:
>
> Page title = ELOG - $subject
>
> where $subject gets replaced by the subject of the logbook entry.
I have those attributes already working for example
[global]
Page title = Customer Relational Management System < this sets the selection
page ok
[Config DB]
Page Title = ABC123 - $Customer Name < this sets the individual log book
entries title
I need something to set the title of the page when on the summary page for
the logbook, as it just says ELOG - Config DB (this isnt set anywhere) |
|
264
|
Thu Apr 3 10:11:08 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Logbook Title bar | > I need something to set the title of the page when on the summary page for
> the logbook, as it just says ELOG - Config DB (this isnt set anywhere)
I added the option "Summary page title = xxx" in a similar way than the "Page
title". The new version is at
http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.64
It will be included in the release 2.3.5 of elog.
- Stefan |
|
66508
|
Tue Aug 11 08:29:23 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.5 | Re: Logbook Parser |
| Alan Grant wrote: |
|
We are exploring whether it's possible/feasible to import ELog logbooks into a another database for special purposes (plotting/statisical, etc). Target database is TBD (perhaps Access).
Does anyone have or know of a logbook parser program? From cut/pasting into, for example, Excel, it does appear that the data fields are already line-feed delimited so offhand it would seem possible to parse if one really wanted to pursue it.
Regards,
- Alan
|
You can export to CSV (comma-separated-values) if you go to "Find" and then click on "Export: CSV". These fiels you ran read right into Excel or other spreadsheet programs for further analysis. |
|