ReadMe: Update include_labels note to focus on OMERO

dgault · Jun 6, 2024 · 057574b · 057574b
1 parent 89a77a4
commit 057574b
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -55,7 +55,7 @@ The OMEZarrReader has a number of reader specific options in version 0.4.0 which
 
 The new default behaviour of the `omezarr.include_labels` option introduced in v0.4.0 represents a change in behaviour from the v0.3 releases. Previously any Zarr arrays found in the labels folder would by default be represented as an additional image series. With the current default settings, Zarr arrays in the labels folder will no longer be included in the list of image series. Changing this setting to `true` will revert to the previous behaviour. 
 
-**Note:** If you had imported data with labels using version v0.3 or earlier then you will need to ensure that the `omezarr.include_labels` option is set to true. You can do this either via the API or by adding a `bfoptions` file to the fileset. In the case of OMERO this will require running psql commands to update the database to include the new `bfoptions` file.
+**Note:** If you had imported data with labels into OMERO using version v0.3 or earlier then you will need to ensure that the `omezarr.include_labels` option is set to true. You can do this by adding a `bfoptions` file to the fileset. This will require running psql commands to update the database to include the new `bfoptions` file. If you need help with this scenario then please contact us on [image.sc](https://forum.image.sc/).
 
 In version v0.5.0 a new option `omezarr.alt_store` was added. This allows for the source of an alternative file store to be configured. Setting the option means the pixel data to be read from a different source than originally used when initialising the reader. The initial implementation was intended for use with the [IDR] (https://idr.openmicroscopy.org/), allowing IDR to read data directly from an S3 location. The current implementation only allows for S3 access when using a public https endpoint with unauthenticated access using anonymous credentials. A more complete, general purpose implementation will follow in a future release.