►
From YouTube: Elevating ILL with some Rapid Improvement
Description
Presenters:
- Andrew Isherwood (PTFS Europe)
- David Peacock (University of Hertfordshire)
A
Hello,
my
name
is
David
peacock
I'm,
a
library
manager
at
the
University
of
Hertfordshire
I,
wanted
to
give
a
brief
introduction
to
Andrew's
main
presentation
about
the
technical
aspects
of
the
kohar
integration
with
rapid
Lau.
To
give
a
business
context
of
why
the
university
chose
rapid
out
by
allow
the
impact
of
that
integration
within
koha
and
the
actual
impact
is
had
on
the
service
give
some
context.
The
University
of
Hertfordshire
main
campus
is
20
miles
north
of
London.
A
A
To
set
the
scene
for
interliby
loans
at
the
University
of
Hertfordshire,
the
university
offers
a
mediated
free
internet
loans
for
all
students
and
staff.
Traditionally,
like
many
UK
libraries,
we've
used
the
British
Library
document
delivery
and
lending
services
for
the
majority
of
our
interlib
loan
requests.
A
Why
did
we
use
rapid
oil?
Well,
the
Story
begins
at
the
start
of
the
first
pandemic,
March
2020,
when
the
British
Library
stopped
supplying
into
Library
loans.
We
had
a
speculative
email
to
join
a
trial
of
rapid
oil.
Around
that
time
we
decided
we
would
join
expecting
maybe
to
get
the
odd
one
or
two
requests,
but
never
expecting
it
to
fulfill
all
our
requirements
during
the
first
lockdown
and
subsequently,
in
actual
fact,
it
did
meet
all
our
requirements
largely
and
it
superseded
our
expectations.
A
A
So
when,
because
it
chases
the
sun,
we
might
as
well
get
documents
returned
from
Australia
during
the
night
awaiting
us.
For
our
breakfast
time
start
of
the
day
we
had
very
high
fulfillment
rates
stood
in
the
first
lockdown.
We
had
a
92
fulfillment
rate,
that's
very
high
and
much
higher
than
the
British
Library.
So
that
meant
we
didn't
have
to
chase
individual
libraries
and
get
things
from
Individual
University
libraries
that
we
had
previously.
A
In
addition,
it
allowed
for
new
workflows,
including
instant
verification
of
resource
availability,
which
again
improves
our
need
for
our
mediated
requests.
We
like
the
idea
of
a
one-off
subscription
fee
with
no
transaction
fee,
so
that
meant
we
could
scale
up
usage
further
and
improve
our
promotion
and
the
visibility
of
the
service
without
an
increase
in
expenditure.
A
The
initial
workflow
is
we
wanted
to
address
with
the
integration
with
cohort
and
into
Library
loans
were
when
we
first
started
doing
the
first
lockdown
staff
had
to
cut
and
paste
the
request
from
the
rapid
dialogue
platform
into
the
cohort
request,
form
or
requests
at
that
stage
had
to
be
mediated.
Staff
couldn't
place
the
request
directly
onto
that.
A
The
rapid
ILO
platform
and
we
wanted
to
utilize
the
power
of
using
doas
and
auto
completion
functionality
that
weren't
available
with
our
integration
with
the
British
Library
API
and
finally,
Interline
staff
had
to
send
documents
manually
from
the
vapid
illow
platform
onto
the
requester,
using
the
email
for
moving
cohort.
So
these
things
initially,
although
there
were
great
savings
and
great
improvements,
these
things
were
quite
clunky
and
we
wanted
to
integrate
those
within
cohort
into
Library
loan
workflows,
and
this,
as
Andrew
will
explain.
A
A
It
actually
shows
a
46
increase
from
2018
2019,
which
was
the
last
normal
year
before
the
pandemic,
so
a
46
increase,
so
that's
a
huge
increase
and
that
excludes
August,
which
isn't
the
educated
form
shown
in
these
figures.
So
we
will
manage
to
really
improve
this
because
of
these
efficiencies
with
the
cohort
integration,
Without
Really,
any
great
increase
in
staff
time
and
finally,
the
auto
completion
from
within
different
sources
like
PubMed
and
scopus,
and
things
like
that.
That
shows
that
was
greatly
improved.
B
I'm,
going
to
give
you
a
very
short
demonstration
now
of
placing
a
request
and
managing
requests
from
both
the
patron
and
the
staff
standpoints.
So,
let's
jump
in
so
the
first
thing
we'll
do
is
Imagine
we're
a
patron
who
wants
to
place
an
ill
request
with
rapid
ill
I
should
point
out
this
point
that
I'm
on
hartfish's
test
server,
so
some
of
the
things
we
see
will
be
specific
to
them,
but
I'll
Point,
those
out
as
we
go
through.
So
we
click
create
a
new
request,
and
this
is
something
that
Hearts
have
turned
on.
B
This
is
a
declaration,
so
we
just
click
past
that
so
now
we're
in
the
rapid
ill
request
form
so
rapidil
provides
a
number
of
different
material
types
and
we
can
see
them
there.
So
what
I'm
going
to
do
is
try
and
place
a
request
for
a
journal.
Article
I've
got
some
metadata
here,
so
I'll
just
copy
and
paste
that
in
so
we
have
an
article
title.
B
B
So
this
is
telling
the
user
that
they
don't
need
to
request
it
because
they
can
all
re-access
it.
Rapid
ill
is
aware
of
hertfordshire's
Holdings
that
they
have
locally
and
won't
allow
a
request
to
be
placed
for
those
items.
So
that's
why
we're
getting
this
notification
here,
so
the
user
could,
at
this
point,
just
click
on
the
item
and
then
be
taken
straight
to
it.
So
now,
let's
try
and
place
in
a
request
for
an
item
that
isn't
already
locally
available.
B
B
B
So
now
I've
got
that
metadata
filled
in
if
I
click
make
request.
That
will
then
contact
rapid
ill
and
place
the
request.
So
we
can
see
that
that's
now
appearing
in
our
list
of
requests
and
says
it's
requested.
If
we
click
view,
we
can
see
that
the
metadata
we
provided
is
all
there
and
we've
also
got
a
rapid
ill
identifier,
which
is
the
unique
identifier
that
rapidill
provides.
So
at
this
point,
the
user
can
be
confident
that
this
the
request,
they've
placed,
has
been
placed
and
accepted
and
will
be
fulfilled
as
quickly
as
possible.
B
It's
sometimes
the
case
that,
when
a
user's
placing
a
request,
they
don't
have
sufficient
metadata
for
that
request
to
be
fulfilled
automatically.
However,
the
rapid
ill
integration
provides
the
facility
for
staff
members
to
jump
in,
provide
any
missing
metadata
and
then
attempt
the
submission
again.
So
I'll
show
you
how
that
works.
So
if
we're
a
patron
now
placing
a
request
I'm
going
to
provide
a
journal
title,
an
article
title
and
then
I
setting
this
request
will
fail,
because
this
isn't
sufficient
metadata
for
the
request
to
happen
automatically.
B
So,
let's
see
what
happens,
we
click
make
a
request,
so
this
has
created
a
request
within
coher,
but
it
hasn't
created
a
request
within
rapid
ill.
But
as
far
as
the
user
is
concerned,
they've
provided
all
the
metadata
that
they
had.
So
it's
now
the
responsibility
of
a
staff
member
to
go
into
the
request,
modify
it
add
in
any
missing
metadata
and
then
submit
it.
B
So
I'll
show
you
how
that
works
now
so
over
here
in
the
staff
interface,
we
can
see
the
request
here
and
we
can
immediately
see
in
the
staff
notes
that
we've
got
a
note
from
the
rapid
ill
API
saying
that
we
must
specify
a
year
or
volume.
So
that's
identified
the
metadata.
That's
missing
for
this
request.
B
So
at
this
point,
I
can
go
into
the
request
and
edit.
The
item
metadata
add
the
year,
which
is
1915,
update
the
request
and
then
I
complete
attempt
to
place
the
request
again.
So
if
we
click
click
request
from
Rapid
ill,
that
goes
away
places
the
request
we
can
see
the
status
is
now
requested
and
down
here
we've
got
a
rapid
ill
identifier,
which
is
the
unique
identifier
for
that
request
with
rapid
ill.
B
So
that's
how
a
staff
member
can
jump
in
after
a
request
has
been
placed
fix
anything
that's
wrong
with
it
and
then
resubmit
it
to
Rapid
ill.
If
we
look
in
the
request
log,
we
can
see
that
that
whole
process
was
audited.
We've
got
the
request,
has
changed
from
a
new
request
to
it
to
requested
status,
and
the
request
here
has
succeeded.
B
So
let's
have
a
quick
look
at
that
now,
so
we
go
and
create
a
rapid
ill
request
and
we
can
see
immediately,
we've
been
being
provided
with
help
at
the
bottom
here
for
the
fields
we
need
to
fill
in
for
the
material
type
that
we've
selected
and
obviously,
as
we
change
the
material
type,
those
fields
will
change
and
they
will
update,
as
as
the
user
fills
them
in.
So
if
I
start
filling
in
some
information.
A
B
A
year
and
an
issn
and
a
user
so
now
I've
selected
that
we
can
see
here
that
the
item
again
has
been
note.
We've
been
notified
that
the
item
is
available
locally.
So
that's
the
first
thing
we
do.
This
is
in
line
with
the
Patron
side
of
things.
We
alert
the
user
that
the
item
is
available
locally.
So
if
we
just
get
rid
of
this
metadata
now
and
try
a
different
item.
B
So
if
we
provide
a
journal
title,
an
article
title
a
year
and
an
issn
rapid
ill
is
immediately
contacted
to
find
out
whether
this
item
can
be
requested,
and
we
can
see
that
it
can
so.
The
staff
member
at
this
point
can
submit
the
request
and
have
confidence
that
that
item
is
going
to
be
fulfilled
and
the
request
can
be
placed
without
any
problems.
B
B
B
That
will
then
place
the
request
with
rapid
ill
and
then
I
can
quickly
show
you
the
live
log
that
we
pull
in
from
Rapid
RL
whenever
we're
on
the
manage
ill
request
page.
So
here
we
are
and
if
I
just
scroll
down
we
can
see,
we
always
get
a
live
view
of
the
rapid
RL
history
for
any
request
that
we're
viewing
So.
Currently
the
rapid
ill
state
is
pending.
Well,
this
isn't
actually
a
request.
B
Finally,
we'll
take
a
quick
look
at
a
very
small
bit
of
development
that
was
done
off
the
back
of
the
rapid
ill
work
and
just
helped
level
up
the
user
experience
of
ill
in
general.
This
isn't
strictly
tied
to
the
rapid
ill
integration.
This
can
be
used
with
other
interlibrary
loan
providers
as
well,
so
in
short,
we're
using
cross
ref
to
automatically
look
up
metadata
based
on
a
DOI,
so
the
user
just
has
to
paste
in
a
DOI
into
the
form
and
the
rest
of
the
metadata
is
automatically
populated.