As a person accessing the database, I find it difficult to query (against) the schema's applications which are available to reviewers to review.
As this logic is not entirely straight-forward, and it is otherwise "baked" into appy, it might be added to a database view/function, which appy provisions (via database migration).
(Obviously it should be somehow ensured or suggested to those looking at and handling appy's code that changes to this logic should be propagated to this function, through further database migration.)
It is likely that this must be a database function, which accepts the single argument of the current program year (though this could alternatively default to the year of the current date).
As a person accessing the database, I find it difficult to query (against) the schema's applications which are available to reviewers to review.
As this logic is not entirely straight-forward, and it is otherwise "baked" into appy, it might be added to a database view/function, which appy provisions (via database migration).
(Obviously it should be somehow ensured or suggested to those looking at and handling appy's code that changes to this logic should be propagated to this function, through further database migration.)
It is likely that this must be a database function, which accepts the single argument of the current program year (though this could alternatively default to the year of the current date).