Open nayib-jose-gloria opened 1 year ago
Not required for 3.1 because the dataset titles provided are all unique and validated to have targeted the intended datasets in the dev migration run. Was not scoped in original tech spec. Can be done as a follow-up as part of the 4.0 Epic.
Deprioritized for 4.0.0. Use-case for this has not come up, and it can be relatively easily handled (1 day x 1 engineer work) if the use-case does come up.
Requested by Lattice team in order to uniquely identify private datasets (by dataset title + collection title) to target for point transformations during a migration, without exposing their private IDs publicly (as we publicly commit the migration script)
Alternatively--consider and propose lightweight options for making the migration script private such that this is not a concern, and private IDs can be used to identify private datasets.
This issue should encompass making the change in the migrate command in single-cell-curation, as well as the follow-up change in single-cell-data-portal to actually pass in the collection title