From 5283ed83fd859fc779f287ed1c70b40ac2698fde Mon Sep 17 00:00:00 2001 From: Julian Ladisch Date: Wed, 28 Jan 2026 17:02:15 +0100 Subject: [PATCH] Add link to permissions naming convention to module acceptance criteria --- MODULE_ACCEPTANCE_CRITERIA.MD | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MODULE_ACCEPTANCE_CRITERIA.MD b/MODULE_ACCEPTANCE_CRITERIA.MD index b777591..8236dad 100644 --- a/MODULE_ACCEPTANCE_CRITERIA.MD +++ b/MODULE_ACCEPTANCE_CRITERIA.MD @@ -125,7 +125,7 @@ Note: Backend criteria apply to modules, shared backend libraries, and edge modu * [ ] All API endpoints are documented in OpenAPI (11) * For existing module evaluation: RMB-based modules may continue using RAML instead. * [ ] All API endpoints protected with appropriate permissions as per the following guidelines and recommendations, e.g. avoid using *.all permissions, all necessary module permissions are assigned, etc. (6) - * -_note: read more at https://dev.folio.org/guidelines/naming-conventions/ and https://wiki.folio.org/display/DD/Permission+Set+Guidelines_ + * -_note: read more at https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/156368925/Permissions+naming+convention and https://dev.folio.org/guidelines/naming-conventions/ and https://wiki.folio.org/display/DD/Permission+Set+Guidelines_ * [ ] Module provides reference data (if applicable), e.g. if there is a controlled vocabulary where the module requires at least one value (3, 16) * [ ] If provided, integration (API) tests must be written in an [officially supported technology](https://wiki.folio.org/display/TC/Officially+Supported+Technologies)[^1] (3, 4) * -_note: while it's strongly recommended that modules implement integration tests, it's not a requirement_