Closed joshmoore closed 3 weeks ago
Thanks, @will-moore. Fixes pushed for most of the above. Another question I have is whether to move from --rocrate-
to --metadata-
everywhere.
@joshmoore I don't mind rocrate
or metadata
, but I guess if the args are --rocrate-
then maybe we should mention why "rocrate".
Actually, the README could do with a short "Metadata" section that simply says "Metadata is written as Ro-Crate to ro-crate-metadata.json
", with an example and say "See ome2024-ngff-challenge resave -h
for more info (assuming we don't want to duplicate the help in the README).
E.g.
ome2024-ngff-challenge resave in.zarr out.zarr --cc-by --rocrate-organism=NCBI:txid10090 --rocrate-modality=obo:FBbi_00000251
idr0010 plate exported with commit c122913 above:
Strangely missing license
from:
{
"@id": "./",
"@type": "Dataset",
"resultOf": {
"@id": "#9c74acf1-aa49-434a-9635-26ef724d9772"
}
},
converted with:
time ome2024-ngff-challenge resave --input-bucket=bia-integrator-data --input-endpoint=https://uk1s3.embassy.ebi.ac.uk --input-anon S-BIAD885/0046b0d0-f20b-4482-84b1-4b2b154865fd/0046b0d0-f20b-4482-84b1-4b2b154865fd.zarr /data/will/idr0010/76-45.zarr --log debug --rocrate-modality=obo:FBbi_00000246 --rocrate-organism=NCBI:txid9606 --cc-by
But I can't reproduce that - working fine with other images and plates... 👍
Proposed changes from the 20240821 morning challenge chat:
resave
subcommand to allow future commands (see below)Follow-up work will include: