> > elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned in the documentation,
> > in the release announcement and in the release and migration notes. K.O.
> 
> But yes, the release documentation by bitbucket is not really that useful: 
> it is difficult for me too, to find out what changed with new releases. 

I did know that I've read it summarized somewhere!
The changes with the different releases are documented here:
http://midas.psi.ch/elog/download/ChangeLog

It is actually not so difficult to find: 
it is linked on the "Download" section http://midas.psi.ch/elog/download.html

"News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"

And for version 3.0.0 it states:
- Create one logbook subdirectory pear year

I admit that version 3.0 has never been announced and the changelog is not mentioned in the announcement of version 3.1.0
Maybe we'll do better in the future ;-)

> 
> "News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"
> 
> And for version 3.0.0 it states:
> - Create one logbook subdirectory pear year
> 

The text should read:

the first time you run the new elogd against old elog data,
all existing entries will be moved into by-year subdirectories
and the old elogd will not work anymore.

K.O.

Hello,

Let's say I have a logboook where I define two attributes:

[TOTEM]
Comment = TOTEM Gas System Status
Attributes = Author, D, M, Y, h, min, ...

I would like to modify the "Last submission" so that I display something like %D/%M/%Y, %h:%min

so in my elogd.cfg I added this line:

Last submission = $D / $M / $Y , $h : $min by $Author

however, when display in the selection page instead of getting $min displayed i get the attribute $M+'in' displayed. How does attributes substitution work? is it case unsensitive? how does it behave when different attributes starts with the same name?

There could be a bug which is triggered by the fact that $M is a substring of $min. Try to rename $M to $Month or so.

Stefan

Hi Stefan,

I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command.

Could that be added? I can think of a multitude of applications:

• In my case I want to fill an attribute X either with free text or generated from other fields. The list view will show just X and not how it was generated.
• I could fill an attribute automatically with the character length of the text.
• I could parse the text in a shell script and set other attributes according to the content.

Thank you for considering it.

Cheers, Andreas

$text is the full body text and can go over many lines. Since attributes are restricted to single lines, it's not possible to substitute them with the body text.

Stefan

While the input widget of text attributes is a single line, they can easily be multi-line in the display - when you use HTML at least.
And of course the user can parse the text field and generate a single line, if he wants to.
If you leave it to me, I'll create wonderful applications to that feature :-)

Please? ;-)