| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65879
|
Tue May 13 16:58:40 2008 |
 | Yoshio Imai | | Question | | 2.7.3-1024 | Re: Access Control |
| Grant Jeffcote wrote: | | At present we can give others a full view by adding them to the 'Users' list for each individual logbook, this unfortunately also gives them 'write' access. |
I think the solution to your problem would be to use Deny statements in the configuration sections for the logbooks.
Assume user1, user2 and user3 are in the "owners'" group of logbook1, and user4 and user5 only have "privileged read" access. Then a configuration as follows might help:
Login user = user1, user2, user3, user4, user5
Deny New = user4, user5
Deny Reply = user4, user5
Deny Duplicate = user4, user5
Deny Edit = user4, user5
Deny Delete = user4, user5
Deny Select = user4, user5
Deny CSV Import = user4, user5
This should give them the same read permissions as the logbook owners but should deny any writing operations. I recognize that this is a little bit of admin work if the lists of such "privileged readers" gets long, but each user would have his/her individual password (even the same as for access to his/her "own" logbook).
Perhaps you can give it a try. |
|
65880
|
Tue May 13 21:56:30 2008 |
| Grant Jeffcote | grant@jeffcote.org | Question | | 2.7.3-1024 | Re: Access Control |
| Yoshio Imai wrote: |
| Grant Jeffcote wrote: | | At present we can give others a full view by adding them to the 'Users' list for each individual logbook, this unfortunately also gives them 'write' access. |
I think the solution to your problem would be to use Deny statements in the configuration sections for the logbooks.
Assume user1, user2 and user3 are in the "owners'" group of logbook1, and user4 and user5 only have "privileged read" access. Then a configuration as follows might help:
Login user = user1, user2, user3, user4, user5
Deny New = user4, user5
Deny Reply = user4, user5
Deny Duplicate = user4, user5
Deny Edit = user4, user5
Deny Delete = user4, user5
Deny Select = user4, user5
Deny CSV Import = user4, user5
This should give them the same read permissions as the logbook owners but should deny any writing operations. I recognize that this is a little bit of admin work if the lists of such "privileged readers" gets long, but each user would have his/her individual password (even the same as for access to his/her "own" logbook).
Perhaps you can give it a try. |
What a great solution, thanks Yoshio, it works a treat. |
|
65881
|
Thu May 15 01:06:21 2008 |
| Dennis Seitz | dseitz@cosmology.berkeley.edu | Question | All | latest | Re: 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... |
|
65882
|
Thu May 15 17:45:44 2008 |
| Grant Jeffcote | grant@jeffcote.org | Question | | 2.7.3-1024 | Re: Access Control |
| Grant Jeffcote wrote: |
| Yoshio Imai wrote: |
| Grant Jeffcote wrote: | | At present we can give others a full view by adding them to the 'Users' list for each individual logbook, this unfortunately also gives them 'write' access. |
I think the solution to your problem would be to use Deny statements in the configuration sections for the logbooks.
Assume user1, user2 and user3 are in the "owners'" group of logbook1, and user4 and user5 only have "privileged read" access. Then a configuration as follows might help:
Login user = user1, user2, user3, user4, user5
Deny New = user4, user5
Deny Reply = user4, user5
Deny Duplicate = user4, user5
Deny Edit = user4, user5
Deny Delete = user4, user5
Deny Select = user4, user5
Deny CSV Import = user4, user5
This should give them the same read permissions as the logbook owners but should deny any writing operations. I recognize that this is a little bit of admin work if the lists of such "privileged readers" gets long, but each user would have his/her individual password (even the same as for access to his/her "own" logbook).
Perhaps you can give it a try. |
What a great solution, thanks Yoshio, it works a treat. |
Is there any way to give a logged in user a 'Guest' view on certain logbooks?
Unfortunately at the moment if they are not in the 'login users = ' group they are automatically logged out and have to re-log back into their own logbook. |
|
65885
|
Sun May 18 06:20:00 2008 |
| Mark Soohoo | marksoohoo@hotmail.com | Question | Windows | 2.7.3-2095 | Re: Help me please I can't uplode Attach file |
| Stefan Ritt wrote: |
|
| Samrit wrote: |
|
Dear All
I can't uplode Attach file. It have Error
| Error: Filename "D:\aaa.doc" contains invalid character |
| Please use your browser's back button to go back |
Thank you very much
Joe..
|
The problematic part is the "\" in the filename, which is not correctly recognized as a directory. I will fix this in the next release. For now, just click on the Browse button, navigate to d:\, and then select there the file aaa.doc.
|
Hi, I'm having the same problem, too, when attempting to upload an attachment. I'm using version 2.7.3-2095.
I wasn't able to attach an image by clicking on the Browse button, clicking on the desired file, hitting the Open button, and then hitting the Upload button. I just noticed that I could upload my error screen to this forum:
Thanks for any help you can provide.
Mark
|
|
65889
|
Fri May 23 13:38:52 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | | Re: Can u send me the configuration file for this logbook ? |
| Franck C wrote: |
|
| Stefan Ritt wrote: |
|
| Franck C wrote: |
|
Hi, I try to set up a logbook and i wanted to create something with icons (like this logbook) and it will be easier for me if i have ur config file 
Thanks a lot
Franck
|
https://midas.psi.ch/elogs/Config+Examples/2
- Stefan
|
Ok thanks... but i meant this Forum logbook... Can u give me the configuration file and the css file if i need a different one ?
thanks a lot by advance
|
The forum logbook is here:
https://midas.psi.ch/elogs/Config+Examples/4
the CSS file you can directly load from the server under
https://midas.psi.ch/elogs/forum/forum.css |
|
65891
|
Mon Jun 2 11:11:27 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.7.0 | Re: Possible to sort attribute chronologically? | > 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?
I tried to reproduce what you said and it worked fine for me. I used:
[demo]
Attributes = Author, Type, Last Edit, Subject
Subst on edit Last Edit = $entry time
And got correctly the entry time copied to the "last edit" field when I changed old entries. I used version V.7.3-2104. |
|
65892
|
Mon Jun 2 12:01:47 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? |
| Dennis Seitz wrote: | 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? |
Ok, now I got your point. Sorry for the late reply, but I was extremely busy the last few weeks. I added the missing functionality to elog revision 2108, so the 'subst on edit Last Edit = $entry date' does now work. |
|