Ability to import/export an application context

[dsuren1]

Description

Ability to import/export an application context from the context manager UI

Acceptance criteria

• The implementation expects to improve the context manager UI
  • Add import & export button on context wizard. While import is disabled in steps > 1 with a tooltip saying To import a context, go to Step 1
  • Export button is disabled on the new context when basic info is missing
  • All the configured plugin and customized configurations of the plugins including mapConfig and other information that are saved within the context must be exported too
  • Name is not replaced when importing a context json. It is retained, if any, from the context in open

Mock

Import/export in Context wizard

Other useful information

georchestra/mapstore2-georchestra#584

[dsuren1]

@tdipisa

Clarifications required

• Ability to configure the base URL of layer on import and export [Context Manager ] Ability to import/export an application context georchestra/mapstore2-georchestra#584 (comment).
  • Should this be implemented as part of this issue. Alternatively, after discussion with @offtherailz , we believe adding this to option to layer setting, to configure a url rather than during import or export. As this will reduce complicating import/export feature (Maybe in a separate issue?)
• Import/export button placement
  • Discussion with @offtherailz , the suggested location of the import/export is placing it in the context wizard

[dsuren1]

@tdipisa Shall we close #8173 in favour of this issue?

[tdipisa]

yes

[tdipisa]

@tdipisa

Clarifications required

• Ability to configure the base URL of layer on import and export [Context Manager ] Ability to import/export an application context georchestra/mapstore2-georchestra#584 (comment).

This is not part of this issue since it is not included in the expected effort as a feature to be supported.

• Should this be implemented as part of this issue. Alternatively, after discussion with @offtherailz , we believe adding this to option to layer setting, to configure a url rather than during import or export. As this will reduce complicating import/export feature (Maybe in a separate issue?)

Both options could be valid. Maybe the one suggested by @offtherailz is better but we should evaluate the best/more convenient one to be implemented as part of a separate issue and not as part of this first delivery. Properly set sources using relative URLs, where possible, is already a valid possibility.

• Import/export button placement

  • Discussion with @offtherailz , the suggested location of the import/export is placing it in the context wizard

That's ok for me to have:

• The export one in the context item inside the contest catalog page
• The import one just beside the "new context" button on top or, maybe better, directly inside the context wizard as part of the existing toolbar at the bottom. Let's evaluate in the preliminary design phase.

[dsuren1]

Mock

Import in Context wizard

Export on context card

[offtherailz]

For conformity and usability, I should put import and export buttons both in context edit wizard. It is simple to find and use.

Having it on the card is a plus. I personally prefer to NOT have it, because:

• It is not strictly necessary. We already have this in the context editor.
• There is no way to use the export outside the context manager, so on the card is a little out of context.

The only "Pros" of having it on the card is that it makes easy to export many context in a few clicks directly in the manager.

Personally I don't think this use case is so frequent to justify the feature.

[dsuren1]

Updated

@offtherailz Kindly confirm if the placement of the buttons is okay?

Import/export in Context wizard

[offtherailz]

Correct. Please update the acceptance criteria.