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

Opened 13 years ago

Last modified 8 years ago

RFE: Add Group/Project/Datasets to DropBox

Reported by: cblackburn Owned by: cblackburn
Priority: major Milestone: GatherReqs
Component: OmeroFs Keywords: n.a.
Cc: jamoore Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by jmoore)

Using some config value let DropBox? import into existing Projects/Datasets? or create new ones on the fly.

Could use directory structure with DropBox? directory? How would Screens/Plates? be handled?

#9899

In https://github.com/ximenesuk/openmicroscopy/commits/dropbox_dataset_4_4 an ad hoc solution is provided as an example for using a directory structure to allow DropBox imports to be made into projects and datasets. This could be formalised using a config option and also allow an import group (as an option) to be selected. For instance, files copied under:

/OMERO/DropBox/user/group/project/dataset/

would be imported into project/dataset of group if all three existed. The project and dataset could be created on demand (as in the branch above). If the path items failed to resolve properly the image could still possibly be imported as an orphan into the default group.

Change History (7)

comment:1 Changed 11 years ago by jmoore

  • Description modified (diff)
  • Summary changed from Allow Project/Datasets for DropBox? to RFE: Add Group/Project/Datasets to DropBox

Closing #9899 as a duplicate.

comment:2 Changed 9 years ago by cblackburn

  • Milestone changed from Unscheduled to 5.1.0-m2
  • Owner set to cblackburn
  • Status changed from new to accepted

comment:3 Changed 9 years ago by jamoore

  • Milestone changed from 5.1.0-m2 to 5.1.0-m3

Pushing to m3. Colin: should this be converted to a task?

comment:4 Changed 9 years ago by cblackburn

  • Milestone changed from 5.1.0 to 5.1.1

comment:5 Changed 9 years ago by cblackburn

  • Milestone changed from 5.1.1 to 5.1.2

comment:6 Changed 8 years ago by jamoore

  • Milestone changed from 5.1.4 to OMERO-5.1.4

Splitting 5.1.4 due to milestone decoupling

comment:7 Changed 8 years ago by jamoore

  • Milestone changed from 5.x to GatherReqs
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.64350 sec.)

We're Hiring!