Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #10319 (closed)

Opened 11 years ago

Closed 11 years ago

ManagedRepo should handle top-dir differently

Reported by: jamoore Owned by:
Priority: critical Milestone: 5.0.0-beta1
Component: OmeroFs Version: n.a.
Keywords: fs Cc: fs@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: FS Demo 2

Description

Per discussions last week in Dundee, the top directory of a managed repository should be handled specially. Namely, it should represent a single user and only that user should be allowed to create files within that directory. Additionally, this should either be done by placing those directories in the "user" group (so that they are always visible/linkable) or they should not be original files at all. In the latter case, it will be necessary to handle the case where usernames change, most likely by encoding the user Id in the directory name as well.

This directory will be the top, hard-coded element of the template path (%USERNAME%_%USERID%)

Change History (2)

comment:1 Changed 11 years ago by jmoore

  • Sprint set to FS Demo 2

comment:2 Changed 11 years ago by jmoore

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67686 sec.)

We're Hiring!