►
From YouTube: System Administration Special Interest Group - 2/14/2022
Description
00:09:36 Emily Lamancusa she/her MCPL: Hi! I'm Emily Lamancusa, with Montgomery County Public Library. We migrated to Koha in October 2021, but I've only been here since October 2022. I'm teleworking while sick so keeping voice/camera off for today
00:12:58 Emily Lamancusa she/her MCPL: I've noticed that too - at least in terms of line breaks. I've noticed that the preview in the Koha account for all notices has about twice as many line breaks as what goes out through email
00:13:20 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30287
00:28:20 Andrew Fuerste-Henry: Bug 30250 - Configure when to apply framework defaults when cataloguing
00:28:33 Andrew Fuerste-Henry: Bug 29146 - Default values from the framework should only be applied at biblio/item creation
00:29:38 Emily Lamancusa she/her MCPL: Lucas is RM, I believe
00:31:29 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11071
00:37:35 Andrew Fuerste-Henry: Bug 31995 - build_holds_queue.pl should check to see if the RealTime syspref is on
00:39:43 Andrew Fuerste-Henry: Bug 32565 - Holds placed when all libraries are closed do not get added to holds queue if HoldsQueueSkipClosed and RealTimeHoldsQueue are enabled
00:47:21 Rebecca Coert (APL-VA): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31557
00:48:59 Emily Lamancusa she/her MCPL: Yes, the RT holds queue checks all the holds on the bib whenever it's touched
00:54:11 Andrew Fuerste-Henry: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25426
00:54:48 Rebecca Coert (APL-VA): Reacted to "https://bugs.koha-co..." with 🥳
00:59:22 Rebecca Coert (APL-VA): timestampdiff(year,dateofbirth,curdate())FLOOR(DATEDIFF (NOW(), dateofbirth)/365)
01:02:27 Jason (SEKLS): MarcFieldForCreatorId MarcFieldForCreatorName MarcFieldForModifierId MarcFieldForModifierName
01:02:46 Andrew Fuerste-Henry: helpful stuff: https://wiki.koha-community.org/wiki/SQL_Reports_Library#action_logs
01:09:22 Andrew Fuerste-Henry: SELECT a.timestamp, b.title, b.subtitle, p.surname, p.firstnameFROM action_logs a LEFT JOIN biblio b ON (a.object=b.biblionumber) LEFT JOIN borrowers p ON (a.user=p.borrowernumber)WHERE module like 'catal%' and action='add' and info like 'biblio%' and date(a.timestamp) BETWEEN date_add(last_day(date_sub(curdate(), interval 2 month)),interval 1 day) AND last_day(date_sub(curdate(),interval 1 month))
01:11:17 Emily Lamancusa she/her MCPL: Sharing my TemplateToolkit from earlier too: https://paste.koha-community.org/1357
01:11:48 Daphne Hoolahan: Thanks Andew
A
B
C
E
I'll
go
I'm
Sally
lodico
with
the
Knox
County
Public
Library,
and
we
migrated
from
Symphony
to
koha
in
November
of
2022.
So
we're
pretty
new
to
all
this
stuff.
But
learning
our
way
around
just
want
to
try
to
listen
in
and
see
what
everybody's
talking
about
and
start
learning
more
I'm,
the
assistant
director
for
it
for
the
library
system.
F
A
I
I
am
definitely
and
I
work
with
interleaf
who
support
koha
in
Ireland,
and
we've
been
supporting
koha
I
think
for
about
10
years
now.
Well,
now,
you're
probably
telling
me
it's
been
longer,
but
it's
been
such
a
good
time.
It's
flown
past
and
I
come
to
these
meetings,
hoping
to
find
that
you've
all
found
the
problems
before
I
upgrade
our
clients
and
then
I
can
avoid
them.
A
J
A
F
A
C
C
K
C
B
There
was
a
bug
with
digest
a
while
ago,
but
I
thought
it
got
fixed.
Does
that
sound
familiar
Andrew,
not
terribly?
We
had
an
issue.
I
know,
template
toolkit
looks
so
much
different
than
the
other
standard
notices
that
it
will.
It's
like
harder
to
pick
stuff
out,
but
if
you're
getting
a
completely
different
message,
I'm
guessing
something's
not
set
up
right.
C
C
A
C
C
Is
my
my
template
toolkit
code
I
was
reading
I
think
this
elsif
can
just
be
an
else,
but
for
the
most
part
the
problem
is.
Is
that
when
there's
several
problems
but
the
when
this
is
displayed
on
the
user's
account
it's
going
to
show
like
huge
gaps
where
the
brakes
are,
but
when
it's
an
email
the
brakes
are,
you
know,
are
typical
of
HTML
breaks.
C
C
G
I've
been
struggling
with
this
notice
too,
but,
like
different
reasons,
I've
had
Lucas
looking
at
it
forever
ever
we've
had
hundreds
of
different
things.
My
problem
is
like
it'll,
it's
triggering
the
notice
at
odd
times,
like
it'll.
Tell
you
that
you
can't
renew
anything
the
day
after
it's
successfully
renewed
something
so
there's
lots
of
issues
with
this
specific
notice
in.
C
L
C
C
L
L
L
L
You
know
all
of
the
different
air
statuses,
because
I
wanted
all
of
them,
but
if
you're
only
wanting
those
two
error-
statuses,
yours
is
not
going
to
look
as
ugly,
but
it's
just
that
way
like
if
it's
looping
through
them
and
the
first
one
happened
in
the
loop
happens
to
be
not
renewed
and
the
second
one
happens
to
be
renewed.
It's
just
going
to
print
them
in
order,
so
I
just
put
them
into
separate
loops
with
you
know.
The
error
message
and
I
also
put
the
due
date,
and
all
of
that
so.
L
C
C
L
C
A
Right,
I
think
that,
for
each
is
the
part
that
is
really
missing
from
your
notice,
though
Daniel
that
makes
sense
that
so
your
Patron
that
ended
up
with
all
of
their
things
that
checked
out
listed
in
the
section
that
was
supposed
to
be
for
an
error
like
a
sequel
wise.
It
would
make
sense
if
one
of
those
titles
had
an
error
at
that
logical
test.
It
said
yes,
that
error
is
present
in
this
pile
of
checkouts
until
they
all
go
here.
Yeah.
C
A
D
Historically,
it
stood
for
summer
Institute
of
linguistics
because
they
would
teach
linguists
translation
skills
in
the
summer
and
then
the
rest
of
the
year.
They
would
go
on
the
field
and
research
that
model
has
kind
of
gone
away,
but
we've
kept
the
name,
because
you
know
everyone
knows
it
in
the
linguist
field.
Anyway,
our
translation
field,
so
I
have
come
across
a
problem.
D
In
the
we
have
a
QA
site
and
a
live
site.
The
QA
our
QA,
is
on
2205.
in
the
hopes
that
our
lives
can
go
on.
2205.
I
am
unsupported,
so
I
kind
of
have
to
come
up
with
all
solutions.
Myself
I
do
have
an
I.T.
We
do
have
two
guys
who
do
I.T
but
I'm,
hoping
that
I
don't
know
the
answer
to
my
problem,
so
I
discovered
recently
that
the
way
we
have
been
using
Frameworks
in
koha
might
not
be
the
way
the
rest
of
the
world
is
using
Frameworks.
D
We
have
been
putting
a
default
value
in
some
of
the
fields
because
we
want
it
to
populate
that
value
whenever
the
framework
is
selected,
either
in
a
new
record
or
in
an
existing
record.
It's
mostly
that
33678,
an
item,
type
information
that
train
catalogers
are
like
yeah
I,
know
all
that,
but
all
of
my
unexperienced
catalogers
are
like
you
want
me
to
what
and
it
would
take
them
hours
to
look
all
that
information
up
and
I'm
like
okay,
I
want
to
save
you
time
it
takes
you.
D
You
know
two
seconds
to
change
the
framework
and
it
auto
populate
versus
looking
all
that
information
up
before
2205.
It
worked
that
way.
If
I
put
the
default
value
in
it,
auto
populated
with
that
information
in
both
new
and
old
in
the
2205,
it
will
not
Auto
populate
that
information
on
existing
records.
It
only
works
in
new
records.
I
did
look
up
some
bugs
and
it
looks
like
in
the
it
looks
like
they
wrote
in
the
code
to
get
rid
of
it,
but
there's
a
system
preference
in
the
20.
D
Well,
the
20,
the
2211
that
you
can
select
on
or
off,
which
makes
sense.
Some
libraries
don't
want
those
default
default
values
to
be
Auto
populated,
and
then
a
group
like
me
does
want
those
does
anyone
else
on
the
2205
like?
Have
you
found
a
workaround?
Do
you
use
kohai
in
that
manner
am
I
all
alone
and
I'm.
Just
gonna
have
to
wait
until
we
upgrade
to
the
2211,
which
is
going
to
be
a
while,
because
I
have
to
learn
how
to
the
interface
is
different.
I'm,
22,
11.
D
I
Yeah
I
think
the
bug
was
that
in
the
past
some
libraries
saw
it
as
a
problem
that
if
you
were
just
updating
an
existing
record,
previous
data
could
have
been
affected.
So
that's
why
they
reported
as
a
bug
and
it's
now
been
fixed,
but
you
don't
like
the
way
it's
been
fixed
and
I.
Think
then,
because
people
made
complaints,
they
introduced
the
the
system,
preference
and
but
the
only
thing
I
could
suggest
for
exist,
so
it
is
working
for
new
records.
You
did
say
that
didn't
you
yes,
so
for
existing
records.
D
Because
that's
quick,
easy
it's
my
my
I
mean
I
have
people
who
are
over
their
HR
department
who
are
having
to
catalog
records,
because
there's
really
I
mean
there's
just
a
small
staff.
It's
a
small
Library
but
I'm
wanting
these
records
to
kind
of
work
with
the
filters
and
all
this
fun
stuff
and
I'm.
Wanting
that
to
be
in
the
record.
D
K
A
Theoretically,
could
get
back
part
to
2205.,
I
guess
I
would
start
there.
I
can't
remember
who
the
release
maintainer
for
2205
is
right.
Now
you
could
ask
on
you
could
make
a
post
on
the
bug
asking
if
this
could
be
back
part
of
the
2205.?
It's
you
know
it's
filed
as
an
enhancement
in
bugzilla,
which
usually
means
it
doesn't
get
back
ported,
but
it
is
like
I
think.
You've
got
a
decent
case
that
this
really
is
not
an
enhancement
for
you.
A
K
A
D
Yeah
well,
and
it
could
be
that
all
right,
you're
just
gonna
I'll,
have
to
do
it
all
I
have
to
just
majorly
watch
those
new
records
that
are
coming
in
or
editing
and
I
have
to
manually
that,
instead
of
letting
them
do
it
or
I,
just
wait
long
enough
and
I
just
export
them
all
and
put
it
all
in
work
at
it.
If,
but
it
it
it
it,
it
breaks
my
workflow,
that's
that's
the
deal.
D
G
G
D
As
I've
looked,
it
looks
like
there
are
a
lot
of
bugs
that
are
related
to
this
and
I'm
like
okay,
it's
cool
I
mean
I
just
have
to
take
the
time
to
like
look
them
all
up
list
them
all
and
say.
Okay,
here
is
how,
in
this
one
just
make
this
and
you
fix
all
of
these
bugs
and
then
I
think
I
have
a
chance
of
it
like
actually
making
it
through,
but
it's
collecting
all
these
little
bitty
bugs
that
are
written.
D
A
E
A
F
A
B
We
were
trying
to
use
the
real-time
sold
queue,
which
is
a
new
feature,
but
it
seemed
as
what
we
had
typical
what
we
had
done
before
is
we
set
things
up
so
every
couple
hours
it
would
reset
the
whole
skew
it.
Things
would
be
randomized,
but
we
turned
on
the
real-time
whole
queue.
It
stopped
that
from
happening,
which
was
kind
of
an
unanticipated
result.
Everything
just
would
stick
in
the
whole,
the
initial
cue
it
got
into
so
I,
don't
know,
I,
think
I
think
it
was
Montgomery
that
put
that
in
there.
B
Want
to
shake
it
up
because
there's
just
right:
we
have
a
lot
of
libraries
and
so
every
once
in
a
while,
there's
like
some
Randomness
that
a
lot
one
Library
just
gets
a
ton
of
requests
and
it's
nice
to
be
able
to
say
hey.
If
you
see
that
just
come
back
in
two
hours
and
it
won't
look
so
scary,
you
won't
have
hours
of
pulling
items
off
the
whole
shelf.
It's
just
kind
of
a
random
thing.
We
also
have
because
Colorado
is
a
big
state
with
mountain
ranges.
B
Our
courier
service
is
not
equal,
it's
not
so
there's
not.
Everybody
fills
holds
at
the
same
rate
because
you
could
fill
them,
but
then
they're
just
sitting
in
a
box
for
a
full
week.
So
having
that
stuff
move
through
helps
us
run
things
more
efficiently,
so
it
was
kind
of
a
key
to
it
is
kind
of
a
key
to
how
we
operate.
So
we
were
hoping
the
real
times.
Whole
queue
would
give
us
some
additional
features
while
maintaining
our
ability
to
keep
things
random,
but
it
appears
it
did
not
do
that.
E
L
L
If
you
had
the
real-time
folds
Q
enabled,
but
like
there's
your
use
case
and
there's
the
use
case
of,
if
you
have
the
syspref
to
sit,
skip,
close
libraries
then,
like
any
holds
that
are
placed
when
all
of
the
libraries
are
closed,
just
get
missed
entirely,
which
is
also
a
use
case
to
in
favor
of
being
able
to
use
a
hybrid
of
both
one
thing.
I
also
want
to
share.
Is
we
actually
haven't
even
been
able
to
use
the
real-time
folds
queue?
L
Yet
because,
without
some
other
bugs
that
are
in
the
system
for
multitasking,
our
system
can't
even
keep
up
with
the
real-time
holds
Q
as
it
is,
but
we
did
some
pretty
extensive
testing
of
it
on
our
test
server
and
what
we
were
finding
in.
There
was
those
like
weird
spikes,
where
one
Library
will
end
up
with
a
huge
list
of
holds
weren't
happening,
at
least
in
our
test
data.
L
When
we
had
the
real-time
holds
key
turned
on,
like
I
made
a
nice,
you
know,
charts
in
Excel
and
everything
and
the
proportions
of
where
the
holds
were
getting
assigned
exactly
match
the
proportions
of
our
library
size,
as
opposed
to
with
the
crown
on
that
same
exact
test
data.
We
still
got
the
spikes,
so
you
know
just
sharing
that
that
we
noticed,
obviously
I
haven't
been
able
to
test
it
for
any
extended
period
of
time
with
our
real
data.
L
E
We
were
doing
the
real
time
hold
cue
and
we
were
not
selecting
libraries
that
were
closed
and
we
hit
that
bug
where
holds
placed
on
Christmas
never
got
filled,
so
we
ended
up
switching
to
turn
off
Library,
don't
fill
libraries
that
are
closed,
but
they
left
the
crime
and
the
Cron
job
was
what
was
she
set
up
to
kick
that
bug
in
the
pants
and
get
things
on
the
list,
but
we
turned
off
the
holds
on
closed
days.
It
works
better
for
us
anyway.
E
Just
ignore
it
if
it
doesn't
get
filled
with
based
on
how
our
hours
are,
but
we're
seeing
that
Spike
and
only
one
of
our
small
branch
is
really
complaining
about
it.
Every
time
that
Spike
happens
to
them,
they
call
and
let
us
know
the
others
just
seem
to
be
putting
up
with
it.
What
we
were
suggested
that
we
could
you
know,
make
an
order
and
put
your
large
ones
first
in
the
small
ones,
but
then
the
large
ones
would
always
you
know
it
didn't.
E
It
didn't
make
a
lot
of
sense
that
if
there
was
some
kind
of
priority
say
if
it's
here
choose
one
of
these,
if
it's
not
here
then
go
to
this
tier
two
level
or
something
that
we
could
kind
of
group
them
in
some
ways.
If
we
could
have
a
little
bit
more
control,
then
it's
either
completely
random
or
do
it
in
this
order,
and
it
just
doesn't
seem
to
be
a
lot
of
in
between
that.
We
could
protect
those
little
guys
who
every
now
and
then
get
that
big
spike.
E
B
B
B
K
G
So
if
we
can
fill
a
hole,
we'll
fill
it
first,
unless
the
library
owns
the
item.
But
then
we've
got
like
our
larger
libraries
on
a
second
tier
and
then
our
our
smaller
libraries
and
I've
factored
in
calculations
like
what
route
they're
on
on
The
Courier.
How
many
days
they're
open
that
sort
of
thing?
G
G
E
So
it's
sort
of
yeah
that
it
sort
of
seems
in
our
looking
at
what
is
going
on
that
the
randomness
isn't
randomly
selecting
okay,
I
have
a
this
item.
Right
here
needs
to
has
a
request,
so
I'm
just
going
to
randomly
choose
one
of
these
libraries.
It
seems
like
every
day
it
randomly
chooses
a
library
to
be
the
first
one
to
ask,
and
for
that
day,
they're
the
ones
at
the
top
of
the
list,
and
they
get
all
of
the
requests
that
they
can
fill
before
it
moves
on
to
the
next
and
the
rest.
E
E
G
Us
it
does
seem
to
really
it
does
balance
between
those
libraries
and
we,
a
long
time
ago,
went
to
to
running
the
crop
every
50
or
crunch
up
every
15
minutes.
It
was
like
from
two
hours
to
15.,
so
it
does
bounce
the
things
a
lot
more
frequently,
but
it
doesn't
seem
to
build
up
on
any
one
Q
for
us.
So
I,
don't
I,
don't
know.
F
F
We
in
our
Crown
job
once
and
once
an
hour
we
do
not
have
real-time,
holds
we're,
not
we're
a
couple
versions
behind
everyone
in
KOA,
but
we
were
noticing
that
it
should
page
at
a
certain
Branch
or
requested
a
certain
branch,
and
it's
not
it's
going
to
the
branch
that
had
the
most
recent
scene
date
of
the
item.
So
that's.
E
E
A
huge
I
mean
it's
it's
a
tough
of
a
difference.
It's
not
like
30
one
day
where
they
think.
Well,
it's
the
day
after
holiday.
It's
a
significant
and
there's
it's
not.
They
don't
own
them
and
they're
kind
of
on
the
edge
of
the
county.
So
they're
not
they're,
not
one
of
the
busier
locations.
So
it's
not
like
they
get
more
returns
and
would
have
more
recently
returned
copies,
but
I'll
certainly
look
into
that.
F
E
A
I
put
two
bugs
in
the
chat
taking
them
from
the
bottom
up
bug
three:
two
five,
six
five
is
the
bug
that
Sally
mentioned
about,
holds
that
don't
end
up
in
the
queue
if
you're
using
the
real
times,
Q
real-time
queue
and
skipping
closed
libraries,
basically,
if,
if
you're
only
using
the
real
times
queue
and
the
library
that
has
that
item
is
closed
at
the
moment,
the
whole
display
is
koha,
says
well,
I
can't
fill
this
hold,
it
doesn't
go
in
the
queue
and
then
it
lasts
forever.
It's
very
sad.
A
The
the
other
bug
there,
though,
bug
three
one:
nine
nine
five
build
holds
Q
should
check
if
real-time
sysprec
is
on
that's
the
one
that
Emily
mentioned
that
got
added
it
made
it
so
that
koha
win
the
build
holds
Q
jobs
starts.
It
checks
that
system
preference
and
the
system
preferences
on
it
kills
the
job
but
Bob.
You
should
be
able
to
run
that
Cron
job
with
a
force
option
to
say
I
know
this
is
papazon,
do
the
job
anyway.
So
what
you
were
looking
for
of
do
real
time,
but
periodically
shake
the
system.
A
B
B
E
E
Yeah
I,
don't
you
know
I,
don't
know
if
an
item
was
checked
back
in.
Would
it
grab
that
hold
it
that
in
our
kind
of
hard
to
know
because
those
holes
got
filled
so
we
weren't
looking
for
them,
but
I,
don't
know
if
that's
part
of
it
I
think
it's
just
related
to
the
queue
not
that
it
would
never
get
hold.
If
one
got
checked
back
in
it
might
trap
it,
but
I
don't
know
for
sure
on
that.
A
And
that
makes
some
stupid
sense
if
there
was
something
going
on
in
the
system.
At
the
moment
he
placed
his
hole
that
made
it
temporarily
in
that
moment,
unfillable
and
caught
that
didn't
put
it
in
the
queue.
But
then,
when
you
came
back
and
touched
the
begin
to
place
a
new
hold
koha
like
reevaluated,
so
oh,
we
can
fill
this
hole.
Then
toxic
in
the
queue.
A
A
A
A
A
When
koha
picks
an
item
to
fill
a
hold
in
the
holds
Cube,
it
will
always
give
first
preference
to
an
item
whose
home
Library
matches
the
hold
pickup
location,
because
koha
assumed
that's
doing
you,
the
favor
of
sort
of
shepherding
your
book
back
to
its
Home
Library
in
the
process
of
filling
a
hole
which
is
all
well
and
good.
Unless
you're,
a
library
like
like
us
who
Home
Library,
means
nothing.
Every
single
item
in
our
collection
shows
our
main
branches,
the
Home
Library.
A
K
A
A
A
F
E
Yeah
we
we
floated
a
few
item
types
in
Symphony
before
we
migrated
and
then
when
we
migrate,
it's
like,
let's
just
leave
everything
where
it
is
and
we'll
come
back
to
that
question
later.
But
we
haven't
come
back
to
that
question
yet,
and
people
are
getting
a
little
antsy
like
we
want
some
new
stuff
I'm
like
well
figure.
It
out.
Give
me
a
second.
So
we
just
we're
evaluating
like
the
rotating
collection
options,
because
there's
two
of
those
and
who's.
H
F
A
F
Our
collection,
too
I
think
there's
only
like
a
few
item
types.
We
actually
set
up
item
types
that
don't
float
and
then
everything
else
just
goes
on
its
on
its
merry
way.
So
and
then
we
built
some
reports
to
track
where
things
are
dying
on
the
vine
and
our
collection
staff,
call
them
back
in
or
ask
them
to
be
sent.
You
know
using
transfer.
So
good
luck.
A
That
reminds
me
that
I
haven't
looked
up
the
Arlington
Library
Memorial
bug
for
voting
behavior
recently,
which
I
only
think
of
as
the
Arlington
Bud,
because
it's
when
I
filed.
While
we
were
doing
your
training,
where
the
Circ
rules
for
whether
or
not
something
float,
don't
get
enforced.
As
expected.
F
Be
a
full
functioning
Branch
with
no
special,
no
special
cases.
So,
okay,
that's
a
special!
It's
a
special
libraries
that
are
the
hard
part
like
we
have
a
reference,
a
local
history
room
inside
of
our
Central
Library,
so
nothing
out
of
there
circulates-
and
you
know
the
special
cases
I
always
put
code
onto
the
test.
A
C
I've
got
another
one
if,
unless
someone
else
wants
to
go
all
right,
changing
the
image
on
for
item
or
for
items
in
koha
they're
supposed
to
be
like
an
upload.
Next
to
the
edit
item,
where
you
can
upload
images
and
it's
not
appearing
on
my
system-
I'm
wondering
if
they
removed
that
recently
or
because
I
saw
there
was
a
Monday
minutes.
But
it
was
like
a
year
ago
and
my
next
test
was
to
use
the
a56
and
upload
the
image
through
there
and
that
didn't
work
either.
C
A
A
I
G
I
K
K
C
K
C
K
A
F
I
have
a
basic
SQL
question
that
I
was
hoping.
The
group
could
help
me
on
I'll.
Put
this
in
I
noticed
that
word
using
two
different
SQL
statements
for
calculating
age
of
a
patron
I'm,
just
kind
of
curious
to
know
which
one
is
more
act.
I
mean
they
both
seem
to
give
the
same
date
but
I'm,
just
wondering
which
one
seems
more
appropriate
to
use
I
kind
of
like
to
keep
it
all
the
same
and
all
the
reports,
if
possible,.
A
F
F
D
G
You
can
also
as
an
alternate
option,
while
he's
looking
there's
the
system
preferences
where
you
can
set
a
mark
field
to
store
the
who
created,
who
edited
and
then
you
don't
have
to
fight
with
blog
this
much.
You
can
just
query
the
mark
field
for
that
information
and
use
that
to
link
it
to
the
borrower
table.
D
A
Let's
scroll
up
a
bit,
there's
a
section
here
that
walks
through,
like
there's
the
different
modules
of
the
action
log,
that's
sort
of
how
they
break
down
because
they're
stored
in
the
database
and
a
slightly
confusing
fashion,
because
why
not?
So
that
was
the
first
thing
I
linked,
but
there
is
also
I
scrolled
back
up.
There's
a
section
in
here
about
querying
marks
how
to
grab
the
value
out
of
any
given
Mark
field
out
of
a
record.
So
that's
what
you
would
use
to
get
that
Creator
ID
out!
A
K
A
So
I
do
that.
That's
going
to
give
me
everything,
that's
in
the
action
logs
in
the
cataloging
module,
where
they
have
added
something,
and
one
of
the
things
it
tells
us
over
on
that
reports.
Library
page,
is
that
in
the
cataloging
log
the
info
field
is
going
to
always
give
us
the
literal
item
or
biblio,
it's
going
to
say
either
this
was
an
item
or
this
was
a
bib
that
got
added
or
changed
followed
by
a
dump
of
the
data
that
went
into
the
database
okay.
A
That
doesn't
give
me
much
information
here.
This
is
just
within
the
action
logs
table
itself,
but
that's
the
borrower
number
of
the
librarian
who
created
this
record.
Okay
and
that's
the
bib
number
of
the
bib
that
was
created,
okay
and
that's
when
it
happened.
So
then
we
can
kind
of
tweak
that
around
a
little
bit,
the
first
look
limit
that
time
stamp.
A
A
A
A
A
D
A
A
There's
a
little
Library
around
here
that
has
been
on
koha
forever,
like
this
guy
Tim
just
installed
it
and
set
it
up
one
day
and
they
were
unsupported
for
years
and
years
and
years
and
they
went
to
buy
water
support
a
year
and
a
half
ago,
because
Tim
said
he
wanted
to
retire
someday
and
that
made
sense
to
me
like
yeah.
It
was
working
really
fine
for
them.
So
long
as
Tim
never
goes
anywhere.
I
know.