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 #2621 (closed)

Opened 14 years ago

Closed 8 years ago

Last modified 8 years ago

CLI: Import to a dataset by name

Reported by: jamoore Owned by: cblackburn
Priority: minor Milestone: OMERO-5.2.2
Component: Import Version: OMERO-5.2.0
Keywords: n.a. Cc: cxallan, jburel, oliver.mueller@…, cblackburn
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by jburel)

Allow importing to a dataset by name
From Oliver Mueller:

My final questions:
- Why do I have to address my dataset by its ID? Can it be also a string "dataset_name"? (see next question)
- Is it possible to implement something like "config.dataset.set("dataset_name")" and "config.project.set("my_projectname")"?
This would be a nice and consistent interface ;-)

Change History (9)

comment:1 Changed 13 years ago by jburel

  • Description modified (diff)
  • Summary changed from Allow importing to a dataset by name to CLI: Import to a dataset by name

comment:2 Changed 12 years ago by jburel

Referencing ticket #2118 has changed sprint.

comment:3 Changed 12 years ago by jburel

  • Cc cblackburn added

comment:4 Changed 12 years ago by jburel

  • Cc bwzloranger removed
  • Owner bwzloranger deleted

comment:5 Changed 8 years ago by jburel

  • Milestone changed from Unscheduled to FacilityManagers
  • Version set to OMERO-5.2.0

comment:6 Changed 8 years ago by jamoore

  • Owner set to cblackburn

I would assume this could be marked done for 5.2.2, right, Colin? (Though there may be follow-ons re: docs & refinements)

comment:7 Changed 8 years ago by jburel

  • Milestone changed from FacilityManagers to OMERO-5.2.2
  • Resolution set to fixed
  • Status changed from new to closed

comment:8 Changed 8 years ago by cblackburn

Thanks for spotting and closing. Certainly docs - do we want this fully exposed in 5.2.2 docs? Refinements, yes too. Adding way of dealing with P/D certainly but also adding another class as an example of a user class but one that is also useful - Timestamp most likely. There probably needs to be a card or two!

comment:9 Changed 8 years ago by jamoore

Can you add cards to devx as you see fit and then we'll go through them in a review soon?

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

We're Hiring!