►
From YouTube: Open Source Software as Free Culture
Description
Presenters:
- Andrew Preater (University of West London)
- Tundun Folami (University of West London)
A
A
A
A
So
thinking
about
our
values
and
principles,
we
would
argue
and
in
the
political
aspects
as
well,
there
is
huge
overlap
between
free
software
and
Open
Access
within
the
domain
of
software.
Free
software
represents
a
free
cultural
work
in
the
domain
of
Higher,
Education
and
Research,
and
scholarship
OA
is
the
equivalent
Open
Access
is
the
equivalent
free
cultural
work
and
we
use
we're
using
here
the
definition
from
the
freedom
defined
Wiki.
This
is
referenced
by
Creative
Commons
among
servers
and
it's
quite
similar
definition
really
to
the
gnu
projects
for
freedoms
for
software.
A
A
We
consider
that
this
licensing
means
that
OA
and
free
software
are
part
of
a
larger
knowledge,
Commons,
that's
to
say
that
they
are
a
cultural
resource
available,
in
theory
at
least
to
all
in
society.
Library
workers,
I'm
sure,
like
many
of
us
in
the
room.
This
room
Advocate
would
practically
facilitate
open
access
in
our
work
in
research
support
in
scholarly
Communications,
and
we
are
enthusiastic
to
the
point
of
sometimes
being
dismissed
as
cheerleaders
for
OA
by
those
critical
of
Open
Access
movement.
A
Obviously,
free
software
dates
back
quite
a
long
time,
so
so
the
80s,
where
it
was
born
in
higher
education,
but
long
experience
shows
there's
a
relative
reticence
really
towards
free
software
in
in
our
libraries,
there's
a
lack
of
bold
action
in
this
space
in
our
libraries
and
obviously
I
leave
aside
friends
and
colleagues
in
this
room
who
have
implemented
koha,
but
certainly
it's
something
where
we
see
quite
a
lot
of
interesting
perceptions,
so
I
just
want
to
alight
on
some
of
those
perceptions.
Here.
A
These
are
some
narrative
comments
from
Marshall,
breeding's
library,
perception
survey,
2022,
Edition
and
Marshall
asked
specifically
about
attitudes.
The
free
software
actually
I
think
the
survey
terms
are
open
source,
but
you
know
I
mean
free
software.
It's
fascinating
the
stuff
that
comes
through
here,
a
rare
example
really
of
a
situation
where
you
should
read
the
comments
and
the
key
beliefs.
Really
they
tend
to
be
themed
in
three
or
four
different
areas.
A
Every
year
in
the
perception
survey,
they
haven't
really
changed
since
my
first
job
when
I
worked
in
higher
education
as
an
I.T
technician
in
2004,
I've
heard
the
same
things
year
in
year
out,
to
be
honest,
they're
pretty
stable,
even
as
Cloud
hosting
and
infrastructure
as
a
service,
and
nowadays
anything
as
a
service
really
has
become
more
and
more
dominant.
These
perceptions
stay
with
us
and
we
want
to
subvert
some
of
these
Perceptions
in
talking
about
free
software.
A
So
we
advocated
for
sorry
excuse
me.
We
selected
and
implemented
koha
supported
by
ptfs
Europe
in
2020
during
the
covid-19
pandemic,
and
my
first
point
about
selecting
a
free
software
system
is,
we
did
not
set
out
to
purchase
a
free
software
system
when
we
wrote
a
business
case
for
this
migration
with
the
management
team.
Here
we
focused
on
the
benefits
we
anticipated
in
migrating
and
we
expected
a
free,
Software
System
would
compete
fairly
against
any
other
any
other
system
on
the
market.
A
An
attitude
of
vendor
locking
can
lead
to
complacency
for
certain
suppliers,
a
tendency
for
product
roadmaps
to
be
quite
aspirational
and
not
necessarily
deliver
things
that
we
actually
need
and
are
promised,
and
indeed
hidden
costs,
hidden
costs
for
work.
That
is
out
of
scope
of
the
support
contract
or
for
hidden
costs
when
you're
off-boarding,
but
when
you
do
actually
want
to
leave
that
supplier.
So
those
are
the
key
risks
that
we
seek
seek
to
mitigate
in
going
with
free
software.
Finally,
financials
and
I
know
it's
money,
but
we
can't
avoid
this
element.
A
We
are
a
publicly
funded
University
in
England.
We
have
a
sector
regulator
and
they
expect
we
deliver
value
for
money
to
the
taxpayer
and
to
students
who
pay
fees
so
for
our
regulator.
Aspects
like
private
Equity
shareholders
Dividends
are
not
really
a
key
concern:
they're
interested
in
value
for
money
to
a
taxpayer
in
terms
of
total
cost
of
ownership.
This
is
a
spectacular
number
really
or
contract
value
for
free
software
versus
closed
Source.
We
have
saved
about
79
of
the
cost
of
the
of
the
product
over
the
contract.
A
A
Having
said
that,
I've
got
a
little
gift
for
you
in
the
spirit
of
koher.
Being
a
gift
to
the
community,
doesn't
mean
we
ignored
free
software
or
licensing.
We
actually
asked
about
it
early
on
in
the
procurement
process
and
our
tendering
process
for
a
new
system,
and
this
is
something
you
can
share
with
your
library
friends
about
how
to
include
software
licensing
questions
in
a
in
a
procurement
document.
We've
asked
here.
We
framed
it
in
terms
of
the
benefits
to
the
supplier
themselves,
so
we
asked
our
suppliers
potential
suppliers
on
the
market.
A
A
B
B
Another
positive
is
that
working
through
the
data
extraction
ourselves
will
support,
will
support
from
ptfs
as
opposed
to
having
our
previous
provider.
Do
this
work
allowed
us
to
get
to
know
our
data
really
really
well,
which
would
prove
especially
beneficial
for
me,
going
forward
as
a
systems
librarian
in
our
team
and
the
fact
that
we
were
working
remotely
also
made
it
easier
to
interact
well
with
future
s.
B
B
There
were
also,
however,
some
notable
challenges
that
the
implementation
presented,
so
the
biggest
one
was
that
we
migrated
systems
during
the
national
lockdown
period
of
2020.
So
in
the
UK
this
was
a
complete
lockdown
between
March
and
October
2020
and
on-site
access
to
University
was
only
for
essential
reasons.
B
We
also
experience
delays
from
our
vendors,
and
this
was
obviously
factored
into
the
equation,
but
we
had
to
wait
quite
a
bit
longer
than
expected,
especially
for
our
reading
list
and
Discovery
system
vendors,
even
after
we
went,
live
with
KOA,
but
the
biggest
takeaway.
For
me,
post
implementation
is
just
how
much
control
our
team
has
over
the
new
system.
B
So
even
though
Peter
Fess
Europe
manages
the
system
for
us
on
the
database
level,
we
can
still
make
decisions
as
a
library
and
then
go
into
KOA
into
the
administration,
module
and
adjust
settings
to
improve
our
workflows.
We
also
have
a
more
Hands-On
approach,
more
generally,
for
example,
when
it
comes
to
reporting
on
data
in
COA
and
managing
the
circulation
rules
and
managing
budgets
or
within
that
position
is
not
jaw,
for
example,
and
in
the
next
slide
I
will
discuss
how
using
cover
has
allowed
me
to
continue
to
develop
professionally.
B
So
the
collaborative
nature
of
COA
has
meant
that
I've
been
able
to
find
a
wide
breadth
of
video,
tutorials
and
articles
from
other
users
around
the
world.
To
help
me
understand
the
system
better,
as
we
continue
to
work
to
optimize
it
for
our
institution
and
being
a
part
of
the
co.
Community
has
allowed
me
to
work
with
other
systems
Librarians
in
the
UK
and
The
Wider
Community
abroad,
to
resolve
issues
while
we
use
Goa
and
make
adjustments
in
the
system.
B
B
I
did
a
lot
of
this
before
we
loaded
the
data
into
our
live
system
to
test
how
certain
circulation,
rules
or
system
preferences
would
affect
user
accounts
and
even
after
going
live
with
KOA
playing
around
in
the
test
environment
has
given
has
helped
me
to
come
up
with
ways
to
resolve
issues
that
we've
come
across
as
we
go
through
upgrades
and
continue
to
implement.
New
policies
having
more
control
with
the
system
has
also
enabled
me
to
develop
my
SQL
knowledge
and
allowed
me
to
provide
reports
for
The
Wider,
Library
team.
B
So
with
our
previous
system,
we
would
have
to
raise
tickets
most
of
the
time
in
order
to
get
specific
data
from
the
system
we
wanted.
But
now
I
can
just
go
in
there
and
have
a
play
myself
and,
lastly,
being
the
main
person
looking
after
cover-
and
my
team
has
allowed
me
to
develop
the
skills
needed
to
explain,
complex
or
technical
issues
within
the
system,
in
a
clear
way
to
my
colleagues
in
the
library,
Services
team,
and
this
in
turn
has
forced
me
to
better
understand
more
complex
issues
that
occur
in
the
system.
A
Okay
and
I
think
our
next
slide
is
just
our
references,
because
we
are
Librarians
but
sudo
I
just
wanted
to
reflect.
Actually
on
that
point
you
said
about
how
it's
you
know
how
how
a
lot
of
what
we
do,
as
as
systems
I've,
growns
or
Library
technologies
that
is
actually
is
framed
around
the
idea
of
going
in
and
breaking
something
seeing
what
happens
and
and
learning
the
system
that
way,
but,
of
course,
with
free
software,
there's
I
mean
it's
essentially
an
unlimited,
unlimited
potential.
A
B
Yeah
so
yeah
I
think
that's
probably
been
at
the
beginning.
I
felt
like
a
baptismal
file
almost
when
we
switched
to
Colwell
but
I
think.
Ultimately
that
was
the
best
way
for
me
to
learn
right
just
going
in
there
and
having
a
go
first
and
then
figuring
out
how
to
resolve
issues
so
yeah
that's
been
really
beneficial
for
me.
A
Okay,
so
colleagues,
in
the
room,
this
is
our
final
slide.
We
have
rest
a
bit
of
time
at
the
end
here
for
questions.
There's
our
contact
info.
If
you
would
like
to
get
in
touch
with
us
or
follow
us
over
on
the
Bird
app
I'm,
not
sure
how
questions
are
working
in
this
sort
of
hybrid
environment.
So
are
there
questions
from
the
room.
D
A
B
I
kind
of
gained
just
from
having
to
liaise
with
our
it
team
and
the
library
team
during
the
upgrade,
it
was
quite
a
few
things
I
had
to
like
learn
as
I
was
going
along.
Just
so
I'd
be
able
to
communicate
back
to
the
library
team
at
audience.
This
is
what's
happening.
This
is
where
we're
at
with
the
migration.
At
this
point
so
I
think
yeah.
It
was
a
lot
of
learning.
While
things
were
happening.
Just
so
I'd
be
able
to
let
everybody
else
know
what
exactly
was
going.
A
So
I
suppose
just
to
comment
on
that
from
a
more
strategic
point
of
view
of
my
experiences,
the
my
role
was
just
the
project
sponsor
or
project,
executive
and
I.
Think
one
thing
that
did
surprise
me
actually
was
just
how
quickly
and
efficiently
we
did
this
migration
and
we
did
it
in
such
a.
We
did
really
did
a
really
tight
time
scale.
We
had
to
cut
over
to
our
new
system
at
the
end
of
our
financial
year
for
various
university
Finance
reasons,
and
just
around
the
year
end.
A
So
we
had
a
very
hard
deadline
on
the
31st
of
July
and
we
actually
completed
it
about
a
week
early
week
or
so
early.
So
I
was
really
impressed,
actually
pleasantly
surprised,
I,
think
you'd
say
with
the
efficiency
of
ptfs
Europe
as
a
support
company,
quite
different
from
some
experiences
I've
had
with
software
suppliers
of
closed
source
and
a
very
highly
authentic
approach
to
to
their
work
as
a
system
support
company.
A
E
C
I
can
just
add
to
that
that
you
know
being
in
kohai
is
a
great
experience,
because
you're
more
Hands-On,
with
with
the
system
than
you
would
be
with
the
a
paid
system,
and
so
it's
a
great
experience
and
it
does
get
you
it
does,
give
you
more
knowledge
of
your
system
than
you
would
with
any
other
product,
yeah
all
right
Andrew
to
do.
Thank
you
very
much
for
your
presentation.