►
From YouTube: Acquisitions Special Interest Group - 4/19/2022
Description
Rhonda and the group walked through the testing and sign-off process using bug 30510 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30510)
A
Welcome
to
the
april
meeting
of
the
acquisition
scene
for
koha,
we
are
a
group
that
gets
together
and
we
welcome
any
kind
of
questions
that
you
might
have
or
cool
things
that
you
discovered
about
coha
or
anything
like
that.
So
each
meeting
we
start
out
with
just
asking.
If
anybody
has
come
with
questions
that
they
would
like
to
ask
the
group
or
ideas
that
they
have
for
new
developments
or
anything
like
that.
So
does
anybody
have
anything
like
that.
A
All
right,
so,
if
we
don't
have
anything,
then
my
thought
for
this
month
was
to
go
through
the
acquisition
bugs
in
bugzilla
and
see
if
there
was
one
that
we
could
just
sign
off
on
just
so
that
people
could
have
see
what
it's
like
to
actually
sign
off
on
a
bug,
because
the
people
who
develop
them
can't
sign
them
off.
They
need
somebody
else
to
do
that,
to
test
it
basically,
and
so
we
can
help
the
process
move
forward
if
we
sign
off
on
the
bug.
A
A
A
A
So
that's
an
opportunity
for
you
to
go
in
and
comment
on
ones
that
you
would
like.
I'm
still
scrolling-
and
you
know,
try
and
boost
the
interest
in
for
the
developers
to
actually
fix
fix.
Some
of
these
bugs
next
status
is
reopened,
and
then
these
here
are
assigned.
That
means
somebody
has
taken
them
and
they're
going
to
start
working
on
them.
So
those
are
also
good
candidates
to
make
comments
on.
If
you
have
an
opinion
about
how
something
should
be.
B
A
C
A
A
A
I
think
I
so
I
looked
at
this
one
add
a
patron
reason,
column
to
the
suggestion
tables
on
suggestion,
dot
tt,
so
that
one
looked
pretty
straightforward
when
I
looked
at
the
test
plan.
So
when
you
come
in
here,
what
you're
gonna
see
is:
okay,
lucas
is
the
person
that
it's
assigned
to
that.
He
actually
probably
wrote
the
the
fix
there
isn't
much
here.
So
basically,
what
this
is
is
adding.
It
they'll
add
another
column
to
the
suggestions
table,
because
some
some
librarians
would
like
to
know
why
the
patron
is
suggesting
it.
A
A
A
A
A
Let's
just
do
it
like
that
instead,
so
this
stuff
correct
me
if
I
am
wrong,
but
this
is
the
information
that's
used
to
update
I'm
gonna,
just
click
on
this
update
the
the
sign
off
on
on
bugzzilla,
your
name
and
your
email
enter
a
simple
name
for
your
sandbox
lowercase,
all
letters
and
numbers.
So
I
usually
do
something
like
bug:
30
510,
something
like
that
mark
advanced
options.
I've
never
done
anything.
So
basically,
oh,
I
missed
the
bug
number.
I
was
like
where's
the
bug
number.
E
A
A
A
A
A
Yes,
yeah,
so
there's
there's
the
qa
process,
then,
after
after
we
sign
it
off,
then
then
quality
assurance
there's
a
team
that
will
check
it
and
they
run
some
like
standard
tests
against
it.
You
know,
scenarios
and
stuff
like
that
and
they'll
look
over
the
code
make
sure
the
code
meets
the
quality
that
they
want
in
quahog
stuff
like
that
so
yeah.
This
is.
A
This
is
just
to
say
that
we
think
it
does
what
it
should
be
doing,
and
you
know
if
we
sign
it
off
and
maybe
somebody
else
sees
it
and
signs
it
off
before
qa
gets
around
to
it.
You
know
that'll
that'll,
all
help
them
understand
it,
and
and
if
we
find
something
that
we
don't
like
you
know,
we
can
just
update
the
the
bug
with
you
know.
We
we
tried
to
test
it.
You
know
we
we
tested
it
and
we
found
you
know
when
we
got
to
step
five,
that
this
happened.
B
A
C
A
F
Sometimes
it
happens
fairly
fast
and
other
times
it
takes
a
while,
and
then
I've
found
that
sometimes
it
will
provision.
I
guess
and
then
I
go
and
try
to
use
the
staff
or
the
opac,
and
I
get
some
kind
of
error
message
that
I
wasn't
expecting
and
so
at
times
I've
gone
and
used
the
biblib
or
the
ptfs
sandboxes
instead
of
by
water,
because
I
couldn't
get
a
bywater
sandbox
to
work
for
me
and
that's
okay,
too
yeah.
A
This
is
how
I
got
there
last
time.
I
never
can
remember
the
right
address
so
which
do
you
prefer
pts
f.
I
always
get
that
backwards,
ptfs
europe
or
libra.
Now
that
we're
talking
about
it,
maybe
maybe
that
was
enough
to
yeah.
Okay,
we
just
had
to
threaten
to
use
someone
else,
okay,
step
one.
What
is
step
one.
E
E
A
A
F
A
A
A
B
D
E
C
C
A
C
A
A
A
A
A
A
F
A
A
E
A
E
A
C
E
A
A
F
A
E
A
A
A
A
A
B
A
A
F
The
other
thing
that
happens
to
me
until
I
learned
that
I
needed
to
refresh
the
page
is:
I
would
go
and
change
the
status
and
then
I
would
get
this
next
page.
That
says
mid-air
collision
like
that,
and
I
guess
it's
too
much
is
happening
at
the
same
time
or
something
I
don't
know
so.
Yeah
refreshing
that
page
before
you
change
the
status
should
prevent
that.
A
F
A
Yes,
this
is
how
you
get
your
name
in
lights
and,
if
yeah
this
this
right
here,
you
know,
there's
it
shows
you
how
many
needs
sign-off
bugs
there
are,
and
you
know
just
all
kinds
of
different
things
that
have
you
know
about
the
status
of
the
pass.
Qa
failed
qa,
so
that
this
qa
is
the
next
step
after
the
synopse.
A
F
C
A
B
F
We
have
each
of
our
selectors.
We
have
one
person
that
kind
of
goes
in
and
looks
at
all
of
them
and
what
we
actually
do.
What
she
goes
in
and
does
is
she
says
well
that
looks
like
a
mystery,
so
she
actually
goes
and
changes
it
and
we
use
the
fund,
even
though
we're
not
really
doing
anything
with
the
fund.
F
B
Oh
okay,
yeah
we
actually
we
do
it
the
way
you
just
stated,
but
when
it's
we
titled
like
an
rfp
card
request
for
purchase,
and
so
when
I
go
in
as
acquisitions
to
order
it,
we
do
edi,
but
I
will
put
a
hold
on
each
item
based
on
who
suggested
it
and
I'll
usually
like
put
a
date
in
there
or
something
but
okay.
Thank
you.
A
Yeah-
and
we
do
something
similar-
we
just
we
have
these-
we
have
each
collection
developer
has
their
own
tab
like
we
went
into
the
whatever
that's
called
authorized
values
and
set
up
tabs
for
all
of
the
collection
developers.
So
we've
got
somebody
assigned
each
day
to
look
through
any
suggestions
that
come
and
then
assign
it
to
the
tab
of
the
collection
developer,
and
then
the
collection
developers
are
responsible
for
keeping
their
number
down,
so
it's
very
similar
to
what
harvard
does
and
then
the
collection
developers
will
actually
put
it
into.
A
A
A
Yes,
yes,
yes,
yes,
all
right,
so
we
go
back
here.
This
is
where
we
had
this
and
there
is
a
big
red
delete
button.
This
is
a
good
thing
to
do,
because
I
think
what
is
it
three
days
and
then
it
will
automatically
go
away,
but
if
other
people
they
they
there
can
only
be
a
certain
number
of
active
sandboxes
at
one
time.
So
if
other
people
want
to
come
in
here
and
use
it
and
you've
got
one,
that's
just
sitting
there,
that's
kind
of
not
nice,
so
we
can
say
delete.
B
A
E
So
they're
there
for
24
hours,
but
I
think
the
only
concern
would
be
is
if
it
started
getting
major
use
like,
but
there's
so
many
other
like.
If
this
one
gets
full
and
it
stops
creating
sandboxes,
there's
bible,
even
there's
ptfs
europe.
So
I
don't
think
there's
too
much
harm
in
letting
your
set
throughout
the
day.
If
you
need
it
to.
A
F
With
an
acquisitions
bug
because
sometimes
you're
going
to
have
to
you
know
import
orders,
you
know
create
baskets
and
make
orders,
and
so
you
may
have
done
an
awful
lot
of
work
to
actually
get
to
the
testing.
You
know
applying
the
patch
portion,
so
yeah
seems
like
because
sometimes
acquisitions
bugs,
I
find
they're
a
little
bit
harder
to
test
because
they
often
take
a
lot
of
setup.