Is it possible to preset an attribute with the current weeknumber?

Excellent thanks

> In the current source which ive compiled and am using on our elog system, 
> the feature that you put in for me that says "Entry is currently being 
> edited by Joe Bloggs on 192.168.0.10" has vanished.
> 
> It removes existing locks from before updating the binary but doesnt but 
> new ones on.
> 
> Is this something that was removed intentionally or by accident ?

No, but there is now a flag "Use Lock = 0 | 1" which is zero by default, 
since not all people want this feature. So put a "Use Locl = 1" and you 
should be fine gain.

In the current source which ive compiled and am using on our elog system, 
the feature that you put in for me that says "Entry is currently being 
edited by Joe Bloggs on 192.168.0.10" has vanished.

It removes existing locks from before updating the binary but doesnt but 
new ones on.

Is this something that was removed intentionally or by accident ?

Thanks

Very interesting, indeed!
Thank you very much for the implementation. I believe this is a big step ahead 
in terms of ELOG screen formating (and therefore easier/more ergonomic 
dataentry/reading).

We will test your modifications as soon as you make a new release.

Tomas


> I implemented your request. The syntax is:
> 
> Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>
> 
> <flags>
>   Sum of following values:
>     1: Display attribute in same line as previous attribute
>     2: Display radio buttons or check boxes in separate lines (if applicable)
> 
> <css_class_name>,<css_class_value> 
>   Cascading Style Sheet class names used for cells containing attribute name
>   or value, respectively. The classes must be defined in the style sheet file 
>   (usually themes/default/default.css)
> 
> <width>> 
>   Width of the text entry field in characters
> 
> <size> 
>   Maximum number of characters allowed. 
> 
> Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
> ommitted, so specifying for example only the flags is possible.
> 
> In order to have several attributes in one line, each line is now a separate 
> table. This requires adjustment of the CSS class "attribname". Best you use 
> the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).
> 
> You can compare the two different approaches (one attribute per line/multiple 
> attributes per line) in this forum and the "archive" logbook. The "subject" 
> field in this forum also uses a different style class.
> 
> Note that if you upgrade to the current CVS version 
> (http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
> have to change following options in your elogd.cfg:
> 
> - The style sheet must contain the new class "attribhead"
> - "Email message body" has been replaces by "Email format"
> - "Filtered browsing" is now off by default
> - Locking (during editing of messages) is disabled by default, and enabled 
> by "Use lock = 1"

I implemented your request. The syntax is:

Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>

<flags>
  Sum of following values:
    1: Display attribute in same line as previous attribute
    2: Display radio buttons or check boxes in separate lines (if applicable)

<css_class_name>,<css_class_value> 
  Cascading Style Sheet class names used for cells containing attribute name
  or value, respectively. The classes must be defined in the style sheet file 
  (usually themes/default/default.css)

<width>> 
  Width of the text entry field in characters

<size> 
  Maximum number of characters allowed. 

Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
ommitted, so specifying for example only the flags is possible.

In order to have several attributes in one line, each line is now a separate 
table. This requires adjustment of the CSS class "attribname". Best you use 
the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).

You can compare the two different approaches (one attribute per line/multiple 
attributes per line) in this forum and the "archive" logbook. The "subject" 
field in this forum also uses a different style class.

Note that if you upgrade to the current CVS version 
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
have to change following options in your elogd.cfg:

- The style sheet must contain the new class "attribhead"
- "Email message body" has been replaces by "Email format"
- "Filtered browsing" is now off by default
- Locking (during editing of messages) is disabled by default, and enabled 
by "Use lock = 1"

Announcing:  elog2sql

elog2sql was created to help translate logbooks created by the program
``elog'' from the native elog flat file format to a MySQL database.  I had a
need to have the elog data in a database, and it appears from the forum that
several others had a similar need.

 I created a set of perl scripts that will allow the translation of elog
logbooks into a MySQL database. The design and implementation of these
scripts are a simple one, and allow the one-time copying of a set of logbooks.

The elog2sql toolkit consists of two scripts. The first script, parsecfg.pl,
reads a elogd.cfg, and creates a sql file that will create a set of db
tables corresponding to elog logbooks. The second script, parselog.pl, takes
a set of elog logfiles, and creates a sql file that will enter the logbook
data into the database. The result is a copy of the elog logbook that can
used as desired inside the framework of MySQL. Attachments are handled by
inserting an entry of the attachment name into an seperate attachment table.
This allows multiple attachments per entry.

You can download the elog2sql program archive at
http://www.davidfannin.com/elog2sql/elog2sql.tar.gz . It contains the
scripts and basic documentation.  You can read the man page at
http://www.davidfannin.com/elog2sql/index.html 

email for questions or comments.

You guessed right. I give it a try soon as I get a chance. Thanks.

> I guess you have a global password file and use "login user" statements for 
> your logbooks. I have added some code which does per default not send any 
> email to people who are not in the "login user" list, in case this list is 
> present. New code under CVS. Please give it a try and let me know if it works 
> for you.
> 
> - STefan