correction request for the LocaliZoom content type

[Majpuc]

Dear all,

I noticed that the cc for LocaliZoom was missing the last part. I think it should be "application/vnd.localizoom.lz+json"

Could you make this correction?

Thank you!

Best, Maja

[UlrikeS91]

Thanks for raising the issue. I see that the LocaliZoom content type is also missing other properties. Would it make sense to do a proper update of the content type or do you need the corrected content type available quickly?

[Majpuc]

Yes, I agree. We could add "description": "JSON specific file for LocaliZoom containing information about the reference atlas "target" and "target-resolution" and section image registration information for each section in the series."
I am not sure about the "dataType" and "displayLabel". Maybe Gergely can supply info here.

[UlrikeS91]

Just to clarify: Does LocaliZoom create one output format with file extension ".lz" (which may or may not be based on JSON format) or is there an additional one with ".json"?

The logic "application/vnd.localizoom.lz+json" as name combined with ".lz" as file extension does not work for our instances.

It can either be:
"application/vnd.localizoom.lz" (name) + ".lz" (file extension)
or
"application/vnd.localizoom+json" (name) + ".json" (file extension)

If both exist, both will be added of course.

Comparable to e.g.,
application_vnd.quicknii.flat with ".flat" as file extension
vs.
application_vnd.quicknii+json with ".json" as file extension

[Tevemadar]

Historically both exists. As of now, LocaliZoom in the Collab creates .lz files, but from the past we have the same kind of files with .json extension, they may appear in datasets.

[Majpuc]

Hi @UlrikeS91 Could you create both please ?

[lzehl]

@Majpuc I don't think I quite understand yet. What is the difference between the .lz file and the .json file? Both are formatted in JSON. But do they contain the same or different information? (are they both produced/necessary or only one?)

[Majpuc]

The different tool specific json files are generated by those different standalone tools. Those are input files for LocaliZoom.
The .lz file is produced by the online LocaliZoom sw and serves as input and output for LocaliZoom.

[lzehl]

@Majpuc could you paste or point to an example for each?

[Majpuc]

Example 1. JSON input file for LocaliZoom service links.

hbp-00168-62_203_222_R20911_VGLUT3_lz.json
The files contains information about: dataset name, (pre-migration) storage directory, atlas used for registration,sw used for registration, atlas resolution and the for each image, the filename, number, dimensions, and registration vectors.

Example 2. .lz file used in the LocaliZoom webapp accessible through the Collaboratory
(the .lz file type is not compatible to upload, so I saved it as text here for sharing with you).
When working in the collab environment, the file contains information about the bucket name, atlas used for registration,the image file names, image file dimensions, image file format,and registration vectors.

my points_as txt.txt