Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 445 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  66339   Fri May 1 08:05:42 2009 Question mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2185Problem Naming Logbooks

I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for

a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.

The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.

If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.

  66348   Wed May 6 15:35:44 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2185Re: Problem Naming Logbooks

 

mike cianci wrote:

I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for

a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.

The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.

If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.

 

I tried to reproduce your problem but without success. In my case the "CentaurNewLot" looks fine:

Capture.png

so what is different in your case? Can you try with the simple example logbook from the distribution and the add one option after the other to see which one causes the trouble?

  66540   Wed Sep 9 08:16:22 2009 Question mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2185Supress Email on Reply

The way I have ELOG configured it sends an email to supervisors based on which "Department " (attribute) was selected. Problem is that when the supervisor replies the department

is still selected and it sends a second email to the supervisor. Is there any way to supress the emails (automatically) on "Reply"?

  66541   Thu Sep 10 16:55:08 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2185Re: Supress Email on Reply

mike cianci wrote:

The way I have ELOG configured it sends an email to supervisors based on which "Department " (attribute) was selected. Problem is that when the supervisor replies the department

is still selected and it sends a second email to the supervisor. Is there any way to supress the emails (automatically) on "Reply"?

No, but you can remove the "Department" with

Remove on reply = Department

this way the attribute vanishes, but that should be ok since you always have the link to the original entry which contains the department. 

  67113   Sun Sep 4 23:01:15 2011 Question mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2185Rename Logbook

I have a logbook with data in it that I need  to  rename  and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?

As always thank you for your time.

  67114   Mon Sep 5 17:10:19 2011 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2185Re: Rename Logbook

mike cianci wrote:

I have a logbook with data in it that I need  to  rename  and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation. 

  67125   Fri Sep 23 01:16:30 2011 Reply mike ciancimike2.cianci@comcast.netQuestionWindows2.7.5-2185Re: Rename Logbook

Stefan Ritt wrote:

mike cianci wrote:

I have a logbook with data in it that I need  to  rename  and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation. 

 Sorry, about this dumb question but with  "Copy to = <logbook list> " what is the format of  <logbook list>?

Is it just the "logbook Name" or is it the actual path name   "http://something/somethingelse"?

  67126   Fri Sep 23 10:46:58 2011 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindows2.7.5-2185Re: Rename Logbook

mike cianci wrote:

Stefan Ritt wrote:

mike cianci wrote:

I have a logbook with data in it that I need  to  rename  and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?

As always thank you for your time.

There are two ways:

1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.

2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.

The second solution is much simpler, but you have to manipulate files and directories yourself.

Whatever you do, make sure to back up you files before any operation. 

 Sorry, about this dumb question but with  "Copy to = <logbook list> " what is the format of  <logbook list>?

Is it just the "logbook Name" or is it the actual path name   "http://something/somethingelse"?

 In order to copy (or move) files from one logbook to another, you first need to ensure that  the
appropriate commands are in the section of elogd.cfg of the logbook the files move *from* (called 'current')

 - made up elogd.cfg to show this, and obviously only the pertinant lines

[Global]

Group = current, Y2011, Y2010, Y2009...

...


 [current]
...
Menu commands = New, ... Copy to, ...
...
Copy to = Y2011, Y2010, Y2009 ...
...
 - end of made up example.
 
So to solve your problem, the <logbook list> is simply the list of logbooks in
this part of elogd.cfg after the 'Copy to =' line in the elogd.cfg file (Y2011, Y2010, Y2009...)  

You also need to ensure that the directory to which the entries are to be copied to exists!

('Move to' would be faster if you are going to delete the entries in 'current' afterwards, but as always, it depends on

your perception of risk.)


For the user, the logbook list is the set of logbooks that appear in the
drop-down menu by the side of "Copy to" in the menu bar, and it allows you to
move that entry (or thread of entries if more than one) to the selected destination.

---

My reason for answering this is because I have actually done this operation 'in
anger' some time ago and regularly since, and would have answered before if Stafan had not beaten me
to it.  I used what was Stefan's second method, which, for those who are
reasonably confident with file manipulation, is far faster, and, dare I say,
less prone to 'unexpected' issues - some here will know what I'm
getting at.

So I say, "Back up your files and take the plunge", I would have put something
else but this is a family friendly forum.

But you must bear in mind my views are those seen through the filter of a
regular Elog ab-user, which may be why Stefan worked so hard to answer before
me ;-)

 

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

ELOG V3.1.5-3fb85fa6