►
Description
Presenter:
- Jonathan Field (PTFS Europe Limited)
Slides:
- https://docs.google.com/presentation/d/1XzfveT-vHhFmuW_3eHNZBhxG45LV_fCc/edit?usp=sharing&ouid=106844837026229096502&rtpof=true&sd=true
A
Hopefully,
you'll
find
this
interesting,
so
I'm
Jonathan
field,
I'm,
one
of
the
founders
and
the
managing
director
of
ptfs
Europe,
and
we're
going
to
have
a
look
at,
hopefully
something
that
exciting
that's
coming
up,
which
you
actually
won't
find
on
bugzilla
at
the
moment.
But
I'll
talk
a
bit
more
about
that
in
a
moment
so
erm.
A
So
first
of
all
what
is
ERM
so
the
Wikipedia
definition
is
well
it's
on
the
screen
there,
but
I
think
hopefully,
most
of
you'll
understand
what
an
ERM
module
is.
So
it's
for
tracking
electronic
resources
that
you
might
have
in
your
library
and
as
I
mentioned
yesterday
in
the
presentation
that
we
did
yesterday
afternoon.
A
This
is
a
joint
development
that
we've
done
or
they're
working
on
at
the
moment,
with
byword
Solutions
and
biblibra
and
ourselves
and
we're
been
really
happy
to
be
working
with
Jonathan
Gerard
on
this
and
I
think
I.
Think
Jonathan,
hopefully,
is
online
as
well
at
the
moment.
A
So
he's
he's
just
become
a
father.
So
congratulations
Jonathan
on
that
yeah.
A
So
he
isn't
here
in
person,
but
he's
online
I
think
so
if
there
are
any
sort
of
questions
that
he
might
be
able
to
get
himself
involved
when
he
is,
he
is
around
so
I.
Guess,
historically
this
information
about
your
subscriptions
to
electronic
resources.
They
would
have
been
held.
Probably
anything
from
you-
know:
access
databases,
Excel
spreadsheets
to
piece
of
pieces
of
paper
stuffed
in
covered
cupboards.
So
that's
what
we're
trying
to
address
here
is
the
storage
of
that
information.
A
Now,
historically,
libraries
using
COA
and
vendors
like
ourselves,
we've
had
to
work
around
this
because
there
isn't
any
sort
of
facility
within
COA
at
the
moment
to
manage
it.
So
we've
had
to
do
it
in
creative
ways.
So
some
of
you
may
be
familiar
with
coral.
The
electronic
Resources
management
you
may
use
it
which
which
can
work
alongside
of
of
COA.
A
The
pace
of
development
of
coral
is
also
slow,
so
we
think
that
actually
bringing
this
functionality
anality
into
Co
is
actually
a
game
changer
for
for
KOA,
and
you
know
for
libraries,
and
we
hear
a
lot
about
Library
service
platforms.
Now,
rather
than
ils's
and
and
lms's,
and
we
think
it
elevates
cover
to
be-
you
know
to
be
a
fully
functional,
Library
Services
platform.
So
that's
very
exciting
as
well.
A
And
in
terms
of
the
library
management
system,
well,
we
believe
it's
crucial
to
to
having
a
fully
functional
Library
management
system
and
I
think
it's
probably
fair
to
say
that
most
libraries
even
of
any
size.
So
even
you
know
the
the
public
libraries
that
we
have
in
the
UK.
They
don't
necessarily
have
a
lot
of
electronic
resources.
They
all
have
some
electronic
resources
of
in
some
shape
or
form.
A
Even
if
it's
sort
of
you
know
small
subscriptions
to
local
history,
databases
and
that
sort
of
thing
so
I
think
it's
important
for
for
all
libraries,
it's
important
for
us
as
vendors,
because
we're
competing
obviously
against
proprietary
vendors,
who
already
have
this
functionality
so
obviously
makes
us
more
competitive
and
at
the
end
of
the
day,
why
wouldn't
we
put
an
electronic
resources
module
in
into
code?
It
makes
perfect
sense.
A
Why?
Wouldn't
we
do
it
so,
just
before
I
jump
into
the
demo
just
to
explain
a
little
bit
about
what
it
does
right
now,
what
we're
hoping
it's
going
to
do
and
then
we'll
actually
go
and
have
a
look
at
it.
So
right
now
it
stores
agreements
information.
A
So
that's
information
about
the
agreement
that
you
have
with
your
vendor
so
includes
things
like
documentation,
whether
the
agreement
is
current,
the
subscription
period
of
that
agreement
and
so
on,
and
that
also
includes
related
agreements
which
which
I'll
show
you
in
just
a
moment
licenses.
So
that's
that's
information
about
the
license
record
itself,
so
that
generally
will
include
a
PDF
of
the
license:
a
scan
of
the
license
e
Holdings.
So
this
is
the
resource
itself.
So
what
what
is
the
electronic
title?
A
We've
added
integration
with
ebscode's
Holdings
management
tool,
so
some
of
you
may
already
be
aware,
but
ebsco
provide
this
tool
have
done
for
about
the
last
two
to
three
years:
called
Holdings
IQ,
it's
a
bi-directional
API
that
allows
you
to
manage
their
knowledge
base
in
real
time
and
excitingly.
It's
the
first
use
of
the
view.js
JavaScript
framework
in
color.
A
So
that's
very
exciting
because
it's
it's
sort
of
experimental
and
you
might
see
some
sort
of
features
on
the
screens
that
sort
of
look
slightly
different
and
that's
because
we're
using
or
Jonathan's
using
View
for
this
piece
of
development
and
it's
it's
with
with
a
view
to
actually
maybe
in
the
future
using
it
in
other
parts
of
Cairo
as
well.
So
that's
that's
quite
exciting
in
terms
of
what
could
it
do
so?
A
The
one
thing
we
haven't
got
to
is
usage
information,
so
most
of
your,
the
Publishers
will
provide
statistics
either
by
Sushi
connections
or
counter
in
counter
format,
and
we
want
to
add
that
in
so
we
can
actually
analyze
the
the
usage
of
electronics
subscriptions
in
the
United
Kingdom.
We
have
big
organizations
that
that
run
the
higher
education
institutions
called
jisk
and
they
run
a
service
called
just,
which
is
like
a
consolidation
service
for
all
your
subscription
statistics
and
I'm
sure
there's
similar
things
in
other
places
around
the
world.
A
So
that's
also
something
we'd
like
to
integrate.
We
wanted
to
look
at
workflow
management,
just
because
it's
a
great
feature
in
Coral.
If
any
of
you
used
it,
so
workflow
management
really
is
when
you
know
subscriptions
coming
up
for
Renewal
and
first
of
all,
maybe
the
library
director
needs
to
sign
off
on
it,
and
then
it
gets
passed,
maybe
to
the
Acquisitions
librarian,
who
orders
it
and
then
to
the
Electronic
Services
librarian,
who
sets
it
all
up
online.
So
you
can
pass
the
record
around
if
you
like,
between
different
people.
A
It's
a
great
feature
and
really
the
only
reason
we
haven't
done
it
straight
off.
The
bat
is
that
we
think
actually
there's
scope
for
widening
that
out
to
a
bigger
cover
feature.
So
you
know
maybe
using
workflow
management
for
things
like
cataloging.
Somebody
creates
a
short
catalog
record,
fast,
ad
catalog
record,
and
then
they
want
to
pass
it
on
to
the
catalog.
A
To
perhaps
you
know,
catalog
the
record
fully.
So
there
are
other
potential
uses.
So
we'll
probably
look
at
that
in
a
more
wider
context
later
on
at
the
moment,
as
you
see
in
a
moment,
we're
working
with
ebsco's
knowledge
base,
but
other
knowledge
bases
are
available
and
we're
looking
at
potentially
integrating
it
with
go
KB,
which
some
of
you
may
know
about,
which
is
an
open,
Global
Knowledge
base
in
the
UK
we
have
a
a
knowledge,
Base
called
KB
plus,
which
again
is
a
sort
of
nationally
organized
knowledge
base.
A
There's
also
potential
for
improved
reporting,
one
of
the
big
benefits
of
actually
bringing
ERM
into
COA.
Is
that
often
you
want
to
report
on
both
your
electronic
Holdings
and
your
physical
Holdings
and
that's
difficult
when
the
data's
in
two
different
places.
That's
one
of
the
problematic
things
with
coral.
Is
it
when
the
electronic
information
is
over
here
and
the
printed
information
is
over
here
it's
very
difficult
to
report
on
foreign
opportunities.
Like
you
know,
we
maybe
produce
A
to
Z
Journal
listings,
like
ebsco's
publication,
find
and
put
that
on
the
OPAC.
A
So
there's
lots
of
scope
for
other
things.
It
could
do
and
just
before,
I
jump
into
the
demonstration
I'll.
Just
give
you
a
little
bit
of
terminology
because
I'm
going
to
be
shouting
out
these
sort
of
terms,
but
we've
got
the
Holdings
IQ.
So
that's
ebsco's,
proprietary,
API,
it's
as
I
said
it's
bi-directional.
It
works
with
their
knowledge
base.
It
allows
you
to
manage
it,
update
it
and
change
things
in
it.
A
So
it's
a
very
powerful
tool,
a
title
in
ERM
terms
we're
talking
specifically
about
the
metadata
of
the
material.
So
that
would
be
things
like
the
title
itself
and
ISS
an
issn,
an
e-issn,
a
publisher
and
so
on.
But
then
we
have
this
separate
term,
which
is
a
resource.
So
resource
is
slightly
different
because
it's
in
effect
an
instance
of
a
title
so,
for
example,
teza
law,
it's
actually
available
in
from
different
Publishers
and
different
sources
in
different
packages.
A
So
Tessa
law
has
a
has
a
title,
obviously,
and
it
has
an
issn
and
so
on,
but
it
belongs
as
a
resource
in
a
directory
of
Open,
Access
journals,
Criminal,
Justice,
abstracts
journals
for
free
and
some
other
packages
as
well,
and
that
means
that
actually
it's
a
slightly
different
thing,
because
different
Publishers
May
hold
different
coverage.
A
Information
about
that
journal,
I'm
going
to
talk
about
a
package,
so
a
package
really
is
just
a
bundle
of
Journal
titles
that
are
sort
of
collected
together
either
by
you
collecting
them
together
into
a
package
or
by
the
Publishers
selling
you
a
package
of
journals
in
the
UK.
Again
just
could
do
do
the
higher
education
institutions
they
sell,
they
negotiate
sort
of
nationally
with
Publishers
and
build
their
own
packages
which
they
which
universities
could
then
subscribe
to,
and
then
finally,
we've
got
providers
and
vendors.
A
So
this
is
the
person
who
actually
provides
a
resource,
so
it
can
be
a
national
body.
In
our
case,
somebody
like
Jessica,
it
could
be
an
individual
publisher
or
vendor
and
obviously
historically
in
a
print
world.
You
work
with
a
sort
of
a
book
supplier
and
when
you
move
into
the
electronic
world,
the
vendors
are
slightly
different,
they're,
not
sort
of
providing
with
a
physical
physical
material.
So
it
does
sort
of
widen
out
the
concept
of
what
a
vendor
is
really
I.
Think,
okay,
let's
have
a
look
at.
A
Now
the
first
thing
to
say,
having
just
had
that
most
excellent
presentation
on
sandboxes,
is,
if
you
go
to
the
biblibra
sandbox
site,
you'll
notice
that
there's
a
single
sandbox
there
that
has
a
delete
button.
That's
grayed
out!
You
can't
actually
delete
it
at
the
moment.
So
whilst
this
development
is
going
on
with
ERM,
we've
got
a
permanent
sandbox,
which
has
been
great
in
terms
of
testing
and
testing
it
and
sort
of
filling
with
data.
So
it
doesn't
keep
getting
wiped
out.
A
So
just
to
let
you
know,
if
you
see
that
sandbox
now
I
think
I
might
see
if
I
can
put
this
on
the
on
the
stand
here,
so
that
I
can
try
and
do
this
with
two
hands,
make
it
a
bit
easier.
A
Okay
right,
so
here
we
are
in
the
in
the
ERM
sound
box,
and
the
first
thing
to
say
really
is:
if
I
just
go
into
Administration.
A
And
into
global
system
preferences,
you'll
notice
on
the
on
the
left
hand,
side
here,
there's
a
new
electronic
Resources
management
tab
and
there's
a
big
master
switch.
So
here's
the
big
master
switch.
Do
you
want
to
even
use
this
module
or
not
so
that
that's
the
first
thing
to
say:
do
we
want
to
enable
it
or
disable
it
then
there's
some
very
specific
system
preferences
for
the
electronic
resources
providers
so
specifically
for
the
ebsco
knowledge
base.
A
So
if
you
want
to
use
that
Holdings
IQ
tool,
you
have
to
speak
to
ebsco
they'll,
give
you
an
API
key,
and
you
need
to
put
that
into
these
into
these
fields
here
and
then
we
have
the
electronic
resources
providers.
A
So
at
the
moment
you
can
see,
there's
there's
just
two
there's
working
with
ebsco
and
is
working
with
local
Holdings
and
I'll
talk
about
both
of
those.
But
this
here
really
is
where
there's
potential
in
the
future,
for
adding
other
knowledge
bases
so
go
KB,
KB,
plus
and
so
on.
A
I
go
over
to
Administration.
A
This
is
controls
what
displays
in
various
tables
and
in
koha
and
again
you
can
see.
There's
a
new
table
setting
for
erm,
so
you
can
choose.
What
fields
are
hidden
by
default
which
which
fields
are
shown
by
default.
So
just
Falls
in
line
with
the
rest
of
color
really.
A
If
I
go
back
to
the
top
and
let's
just
go
into
authorize
values
so
under
authorized
values,
there's
a
whole
bunch
of
new
authorized
values
which
are
available
I,
just
filter
those
by
erm.
A
You
can
see
that
there's
quite
a
lot
of
erm
settings
there,
so
these
really
are
used
wherever
there's
a
drop
down
list
in
the
electronic
resources
module.
So
in
common
with
everything
else
in
Co
really,
so
they
cover
things
like
the
status
of
an
agreement
licensed
locations,
closure,
regions,
I
think
they're,
they're
fairly
sort
of
self-explanatory,
really
renewal
priorities.
A
So
you
can
add
and
remove
to
these
so
we're
delivering
a
set
of
sensible
defaults,
but
you
can
add
and
remove
to
those
and
the
other
benefit
of
the
match
is
you
can
use
them
in
reporting
as
well
of
course,
and
then?
Finally,
there
is
a
link
in
the
menu
option
for
the
electronic
resources
module.
So
let's
go
there
now.
A
So
on
the
electronic
resources
home
page
you've
got
this
sort
of
left-hand
menu
and
you'll
notice
as
I
move
around.
It
highlights
the
place
that
we're
at
so
it
it's
probably
difficult
for
you
to
see
on
the
projection,
but
as
we
actually
move
into
different
parts
of
it,
it
bolds
the
link.
So
you
can
sort
of
tell
where
you
are
on
the
hierarchy.
A
We've
also
got
this
sort
of
omni
box
at
the
top
in
common
with
the
rest
of
koha.
So
on
the
home
page
you
can
search
agreements,
you
can
search
packages,
you
can
search
titles,
so
we
can
do
a
quick
sort
of
quick
search
really.
A
Importantly,
agreements
and
licenses
so
really
just
to
explain
agreements
really
describe
what
you
can
access,
whereas
license
describe
what
you
can
do
with
that
license
with
that
material.
So
that's
really
the
sort
of
distinction
between
the
two.
A
And
the
first
thing
to
say
is:
we've
got
the
table
settings
here,
so
this
is.
This
is
from
that
that
table
settings
page
I
showed
you
just
now.
A
We've
also
got
the
you
know
various
standards
sort
of
search
same
as
you
would
see
on
any
other
page,
but
we've
also
got
these
filters
in
the
data
table
here.
So,
for
example,
if
we
want
to
let's
just
quickly
look
at
our
canceled
material
or
cancel
subscriptions,
we
can
filter
really
nice
and
easily
on
there.
A
This
table
box
as
well,
has
got
this
special
feed
filter
at
the
top
here,
and
the
reason
we've
got
this
here
is
it's
really
I,
don't
know
whether
you
know
on
these
print
sub
serial
subscription
page
there's
a
link
on
the
left
hand,
side,
which
is
I,
think
it's
called
expired
subscriptions
or
expiring
subscriptions
or
something.
This
is
effectively
doing
the
same
thing.
A
So
it
allows
you
to
filter
this
potentially
long
list
of
agreements
and
see
which
agreements
perhaps
have
already
expired
or
which
perhaps
are
coming
up
for
expiration,
so
so
that
you
know
what
you
have
to
deal
with
in
terms
of
renewing
a
subscription,
so
I
can
just
perhaps
go
back
to
the
end
of
oops
end
of.
A
A
Just
filter
there
and
then
out
of
that
list,
there's
a
couple
of
a
couple
agreements
that
are
actually
coming
up
for
Renewal,
so
we
perhaps
need
to
do
something
about
these
and
and
deal
with
them.
A
Get
back
to
the
full
list
so
on
the
full
list
here,
we've
we've
got
a
an
agreement;
name,
a
description
of
what
it
is.
We've
got
some
edit
buttons
delete
buttons.
So
let's
just
go
and
have
a
look
at
ACM
digital.
First
of
all,
to
start
with.
A
First
thing
to
say:
it's
linked
to
a
vendor
record,
so
obviously
I
can
open
that
in
the
new
tab
and
then
we're
looking
at
my
ACM
digital
vendor.
So
that's
standard
cover
Acquisitions
functionality.
Now
we're
just
linking
linking
the
agreement
record
to
a
vendor
record
I.
Think
there's
a
lot
of
potential
going
forward
to
do
more
in
the
Acquisitions
area.
A
A
And
then
we've
got
some
information
about
the
about
the
status
closure,
room
reasons
and
so
on,
and
then
we've
got
these.
A
These
different
sort
of
periods,
so
you
can
have
an
agreement,
can
will
last
for
a
certain
period,
and
you
can
hear
record
historical
agreement
periods
and
you
can
also
record
forthcoming
subscription
periods,
and
you
can
also
record
the
current
subscription
period.
A
So
you
can
see
on
this
particular
particular
one
we've
actually
got
the
current
subscription
period
you
can
see
is
here
in
the
current
year
and
what
we're
planning
to
do
I
think
that's
is
on
the
to-do
list.
Is
we
will
we're
actually
going
to
highlight
the
the
current
period
to
make
it
very
obvious?
That
is
the
current
period
based
on
on
the
calendar
date,
the
time
that
you're
looking
at
it.
A
Agreement
users,
so
agreement
users
are
really
a
member
of
Library
staff
who
has
some
sort
of
relationship
with
this
record,
and
so,
as
I
said
in
in
the
workflow
context,
it
may
be
the
library
directory.
It
may
be
the
arm
librarian.
It
may
be
a
subject
librarian,
so
you
can
add
multiple
users
to
an
ERM
record.
A
But
it's
important
to
say
actually
one
thing
I
forgot
to
say
when
I
was
sort
of
showing
you
the
administration
side.
If
I
just
go
back
up
the
top
here
and
go
to
patrons.
A
There's
actually
a
new
a
new
permission,
we're
going
to
permissions.
A
You
can
see
at
the
very
bottom
there's
permission
to
manage
electronic
resources
module.
This
permission
will
probably
become
a
set
of
permissions
and
become
more
granular
again,
that's
on
the
to-do
list,
so
that
we
can
perhaps
allow
access
just
to
view
agreements
rather
than
edit
agreements
delete
agreements
and
so
on.
A
But
in
the
context
of
that
agreement
record
any
staff
member
that
you
link
to
an
agreement
must
have
a
must.
Have
that
permission
in
order
to
be
linked.
A
So
that's
important
and
partly
the
reason
for
that
is
when
you're
actually
doing
that
linking
you,
you
don't
want.
You
know
you
don't
want
30
000
paid
from
records
popping
up
in
your
as
you're
trying
to
filter
these
things.
That's
that's
one
of
the
reasons
behind
it
at
the
bottom.
There
we've
got
licenses,
so
an
agreement
is
typically
linked
to
a
license,
but
the
way
this
is
actually
sort
of
designed
is
you
can
use
agreements
independently.
A
But
if
you're,
if
you're
sort
of
using
the
full
thing,
you
can
link
these
together
and
I'll
move
on
to
licenses
in
just
in
just
a
moment
and
then
finally,
at
the
bottom,
you've
got
documents
so
documents
in
the
context
of
Agreements
are
slightly
different
to
documents
in
the
context
of
licenses.
So
in
a
license
you
would
perhaps
expect
to
see
the
license.
Agreement
itself
may
be
signed
no
signed
license
agreement,
whereas
in
the
agreement
record
you
would
perhaps
expect
to
see
correspondence
between
you
and
the
vendor.
A
A
Journal
archives,
so
a
different
agreement,
but
you
can
see
it's
similar
and
the
reason
I'm
going
to
mention
Journal
archives
is
at
the
bottom.
You
can
see
that
it's
a
related
agreement,
so
this
agreement
is
actually
linked
to
just
trans
the
just
transitional
agreement.
So
that
means
that
the
agreements
have
some
sort
of
relationship
with
each
other
and
that's
a
two-way
relationship
and
there's
some
sort
of
relationship
reasons,
and
why
why
these
are
linked
together
and
you
can
link
both
ways.
A
So,
if
I,
just
click
on
this
link,
I've
jumped
into
the
just
Transit
transitional
agreement
and
as
you
can
see
at
the
bottom,
it's
now
directing
me
back
again
to
that
and
on
this
page
we
can
see
that
the
Journal
archives
is
superseded
by
just
traditional
agreements
and
on
the
journal,
icons
page.
We
can
see
that
the
just
transition
agreement
supersedes
this
agreement,
so
you
can
build
this.
These
two-way
relationships,
which
is,
is
quite
nice
and
you
have
these
relationship
reasons
which
sort
of
build
that
link
together.
A
So
this
is
actually
stored
in
a
table
called
ERM
agreement,
relationships.
I,
think
so
that's
that's.
Where
those
sort
of
are
held.
A
A
So
typically,
when
you
sign
an
agreement
with
a
vendor,
they
will
often
cover
you
know
multiple
different
packages,
I'll
just
linked
to
here
or
may
just
be
a
single
package.
But
here
this
is
where
you
can
see
exactly
what
is
actually
covered
by
this
agreement,
and
you
can
see
these
also
hypertext
links
through
to
the
packages
themselves.
So
I'll
move
on
to
packages
in
just
a
minute,
and
you
can
actually
have
a
look
at
look
at
that:
okay,
I'm,
just
going
to
go
back
to
the
agreements
home
page
again,.
A
A
I
can
link
into
a
vendor,
so
you
can
see.
I've
got
a
drop
down
list
of
my
vendor
records
here
and
I'm,
going
to
link
it
to
Oxford
University
press
I
can
just
add
a
bit
more
descriptive.
A
So
we'll
make
this
active,
you'll
notice,
the
closure
reason
box
is
grayed
out
at
the
moment.
I
can't
actually
type
into
it,
and
the
reason
for
that
is
because
it's
active,
so
it
kind
of
makes
sense.
But
Mark
that
is
closed.
You'll
see
that
that
box
is
now
available.
I
can
actually
specify
a
closure
reason,
but
for
the
time
being,
I'm
just
going
to
make
it
active.
A
It's
a
Perpetual
agreement,
another
drop
down
field.
What's
the
priority,
we're
definitely
going
to
renew
this
one
because
we
love
it.
We
can
specify
a
bit
of
license
information
in
here
and
that's
really
in
case.
You
do
want
to
use
agreements
without
the
licenses,
so
you
can
put
basic
sort
of
license
information
here
or
notes
and
then
we
can
add
license
periods.
So,
as
you
saw
you
know
earlier
on,
you
can
have
multiple
periods,
so
I
can
add
multiple
periods
to
this
so
I'm
going
to
add
one
for
the
start
date.
A
We
can
specify
cancellation
deadline
date
so
again
that
allows
you
to
report
on
these.
So
you
can
say
this
is
up
an
upcoming
subscription.
So
I
probably
want
to
know
about
this
roundabout
August
2023
note
field.
A
We
can
then
add
ERM
users.
So,
as
I
said,
this
is
anybody.
Who's
got
a
relationship
with
this
agreement,
so
I'm
going
to
select
a
user
and
in
this
list
here
I'm
not
going
to
see
Patron
records
from
my
whole
Patron
database
I'm
only
going
to
see
users
with
that
staff
permission.
So
that's
me
and
Alice,
so
I'm
going
to
select
myself
and
my
role
is.
A
Then
we
can
add
a
license
to
this
agreement,
so
the
license
has
to
be
pre-created
in
the
licenses
area.
So
this
is
one
of
actually
have
actually
prepared
earlier.
So
I've
created
an
an
oup
Oxford
academic
law
license
records,
so
I
can
attach
that.
So
that's
how
we
build
the
two-way
relationship
there
and
again
give
it
a
status.
This
is
the
controlling
license.
A
Physical
location
is
quite
useful
because
you
know
if
there
is
actually
a
physical
paper
copy
of
that
and
somebody's
stuffed
it
under
a
desk
or
in
a
Cupboard,
or
something
like
that.
You
can
actually
specify
where
it
is.
So
you
know
where
to
go
and
actually
look
for
the
thing
we
can
put
notes.
If
the
agreement's
available
online
or
maybe
parts
of
it
or
information
related
to
the
agreement,
you
can
link
out
to
it
by
your
URI
as
well.
A
And
here
is
where
you
can
have
the
related
agreement,
so
this
is
where
you
can
link
one
relation
agreement
to
the
other.
So
where
I
showed
you,
those
agreements,
one
supersedes
the
other,
so
I
won't
actually
link
one
together,
but
you
this
is
basically
how
it
works,
specify
the
agreement
you're
linking
to
and
then
the
sort
of
purpose
of
the
link.
A
B
A
So
license
records,
as
I
mentioned,
that
describes
what
you
can
do
with
the
material.
So
it's
worth
also
saying
that
this
is.
This
is
a
sort
of
work
in
progress.
This
is
really
where
we
got
up
to
before.
Jonathan
went
off
on
his
paternity
leave,
so
there's
still
work
to
be
done
here,
but
we
just
perhaps
have
a
look
at
again.
A
The
ACM
digital
license
again,
there's
a
link
to
a
vendor
and
the
reason
there's
a
link
to
the
vendor
here
is
that
again,
if
you
want
to
use
licenses
separate
from
agreements,
you
can
do
so
so
again.
It's
just
hypertext
link,
you've
got
agreement,
starts
dates,
ends,
dates
and
so
on
and
if
I
just
go
back
to
the
licenses
home
page
I'm
just
going
to
create
a
new
license
here,
show
you
again
the
fields
available
so
license
name
a
link
back
to
the
vendor
description,
the
type
of
license.
A
So
again,
these
two
would
build
with
the
drop
down
they'd
come
from
those
authorized
values
and
then
a
start
date
and
an
end
date
after
the
agreement
and
then
importantly,
the
final
field,
which
is
missing
here,
is
the
link
to
upload
the
document.
So
so,
if
somebody
fancies
adding
that
before
Jonathan
gets
back
from
us
potentially
if
we
ever
serve
as
a
grateful,
so
that's
that's
where
that's
going
to
go
at
the
bottom
there.
A
So
that's
the
license.
It's
a
fairly
simple
record!
So,
let's,
let's
move
over
to
the
E
Holdings
area.
So
as
I
mentioned
e
Holdings
really
describes
the
resource
record
itself,
not
not
the
title
itself
and
you
can
see
that
I've
got
ebsco
with
packages
and
titles
and
I've
got
local
packages
and
titles.
A
And
from
that
drop
down
box,
I'm
just
going
to
deselect
ebscope
just
for
just
for
the
moment,
save
that
oh
battery
resources
and
oops
they're
about
to
be
resources
and
refresh
the
screen
and
you
can
see
episode
have
gone.
So
if
perhaps
you
don't
have
a
if
you
don't
have
a
subscription
with
ebsco,
but
you
actually
do
want
to
record
just
information
about
a
few
local
titles,
local
history,
titles
and
things
that
you
perhaps
want
to
record.
A
Then
you
can
use
this
independent
of
actually
having
a
subscription,
but
for
now
I
need
to
put
it
back
on.
Just
show
you
what's
going
on
here:
okay,
let's
look
first
of
all
at
ebsco,
then
so,
as
I
mentioned,
it's
linked
to
ebsco's
knowledge,
Base,
fire,
Holdings,
IQ
and
holdings
IQ
can
be
used
in
all
sorts
of
different
ways.
So,
if
you
are
familiar
with
coral,
Coral
actually
integrates
with
Holdings
the
ebsco
knowledge
base,
and
that
uses
also
uses
the
Holdings
IQ.
A
So
I
guess
what
I'm
saying
is:
there's
potentially
various
ways
you
can
manage
your
ebsco
Holdings.
You
could
actually
be
going
to
EDS
admin
and
managing
it
through
there.
You
could
be
managing
it
through
Coral,
you
could
be
managing
it
through
COA.
The
end
result
is
that
ebsco's
knowledge
base
is
the
master
and
whatever
you
change
will
be
updated
there
in
the
master
sort
of
place.
If
you
like.
A
And,
and
the
way
this
has
been
implemented
is
really
COA
is
acting
as
a
as
a
proxy
almost
for
that
knowledge
base.
So
we
haven't
got,
as
you
know,
probably
know.
Ebsco's
knowledge
base
is
literally,
you
know
millions
and
millions
of
Records.
We
don't
want
to
start
store,
start
storing
sort
of
13
million
resource
records
in
the
code
database
and
fill
your
disk
with
information
you're
not
really
interested
in
so
we're
sort
of
using
Cairo
as
a
proxy
to
view
take
a
view
of
that
knowledge
base.
A
So
the
data
I'm
going
to
show
you
now
is
not
stored
in
color.
It's
a
view
of.
What's
in
the
knowledge
base,.
A
So,
let's
just
have
a
look
at
titles.
First
of
all
and
I'm
going
to
search
for
a
title.
A
And
you
can
see,
we've
got
some
filters
and
these
these
filters
relate
to
filters
that
are
available
in
in
through
the
ebsco
API,
so
the
publication
type
and
the
select
selection
status
so,
whether
you've
already
selected
it
perhaps
an
EDS
admin.
A
A
A
And
again
we
can
filter
it.
So
perhaps
if
we
want
to
narrow
it
down
to
just
the
selected
ones,
we
can
we
can
do
that.
A
You
can
see.
Well,
hopefully
you
can
just
about
screen.
There's
a
little
check
check
mark
there
and
there's
one
down
there.
So
that
means
it's
already
selected,
so
you've
selected
you've
subscribed
to
that
journal
through
through
ebsco.
So
we
can
see
very
clearly
what
what
is
part
of
our
Holdings
at
the
moment
and
what
isn't
part
of
our
Holdings
foreign.
A
A
A
So
that's
what
I
would
expect,
because
ebsco's
knowledge
base
is,
is
the
master
now
I'm
just
going
to
go
and
view
this
record
in
full,
it's
tetrahedon
title
and
on
the
full
view
of
the
record,
what
we'll
be
able
to
see
is
the
metadata
itself
about
the
record,
so
we
can
see
that
it's
issn,
it's
eiss
SN,
who
the
publisher
is
the
publication
type
and
so
on,
but
we
can
also
see
at
the
bottom
there
which
packages
it's
available
in
so
as
I
said,
a
title
can
belong
to
multiple
in
multiple
packages.
A
So
that's
why
you
have
resource
instances
of
a
title,
and
you
can
see
this
particular
one
is
actually
in
87
different
87
different
packages
and
again,
we've
got
this
really
nice
filter
button
here.
So
we
can
just
say
well,
which
actually
are
those
packages
are
packages
are
actually
subscribed
to.
So
we
can
see
that
we
get
this
title
through
science
Direct.
That's
that's
the
package
that
we're
subscribing
to
now
at
the
top
here.
We've
also
go
back
to
the.
A
A
We
can
see
it's
part
of
science
direct
from
elsevier.
We
can
see
what
the
coverage
that
this
the
elsevier
provide
and
importantly
at
the
top
we
can
see
we
can
remove
this
title
from
our
Holdings.
So
if
we
no
longer
subscribe
to
it-
and
this
is
an
individual
title
and
not
the
package
itself-
we
can
remove
this
title
from
our
Holdings
and
I'll.
Just
take
a
second.
Whilst
it
updates
the
master
knowledge
base
at
ebsco.
A
And
that's
gone
now
in
theory.
If
I
go
here
and
perform
that
search
again,
we
should
see
it's
deselected
in
here
as
well,
because
it's
exactly
the
same
view
of
the
knowledge
base
and
there
it
is
tetrahedron
current
status.
Well,
it's
unselected
and
if
I
perhaps
just
go
and
add
this
title
back
in
again,.
A
A
Let's
go
back
to
let's
go
back
to
cover;
let's
just
go
back
to
the
titles
and
this
time
I'm
going
to
search
for
Irish
history.
A
Now
the
692
entries
from
ebsco,
but
you
can
see
here
at
the
top
there's
one
local
title.
So
this
is
something
that's
in
our
local
knowledge
base.
So
it's
not
something
that
we
can
subscribe
to
from
ebsco
ebsco
directly,
but
it
is
in
our
Holdings,
so
it
lives
actually
somewhere
down
here.
It's
one
we've
created!
So
that's
the
nice
thing
about
when
you're
searching
doing
the
searching
here
you
can
search
across
both
electronic
Holdings
and
your
local
Holdings.
A
Hopefully,
you
can
see,
on
the
left
hand,
menu
it's
bolded,
the
the
titles
under
local
packages
there
just
to
make
it
clear
where
you
are
in
the
navigation
and
if
I
click
through
to
that,
we
can
actually
see
see
that
title
there
and
we
can
see
that's
part
of
a
local
package
called
called
British
history
that
we
subscribe
to
and
I'm
just
going
to
edit
this
and
just
to
show
you
the
metadata.
A
So
when
we
edit
a
local
title,
we've
got
a
whole
list
of
metadata
and
this
metadata
is
all
based
on
K
Bar
format,
which
you
may
be
feeling
familiar
with
K
bar
too.
So
again,
it's
sort
of
like
a
de
facto
International
standard
for
this
type
of
metadata,
so
the
beauty
of
that
is
means
potentially
in
the
future.
We
can
export
and
import
data
in
in
that
type
of
format,
and
you
can
see
at
the
bottom
here.
A
Here's
the
option
where
we
can
add
this
title
to
a
local
package,
so
not
an
ebsco
package
to
a
local
package.
A
C
A
And
again
you
can
see
there's
a
lot.
Sorry
titles
I'm
meant
to
look
for
packages.
A
So
again
now
we're
searching
packages
rather
than
the
individual
titles
themselves,
so
so
packages
typically
have
names
and
again,
we've
got
these
filters
here
which
are
ebsco
filters,
but
I'm
just
going
to
search
for
that,
and
you
can
see
there's
a
lot
a
lot
of
packages
with
with
that
particular
string
in
the
title.
So
again,
I
can
use
the
Builders
here
to
perhaps
just
narrow
it
down
to
package
that
I've
selected
that
I've
actually
subscribed
to.
So
you
can
see
this
from
that
big
list.
There's
actually
four
there.
A
And
what
you
can
see
here
is
information.
That's
come
back
from
ebsco
about
the
package
itself,
who
the
vendor
is
the
package
type,
but
we
can
also
see
what
actually
is
contained
within
that
package
package.
So
you
can
see
there's
877
titles
within
the
package
itself.
A
So
that's
obviously
quite
a
lot
quite
a
lot
of
electronic
subscriptions
there.
So
that's
why
we've
got
this
filter
option
here,
because
we
can
actually
filter
it
down
to
individual
titles.
So
we
can
search
for
individual
titles
within
that
package
which
again
filtered
by
subscriptions
type,
and
then
we
can
also
filter
by
status
as
well.
A
So
I
know
that
I've
got
a
lot
of
titles
out
in
that
package,
but
what
I
want
to
know
is
actually
which
pack
which
titles
aren't
selected
so
I
can
filter
down
to
the
ones
not
selected
out
of
that
package
and
that
narrows
it
down
to
just
fall.
So
maybe
I
could
just
perhaps
go
and
have
a
look
at
one
of
those,
and
what
you
can
see
now
is
I
can
perhaps
add
that
title
back
into
my
Holdings.
If
I
want
to
do
that.
A
A
A
couple
of
other
things
to
notice
on
on
this
particular
screen.
You've
got
another
button
up
here
to
add
and
remove
to
to
negotiate
the
the
ebsco
knowledge
base
in
this
case,
because
we're
on
a
package
and
not
a
title,
it's
an
ad
remove
package
button.
So,
if
I
remove
the
package,
it's
going
to
remove
all
877
of
those
titles
for
my
subscription.
A
The
other
thing
you
can
see
here
is
I'm
got
a
link
through
to
the
agreement
records,
so
this
package
has
been
linked
to
an
agreement.
So
if
I
just
open
that
in
a
new
tab,
there's
the
agreement
record-
and
this
is
the
one
we
were
looking
at
earlier
on
packages
that
we
included
in
this
agreement-.
A
So
that's
nice
to
be
able
to
see
exactly
what's
linked
if
we
try
and
add
it
to
a
new
agreement.
We'll
have
a
list
of
the
agreements
that
are
currently
on
the
system
and
we've
got
a
nice
thing
here.
If
we
just
try
and
Link
it
to
same
agreement
again
just
got
a
little
warning
dialogue
there
that
it's
already
linked.
So
that's
just
quite
useful.
A
Okay
I'm
just
going
to
go
across
the
local
titles,
now
I'm
going
for
some
running
out
of
time.
So
these
are
all
titles
that
have
been
created
manually
so
by
Library
staff.
So
if
we
perhaps
have
a
look
and
filter
down
to
one
here,.
A
Got
a
couple
of
couple
of
local
titles
here
and
if
I
just
click
through
to
those
you
can
see,
these
are
ones
that
have
been
created
manually
and
the
nice
thing
is
when
you
create
a
local
title
within
COA,
it
automatically
takes
the
metadata
from
that
kbar
template
and
builds
a
catalog
record
for
you
in
the
catalog
module.
So
if
I
just
open
that
link
in
a
new
tab,
you
can
see
that
it's
taking
me
through
to
a
bibliographic
record.
A
A
And
again
here
you
can
see
that
this
title
is
linked
to
a
local
package,
so
you
can
build
your
own
local
packages.
So
again
you
may
work
with
a
local
history
vendor
who
perhaps
provides
one
or
two
different
titles
as
part
of
their
sort
of
roughing
to
you.
So
you
have
the
the
concept
of
these
sort
of
local
and
and
Global
sort
of
packages.
A
If
I
just
go
back
to
titles
and
I
create
a
local
title,
you've
got
all
this
metadata
and,
as
I
said,
this
is
Kmart
metadata.
So
that's
that's
why
it's
sort
of
quite
verbose
and
detailed,
but
it
does
sort
of
match
the
Kmart
format
and
at
the
bottom
there
you
can
see
that
I
can
add
it
to
a
local
package
and
then
one
other
nice
thing
under
local
titles.
Is
this
import
from
list?
So,
if
you've
imported,
perhaps
a
load
of
records
from
a
vendor
they've?
A
B
A
Oh
I,
don't
think
I
have
actually
sorry
but
yeah.
What
what
you
see
would
see
here
is
all
the
lists
that
are
created
through
the
list:
module
and
there's
a
just
a
button.
You
can
press
and
it
just
adds
them
all
right
into
your
Holdings,
which
is
quite
a
useful
little
feature
there.
A
Okay,
so
that's
that's
really
where
we
are
right
now,
so
just
really
to
finish
off.
A
And
talk
about
what
happens
next,
so
we
want
to
carry
on
there's
a
lot
we
want
to
carry
on
doing
with
this
I
know,
there's
a
lot
of
scope
to
add
more
stuff
to
it,
so
funding
always
helps,
although
actually
at
the
moment,
that's
not
the
biggest
problem.
We've
we've
got
a
lot
of
people
interested
in
ERM
a
lot
of
people
willing
to
contribute
to
it.
So
that's
not
particularly
an
issue.
The
bigger
issue
really
is
is
hands
to
more
people
to
get
involved
in
it.
A
So
there's
two
ways
you
can
really
get
involved
in
it
go
and
have
a
look
at
that
sandbox,
it's
on
the
biblibra
sandbox
page,
look
at
it
feel
free
to
mess
with
my
data,
all
the
test
data
I
put
on
there
feel
free
to
create
new
records,
but,
most
importantly,
we
need
eyes
on
the
code
on
this
code,
so
we
really
want
to
get
a
minimal,
minimal,
viable
product
into
2211
and
I.
A
Think
Thomas
is
happy
to
do
that
because
it's
a
very
Standalone
piece
of
work
and
it
doesn't
impact
on
anything
else
in
covers.
So
it's
it's
low
risk
if
you
like,
but
he
does
want
eyes
over
the
code
to
ensure
that
it's
been
looked
at
by
more
than
one
person
more
than
Jonathan
Jonathan's
created
a
great
wiki
page
and
we'll
show
you
the
links
for
these.
But
this
Wiki
page
explains
here.
A
Why
we're
doing
this?
What
it
is,
there's
a
lot
of
technical
information
in
here,
so
there's
links,
sort
of
links
to
all
the
apis
that
he's
built
to
make
this
work
so
at
end
points
to
manage
the
agreements
to
licenses
those
knowledge
bases.
It
explains
all
about
the
system
preferences.
Those
authorized
values.
I
showed
you.
It
gives
you
the
tables
that
have
been
created
to
make
all
this
happen,
so
the
API
routes,
and
so
it
goes
on
it's
it's
very
detailed.
A
A
D
So
there
was
one
question
that
I
missed,
because
I
thought
somebody
else
was
paying
attention
to
the
I
thought
somebody
else
back.
There
was
paying
attention
to
the
zoom
questions
and
so
I'm
not
sure
what
part
of
the
presentation
it
came
at
and
she
said,
are
these
attached
to
items
similar
to
the
Acquisitions
tab,
I'm
going
to
get
your
email
and
her
email
and
get
you
two
together?
So
she
can
ask
that
specifically,
but
in
the
face
in
the
YouTube
chat,
somebody
said.
D
So
what
would
this
look
like
on
the
patron
end
and
they
want
to
know
if
you
could
send
a
link
to
the
sandbox?
Can
people
look
at
the
sandbox
online
and
well
we'll
make
sure
we'll
get
that
link,
and
so
what
would
it
look
like
on
the
patron
end?
I
guess
is
her
question
right
now.
A
Okay,
the
sandbox
link
is
in
the
slides,
so
you
it'll
be
there.
You
can
go
and
have
a
look
at
that.
It's
on
the
bib
Libra
sandboxes
page.
If,
if
you
want
to
go
and
look
at
it
there
as
well,
what
does
it
look
like
in
the
online
catalog?
Well,
typically,
if
you're,
using
if
you're
using
ebsco's
knowledge
base,
what
it's
doing
is
controlling
what
appears
in
ebsco
Discovery
service.
A
So
if
that's
your
just
sort
of
front
end,
then
as
I'm
adding
and
removing
journals,
they
will
appear
and
remove
automatically
from
ebsco
Discovery
service,
which
is
a
great
you
know
great
feature:
local
Holdings.
The
plan
is
that
well
it's
there
now,
as
you
as
I
said.
As
you
create
a
local
title,
it
will
automatically
create
a
bibliographic
record
which
you
can
choose
to
display
or
not
to
display
in
the
online
catalog,
give
it
an
item
type
of
ebook
and
so
on.
A
A
So
yeah
that's
also
there,
this
wiki
page
and
the
kanban
board,
which
is
associated
with
it,
will
also
share,
and
if
you
do
want
to
get
involved
in
actually
doing
development
work,
then
great,
because
there's
a
list
in
that
left
hand
column
of
new
features
that
we
want
to
add
and
Jonathan's
very
kindly
Mark
Summers
sort
of
developer
warm-up
features.
A
So
if
there's
something
you
just
want
to
get
in
quickly
into
it
quickly
and
just
write
a
simple
bit
of
code,
there's
some
small
features
which
will
just
get
you
going
getting
using
the
view
JS
and
so
on.
There's
another
question:
there.
E
My
colleague
we
I
work
in
a
special
Library
I
work
in
a
law,
firm
library
and
I
feel
like
one
or
both
of
those
questions
that
came
through
could
easily
have
come
from
my
colleague
who's
watching
this
online
and
we
we
were
very
excited
about
this
module
like
we're.
Really.
We
have
hopes
and
dreams
for
this
and
I
now
I'm
thinking,
maybe
some
of
those
things
are
pretty
far
outside
the
scope
of
what
this
is
intended
to
do,
but
not
only
for
it
to
just
do
all
this.
E
But
the
question
about
to
appear
in
a
tab
like
Acquisitions,
and
how
does
it
look
on
the
patron
end?
I
say
you
could
you're
looking
at
the
resource
and
it
says
what
the
license
model
is.
Since
we
work
in
a
special
Library,
we
don't
have
a
lot
of
firm
wide
resources.
We
might
have
something
where
say
we
subscribe
to
this
database.
We
get
50
seats,
and
so
excuse
me,
so
we
were
hoping
that
we
could
open
that
resource.
E
E
45
of
them
are
occupied
great
now
we
know
we
have
five
seats
available
and
so
there's
that
aspect
to
it
and
then
say:
if
you
had
the
patrons
all
signed
up
now,
when
you
look
at
something
in
staffco
and
there's
the
Acquisitions
Tab
and
you
can
see
the
invoices
that
would
have
been
paid,
we're
hoping
there'd,
be
a
users
tab,
not
users
in
the
sense
that
you
were
saying,
but
you
could
see.
E
Oh
here's,
the
tab
that
shows
everybody
that
has
a
seat
to
it
and
for
us,
when
someone
leaves
our
firm,
we
have
a
process
where
we
go
into
their
office
if
they
use
Co-op,
we
look
in
their
patreon
record.
If
they
have
things
checked
out.
If
they
have
ills,
if
they're
on
the
routing
for
things,
we
try
to
get
that
stuff
back
before
they
quit
and
run
away
with
it,
and
also
if
it
listed
the
things
they
had
a
seat
to.
E
We
could
one
know
that
now
that
seat
was
available
and
also
we
could
shut
it
down
when
they
leave,
so
they
can't
continue
to
access
it
after
they're
gone.
So
that's
our
I
think
I
wanted
to
really
get
a
chance
to
say
that,
because
I
feel
like
I'm
there's,
not
a
lot
of
special
Librarians
here.
So
I
wanted
to
provide
our
our
perspective
on
what
we're
kind
of
hoping
for.
A
Yeah
so
good,
that's
a
good
question
actually
because
that's
not
in
the
scope
of
what
we're
doing
at
the
moment,
but
actually
you're
the
second
person
that
said
that
to
me
that
requirement
so
so
we'll
either
add
it
to
the
kanban
board
or
we'll
add
it
to
the
specification.
We've
got.
I
know
that
there
are
libraries
that
work
in
in
that
way.
Yeah
so
yeah.
Take
that
into
consideration
any
other.
F
I
I
wanted
to
follow
up
on
the
question
earlier
about
whether
these
will
populate
and
it
should
write
these
will
populate
in
the
catalog
as
titles
these
the
packages
and
titles.
So
if
we're
using
EDS
and
we
bring
in
the
whole
knowledge
base
and
they're,
not
exactly
the
same,
we're
going
to
get
a
lot
of
duplicate
titles
of
the
same
thing,
which
and
or
ideally
we
would
want
these
to
hook
up
with
the
titles
we
have
it
in
koha
right
so.
F
Going
to
be
some
problems
with
populating
it
with
our
EDS
Holdings,
we
have
massive
EDS
Holdings
and
a
lot
of
those
are
in
koha.
A
lot
of
them
aren't.
B
C
A
Yeah,
the
idea
for
pricing
is
that
we're
going
to
link
that
to
the
Acquisitions
module
so
that
you'll
be
able
to
create
orders
and
invoices
in
the
same
way
that
you
can
for
physical
material,
which
will
be
great
again,
it's
not
on
the
November
sort
of
deadline,
mainly
because
we
don't
want
to
break
anything,
that's
already
there
at
the
minute.
We
want
to
get
this
in
working,
but
that
is
very
much
on
the
to-do
list:
yeah
yeah
and
the
ability
to
look
at
a
license
from
the
vendor
or
the
agreement
from
the
vendor.
G
So
I
do
like
the
fact
that
it
is
you
guys,
are
looking
forward
to
linking
to
the
Acquisitions.
In
that
sense,
you
can
have
the
contract
renewal
terms
automatically
fill
in
and
populate
a
little
bit
quicker
than
just
the
Holdings
with
the
API,
so
that's
kind
of
nice
and
then
obviously
it
goes
to
the
master.
So
if
you're
using
Aspen
EDS,
it
automatically
just
built
this
over
correctly.
If
you
uncheck
something
and
check
it
back.
B
A
Yeah
so
Aspen,
if
Aspen's
integrated
with
ebsco
same
deal,
because
Aspen
also
uses
the
what
it
uses:
the
ebsco
API
to
the
Eds,
which
is
updated
from
the
Holdings
IQ.
If
you
see
what
I
mean,
okay,
any
fun,
I
know
we're
running
a
little
bit
over
sorry.
So
right,
okay,.
D
Comments
I
think
on
YouTube.
So
a
couple
of
last
comments
from
YouTube
somebody
said:
I,
don't
want
to
say
her
name,
because
I
don't
want
to
insult
her
by
mispronouncing.
It
which
I'm
guaranteed
to
do
I
would
love
if
this
push
license
terms
to
patrons
out
into
the
OPAC
and
then
Neve
and
then
recording
who
a
license
is
allocated
to
would
also
be
useful
and
then
Dwight
says.
D
Dwight
says
that's
transaction
and
software
licensing
billing
I'm,
not
sure
what
that
comment
means
could
be
just
as
ebsco
Holdings
IQ
Services
used
to
embed
Holdings.
Can
the
upskill
link
IQ
service?
D
A
Link
IQ,
we
haven't
looked
to
that
yet
we've
actually
looked
at
the
publication,
find
the
API
in
terms
of
doing
a
to
z,
Journal
listings,
but
yeah
they've
got
a
few
AP
apis,
that's
one!
We
haven't
looked
at
going
back
to
the
terms
tool.
That's
definitely
something
we
want
to
that
is
on
the
list
already.
That's
something
we
want
to
look
at.
I
think
I'd
be
surprised
if
we
get
into
the
November
now,
just
because
of
time,
but
definitely
on
the
on
the
to-do
list.