►
From YouTube: DSpace 7.6 Live Question and Answer Session
Description
In this recording, DSpace Technical Lead Tim Donohue and DSpace Program Coordinator Natalie Baur hosted a DSpace 7.6 question and answer session with the DSpace Community on July 19, 2023. This free webinar will review the latest DSpace release and answer community questions about DSpace 7.6.
A
A
A
Okay,
without
any
further
Ado,
we'll
begin
Tim.
Can
you
do
the
next
slide,
so
just
a
quick
announcement
that
these
releases
and
functionality
improvements
are
made
possible
through
contributions
from
the
community,
especially
to
the
dspace
Development
Fund.
This
allows
us
to
have
more
predictable
releases,
Greater
Community
and
Greater
Community
oversight
of
development
outcomes.
A
Dspace
is
for
and
by
the
community.
You
can
also
contribute
to
the
dspace
Development
Fund
by
becoming
an
Institutional
member
of
dspace,
increasing
your
membership
level,
one
time
or
recurring,
and
making
a
one-time
contribution,
institutional
or
individual
to
the
Development
Fund,
and
you
can
contact
us
at
the
email
address,
listed
below
or
check
out
our
Wiki
for
more
information
and
I'm
going
to
hand
things
over
to
Tim
Donahue.
Our
lead
tech
lead
for
dspace
who's
going
to
guide
us
through
this
question
and
answer
session
and
also
give
us
some
quick
updates
on
dspace
7.6
release.
A
B
B
I'll
make
sure
that
the
questions
that
are
asked
in
that
document
either
are
answered
today
or
will
be
answered
after
this
session
if
they're
a
little
bit
more
detailed
or
I
have
to
dig
into
finding
the
answer
myself,
but
the
questions
in
there
will
get
answered,
so
you
can
keep
that
as
a
link
that
you
can
refer
back
to
for
any
of
the
questions
that
are
already
there
or
you
can
continue
to
add
them
throughout
this
session.
Here.
B
But
first
I
did
want
to
note
that
we've
had
seven
releases
in
two
years.
So,
if
you've
been
keeping
track
of
all
of
these
releases
that
have
been
coming
out,
there's
a
lot
of
new
features
that
have
come
across
everything
they've
come
across
in
d
space,
seven,
so
lots
of
new
features
layered
into
every
single
release.
B
If
you're
already
on
one
of
these
releases,
you
may
want
to
upgrade
to
the
latest,
because
there
are
even
more
new
features
that
have
come
out
within
7.6
and
I
also
wanted
to
quickly
highlight
some
of
the
reasons
why
we
highly
recommend
you
upgrading
to
dspace
7
as
soon
as
possible.
If
you
haven't
already
or
did
you
space
7.6,
these
are
things
that
I've
gone
through
and
past
q
a
sessions,
but
it's
good
to
kind
of
revisit
them.
B
First,
just
noting
you
know,
we
have
the
single
user
interface
that
is
built
with
web
best
practices
in
terms
of
accessibility
in
terms
of
search
engine
optimization
and
everything
like
that.
We
have
an
integration
ready,
rest
API.
We
have
the
new
configurable
entities,
features
which
I'll
talk
about
a
little
bit
here
today,
you
can
upgrade
from
any
Past
release.
Your
data
will
move
over
in
a
more
automatic
fashion
from
the
database
and
it's
also
backwards
compatible
with
your
old
Integrations,
and
we
do
our
best
to
align
with
repository
best
practices.
B
Sorry
I
got
a
little
bit
of
a
frog
in
my
throat,
let's
see
but
10
features
also
that
are
not
available
in
d
space
6
or
below.
To
be
aware
of.
Are
these
10
right
here?
This
is
just
there's
many
more
that
are
that
are
not
listed
here.
These
are
the
top
10
that
I
could
think
of.
I
mentioned
the
rest
API
the
configurable
entities.
We
also
have
orcid,
authentication
and
synchronization
with
your
orcid
profile.
There's
now
triple
AF
support
or
you
can
use
use
a
basic
image.
B
Video
audio
viewer
either
one
of
those
or
both
of
those
are
possible
to
enable
you
can
run
many
of
the
command
line
scripts.
Now
from
a
new
processes
menu,
we
have
the
ability
to
pre-register
handles
and
dois
I
mentioned
open
air
researcher
profiles
is
now
a
thing
in
d
space
7,
where
you
can
have
your
own
profile
and
d
space
that
can
sync
up
optionally,
with
orcid
with
your
orcid
profile.
B
We
have
new
forms
of
authentication,
not
just
orcid,
but
also
open,
ID
connect,
and
we
have
a
lot
of
great
ways
to
import
metadata
from
external
Services,
some
of
which
are
mentioned
here.
This
allows
you
to
get
a
submission
started
very
rapidly
because
you
don't
have
to
do
as
much
manual
entry
of
the
metadata,
so
these
are
kind
of
10,
more
reasons
to
go
to
good
up
to
dspace
seven
as
soon
as
you
can
so
what's
new
in
7.6
that
just
came
out
a
little
less
than
a
month
ago,
back
in
June.
B
These
are
the
four
biggest
features
that
you'll
see
in
7.6.
The
batch
or
policy
management
tool
allows
you
to
manage
privileges
across
many
different
Community,
Collections
or
items
at
once,
so
that
you
can
quickly
and
easily
embargo
many
items
at
once
or
embargo
many
bit
streams
or
files
at
once.
You
can
also
remove
embargoes
or
access,
restrict
everything
at
once
or
remove
access
restrictions.
It
allows
you
a
lot
of
those
management
of
permissions
in
a
much
easier
fashion
and
this
tool
has
been
completely
rebuilt
and
redesigned
in
deep
space.
B
B
Just
to
give
you
a
sense
of
what's
there,
we
also
newly
added
signposting
the
scholarly
web,
which
is
a
best
practice
from
core
to
allow
dspace
to
represent
what
objects
are
included
or
how
to
how
to
get
information
about
objects,
metadata
about
various
objects
and
links
to
their
files
via
these
signposting
links
and
headers.
There's
much
more
information
on
the
links
that
are
in
this
slide,
but
we
support
the
fair
sign.
Posting
level
sign
posting
profile
level.
B
Two
I
mean
I,
should
mention
I'm,
going
to
pause
here
for
a
moment
to
mention
these
slides
will
be
available
after
this
session.
So
there
are
a
lot
of
links
and
within
this
slide,
you'll
have
this
all
available
to
you.
Afterwards,
you
don't
need
to
copy
anything
down.
You'll
have
this
available
immediately
after
the
session,
we
also
have
primary
bitstream
support.
So
by
default
in
d
space
7,
the
very
first
bit
stream
or
very
first
file
in
your
list,
is
the
one
that
is
used
for
things
like
thumb,
thumbnails
or
full
text
searching.
B
B
And
this
gives
you
a
little
demo
of
that
bulk
Access
Control
Management
feature
from
the
admin
menu
and
it's
going
to
show
us
a
searching
across
Collections
and
communities
and
items
you
can
select
multiple
here,
so
we
can
select
a
couple
collections.
We
want
to
manage
permissions
Within
and
then
at
the
bottom.
B
You
can
also
use
that
same
tool
as
I
mentioned,
to
remove
permissions,
but
you
get
a
nice
little
report
out
here
of
what
permissions
were
updated
for
which
items
this
is
just
the
the
video
starting
over
again
and
showing
it
from
the
admin
menu
and
also
it's
not
only
available
from
the
admin
menu,
but
I
have
a
second
one
here.
That
shows
that
you
can
do
these
same
permissions
management
management
from
the
item,
Access,
Control
tab
or
even
the
community
and
collection.
B
So
this
is
it
again
just
showing
from
the
edit
item
screen.
There's
this
new
Access
Control
tab
that
same
tab
is
on
this:
the
collection
and
the
community
screens
that
allows
you
the
same
sort
of
capabilities.
So
this
is
one
of
the
features
we're
most
excited
about
within
the
7.6
release.
It
took
a
lot
of
effort
and,
like
I
mentioned,
it
was
a
complete
redesign
from
what
was
in
deep
space
six.
So
we
hope
that
it's
a
lot
easier
to
use.
Now
within
d
space,
7.
B
With
the
7.6
release,
I
also
want
to
highlight
and
mention
again
that
d
space
7
is
now
considered
feature
complete.
So
all
of
the
old
d
space
6
features
that
we've
been
porting
little
by
little
into
the
dspace
7
release,
all
those
top
three
tiers
which
are
the
highest
priority,
medium
high
and
medium
priority.
All
of
those
have
been
more
ported
over
to
d
space
7
and
the
medium
low,
almost
everything
except
for
maybe
one
has
been
ported
over
and
there
are
some
low
priority
things
that
have
not
been
ported.
B
So
there's
only
a
couple
features
that
existed
within
dspace
six
that
are
not
in
d
space
7.
most
of
those
are
quite
low
priority
and
we
don't
anticipate
them
impacting
many
users.
It
is
still
possible
for
those
to
get
into
dspace
8,
which
I'll
talk
more
about
later
on,
but
we're
waiting
on
volunteers
for
those
very
low
priority
features
just
simply
because
we're
not
really
sure
who's
even
using
them
anymore,
which
is
why
they're
such
low
priority,
but
but
if
you
are,
are
using
them
or
find
you
need
those
features.
B
There
are
opportunities
to
contribute
that
back
either
by
adding
the
code
yourself
or
hiring
a
service
provider
or
talking
a
little
bit
with
the
steering
committee,
and
we
can
look
at
how
we
could
potentially
prioritize
things
for
the
future
with
all
this
said,
this
means
that
d
space
7
is
entered
maintenance
mode,
so
we
will
not
have
any
new
features
added
to
dspace,
seven
after
that
7.6
release.
This
will
make
the
upgrades
within
d
space
7
a
lot
easier.
B
B
Yet
these
tips
are
all
based
on
the
dspace
7
upgrade
webinar
that
we
had
last
year
in
November,
so
I'd
still
recommend
going
back
and
looking
at
that
webinar
if
you
need
additional
help
or
want
a
little
bit
more
tips
or
hints
during
your
upgrade
process,
there's
a
lot
of
a
lot
of
good
information
back
in
that
webinar,
but
the
tips
that
I
have
here
provide
some
of
the
summary
information
of
what
came
out
of
that
as
well.
As
recently
asked
questions
on
on
lists
around
excuse
me
around
some
of
those
tips.
B
Let
me
get
a
quick
drink
of
water
here,
okay,
so
let's
go
through
a
couple
of
these
tips
here.
The
first
thing
I
mentioned
this
already,
but
it
does
come
up,
is
whether
or
not
you
can
upgrade
from
any
old
release.
As
I
mentioned,
your
backend
data
will
automatically
upgrade
via
our
database
migration
Scripts.
B
If
you
are
upgrading
from
a
version,
that's
older
than
d
space
6,
you
might
want
to
consider
starting
with
fresh
configuration
because
there's
a
new
local
CFG
file
that
was
added
in
deep
space
6.
That
makes
configs
a
lot
easier
to
manage,
so
you
might
want
to,
during
the
upgrade
start
fresh
with
a
brand
new
local
CFG
and
copy
your
old
configs
over
into
that.
I
would
also
recommend
reviewing
the
release,
notes
for
each
of
the
versions
you're
jumping
over,
like
if
you're
going
from
four
all
the
way
to
7.
B
B
There
are
two
upgrade
options
available,
so
you
can
upgrade
in
place.
We
have
our
upgrade
guide
in
the
documentation
that
talk
walks.
You
through
upgrading
all
the
prerequisites,
doing
the
upgrade
to
the
back
end
and
then
installing
the
front
end.
So
that's
option
one.
The
second
option
is
to
actually
start
fresh
where
you
can
install
dspace
7
fresh
with
no
data
within
it,
install
just
the
front
end
and
the
back
end
and
then
once
you're
comfortable
with
that
front
and
back
end
once
you're
sure
it's
running
it
looks
good.
B
You
can
migrate
your
existing
data
over
into
it.
Either
option
is
possible
and
people
choose
either
different
options
for
different
reasons.
It
really
is
a
matter
of
kind
of
looking
at
both
options
and
deciding
which
one,
you
think
would
work
best
for
your
institution
and
we
do
have
a
migration
guide
there
that
last
link
to
migrate.
Existing
data
link
links
you
over
to
the
migration
guide,
which
walks
you
through
how
to
migrate.
B
B
Video
I
gotta
get
her
off
the
table
here,
but
in
terms
of
starting
fresh
versus
upgrading
in
place,
we
do
recommend
that
from
the
scale
of
this
upgrade,
you
really
should
consider
whether
starting
fresh
would
be
easier
for
you,
because
in
some
ways
it
can
be
an
easier
way
to
get
familiar
with
d
space
7
and
understand
the
setup.
So
you
get
more
comfortable
with
the
installation,
the
setup
and
the
configuration
before
you
go
live.
B
So
this
is
something
I
would
recommend
for
folks
who
are
feeling
uncomfortable
about
the
upgrade
process,
or
just
feel
that
d
space
7
has
too
many
new
things,
and
you
want
to
get
more
comfortable
with
it.
It
is
completely
reasonable
to
go
with
this
approach,
so
I
would
recommend
really
considering
this.
If
that's
where
your
institution
sits.
B
This
has
come
up
several
times
as
well
as
to
whether
you
need
to
run
the
front
of
them
back
and
on
different
servers
or
the
same
server.
Either
approach
works,
so
you
do
not
need
to
have
them
on
different
servers.
You
can
choose
which
approach
works
best
for
you.
They
could
be
in
the
same
server
if
you
wish
they
can
be
on
different
servers.
B
This
comes
up
frequently
as
well.
In
fact,
I
think
I
saw
a
question
on
this
in
the
Q,
a
document
as
to
whether
you
can
run
dspace
7
via
Docker.
You
can,
and
there
are
institutions
that
are
already
doing,
that
we
do
have
a
Docker
scripts
that
are
available
in
our
front-end
and
back-end
code
base.
Right
now.
Those
are
really
development
oriented,
so
you're
welcome
to
repurpose
them
and
reuse
them.
A
lot
of
the
concepts
you'd
need
to
run
d.
Space,
7
and
Docker
are
already
in
those
scripts.
B
There
are
probably
going
to
be
updates
that
will
be
required
to
allow
you
to
run
it
in
production.
We
do
not
have
an
out
of
the
box
installation
or
upgrade
process
via
Docker,
but
you
can
very
easily
run
dspace
7
via
Docker.
So
if
your
team
is
very
comfortable
with
docker,
please
take
a
look
at
our
scripts
feel
free
to
use
reuse
as
much
as
you
want
and
and
go
with
the
deployment
and
that
approach,
because
it
is
a
a
nice
way
to
set
up
d
space
7.
B
This
is
a
new
tool.
Pm2
is
a
brand
new
tool
within
the
dspace
7
user
interface.
So
we
have
had
Institute
institutions.
Ask
do
I,
need
this
process
manager
to
run
the
user
interface.
It's
a
process
manager
tool
that
runs
any
node.js
app
and
the
front
end
is
a
node.js
application.
We
do
recommend
installing
it
with
pm2.
In
fact,
this
is
part
of
the
installation
instructions
that
we
have.
It's
not
a
required
tool.
B
You
could
use
other
tools,
but
the
thing
that
we
like
most
about
pm2
is
the
cluster
mode,
which
allows
you
to
scale
the
user
interface
and
get
much
better
performance
out
of
it
that
many
of
the
other
node.js
process
Manager
Tools.
So
we
would
highly
recommend
you
use
this
tool
and
get
comfortable
with
it
and
look
at
the
cluster
mode
as
well,
because
that
does
help
scale
and
and
performance
wise.
But
you
can
use
other
tools.
B
You
just
may
want
to
make
sure
that
they
have
similar
functionality
to
be
able
to
deploy
that
front-end
and
there's
much
more
information
on
pm2
in
the
installation.
Instructions,
including
links
over
to
it
and
all
of
that,
and
in
fact,
I
want
to
bring
this
up,
because
this
has
come
up
recently
on
mailing
lists.
There's
been
some
sites
that
have
once
they've
scaled
things
up
and
they've
got
they're
gone
to
production.
They
have
lots
of
content
coming
in.
They
have
lots
of
users
hitting
the
site.
B
They've
noticed
that
the
home
page
starts
loading
a
little
bit
slowly
and
usually
that
is
one
of
these
first
two
things
in
terms
of
something
that
you
may
have
skipped
over
or
overlooked,
or
you
may
want
to
try
to
help
scale
even
better.
Usually
it's
either
that
you're
not
running
pm2
in
that
cluster
mode,
which
provides
much
better
performance
or,
as
of
7.5,
there's
a
caching
option
that
we
have
in
the
user
interface
that
allows
you
to
Cache
the
pages
for
anonymous
users.
B
Only
so
when
Anonymous
users,
or
even
when
Bots
come
to
your
site,
they
get
a
slightly
cached
version
of
your
site.
It's
only
a
couple
seconds
old
I
mean
you
can
actually
configure
how
old
you
want
that
cache
version
to
be,
but
that
provides
a
lot
better
performance,
especially
on
the
home
page
or
any
page.
That
has
a
lot
of
content
on
it,
so
you
might
want
to
consider
looking
at
that
caching
option
and
also
that
cluster
mode,
because
those
two
together
usually
solve
the
majority
of
those
problems
that
we've
seen
so
far.
B
That
is
a
great
guide
and
it's
constantly
kept
up
to
date
with
tips
we've
learned
or
as
people
are
installing
stuff,
if
they
run
into
a
new
problem
seen
before,
and
we
figure
out
a
way
around
it.
We
update
it
in
the
performance
tuning
documentation,
but
you
may
want
to
keep
an
eye
on
that
page,
because
there's
lots
of
tips
for
how
to
make
dspace
perform
better,
both
from
the
front
end
and
from
the
back
end
and
how
to
kind
of
tune
things
for
your
needs.
B
I
mentioned
this
in
past
webinars
as
well,
but
it
comes
up
a
lot.
A
lot
of
people
looking
at
the
upgrade
for
d
space,
7,
look
at
the
new
configurable
entities
feature
and
wonder
whether
or
not
they
need
to
do
every
a
migration
over
to
everything
to
entities
or
what
they
should
be
doing
with
all
the
rule.
D:
space,
6
content,
as
they
update
to
d
space
7..
So
I
do
want
to
talk
about
this
and
revisit
this
again.
Just
with
you
all
here.
B
First
off
it
is
worth
noting
that
entities
are
still
an
advanced
feature.
They
are
a
very
useful
feature
and
if
you
need
this
feature,
I'd
highly
recommend
updating
as
titty
Space
7
and
using
entities.
However
they're
an
advanced
feature
because
they're
they're
new
and
they're
not
built
into
every
single
aspect
of
dspace
7,
yet
that
stuff
we're
working
on
so,
for
example,
the
archival
information
packages,
aips,
don't
yet
support
entities
fully.
B
They
support
some
of
the
basic
metadata
capturing
of
of
of
the
item
level
metadata,
but
they
don't
support
representing
all
the
relationships
between
entities.
So,
if
you're
very
dependent
on
aips,
that's
a
limitation
to
be
aware
of,
we
don't
have
any
sort
of
bulk
migration
at
this
point
in
time,
you
can
migrate
individual
items,
one
by
one
and
there's
some
tips
about
that
in
the
configurable
entities
docs.
But
essentially
it's
just
a
single
metadata
field.
B
You
can
change
in
the
item
to
transform
it
into
an
entity,
but
there's
not
a
bulk
migration
script
at
this
point
in
time,
and
you
also
need
to
set
up
your
collections
in
order
to
use
entities
properly
so
for
every
entity
type
you
want
to
use.
You
need
to
have
at
least
one
collection
that
can
accept
that
type
of
entity
from
a
submission
or
deposit
standpoint.
So
those
are
just
some
limitations
to
be
aware
of
and
because
of
those
limitations
it's
worth
going
through
when
you
might
want
to
enable
entities
versus
disable
them.
B
So
if
you
are
really
dependent
or
really
excited
about
using
the
researcher
profiles
or
the
syncing
your
local
profile
with
an
orchid
profile,
then
you
definitely
need
entities
because
those
both
require
entities.
We
cannot
do
that.
Sync,
with
Orchid
without
entities
and
researcher
profiles
are
basically
a
person
entity
page
that
is
associated
with
your
your
login
account.
B
So
you
would
need
entities
in
that
scenario
or
if
you
find
that
the
default
entities
that
are
set
up
within
dspace
that
are
provided
there
align
well
with
the
sort
of
content
you're
putting
in
you
might
want
to
consider
migrating
over
to
entities
sooner
rather
than
later.
But
it
is
worth
noting
that
you
do
not
need
to
migrate
all
your
content
to
entities
at
once.
You're
allowed
to
have
items
and
entities
living
together.
B
So
when
you
do
the
upgrade
process
from
d
space
6
to
d
space
7,
you
can
keep
all
of
your
old
d
space
6
items
as
just
basic
items.
If
you
want
to
and
start
to
add
brand
new
entities-
and
you
can
slowly
move
items
over
to
entities
if
you
feel
like
it
or
when
you
feel
like
it,
you
don't
need
to
do
this
all
at
once.
It
is
not
a
required
feature.
You
can
use
both
together
at
the
same
point
in
time
as
well.
B
So
that's
worth
being
well
aware
of,
even
if
you
enable
entities
you
don't
have
to
migrate
everything
into
it
and
you
might
want
to
keep
entities
disabled,
which
is
the
default.
I
should
note
if
you
depend
heavily
like
I
mentioned,
on
the
AIP
backup
and
restore
functionality.
If
you
really
just
aren't
interested
in
being
an
early
adopter,
you
don't
need
that
advanced
feature
for
any
particular
reason,
or
if
this
upgrade
already
looks
very
complex
to
your
institution.
You
can
upgrade
to
entities
at
any
point
in
time.
B
It's
very
easy
to
turn
them
on
and
enable
them
even
after
you've
upgraded
to
deep
space
seven.
So
if,
if
this
looks
daunting
to
you,
then
I'd
recommend
upgrading
to
d
space
7
with
entities
turned
off
initially
and
then
you
can
later
on
whether
it's
six
months
or
a
year
later,
you
can
say:
okay,
let's
try
out
entities
now
and
you
can
enable
them
at
that
point
in
time
and
begin
to
create
some
entities.
B
You
don't
need
to
do
it
all
at
once
and
again,
as
I
said,
even
once,
you've
enabled
entities
you
can
keep
all
your
old
items.
As
is
you?
Don't
need
to
migrate
them
to
entities
unless
you
want
to
so
there's
a
lot
of
options
available,
but
I'm
just
trying
to
alleviate
any
concerns
there.
That
entities
are
not
required
in
any
way,
and
it's
totally
up
to
you
what
approach
works
best
for
you
and
even
once
they're
enabled
you
don't
have
to
use
them
for
everything.
B
B
There
are
some
tips
there
for
how
you
can
migrate
to
postgres.
If
you
are
still
on
Oracle
and
I
know
that
there
was
at
least
one
institution
that
used
that
aura
2pg
tool
to
do
a
migration
there's
been
others.
Who've
used
just
the
AIP
backup
and
restore
that
works
as
well,
except
for
those
in
progress
submissions.
B
B
And
that
said,
if
you
run
into
issues
along
the
way
with
d
space
7,
there
are
lots
of
places
to
get
help
here.
These
are
some
of
the
common
questions
that
come
on
the
list
all
the
time,
so
the
UI
is
not
loading
or
it's
just
spinning
or
I
get
a
500
error.
What
does
that
mean
or
I
can't
log
in
or
I'm
getting
400
403
Forbidden?
These
sort
of
things
come
up
a
lot
and
we
have
guides
for
walking
through
these
problems.
So
there's
a
common
installation
issues
Link
at
the
bottom.
B
This
is
at
the
very
bottom,
the
install
process,
which
lists
all
of
these
errors
and
how
to
fix
them
or
different
options
to
look
at
with
fixing
them.
So
that's
the
first
place
to
look
if
you're
hitting
a
weird,
behavior
and
you're,
not
sure.
What's
going
on
go
to
that
common
installation
issue
see
if
it's
already
got
a
solution
there,
if
you
can't
even
figure
out
what
the
issue
is
or
why
the
UI
isn't
working
right.
If
something
weird
is
happening
in
the
user
interface,
that
troubleshoot
an
error
page
is
a
great
place
to
go.
B
It
walks.
You
through
how
to
find
the
underlying
error
that's
going
going
on
if
the
UI
is
not
loading
properly,
chances
are
there's
an
error
happening
either
in
the
user
interface
level
or
on
the
back
end,
and
that
troubleshoot,
an
error
page
walks
you
through
how
to
find
those
errors,
and
once
you
find
the
error,
it
might
be
one
of
the
ones
listed
in
that
common
installation
issues
page.
B
So
it's
worth
noting
that
these
resources
are
there
to
allow
you
to
try
and
help
yourself
as
much
as
possible,
and
we
keep
them
updated
based
on
things
that
we
see
that
have
come
up
frequently,
as
always,
there's
also
Support
options.
The
last
link
there
goes
to
our
list
of
Support
options,
which
includes
the
mail
list
slack
even
these
sort
of
webinars
and
other
documentation,
as
well
as
the
service
providers,
as
I
mentioned.
There
are
also
options
for
support.
B
If
you
want
to
pay
somebody
for
training
or
support
they're
there
to
provide
provide
that
to
the
community
at
Large,
so
you're
not
alone
ask
for
help
on
any
of
those
channels
and
take
a
look
at
what
we've
documented
already,
because
a
lot
of
the
problems
that
people
have
hit
into
are
common
problems
and
it's
chances
are
the
problem.
You're
hitting
has
probably
been
encountered
by
someone
else
as
well
and
hopefully
solved
along
the
way.
B
B
If
you're
interested
in
any
of
what's
going
on
with
development
activities,
those
meetings
are
completely
open
to
anybody
to
attend.
The
agendas
are
always
open
on
the
wiki
as
well.
We
meet
every
Thursday
you're,
welcome
to
just
jump
into
a
meeting
and
and
listen
in
if
you
want
you're,
also
welcome
to
join
us
on
slack
there's
a
Dev
Channel
there.
B
If
you
have
development
questions,
you
can
ask
them
there
and
we'll
get
somebody
get
an
answer
to
you
there
and
it's
worth
noting,
though,
that
the
members
in
those
Chan
that
both
the
channel
and
on
in
the
meetings
are
volunteering
their
time
to
to
build
improved
d
space.
So
it's
really
a
collaborative
effort.
B
We
do
have
that
deep
space,
Development
Fund
that
Natalie
mentioned
earlier,
where
we're
able
to
fund
a
portion
of
development
work
from
some
trusted
service
providers
at
times,
but
those
are
usually
feature
specific
development
and
the
majority
of
the
work
here
coming
from
service
providers
as
well
as
community
members
is
volunteer
oriented.
So
we'd
really
welcome
other
volunteers
to
get
involved
because
the
more
of
us
that
get
involved,
the
better
dspace
gets
and
the
more
quickly
it
gets
better.
B
The
options
there
are
really
to
donate
the
feature
yourself
or
look
at
that
d:
space
Development
Fund,
so
we
do
take
volunteer
work
from
anyone.
We
just
recommend
you
create
a
ticket,
and
let
us
know
that
you're
working
on
this
feature
so
that
we
don't
have
somebody
else,
do
the
same
work.
We
don't
want
two
people
building
the
same
thing,
we'd
like
to
avoid
that,
if,
at
all
possible,
service
providers
also
can
be
hired
to
build
things
on
behalf
of
Institutions
that
do
not
have
developers
available.
B
So
they
do
that
quite
frequently.
Many
of
the
larger
service
providers
that
we
work
with
all
the
time
will
build
a
feature
and
they'll
donate
it
back
to
dspace
and
it'll
come
out
in
the
next
release.
So
you
can
talk
to
them
about
what
features
you
need
built
and
and
sign
a
contract
with
them
to
make
that
happen.
B
7.0
had
the
most
code,
unique
control
code
contributors
by
far
because
it
was
a
massive
amount
of
work
through
several
betas
to
get
it
out
the
door
and
then
we've
slowly
been
ramping
back
up
to
about
the
50s
in
terms
of
each
release,
has
about
50
people
contributing
code
and
there's
other
contributors
that
come
in
along
the
way
as
well
contributing
documentation
translations.
This
is
just
the
folks
that
are
doing
code
for
us
right
now
and
I
do
anticipate
this.
B
This
will
keep
ramping
upwards
little
by
little
as
more
and
more
get
comfortable
with
dspace,
seven,
but
you're
definitely
not
alone.
If
you
want
to
try
and
jump
into
d
space
7
and
help
us
out,
we'd
love
any
volunteers
that
are
interested
in
doing
that
and
there's
a
lot
of
other
people
to
learn
from
here
along
the
way.
As
you
get
your
feet,
wet
with
d
space
development,
so
briefly
now
I
mentioned
d.
Space
7
has
entered
maintenance
mode.
B
The
next
release
is
going
to
be
a
7.6.1
release,
so
everything's
going
to
be
numbered
in
that
fashion,
based
on
7.6,
because
7.6
with
the
last
one
with
new
features.
So
we
are
only
providing
fixes
now,
whether
those
are
bug
fixes
usability
security
fixes
things
of
that
nature
can
go
into
seven
still,
but
no
new
features
along
the
way.
We
do
not
have
a
release
date.
Yet
for
that
7.6.1
release
we're
already
fixing
some
small
bugs
that
have
been
found,
but
that
release
date
will
be
announced
as
soon
as
we
feel
like.
B
We've,
we've
got
a
decent
group
of
bugs
fixed
up
that
we
can
release
out
to
get
Folks
up
to
date
on
the
latest
bug
fixes
and
to
that
point,
if
you
find
any
issues
along
the
way,
we
always
recommend
reporting
issues
you
found.
So
we
can
find
somebody
to
help
us
out
in
fixing
them
and
get
that
into
the
next
bug
fix
release
and
with
8.0,
as
I
alluded
to
we're
already
starting
to
discuss
8.0.
The
planning,
though,
has
just
begun.
We
just
got
7.6
out
the
door.
B
We've
been
restructuring
the
development
team
a
little
bit
in
terms
of
trying
to
get
ourselves
aligned
towards
both
maintaining
d
space
7,
as
well
as
new
development
for
d
space.
Eight,
so
we're
having
some
discussions
in
those
development
team
meetings
about
some
ideas
that
we
have
that
could
come
into
deep
space,
Aid
or
even
D
Space
Nine.
So
a
lot
of
this
is
really
in
the
early
stages,
but
eight
right
now
is
likely
to
include
new
features
that
miss
that
7.6
release.
B
There
were
some
brand
new
to
dspace
features
that
did
not
get
into
7.6.
They
had
never
existed
in
dspace
before
and
we're
looking
at,
bringing
those
to
d
space.
Eight
that
exact
list
is
still
under
discussion
within
steering
and
developers
are
also
talking
little
by
little
about
some
of
the
features
on
there
as
well.
B
It
is
worth
noting
that,
with
these
space,
8
we're
transitioning
back
to
our
release,
numbering
scheme
that
we
had
before
d
space
7.
This
means
that
new
features
will
only
be
in
that
8.0
release
after
8.0
goes
out
8.18.28.3.
Those
will
be
bug
fixes
only
and
that's
the
process
we'll
go
through
for
eight
for
nine.
For
ten
as
we
go
along
and
we're
also
going
to
have
one
major
release
a
year,
so
8.0
will
come
out
in
2024..
B
That'll
go
out
to
the
list
around
when
that
release
will
be
planned
to
come
out
and
what
features
we
think
is
are
going
to
be
in
that
release,
but
that's
all
happening
right
now
and
finally,
the
last
slide
is
really
how
you
can
help.
I've
mentioned
a
lot
of
these
things.
Already
we've
got
becoming
a
member
or
funding
the
dspace
Development
Fund,
which
we
mentioned
already
contributing
code.
In
that
developer
team
we
have
a
new
learning
dspace
documentation,
section,
which
the
dcat
team
has
been
working
on.
B
If
you're
interested
in
documenting
dspace
from
a
user
perspective,
there's
opportunities
there
to
con
to
contribute
documentation
there
and
enhance
what's
been
started
there.
The
dspace
community,
advisory
team
or
dcat
has
monthly
meetings
you're
welcome
to
join
them.
That
is
a
repository
manager,
interest
group,
so
they
discuss
how
how
institutions
use
dspace
what
they're
using
things
for
they
work
on
that
learning,
dspace
documentation,
sometimes
they're
discussing
the
upgrade
processes
or
things
they've
hit,
there's
different
topics
each
month
and
I'd
recommend
going
to
their
Wiki
page.
B
If
you're
interested
in
joining
any
of
their
discussions,
we
also
have
a
large
number
of
dspace
user
groups
that
have
popped
up
around
the
world.
So
you
may
want
to
look
at
our
user
group
page
to
see
if
there's
one
nearby
you
that
you
could
join
or
get
involved
with
as
always
report
any
issues
you
find
try
things
out
and
we
really
do
appreciate
supporting
others.
As
I
mentioned,
a
lot
of
the
work
in
deep
space
is
volunteer
based.
B
So
when
you
see
questions
on
mailing
lists
or
slack
that
you
know
the
answer
to
or
you've
run
into
and
figured
out,
if
you
can
answer
those
for
us
that
really
helps
things
out
a
lot
and
helps
build
a
stronger
net
community
and
helps
everybody
make
dspace
better
and
learn
dspace
together.
So
please
do
ask
questions
there,
but
also
help
others
out.
B
A
B
So
in
the
Q,
a
the
first
question
here
is:
how
long
do
you
support?
Dspace
7.6.x
is
7.6
7.6
and
LTS
release.
Yes,
it
is
an
LTS
release
and
that
it
will
be
supported
for
at
least
or
for
three
years
essentially
so
d
space
7
is
under
support
until
d
space.
Let's
see
eight
nine
until
d
space
10
comes
out,
so
every
release
of
d
space
by
default
is
supported
for
at
least
three
years
or
three
releases.
B
So
deep
space
seven
is
supported
while
d
space
8
is
out
while
D
Space
Nine
is
out
and
then
as
soon
as
10
is
released
three
years
after
the
fact.
That's
when
seven
would
go
out
of
support
and
same
with
eight
eight
would
be
under
support
until
d
space
11
comes
out.
So
that's
our
general
support
policy
that
did
change
a
little
bit
with
five
and
six
recently,
where
we
had
to
announce
that
they
were.
B
They
had
to
go
end
of
life
earlier
than
anticipated,
but
that
was
a
very
special
scenario
where
those
releases
were
so
very
old
that
it
was
becoming
incredibly
complex
to
support
them.
But
our
policy
has
been
a
3
year
release
or
three-year
support
policy,
and
that's
documented
under
that,
under
our
our
release
policy
and
that
release
numbering
scheme
as
well.
B
Let's
see
another
question:
did
I
hear
correctly
that
there
is
not
currently
a
way
to
bulk
transform
anything
into
a
configurable
entity.
Does
that
include
a
point
of
migration
from
seven
to
six
there's
not
a
way
to
change
authors
to
configured
persons
that
is
correct.
There
is
not
currently
a
way
to
both
transform
anything
into
a
configurable
entity.
B
If
you
had
an
old
Journal
hierarchy
represented
in
communities
and
collections
in
d
space
six,
we
don't
have
a
way
to
migrate.
Those
communities
collections
hierarchy
into
the
new
Journal
entities.
We
also
don't
have
a
way
to
migrate,
an
author
metadata
field
from
deep
space
6
into
a
new
person
entity.
Those
don't
exist
right
now
and
that's
why
I
mentioned
it's
an
advanced
feature.
B
B
B
Please
do
thank
you.
This
first
question:
I
I,
remember
this
being
on
mailing
lists
and
I
believe
there
was
some
answers
provided
there.
It
looks
like
Keith
Gilbertson
thanks
Keith
also
noted
that
it
fixed
fixed
for
him
when
he
just
logged
out
and
logged
back
in
I
think
there
might
be
a
caching
issue
there
when
you
first
update
to
do
space
7
out
of
five
or
seven,
not
six,
but
but
I
I
have
not
seen
that
behavior
long
term.
B
So
I
would
look
at
the
troubleshooting
guide
to
look
for
underlying
errors.
If
you're
having
weird
behavior
in
the
user
interface
always
take
a
look
at
that
troubleshooting
guide.
That
was
on
the
the
slides
that
I
had
today
and
I'll
share
those
slides
after
the
fact,
because
there's
pop
it's
possible
there's
an
error
underneath
that
is
causing
that
weird
Behavior.
B
But
that's
not
one
I
can
answer
here
quickly:
DOI
registration,
so
the
DUI
is
in
one
metadata
field
versus
the
other,
I
believe
DOI
registration
and
d
space
7
works
pretty
much
the
same
as
in
deep
space.
Six,
so
I
think
it
would
work
the
same
way
as
in
d
space.
6,
if
is
it
because
you
say
it's:
it
was
possible
in
older
versions.
I
think
it's
pretty
much.
B
B
Let's
see
new
version
has
a
lot
of
changes.
Is
it
possible
to
easily
export
a
list
of
documents
by
author
from
acute
current
community,
the
first
one
in
terms
of
exporting
documents?
The
best
way
to
do
that
in
d
space
7
is
probably
to
do
a
search
on
display
7
to
find
the
things
you
want
to
export,
and
then
you
can
export
them
to
CSV
from
the
search
results,
so
that
would
be
the
best
option
for
d
space,
7,
exporting
downloads
and
consults
I'm,
not
sure
I
understand
what
consults
are.
B
This
sounds
like
it's
statistics
right
now
and
there's
not
really
great
exporting
statistics
options
at
this
point
in
time,
but
I
can
revisit
this
after
the
the
the
chat
here
today
and
see.
If
there's
anything
else,
I
can
find
on
that
one
for
it's
possible
there's
a
bug
there.
It
looks
like
you're
sitting
translation
issues
on
particular
Fields
I,
don't
know
off
the
top
of
my
head
whether
those
fields
are
hard-coded,
it's
possible.
They
are.
B
We
have
run
into
this
in
the
past
where
accidentally,
some
text
in
the
user
interface
is
hard
coded
to
English.
That
is
always
an
accident.
We
never
want
it
to
be
hard-coded
to
English.
So
if
that's
the
case,
that
would
be
considered
a
bug
and
I'd
recommend
creating
a
ticket.
So
we
can
get
that
fixed
in
d
space,
7.6
dot
X,
so
that
would
probably
be
a
bug
if
that's
what
you're,
seeing
but
I'll
take
a
look
at
that
afterwards
as
well.
I
want
to
know
if
we
can
work
in
production
with
containers.
B
So
this
sounds
like
it's
related
to
Dockers
or
Docker
containers.
I
answered
that
a
little
bit
today
you
can
work
with
Docker
containers.
We
have
scripts,
you
can
base
your
work
on,
but
we
do
not
have
any
out
of
the
box
scripts
that
you
can
just
spin
up
yourself
in
production.
You'd
want
to
take
a
look
at
our
scripts
and
update
them
based
on
your
production
scenarios,
but
you
are
more
than
welcome
to
use
Docker
in
production
and
I
do
know
that
several
service
providers
use
Docker
in
production
and
some
institutions
as
well.
B
So
it's
it's
a
common
setup,
they're
relatively
common
six.
How
do
you
create
author
links
on
item
pages
with
authority
records
turned
on
I?
Think,
author
links,
author
links
happen
on
the
item
Pages
automatically,
but
I
don't
know
if
they
in
terms
of
linking
you
back
to
the
the
the
list
of
auth
or
the
list
of
other
items
from
that
author
I
think
they
happen
automatically.
As
of
7.5.
B
Maybe
I'll
have
to
go
back
and
look
I.
Don't
know
that
Authority
records
impact
that
but
I
might
be
misunderstanding
that
question
so
I
may
have
to
revisit
that
as
well,
but
I
believe
they
happen
pretty
much
automatically
on
our
demo
site.
You
could
look
at
demo
7.dspace.org
and
see
if
they're
already
appearing
there
and
if
so,
that's
a
feature
that
is
in
the
later
d
space
7
releases.
B
Yes,
it
would
be
possible,
so
the
rest
API
it's
worth
noting
is
has
every
single
feature
in
d
space,
since
the
user
interface
is
a
javascript-based
interface,
every
feature
it
uses
is
in
the
rest,
API
so,
and
that
also
means
you
could
build
scripts
against
the
rest
API
to
do
things
in
bulk.
So
if
you
can
do
it
once
you
could
build
a
loop
over
something.
It'd
require
your
own
coding,
but
you
can
code
it
in
whatever
language
you
want.
B
B
Let's
see
what's
the
best
way
to
customize
the
interface,
we
do
have
a
customization
docs
in
the
main
documentation
which
I
can
link
into
this
after
the
meeting
that
has
some
basic
guides
for
doing
things
like
header,
footer,
customizing,
the
logo,
the
the
color
scheme.
So
that's
the
best
place
to
get
started.
B
If
you
have
questions
on
things
that
are
not
listed
there,
you
can
ask
them
on
the
list
or
look
on
the
mailing
list
as
well,
because
I
know
there's
been
questions
there
that
get
posted
and
others
have
been
chipping
in
on
that.
But
basically
this
is
an
area
that
we're
still
working
to
document
how
to
customize
every
single
aspect
of
the
user
interface.
There's
a
lot
to
document
there.
So
the
more
people
collaborate
with
this
and
help
out
with
the
docs
there,
the
better
they
will
get
more
quickly.
B
B
B
There
is
most
Fields,
almost
all
the
metadata
fields
in
the
submission
form,
I
think
you're.
Talking
about
the
submission
form
most
the
fields
in
the
submission
form.
You
can
actually
add
a
regular
expression
to
that.
Allow
you
to
limit
what
values
can
be
put
in
those
fields.
I
suspect
you
might
be
able
to
do
that
here
with
the
title
of
files,
but
I
don't
know
off
the
top.
B
How
do
I
make
upload
optional
for
some
entities
but
mandatory
for
Publications
every
entity
has
its
own
submission
form
configuration
that's
something
you
have
to
set
up
for
entities
and
the
upload
section
has
a
configuration
itself
to
allow
it
to
be
optional.
So
I
think
you
just
need
to
update
the
submission
form
for
those
entities
to
make
the
upload
section
be
optional
for
those
particular
entities
and
then
leave
it
as
required
for
Publications
I.
Believe
that's
all
you'd
have
to
do,
but
I
can
put
some
links
in
there
after
the
meeting
here
as
well.
B
Is
there
documentation
for
redeploying
updates
to
the
Deep
Space
7
backend
I
would
look
at
the
upgrade
documentation
for
d
space
7,
because
that
has
some
Doc
basic
docs
on
how
to
upgrade
the
dspace
backend
redeploying
is
basically
kind
of
like
an
upgrade.
You
rebuild
the
back
end
using
Maven
and
redeploy
it.
So
if
you
look
at
the
back
end
up
upgrade
process,
it
would
be
very
similar
to
that.
B
We
don't
have
separate
docs
on
just
doing
redeployment,
but
that's
a
good
suggestion.
We
could
possibly
pull
those
out
of
that
upgrade
script
or
upgrade
docs,
but
I'd
look
at
the
upgrade
docs
first
customizing.
The
theme
I
mentioned
already,
but
the
home
page
is
still
the
same.
It's
possible!
You
did
not
either
you
didn't
rebuild
the
user
interface
after
you
customize
it
or
you
have
something
cached.
If
you,
if
you're
running
it
in
pm2,
sometimes
that
pm2
node
app,
then
caches
things
you
might
need
to
do
a
restart
there.
B
So
it's
probably
you
they
need
to
rebuild
or
restart.
If
something
is
caching
and
not
updating
in
the
theme,
but
in
the,
if
you
look
at
the
theme,
customization
docs,
we
recommend
they're
running
the
user
interface
in
development
mode,
while
you're
customizing
the
theme
just
temporarily,
because
that
will
automatically
update
anytime.
You
should
make
a
change.
The
development
mode
does
an
automatic
rebuild
within
a
few
seconds.
It's
right
there
to
look
at
and
that
just
makes
it
easier
to
do
the
customizations
in
development
mode
and
once
everything's
ready
to
go.
B
B
Adding
more
metadata
fields
to
the
metadata
form
we
have
docs
on
that
and
the
submission
configuration
docs.
All
the
submission
forms
are
completely
configurable
right
now
you
still
have
to
configure
them
in
a
way.
That's
similar
to
d
space
6,
where
there's
an
XML
configuration
file
that
describes
the
entire
structure
of
the
submission
form,
but
you
can
add
metadata
Fields
there
change
them
all
sorts
of
capabilities
there
within
the
metadata
forms,
so
I
would
look
at
the
submission,
documentation
and
I'll
add
a
link
in
there.
B
So
the
basic
message
here
is
no
I.
Don't
know
I'm
not
aware
of
any
activity
on
this
yet
but
I
know
this
has
been
impacting
a
couple
sites
in
terms
of
theming
when
you're
trying
to
extend
themes
so
I'll
bring
it
to
the
developers
meeting
and
see
if
we
can
get
some
movement,
but
I
I
have
not
heard
of
anybody
working
on
this
right
now.
I
will
also
warn,
though,
because
it's
July
and
because
a
lot
of
people
take
vacation
over
July
and
August.
B
Some
of
these
tickets
are
going
to
be
slow
moving
a
little
bit
over
the
the
summer
months.
Here
at
least
some
are
in
in
North
America,
so
my
apologies
for
that,
but
that's
just
kind
of
the
nature
of
vacations
and
holidays,
obviously,
but
that
is
a
high
priority
issue
for
fixing,
hopefully
in
7.6.1,
and
if
anybody
wants
to
work
on
that,
it's
a
good
opportunity
to
take
a
look
at
it
or
or
volunteer
for
it.
It's
possible
there's
a
very
small
bug
that
we
just
have
not
figured
out
where
it
sits.
B
B
Okay,
so
I
will
keep
moving
here.
Then
I
just
wanted
to
make
sure
that
we
weren't
shutting
off
shortly.
Folks
need
to
drop
off
again.
I
will
make
sure
everything
gets
answered
in
this
document,
we'll
also
copy
over
questions
that
were
asked
in
the
Q
a
area
of
zoom
and
make
sure
they
get
answered
in
this
document.
So
you
can
always
reference
back
if
you
need
to
drop
off,
but
I
am
going
to
keep
moving
here,
since
we
do
have
some
more
time
in
the
zoom
room.
B
So
I'm
going
to
continue
here,
I
see,
there's
other
q
a
questions
in
the
Q,
a
chat
as
well,
but
I'm
going
to
continue
through
these
ones.
Here,
real
quick,
I
think
it'd
be
helpful
to
have
a
system
diagram
for
the
new
angular
front.
End
I
have
a
number
of
heavily
customized
instances
that
are
due
to
be
updated
and
it's
not
clear
how
all
the
commit
components
communicate.
B
Yes,
we,
this
is
something
we
could.
We
could
look
at
doing.
I
know
that
there
were
some
old
high
level
system
diagrams
when
we
were
doing
early
development
of
d
space
7
that
were
in
slides
I
could
probably
pull
one
of
those
old
slide
decks
out.
I,
don't
have
it
in
this
current
slide
deck
of
just
a
high
level
how
things
work
together,
that's
definitely
possible
to
do
it
at
a
high
level.
I'm,
not
sure.
If
I'd
answer
all
your
questions,
but
I
think
that's
possible
to
do.
B
If
anybody
out
here
has
something
they've
built
already.
Please
pass
it
my
way
or
link
to
it
in
this
document.
Otherwise,
I'll
see
if
I
can
get
some
time,
either
myself
or
from
another
developer
to
kind
of
add
a
high
level
system
diagram
to
our
main
documentation.
I
agree:
it
would
be
useful
for
those
getting
used
to
this
new
setup
with
the
space
7.
B
B
That's
based
off
the
top
of
my
head,
but
I
do
remember
there
being
some
bugs
around
this.
That
I
believe
were
fixed
recently,
so
you
might
want
to
look
at
what
was
fixed
in
7.6
in
the
release
notes
to
see
if
this
impacts
you
or
fixes
the
problem
you're
encountering
if
you're
already
on
7.6
I
might
need
more
information
here.
But
I'll
look
back
at
this
after
the
meeting
and
Link
in
the
tickets
that
I'm
thinking
about
that
I
believe
were
solved
in
7.6
to
see
if
those
help
out.
B
B
We
search
for
a
project
in
select
one,
and
we
don't
see
yes
yeah.
There
was
an
issue
with
this
in
7.5,
where,
when
you
select
a
entity
relationship
in
the
submission
form,
when
you
select
it,
it
was
not
appearing
properly
on
the
form
there
were
bug
fixes
to
that
applied
in
7.6
and
yeah
you're
right
that
in
7.5,
even
though
it
didn't
appear
in
the
form
it
would
be
in
the
record
afterwards,
so
it
was
really
there,
but
it
just
was.
The
bug
was
that
it
wasn't
appearing
properly
in
7.6.
B
B
B
If
there
are
any
issues
that
you're
encountering,
though
please
make
sure
they
get
in
bug
tickets.
That's
the
only
way
for
us
to
get
things
fixed,
it
has
to
get
into
a
bug
ticket
and
we
need
to
be
able
to
reproduce
it.
So
we
need
to
have
details
on
what
the
problem
is
even
a
screenshot.
If
you
have
one
things
like
that,
if
we
can
reproduce
it,
then
I
can
make
sure
that
I
can
assign
it
to
someone
or
find
a
volunteer
to
work
on
it.
B
But
on
the
item
page
one
I,
don't
I,
don't
recall
if
there's
a
ticket
for
that.
If
there
is
then
I'll
I'll
double
check
that
we
have
it
on
the
right
board,
so
we
can
get
that
fixed,
hopefully
soon,
if
there's
anybody
out
there
who's
interested
in
this.
This
might
be
something
that
is
relatively
easy
to
fix
on
item
pages
in
terms
of
pulling
the
the
data,
the
data
should
already
be
there
from
the
back
end.
Rest
API,
it's
just
a
matter
of
making
sure
it
gets
displayed
properly
on
the
item
page.
B
We
need
to
set
up
the
file
rights
on
restriction
for
a
specific
group
of
users.
Is
that
something
that's
part
of
7.6?
If
I
understand
correctly,
I
think
this
is
related
to
the
bulk
access
management
tool,
you
can
restrict
files
to
a
group
of
users,
so
you
could
create
a
group
that
involves
all
your
library,
employees
and
you
can
restrict
files
or
entire
items
to
that
group.
So
that
is
possible
to
do.
B
What's
the
easiest
way
to
migrate
information
from
d
space
6
to
7,
we
have
a
migration
guide
in
the
documentation
that
talks
about
how
to
migrate
your
data
and
it's
basically
a
matter
of
kind
of
dumping,
things
out
of
the
database
and
moving
that
over
and
then
copying
over
the
files
as
well.
But
I
would
look
in
the
documentation,
there's
a
migration
guide
that
is
linked
from
the
upgrade
guide.
So
if
you
look
at
that,
it's
it's
linked
there.
It
was
also
in
my
slides
earlier
but
I'll
add
the
link
in
here.
B
After
the
meeting
we
keep
seeing
a
white
label
error
when
we
try
and
export
from
dspaces
this
a
bug.
How
can
we
fix
this
I'm,
not
sure
if
it's
a
bug,
I
actually
I,
doubt
it's
a
bug,
I'll
say,
but
it
may
be
dependent
on
the
batch
export
you're
doing.
Maybe
there
is
something
in
there
that
is
buggy
I
know
batch
export
works
by
default,
but
when
exporting
anything,
sometimes
the
data
you
are
exporting.
B
If
there's
an
issue
in
the
data
you're
exporting
that
can
cause
errors.
Whenever
you
see
a
white
level
error
page
or
whenever
you
see
any
sort
of
odd
behavior,
whether
it's
an
error,
that's
unexpected
or
a
blank
page,
any
of
those
things.
If
you
see
that
in
d
space
7
the
place
to
start
is
that
troubleshooting
guide,
I'll
link
that
in
here
after
the
meeting
is
again
in
my
slides,
that
troubleshooting
guide
will.
Let
will
walk
you
through
how
to
look
for
underlying
error
messages.
B
So
those
are
the
really
detailed
error
messages
that
could
appear
on
either
the
user
interface
side
or
on
the
back
end
in
the
logs
or
both,
sometimes
that
finding
that
underline
error
is
what
you
need
to
figure
out
how
to
fix
it.
So
the
white
label,
error
page
just
says
something
happened.
That's
all
we
know
we
don't
know
what
happened
to
find
out
what
happened.
B
So
that's
where
to
start,
if
you
once
you
find
that
underline
error,
it's
if
you
want
to
share
it
in
the
mailing
list
that
can
we
can
help
you
out
there
as
well
as
needed
last
one
here
on
this
page.
There's
a
couple
others
over
in
the
chat.
Is
there
a
way
to
create
a
set
for
oaipmh?
That
isn't
based
on
a
collection.
B
Two
so
I
believe
that's
a
good
question.
There
probably
is,
but
it
might
require
code.
I,
don't
recall
how
that's
set
for
collections
is,
is
created,
I
think
it's
in
it
might
be
in
Java
code.
I'll
have
to
look
into
this.
If
anybody
else
out
there
knows
the
answer
to
this
you're.
Welcome
to
add
it
in
or
add
links
into
this,
but
I
don't
know
the
answer
off
the
top
of
my
head.
B
To
be
quite
honest:
I,
don't
remember
if
there's
a
way
to
configure
how
a
set
is
created
or
if
you'd
have
to
code
it
with
Java
code,
so
I
don't
know,
but
you're
right
that
an
oaipmh
sets
by
default
are
created
by
all
for
all
collections
and
I
believe
all
communities,
but
they
don't
necessarily
represent
other
types
of
groups
of
items.
Necessarily
so
I'll
look
look
into
this
a
little
bit
more
afterwards
and
see
if
I
can
find
a
better
answer
as
to
how
that
would
be
done.
B
That's
it
on
this
page
I'm
going
to
jump
over
to
the
Q
a
area
of
Zoom.
Oh
this,
let's
see
the
CC
license.
One
was
answered
already
just
to
verify
in
7.6
you
will
be
shown
the
DOI
when
you
start
the
deposit,
so
that
users
can
know
the
DOI
before
the
deposit
completes
yeah
Jose.
Yes,
that
is
possible
to
do
in
7.6.
It
is
not
enabled
by
default,
but
there
is
an
a
new
step
submission
form
step
in
7.6.
B
If
you
look
in
the
release
notes
for
7.6,
it's
documented
there
and
linked
to
there,
but
there's
a
new
submission
step
that
you
can
enable
within
7.6
that
will
pre-assign
dois
and
or
handles
depending
on
how
you
configure
that
step.
When
you
configure
that
step
and
put
it
in
your
submission
form,
then
yes,
exactly
what
you
said
will
will
occur
as
soon
as
the
submission
starts.
You
get
pre-assigned,
either
a
handle
or
a
DOI,
and
that
submitter
can
see
that
handle
or
DOI.
B
B
Oh
that,
that's
related
to
that
other
DOI
question
related
to
what
metadata
field
it's
in
yeah
I
believe
that
that
behaves
the
same
as
in
d
space.
Six
in
terms
of
the
DC
identifier,
URI
and
DC
identifier,
DOI
versus
which
field
it
it
uses,
but
I'll
have
to
double
check
on
that
and
we'll
we'll
see
what
the
answer
is
on
that.
B
B
Different
rates
for
bit
streams
at
a
collection
level.
There's
you
can
configure
what
is
called
the
default.
Bitstream
read
permission
so
in
a
collection
when
you
edit,
a
collection,
there's
a
I
think
it's
called
the
roll
tab
or
something
like
that
or
I
forget
what
the
tab
is
called,
but
in
editing
a
collection,
there's
a
there's,
a
tab
there
that
lists
things
like
being
able
to
manage
submitters
for
that
collection,
as
well
as
the
item
read
permissions
for
the
collection
and
there's
also
a
bit
stream,
read
permissions
for
that
collection.
B
If
you
change
the
bitstream
read
group
for
that
collection,
then
any
new
items,
anytime,
a
new
item
goes
into
that
collection.
It
gets
automatically
assigned
the
bit
streams
will
get
assigned
that
bitstream.
Read
permission
same
for
the
item.
Read
permission,
so
I
believe
that
that
might
be
what
you're
asking
about
is
that
when
they
submit
a
new
item
into
the
collection,
you
want
those
bit
streams
to
automatically
get
certain
access
rights.
You
should
be
able
to
do
that
at
the
collection
level.
B
B
You
might
be
able
to
configure
it
within
the
submission
form
as
well,
so
I
believe
that
might
be
what
you're
asking
about
there,
but
if
I'm
still
getting
the
question
wrong,
please
feel
free
to
keep
asking
it
in
the
document
that
I'm
sharing
on
my
screen
or
or
detail
more
information
about
what
exactly
you're
trying
to
do
there.
So
I
can
make
sure
it
gets
answered
a
couple
more
in
the
Q,
a
area.
Let's
see
Hello
request
to
copy
emails
are
encoded
to
prevent
xss
attacks.
B
B
I
don't
know
if
there's
a
way
to
work
around
email
display,
I'm,
not
sure
if
I've
seen
this
issue
before
it
might
be
worth
adding
more
details,
either
in
an
email
to
the
mailing
list
or
create
an
issue
ticket
to
describe
exactly
what
you're,
seeing
even
possibly
with
like
a
screenshot
on
as
to
how
they're
being
encoded
or
what's
happening
there.
I,
don't
know
the
answer
to
that
off
the
top
of
my
head,
but
I'd
be
interested
to
understand
more
of
the
problem.
B
So
we
can
see
if
there's
a
workaround
we
can
think
of
to
to
avoid
what
you're,
seeing
so
I
think.
That's
those
first
two.
Do
you
think
configurable
entities
will
shift
from
advance
to
basic
feature
in
d
space
8,
with
attention
given
to
bulk
author
into
the
assignment
I.
Think
that's
going
to
happen
over
time.
Yes,
I
think
that
entities
are
going
to
be
the
future
of
d
space.
B
But
I
do
think
that
what
you
are
going
to
see
over
d,
space,
8
and
possibly
D
Space
Nine
is
that
transition
from
an
advanced
feature
into
that
sort
of
basic
level
feature
of
that
d.
Space
is
about
entities,
but
there's
a
lot
of
work
to
be
done
there,
as
you
mentioned
that
there's
there's
not
only
just
integrating
it
in
with
things
like
aips,
but
also
trying
to
provide
easier
tools
to
allow
people
to
migrate
from
old
structures
into
those
entities.
B
B
B
It
could
be
under
consideration.
Yes
right
now
we
concentrate
most
on
bit
streams
and
metadata,
because
that
is
really
where
most
people
want
to
make
changes
in
terms
of
permissions.
They
want
to
either
access
restrict
or
embargo
an
item
or
they
want
to
access
and
restrict
or
embargo
bit
streams
within
it,
and
so
that's
why
that
tool
has
been
set
up
in
that
way
and
I
believe
that's
also
how
it
worked
in
do
space
six,
so
we're
trying
to
align
it
a
little
bit
with
how
things
worked
in
d
space,
6.
B
I
think
there
would
be
an
option
to
manage
things
at
the
bundle
level,
but
bundles
are
a
little
bit
they're
a
little
bit
hidden
for
lack
of
a
better
word
and
that
they're
hard
to
work
with,
because
they're
not
really
visible
to
users
much
and
and
to
administrators.
Those
who
know
that
bundles
exist
I
know
you
may
use
them
for
certain
things,
but
the
things
that
people
you
use
the
most
are
those
bit
streams
and
and
items.
B
I'm
not
aware
of
anybody
who's
working
on
that
sort
of
thing
right
now,
but
a
ticket
is
a
good
way
to
get
started
and
start
that
discussion,
the
Q
a
side,
let's
see
d
space
entities
versus
d
space,
Chris
I'm,
assuming
you're,
asking
sort
of
whether
those
are
a
way
to
move
more
towards
dspace
Chris
and
yes,
as
a
general
fashion,
d,
space
and
d
space
Chris
are
trying
to
find
ways
to
move
closer
together
over
time.
Here.
B
As
you
may
be
aware,
dspace
Chris
is
a
product
for
science,
who
is
one
of
our
trusted
service
providers.
They
control
the
code
base
for
deep
space.
Chris
I
don't
have
any
involvement
with
these
spacecrafts,
but
I
do
chat
with
their
developers
all
the
time
they're
they're
tech
leads
and
and
CTO,
and
all
that
sort
of
stuff
all
the
time.
So
the
dspace
Chris
team
I
know
at
four
science.
They
they
use
the
same
entities
that
d
space,
7
uses
and
they're
wanting
to
try
and
Port
features
from
dspace
Chris
back
into
dspace.
B
That's
happened
a
little
bit
and
d
space
7,
so
the
orcid
integration
is
one
example
and
there's
others
as
well
that
are
slipping
my
mind
where
we've
taken
features
from
dspace
Chris
and
moved
them
back
into
dspace
and
I.
Think
we're
going
to
see
that
happening
more
and
more
as
we
go
forward.
Whether
there's
become
one
product
at
some
point
in
time
is
still
yet
to
be
determined,
but
I
know
we
want
to
move
them
closer
together.
B
So
there's
an
opportunity
to
maybe
just
have
a
single
product
which
is
d
space
and
make
it
a
little
bit
easier
on
folks
who
want
to
use
it
for
crisp
purposes
versus
other
use
cases.
But
right
now
the
the
goal
is
to
bring
dspace
Chris
and
d
space
closer
together
and
you
should
use
which
product
better
suit.
Your
need
right
now,
but
just
be
aware
that
I
only
support
dspace
I
can
only
support
dspace
because
I'm
the
tech
lead
of
d
space
dspace
Chris
is
a
separate
product.
B
It
is
built
on
dspace,
but
the
four
science
team
supports
that.
So
when
you
choose
to
use
dspace
Chris,
there
is
people
using
it,
but
it's
primarily
supported
by
for
Science
and
the
users
of
dspace
Chris,
whereas
I'm
supporting
more
the
the
general
dspace
product.
So
hopefully
that
answers
the
question
there.
But
there
is
a
trajectory
to
try
and
bring
those
closer
together
over
time
so
that
we
can
work
together
on
a
common
code
base
as
much
as
possible.
B
Jose
asks,
let's
see,
can
users
be
put
in
an
e-person
group
based
on
the
user's
IP
address?
Yes,
that's
a
feature
that
was
that
existed
in
d
space
six,
it
works
the
same
in
d
space
7,
there's
an
IP
based
authorization
plug-in
that
allows
you
to
based
on
the
IP
that
a
user
comes
to
that
can
be
put
into
a
specific
group,
and
then
you
can
use
that
group
to
manage
permissions
so
that
you
works
the
same
as
it
did
in
d
space
6.
B
B
I
mentioned
this
briefly
in
the
slides
that
we're
working
on
deploying
the
demo
site
on
our
Docker
scripts
that
are
in
the
code
base
that
is
coming
along
very
well
and
I
anticipate
that
redeployment
will
happen
here
over
the
summer
months
at
some
point
in
time,
either
later
in
July
or
in
August.
At
that
point
in
time,
the
dspace
demo
site
will
just
auto
update
constantly
right.
Now,
it's
a
bit
of
a
manual
process.
B
We
have
to
push
updates
out
when
the
7.6
release
came
out,
though
I
recall
pushing
updates
out
to
the
demo
site,
so
it
should
be
running
deep
space,
7.6,
so
I
believe
it's
already
on
there.
If
I'm
wrong
about
that.
Please
correct
me
and
we
could
push
out
updates
again,
but
I
think
it's
already
running
7.6
in
the
near
future.
It
will
auto
update
itself
once
we
get
it
deployed
on
those
Docker
scripts.
So
anytime
code
changes
happen
to
dspace
seven.
B
B
Yep
yeah
and
as
I
mentioned,
we're
we're
getting
near
the
half
an
hour
Point
here
anyways,
as
I
mentioned
I,
will
go
through
over
the
next
some
over
the
next
few
days.
Try
and
get
to
it
this
week
for
the
most
part
and
add
in
quick
answers
to
each
of
these
in
this
document
itself
and
provide
links
to
resources
that
might
be
useful.
B
I
really
appreciate
that
people
are
already
adding
some
comments
into
here,
providing
some
hints
to
folks
and
in
some
cases
saying
that
you
know
you
also
encountered
this
that's
very
useful
to
me
to
understand
who's
who's
encountering
things
and
if
folks
have
answers
and
beat
me
to
it,
I
would
love
folks
to
fill
out
your
answers
there
and
I
can
enhance
those
as
needed
as
we
go
through
here,
but
keep
an
eye
on
this
document.
There
will
be
answers
listed
within
here
and
resources
listed
within
here.
B
Obviously,
this
is
not
the
end
of
all
q,
a
for
dspace.
So
if
you
have
other
questions
that
come
up,
the
mailing
list
is
really
the
best
resource
for
for
detailed
questions.
If
you
have
a
big
detailed
question,
a
lot
or
an
error,
you
want
to
get
answered.
That's
a
great
place
to
share
those
detailed
questions.
B
If
you
have
quick
questions,
slack
is
a
great
resource,
but
obviously
slack
is
text
chat,
so
detailed
questions
can
be
a
little
bit
harder,
sometimes
in
slack,
but
both
of
those
are
the
two
to
excuse
me,
two
main
places
that
I
would
recommend
going
with
your
questions
and
I'd
highly
recommend
others
help
out
on
both
places
as
well.
I
do
my
best,
as
you
may
see
about
once
a
week,
go
in
and
try
and
catch
up
with
things
and
answer
things
there.
B
Sometimes
they
get
a
little
bit
more
time
in
a
given
week,
but
I'm
not
always
able
to
keep
up
to
date
with
every
question
on
a
day
by
day
basis
just
depends
on
how
busy
my
day
is.
So
if
others
have
time
when
you
have
time
or
know
an
answer
to
something,
please
do
contribute
in
there
help
folks,
along
help
help
help.
People
learn
dspace,
seven
as
we
go,
and
thank
you
very
much
to
all
the
attendees
here.
I
see
a
lot
of.
Thank
yous
in
the
web
in
our
chat
so
appreciate.
B
A
B
Yes,
thank
you
very,
very
much
and
again
the
the
document
is
this
tiny
URL
link
Natalie.
If
you
could
copy
that
in
one
last
time,
I
think
most
everybody
happens
it,
but
it
happens
to
have
it.
But
if
you
can
copy
that
tiny
URL
Link
in
one
last
time,
I
will
make
sure
at
the
top
of
that
document,
as
well.
I'm
going
to
add
a
link
to
these
slides,
probably
here
within
the
next
10
to
15
minutes
so
you'll
have
a
link
directly
to
these
slides.