| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67927
|
Thu May 21 10:59:07 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Comment | All | 3.1.0 | Re: elogd moves elog entries |
I had no intention of causing any offence with my lazy archiving comment - hope I didn't, sorry if I did.
No offence taken :-)
Personally, I would have found it useful to put the attachments into a separate directory - or at least to allow
the possibility. Elog as it stands sometimes can, and sometimes cannot cope with that functionality - and even to try means messing around directly with the
yymmdda.log files. For me it would have saved me having duplicates of the same large attachment in two or three different logbooks, if I could always reference
the same Master copy of the attachment. This was at the time I was severely memory constrained, and in part forced me to change how I had operated elog, so for
me that need isn't as great as it once was.
David.
You can put a reference to the attachment of the other entry in your logbook: elog:67896/1
Or, if it is an image, you can just include it in your new entry like I did below.
Of course this only works if the other logbook is accessible on-line.
But how would you manage access rights to a common attachment folder?
Probably I just did not understand your idea.
Cheers
Andreas
|
|
67928
|
Thu May 21 12:13:21 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | All | 3.1.0 | Re: elogd moves elog entries | > > 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 ;-) |
|
67935
|
Tue May 26 11:26:12 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.0 | Re: Fixed text | Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
| Neal Grafton wrote: |
|
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
67938
|
Wed May 27 08:41:05 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.0 | Re: Fixed text | Hi Neal,
you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.
But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.
Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.
You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.
Did you've set up the demo logbook and played around with it? Because your question suggests to me that you don't figured out yet what ELOG does. (Or as a direct answer: no, it does not make sense to me ;-) )
But I'm sure you'll figure it out: ELOG is best learned by trial and error.
Kind Regards
Andreas
| Neal Grafton wrote: |
|
Sorry I call this field that you write in the subject field, a little confusing.
So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)
Neal
| Andreas Luedeke wrote: |
|
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
| Neal Grafton wrote: |
|
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
|
|
67940
|
Wed May 27 08:54:27 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.0 | Side effects of draft messages (was Fixed text) | Hi Stefan,
I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.
I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).
It feels wrong if I watch people while they making an entry ;-)
Anyway, it is just an idea.
Cheers
Andreas
| Neal Grafton wrote: |
|
Thanks Andreas
We are still playing around with ideas, just thought I'd ask, didn't think it was possible.
We are ok with setting attributes but this is new to us as yet so may have more questions later.
| Andreas Luedeke wrote: |
|
Hi Neal,
you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.
But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.
Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.
You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.
Did you've set up the demo logbook and played around with it? Because your question suggests to me that you don't figured out yet what ELOG does. Or as a direct answer: no, it does not make sense to me ;-)
But I'm sure you'll figure it out: ELOG is best learned by trial and error.
Kind Regards
Andreas
| Neal Grafton wrote: |
|
Sorry I call this field that you write in the subject field, a little confusing.
So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)
Neal
| Andreas Luedeke wrote: |
|
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
| Neal Grafton wrote: |
|
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
|
|
|
|
67941
|
Wed May 27 10:50:41 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | V2.9.0-239 | Re: RSS Feed Not Providing Time Stamps For datetime Attributes | Hi Kamen,
I've just tried it for V3.1.0 (6ab0fd5) and the described behaviour is unchanged.
It is even worse if you don't specify the "RSS Title": datetime attributes are just displayed as seconds of the epoch then.
I think this is a feature of ELOG at the moment.
You'll either need to dig into the code yourself or wait for Stefan to fix it.
I have an idea for a quick workaround:
you can create new hidden attributes, that contains a copy of the datetime attribute as a string, set by the subst command. You could then use those string attribute in the "RSS Title": that should work.
Cheers
Andreas
| Kamen Nikolov wrote: |
|
Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?
Thanks,
Kamen
| Kamen Nikolov wrote: |
|
Hello,
I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?
Additional info:
I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).
Please let me know if I am doing something incorrectly?
Thanks
|
|
|
|
67944
|
Fri May 29 09:38:40 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Request | Other | 3.1.0 | ELOG Version field in elogs/Forum | Hi Stefan,
could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
number?
That would be 13 characters.
Cheers
Andreas |
|
67945
|
Fri May 29 09:46:11 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.0-2 | ELOG Forum: drafts cannot be deleted | I wanted to reply to the post "Three problems..." and then changed my mind.
But since this logbook does not allow to delete entries (not even my own) I was neither able to remove the draft
nor the final entry.
Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.
Cheers
Andreas |
|