Add batchset for rendering a folder of datasets

[manics]

This is useful if all images in a dataset have the same renderdefs, but there are a lot of datasets:

1. Create a top-level directory
2. Under that directory create one directory per dataset with a name matching that of the dataset
3. In each of those directories create renderdef.yml with the rendering settings
4. Run `omero render batchset Project: path/to/top-level/directory

Example: IDR/idr0071-feldman-crisprko@5d41cd7 (private)

[joshmoore]

Generally nice idea! Did you also consider having all the renderdefs block in a single YAML which would allow using references & anchors?

[manics]

If there are no objections to defining version: 3 of the format I can try it.

[sbesson]

Cross-linking to #36 and https://github.com/IDR/idr0067-king-yeastmeiosis/tree/master/experimentA where a similar logic was required at the image level rather the dataset one. See also https://github.com/IDR/idr0040-aymoz-singlecell/tree/master/experimentA/rendering_settings for IDR precedents. As we have all implemented our own wrapping logic to handle this scenario, I am totally in favor of working towards a more generic way at the level of this repository.

A few comments:

• the name renderdef.yml feels a bit arbitrary but is descriptive enough. If we wanted flexibility, the filename could easily become an option of the batchset command. For comparison, idr0067 used <dataset name>.yml which reduced this requirement
• thinking of the generalization of this extension step, I assume the logic could be further extended to images using <dataset name>/<image name>/renderdef.yml or <plate name>/renderdef.yml for HCS in a second step?

[manics]

#52 is a better solution since it avoids needing to escape filenames