►
From YouTube: DSpace 7.4 Upgrading to DSpace 7.4
Description
Planning an upgrade to DSpace 7 in the future? This workshop will guide you through the upgrade process, providing hints to help simplify your upgrade. We will provide tips for updating older DSpace configurations for DSpace 7. Presenters: Tim Donohue (LYRASIS) and Corrado Lombardi (4Science) . Webinar from November 16, 2022.
A
Okay,
good
morning
afternoon
evening,
depending
where
you're,
connecting
from
and
welcome
to
day,
two
upgrading
to
dspace
7.4,
we're
excited
to
have
you
here
with
us
and
yep.
So
this
is
our
schedule.
We'll
have
a
short
introductions:
the
overview
of
the
upgrade
process,
overview
of
new
configurations
and
a
half
an
hour
for
questions
and
answers,
and
next
slide
I
just
wanted
before
we
started.
A
I
wanted
to
take
a
moment
here
to
remind
the
dspace
community
at
Large
that
d
space
wouldn't
be
possible
without
your
expertise
and
financial
support.
Dspace
software
is
financially
supported
by
the
community
via
membership
dues,
certified
partners
and
service
providers
and
various
fundraising
efforts.
A
Current
pledges
and
campaigns
are
the
dspace
Development
Fund,
the
global
sustainability
Coalition
for
open
science,
Services
known
as
Scots,
and
if
you've
been
enjoying
the
benefits
of
working
with
this
open
source,
community
and
software
product.
Please
consider
contributing
to
one
of
our
fundraising
campaigns
in
the
coming
year.
A
A
Okay,
so
I'm
gonna
do
some
quick
presenter
introductions.
I'll
start
with
myself.
My
name
is
Natalie
Bauer
and
I'm.
The
program
coordinator
and
I
just
started
a
couple
months
ago.
So
it's
great
to
be
here
with
such
a
big
number
of
the
dspace
community
in
these
three
days,
so
I'm
so
happy
to
be
able
to
be
working
with
you
all,
and
then
our
two
presenters
are
just
going
to
my
text
here.
Corrado
Lombardi
Corrado
is
a
technology
Enthusiast
born
in
Parma
Italy,
where
he
lives
and
he
was
born
in
1982..
A
A
These
experiences
gave
him
the
opportunity
to
collaborate
with
established
professionals
who
contributed
to
his
professional
growth
and
inspired
him
to
give
particular
attention
to
the
Quality
aspects
of
of
the
software
developed.
He
is
a
firm
advocate
of
extreme
programming.
He
adopts
and
recommends
these
practices
to
facilitate
projects.
He
has
an
MSC
in
computer
science
and
he
obtained
several
technical
certifications.
He
is
Deputy
CTO
at
for
science,
a
company
he
joined
in
2020.,
and
then
we
also
have
with
us
today.
Tim
Donahue
and
Tim
is
the
technical
lead
for
the
dspace
project.
A
A
So
Tim
has
put
the
URL
there
in
the
chat
box
so
that
you
can
access
that
document
and
make
sure
you
put
your
questions
in
the
section
for
today,
because
there
are
questions
already
in
that
doc
from
yesterday.
So
just
make
sure
you're
putting
your
questions
at
the
end
of
the
there's
already
a
few
questions
that
people
put
in
ahead
of
time
for
today
just
make
sure
you're
adding
to
that
as
we
go
and
if
it's
easier,
you
can
also
put
questions
in
the
chat
and
I'll.
A
B
Okay
and
now
it's
it's
over
to
me,
thank
you
Natalie
and
welcome
everybody.
One
thing
I
did
want
to
note
at
the
very
beginning
here:
I
saw
it
run
by
through
chat,
the
the
recording
will
be
available
to
everybody
after
these
presentations
over
these
three
days.
We're
planning
on
getting
them
sent
out,
hopefully
later
this
week
or
early
next
week
at
the
very
latest
and
the
slide
deck
as
well
will
be
available
to
everybody.
So
you
don't
need
to
rush
to
try
and
write
down
tons
of
notes
or
anything
like
that.
B
So
I'm
going
to
start
us
off
here
today
talking
about
the
upgrade
process
to
d
space,
7
and
first
off
like
why
you
might
want
to
upgrade
to
d
space
7.,
and
let
me
get
my
slides
working
there.
We
are
so
we
have
a
top
eight
reasons
to
upgrade
to
dspace
seven
and
most
of
these.
If
you've
looked
at
d
space
7
so
far,
they
might
be
somewhat
familiar
with
you
or
familiar
to
you.
B
We
have
a
brand
new
user
interface
that
has
enhanced
privacy
and
aligns
with
best
practices
for
accessibility,
a
rest
API
that
has
every
single
feature
of
dspace
support
for
Best
Practices
like
open
air
4,
as
well
as
the
core
Next
Generation
repositories.
A
New
Concept
called
configurable
entities,
which
we'll
talk
a
little
bit
more
about
as
we're
going
along
here
today,
but
allows
you
to
store
different
types
of
objects
within
d
space.
B
B
Three
I
already
mentioned
on
that
previous
slide,
but
we
also
I
also
want
to
stress
some
of
these
other
features
that
you
cannot
find
in
any
other
dspace
release.
We
support
orcid
authentication
now
and
you
can
synchronize
your
orcid
profile
with
a
local
researcher
profile
in
dspace
that
researcher
profile
uses
the
person
entity,
so
those
two
features
do
require
enabling
configurable
entities,
if
you
wanted
to
utilize
those
we
now
do
have
triple.
B
I
f
support,
there's
also
a
basic
image
and
video
viewer,
which
is
separate
from
the
triple
AF
supports
you
can
decide
which
one
you
want
to
use
and
that
scenario
based
on
your
use
cases.
We
support
openid
connect,
authentication
a
lot
of
the
scripts
that
used
to
have
to
run
on
the
back
end
and
the
command
line.
You
can
now
run
directly
from
the
admin
user
interface,
so
we're
trying
to
bring
more
tools
directly
to
your
fingertips
at
the
user
interface
level
and
we're
also
supporting
a
lot
more
import
mechanisms.
B
C
B
That
is
every
four
months,
which
means
we
do
one
release
every
three
months
and
the
reason
for
this
release
schedule
is
to
help
get
as
many
features
out
to
you
as
possible
in
d
space
7,
and
also
to
back
port
or
not
sorry,
not
back
port
forward.
Port
features
from
d
space
6
to
d
space,
seven,
so
we're
trying
to
move
features
from
d
space
6
into
7
as
quickly
as
possible,
so
that
we
have
a
feature:
compatibility
between
old
releases
of
dspace
and
the
d
space
7
release.
B
But
this
gives
you
an
idea
of
all
the
features
that
have
come
into
dspace
seven
over
the
last
little
over
a
year
and
right
now
we
are
working
on
these
features
here
that
are
all
old
features
that
existed
in
d,
space,
6
and
they're
all
being
moved
over
to
the
dspace
7
framework,
and
these
are
due
in
February
of
2023.
So
just
in
a
couple
months
here
and
we
anticipate
having-
hopefully
all
of
these,
but
at
least
most
of
these
will
be
in
that
release.
B
I'm
not
going
to
go
through
these
in
great
detail,
but
these
are
all
features
that,
if
you've
used
d,
space,
6
or
5,
these
existed
in
all
those
older
releases
of
dspace
and
that
release
will
also
include
other
improvements
and
fixes
and
other
possible
minor
features
coming
out
of
the
community.
When,
when
community
members
Give
us
new
code,
we
try
and
get
it
out
the
door
as
quickly
as
possible,
and
so,
if
you're
interested
in
taking
a
look
at
what's
going
on
with
7.5,
there
is
a
link
there
at
the
bottom
of
this
slide.
B
B
Now
I'm
going
to
talk
a
little
bit
more
about
what's
different
about
the
d
space
7
architecture
compared
to
dspace
six,
just
to
give
you
an
understanding
of
the
differences
there
and
then
we'll
go
through
the
upgrade
process.
What
it
looks
like
what
your
options
are
and
starting
to
get
into
different
tips
and
hints
that
we
have
for
you
here
today,
but
first
with
the
dspace
7
architecture,
if
you've
used
dspace
before
this
is
a
very
high
level
view
of
what
it
looked
like
sort
of
in
d
space
6..
B
So
in
d
space
6,
you
had
a
number
of
web
applications.
They
were
all
separate,
War
files
or
web
application
files
that
are
highlighted
here
in
the
red,
dotted
lines
where
you
could
decide
which
pieces
you
wanted
to
install
of
dspace
six
and
from
the
get-go.
You
had
to
choose
a
user
interface,
so
you
choose
either
the
JSP
UI
or
the
XML
UI,
and
then
there's
various
integration
tools
there
through
sword,
oai
pmh,
an
old
rest
API,
all
that
sort
of
stuff.
B
So
that's
what
you
may
be
familiar
with
if
you've
used
dspace
before
d
space
7,
the
back
end
is
similar
in
nature
in
terms
of
being
able
to
have
the
same
features
and
functionality
as
in
d
space
6..
However,
we've
combined
a
lot
of
those
tools
into
a
single
web
application
called
the
server
web
app
and
that
server
web
app
includes
not
only
the
new
rest
API
for
g-space
7,
but
it
also
includes
those
old
integration
tools.
B
So
the
sword
integration,
the
oaipmh
integration,
I'm,
even
the
rdf
integration-
and
we
do
allow
you
to
also
install
separately
that
old,
rest
API.
If
you
wanted,
if
you
need
it
for
backwards
compatibility.
The
bigger
Point
here,
though,
is
the
back
end
is
separate
now
from
the
front
end.
So
the
front
end
is
a
separate
application
that
communicates
with
the
back
end.
It's
an
angular
application
that
uses
bootstrap
for
theming.
B
But
that's
the
basic
idea
here
of
the
differences
between
those
two
platforms.
I
do
want
to
stress
here,
though,
that
the
back
end
in
terms
of
the
database
and
the
asset
store
and
solar
are
all
all
really
the
same
in
d
space.
Seven,
the
one
difference
is
that
solar
does
need
to
be
installed
separately.
Just
because
how
solar
changed
their
own
application,
we
can
no
longer
bundle
it
as
part
of
dspace,
so
you
do
need
to
install
that
separately
as
part
of
the
installation
for
dspace
7.
B
B
First
off
I
mentioned
this,
but
I
can't
stress
this
enough.
You
can
upgrade
to
d
space
7
from
any
old
version
of
dspace.
Your
data
is
going
to
upgrade
automatically
when
you
upgrade
your
database
using
the
database
script.
Your
files
are
automatically
recognized
as
well.
There's
nothing.
You
need
to
do
other
than
run
that
upgrade
script
to
update
from
any
old
version
of
dspace
7..
If
you
are
operating
from
an
older
version,
though,
you
may
want
to
consider
starting
with
the
fresh
configuration
on
the
back
end,
because
there
are
some
major
configuration
changes
in
dspace.
B
Six,
if
you
haven't
looked
those
yet
you'll,
probably
want
to
anticipate
that
during
your
upgrade
process,
if
you're
coming
from
four
or
five
or
even
earlier
I
mean
I
also
do
stress
that,
if
you're
upgrading
from
a
really
old
release
like
three
or
four,
you
want
to
check
the
release
notes
for
each
version
that
you're
jumping
over
just
in
case.
There
are
important
updates
there
that
that
may
impact
your
local
installation
or
things
that
you
use
in
planning
your
upgrade.
It's
important
to
note.
B
I
would
recommend
walking
through
the
installation
instructions,
though,
obviously,
when
you're
doing
this
yourself,
first
off
when
you're
installing
dspace
I
mentioned,
there's
the
back
end
and
the
front
end.
The
back
end
installation
is
very
similar
to
an
old
installation
and
d
space,
five
or
six
you're,
using
a
lot
of
the
same
tools
here.
The
process
is
extremely
similar
and
will
look
very
familiar
to
you
if
you've
ever
installed
an
old
version
of
dspace
before
so
you,
you
need
the
basic
prerequisites.
B
Once
you
have
those
basic
prerequisites
in
place,
you
download
the
backend
code
base
or
download
it
from
GitHub.
You
can
configure
your
local
configuration
at
the
very
least
you'll
want
to
configure
what
directory
you're
going
to
be
installing
into
and
some
basic
connection
information
to
your
database.
But
all
those
details
are
in
the
detailed
instructions.
You
do
a
build
and
installation
which
is
very
similar
to
how
you
did
with
deep
space
five
and
six
and
the
deploying
it
to
Tomcat
very
similar
again
to
how
it's
done
in
d,
space,
five
and
six.
B
The
one
difference
here
from
d
space,
5
and
6
over
to
seven
is
in
that
you
need
to
copy
your
dspace
solar
configuration
over
into
your
solar
instance.
It's
a
quick
copy
and
paste
into
solar
and
rebooting
stroller,
but
it
is
important
to
allow
solar
to
understand
what
information
dspace
is
going
to
be
indexing
within
solar,
sending
to
it
so
that
your
search
and
browse
works
properly.
B
At
the
very
end,
once
you
start
everything
up,
you'd
be
running
on
localhost
by
default,
you'd
have
a
URL
like
this
running
on
port
8080
by
default
and
that
server
web
app
as
I
mentioned,
that
single
web
application
would
be
running
there,
and
so
it's
like
the
basic
overview
of
what
that
backend
looks
like
and
how
you'd
install
it.
The
front
end
is
a
is
a
brand
new
installation
for
all
of
you.
B
If
you
haven't
done
this
before,
it
is
relatively
easy,
I
will
say
easier
than
installing
the
back
end
in
terms
of
the
number
of
things
you
need
to
put
in
place
and
how
to
configure
it.
You
just
download
and
install
node
and
yarn
download
our
code
base
from
GitHub,
either
the
zip
file
or
the
code
base
from
get
install
the
dependencies,
which
is
a
single
command,
that
yarn
install
command
that
will
install
all
the
dependencies.
B
You
need
configure
your
configuration,
which
just
allows
you
to
specify
again
sort
of
your
basic
information
about
this
installation,
and
then
you
build
it
and
start
it
up.
The
build
process
takes
a
little
bit
of
time.
It'll
take
a
somewhere
between
five
to
ten
minutes,
depending
on
the
speed
of
your
server,
so
it
it
is
worth
noting
that
the
build
is
compiling
all
that
JavaScript
together
minimizing
things
making
getting
it
ready
to
go.
The
startup
is
almost
instantaneous,
it's
like
a
second
or
two,
and
there
are
two
ways
to
start
things.
B
If
you're
just
doing
a
very
quick
installation
and
running
it,
there's
a
yarn
command
for
that.
We
do
recommend
considering
using
pm2.
It
will
make
your
lives
a
little
bit
easier
when
you're
running
in
production.
I'll
talk
a
little
bit
more
about
that
as
we're
going
along
here,
but
in
the
end
you
end
up
with
an
application
running
on
that
Port
4000
there
on
your
Local
Host.
B
Once
you
have
the
back
end
and
the
front
end
in
place.
If
you
want
to
add
that
https
production
support
control
or
a
production
installation
does
require
https
or
secure
connection.
If
you
want
to
add
that
so
your
secure
connection
easily
I'd
recommend
using
either
Apache
or
nginx.
There
are
other
ways
to
do
this,
but
I
find
that
most
sites
using
dspace
7
find
it
the
easiest
just
to
install
either
Apache
or
nginx
and
proxy
everything
through
those
it's
a
pretty
simple
setup.
B
We
have
instructions
for
how
to
do
it
with
a
Apache
in
our
installation.
Instructions
nginx
is
pretty
easy,
I'm
told
as
well
I'm
not
as
familiar
with
the
installation
there,
but
I
would
encourage
folks
who
are
familiar
with
that.
We
can
add
documentation
there.
Please
send
it
our
way.
We
can
add
some
more
information
for,
for
others
who
may
want
to
use
nginx,
but
you
install
one
of
those
two
tools
and
then
you
can
proxy
your
request
into
the
back
end
or
the
front
end
where
you
can
send
any
requests
to
that.
B
B
I
mentioned
this
very
briefly:
security
is
really
a
priority
in
d
space
7
we're
trying
to
keep
your
back
end
and
your
front,
and
your
data
very
secure.
That
does
mean
that
https
is
required
in
production.
You
have
to
run
the
back
end,
at
least
in
that
secure
mode.
It's
not
only
required
by
dspace.
It's
also
going
to
be
forced
by
your
web
browser.
There's
not
a
way
to
get
around
this,
because
dspace
depends
on
some
web
cookies
and
those
cookies
need
to
be
sent
securely,
so
your
web
browser
will
block
those
secure
cookies.
B
If
you
try
to
get
around
this,
so
you
will
need
to
do
this
in
production.
It
is
possible
to
run
the
dspace
7
app
in
just
HTTP
mode
as
long
as
you're
doing
everything
on
your
local
machine,
so
developers
do
that
all
the
time,
if
you're
doing
it
all
in
your
local
machine,
you
can
run
everything
on
localhost
and
you're
good
to
go,
but
as
soon
as
you
want
to
bring
this
to
a
production,
application,
you'll
need
to
put
it
in
that
secure
mode.
B
B
There
is
actually
where
your
UI
is
running
locally,
and
so
that's
often
going
to
be
a
local
host
URL,
and
it
may
say
that
it's
localhost
Port
4000
and
that's
perfectly
okay
to
be
doing
that
in
production.
Because
again
you
have
that
proxy
in
front
if
you're
setting
it
up
through
Apache
or
nginx.
That
allows
you
to
proxy
it
to
that
full.
You
URL-
and
this
is
something
that
often
does
trip
people
up.
There
are
tons
of
information
the
documentation
about
it.
B
I'll
mention
some
of
the
places
to
go
for
help
later
on
here,
but
that's
just
something
to
be
aware
of
once
you
have
everything
set
up
in
that
installation
process.
As
I
mentioned,
you
can
easily
migrate
your
data
over.
We
have
a
installation,
documentation
or
migration
documentation
for
this
linked
at
the
bottom,
where
you
can
find
all
the
information
about
how
to
migrate
your
data
from
an
old
d
space
into
a
new
one.
These
are
the
basic
steps
you
would
follow.
B
You'd
migrate,
the
database,
then
the
asset
store
you'd,
either
migrate,
your
configs
or
recreate
them.
If
you're
coming
from
a
very
old
version,
I'd
recommend
recreating
them.
If
you're
coming
from
d
space
6,
you
might
be
able
to
just
migrate
them
for
the
most
part,
you'd
update
your
database
by
running
the
database,
migrate,
command,
re-index
everything,
and
then
you
can
swap
your
domain
over
once
you're
ready
to
go.
This
does
allow
you
to
have
minimal
downtime.
B
If
you
want
to
do
that,
you
can
swap
the
domain
over
after
the
re-indexing
has
completed
with
everything
to
go.
You
would
want
to
have
some
important
time
where
you're
doing
that
migration,
of
course,
and
make
your
users
aware
not
to
be
adding
content
during
a
period
of
time
when
your
migration
is
taking
place,
but
this
is
one
way
of
going
about
that
upgrade
process.
B
The
second
way
is
doing
that
upgrade
in
place
this.
These
instructions
are
going
to
go
a
lot
quicker
because
it's
very
similar
to
that
installation
process,
but
there
are
detailed
documentation
of
that
upgrade
in
place
again
in
the
wiki
there
at
the
bottom.
Upgrading
the
back
end,
that's
very
similar
to
that
installation
of
the
back
end.
B
You
basically
just
want
to
upgrade
or
install
all
your
prerequisites,
make
sure
they're
all
up
to
date,
based
on
what
is
required
for
d
space
7,
but
it's
very
similar
to
to
in
the
past
as
well,
and
this
these
are
those
basic
steps.
These
will
look
familiar
to
you
if
you've
ever
done
an
upgrade
before
with
dspace
five
or
six,
it's
basically
going
through
and
downloading
that
latest
code.
Updating
your
configs
doing
that
build
and
update
Running
that
database
migrate
script.
B
The
one
thing
that
is
different
here
and
Corrado
will
mention
this
again
later
on,
as
we're
going
through
is
that
there
is
a
migration
for
the
submission
form
XML
there
used
to
be
an
old
input
forms
XML
file,
which
has
now
been
redefined
at
a
new
submission
forms
XML
file
in
deep
space.
Seven
krato
will
go
through
that
in
a
lot
more
detail,
but
it's
worth
being
aware
of
that.
The
submission
configuration
changes
here
and
then
you
do
the
usual
deployment
to
tomcat
and
as
I
mentioned
about
solar.
B
In
this
case,
you
need
to
bring
the
solar
configs
over.
The
one
thing
to
stress
again
is
if
you're
doing
this
upgrade
in
place,
there's
no
path
to
upgrade
from
the
old
XML,
UI
or
jspui.
You
need
to
adopt
the
new
dspace,
7
user
interface,
there's
no
way
to
move
forward
from
those
old
user
interfaces.
They've
gone
Obsolete
and
they're
not
possible
for
us
to
migrate
into
the
new
platform
instead,
so
you'll
have
to
install
the
user
interface
like
I
went
through
already,
so
I
do
have
some
tips
here.
B
That's
the
overview
of
what
that
upgrade
looks
like
how
to
do
it
at
a
high
level.
Again,
the
documentation
is
your
friend
here,
but
these
are
some
tips
based
on
what
some
of
the
early
adopters
have
learned
along
the
way
people
have
done
this
before
in
terms
of
starting
fresh
free,
nap
versus
upgrade.
I
mentioned
this
already,
because
the
scale
of
the
upgrade
there
are
some
who
have
reported
to
us
that
they
found
that
it's
almost
easier
to
start
fresh.
B
It
might
be
a
good
opportunity
to
start
fresh,
get
that
d
space,
7
installation
in
place,
get
comfortable
with
d
space
7
and
how
it
works.
I,
give
it
a
give
you
a
chance
to
review
and
update
your
configuration
if
you
need
to
have
a
configuration
review
and
then
migrate
that
data
over
when
you're
ready
to
do
that
that
swap
over.
So
some
people
found
this
a
lot
easier
to
approach
than
the
In-Place
migration,
so
I'd
recommend
considering
that
as
an
option
locally
I
mentioned
I'd
talk
a
little
bit
more
about
pm2.
B
This
is
a
new
tool
that
is
optional,
but
we
do
recommend
it
highly.
It's
a
process
manager
for
any
node.js
apps
the
front
end
is
a
node.js
app.
It's
a
JavaScript
based
app
built
on
angular.
The
reason
we
do
recommend
considering
this
is
that
there
is
a
cluster
mode
that
you
can
run
pm2
in.
That
allows
you
to
scale
the
user
interface
across
multiple
CPUs.
B
This
can
really
improve
the
performance
of
the
server-side
rendering,
which
is
what
is
used
for
search
engine
optimization,
and
it's
also
that
when
you
first
hit
the
site,
it's
when
that
first
page
load
happens.
If
you're
seeing
slowness
there,
you
probably
want
to
switch
over
to
a
cluster
mode
or
some
other
tool
like
pm2.
That
can
use
this
sort
of
clustering
across
CPUs.
So
we
have
found
this
very
useful
for
those
performance
reasons.
If
you
don't
want
to
use
pm2
you
don't
have
to.
There
are
other
tools
that
can
do
things.
B
This
is
also
a
common
question.
We've
heard,
there's
been
some
confusion
about,
can
I
run
d,
space,
7
and
Docker.
You
can,
and
there
are
many
sites
that
are
already
running
deep
space
7
in
Docker.
We
do
have
development
Docker
scripts.
In
our
code
base
you
can
find
those
in
the
open
source
code
base
in
both
the
front
and,
in
the
back
end,
you're
welcome
to
reuse
or
repurpose
those
scripts.
For
your
purposes,
however,
we
don't
recommend
running
them,
as
is
because
they
open
up
some
ports
that
you
probably
don't
want
open
up
in
production.
B
They
are
used
for
development,
so
we
open
up
ports
to
allow
us
to
do
more
testing
and
development
to
do
some
debugging
and
development,
and
you
probably
don't
want
those
open
in
production.
So
we
do
not
yet
have
those
production,
quality,
Docker,
scripts,
I,
think
someday.
We
may
and
I'd
encourage
if
folks
want
to
help
us
build
those.
B
Another
question
can
I
continue
to
use
the
Oracle
database.
If
you
haven't
heard
Oracle
support
has
been
deprecated,
it'll,
be
ending
next
year
mid
next
year,
so
we
do
not
recommend
upgrading
with
Oracle
database
in
place.
We
recommend
taking
this
opportunity
to
migrate
over
to
postgres.
If
you
have
not
already
from
our
understanding.
Most
people
are
on
postgres
I
know
there
are
still
some
Oracle
users
out
there,
so
this
probably
does
not
impact
many
of
you,
but
for
those
that
does
impact
there
are
options
for
how
to
do
this.
Migration.
B
B
There
is
also
an
option
to
use
the
aura
to
PG
script,
which
is
a
third-party
tool,
not
something
we
built,
but
it's
just
a
way
to
migrate
from
Oracle
to
postgres
in
general.
There
is
a
link
there
in
these
slides
of
an
example
of
one
dspace
site
that
did
use
that
successfully,
so
it
is
possible
to
do
you
also
can
hire
one
of
our
service
providers.
I
know
they've
done
these
migrations
before
you
can
get
in
touch
with
one
of
them,
if
you
want
to
just
hire
them
just
for
this
migration
purpose.
B
And
finally,
this
is
sort
of
my
final
little
section
here
before
I'm
going
to
hand
it
over
to
Corrado
there's
a
couple
more
slides
here,
but
this
comes
up
a
lot.
So
I
do
want
to
spend
a
few
slides
to
talk
about
it.
Do
I
need
to
use
configurable
entities
that
is
a
big
flashy
new
feature
in
d
space
7,
if
you're
not
very
familiar
with
it.
We
did
go
through
these
slides
yesterday
and
gave
a
little
bit
more
of
a
demonstration
of
what
configurable
entities
look
like.
B
But
it's
worth
noting
just
a
couple
highlights
here
that
entities
are
new.
Are
a
new
type
of
item
they're
still
an
item
but
their
new
type
of
item
where
you
can
actually
Define
a
specific
type
they're
completely
optional,
but
they're
kind
of
useful
in
that
you
can
Define
relationships
between
one
entity
and
another
entity,
I
mean
they
don't
replace
items
altogether.
B
You
can
still
use
items
and
collections
do
need
to
be
aware
of
entities,
so
usually
a
collection
will
accept
either
an
entity
type
or
an
item,
type
or
regular
item,
but
we
do
have
some
out
of
the
box
entities.
We
showed
these
off
a
little
bit
more
yesterday,
but
these
are
what
are
available
out
of
the
box,
but
the
main
question
about
should
I
use
configurable
entities.
I
do
want
to
stress
that
entities
are
considered
an
advanced
feature
at
this
time,
so
there
are
some
known
limitations
to
them.
B
They
do
not
support
aips,
that
AIP,
backup
and
and
restore
process.
They
do
not
support
that.
Yet
there
is
not
yet
a
bulk
migration
process
from
old
d
space,
6
items
into
d
space,
7
entities,
I
think
that
will
be
coming
at
some
point
in
the
future.
But
it's
not
there
yet
I
mean
you
really
need
to
understand
the
relationship
with
a
collection.
B
You
need
to
have
a
collection,
at
least
one
collection
for
each
entity,
type
that
you
wish
to
create
in
your
system,
and
so
one
scenario
where
you
might
want
to
enable
entities
is
if
you
need
some
of
those
new
features.
I
mentions
that
do
require
entities.
It
is
possible
to
enable
entities
and
only
use
them
for
this
orcid
synchronization
with
these
local
researcher
profiles.
B
That
could
be
your
own
use
case
of
entities
initially
until
you
get
more
comfortable
with
them
or
until
you
want
to
use
them
more
or
you
may
want
to
use
them
if
those
default
entities
that
I
showed
briefly
align
well
with
the
sort
of
data
you
want
to
add
into
your
d
space,
but
you
may
want
to
keep
it
disabled
if
you
depend
heavily
on
that
AIP
backup
and
restore
process,
because
they're
not
supported
there,
yet
they
will
be
supported
in
the
future,
but
they're
not
there.
Yet.
B
You
also
may
want
to
keep
it
disabled
if
you're
not
really
interested
in
being
an
early
adopter.
Because
again,
these
are
an
advanced
feature.
They
work,
but
not
all
those
tools
and
services
are
integrated
into
them
like
that.
Aip,
backup
and
restore
and
similar-
and
if
this
upgrade
already
looks
really
complex
to
you,
I-
would
highly
recommend
keeping
them
off
for
now.
I
I
would
not
overly
complicate
your
upgrade
process.
I
know
this
is
a
big
upgrade
for
folks.
B
B
And
finally,
if
you
go
through
this
process
and
you
get
frustrated,
you
look
like
the
face
up
there
in
that
corner
and
you
hit
an
issue.
There
are
common
issues
that
people
are
hitting
during
this
upgrade
or
the
installation.
We've
documented
many
of
these
in
the
common
installation
issues
Link
at
the
bottom
there,
and
these
are
some
of
them
linked
or
mentioned
at
the
top
here,
where
the
UI
spins,
you
get
some
weird
errors
that
you
don't
understand.
B
You
can't
log
in
a
lot
of
those
scenarios
are
documented,
along
with
the
solutions
to
them
and
that
common
installation
issues
link.
We
also
do
have
a
troubleshoot
and
error
page
if
you
really
can't
figure
out.
What's
going
on
or
you
need
to
find
the
underlying
error
message:
that's
a
great
resource
to
allow
you
to
understand
where
to
find
errors
in
d
space
7..
Sometimes
there
is
going
to
appear
more
on
the
front
end.
Sometimes
they
can
appear
more
on
the
back
end
and
that
guides
you
through
how
to
find
those
error
messages.
B
And
finally,
if
neither
of
those
first
two
links
help
you
out,
there's
the
option
there
to
ask
for
more
help
or
support.
That
brings
you
right
to
to
our
Support
options,
the
main
places.
Of
course
you
may
be
well
aware
of
we
have
all
of
our.
We
have
slack.
We
also
have
all
of
our
mailing
lists
available
to
you
and
there's
also
a
stack
Overflow,
where
you
can
ask
questions
there
as
well,
and
that
wraps
things
up
for
me.
B
So
I'm
going
to
hand
things
over
here
to
Corrado
and
he'll
walk
you
through
many
of
the
new
configurations
in
d
space
7.,
so
I
was
able
to
give
you
an
update
of
overview
of
the
upgrade
and
installation
process.
Now
krata
is
going
to
dig
in
a
little
bit
deeper
into
some
of
the
configurations
you
may
want
to
more
closely
look
at
as
you're
doing
this
upgrade
and
installation
of
d
space
7.,
so
Corrado.
If
you
want
to
take
it
away
here,.
C
Okay,
thank
you
very
much
team
hello,
everybody
good
morning,
good
afternoon
and
good
evening.
So
yes,
as
the
team
said
now,
I'm
going
to
share
with
you
some
a
bit
deeper
overview
on
which
are
the
new
configurations
available
in
the
space
7
systems.
So,
let's
start
from
the
user
interface
configuration
which,
which
are
the
already
mentioned,
config
yaml
file.
C
The
space
7
allows
you
to
provide
different
configurable
file
depending
on
the
environment.
You
will
eventually
want
to
run
so
now.
Let's
have
a
quick
overview
about
the
most
common
or
the
part
of
the
configuration
file
display
screen
is
Adopt,
A
displace
adapter
could
want
to
edit.
The
one
of
the
this
section
is
the
one
who
drives
the
language
selection,
the
language
selector.
C
Is
this
a
part
you
are
seeing
in
the
animation
in
the
background,
allows
you
to
Define
Which
languages
are
enabled
in
your
display
7
instance,
and
how
they
should
appear.
The
space
comes
with
a
lot
of
languages.
It
is
up
to
display
7,
administrator
or
installer
or
adopter
to
decide
which
languages
they
want
on
their
instance.
C
Those
are
two
components
available
out
of
the
box
in
the
space
seven,
so
it
is
possible
for
what
concern
of
the
recent
submission
it
is
possible
to
define
the
standard
page
size
and
also
the
step
to
be
followed
when
load
more
button
is
clicked
and
which
is
the
criteria
on
top
of
which
recent
submission
are
sorted
on
the
other
side.
For
what
concert
sorry
for
what
concerned
the
top
Community
level
it
is
possible
to
since
they
are
listed
in
a
paginated
way,
it
is
possible
to
define
the
page
size
go
ahead.
C
Next
slide,
please,
okay,
the
same
applies.
Another
property
is
the
one
driving
the
close
by
option.
It
is
possible
to
browse
the
repository
content
according
to
several
criteria,
so
they,
the
last
two
properties,
are
common
for
all
the
browse
possibilities
and
they
drive
whether
or
not
in
the
browsing
section.
This
space
should
display
the
thumbnails
of
the
items
and
since
the
browser
pages
are
still
paginated,
it
is
possible,
with
the
page
size
attribute
to
Define
how
many,
how
big
should
be
a
step
and
how
big
are
the
pages.
C
In
the
particular
case
of
browsing
involving
a
database
filter,
it
is
also
possible
to
Define
how
the
hear
selection
here
selection
should
be
populated.
It
is
possible
to
Define
how
many
years,
which,
with
one
here
step,
must
be
proposed
into
the
select
how
many
years
with
a
five-year
step,
you
can
see
it
in
the
screenshot
in
the
select
here
select
screenshot
from
2010
back
the
step
back
is
five
years,
whereas
from
2022
to
20
to
2011
the
step
is
one
year
and
we
also
provide.
C
C
It
is
possible
to
Define
even
the
the
page
size,
which
means
how
many,
how
many
communities
should
be
displayed
in
their
list
and
how
big
is
the
step
when
the
show
more
button
is
clicked
next
one,
the
space
7
provides
a
media
viewer
and
it
is
up
to
the
administrator
via
the
configuration
file,
to
decide
whether
or
not
the
media
viewers
should
be
enabled.
In
the
black
background
GIF.
C
We
are
seeing
an
example
available
when
the
video
media
viewer
is
enabled,
so
the
property
is
set
to
true,
and
these
allow
the
space
to
show
the
video
content.
Video
attachments
by
mean
of
this
embedded
video
player,
something
similar
applies
when
image
viewer
is
enabled,
meaning
that
attachments
image
attachments
that
are
images
are
displayed
in
a
kind
of
gallery
view.
C
Next,
please,
okay,
so
these
were
the
let's
say
the
most
common
properties
display
7
adopter
could
want
to
might
want
to
change.
Jumping
on
the
back
end,
the
backhand
configuration
files
are
all
under
the
config
and
config
folder
of
the
space
and
the
space
installation
directory,
as
well
as
its
subdirectory
modules.
C
Next,
please,
foreign,
so
the
most
common
file
configuration
file
you
may
want
to
update
or
to
change
is
the
local
CFG
which
has
in
the
previous
versions,
allows
to
override
the
the
value
of
properties
when
defined
also
in
other
files.
So
the
actual
value
which
will
be
taken
into
account
by
the
space
7
will
be
the
one
defined
in
local
CFG.
C
These
set
of
properties
are
the
important
backend
configuration
AKA
as
the
properties
that,
if
missing
or
misconfigured,
could
lead
to
an
unexpected
behavior
of
our
display
7
instance,
and
they
are
the
displays
directory,
which
holds
a
reference
to
the
folder
where
the
back
end.
The
application
is
installed.
The
display
server
URL,
which
holds
the
actual
URL
of
the
backend
application
on
the
counterpart.
The
displays
UI
URL,
holds
the
URL
to
which
is
exposed
to
the
front-end
application,
all
the
properties
they
are,
if
I'm,
not
wrong.
C
Three
under
the
DB
prefix
are
the
one
driving
the
access
to
the
database,
whereas
the
solar
server
must
contain
the
URL
of
the
solar
system,
which
will
hold
the
index
at
the
Space
7
data
and
to
properly
deal
with
course
and
csrf
protection,
as
I
said
previously
by
default,
the
back
end
allows
connections
just
from
the
display
UI
URL
it
is.
It
is
possible
to
allow
other
URL
to
send
requests
to
the
backend.
Our
warrant
is
to
pay
attention
to
which
are
the
allowed
Origins.
You
want
to
set
next
slide.
C
C
We
say
the
that
display:
73
comes
with
a
new
sources
from
which
it
is
possible
to
import
metadata
and
to
properly
have
some
of
those
sources
working.
It
is
as
a
prerequisite.
It
is
a
properly
key
or
properly
API
credentials
are
needed,
since
all
those
integration
with
the
star
and
providers
are
built
on
top
of
API
integration.
C
C
This
is
an
example
of
where
those
keys
are
useful.
The
display
7
user
is
allowed
to
query
external
system,
which
are
the
ones
available
in
the
drop
down,
and
then
what
is
happening
here
behind
the
scenes
is
that
one
of
those
external
system
is
being
queried
and
once
the
results
are
available,
the
submitter
is
able
to
start
a
new
submission,
starting
from
one
of
those
query
results
and
the
said
to
have
some
of
these
system.
C
The
space
7
is
integrated
with
it
is
needed
to
have
an
API
key
which
could
be
set
must
be
set
into
the
configuration
file.
We
suggested
to
put
them
into
the
local
CFG,
even
the,
even
if
there
is
a
properly
configuration
file
driving
and
containing
all
the
properties
needed
to
deal
with
these
external
providers.
C
Next
one
please,
okay,
and
this
is
what
concern
the
basic
front
hand
and
back-end
configuration
now
speaking
about
submission.
Let's
have
a
look
at
how
the
submission
form
must
be
could
be
sorry
configured
next,
please,
okay,
basically,
the
submission
is
configured
with
two
files
item
submission
XML
as
it
was
already
in,
and
it
is
something
similar
to
what
what
was
in
the
previous
versions
and
the
other
file
we
will
see
in
our
shortly
is
submission
forms
XML,
for
what
concern
is
the
first
file?
C
It
still
allows
you
to
map
submission
a
particular
submission
to
one
of
the
collections.
So
if
you
want
a
particular
submission
flow
for
a
collection,
you
can
configure
it
in
this
XML
file
and
still
here
here,
the
steps
of
composing.
The
submission
are
still
the
find
as
a
as
a
difference
from
the
previous
version.
Now
each
step
represents
the
section,
a
section
of
a
form
which
which
are
displayed
the
section
in
a
kind
of
an
accordion
fashion.
C
Each
step
may
be
mandatory
or
optional
and
for
each
step
each
step
holds
a
proper
type,
which
will
be
eventually
reflected
to
a
different
action
taking
during
the
submission
next,
please
so
he
he
wrote
a
brief
example
of
how
the
step
and
the
submissions
are
defined.
So
from
the
bottom.
A
submission
could
be
eased.
It
could
be
defined
by
with
by
a
series
of
steps.
C
Each
step,
as
you
can
see
in
the
screenshot,
represent
a
part
of
the
submission
of
the
submission
and
those
steps
are
defined
in
another
node
of
the
same
XML
file,
which
is
the
one
reported
above
called
Step
definition
or
held
in
Step
definitions.
Node
back
to
the
accordion,
as
you
can
see,
each
step
represents
a
section
of
the
submission
form.
C
C
Item
submission
Define,
some
other
optional
steps,
which
is
which
are
which,
whose
adoption
in
the
submission
is
up
to
the
need
of
your
institution
of
your
display
7
instance.
Just
to
mention
a
couple.
We
do
Halal
the
submit
that
we
do
allow
the
selection,
the
setting
of
creative
common
based
license
with
a
proper
step.
C
Part
of
the
form
which
allows
a
submitter
to
define
the
access
policies
to
the
to
the
item
they
are
going
to
submit
next
one,
please,
okay,
now
the
other
file
needed
to
properly
Define
and
draw
a
submission
process
is
the
submission
form
which
is
a
replacement
for
what
was
called
the
input
forms
XML
in
previous
versions
and
basically
in
this
file,
all
the
metadata
fields
that
will
will
eventually
appear
in
each
submission
form.
Step
are
defined
and
listed
here.
C
C
So
the
structure
of
this
file
is
this
one.
Within
the
form
definitions,
we
have
a
list
of
forms
of
form
entries
which
reflects
represent
a
part
of
the
submission
form
page
in
this
case,
a
part
of
the
accordion
we
have
seen.
We
are
going
deeper
next
slide
for
each
form,
one
or
many
rows
could
be
set
and
each
row
node
represent,
represents
a
row
to
be
displayed
within
the
submission
form,
and
this
is
all
customizable.
C
If
they,
it
is
possible
to
Define
many
fields
in
the
same
row,
because
the
Leaf,
let's
say
Leaf
node
of
the
row
of
the
row
component
of
the
row.
Node
is
the
field
and
for
each
node,
as
you
can
see
in
this
example,
it
is
possible
to
collect
many
metadata
to
display
many
input
fields
to
hold
metadata
next
slide.
C
C
C
The
new
aspect
is
that
the
workflow
steps
are
and
the
roles
are
whole
configurable
and
configured
as
string
beans,
as
since
the
display
7
is
built
using
spring
framework
in
the
workflow
XML
file
and
yeah.
So
the
it
is
possible
to
configure
the
a
given
workflow
a
custom
workflow
for
a
given
collection.
Next
one
please.
C
So
this
is
an
example
of
how
the
workflow
XML
file
might
look
alike.
We
have
been
defining
the
whole
workflow
in
this
case
the
defaultware.
The
steps
composed
in
the
world
right
are
listed
and
the
indication
the
reference
to
which
is
its
first
step
and
on
the
left
on
the
right
side,
we
have
a
diagram
representing
these
default
workflow
coming
out
of
the
box
with
display
7.
C
next
one,
please
so
going
deeper.
What
is
a
workflow
step?
How
how
What
defined
in
WordPress
ml
is
reflected
in
the
user
interface?
In
this
case,
we
are
reporting
a
brief
example
of
the
review
step
configuration
which,
for
which
is
defined,
how
the
the
staff,
the
task
step,
is
to
be
assigned,
if
so
to
users
and
which
actions
are
performed
and
most
important,
which
are
the
users,
which
is
the
role
representing
the
users
allowed
to
perform
this
step.
C
C
B
My
slides
there.
We
are
okay,
so
what's
next
for
7.x,
so
I
I,
already
kind
of
talked
about
this
alluded
to
this
earlier.
We
do
have
a
release
status
page
here
at
the
bottom
here
that
talks
about
every
single
7.x
release.
What
features
are
coming?
What
we're
working
on
all
that
sort
of
information
is
available
there.
So
I
want
to
highlight
that
first
off
that
that's
a
great
resource
for
you
to
go
to.
B
If
you
want
to
know
what's
coming
next,
but
as
I
mentioned
and
I
I
talked
about
briefly
beforehand,
but
I
want
to
stress
again
the
goal
of
d
space
7
is
really
about
rapidly
modernizing
the
platform
of
dspace,
so
we
are
adding
new
features
in
every
single
7.x
release.
I
know
this
is
different
than
in
the
past.
It
used
to
be
that
we'd
only
add
new
features
and
major
releases
7.x
is
a
is
different.
B
It's
about
a
rapid
modernization
of
our
framework
and
it's
a
a
different
sort
of
release
that
you
need
to
be
aware
of
the
reason
why
we're
approaching
it
this
way
is
that
we're
trying
to
add,
add
6.x
features
into
each
release.
Little
by
little,
we
could
not
re
wait
to
do
7.0
until
every
single
6.x
feature
was
in
it.
It
would
take
really
too
long
to
get
to
that
7.0
platform.
B
So
we
chose
this
approach
specifically
for
d
space,
7,
that
we
want
to
make
sure
that
we
are
getting
out
features
in
every
single
release
and
releasing
them
as
rapidly
as
we
can
to
allow
people
to
upgrade
as
soon
as
they
are
able
to
as
if
necessary.
There
are
times
that
coder
factors
may
occur
in
these
releases,
but
we're
trying
to
minimize
those,
and
we
will
document
them
in
the
upgrade
processes
when
they
occur.
B
B
7.7
would
be
around
October
as
soon
as
7.x
is
feature
compatible,
though
with
6.x.
That
is
when
we're
going
to
start
talking
about
what
comes
next
in
d
space
8.
at
this
point
in
time-
and
this
is
the
latest
and
greatest
news-
it
does
look
like
we
are
getting
close
to
Future
compatibility
and
it
may
occur
either
after
7.6
or
7.7.
B
So,
by
mid
next
year
expect
to
have
some
some
sort
of
General
announcement
about
what's
going
on
with
eight,
even
if
it's
just
that
we're
starting
the
planning
for
eight
and
what's
coming
next
so
d,
space
7
is
getting
close
to
that
level
of
having
all
the
features
of
six
again.
All
the
information
is
down
there
in
the
in
the
link
at
the
bottom,
in
terms
of
the
goals
for
seven
and
and
our
timelines,
and
all
that
I
do
also
want
to
note
that
there
are
places
that
you
can
contribute.
B
Dspace
is
an
open
source
project.
We
are
doing
our
best
to
move
rapidly
with
the
team
that
we
have
with
the
donations
and
funding
that
we
have
that
Natalie
mentioned,
but
we
also
could
use
people
at
times
ideas
at
times.
So
we
do
have
a
development
team
if
you're
a
developer
and
you're
interested
in
adding
in
a
small
feature,
fixing
a
small
bug.
Anything
and
everything
is
welcome
as
small
or
as
big
as
you
want.
To
give
your
time,
we
do
meet
every
Thursday
you're
not
required
to
even
attend
those
meetings.
B
If
you
just
want
to
send
a
small
bug,
our
way,
we'll
take
a
look
at
it
and
we'll
help
get
reviewers.
We
also
welcome
anybody
to
help
us
test
pull
requests
from
other
developers.
So
if
there's
a
bug,
that's
annoying
you
and
somebody
else
fixes
it
and
you
find
the
fix
out
there
on
GitHub
give
it
a
test.
B
Let
us
know
if
it
works
for
you
that
helps
us,
move
it
along
more
quickly,
if
you're,
not
as
technical
there's
opportunities
for
repository
managers,
also
to
gather
in
the
dspace
community
advisory
team
meetings,
they
meet
monthly
and
their
next
one
is
kind
coming
up
in
December
and
they
provide
a
lot
of
feedback
to
the
development
team
and
the
governance
about
next
steps
for
dspace.
The
development
team
also
asks
them
questions,
sometimes
about
features.
What
what's
important
in
a
feature?
What's
what
are
use
cases
things
of
that
nature?
B
So
if
you're
interested
in
that
sort
of
work
or
just
talking
with
others
who
use
dspace,
join
those
dcat
meetings
and
now
I
think
it's
time
for
us
to
go
ahead
and
open
things
up
for
questions
as
I
mentioned
and
promised
the
worksites
workshop
slides
for
this
slide.
Deck
are
here
immediately
Natalie
if
you're
able
to
copy
that
into
the
chat.
If
not
I
can
do
that
here
as
we're
going
through
questions
here
in
a
second.
B
A
One
second
I
translated
the
lens
that
people
put
in
there
from
Spanish
into
English
and
then
the
the
people
a
lot
of
folks
put
stuff
in
the
chat.
So
those
are
all
here
now
and
I
think
that
I
think
I
missed
a
few
that
were
in
Spanish,
but
some
of
these
I
think
that
people,
one
of
the
general
things
that
kind
of
was
coming
up
a
lot
was
this:
can
you
migrate
from
deep
space
CRS
to
7.4,
or
is
that
even
the
same
thing?
B
Sure
I
can
start
with
d
space
Chris
question
so
d,
space,
Chris
and
d
space
are
separate
products.
It's
worth
stressing,
so
Corrado
can
probably
answer
more
on
the
dspace
Chris
side,
because
d
space
Chris
comes
out
of
the
four
science
team.
It
is
built
on
top
of
dspace,
but
it
is
not
something
that
I'm
involved
with
directly
I'm
the
d
space,
Tech,
lead
and
Corrado,
and
the
fourth
science
team
help
out
with
dspace
Chris
I
did
before
we
talk
about
that.
B
But
as
of
this
moment,
there
are
two
separate
systems.
So
if
you
have
d
space
Chris,
you
are
running
a
separate
system
from
dspace.
They
are
very
similar,
but
it
is.
It
is
a
separate
system
and
so
Corrado
I,
don't
know.
If
you
wanted
to
answer
that
in
terms
of,
is
there
a
migration
path
from
an
old
version
of
dspace
Chris
over
to
d
space
7?
Is
that
possible
to
do
or
are
you
more
sticking
with
dspace
Chris
for
now.
C
B
B
So
yeah
I
would
recommend
for
folks
who
have
questions
about
dspace
Chris
get
in
touch
with
the
four
science
team,
since
they
lead
the
efforts
there.
I
I
would
not
be
able
to
help
you
as
much
with
that
particular
question.
Unfortunately,
but
it
is
a
good
question
to
note
that
those
are
two
separate
systems
and
understanding
the
differences
between
them.
B
A
Also
see
in
the
chat
recently
and
then
there
are
a
few
questions
in
the
document
relating
to
cyber
security.
So
are
there
any
updates
to
people
say
that
they're
facing
cyber
cyber
security
issues
and
it
teams
are
raising
concerns
how's
that
being
considered,
and
then
there
was
another
one.
Are
there
any
improvements
for
the
7.x
versions?
B
So
I'll
start
with
the
security
aspect.
I
mentioned
already
briefly,
that
every
single
code
change
that
goes
into
dspace
seven,
and
this
is
different
from
d
space
6
entirely.
Every
single
code
change
that
goes
into
d
space
7
goes
through
a
security
scan.
We
use
an
automated
security
scanner
right
now.
It's
a
tool
called
lgtm.com,
but
we're
migrating
over
to
github's
own
internal
security
scanning
capabilities,
which
is
replacing
that.
So
all
the
code
within
dspace
goes
through
a
security
scan.
B
We
also
receive
the
security,
notices
and
notifications
for
whenever
something
we
use
a
tool
we
use
has
a
security
loophole
and
we
patch
those
as
quickly
as
possible.
We
analyze
them
first
and
then
patch
them
in
the
next
release
and
have
actually
released
quick
patch
releases
in
in
extreme
scenarios.
So
like
when
the
log
for
J
breach
occurred.
There
was
a
quick
release
of
I.
Don't
remember
if
it
was
7.2
2
might
have
been
a
7.2.
B
There
was
a
7.2.1
to
patch
that
immediately,
so
folks
could
be
up
to
date
as
quickly
as
possible,
so
with
dspace
7.
We
are
monitoring
security
very
very
seriously
and
we
do
have
those
tools
in
place
to
try
and
keep
things
as
safe
and
and
secure
as
possible
at
all
times.
So
if
there
are
specific
questions
about
specific
security,
vulnerabilities
or
questions,
or
things
like
that,
we
do
have
an
email
address,
that
you
can
email,
which
is
security,
I'll
type
it
in
the
chat
here,
security
at
dspace.org.
B
B
If
you
see
an
issue
that
you're
concerned
about,
if
you
want
feedback
on
it
before
making
anything
public,
if
you're
concerned
about
something
you
can
email
us
at
securityspace.org,
we'll
analyze
it
and
get
back
to
you,
let
you
know
and
basically
that
that's
the
answer
to
in
terms
of
the
the
security
and
how
we're
monitoring
security,
but
I
do
welcome
feedback
on
that
from
anybody
who
does
have
feedback.
Send
it
my
way.
B
As
for
questions
about
New
Relic,
that's
a
tool,
that's
external,
to
deep
space!
I!
Think
some
people
do
use
it.
I.
Don't
know
enough
information
about
what
an
integration
with
New
Relic
looks
like
4D
space.
So
if
it's
as
easy
as
configuring,
New
Relic
for
dspace,
there
might
be
others
who
have
familiarity
with
New
Relic
in
terms
of
being
able
to
monitor
your
site.
I
do
know
there
are
a
ton
of
monitoring
tools
out
there
that
can
do
different
levels
of
monitoring.
I
mean
I.
B
Do
encourage
people
to
use
those
in
production,
but
I
don't
tend
to.
We
don't
tend
to
recommend
any
sort
of
specific
monitoring
tool
in
the
dspace
installation
or
upgrade
procedures
just
because
that
often
is
a
local
need
and
based
on
what
you
use
locally.
But
if
folks
do
find
that
there's
usefulness
and
if
there's
something
we
need
to
add
to
dspace
to
make
it
more
compatible
to
New,
Relic
or
other
tools.
Let
us
know
you
can
create
a
ticket
and
GitHub
or
you
can
even
send
us
code
if
there's
a
small
change.
B
B
A
B
You
have
a
lot
of
options
in
terms
of
whether
you,
whether
you
want
to
install
the
front
end
and
back
end
on
the
same
server
or
on
separate
servers,
or
you
can
use
Docker
as
I
mentioned,
to
do
different
containers
for
them.
Any
of
those
are
completely
available
to
you
and
it's
really
kind
of
a
local
decision
to
be
honest,
whether
you
want
to
run
them
on
the
same
server
or
separate
servers,
you
can
do
the
front
and
the
back
end
on
the
same
or
on
separate.
B
It
really
does
not
matter
in
terms
of
the
behavior
of
dspace.
If
they
are
on
the
same
server,
you
probably
do
need
to
have
a
pretty
powerful
server
in
terms
of
memory
and
CPUs.
We
have
some
rough
Performance
Tuning
guidelines
on
that
and
some
rough
recommendations
on
this
link
that
I'm
sending
out
to
everybody
right
now.
There's
a
performance
stream
page
on
dspace,
for
that
has
some
tips
for
DSP
7
already.
We
are
working
on
improving
this
constantly.
B
So
as
we
get
feedback
from
users
of
dspace,
seven
people
using
production
things
they
found
useful.
This
gets
updated
on
a
regular
basis.
So
if
you
have
feedback,
you
want
to
add
into
this
or
suggestions
if
you've
already
started
your
upgrade
or
once
you've
started,
your
upgrade
I
welcome,
sending
those
suggestions
my
way.
B
Basically,
this
is
a
page
that
allows
us
to
gather
that
feedback
together
and
provide
recommendations
and
that
feedback
right
now
is
mostly
out
of
early
adopters
for
deep
space
7
out
of
the
people
in
the
development
team
who
host
their
own
d
space
7
instance
already
things
that
they've
found
and
as
I
said
they
we
will
update
it
as
we
go.
But
that's
where
the
latest
recommendations
are
I
did
see.
Also
a
question
here
about
a
Linux
installation
package.
B
I
will
admit
there
that
I
don't
have
enough
I
I,
don't
have
enough
knowledge
about
what
it
takes
to
build
a
Linux
installation
package
for
for
a
web
application
like
dspace,
dspace
I,
think
the
challenge
there
would
be
making
it
still
configurable
and
customizable,
which
we
hear
deep
space
users
want
a
lot.
So
if
there
are
people
out
there
who
know
who
have
good
examples
of
a
Linux
installation
package
and
ways
that
we
that
are
there's
an
installation
package,
that's
similar
in
some
way
to
dspace-
that's
something
we
could
consider.
B
We
haven't
considered
that
in
the
past,
because
we
find
that
there
is
a
number
of
operating
systems
that
people
want
to
run
dspace
on
and
because
of
those
need
for
high
level
configuration
or
not
high
level,
very
detailed
configuration
as
well
as
detailed
customization,
including
theming,
branding
all
that
sort
of
stuff.
So
we
tend
to
lean
more
towards
that
Docker
approach
of
we
have
some
Docker
scripts
to
allow
you
to
spin
things
up
quickly.
You
can
build
off
of
those
and
and
and
utilize
those
for
product
action,
as
you
may
may
want
to.
B
I,
did
see
a
question
in
chat
here
about.
Can
you
migrate
directly
from
dspace
5
to
d
space
7?
Yes,
you
do
not
need
to
go
3D
Space
six!
You
can
even
migrate
directly
from
four
to
seven
or
three
to
seven.
You
don't
need
to
go
to
through
all
those
versions
in
between,
but
I
do
recommend
that
you
read
the
release
notes
for
all
those
versions
in
between,
because
sometimes
there
are
significant
changes
that
will
impact
you
during
the
upgrade.
B
So
for
that
d,
space,
five
to
seven
jump,
you
need
to
be
aware
that
in
d
space
6
the
the
configuration
change
significantly
to
use
a
local
CFG
file
that
same
configuration
is
in
place
in
d
space
7..
So
you
can
make
that
jump.
But
you
need
to
understand
what
changes
happen
in
d
space
6
to
the
configuration
because
you'll
see
those
same
changes
in
d
space,
7.
C
B
Sure,
let
me
bring
it
up
in
my
browser
here
since
I'm
sharing
my
other
screen
here,
I'm
going
to
pull
this
over
okay.
So
all
of
our
tickets
are
in
GitHub
these
days
so
that
we
have
two
GitHub
repositories,
one
for
the
front
end
and
back
end.
Where
you
submit
a
ticket,
really
doesn't
matter
to
me
or
to
anyone
else.
We
can
move
it
around
as
needed,
but
generally
speaking,
there's
issue
pages,
so
the
angular
dspace.
B
If
I
can
spell
today,
there's
an
angular
issues
section
for
angular
issues
and
there's
a
dspace
issue
section
for
the
back
end
issues
you
can
add
tickets
into
here
with
a
GitHub
account.
You
can
create
a
new
issue
when
creating
an
issue.
You
have
an
option
of
submitting
either
a
bug
report
or
a
future
request,
or
you
can
even
report
a
security
vulnerability
which
will
send
us
to
send
you
to
the
email
list
about
that.
B
So
this
is
how
you
would
report
an
issue
you
can
send
it
in
either
place
when
you're
reporting-
something
that's
like
a
bug
report.
It
will
ask
you
information
about
describing
the
bug.
We
need
information
about
how
to
reproduce
it
and
you
can
add
additional
details
as
as
well,
so
that
allows
us
to
better
reproduce
the
bug,
so
we
can
fix
it
quicker
if
you're
asking
for
a
future
request,
it's
a
different
sort
of
form.
So
it's.
B
Why
is
this
feature
important
to
you
describe
what
the
solution
might
look
like
describe
other
things
or
work
around
you
might
have
considered,
and
that
allows
us
to
gather
some
of
the
basic
use
cases
to
allow
us
to
get
more
information
about
that.
I.
Do
want
to
stress,
though,
that
creating
tickets
is
a
wonderful
way
to
give
us
feedback,
but
but
it
is
a
open
source
product.
B
But
you
are
still.
If
you
don't
have
developers
on
staff,
you
can
create
those
tickets,
we'll
analyze
them
and
prioritize
them.
The
way
we
work
is
while
we're
talking
about
this
is
we
have
our
own
set
of
project
boards
in
our
in
our
dspace
repository.
These
are
linked
from
that
status,
page
that
I
that
I,
provided
you
earlier
about
finding
the
status
of
of
7.x
releases,
but
right
now
we're
working
on
a
7.5
project
board
and
we
have
developers
claiming
things
and
working
on
things
on
that
board.
B
We
have
things
that
are
already
in
the
review
stage,
so
they
either
need
reviewers
assigned
or
they're
in
the
review
process.
We're
testing
reviewing
them.
People
can
also
jump
in
and
help
out
on
this
board.
This
is
where,
where
you,
we
do
a
lot
of
work
in
our
meetings
on
our
developer
meetings,
but
you're
welcome
to
contribute
outside
those
meetings.
If
you're
not
able
to
join
us
in
a
meeting,
you
could
review
something.
That's
in
our
under
review
column
tell
us
what
you
think
you
could
look
at
our
to
do
column
and
claim
something
there.
A
B
B
There
is
the
tech
support
group
that
Natalie
linked
there's
a
support
page
here
that
provides
you
every
single
support
option
based
on
what
type
of
support
you
need.
Some
of
them
may
lead
you
to
the
documentation,
often
you're
led
to
that
Google
group
that
Natalie
linked
into,
but
there's
also
information
about
how
to
get
the
training
Workshop
materials
we
link
into
here.
We
also
have
information
about
if
you
want
to
hire
somebody
to
customize
your
d
space,
how
to
find
the
registered
service
providers
how
to
report
security
vulnerabilities.
B
Foreign,
let's
see,
if
there's
any
other,
we
got
a
couple
more
minutes
about
six
more
minutes
here.
I'm,
seeing
trying
to
see
I
see
a
lot
of
thank
yous
and
yeah
I
see
a
question
about:
will
all
the
questions
that
cannot
be
answered,
maybe
answered
in
writing?
Yes,
they
will.
They
will
be
answered
on.
Let
me
get
this
out
of
the
way
this
questions
doc
here
at
the
bottom
of
this
slide,
please,
if
your
question
is
not
made
it
into
that
question
doc.
B
If
we
missed
it,
there
was
a
lot
of
chat
flying
by.
If
we
missed
your
question
in
the
chat,
add
it
into
that
questions.
Doc
and
I
will
make
sure
it
does
get
an
answer
there
keep
in
mind
after
yesterday's
session,
There
Was
80
questions.
So
it's
going
to
take
me
some
time
to
comb
through
all
of
these
I
will
get
to
it.
B
Oh,
it
says
the
question
about
just
to
make
sure
the
embedded
media
feature
for
for
default
for
7.x
versions.
Yes,
the
embedded
media
viewer
that
you
saw
is
in
all
7.x
versions
since
I
think
7.2.
Maybe
it's
it's
default
disabled,
but
it's
very
easy
to
enable
Corrado
noted
that
you
set
a
flag
to
true,
and
that
turns
on
the
video
viewer
and
there's
also
an
image
viewer
there
as
well,
so
that
is
enabled
or
possible
to
enable
very
quickly
and
rapidly
in
d
space
7.
If
you
need
that.
B
A
sec
I've
seen
a
lot
of
thank
yous
in
the
chat.
The
recording
will
be
available
later
this
week
likely
or
early
next
week.
That's
the
recording,
along
with
the
slides
for
all
three
presentations,
will
be
available
to
everybody
and
it
will
be
publicly
posted
also
on
our
Wiki
and
I
think
there
may
be
and
even
be
like
some
tweets
and
blog
posts
about
it
as
well.
So
you
will
get
the
video
and
all
the
materials
that
we
have
here.
B
A
B
But
I
do
take
breaks
and-
and
that
said
actually
for
those
of
you
looking
for
questions
for
me-
I
realized
I'm
off
next
week
for
the
Thanksgiving
holiday,
so
I'll
get
as
much
done
this
week
as
I
can
I
will
get
other
other
things
answered
after
the
Thanksgiving
holiday
for
local
Fields.
Could
they
be
easily
migrated
to
newer
versions?
Yes,
the
metadata
framework
is
the
same
and
d
space
7
as
it
has
been
in
the
past.
B
B
B
Well,
thank
you
all
for
for
your
participation
today,
I
see,
I
saw
it
at
one
point
in
time
we
had
up
to
about
450
people
in
here
which
has
been
wonderful
to
see
that
much
interest
in
the
upgrade
process.
I've
seen
a
lot
of
thank
yous
in
the
chat,
so
just
want
to
say
thank
you
back
to
you
all
and
as
Natalie
mentioned,
if
you're
finding
these
useful,
please
do
consider
trying
to
become
a
supporter
of
dspace.
B
Have
your
institution
become
a
member
help
us
out
through
code,
there's
also
the
dspace
Development
Fund,
which
was
mentioned
earlier
in
the
slides
that
can
help
it
that
helps
us.
Do
quicker
development
on
dspace
seven
and
help
us
fund
some
of
that
development.
So
those
are
ways
you
can
really
help
us
out
to
make
deep
space
even
better,
but
we
appreciate
all
your
support
and,
and
all
your
time
today
as
well
and
I,
think
we're
probably
writing
out
a
to
go
ahead
and
wrap
up.