Create a dedicated user role for scripts
The proposal is to create a user role SYSTEM_MODERATOR
that is used by scripts to read/write data.
Or in @mkozak words: "Maybe we need another user role? We have now CONTRIBUTOR (human), SYSTEM_CONTRIBUTOR (for ingesting scripts), MODERATOR (human), and ADMINISTRATOR (human). I am in favor of adding SYSTEM_MODERATOR (for moderation scripts)."
Scripts may use hidden properties like HTTP-status-code
or processed-at
(probably most of the properties that are collected in the group "CURATION"). For this the script needs to authenticate otherwise such properties are not visible in the API.
Also scripts may manipulate data. It could be helpful to differ alongside the user role between such manipulations by humans and by scripts.
Opinions and comments? @matej.durco @lbarbot @edward.gray @cesare.concordia @frank.fischer01 @Seung-Bin.Yim @alireza.zarei1