Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 595 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 594, 595, 596 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  1535   Thu Nov 24 20:08:00 2005 Warning Yoshio ImaiBug reportLinux2.6.0beta5"Logkook dir" in top group [global] section ineffective
Hi, it's me again!

I have found one possible bug. We have declared top groups for our logbooks; one for administration and one for the shift logbooks. In the [global]-section there is a "Logbook dir"-statement of the form
[global]
Top group Admin = <...>
Top group Shiftlogs = beamtime1,beamtime2,...

Logbook dir = /data/logbooks
Now, in the [global Shiftlogs] section there is another "Logbook dir"-statement to have all associated logbooks in one tree:
[global Shiftlogs]
Logbook dir = /data/logbooks/shift-logbooks

[beamtime1]
Subdir = beamtime1
The problem is, that the manually created subdirectories /data/logbooks/shift-logbooks/beamtimeN are ignored, and the elogd creates new "Subdir"-directories /data/logbooks/beamtimeN (as if the "Logbook dir" statement in the top group [global] section were ineffective). Is this a bug or configuration error from our side?

There are also one question/request (you see that we use the elog extensively now Wink):
When searching for a particular event in our shift log using the "Find" function, it would often be useful not to go to the single entry, but to the page where that entry resides. This way we can see the whole context of the event. When clicking onto an entry in the "Find" result page, this takes us of course to the single entry, but could you add a function to go to the page instead. Alternatively, is it possible to include a button "Go to page" in the single entry view (it need not even be exactly +/-N entries around, the usual page partition would do)?

Thanks in advance.

Yoshio
  1536   Fri Nov 25 14:05:08 2005 Reply Yoshio ImaiBug reportLinux2.6.0beta5Re: "Logkook dir" in top group [global] section ineffective
OK, I found the note about "Logbook dir" in Stephen Wood's entry (http://midas.psi.ch/elogs/Forum/1101) Wink
  1546   Tue Dec 13 10:51:13 2005 Question Yoshio ImaiRequestLinux2.6.0beta5Logbook 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 ... Wink

Yoshio Imai
  1547   Tue Dec 13 20:34:39 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.0beta5Re: 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 ... Wink


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 Big grin .
  1548   Wed Dec 14 11:40:54 2005 Idea Yoshio ImaiRequestLinux2.6.0beta5Re: 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 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.0beta5Re: 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 Crying ). 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 Reply Yoshio ImaiRequestLinux2.6.0beta5Re: 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... Wink). I hope you didn't invest too much time in that already.

Thanks, and happy beamtime!

Yoshio
  1568   Thu Dec 22 20:50:57 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0beta5Re: "Logkook dir" in top group [global] section ineffective

Yoshio Imai wrote:
There are also one question/request (you see that we use the elog extensively now Wink):
When searching for a particular event in our shift log using the "Find" function, it would often be useful not to go to the single entry, but to the page where that entry resides. This way we can see the whole context of the event. When clicking onto an entry in the "Find" result page, this takes us of course to the single entry, but could you add a function to go to the page instead. Alternatively, is it possible to include a button "Go to page" in the single entry view (it need not even be exactly +/-N entries around, the usual page partition would do)?


I implemented that request. When you click on "list", it takes you to the listing page containing the current entry, which is even highlighted. Have a look at this forum if this is what you like.
Goto page Previous  1, 2, 3 ... 594, 595, 596 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6