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 #9821 (accepted)

Opened 7 years ago

Last modified 4 years ago

Path/names of files should be sensible to users

Reported by: jamoore Owned by: jamoore
Priority: blocker Milestone: 5.0.0-beta1
Component: OmeroFs Keywords: fs
Cc: ux@…, fs@…, mtbcarroll Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: 0.0d Estimated Remaining Time: n.a.

Description

In order to increase the users' trust in the FS, all files stored in the managed repository should to the extent possible be easily identifiable by their paths. Similarly, all queries returning OriginalFile objects should return objects which are what the user expects. This will require (numerous) trade-offs between what the user really wants (a full OS-level filesystem) and what we can sensibly offer while also maintaining the Postgres DB.

Probably the most important aspect of making the names sensible is to have the correct (bug not too much) configurability in the clients and API. And what's not configurable should be simple and standardized.

Change History (12)

comment:1 Changed 7 years ago by wmoore

It seems to me that it's essential for the clients to support this path in their UI if we're going to ask users to configure it in the clients. It's tricky enough to make an intuitive UI for path configurability if you don't give the user any feedback on how their choice affects anything.

So we have to allow users to browse their FS data via path in the clients before we ask them to configure it (IMHO).

comment:2 Changed 7 years ago by jmoore

I disagree that we have to allow users to browse their FS data first. I think we can start by showing them how it will map (C:\Users\me\Desktop\Data\Good\OME-TIFF\Tuesday\foo.ome.tif --> OME-TIFF\Tuesday\foo.ome.tif). But otherwise, agreed. We need to provide them good feedback so they know what to expect.

comment:3 Changed 7 years ago by jmoore

  • Cc sylittlewood added

comment:4 Changed 7 years ago by mtbcarroll

  • Cc mtbcarroll added

comment:5 Changed 7 years ago by agilo

  • Status changed from new to accepted

Updated status, related task in progress

comment:6 Changed 7 years ago by jmoore <josh@…>

(In [da774d18191d63c7ddc2ce4f6a7d7d95b22fbdc9/ome.git] on branch develop) Initial draft of the new Fileset objects (See #9821)

Though there are likely other types and fields needed,
I'm uploading this so everyone can take a first look.

comment:7 Changed 7 years ago by jburel

  • Milestone changed from OMERO-4.5 to OMERO-5

comment:8 Changed 7 years ago by pwalczysko

  • Cc ux@… fs@… added; bpindelski jburel cblackburn wmoore sylittlewood removed

comment:9 Changed 7 years ago by jmoore

  • Resolution set to fixed
  • Status changed from accepted to closed

Demoed today. See #10310.

comment:10 Changed 7 years ago by agilo

  • Status changed from closed to accepted

Updated status, related task in progress

comment:11 Changed 7 years ago by jamoore

  • Status changed from accepted to closed

Largely with demo 2 and certainly with demo 3 this work can be considered stable.

comment:12 Changed 4 years ago by agilo

  • Status changed from closed to accepted

Updated status, related task in progress

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.272259 sec.)

We're Hiring!