To support automatic capabilities creation and keep FOLIO permission usage consistent, it is suggested that all module descriptors be reviewed and inconsistencies in permission namings and usage be fixed.

https://github.com/folio-org/folio-module-descriptor-validator can help teams with finding such problems in the module descriptor.

If the module is not a java based - https://github.com/folio-org/folio-module-descriptor-validator/blob/master/scripts/module-descriptor-batch-validator/README.md

Permission naming convention for renaming - https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/156368925/Permissions+naming+convention

How to rename a permission:

• https://folio-org.atlassian.net/wiki/spaces/TC/pages/5055284/DR-000014+-+Migration+of+Static+Permissions+Upon+Upgrade

• https://github.com/folio-org/okapi/blob/master/doc/guide.md#permissions-and-the-_tenantpermissions-interface

Rules for Module Descriptor:

• Permission name according to the convention

• One permission can be used to protect only one endpoint

• Endpoint should be protected by 0-1 permissions

• Permission with sub permissions(Permission set) can’t be used for endpoint protection

Scope:

• Add plugin to the modules pom file and run build

• Fix problems in module descriptor according to the Permission naming convention or rules

• If module is not a java based - run local scripts and fix module descriptor