Need some solution for collaborative file creation

[GoogleCodeExporter]

See also issue xx

Having some kind of solution for collaborative file updating is needed; e.g. 
for group files imported ffrom another storage medium.  The collaboration area 
pattern falls foul of a ACL bug.

Maybe introduce a new user who's shared and collab areas are read-write to all 
RGMember users?

Needs testing.

Original issue reported on code.google.com by gk-goo...@ninebynine.org on 23 May 2011 at 2:45

[GoogleCodeExporter]

See also issue 16, issue 25

Original comment by gk-goo...@ninebynine.org on 23 May 2011 at 2:46

[GoogleCodeExporter]

Outline plan:

1. Up to date deployment of ADMIRAL on zakynthos
2. Test alternative protections on collab area:  find a configuration that 
provides the desired charing capability
3. Decide how to deploy --- NEEDS DISCUSSION
4. Create new test cases
5. Update deployment scripts & test
6. Roll out to zoo-admiral-ibrg and test
7. Negotiate roll-out with user groups.

Original comment by gk-goo...@ninebynine.org on 7 Jun 2011 at 9:30

[GoogleCodeExporter]

TestCases that worked after collab area's acl changes:

Having given write permissions through ACLs to RGMembers in collab area, the 
problem seems to be resolved.
With this change, RGMembers have read/write access to each others' collab files 
while the RGCollaborator can only view them but not edit them and hence works 
as expected.
Tried modifying it from linux, logging in as TestUser1(RGMember) and was able 
to write into TestUser2(RGMember)'s collab area file (ie. su TestUser1 and then 
did the operations)
Tried modifying it from linux, logging in as TestCollab(RGCollaborator) and was 
able to read TestUser2(RGMember) ' collab area file but not write to it (ie. su 
TestUser1 and then did the operations)
Hence the solution works rightfully as expected.

________________________________________________________________________________
__

Problem with:

Problem with mapping windows network drive on the testsystem/data as 
TestCollab(RGCollaborator). It is not letting me map the drive

But I am able to map the drive as TestUser1(RGMember) or TestLeader(RGLeader) 
and I see that they work as expected in the collab area.

Original comment by bhavana....@gmail.com on 8 Jun 2011 at 4:09