> From what we are seeing in the logs, it appears that for each bucket
> in the database, it checks 1) whether you have ADMIN_BIB_BUCKET at
> all 2) whether you have CREATE_BIB_BUCKET at all 3) whether you have
> ADMIN_BIB_BUCKET for that bucket and 4) whether you have
> CREATE_BIB_BUCKET for that bucket.
>
> Multiply that by the 91,739 buckets in the PINES database to see what
> a burden this is - it should only really be doing perm checks on the 2
> buckets that we have configured as carousels.
Could you describe the circumstances where it is doing the permission
checks? It is not clear to me that the referent of "it checks" is.
> From what we are seeing in the logs, it appears that for each bucket
> in the database, it checks 1) whether you have ADMIN_BIB_BUCKET at
> all 2) whether you have CREATE_BIB_BUCKET at all 3) whether you have
> ADMIN_BIB_BUCKET for that bucket and 4) whether you have
> CREATE_BIB_BUCKET for that bucket.
>
> Multiply that by the 91,739 buckets in the PINES database to see what
> a burden this is - it should only really be doing perm checks on the 2
> buckets that we have configured as carousels.
Could you describe the circumstances where it is doing the permission
checks? It is not clear to me that the referent of "it checks" is.