| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1546
|
Tue Dec 13 10:51:13 2005 |
 | Yoshio Imai | | Request | Linux | 2.6.0beta5 | Logbook aliases | Hi!
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 ... 
Yoshio Imai |
|
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 |
|
1569
|
Thu Dec 22 21:15:19 2005 |
| Edmundo T Rodriguez | edrodrig@chpnet.org | Request | | 2.6.0 | "Syntax of elogd.cfg" - Document | The document "ELOG - Syntax of elogd.cfg" is outdated!
Are we going to have an updated documented?
How much difference exists between the one posted as a reference
and new one covering all new options in ELOG? |
|
1570
|
Fri Dec 23 09:07:14 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | 2.6.0 | Re: "Syntax of elogd.cfg" - Document |
| Edmundo T Rodriguez wrote: | | The document "ELOG - Syntax of elogd.cfg" is outdated! |
I forgot to update the web server, but the document distributed in the 2.6.0 package was up to date.
| Edmundo T Rodriguez wrote: | | Are we going to have an updated documented? |
I copied the actual version to the web server.
| Edmundo T Rodriguez wrote: | How much difference exists between the one posted as a reference
and new one covering all new options in ELOG? |
For the changes from one version to the other, have a look at the changelog. |
|
1624
|
Tue Jan 24 14:43:19 2006 |
| T. Ribbrock | emgaron@gmx.net | Request | Linux | 2.6.1 | Suggestion additional ElCodes | I have to say, now that I'm finally on 2.6.x, I grew really fond of the ElCode stuff - great addition! It saves a lot of straight HTML typing for me... THANKS!
However, there are two things I'm missing:
- Headings
It would be great to have a range of , , ... tags that map directly to their HTML counterparts (and have buttons, of course... ). That makes structuring an entry much easier in my opinion (and the output is easier to deal with for tools like html2ps) and I'm really missing those.
- Tables
This one is probably more difficult to add, but support for simple tables would be enough. But this is more a "nice to have"...
|
|