►
From YouTube: S3E21 | Permission Reports
Description
Sometimes math sucks. And figuring out the math for a report on permissions is the worst. Christopher and George with share their approaches to creating reports that will help you keep a handle on who has what permissions. While the reports are more advanced, the outcome is quite simple and extremely helpful. And they challenge users to find better solutions to keeping up with the ever-changing permissions beast.
Contents:
0:00 - Title
0:27 - Intros
5:17 - The Idea
7:03 - The Permissions
12:43 - Previous Permission Reports
18:46 - George's Approach to a Permissions Report
28:27 - Christopher's Approach to a Permissions Report
39:25 - A Hope for a Better Report
Additional Resources:
https://wiki.koha-community.org/wiki/SQL_Reports_Patrons#Patrons.2C_Categories.2C_and_Permissions
https://wiki.koha-community.org/wiki/SQL_Reports_Patrons#Accounts_with_permissions
https://wiki.koha-community.org/wiki/SQL_Reports_Patrons#Accounts_with_permissions_.28v22.11.29
Music: https://bensound.com/
Text -to-speech: https://wideo.co/text-to-speech/
Audio Effects: https://zapsplat.com/
Visual Effects: https://flexclip.com/
A
B
A
We
will
hopefully
have
our
presentation
proposals
in
hand
and
start
to
have
some
sort
of
schedule
that
we
can
get
online,
but
we
hope
to
see
everybody
there
and
we
hope
that
we
have
plenty
of
great
presentations
to
to
listen
to
I'm
looking
forward
to
it,
and
today
we
are
going
to
be
talking
about
a
beast
of
a
report
to
look
up.
You
know
who
has
what
kinds
of
permissions
before
we
get
into
that.
Here's.
A
brief
message
about
koha
us.
C
Us
provides
excellent
information,
both
original
and
curated
from
around
the
internet,
including
the
terrific,
every
other
day,
training
videos.
You
will
also
find
several
special
interest
groups
to
connect
with,
as
well
as
our
general
monthly
meeting
Where
We
Gather,
to
talk
about
the
latest
Kohan
news.
You
should
also
check
out
the
koha
U.S
annual
conference
held
at
various
locations
around
the
U.S.
This
is
a
great
opportunity
to
meet
with
other
users
face
to
face
and
build
your
Kohan
Network,
as
well
as
new
friendships
and,
of
course,
don't
forget
about
the
great
presentations
koha.
C
Us
is
also
actively
involved
in
the
koha
community
by
contributing
towards
new
developments.
If
you
are
interested
in
contributing
towards
koha
U.S
funded
developments
join
the
koha
U.S
memberships.
Your
annual
membership
builds
the
funds
to
sponsor
new
developments
in
the
community
and,
as
a
member,
you
also
help
shape
koha
us
with
your
membership
votes
and
receive
a
discount
on
the
annual
conference.
You
can
also
contribute
towards
developments
through
a
direct
donation
or
by
purchasing
some
great
koha
us
merchandise,
through
our
threadless
accounts
visit
us
at
kohaus.org
to
find
out
more.
A
B
Right
so
first
I
wanted
to
mention
before
we
got
any
further
along
that
you
know
there
was
a
koha
system,
administration,
koha,
U.S
system
administrators
meeting
today
and
Juliet
I
forget
which
Library
she's
at
mentioned.
Oh
it's
right
on
the
tip
of
my
tongue.
Anyway,
she
mentioned
that
she
had
used
an
idea
from
one
of
our
videos.
You
came
to
the
meeting
late,
so
you
weren't
there
for
that
part.
But
you
know
we
had
talked
a
few
months
ago
about.
You
know
how
to
add.
B
The
Kohan
closed
date
calendar
the
holiday
calendar
from
Kohan
to
the
front
page.
So
you
always
know
you
know
when,
when
the
next
close
date
is
at
your
library-
and
she
had
taken
that
idea
and
instead
of
putting
the
calendar
on
on
there,
she
put
in
a
report
that
helps
them
find
materials
in
their
materials
sorter
that
have
requests
on
them.
So
that
way,
whenever
anything
goes
through
the
materials
sorter.
That
has
a
request
on
it.
B
A
B
A
All
right
well,
as
I
said
earlier,
we're
going
to
be
talking
about
a
report
where
we're
looking
at
permissions
that
are
set.
You
know
you
may
have
a
small
staff
and
you
may
have
only
a
couple
users
in
your
system
that
have
permissions,
but
if
your
Consortium
like
what
George
belongs
to
or
what
I
Belong
To
You
may
have
hundreds
of
people
that
have
permissions
and
keeping
that
in
check
is
very
important,
and
so
it's
always
good.
You
know
we
here
at
our
Consortium.
A
A
You
know
maybe
they've
become
a
regular
Patron
they're
still
in
the
system,
but
those
permissions
never
got
cleaned
up,
and
so
this
is
a
good
tool
to
use
in
order
to
find
those-
and
you
know
evaluate
you
know
if
they
had
everything
that
they
need
if
they
have
more
than
they
need,
if
they
shouldn't
be
in
there
at
all.
So
we're
gonna
show
a
couple
of
approaches
that
we've
taken
to
doing
this
difficult
task
and
I
say
it's
difficult,
because
the
way
that
this
information
is
stored
is
not
straightforward.
A
C
B
To
set
permissions
currently
they're
set
as
a
super
librarian,
and
you
know
if
you
click
on
some
of
the
on
the
show
details,
button,
there's
a
main
permission
and
then
underneath
that
there
are
individual,
granular
permissions
that
are,
you
know.
This
is
the
circulate
permission.
If
we
check
this,
then
that
person
that
person
has
all
of
the
different
circulation
permissions,
but
maybe
we
don't
want
them
to
have
all
of
those.
B
B
A
D
A
Know
the
the
number
itself
boggles
my
mind
why
they
didn't
use
a
a
code
like
they
use
everywhere
else
and
store
that
information
I'm,
not
sure,
but
you
know
because
they
were
storing
this
in
one
field.
Maybe
that's
that's
it.
It
was
just
a
simply.
They
were
storing.
You
know
what
level
of
permission
a
person
had
as
a
number
that
built
off
of
itself
exponentially
so
that
they
could
store
it
in
one
place
and
they
didn't
have
to
have
a
separate
table.
But
then,
as
granularity
was
introduced,
they
decided
Well.
A
B
B
It's
a
legacy
issue
with
koha
that
probably
goes
all
the
way
back
to
koha
version,
1.0
and
I.
Actually,
you
know
this
is
a
report
that
I
wrote
to
show.
You
know
this
is
how
part
of
the
permissions
are
actually
written
into
the
borrower's
table.
There's
a
column
in
the
borrowers
table
called
flags
and.
D
C
B
Exponential
because
if
you
have
permission
to
use
the
Patron
clubs
module
the
way
it
works
is
koha
takes
two
to
the
21st
power
which
comes
up
with
this
number,
which
is
like
2
million.
Ninety
seven
thousand
one
hundred
and
fifty
two,
and
it
puts
that
number
into
the
flags
field
in
the
borrowers
table.
B
And
so,
if
you
have
permission
for
lists
and
permission
for
clubs,
it
adds
those
two
together.
It
takes
two
to
the
20th
power
plus
2
to
the
21st
power,
and
it
adds
them
together
and
that's
the
number
that
appears
in
that
Flags
column
and
then
Kohan
knows
when
it
sees
that
unique
number.
Because,
if
you
add
any
of
these
exponents
together,
there's
no
combination.
B
There's
absolutely
no
way
to
get
an
overlapping
number,
there's,
no
way
that
you
can
have
free
permissions
that
equal
the
same
thing
as
maybe
four
different
permissions.
It's
just
mathematically
not
possible
for
these
numbers
to
add
for,
for
any
combination
of
these
numbers,
any
two
different
combinations
of
these
numbers
to
add
up
to
the
same
thing,
it's
just
not
mathematically
possible.
B
A
It's
genius
and
how
it
was
developed
so
that
they
could
use
one
field
and
one
number,
but
it's
you
know
it's
it's
maddening
in
every
other
approach,
I
mean
if
you
want
to
do
a
report
on
it
you,
your
report
is
not
going
to
be
simple
and
yeah.
That
is,
that
is,
has
complicated
report
writing
on
this
tremendously.
B
Yeah
I've
actually
got
that
pulled
up.
You
know.
We've
got
reports
written
about
staff
level
permissions
going
back
to
you
know.
This
is
one
by
Ian
at
Bywater
solutions
that
is
probably
koha
two
point
something
or
maybe
early
three
point
something:
I
got
a
one
here
by
Nicole
and
joy
and
Elliott
at
Bywater,
Solutions
and
one
by
Tomas
and
yeah.
B
B
B
A
B
B
A
B
B
Wouldn't
be
the
worst
thing
in
the
world
yeah
and
one
of
the
things
so
I
started
my
work
at
Northeast,
Kansas
library
system,
with
this
version
of
this
report,
I
think
and
then
I
went
through
and
I
built
on
it
to
get
what
I
used
for
a
long
time,
and
it
had
that
problem
that
we've
talked
about
before.
What
we
were
talking
about.
B
The
circulation
rules
is
that
the
big
problem
I
had
with
this
report
is
that
each
permission
is
its
own
column
and
so
for
up
to
26
27
different
permissions,
different
top
level
permissions.
Now
that
gets
you
a
table,
that's
a
you
know.
I've
got
three
screens
on
my
desktop
and
that's
the
kind
of
thing
that
you
put
it
on
all
three
screens
and
then
maybe
you
still
have
to
scroll
a
little
bit
with
27,
maybe
28
columns,
that's
a
big
big
wide
table
and
it's
really
hard
to
look
at.
It's
really
hard
to.
A
B
A
B
D
B
And
that's
the
way
I
keep
going.
Is
you
know,
I
wanted
to
get
away
from
from
those
multiple
columns
and
we're
in
the
middle,
we're
still
in
it's
an
ongoing
process
here,
where
we're
moving
from
libraries
having
like
a
director
account
and
a
Circ
account
and
a
tech
account
to
each
person
having
an
individual
who
has
to
log
into
koha
having
an
individualized,
login
and.
C
B
What
I
needed
was
a
report
that
I
could,
where
I
could.
You
know
maybe
look
at
two
different
patrons
at
a
library
to
compare
their
permissions
and
having
that
big
spreadsheet
was
kind
of
getting
to
be
a
problem
for
me,
and
so
that's
when
I
wrote
this
thing,
which
is
on
the
wiki
and
it
needs
to
be
updated.
This
was
for
version
2111
and
we're
about
to
upgrade
here
to
22.
C
B
B
A
B
It's
false,
then
it
goes
through
this
set
of
then
it's
gonna.
Then
it's
gonna
do
all
of
this.
If
it's
false
and
this
report
is
kind
of
a
long
report,
it
goes
on
forever
and
ever
and
ever,
but
it's
basically
doing
one
thing:
it's
just
doing
it.
It's
just
kind
of
looping
through
all
the
different
permissions,
so
I'll
break
it
down
here.
But
but
let
me
go
back
to
that
report
first,
so
this
one
is
a
super
librarian.
B
B
B
B
B
B
B
B
And
if
it's
not
true,
then
it's
going
to
go
on
to
this
separate
thing
and
it's
going
to
go
over
to
the
user
permissions
table
and
it's
going
to
look
for
module
bit
number
one,
which
is
the
circulation
module
bit.
And
then
it's
going
to
drag
out
all
of
the
circulation
sub
permissions
that
go
with
that
possible
with
the
circulation
permissions.
B
This
person
only
has
the
sub
these
three
sub
permissions
from
edit
catalog.
So
in
cases
where
and
here's
here's
a
better
one
that
says,
circulate
circulate,
they
have
remaining
permissions,
so
they
don't
have
the
all
parameters
for
circulate.
They
only
have
the
circulate
remaining
permissions,
sub
parameter,
and
so
that's
what
this
complicated.
B
So
it's
saying
if
they
have
the
all
parameters
flag,
it's
going
to
say,
circulation
all
parameters
if
they
have
just
sub-permissions
it's
just
going
to
plug
in
the
sub
permissions
and
if
they
don't
have
any
sub-permissions
or
if
they
don't
have
that
parameter.
And
there
are
no
sub
permissions.
It's
just
going
to
leave
a
blank
space,
and
so
that
got
me
from
a
28
wide
table
down
to
having
all
of
this.
In
one
column,
which.
C
A
I
needed
to
update
the
the
report
for
for
our
website
as
or
our
cohab,
for
our
libraries
as
well.
I
knew
that
more
permissions
were
in
the
mix
since
I
last
worked
on
this,
and
so
it
gave
me
an
opportunity
to
to
re-familiarize
myself
with
with
the
code
because
I
don't
like
touching
this
stuff,
it's
hard
to
even
talk.
B
A
D
A
My
RO,
my
report,
you
know
it
was
the
multiple
columns
and
I
was
looking
at
a
way
to
condense
it
and
then
you
and
I
talked
about
it
and
it
turned
into
a
possibility
of
this
video.
But
when
you
showed
me
that
it's
like
okay,
that
that
convinced
me
I
can
do
this
and
I
did
condense
some
things
so
I
have
a
lot
of
the
same
information
type
of
information
but
I
formatted
it
differently.
Yeah,
so,
and
I
stripped,
yeah
I
I
have
in
the
official
report.
A
I'll
have
the
the
last
name
and
card
number
included
with
this
as
well,
but
because
there
is
some
people
that
are
active
on
the
system,
I
just
wanted
to
whittle
it
down
to
something
a
little
less
sensitive
so
but
the
permissions
I
kind
of
went
the
same
route
but
I
formatted
things
yeah.
Just
you
know:
I
I
wanted
the
the
category
to
be
on
its
own
line
and
to
say
whether
on
the
next
line
say
whether
it
was
all
permissions
or
what
sub
permissions
were
listed
under
there.
D
A
Had
chose
to
highlight
specific
ones
that
I
the
specific
permissions
I
thought
were
kind
of
critical
to
know
about
you
know
if
they're
super
librarian
or
if
they
can
log
into
the
staff
interface,
if
they
could
change
permissions
or
if
they
could
change
parameters.
Those
are
critical
to
me.
So
I
I
made
sure
that
those
particular
elements
stood
out
in
red
and
I.
I
had
a
little
explanation.
Next,
to
that
permission,
category
right
case
to
make
that
clear,
I.
A
A
I
have
separated
the
way
it
formats
in
a
in
a
select
and
I
have
a
select
within
the
from
that
does
all
the
the
logic
and
instead
of
using
the
mods
I.
What
I'm
doing
here
is
in
ice
it
it
starts
from
the
top
down.
Yours
goes
kind
of
the
opposite
direction
in
in
checking
right,
I
check
a
different
way,
so,
basically,
it's
starting
from
the
the
the
furthest
possible
permission
and
I
do
have
one
I
think
I
have
to
add
here
for
the
22
2211,
but.
B
A
The
CRM,
that's
it
so
I'll,
probably
update
that
before
I
I
put
it
on
the
SQL
library,
but
I
would
just
slip
that
in
before
this,
so
I
I
have
a
little
reconfiguring
to
do,
but
basically
I'm
just
going
by
the
raw
number
and
I'm
I'm
checking.
If
I'm
throwing
the
flag
into
this
I
I
call
it
a
variable.
You
know
it's
a
way.
I've
learned
to
do.
D
A
A
So
I
call
that
true,
otherwise
I
leave
that
that
that
variable,
blank
and
I
put
that
in
a
a
column,
called
recalls
main
so
basically
checking
the
the
main
flag
for
that
category
and
then
I'm
doing
a
separate
column.
That's
checking
the
subcategories
and
it's
checking
that
up
code
from
the
user's
permissions
user
permissions
and
checking
to
see
if
the
bit
is
set
for
that
and
Gathering
all
the
the
categories
or
the
excuse
me
the
codes
that
are
set
for
that
and
it's
sticking
it
in
that
column.
A
So
I'll
do
that
and
then
it's
doing
another
check
it's
it's.
If
the
check,
if
the
check
is
greater
than
or
equal
to
zero,
it's
setting
the
check
to
equal
whatever.
That
number
is
minus
that
number.
So
it's
basically
trying
to
find
out
what
the
remainder
is
right.
You
know
I
I,
you
know,
I
get
I
am
not
a
bad
person,
there's
probably
a
more
elegant
way
to
do
it.
A
The
mod
seems
to
be
a
more
elegant
way,
but
it's
very
difficult
for
me
to
wrap
my
head
around,
so
this
made
a
little
bit
more
sense,
so
I'm
and
it's
taking
a
little
bit
more
coding.
But
it's
a
little
bit
more
straightforward
to
me
as
to
what
the
logic
is
and
then
it's
reassigning
that
that
value
it's
it's
reassigning
the
check
for
the
next
set
of
lines.
So
basically
it's
just
going
through.
You
know
the
remainder.
A
If
the
circulate
mean
is
not
black
or
excuse
me
blank,
then
then
it's
going
to
save
circulation
and
it's
going
to
go
to
the
next
line,
and
it's
going
to
do
that
Dash
all.
So
that's
saying
that
everything
is
selected
for
that.
Otherwise,
if
the
circular
circulate
Subs
is
not
null
and
I
had
to
check
that
differently.
It's
it's
interesting.
This
one
I
check
against
a
blank.
This
one
I
check
against
whether.
B
A
Yeah
so
so
I
checked
that
and
then
in
here,
I'm
I'm
doing
a
con
I
can
cats
doing
the
main
label
again
and
this
time
on
the
next
line.
It's
I'm
doing
a
replace
in
here,
because
all
of
your
codes
that
might
be
in
for
that
particular
bit
or
or
a
number
it
is
or
the
flag
I
should
say,
they're
separated
by
commas.
A
So
you
could
have
if
you
have
five
different
subcategories
under
that
in
that
grouping
they're
all
in
there,
in
that
one
field
separated
by
commas
and
so
I'm,
replacing
the
comma
with
a
line
break
and
then
adding
a
hyphen
in
front
of
it.
And
so
that's
what
gives
it
that
nice
format
and
adding
that
I've
been
under
the
category
and
then
listing
each
of
those
subcategories?
A
B
A
B
B
It
pretty
cool
the
one
thing
I'm
thinking
about
doing
as
like
the
next
phase
of
working
on
this
is
you
know,
since
it
is
possible
to
tell
you
know
what
the
flags
are
and
the
borrowers
column
I'm
thinking
of
ways
to
do
that
whole?
If
then,
proposition
programmatically
instead
of
having
to
instead
of
having
to
put
the
actual,
you
know
number
that
exponent
in
there.
B
If
there
was
a
way
to
go
in
there
and
easily,
you
know
plug
that
in
programmatically,
so
that
so
that
way
you
wouldn't
have
to
keep
adding
on
to
the
report.
You
know
each
time
koha
changes
and
adds
a
new
set
of
permissions.
It
would
just
be
able
to
to
dynamically
get
that
data
from
the
from
the
about
what
table
is
that.
A
Us
know
because
yeah
that
that's
like
a
it's
one
of
the
Holy
Grails
of
the
reports
for
us
right
now,
it's
like
you
know
this
one
we
have
to
maintain
and
every
time
a
new
permission
comes
out.
We
have
to
go
in
and
tweak
the
report,
so
it
includes
it.
Otherwise,
you
know
in
in
my
case
on
my
report.
I,
don't
know
about
yours
on
my
report.
A
If
I
get
a
new
number,
that's
higher
than
everything
else,
it
gives
me
wonky
results
so
so
yeah,
it's
it
can
throw
things
off
with
those
new
permissions
on
my
report,
I,
you
know
I.
It
might
be
different
with
yours,
because
you're
approaching
it
from
the
bottom
and
going
up
where
I'm
going
from
the
top
down
so
right,
yeah,
you
know
different
approaches
to
to
tackling
this
I
I
am
I,
am
not
an
expert
report
writer
by
any
means
and
I.
A
You
know,
I
did
the
my
best
to
to
wrap
my
head
around
the
the
logic
of
permissions.
It
would
be
nice
down
the
road
Developers
if,
if
that,
if
that
flag
feels
were
done
away
with
down
the
road,
I
would
love
to
see
that
information.
You
know
going
away
from
this.
The
single
number
that
we
have
to
decipher
and
have
that
moved
over
to
the
table.
Maybe-
and
you
know
I
I-
don't
understand-
you
know
I
am
sure
that
there's
probably
some
logic
behind
it.
A
Maybe
it
has
to
do
because
of
the
combination
of
that
table
and
this
flag
number,
but
I,
don't
understand
why
why
those
subcategories
are
defined
by
a
number
rather
than
the
the
category
code?
You
know
what
to
me
just
for
Simplicity
for
people
for
those
of
us
that
have
to
write
reports
down
the
road.
You
know
I
I
get
it.
Maybe
it
was.
It's
made
sense
for
you
as
a
programmer,
but
for
us
that
have
to
work
with
the
end
results
of
that
it's
a
little
challenging.
A
It
would
have
made
sense
more
sense
to
me
if
that
number
was
the
actual
category
code,
and
then
you
know
you
have
all
of
those
subcategories
listed
in
there.
That's
great
and
then
maybe
this
flag
is
migrated
over
to
that
table
with
you
know.
If
there
is
no
subcategory
listed
there,
then
it's
assumed
that
that
whole
category
is
selected.
A
D
A
B
A
Let's
put
the
challenge
out
to
the
rest
of
the
community:
if
you
can
simplify
this
report
and
where
it's
Dynamic
and
keeps
up
with
the
ongoing
changes,
that
would
be
fantastic
yeah
that
would
be
pretty
cool,
so
throw
us
your
ideas,
put
it
out
there
in
the
library
or
messages
and
give
us
a
comment
or
email
us
at
koha
us.
Let
us
know
if
you've
got
a
a
better
take
on
this
or
a
better
approach,
or
you
know
some
way
to
to
understand
this
and
make
this
a
much
simpler
report.
I
would
love
it.
B
A
A
There's
no
dash
and
you'll
find
all
our
videos
plus
videos
from
all
of
our
meetings,
and
you
can
also
like
And
subscribe
to
our
particular
content.
If
you
want-
or
you
can
leave
comments,
we'd
love
to
hear
comments,
so
please
make
sure
that
you
check
us
out
on
both
locations
and
until
next
time
see
you
later.