Skip to content

[NEW FEATURE] MANAGE INSTRUMENT --> Error management for old MM JSON files #480

Description

@strambc

This inherits from #360 and from #468, which were closed and substituted with this one.

  • Unify error management between Load from Home Folder and Import file

Create separate error cases:

  • 1. Does not validate against schema ---> "This file does not appear to be a valid Microscope.JSON file. Please select a valid file."

  • 2. No "Model Version" --> "This file does not contain a valid 'Model Version' field and cannot be opened with this version of Micro-Meta App."

  • 3. Old "Model Version" --> "This file was created using a previous version of the Microscopy Metadata model. Please contact us for possible solutions."

  • 4. "Model Version" < 2.0.0 --> "This file was created using a version of the Microscopy Metadata model that is no longer supported. You might be able to open it using v1.6.15-b1 or earlier."

  • 4. Newer "Model Version" --> "This file was created using a version of the Microscopy Metadata model, which is not yet supported by this Micro-Meta App version. Please open it using a matching version of the App."

  • 6. No "App Version" --> "This file does not contain a valid 'App Version' field and cannot be opened with this version of Micro-Meta App."

  • 7. Old "App Version" --> WARNING: "This file was created using a previous version of Micro-Meta App. Please save it using this version to avoid future issues if you want to create a Settings file."

  • 8. Newer "App Version" --> "This file was created using a more recent version of Micro-Meta App. Please update your Micro-Meta App to the latest version you can download from here: https://github.com/WU-BIMAC/MicroMetaApp-Electron/releases/latest."

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions