feat: Extensibility of import and export notes processing

[azayati]

Rationale

Currently, import and export notes processing is performed directly in notes codebase. That's why it is not possible to perform other pre import or post import operations from other modules.

1. Functional requirements

This feature must not change the current notes import and export operations.

2. Non Functional Requirements

• Expected volume & Performance requirements

  • No change.

• Security requirements (Authentication, Authorizations, Audit track / traceability, data retention…)

  • No modification with actual behavior

• Extensibility requirements (Identified extension points, pluggable implementations...)

  • Implement NoteImportProcessor interface which with pre import and post import methods, this will make possible for each module to implement its own pre import and post import connector operations.
  • Implement NoteExportProcessor interface which with pre export and post export methods, this will make possible for each module to implement its own pre export and post export connector operations.

• Configurability requirements (properties introduced, default settings, jobs, etc...)

  • No configuration

• Requirements related to existing users data

  • No change

• Requirements related to existing features (ex: Add a button to existing modules...)

  • No change.

• Feature Flag (property name, default status, target audience, functional behavior)

  • No feature flag

• Other NFR (ex: Use of VueX, Vue, Vuetify)

  • No change.

3. Impacts

• Documentation to update?

  • No documentation to update

• Training level / Change management needs

  • No change management needs

4. Software Architecture

Architectural impact has to be evaluate with a technical study

• Security

  • No security change

• Access (GUI, API…)

  • No change.

• Services & processing

  • No change.

• Data and persistence

  • No data model modification

• Support for clustering

  • No change.

• Support for multitenancy

  • No change.

• Integrations

  • No change.

• Migration strategy

  • No change.

5. Annexes

• Reasoning that explain the technical choices
• Impacts (ex: impact on public REST/Java API)
• References (links...)

[rdenarie]

@margondicco I put this mip in open status, as there is no priority on that

[plamarque]

May be useful when we will support images in notes.

[srenault-meeds]

I archive it for now as no news for it since 7 months

[azayati]

I archive it for now as no news for it since 7 months

@srenault-meeds I clicked by mistake on "restore", you can archive it again ?