Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 641 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  65799   Tue Apr 1 02:04:35 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll Duplicate entry suggestion

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

Thanks,

Dennis

  65802   Tue Apr 1 20:31:26 2008 Reply Dennis Seitzdseitz@berkeley.eduRequestAll Re: Duplicate entry suggestion

 

Stefan Ritt wrote:

 

Dennis Seitz wrote:

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

 

I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically.

 

Thanks, I was not aware of that - usually I have copied and pasted the entire path from my browser.

In any case, can you consider my request for possible future implementation? I think it's a useful function. For now, it's really no big deal to simply copy the url before selecting the Copy To: menu and then replacing the body text with the copied link. But I think it would be more useful to make this happen automatically, so I don't have to ask users to comply voluntarily.

Thank you.

 

  65804   Tue Apr 1 21:24:17 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll attachment indicator in summary view

 It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.

Thanks.

  65812   Sat Apr 5 00:43:21 2008 Smile Dennis Seitzdseitz@cosmology.berkeley.eduRequestAll Re: attachment indicator in summary view

 

Stefan Ritt wrote:

 

Dennis Seitz wrote:

 It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.

 

Nice idea. I implemented that feature, as can be seen at the contributions logbook for example. It will be contained in the next release.

Thanks!

 

  65863   Tue Apr 29 02:00:03 2008 Reply Dennis Seitzdseitz@cosmology.berkeley.eduQuestion 2.7.0Re: Possible to sort attribute chronologically?
> > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
> 
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.

Thank you for pointing out the method to identify Last Edit as a datetime type so that it will sort properly. I now have created Last Edit in several 
preexisting logbooks. 

I want to use 
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit. 

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I 
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry. 

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about 
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to 
another's?

Thanks
  65873   Wed May 7 17:10:07 2008 Question Dennis Seitzdseitz@berkeley.eduQuestionAlllatest$entry time not readable by Subst, else not datetime type?
I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:


Thank you for pointing out the method to identify an attribute as a datetime type so that it will sort properly. I now have created my "Last Edit" attribute in several
preexisting logbooks.

I want to use
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit.

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry.

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to
another's? To reiterate, I want to initialize Last Edit = $entrytime for all entries that have not been re-edited.

Thanks
  65881   Thu May 15 01:06:21 2008 Reply Dennis Seitzdseitz@cosmology.berkeley.eduQuestionAlllatestRe: Re: $entry time not readable by Subst, else not datetime type?

Dennis Seitz wrote:
I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:


Thank you for pointing out the method to identify an attribute as a datetime type so that it will sort properly. I now have created my "Last Edit" attribute in several
preexisting logbooks.

I want to use
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit.

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry.

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to
another's? To reiterate, I want to initialize Last Edit = $entrytime for all entries that have not been re-edited.

Thanks


OK, now I realize how stupid I sound here. To partially answer my own question: $entry time is a string and Last Edit is now a number since I have changed it to the datetime type so that it will sort properly.

So I can't make Last Edit = $entry time. Is there some way I can access the entry time in datetime format so that I can set Last Edit equal to that?

Sorry if I'm missing something obvious, I'm confused...
  65884   Thu May 15 19:57:23 2008 Question Dennis Seitzdseitz@cosmology.berkeley.eduQuestion  Is there a way to indicate when an entry has been edited?

 You've probably seen my other posts on this subject.

I want to be able to re-edit some entries but I need some way to know the dates entries were re-edited.

Am I just approaching this the wrong way? Should I disable re-editing of entries and use threads to follow changes by posting replies to an entry?

The only problem with that is that if I make a mistake I will have to submit a new entry to fix it. 

 

Thank you for your advice.

ELOG V3.1.5-3fb85fa6