►
Description
Presentations session 2: Fedora Software and Community Update: All Aboard for Fedora 6.0 - David Wilcox and Arran Griffith, LYRASIS, Canada; DSpace 7.0 : Coming to a DSpace near you - Tim Donohue, LYRASIS, United States of America; Islandora Community Update: Islandora at Home - Danny Lamb, Islandora Foundation, Canada, and Mark Jordan, Simon Fraser University.
B
A
A
A
All
right,
I
think
we
are
right
at
times.
Sarah,
are
you
ready
to
start
the
recording
as
well?
It
should
now
be
started
super
all
right.
Everyone
welcome
to
our
first
parallel
track
session
in,
in
our
first
full
day
of
open
repositories
in
this
session,
we'll
have
a
kind
of
a
roundup
of
community
updates.
From
from
several
of
our
different
repository
system
developers
we'll
be
hearing
from
fedora
d,
space
and
islandora
in
this
session.
A
Before
we
get
started,
I
want
to
remind
you
of
the
open
repositories
code
of
conduct
and
also
want
to
remind
you
that,
following
this
session
immediately
following
this
session
will
be
having
a
networking
session
using
wonder
you
can
find
information
about
that
session.
Instead,
there
are
also
some
more
detailed
directions
in
the
attendee
guide
in
on
the
or
2021
website,
which
is
linked
from
the
scad
event.
So
please
join
us
for
that
networking
event
following
this
session,
so
with
that
I'll
turn
it
over
to
our
first
set
of
presenters.
C
Thanks
yeah,
can
everyone
see
my
screen?
Okay,
good,
all
right,
perfect!
Thank
you!
So
yeah
hi
everyone.
My
name
is
david
wilcox,
I'm
the
program
leader
for
fedora
at
lyricists
and
joined
by
my
colleague,
aaron
griffith
who's,
the
program
coordinator
and
just
wanted
to
provide
a
brief
update
on
the
fedora
in
terms
of
the
software
and
some
of
the
community
activities
that
are
going
on
as
we
approach
the
release
of
fedora
6.0.
C
So
our
roadmap
for
this
year
is
pretty
simple.
I
mean
top
of
the
roadmap
is
release
fedor
6.0
in
a
few
minutes,
I'll
kind
of
share
the
details
on
where
we
currently
are
with
with
the
release
schedule,
but
then,
along
with
that,
we
really
want
to
release
very
robust
migration,
tooling
and
documentation
to
help
people
using
all
previous
versions
of
the
software
and
in
different
environments,
whether
it's
island
or
in
simvera
or
custom,
to
be
able
to
move
forward
to
the
latest
version.
C
C
So
if
you
haven't
been
following
too
closely
for
fedora
6.0,
there
are
sort
of
some
top
line.
Features
that
we
think
are
pretty
compelling
number
one,
I
think,
is
just
enhancing
the
digital
preservation
support
that
fedor
provides
largely
through
adopting
a
new
standard
called
the
oxford
common
file
layout,
which
I'll
talk
about
in
a
moment.
But
we've
also
done
a
lot
to
improve
the
performance
scale
relative
to
previous
versions
of
the
software.
C
We
have
added
a
built-in
search,
endpoint
I'll,
say
a
little
bit
more
about
that
later.
In
the
presentation.
This
is
primarily
for
developers
and
repository
administrators
to
very
quickly
be
able
to
retrieve
content
in
the
repository,
and,
I
think,
really
importantly,
we've
minimized
changes
to
the
api.
C
So
between
version
four
and
five,
if
you're
upgrading
to
version
six,
there
shouldn't
be
a
lot
of
client
code
changes
required
and
we've
seen
that
already
with
island
aura,
which
has
already
sort
of
made
the
move
to
from
version
5
to
version
6
with
very
little
issues
and
and
we're
hoping
the
same
as
will
be
true
with
other
other
implementers
and
just
finally,
we've
made
migrations
easier,
but
we're
also
anticipating
fewer
migrations
into
the
future.
And
again
this
comes
back
to
this
oxford
common
violate,
which
I
mentioned.
C
I've
given
presentations
on
this
before
and
others
have
as
well.
So
I
won't
say
a
ton
about
it
here,
but
this
is
a
relatively
new
open
standard
approach
to
the
layout
of
preservation:
persistence,
in
other
words,
how
you
lay
out
the
contents
of
your
repository
in
a
sort
of
fairly
simple
file
and
folder
structure,
with
strong
notions
of
versioning
and
fixity.
That's
really
just
in
alignment
with
digital
preservation
best
practices.
C
So
this
is
going
to
allow
us
to
provide
better
services
around
digital
preservation,
but
also
because
this
is
a
standard
that
fedora
is
committing
to
future
versions
of
the
software
won't
require
sort
of
massive
data
migrations
because
they'll
continue
to
comply
with
the
way
the
content
is
already
laid
out
on
disk,
so
there's
more
to
be
said
there
and
certainly
feel
free
to
reach
out.
If
you'd
like
to
know
more
about
the
ocfl
or
you
can
just
go
to
the
website,
it's
not
a
fedora
specific
effort.
C
It's
one
that's
been
adopted
by
other
implementers
and
we're
just
one
of
many
in
terms
of
performance
and
scale.
So
those
of
you
that
are
familiar
with
previous
versions
of
fedora
may
know
version
four
and
five
were
backed
by
mode
shape,
which
gave
us
a
lot
of
benefits,
but
also
ended
up,
causing
us
a
lot
of
performance
and
and
scale
issues.
So
in
this
latest
version,
we've
completely
replaced
the
back
end
with
a
simplified
persistence
layer.
C
As
I
mentioned,
we've
also
added
a
built-in
search.
This
is
really
more
for
developers
and
repository
admins,
but
this
is
built
off
of
the
database
index,
so
we're
using
the
same
index
and
it's
not
intended
to
replace
a
more
robust
option
like
solar
or
elasticsearch.
Those
are
still
supported
as
external
integrations,
but
it
is
built
off
of
this
index,
which
we
support.
Several
of
postgres
seems
to
be
the
most
performant
in
our
testing,
but
we
do
support
mysql
and
mariadb
for
those
those
that
need
it.
C
Just
in
terms
of
migration
tools
and
support,
we've
done
a
lot
of
work
here
to
you
know:
try
to
bring
everyone
forward
so,
if
you're
using
a
custom
implementation-
and
we
think
this
will
also
be
true
for
sambar
implementations
at
least
one
community
member
has
already
successfully
migrated
a
severa
application.
But
of
course
there
are
numerous
applications
in
the
community,
so
we
do
need
to
do
more
testing
there,
but
we
have
done
a
number
of
tests
with
custom
implementations,
and
these
tools
have
proved
really
valuable.
C
So
we
have
the
migration
utils
for
fedora
3,
sort
of
custom
repositories.
We
also
have
a
validation
tool
that
you
can
use
to
make
sure
that
the
content
you
migrated
is
the
same
as
the
source
material.
But
then
we
also
have
these
import
export
and
upgrade
utilities
if
you're
running
version
four
or
version
five.
C
So,
basically,
for
any
of
those
previous
versions,
we
have
upgrade
paths
and
documentation
that
you
can
use
for
island
dora
and
I'm
basing
this
on
the
work
that
we've
done
so
far
in
a
grant
that
I'll
talk
about
momentarily,
we've
really
found
island
or
workbench
to
be
probably
the
the
tool
that
we
would
recommend.
Starting
with.
C
There
are
some
other
tools
in
the
community,
but
this
does
seem
to
be
the
one
that's
kind
of
garnering
majority
support
and
we've
certainly
invested
a
lot
of
time
in
sort
of
improving
improving
the
tools
so
that
that's
probably
the
recommended
approach
there,
but
basically,
whether
you
have
a
custom
or
a
sambera
or
an
island
or
a
installation.
There
are
pathways
that
you
can
follow
to
get
to
the
latest
version
just
in
terms
of
status.
C
So
in
december
we
released
an
alpha
build
and
we
followed
that
by
a
beta
in
february
and
now,
just
earlier
this
month
we
cut
a
release
candidate
and,
along
the
way,
we've
been
making
small
but
significant
improvements
to
optimizing
the
performance
and
scale
and
resolving
a
few
remaining
issues.
So
we're
planning
to
be
in
a
release
candidate
phase
for
a
couple
of
weeks
and
then
barring
any
major
issues,
a
full
release
by
late
june
or
early
july,
which
is
more
or
less
on
track
with
what
we
were
anticipating
earlier
this
year.
C
So
this
is
really
significant
news
for
the
community.
This
is
represents
about
two
years
or
so
worth
of
design
and
development
work
and
is
a
release
that
we're
quite
confident
in
in
tandem
with
this,
we've
been
working
on
a
fairly
major
grant
project
from
the
institute
of
museum
and
library
services,
the
fedora
migration
paths
and
tools,
project
I'll
share
a
link
to
these
slides
in
the
in
the
chat
after
after
we're
done
speaking.
If
folks
want
to
kind
of
follow
these
links.
C
But
this
has
just
been
focused
on
fedora
three
to
six
migrations
over
an
18-month
period,
and
you
know
the
the
main
high-level
goal
here
is
to
bring
the
community
forward
to
a
modern
and
supported
version
of
fedora,
which,
as
you
can
tell
from
the
previous
slides,
is
very
well
much
in
line
with
the
work
that
we've
already
been
doing
on
the
core
software.
So
it
was
very
fortunate
timing
with
this
grant.
C
We
started
work
in
september
and
there's
been
a
few
kind
of
steps
in
the
process
here
again,
it'll
be
very
brief,
but
we're
working
with
pilot
partners
to
kind
of
pilot
out
a
migration
scenario,
get
them
to
a
production
instance
and
then
along
the
way,
sort
of
develop
tests
and
refine
the
migration
tools.
So
a
lot
of
the
tools
I
mentioned
that
previous
slide.
Much
of
there's
been
a
lot
of
work
from
the
grant
funded
by
the
grant.
C
C
A
draft
version
of
it
available
within
the
next
couple
months
and
then
we'll
iterate
on
that
with
the
community
to
produce
a
production
version
of
that
and
the
grant
is
intended
to
culminate
with
a
sort
of
a
dedicated
migration
training
event
which
we
we're
originally
planning
for.
This
fall,
but
with
a
covid
situation,
we'll
most
likely
have
early
early
next
year,
but
we're
also
producing
online
training
materials
to
go
with
this.
C
Of
course,
none
of
this
would
be
possible
without
our
members.
The
grant
is
one-time
funding,
but
the
ongoing
operations
of
the
program
are
really
only
possible
because
we
have
a
great
community
of
members
that
pay
annual
dues
to
support
staff,
support
our
ability
to
offer
workshops
like
the
one
we
we
provided
at
open
repositories
yesterday
and
to
build
and
sustain
and
support
the
software,
and
also
to
sustain
and
iterate
on
the
grant
products
once
the
grant
is
complete.
D
Yeah,
so
thanks
david,
I'm
erin.
I
am
the
program
coordinator
here
at
fedora
and
since
I
joined
in
october,
my
focus
really
has
been
generating
a
structured
communications
calendar
that
it
touches
on
a
variety
of
outlets
and
with
it
has
content,
that's
aimed
at
different
levels,
so
that
all
community
members
are
getting
value
from
what
we're
sending
out.
So
what
this
means
is
that
if
you
join
any
of
our
mailing
lists
or
communication
outlets,
you'll
see
a
link
in
the
next
slide
to
the
different
ways
to
get
connected.
D
We
send
a
monthly
demo
video
that
we
create
to
help
kind
of
outline
and
talk
about
the
features,
especially
with
fedora
6
coming
out,
and
then
we
also
send
out
two
links
to
two
blog
posts
that
we
put
up
monthly.
So
one
is
an
imls
grant
update
from
david
and
the
other
one's
a
general
interest
blog
that
we
send
out
that's
kind
of
meant
just
for
fun
reading.
D
The
second
thing
that
we
have
upcoming
is
we
have
committed,
as
a
community,
to
hosting
a
workshop
at
least
once
a
quarter.
So
typically,
as
a
member
benefit,
we
open
the
registration
to
members.
First,
we
give
them
first
access
before
making
registration
publicly
available,
so
at
the
end
of
this
month,
actually
we're
hosting
a
technical
workshop
that
will
go
that
will
follow
the
migration
process
from
fedora
3
to
fedora
6..
D
The
event
is
free
to
attend
thanks
to
the
imls
grant.
So
registration
is
available
via
the
link
in
the
slides
that
david's
going
to
share
with
you,
so
you
can
go
and
do
that
and
the
last
thing
that
we're
planning
for
now
is
to
hold
our
annual
member
forums
and
something
kind
of
new
that
we'd
like
to
try
is
a
an
open
information
gathering
session.
D
So
you
can
look
forward
to
all
of
those
things
upcoming
and
you
can
just
flip
over
to
the
next
one
there
david
so
to
get
connected
here
are
some
resources,
some
links
that
david
mentioned,
I'm
just
going
to
touch
on
a
few
really
quickly
here.
The
first
link
is
the
link
to
migrate
or
sorry
to
download
and
test
fedora
6,
which,
as
david
mentioned,
is
in
the
release
candidate
phase.
D
Now,
so
you
can
go
there
and
access
that,
and
there
is
a
link
to
join
in
the
conversations
and
take
advantage
of
any
of
the
communication
pieces
that
I
did
just
outlined.
Above
there's
all
kinds
of
ways:
mailing
lists
slack
excuse
me
any
and
our
newsletter
obviously,
and
lastly,
a
link
to
become
a
member.
If
you're
not
already
one,
as
we
said
it's
because
of
our
member
institutions,
that
we're
able
to
provide
such
great
continued
support
and
continue
with
the
development
of
fedora.
C
C
Yes,
we
haven't
really
discussed
that
officially,
but
I
think
it's
safe
to
say
that
it
will
be.
That
is
where
the
kind
of
community
effort
we'll
be
going
into
going
forward.
We
don't
have
a
sort
of
major
road
map
of
core
changes.
So
there's
no,
you
know
I'm
sure
there
eventually
will
be
a
fedora
seven,
but
we
don't,
you
know,
have
any
sort
of
short
to
medium
term
plans.
A
A
D
B
Awesome,
okay,
so
before
we
get
started
well,
first
off
hi,
all
tim
donahue
at
lyricist
and
I'm
the
d
space
tech
lead
before
we
get
started.
I
did
want
to
note
that
we
have
an
active
d
space-
7
q,
a
google
doc
down
here,
where
you
can
ask
us
anything
even
after
this
session,
so
you're
welcome
to
ask
questions
during
the
session,
but
if
you're
watching
this
on
live
stream
or
recorded
later,
we
started
this
up
yesterday
in
our
workshop
and
you're.
Welcome
to
ask
anything:
there's
like
60-some
questions
already.
B
If
yours
isn't
answered
yet
ask
it
and
we'll
get
it
answered.
But
today,
here
I
want
to
talk
to
you
about
d
space
7.0
and
the
main
question
you
may
want
to
you
may
be
asking
already
is:
when
is
it
coming
out?
We
have
a
date
for
you,
it's
going
to
be
out
by
august,
2nd,
possibly
even
before,
then,
if
things
go
perfectly,
but
we
can
guarantee
that
you
can
go
and
download
it
and
play
around
with
d
space
7.0.
B
As
of
that
date,
right
now,
really
we
only
have
some
small
things
left
to
do
before
then.
We're
fixing
up
some
of
the
bugs
that
were
reported
during
our
test-a-thon,
which
started
in
april
late
april
and
went
into
may
during
that
same
time
period.
We
did
some
accessibility
analysis
with
an
external
provider.
B
They
reported
back
some
basic
accessibility
issues
that
we
had
with
the
new
ui
and
we're
working
on
fixing
those
as
well
and
we're
cleaning
up
the
final
documentation.
So
honestly,
if
you're
wanting
to
play
around
with
it
early
you're
more
than
welcome
to,
but
we
don't
feel
comfortable
calling
it
production
ready
until
we
get
all
those
little
bugs
fixed
and
the
accessibility
issues,
squashed
as
well.
B
So
another
question
we
hear
a
lot
is:
why
did
it
take
so
long
so,
and
I
wanted
to
kind
of
go
through
some
of
the
the
background
here
briefly
before
showing
you
some
of
the
highlights
of
what
to
expect
I'm
not
going
to
go
through
this
slide
entirely.
But
it's
worth
noting
that
the
discussion
around
a
new
user
interface
for
d
space
started
way
back
in
2014..
Development
started
around
2017,
although
it
was
very
lightweight
at
that
time.
B
I
mean
it's
also
worth
noting
that
this
is
by
far
the
most
massive
release.
We've
ever
done
in
d
space
history,
with
over
a
million
lines
of
code
changed,
and
you
can
see
the
scale
compared
to
other
major
releases
here
that
we've
had.
This
is
bigger
than
the
last
four,
even
five
releases
combined
all
the
effort
that
has
gone
into
d
space
seven.
B
So
this
is
really
what
we're
talking
about
and
why
it's
taken
so
long
here
to
get
this
into
your
hands,
but
we're
super
excited
for
you
all
to
get
to
play
with
it,
and
this
is
sort
of
the
development
progress
that
we
made
per
year.
So
in
2020
we
also
began
funded
development
which
helped
us
kick
it
into
full
gear.
Despite
that
pandemic
year
that
we've
all
gone
through
here,
we
were
able
to
do
fundraising
around
d
space.
B
So
I
want
to
go
through
a
little
bit
of
what
is
in
d
space
7.0
here
and
so
that
you
get
a
sense
of
what
all's
here.
You
may
have
seen
some
of
this
in
the
workshop
yesterday,
if
you
attended
it,
but
for
those
who
are
watching
this
for
the
first
time,
there's
some
new
information
here
for
you,
as
well
as
you
may
have
heard,
and
as
I've
already
alluded
to,
we've
got
a
brand
new
user
interface.
B
Lots
of
features
redesigned
there,
enhanced
user
privacy
to
better
align
with
gdpr
we've,
also
taken
some
of
the
old
command
line
tools
that
you
had
to
run
back
on
command
line
and
brought
them
into
the
admin
user
interface
into
a
new
processes.
Section
there's
some
embedded
video
basic
embedded
video
player
there.
All
of
these
features
that
are
in
the
ui
are
in
our
best
apis.
You
know
it's
fully
enabled
from
that
rest,
api
layer
as
well.
B
In
fact,
you
could
even
run
it
headless
if
you
really
wanted
to
and
there's
support
for
open
air
4
along
with
configurable
entities
which
I'll
touch
on
briefly.
All
of
this
built
on
the
same
sort
of
back
end
and
a
framework
that
dspace6
had
and
at
a
high
level.
This
is
sort
of
what
we're
talking
about
here.
We
have
that
back
end,
I'm
not
going
to
go
into
everything
here,
but
the
back
end
tools
and
functionality
is
very
similar
in
nature
to
dspace6,
with
still
having
solar
a
database.
B
B
And
it
is
worth
noting
here
that
we
had
a
couple
design
goals
that
we
brought
through
this
entire
development
process,
so
that
front
end
we've
made
themeable
by
a
bootstrap
designer
and
what
we
mean
by
that
is
that
we
want
you
to
be
able
to
theme
this
easily.
We
want
you
to
be
able
to
just
hire
somebody
who
knows
bootstrap
and
some
basic
html,
and
they
can
get
away
with
doing
quite
a
bit
of
the
the
theming
for
you
right
in
that
d
space
user
interface
without
needing
to
know
much
about
angular
at
all.
B
We're
also
striving
for
that
accessibility
alignment.
The
back
end,
is
streamlined
into
a
single
web
application,
which
is
a
little
bit
easier
to
resource
and
easier
to
install
and
configure,
and
that
back-end
also
really
has
security
and
stability
in
mind
these
days.
So
we
know
everybody
wants,
wants
your
data
out
there,
but
you
want
it
safe.
B
B
The
backend
also
has
to
trust
the
clients
that
it's
using,
so
it
only
trusts
your
user
interface
by
default,
but
you
can
enable
it
to
trust
other
clients
if
you
want
to
use
that
back
in
other
ways
and
everything
we've
built
in
dspace
7
has
been
using
test
driven
development,
so
we
can
find
and
squash
those
bugs
early,
whether
they're
on
the
ui
or
on
that
back
end-
and
this
is
one
of
the
other
questions
that
I
get
all
the
time
is,
can
how
do
I
upgrade?
Can
I
upgrade?
What's
that?
B
All
look
like
the
quick
answer
here
is
that,
yes,
you
can
upgrade
from
any
old
version
of
d
space
to
d
space.
Seven,
your
data
is
safe
and
can
will
upgrade
automatically
when
you
install
that
back
end.
On
top
of
it
the
front
end,
though
it
is
worth
noting,
this
is
the
one
area
that
will
be
a
migration
for
everyone.
You
must
install
that
brand
new
user
interface.
We
think
we're
you're
going
to
love
it
though,
and
we
think
you're
going
to
like
the
experience
there
a
lot
better
than
those
old
user
interfaces.
B
So
I'm
going
to
highlight
a
couple
quick
features
here:
I'm
going
to
move
slightly
quickly,
just
because
I
only
have
15
minutes
here,
but
this
is
some
of
the
stuff.
We're
really
excited
about
getting
to
show
you
or
getting
have
you
experienced
first
off
searches
available
everywhere
in
the
application
things
you
couldn't
search
before
you
can
now
search
so
things
like
your
in
progress
submissions,
your
workflows,
go
admin
only
search,
even
searching
across
entity
relationships,
all
of
that's
available
throughout
the
application
and
all
of
that's
also
available
within
the
header.
B
B
B
There
are
those
those
processes
that
we
brought
from
the
command
line,
which
I'll
show
briefly
here
as
well,
and
you
also
have
the
power
to
see
all
the
workflows
that
are
in
progress
and
administer
them
as
an
admin,
and
this
is
just
a
very
basic
oop.
It
jumps
midway
through
here.
It
looks
like
this
is
showing
some
of
the
processes
here
that
are
available
from
the
the
command
line
processes
that
you
can
kick
off
and
actually
monitor
from
within
this
processes
overview
in
the
admin
ui.
B
B
As
I
mentioned,
your
data
is
totally
open
for
integrations.
All
the
features
are
in
that
rest.
Api
built
by
with
best
practices,
is
mined
browsable
by
humans
or
machines,
every
endpoint
documented
and
arrest
contracts,
and
you
have
that
safety
and
stability
that
you
can
decide
which
clients
you
want
to
trust.
So,
while
anybody
can
read
your
metadata
there,
that's
public,
they
can't
all
log
in
unless
you
actually
trust
that
client
that's
coming
to
you
and
your
users
have
more
privacy,
more
alignment
with
gdpr.
B
You
have
user
agreements
and
privacy
statements
customizable
out
of
the
box.
You've
got
user
cookie
preferences.
You
can
delete
any
account
quickly
and
easily
through
the
dspace
admin
ui
and
briefly,
you
may
have
heard
a
little
bit
about
configurable
entities.
There's
there's
a
session
on
this
later
in
the
conference,
but
at
a
brief
level
entity
is
a
new
sort
of
object
within
d
space.
It's
an
item
that
has
a
specific
type
or
label
on
it
and
you
can
relate
it
then
to
other
entities
or
items
they're,
totally
optional,
but
completely
configurable
as
well.
B
All
of
this
is
enabled
within
entities
there's
much
more
on
entities
and
enhanced
submission
and
workflow
coming
on
thursday,
so
I'd
recommend
either
watching
these
live
or
watch
the
recording.
After
the
fact.
If
you
want
to
learn
a
little
bit
more
about
those
areas-
and
I
mentioned
that
we
had
extra
fundraising
for
d
space
seven.
So
these
are
the
folks
that
we
really
want
to
thank
around
providing
us
some
extra
funds
to
make
to
kick-start
that
development
and
really
push
it
into
high
gear
in
2020
and
2021,
and
also
a
huge
thank
goes.
B
B
I
mean
it
is
worth
mentioning.
We
do
have
a
plan
for
what's
coming
next
after
7.0,
7.0
does
not
include
all
of
the
features
of
6.0
or
6.3
or
any
of
those
6.x
releases,
but
those
are
coming
and
we're
planning
those
out
in
a
stage
7.x
release
plan.
So
we're
looking
at
adding
all
those
missing
features
over
several
smaller
releases
and
we
prioritize
them
on
the
on
a
wiki
page
which
is
linked
to
here.
B
You
can
see
that
in
the
slides
which
I'll
share
after
this
talk-
and
the
goal
here
is
to
try
and
get
those
highly
prioritized
features
in
your
hands
as
soon
as
possible
to
encourage
everybody
to
upgrade
and
we're
trying
to
really
do
this
in
the
same
sort
of
way
that
we
did
that
beta
release
structure.
So
we
had
five
betas
within
a
year.
B
B
The
slides
are
available
at
this
tiny
url
right
here
and
I'll
copy
it
into
the
chat
right
after
I'm
done
here.
The
public
google
doc
there
is
bolded
in
the
middle
and
the
slides
for
our
workshop
are
also
available
from
yesterday,
and
we
will
be
around
in
the
networking
sessions
coming
up
where
it
aligns
with
our
schedule.
So
you
can
find
myself
the
app
my
team,
the
for
science
team.
If
you
want
to
ask
some
more
one-on-one
questions
within
those
sessions.
A
A
B
So
a
little
bit:
yes,
it's
a
little
complex
to
describe
quickly,
but
we
do
have
some
author
authority
capabilities
built
into
the
new
configurable
entities
to
be
able
to
track
things
like
your
orcid
in
that
new
person
entity
model
and
be
able
to
actually
import
new
entities
from
orcid
to
create
them
within
d
space
and
allow
you
to
actually
even
define
your
preferred
name
within
that
all
that
sort
of
stuff.
So
there's
a
little
bit
in
that
entities
layer,
we
also
do
support
the
old
manner
of
authority.
B
There's
an
older
authority
framework
that
was
in
d
space,
five,
six
and
six,
that
we
support
some
basic
authority
mechanisms
as
well,
but
I'll
have
to
link
you
to
those,
probably
in
the
google
doc
as
best.
But
that's
kind
of
the
very
quick
summary
there's
not
a
whole
lot
new
there
other
than
the
entity
side
of
things.
B
Yeah
so
so
we're
introducing
entities
in
7.0.
There
will
be
many
many
enhancements
to
that
to
that
model,
incoming
7.x
releases
and
beyond,
and
we
are
hoping
to
be
able
to
have
tighter
integration
with
things
like
orcid
and
other
persistent
identifiers
sort
of
apis
out
there
to
be
able
to
create
entities
and
sync
entities
and
things
of
that
nature.
B
Automatic
citation
creation-
I'm
assuming
you
want
like
a
yeah
like
a
chicago
style,
citation
or
things
of
that
nature.
Right
now,
that's
not
in
the
d
space
7
interface,
but
I
think
that
that
could
be
something
that
could
be
generated
more
dynamically.
So
I
would
recommend
they
submit
a
feature
request
to
github
issues
where
we're
tracking
things
these
days
and
we
can
see
where
we
can
try
and
slot
that
in
along
the
way.
So
a
lot
of
that
information
is
captured
by
d
space,
but
not
necessarily
displayed
in
the
ui.
Yet.
A
B
Yeah
with
java,
we
are
up
to
java
10
now
and
we
do
require
java
10
to
in
order
to
upgrade.
So
you
cannot
run
eight
or
seven,
which
is
seven,
I
know,
is
end
of
life.
I
think
eight
has
become
end
of
life
as
of
2020.,
but
we're
on
java
10.
We
try
and
stay
on
lts
versions
as
much
as
possible,
and
the
plans
for
the
future
is
just
to
stay
on
lts
versions
both
for
java
and
for
angular
as
well.
A
B
Yeah,
so
we
are
looking
at
an
option
to
be
able
to
run
the
back
end
with
an
embedded
tomcat,
because
the
backend
now
runs
on
spring
boot,
which
allows
an
option
to
enable
embedded
tomcat.
So
you
can
just
kind
of
double
click
it
and
it
runs-
that's
not
enabled
right
now
in
dspace
space
7.0,
but
I
think
it
is
definitely
possible.
So
I
think
that
may
be
coming
down
the
line.
B
At
least
I
would
hope
it
would
be
coming
down
the
line,
something
I'm
interested
in
as
well,
but
I
don't
have
an
exact
timeline
for
when
that
would
happen,
but
folks
are
welcome
to
start
to
play
with
it.
If
you
figure
out
a
way
to
make
it
happen,
send
it
my
way-
and
I
would
love
to
get
it
out
to
everybody.
B
So
I
think
there
are
commonalities
there
that
we
could
start
to
look
at
how
to
make
that
happen
in
a
future
version
of
dspace.
But
it's
not
yet
definitively
on
the
road
map,
because
we're
trying
to
first
get
all
those
d
space.
Six
features
ported
over
to
d
space
seven
and
get
those
out
the
door
to
people.
B
Oh
aaaf,
yes,
we
actually
have
a
developer
who's
been
working
on
that
with
dspace
7
in
mind,
so
there's
some
pull
requests
that
are
out
there
related
to
adding
triple
a
f
support
both
to
the
back
end
and
the
front
end
to
make
it
work
properly
between
the
two.
So
that
work
has
started
with
one
developer,
but
I
know
he's
looking
for
more
people
to
test
and
help
out
with
that.
B
It
is
not
yet
in
7.0,
but
the
team
has
been
interested
in
that
work
that
he's
been
doing,
and
so
we're
going
to
start
to
look
at
that
as
we're
planning
out
7.1
and
7.2
to
see
if
we
can
try
and
help
that
effort
along.
So
if
you're
interested
in
that,
I
would
recommend
getting
in
touch
on
the
triple
I
f
channel
and
the
d
space
slack,
and
I
can
also
send
you
more
information.
A
E
E
Of
course,
community
is
much
more
than
numbers,
but
looked
at
from
that
perspective,
you
have
a
320
instances
out
in
the
wild
of
allendora
running
two
major
versions,
mainly
island
or
seven,
and
more
and
more
island
or
eight
and
I'll
showcase,
a
half
dozen
or
so
goes
down
to
our
eight
sites.
In
a
few
minutes,.
B
E
Or
eight
will
become
known
as
andorra
2.0
very
soon
we
have
a
fairly
active
email
list.
Well,
more
active
slide
channels.
These
days,
the
email
list
is
really
reserved
for
announcements.
These
days
we
have
34
island,
our
foundation,
members.
These
are
our
institutions
who
fund
the
island,
our
foundation
and
fund
the
staff
members
salaries.
E
We
have
a
thriving
vendor
community
five
vendors,
who
are
members
of
the
andorra
foundation
and
thriving
interest
groups,
some
on
hiatus
and
not
so
active.
Some
very
active
and
I'll
talk
about
a
couple
of
those
in
a
few
minutes,
just
a
map
showing
spattering
of
smattering
of
some
of
the
instances
that
we
know
about,
as
you
can
see
heavily
heavily
north
america
heavily
europe
and
well
represented
in
other
parts
of
the
world.
At
the
moment,.
E
E
E
This
is
the
herbarium
from
university
of
prince
edward
island.
It
documents,
flora,
species
on
the
island
and
an
interesting
feature
of
the
herbarium.
Is
this
graph
view?
This
is
not
a
standard
feature
of
aldor
8,
but
it
did.
This
is
something
specific
to
this
repository,
but
it
does
demonstrate
some
of
islander
8's
linked
data
capabilities.
E
A
couple
of
sites
now
from
new
zealand,
this
one
is
canterbury
stories,
a
website
of
the
repository
of
the
christchurch
city,
libraries.
This
is
not
their
home
page.
This
is
listing
a
brief
listing
of
some
exhibits
that
they've
put
together,
and
this
is
one
of
those
exhibits,
as
you
can
see,
table
of
contents
again
not
shown
here
in
this
top
top
top
half
of
the
page
screen
snapshot,
but
some
rich
media
embedded
in
the
in
this
exhibit.
E
This
is
the
second
one
from
new
zealand
that
I'll
showcase
it's
archive
central
group
of
archives
in
the
central
north
island-
and
this
is
interesting
because,
as
you
can
see
along
the
menu
of
the
top
agents
series
records,
this
is
a
example
of
an
outdoor
eight
site
that
that
demonstrates
quite
well
highly
hierarchical
information.
This
is
archival
descriptions,
so
those
this
interface
lets
you
drill
down
through
accessions,
series
and
records.
E
E
This
way,
final,
one
I'll
showcase,
is
lady,
the
latin
american
digital
initiatives
archive
repository
from
the
university
of
texas
at
austin.
It's
a
multilingual
variety
of
kinds
of
content
in
this,
and
one
of
the
remarkable
features
of
this
site
is
a
highly
sophisticated,
advanced
search
interface.
E
They
did
this
work
before
advanced
search
became
part
of
the
mainstream
island.
Dora
8
code
base,
so
they've
forged
ahead
and
done
this
on
their
own.
But,
as
you
can
see,
it's
fielded
you
can.
You
can
choose
various
fields
and
sort
attributes
and
has
many
other
solar
based
sites
is
highly
faceted,
so
shifting
from
some
calendar
eight
showcase
sites
back
to
the
community
a
little
bit
the
previous
year,
we
saw
a
couple
of
community
driven
sprints,
for
example.
These
are
coming
from
interest
groups,
mainly
so
the
metadata
interest
group
is
just
finishing
up.
E
Some
work
on
defining
and
refining
a
default
metadata
profile
for
aldor
8.,
the
under
documentation
interest
group
is
also
just
wrapping
up
a
sprint
to
update
the
documentation
to
match
some
of
the
new
features
and
functionalities
in
the
calendar.
Eight
release
that's
about
to
come
out
which
daniel
will
talk
about
in
a
few
minutes
and
the
last
one
group
online
support.
This
is
not
from
an
interest
group.
E
This
group
of
committers
got
together
and
just
did
that
pretty
quickly
without
the
formal
structure
of
a
sprint
or
an
interest
group,
which
was
quite
an
interesting
thing
to
watch
a
few
other
community
updates
at
the
end
of
2020,
the
aldor
foundation
deployed
a
feature
priority
survey
to
the
community
and
from
that
much
of
the
development
and
the
current
island
door.
Release
has
come
it's
very
good
to
see
the
community
pitching
in
to
tell
the
core
developers
what
features
were
important
to
them,
which
ones
were
not
so
important.
E
The
documentation
interest
group
was
one
of
those
interest
groups
that
kind
of
went
into
a
little
bit
of
hiatus
for
a
while.
It
is
now
back
in
full
force,
as
I
mentioned
a
minute
ago,
they're
just
wrapping
up
their
own
community
driven
sprint
to
bring
the
documentation
up
to
the
about
to
be
released
version
of
ellen
dora,
and
we
now
have
a
couple
of
new
regular
meetings.
E
We
have
had
a
technical
call
for
a
weekly
technical
call
for
quite
some
time
a
few
years,
but
now
we
have
two
new
calls:
a
user
user's
call
and
an
open
meeting.
These
are
both
monthly
meetings
and
the
user's
call
is
kind
of
a
counterpoint
to
the
technic
to
the
tech
call,
which
is
mainly
developers
and
integrators,
and
the
open
meeting
is
a
chance
for
it's
kind
of
like
outdoor
foundation,
office
hours,
it's
a
chance
for
people
to
come
and
just
chat
or
for
people
to
come
and
showcase
things.
They're
working
on.
E
The
key
new
thing
here
is
the
addition
of
a
leadership
group
which
is
sort
of
modeled
after
the
fedora
leadership
group.
Prior
to
this,
the
board
of
directors
was
large,
had
about
12
13
people
on
it,
representing
a
partner
level,
boundary
foundation
supporters
after
this
change.
That
group
is
now
the
leadership
group
and
they
are
tasked
with
defining
strategic
vision
for
the
ander
foundation.
E
The
board
of
directors
is
much
smaller
for
people
and
their
scope
is
limited
to
board
stuff
financial
illegal
mainly,
but
we
have
other
parts
of
the
under
community
or
the
around
our
community
governance
structure,
which
are
active
and
super
important.
The
coordinating
committee
is
the
operational
group
within
the
elder
foundation
and
they
do
important
things
like
manage
community
contributions,
both
in
code
documentation
and
so
forth,
and
also
plan
events
and
also
draft
policies
like
the
code
of
conduct.
For
example,
we
have
a
technical
advisory
group
which
does
what
it
says
on
the
label.
E
It
advises
danny
the
tech
lead
on
important
questions.
We
have
a
core
group
of
developers
who
are
responsible
for
ensuring
quality
in
the
code
base
and
we
have,
as
I
said
earlier,
a
thriving
set
of
interest
groups
who
are
communities
of
practice
around
things
like
digital
preservation,
metadata
institutional
repositories,
things
of
that
nature
and
like
david
and
tim,
I
want
to
thank
all
those
institutions
who
have
supported
us
over
the
years.
This
is
a
fairly
up-to-date
representation
of
those
institutions.
So
I
thank
you.
F
Okay,
so
I'm
here
to
talk
to
you
about
what's
coming
up
in
the
latest
release
of
island
aura.
So
I
guess
one
of
the
big
obvious
things:
you'll
notice
is
that
our
branding
has
changed
ever
so
slightly.
So
before
we
had
our
previous
major
version
was
island
or
seven.
This
is
island
or
eight
we
released.
It
was
island
or
eight
version
1.0.0.
F
So
we
wanted
to
have
semantic
versioning,
but
then
also
keep
you
know
the
drupal
major
version
kind
of
in
the
name.
Now
that
we're
on
drupal,
8
or
9
that
sort
of
no
longer
makes
sense.
We
don't
want
to
be
island
or
a
you
know:
8
9
version,
something
or
other,
so
we
just
dropped
the
numbers.
So
we
are
now
just
island
aura
and
version
2.0.0,
even
though
this
is
the
third
release
of
what
was
previously
known
as
as
island
or
at
8..
F
F
F
We
also
developed
an
advanced
search
module.
This
was
something
from
island
or
seven
that
we
had,
that
everyone
used
and
loved
and
was
sorely
missing
from
island
or
a
you
have
a
lot
of
improvements
of
search
in
search
and
indexing
in
island
or
eight
in
general,
and
so
then
this
just
brings
us
right
back
up
to
future
parity.
F
So
you
can
do
your
typical
boolean
type
searches
and
choose
your
fields
and
stuff
like
that,
so
you
can
really
control
and
hone
in
on
your
searches
with
that
and
I'll
just
say
it
is,
although
it's
bundled
up
with
the
allendore
module
right
now.
There
is
absolutely
nothing
island
or
specific
about
it.
F
We
also
added
audio
and
video
transcriptions
of
vtt
files.
It
will
accept-
and
this
will
actually
work
with
several
different
viewers
out
there.
So
if
you
want
to
just
work
with
the
html5
stuff
you
get
by
default,
we've
dropped
in
some
javascript
that
will
actually
play
these
transcripts
underneath
the
viewer
for
you.
But
if
you
use
a
more
sophisticated
solution
like
video
js
or
the
able
player,
which
is
actually
a
wonderful
player,
that's
got
a
module
for
drupal,
it's
very
accessible.
F
If
you
use
these
for
the
most
part,
you
can
kind
of
just
configure
the
modules
correctly
and
it
will
find
the
vtt
files
and-
and
it
will
work
as
expected,
so
this
sort
of
adds
another
content
type
to
what
island
or
a
can
provide
compared
to
what
seven
did.
So.
This,
essentially
is
the
new
version
of
what
was
oral
histories
in
island
or
seven
and
just
in
general.
F
F
There's
the
island
or
workbench
tool
that
david
wilcox
mentioned.
That
mark
actually
wrote,
and
you
can
certainly
use
that
for
doing
a
full-blown
migration
and
getting
all
of
your
content
in.
But
if
you
just
want
to
upload
these
five
things,
that's
what
this
batch
uploader
is
for.
So
now
you
can
just
kind
of
drag
your
your
original
files
and
drop
them
in
in
a
in
an
upload
widget,
and
it
will
do
all
the
work
of
you
know
sniffing
out.
F
What
sort
of
you
know
entities
it
should
create,
create
all
the
entities
and
then
wire
them
all
together
with
all
of
the
relationships
for
you.
So
it
saves
you
a
boatload
of
clicks
basically,
and
it
meets
this
nice
kind
of
middle
ground
that
we
used
to
have
in
island
or
seven
with
the
zip
batch
uploader,
and
so
this
this
also
sort
of
essentially
replaces
that,
but
it's
very
streamlined
experience,
just
kind
of
drop
your
files
in
and
then
they're
in
your
repository,
it's
pretty
nice.
F
So
that's
that's!
The
major,
like
software
features
that
I
wanted
to
talk
about,
but
mark
if
you'll
click
on
the
next
slide
I'll
talk.
This
is
another
huge,
huge
part
of
this
upcoming
release,
which
is
isle.
This
is
our
dockerized
island
aura.
The
isle
project
itself
has
been
around
for
for
a
while.
Now
it
started
out
as
a
a
grant
funded
project,
mellon
grant
funded
initiative
actually
for
island
oil.
F
F
All
of
those
took
anywhere
from
you
know,
30
minutes
to
an
hour
to
run
to
provision
an
environment
with
aisle.
Once
you
download
the
initial
images,
which
is
you
know
if
your
internet
connection
is
decent,
it's
a
couple
of
minutes,
then
it's
really
only
just
a
couple
more
minutes
until
you
have
your
your
island
or
installation.
F
So
a
typical
install
with
the
full
download
of
all
the
images
is
usually
less
than
10
minutes
and
for
developers
who
are
changing
things
or
iterating
things
to
deploy
your
changes
now,
making
a
small
change.
Does
it
lead
to
another
like
30
minute
to
an
hour?
Wait.
It
actually
just
leads
to
another
like
minute
or
two
max,
so
in
terms
of
developer
productivity,
devops
productivity,
it's
astronomical!
The
benefits
are
just
crazy.
F
F
A
lot
of
the
moving
parts
are
all
hidden
from
you,
which
is
really
great,
and
so,
when
you're,
focusing
on
maintaining
and
running
your
island
or
repository
now,
you're
really
just
kind
of
hyper
focused
on
maintaining
and
running
your
drupal
site
and
sort
of
all
of
the
rest
of
it
is
taken
care
of
for
you.
So
it
just
really
lowers
the
barrier
to
entry.
F
If
you
want
to
get
the
latest
changes,
you
just
use
doctor
and
you
pull
them
in,
and
the
community
does
that
for
you.
I
realize
I'm
running
out
of
time
here,
I'm
going
to
burn
through
these
last
slides,
so
I'm
just
going
to
burn
through
this
real
fast.
So
all
of
our
images
for
aisle
are
available
on
docker
hub.
You
can
get
them,
there's
an
island
door
organization
there.
You
can
see
them
anytime.
F
We
tag
a
release,
they
get
tagged
with
a
named
release
and
but
all
commits
are
tagged
and
pushed
up
to
dockerhub
using
their
commit
hash.
So
you
can
literally
find
and
locate
at
any
point
in
time
of
the
project's
history.
A
working
environment
and
just
real
quick
I'll
also
provide
a
lot
of
tools
for
using
docker
compose
to
actually
deploy
and
run
the
the
orchestration
it
generates
the
configuration
for
you.
We
got
a
lot
of
stuff.
F
So
we've
got
the
tools
for
sort
of
using
docker
to
do
all
these
things,
these
kind
of
sysadmin
workflows,
if
you
will
so
that's
it
I'll
leave
it
at
that.
I
got
two
links
down
here,
ones
to
our
website
islanddoor.ca
and
then
the
other
one
is
where
you
can
go
get
aisles.
So
if
you
are
interested
in
trying
out
island
dora,
basically
clone
that
down
using
git
and
type
make
demo
and
you've
got
an
island
or
I'll
leave
it
at
that.
A
F
So
yeah
every
time
we
push
it's
got
the
latest
commit
hash.
We
are
very
careful
to
avoid
using
the
latest
tag,
because
that
can
get
you
in
a
lot
of
trouble
because
things
won't
necessarily
line
up.
But
if
you
look
at
aisle
it's
built
with
a
different
github
repo,
but
you
can
go
in
literally
every
commit
in
that
repository.
It's
available
up
there
for
you
to
use,
so
you
can
always
find
the
latest.
F
But
the
thing
to
understand
is
that
your
drupal
site
we're
not
really
maintaining
so
you've
got
this
drupal
site
and
you're
updating
it
kind
of
out
of
sync
with
the
rest
of
the
other
stuff.
Really
what
you're
getting
is
the
rest
of
all
the
repository
infrastructure
like
the
stuff
to
generate
your
image
derivatives-
and
you
know
your
active
mq
and
tomcat
running
fc,
repo
and
and
and
that
sort
of
stuff,
so
that
stuff,
it's
very
easy
to
always
get
the
latest.
A
F
B
B
D
F
A
All
right,
well
thanks,
so
much
to
to
all
of
our
presenters
for
this
great
this
great
session.
Next
up,
as
as
I
mentioned
at
the
beginning
of
the
session,
we
do
have
our
very
first
of
our
three
networking
sessions.
I'm
pasting
the
link
to
the
sched
event
there,
and
that
is
happening
over
in
a
different
platform
in
wonder.me.
A
There
are
some
the
link
and
some
instructions
linked
in
that
sched
in
that
sket
event,
so
you
can
go
and
chat
with
our
generous
sponsors
and
also
meet
up
with
your
colleagues,
including
possibly
presenters
from
this
session.
If
you
have
more
questions,
I
hope
everyone
will
join
us
there
all
right
thanks.
Everyone
see
you
in
the
networking
session.