Re: Display last page by default, posted by Yoshio Imai on Mon Oct 31 01:39:52 2005
|
I have installed the new version, and it works just fine. It is also MUCH faster than my intermediate solution.
| Quote: |
For the moment, I could satisfy the users by setting the start page to the "All" view
|
Thanks for the work! |
Getting back from "Find" mode, posted by Yoshio Imai on Tue Nov 15 10:58:23 2005
|
Hi again!
There is one question regarding the "Find" function of the elog. Clicking onto "Search" takes the user to the list view on only those entries that match the search conditions. Since we use the list view in "Full" mode by default, this usually is enough to give us an overview of the event we looked for.
Is there a more direct way to get back to the unfiltered list view than selecting an entry and go to "List" or using "Find" again and clicking on "Back"?
Greeting
Yoshio |
|
Passive elog mirrors, posted by Yoshio Imai on Fri Nov 18 19:57:03 2005
|
| Hi!Is it possible to install a "passive" elog mirror? We want to allow members of another institute to browse our logbook, but the connection is rather slow. The idea is now to set up an elog mirror at their site for faster access. Still, we should be the only ones who can add and edit the entries, so the update mechanism needs to be restricted in one direction. Is this possible at all? I didn't find any clues on that in the documentation ...ThanksYoshio |
Re: Passive elog mirrors, posted by Yoshio Imai on Mon Nov 21 14:35:20 2005
|
| Thanks, I will try it with one of these methods. |
"Logkook dir" in top group [global] section ineffective, posted by Yoshio Imai on Thu Nov 24 20:08:00 2005
|
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  ):
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 |
|
Re: "Logkook dir" in top group [global] section ineffective, posted by Yoshio Imai on Fri Nov 25 14:05:08 2005
|
| OK, I found the note about "Logbook dir" in Stephen Wood's entry (http://midas.psi.ch/elogs/Forum/1101) |
|
Logbook aliases, posted by Yoshio Imai on Tue Dec 13 10:51:13 2005
|
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 |
Re: Logbook aliases, posted by Yoshio Imai on Wed Dec 14 11:40:54 2005
|
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? |