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"

User Story #978 (closed)

Opened 16 years ago

Closed 13 years ago

Support CMS-like view on files for users

Reported by: jamoore Owned by: cblackburn
Priority: minor Milestone: Unscheduled
Component: OmeroFs Keywords: usecas, Scripting, stdout, stderr
Cc: dzmacdonald Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.


Adding to the OmeroFs use cases here: a user would most likely want a filesystem-like view on his or her scripts and script outputs. First to find the scripts, there should be a directory which can be well organized:

   |_ matlab/
   | |_ a.m
   | \_ b.m
   |_ python/
     |_ a/
     \_ b/

(This is not only important for organizational purposes, but the naming of say the matlab scripts is criticial to being able to load them from the path.)

Then, all job outputs could go in another directory:

 |_ 001
 | |_stdout
 | \_stderr
 |_ 002
 \_ 003

One question is how do we present these directory structures to the user? Making them show up for the server is fairly straight-forward, but you can imagine a user wanting to make a listing of all files:

 |_ OmeroFs1
 |  |_ scripts/
 |  \_ joboutput/
 |_ OmeroFs2
    \_ somethingelse

but then what do you do about permissions?

Note: A possible alternative to having all of this done in OmeroFs would be to use tagging (one tag for each directory level), but I don't think this would make the stored files nearly as easy to use.

Change History (4)

comment:1 Changed 15 years ago by cblackburn

  • Status changed from new to assigned

Moved to Future to clear from 4.0. Needs to be rescheduled.

comment:2 Changed 15 years ago by cblackburn

  • Milestone changed from OMERO-Beta4 to Future

comment:3 Changed 13 years ago by cxallan

  • Status changed from assigned to new

Closing in favor of the overarching story #909.

comment:4 Changed 13 years ago by cxallan

  • Resolution set to duplicate
  • 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.63860 sec.)

We're Hiring!