Re: can attrinute fields contain more that one line, posted by Paolo Franchini on Fri Nov 20 11:20:49 2015
|
> > > Was just wondering about the status of the multi-line attributes in Elog, are
> > > they implemented in elog yet? If not is that something you are planning to do
> > > in the future?
> >
> > In order to have multi-line attributes, the whole format of the logbooks has to be
> > changed. I plan to use XML for the logbook format in the future. We would not have
> > any more one file per day, but one big file per logbook. I have already some XML
> > functionality in elog, but this one requires a major rewrite of the whole code. On
> > the other hand, searching etc. will become much faster afterwards. I plan to start
> > this development soon, but it might take quite some time, so don't expect it
> > before summer or fall.
> >
> > Best regards,
> >
> > Stefan
>
> Thanks for your help, thats useful to know.
>
> Paul
Hi Stefan,
any update on the multi-line request?
cheers,
Paolo |
|
Re: can attrinute fields contain more that one line, posted by Paolo Franchini on Fri Nov 20 15:27:12 2015
|
> > > > > Was just wondering about the status of the multi-line attributes in Elog, are
> > > > > they implemented in elog yet? If not is that something you are planning to do
> > > > > in the future?
> > > >
> > > > In order to have multi-line attributes, the whole format of the logbooks has to be
> > > > changed. I plan to use XML for the logbook format in the future. We would not have
> > > > any more one file per day, but one big file per logbook. I have already some XML
> > > > functionality in elog, but this one requires a major rewrite of the whole code. On
> > > > the other hand, searching etc. will become much faster afterwards. I plan to start
> > > > this development soon, but it might take quite some time, so don't expect it
> > > > before summer or fall.
> > > >
> > > > Best regards,
> > > >
> > > > Stefan
> > >
> > > Thanks for your help, thats useful to know.
> > >
> > > Paul
> >
> > Hi Stefan,
> >
> > any update on the multi-line request?
>
> Nope. Too many other things to do during my "day job".
>
> Stefan
Thank you, your eLog is already a very good instrument! |
multiple "text entry" field, posted by darshak on Mon Jul 12 09:07:32 2004
|
Is it possible to add one more "text entry" field ? |
|
Re: multiple "text entry" field, posted by darshak on Wed Jul 14 08:57:37 2004
|
Your guess is correct. I would like to have that feature in ELOG.
Thanks
> > Is it possible to add one more "text entry" field ?
>
> I guess you mean the main body text, which is multi-line. No, this is not
> possible right, now, but I added your vote to the wishlist istem "Multi-line
> attributes". |
|
Re: Author name in reply to entry is from original poster, posted by Max on Thu Oct 10 12:01:10 2019
|
Brilliant in all its simplicity! Many thanks!
| Stefano Lacaprara wrote: |
|
This should do the trick
Preset on reply Author = $long_name
Best, Stefano
| Max wrote: |
|
My elog has this config for the author:
Option Author = Filled In Automatically
Preset Author = $Long_name
Locked Attributes = Author
This works as intended: when you submit a new entry, the author name is filled in automatically and cannot be changed.
However, when Alice wants to post a reply to an entry the Bruce has made, the preset author name does not say Alice, it says Bruce. I haven't been able to find out how to change this (other than make the author name editable). Even when Author isn't configured as as locked attribute, it still displays the original author's name.
How can I get this to work like I want/need to?
|
|
|
|
Quick filter for date, posted by Michael on Thu Jul 16 11:18:05 2009
|
Hello !
Is any posibility to set quick filter, for fields with atribute "date", to exactly value, like 15/07/2009, instead of drop menu with values like - last day, last week, etc ?
Tnx in advance !
|
|
Re: Quick filter for date, posted by Michael on Thu Jul 16 13:47:31 2009
|
| Stefan Ritt wrote: |
|
| Michael wrote: |
|
Hello !
Is any posibility to set quick filter, for fields with atribute "date", to exactly value, like 15/07/2009, instead of drop menu with values like - last day, last week, etc ?
Tnx in advance !
|
No, this is not imlemented. But you can go to the "Find" page, and select the "Start" and "End" date with the calendar picker tool. This are a few more clicks to do, but puttting this all into the quick filter would not fit there.
|
ok, tnx. |
Re: Truncation of the displayed text in Summary view of the list of entries, posted by Olivier Callot on Wed Mar 14 15:08:17 2012
|
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.
|
That's a feature 
In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose.
|
Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway. |
|