Description

For some customer with dedicated user base, the terminology used for sharing across multiple instances is not helpful (currently Science mesh)

User Stories

• As a customer I want to be able to customise the name of the OCM feature to adapt it to their end-user base.

Value

End users must be able to understand how to share with other users from other instances of OCIS even if they are not part of a science related institution (e.g. university).

Acceptance Criteria

• use custom translation as proposed by @kobergj
• the name of the functionality MUST be a string
• there COULD be additional validation on the string (e.g. restrict special characters to avoid display issues)
• the name length MUST be limited such that there is no display issue on the UI (identify max. length or use reasonable limit instead)

Definition of ready

• Everybody needs to understand the value written in the user story
• Acceptance criteria have to be defined
• All dependencies of the user story need to be identified
• Feature should be seen from an end user perspective
• Story has to be estimated
• Story points need to be less than 20

Definition of done

• Functional requirements
  • Functionality described in the user story works
  • Acceptance criteria are fulfilled
• Quality
  • Code review happened
  • CI is green (that includes new and existing automated tests)
  • Critical code received unit tests by the developer
• Non-functional requirements
  • No sonar cloud issues
• Configuration changes
  • The next branch of the ocis charts is compatible