►
From YouTube: OR2016 - "Introducing the New DSpace User Interface"
Description
Tim Donohue (DuraSpace) presenting at Open Repositories conference in Dublin, Ireland on June 15, 2016. Session was streamed / recorded from the Chartered Accountants House, room CA1 (see http://or2016.net/live/ for full day's recording). This video is a trimmed copy of the live stream.
A
Okay,
so
I
will
apologize
first,
that
I
didn't
wear
my
pink
shirt
today.
I
accidentally
spilled
a
little
wine
on
it
and
I
figured
it'd
probably
be
more
appropriate
not
to
wear
that
and
something
that's
being
stream
live
and
talking
to
all
of
you
about
the
new
UI
work,
but
I'm
kind
of
telling
a
story
and
several
parts
here
as
well
as
kind
of
getting
you
up
to
speed
with
where
we
started
from
last
year
and
where
we're
going
next
and
what
has
gone
into
this
decision
process
and
and
why?
A
Why
we've
kind
of
come
to
the
conclusion
that
we've
come
to
so
last
year.
If
you
were
at
open
repositories-
or
you
saw
my
slides-
I
had
this
slide.
This
is
a
complete
copy.
From
last
year,
I
said
you
know,
last
year
we're
going
to
prototype
2
to
3
platforms
and
one's
going
to
be
java-based
one's
going
to
be
non
java-based
and
we're
going
to
figure
all
this
stuff
out.
And
you
know
this
was
the
general
schedule,
and
while
we
didn't
follow
that
exact
schedule
per
say,
some
of
the
diamonds
are
a
little
bit
off.
A
This
is
essentially
what
has
happened
in
the
last
year
and
even
beyond
that,
so
we
said
two
to
three:
you
I
platforms,
one
Java
one
non
Java.
In
reality,
what
ends
up
ended
up
happening
is
after
open
repositories,
we
established
a
user
interface
working
group,
mostly
committers
decat
members
and
folks
on
steering
or
leadership.
They
helped
us
establish
a
user
interface
prototype
challenge,
which
you
may
have
heard
of
through
the
lists,
and
all
of
that
we
had
an
amazing
number
of
9
submission,
not
223.
A
We
had
nine
different
prototypes
submitted
from
our
community
from
eight
different
institutions.
The
logos
you
see
down
here,
where
they
kind
of
fell
in
terms
of
technologies,
so
we
had
some
Java
ones.
We
had
a
couple
that
were
JavaScript,
namely
ember,
j/s
and
angular
1,
and
we
had
some
Ruby
ones
as
well
after
that
process
in
December.
A
Of
course,
there's
a
holiday
break
there
for
a
lot
of
folks
and
we
kind
of
picked
up
right
after
the
holidays
and
jumped
in
and
January
in
February,
and
had
each
of
these
nine
developers
come
and
do
a
live
demo,
which
we
recorded
all
of
these
they're.
All
up
on
the
wiki,
if
you
want
to
go
back
and
see
that
historic
stuff,
we
also
started
to
get
off
historic.
It
was
six
months
ago.
We
also
started
to
gather
public
feed
from
all
of
you.
A
We
put
out
a
public
feedback
form
google
doc,
where
we
asked
for
your
input
on
these
prototypes.
What
you
liked,
what
you
didn't
like,
what
what
things
were
of
interest
or
concerning
right
away?
We
narrowed
options
here,
oh
and
I
should
mention
my
little
logo.
This
is
me
it's
an
older
picture
now
at
this
point
in
time,
but
I've
got
one
of
the
Java
ones.
That's
why
this
is
where
this
is
where
the
story
starts.
To
begin,
I
was
very
firmly
in
the
Java
camp.
A
We
also
found
that
there
were
not
as
many
distinct
advantages
to
Ruby
over
Java
or
JavaScript,
so
it
was
hard
to
make
an
argument
for
why
we
would
suddenly
jump
to
a
different,
a
different
server
side
platform
that
was
not
java
and
so
that
kind
of
got
pushed
aside
then
early
on,
and
we
said,
let's
really
start
to
concentrate
on
this
Java
and
JavaScript.
There's
some
promise
here.
Let's
see
where
we
can
go
with
this,
so
these
UI
discussions
then
began.
They
were
pretty
in-depth
and
they
kept
going
on
in
the
UI
working
group.
A
We
had
some
other
people
pop
on
and
off
on
these
meetings.
Little
by
little
they
were
bubbling
up
into
the
steering
and
leadership
groups
through
februari
and
marched.
It
really
became
that
Java
versus
JavaScript
questions.
We
had
these
two
JavaScript
technologies,
Java
on
the
other
side
and
and
we
started
to
narrow
down
what
the
real
pros
and
cons
are
of
these
platforms.
Why
would
you
want
to
do
Java?
Why
would
we
want
to
do
javascript?
A
What
can
we
see
as
the
benefits
of
each
the
detriments
of
each
and
it
came
down
to
sort
of
on
the
Java
side
of
things
we
saw
that
it's
really
stable
trusted,
it's
known
in
our
community.
It
would
be
the
same
back
in
as
our
API.
We
could
do
everything
you
know
in
one
language.
We
could
do
it
on
a
more
modern
Java
technology.
We
use
something
like
spring
boot
or
whatever
else
so
we
could
be.
We
could
get
a
lot
of
benefits
right
out
of
Java.
A
We
went
with
a
Java
user
interface,
built
it
on
a
newer
technology,
but
we
kept
having
these
bubbling
up
through
folks
around.
Is
this
really
all
that
innovative?
Is
there
as
much
added
value
here?
If
we
want
to
build
a
modern
user
interface,
we're
going
to
need
a
lot
of
JavaScript
and
things
like
that
to
kind
of
make
it
a
little
flashy
make
it
more
interactive.
We're
still
gonna
have
to
build
it.
On
top
of
this,
are
we
going
far
enough?
A
Are
we
building
something
that
we
can
excite
new
developers
around,
so
we
had
already
been
receiving
some
feedback
through
the
feedback
forms
and
things,
and
and
in
the
last
few
years
around
in
some
areas
of
the
world,
it's
harder
and
harder
to
get
good
java
developers.
So
you
want
to
customize.
Are
you
going
to
be
able
to
do
that
as
easily
if
we
build
it
all
in
java
again,
so
there's
some
questions
that
we're
starting
to
bubble
if
they
weren't
they
weren't.
You
know
groundbreaking
different
questions.
A
A
You
can
build
a
more
dynamic
interface
in
a
JavaScript
platform,
and
it
was
proven
very
well
through
our
two
prototypes
and
JavaScript
through
from
at
meijer
and
texas
A&M,
who,
who
led
those
two
prototypes,
they
showed
off
what
we
could
do
in
that
to
achieve
a
better
user
experience
to
kind
of
move
the
platform
forward.
It
would
also
really
force
us
to
do
a
separation
of
concerns.
A
What
that
means
is
that
it
would
make
us
pull
apart
our
user
interface
and
have
a
rest
api
that
actually
could
be
used
more
than
just
kind
of
in
proof-of-concept
nature.
I
mean
people
use
it,
but
it
doesn't
give
all
the
features
of
that
java
api,
so
it
forces
to
kind
of
do
some
things
that
d
space
needs
going
forward
to
make
it
more
interoperable
work
with
more
systems.
But
there
were
some
significant
questions
here
and
it's
worth
pointing
out.
A
We
hit
some
block
blocks
right
away
with
these
two
technologies
with
ember,
yet
ember,
j/s,
well,
I
think
what
version
this
was
I'll
have
to
ask
art
later
on,
but
with
the
version
of
member
GS,
we
were
doing
an
angular
1.
We
hit
some
blocks
in
terms
of
we
found
it
immediately.
It
wasn't
really
search
engine
compliant
and
there
are
search
engines
who
can
handle
JavaScript.
Can
these
oh,
this,
this
older
JavaScript?
They
can
run
the
JavaScript,
they
can
index
it
all
that
sort
of
stuff,
but
we're
having
issues
with
that
with
the
initial
prototypes.
A
There
were
questions
about
whether
or
not
you
know,
accessibility,
most
screen
readers.
These
days
can
do
javascript
that
can
sometimes
still
trip
things
up
a
little
bit.
We
had
more
proven
out
that
it
could
meet
our
needs
because
of
these
prototypes,
but
there
was
still
some
that
were
may
have
been
questioning
that
alone.
That's
along
that
period
of
time.
A
Meanwhile,
while
we
are
having
all
these
internal
discussions,
angular
1
had
suddenly
gone
to
angular
2
2
point
0
beta
back
in
December,
so
we
never
prototyped
on
this.
We
did
angular
1,
it
was
an
SEO
compliant,
but
angular
2
came
along
and
they
said,
look
we're
JavaScript,
you
I.
We
are
the
most
widely
used
JavaScript
framework
out
there
we
support
SEO,
we
can
do
everything
we
can
give
search.
Engine
search
engines
will
be
able
to
index
us
because
vote.
We
can
compile
the
JavaScript
server-side
automatically.
We
care
about
accessibility.
A
We
want
to
make
that
a
high
priority.
All
this
is
sort
of
up
there
on
their
features
on
the
angular
isle
website
that
I
have
here
on
the
bottom,
for
what
angular
2
was
seldom,
and
so
we
heard
this
and
we're,
like
you,
know,
hey
this.
This
is
sounding
kind
of
interesting
kind
of
wish.
We
would
have
had
a
chance
to
prototype
on
that.
Maybe
we
should
look
at
that
a
little
bit
more
and
at
the
dura
space
summit
in
mid-march.
That's
the
sort
of
discussion
that
started
to
come
about.
A
I
was
kind
of
more
on
the
fence.
Now
I'd
heard
about
angular
2
at
this
point
in
time,
I
was
like
you
know,
there's
interesting
stuff.
There
I
can
see
the
benefit
of
JavaScript,
but
we
don't
know
you
know
what
we
can't
really
prove
so
at
the
summit
at
the
summit
we
had
these
discussions
with
the
steering
in
the
leadership
group.
We've
had
some
good
feedback
that
they
saw
a
lot
of
promise
in
the
JavaScript
nature,
but
that
Java
was
still
sort
of
our
safety
net.
A
So
this
is
where
we
came
to
a
building,
a
proof-of-concept
user
interface
and
I'm,
going
to
give
you
a
live
demo
here,
we're
going
to
see
how
well
a
live.
Demo
works.
It
is
running
on
my
laptop.
So,
but
it's
worth
noting
a
couple
things
before
I
get
into
that,
so
it's
a
proof-of-concept
user
interface
that
we
built
in
two
and
a
half
months-
and
this
includes
us
learning,
angular
2,
so
one
group,
texas,
A&M
new
angular
1,
and
so
they
were
able
to
help
us
along
a
little
bit.
A
The
rest
of
us
did
not
really
know
angular
2
we
had
to
ramp
up.
We
had
to
move
quickly.
We
had
four
very
part
time
developers
trying
to
do
this.
We
meeting
on
a
weekly
basis
checking
up
trying
to
get
our
trying
to
figure
who
what
you're
going
to
do
for
the
next
week
reporting
back.
So
these
are
the
people
who
are
involved.
The
folks
in
green
here,
William
Welling
did
amazing
amount
of
work
from
Texas
A&M
on
this,
as
well
as
art
and
Dylan
from
at
meijer.
A
I
was
involved
from
dura
space
in
the
programming
side,
because
I
want
to
get
my
feet.
Wet
I
wanted
to
get
into
this
I
admit.
I
did
not
do
nearly
as
much
as
William
and
Dylan
an
art
good,
but
I
did
do
some
features
in
here
to
to
kind
of
get
my
feet
wet
understand
how
this
all
would
work
and
and
what
it
all
looks
like.
A
James,
Creole
and
Rick
aundrea,
Bellini
and
Jonathan
mark
I
were
all
there
to
help
help
as
consultants
sort
of
kind
of
helped
us,
along
with
the
process,
make
sure
that
we
were
hitting
all
of
the
basis
that
we
were
answering
all
the
questions
that
we
needed
to
answer
and
coming
to
a
good
conclusion
here,
coming
up
to
open
repositories.
So
here's
what
I'm
going
to
show
a
demo
and
there
is
a
public
demo
if
you
want
to
try
things
out-
you're,
not
gonna,
be
able
to
log
in
yet
you
can
run
this
locally.
A
The
codes
all
out
there
on
github,
as
I'd
shown
in
the
previous
slide
up
there
at
the
top
under
our
D
space
labs,
github
repository,
but
there's
a
public
demo
here
that
you
can
go
and
play
around
with.
If
you
want
to
I'm
going
to
be
running
this
locally
off
of
my
laptop
and
the
reason
I'm
doing,
that
is
because
I
wasn't
sure
how
well
wife
I
was
going
to
hold
up
and
if
a
bunch
of
people
jumped
on,
if
things
would
get
really
slow.
A
A
B
A
C
A
Did
not,
let's
see
here,
key
changes?
Thank
you
very,
very
much
and
now
let
me
get
this
win
this
thing
out
of
the
way
perfect.
Okay,
we
are
good.
So
this
is
the
again
a
proof-of-concept
user
interface.
The
goal
here
was
not
to
build
every
single
feature
in
D
space.
The
goal
was
to
prove
out
that
we
could
do
the
things
we
want
to
do
in
angular
2
to
achieve
ad
space
user
interface
here
and
that's
kind
of
important,
because
we
built
this
all
based
on
the
D
space.
A
Five
rest
api,
dspace
six
at
the
time
when
we
started
was,
you
know
pretty
far
along,
but
the
rest
api
sold
a
couple
little
issues
there,
so
we
decided
right
away
that
we
want
to
do
d,
space
five
and
actually
also
be
able
to
point
it
at
some
production
sites
to
see
data
right
away.
So
this
is
what
we
came
up
with
its
on
bootstrap.
It's
not
super
pretty,
but
but
art
did
a
good
job
here
and
Dylan
from
meijer,
helping
us
kind
of
make.
This
look
a
little
bit
nicer,
so
we
got
the
usual.
A
You
know
mobile
stuff.
Here,
fancy
fancy
we
got,
we
got
the
news
here
at
the
front
and
then
we
got
our
little
browse
community
and
collections
and
items
so
I'm
I'm
working
up
a
very
small-
well,
not
a
small
laptop,
but
a
small
D
space
here,
I'm
in
terms
of
I
just
have
six
items
right
now:
a
couple
collection
in
the
community,
but
we've
got
basic
browse
pages
for
each,
so
you
can
jump
into
a
collection
of
items
and
we've
got
our
items
listed
here.
A
Currently
we
don't
have
thumbnails
enabled
in
here
we
can
go
in
any
of
this
sort
of
stuff,
that's
just
sort
of
the
normal
browse
experience
of
D
space,
but
in
a
new
environment.
The
one
thing
to
point
out
here,
though,
remember
there
was
this
SEO
concerns.
We
wanted
to
be
able
to
prove
out
that
search
engine.
Optimization
worked.
So
in
order
to
do
that,
we
wanted
to
be
able
to
prove
that
Google
scholars
needs
which
were
the
most
strict
that
we
could
find
were
met.
A
So
we
talked
to
honor
agha,
google
scholar
and
had
him
actually
test
out
our
live
demo
up
there
in
that
public
thing,
and
then
I'm
going
to
find
what
am
I
looking
for
here
where's
my
JavaScript:
that's
not
what
I
wanted.
Let
me
develop
the
tools,
so
we
wanted
to
make
sure
that
Google
scholars
needs
were
met
and
Google
Scholar
basically
told
us
flat
out.
Look
if
you
have
any
javascript
in
your
site,
we're
not
going
to
run
it.
We
ignore
it.
A
So
if
your
JavaScript
site
you're
really
not
going
to
get
much
your
site
indexed,
if
you're
totally
built
by
JavaScript,
so
we
want
to
be
able
to
do,
is
actually
prove
out
that
this
site
worked
completely
with
JavaScript
turned
off,
and
so
that's
what
I'm
going
to
do
right
now
is
turn
off.
There's
the
settings
I
want!
Oh
and
I'm
disabled
good,
okay,
get
this
out
of
the
way,
so
this
little
icon
up
here
that
I'm,
pointing
to
with
my
mouse,
is
that
javascript
is
disabled.
Currently
and
again,
I'm
running
a
javascript
user
interface.
A
Let
me
go
back
to
the
and
I
can
go
ahead
and
just
browse
around
to
my
heart's
content
and
everything
is
still
working
in
terms
of
being
able
to
interact
with
the
cyclin,
and
this
is
very
important,
because
this
is
exactly
what
Google
scholars
robots
would
see.
They
want
to
be
able
to
see
a
site
that
is
actually
usable
to
their
robots
with
JavaScript
completely
turned
off,
and
so
we
talked
with
honor
AAG
about
that.
He
ran
my
tremendo
script
back
on
here.
A
If
I
can
get
it
going,
okay,
we
talked
to
honor
OGG
and
he
he
did
some
testing
on
his
end
to
make
sure
that
everything
was
coming
up
properly,
that
we
were
able
to
that.
He
was
able
to
index,
are
our
sample
site
and
he
had
little
feature
little
request
here
and
there,
in
terms
of
all
this,
isn't
quite
working
quite
as
well
as
Deez
base
currently
does
and
done
it.
But
the
basics
all
work,
and
that
was
the
most
important
question
it
wasn't.
Can
we
get
it
as
good
as
d
space?
A
A
Yes,
this
is
working,
and
this
was
the
first
time
google
scholar
had
actually
tested
out
with
angular
2
from
my
talking
with
honor
on,
but
I'm
going
to
log
in
here
and
show
off
some
of
what
else
we
actually
have,
because
that's
the
more
important
stuff
as
once,
we're
logged
in
here.
What
we
have
here
so.
A
Okay,
so
I'm
logged
in
as
an
admin
account
another
thing
we
wanted
to
be
able
to
prove
here.
I
do
have
my
JavaScript
turned
back
on
now,
because
there
are
some
features
that
don't
fully
work
with
JavaScript
off
some
of
the
flashy
animations
things
like
that.
You'll
still
get
the
basic
site
experience,
but
not
everything
works,
and
it
was
good
enough
for
what
Google
Scholar
needs.
All
the
public
access
stuff
is.
A
Work
works
completely
with
JavaScript
turned
off,
but
in
torque
in
order
to
do
some
other
sort
of
a
proof-of-concept
work
that
we
were
trying
to
do
in
this.
We
wanted
to
be
able
to
prove
out
that
we
could
do
things
like
okay.
So
one
of
the
big
claims
of
JavaScript
that
we're
showing
off
and
our
JavaScript
prototypes
is
that
we
can
do
things
more
time.
Amelie
we
can
do
some
dynamic
editing.
We
can
achieve
things
in
a
different
way
than
we've
done
them
with
indie
space.
Saudi
space
obviously
has
a
lot
of
back-end
config
files.
A
We
want
to
try
and
get
away
with
that,
get
away
from
that
and
start
to
move
towards,
like
admin,
UI,
sort
of
capabilities
being
able
to
tweak
things
from
your
admin
UI.
So
one
of
the
things
we
did
that
was
done.
Is
this
little
edit
sidebar
here?
So
you
can
see
my
sidebar
here.
We
got
an
account
area.
Just
has
login
logout
an
admin
area.
What's
right,
now
is
just
an
edit
sidebar
just
for
the
proof
of
concept.
We
have
this
link
section
and
I
have
a
link
here.
A
A
And
notice
how
everything
is
changing,
as
I
type
the
reason
why
we
wanted
to
prove
this
out,
so
not
only
for
the
dynamic
aspect,
but
what's
actually
happening
here
behind
the
scenes.
What
you
cannot
necessarily
see
here
live
is
that
it's
actually,
when
I
save
this
so
right
now,
normal
users
wouldn't
be
seen
those
at
it's
live,
but
as
soon
as
you
save
it,
it's
actually
saving
to
a
configuration
file
on
the
back
end.
A
So
if
I
reload
my
site
or
if
other
users
now
you
know,
go
back
to
your
site,
they're
going
to
see
this
new
text
section
if
I
close
down
this
browser
completely
and
go
back,
it's
saved
because
it's
actually
editing
a
configuration
file
on
the
server
side.
So
it's
more
dynamically
editing
a
configuration
and
changing
it
within
the
menu
at
the
same
point
in
time,
which
is
something
we
wanted
to
be
able
to
achieve
because
it's
stuff
we've
wanted
to
do
in
deep
space
for
a
long
time
and
it
could
be
done
in
Java.
A
A
Let
me
go
back
to
the
home,
so
you
want
to
want
to
deal
with
more
complex
configuration
files
on
the
backend,
a
good
example
of
doing
some
more
complex
work
in
configuration
or
things
that
requires
complex
configuration
is
actually
the
item
creation
screen
and
we
did
not
build
the
entire
workflow
process
into
this,
as
I
mentioned
here.
Briefly,
it's
not
available
within
the
rest
api
right
now.
So
what
we
limited
ourselves
to
doing
is
just
having
a
basic
item
creation
form
that
is
driven
though,
however,
from
back-end
configuration
files.
A
I
just
proved
that
I
can
edit
back
in
configuration
files
dynamically
from
the
sidebar
and
now
I'm
just
showing
off
a
basic
form
that
is
kind
of
like
an
input
forms
thing
with
the
space
right
now,
but
you
could
imagine
it
could
be
dynamically
changed
from
from
admin
UI.
In
this
case,
it's
not
actually
going
to
be
dynamically
changed
because
we
didn't
get
that
far,
but
we
did
get
a
cool,
some
cool
little
features
here
we
got
a
form,
that's
a
basic
form.
Here.
You
can
notice
right
away.
A
We
got
a
little
drag-and-drop
thing
up
here:
fancy
fancy
we
do
have
a
type
select
a
type
of
what
you're
putting
in
here.
So
if
I
look
at
my
metadata,
I've
got
just
some
generic
fields.
Title
author,
publication
days,
public
publisher,
let's
say
I'm
going
to
put
in
a
thesis.
I
wanted
to
submit
a
thesis.
You
really
want
to
advisor
so
I'm
dynamically,
changing
the
fields
on
this
page
based
on
what
type
of
document
you
want
to
deal
with,
and
we
have
this
for
several
different
types.
Most
of
them
right
now
are
very
generic.
A
We
just
have
title
description
when
you
change
this.
The
default
shows
most
everything,
but
it
allows
you
to
kind
of
imagine
where
you
could
go
with
this
in
terms
of
moving
the
D
space
user
experience
forward,
as
well
as
being
able
to
modify
these
more
dynamically
on
the
from
the
user
interface
and
have
a
better
experience.
So,
on
the
back
end,
these
were
all
JSON
configuration
files
and
with
the
sidebar
we
were
dynamically
editing.
A
A
JSON
configuration
file
in
this
case
we're
just
dynamically
changing
between
which
JSON
configuration
file
we're
going
to
use,
and
you
can
imagine
we
could
edit
those
more
dynamically
in
the
future
as
well.
Another
feature
that
we
wanted
to
kind
of
play
around
with
was
a
weight
actually
I
want
to
show
I'll
just
show
off
the
drag
and
drop
stuff,
because
the
JSP
UI
has
this,
but
but
XML
you
I'd
is
not
so
I
can
pull
a
file.
A
/
do
all
that
fancy
stuff
and
then
I'm
just
going
to
do
a
something
that
just
has
a
title
and
book
just
gives
me
required.
Oh,
and
we
can
also
change
what
fields
are
required.
I
should
show
that
if
I
can
find
my
editor
sorry,
you
can
tell
this
is
a
really
live
demo,
because
I'm
having
trouble
in
my
tiny
screen
finding
all
the
things
that
I
wanted
to
find.
A
Oh
wait!
Well,
that's
coming
up
here
just
come
on
Adam.
You
know
you
want
to
start
up
there.
We
are
okay,
so
I
do
want
to
show
really
quickly.
That's
that
these
are
also.
These
are
the
type
forms
right
here.
We
have
these
various
type
forms
stored
on
the
back
end.
This
is
looking
at
the
backend
configuration
files.
These
are
JSON
just
because
JavaScript
deals
more
with
JSON
and
can
interact
with
it
easier.
A
So
we
just
want
something
quick,
but
what
we
have
here
is
this
capability
to
to
specify
you
know
what
field
is
this
having
to
do
with
do
like
you
know
normal
this,
the
pretty
name
for
it?
It's
going
to
be
a
text
box,
this
one's
not
going
to
be
repeatable,
but
maybe
other
ones
could
oh
and
let's
make
some
validation
rules.
Let's
say
you
know
this.
This
is
required
and
it
must
have
at
least
four
characters
and
can
only
be
128.
A
These
are
all
things
you
could
change
dynamically
if
you
can
imagine
that,
because
this
is
all
JSON
and
javascript
is
great
at
changing
changing
JSON
on
the
back
end.
So
that's
like
one
of
the
forms
that
thesis
form
and
we've
done,
that
that
sort
of
configurate
configurability
in
that
back
end
area,
but
it
then
allows
us
to
do
that
sort
of
validation,
so
I
can
just
say:
I
can
start
typing
some
characters.
A
Okay,
so
I've
got
a
own
as
a
PDF.
How
so
we
gotta
test
upload
here
from
from
open
repositories,
we'll
go
ahead
and
submit
that
we
got
a
progress
bar
as
we're
uploading
our
file
and
it's
taking
a
little
longer
on
my
local
machine.
It
looks
like
okay
should
be
done
there
we
go
so
we
uploaded
successfully.
We
can
go
ahead
and
scroll
down
here
and
our
collection
and
see
our
test.
A
Upload
from
0
are
16,
and
we
have
a
little
bit
of
overlap
here,
because
my
screen
is
so
small,
but
we
got
our
file
basic
metadata.
Nothing
was
really
specified
there.
So
that's
just
the
upload
process,
of
course,
just
an
example
of
that
something
else
we
achieved.
The
last
thing
I
do
want
to
show
off
is
another
sort
of
JavaScript
d,
something
it's
a
little
bit
easier
to
achieve
in
a
JavaScript
realm
rather
than
in
a
back-end.
Realm
could
still
achieve
it
there,
but
so
we
have
a
an
existing
item.
A
Okay,
a
test
web
page,
some
files-
some
some
metadata
here-
I'm
going
to
go
in
here
and
go
ahead
and
edit
this
and
now
I
can
actually
do
inline
editing
here.
So
we
can
say
if
there's
only
specific
fields,
you
want
to
touch
and
change.
You
can
go
ahead
and
just
change
those
in
line
within
the
oh,
my
browser
just
pushed
it
down.
A
And
so
you
can
contrast
this
to
the
editing
experience
with
indie
space
right
now,
where
it's
a
lot
more
difficult
to
figure
out
where
things
are
going
to
sit
on
the
page,
how
things
are
going
to
line
up
and
how
to
actually
going
to
go
in
and
edit
stuff.
But
so
this
is
one
other
feature
that
we
added
here.
Everything
is
not
perfect.
This
is
not
a
hundred
percent
bug
free.
It's
all
supposed
to
be
a
perfect
concept
to
show
off
what
we
can
achieve
here,
going
forward
with
in
angular
2.
B
A
Start
my
talk
up,
everything
went
horribly
long,
I
had
screen
shots,
but
it
didn't
go
horribly
wrong
other
than
the
little
thing
up
there
that
Windows
10
stuff.
So
so
what
we
proved
out
during
this
process
was
that
search
engine
optimization
was
possible.
If
we
wanted
to
do
angular
2,
we
proved
it
out
with
google
scholar,
while
we
were
doing
this
straight.
Not
strangely,
but
coincidentally
one
day,
somebody
on
IRC,
I
was
out
there
from
university,
kansas
ping
me
and
said:
hey:
have
you
looked
into
accessibility
as
it
proved
have
you
proven
out?
A
The
accessibility
need?
No,
not
quite
we've
done
a
little
bit
with
it,
and
so
they
ran
it
through
their
their
accessibility
team,
locally
University
of
Kansas
and
came
back
with
very
few
issues,
nun
major.
They
said
it
was
just
tiny
stuff
that
we
could
tweak
just
to
improve
it,
but
everything's.
Looking
good
we're
like
great
okay,
that's
excellent!
So
we're
we're
doing
well
in
accessibility.
We
just
need
to
keep
on
top
of
that.
Keep
it
moving
forward
as
we're
as
we're
getting
this
interface
moving
forward
as
well.
A
I
show
that
it
showed
already
that,
obviously
we
can
achieve
some
better
user
experience
in
terms
of
editing
things,
dynamically
changing
stuff
on
the
fly,
making
things
more
configurable
from
the
user
interface
and,
of
course,
everything
is
still
job.
On
the
back
end.
Here,
I'm
running
this
I'm
running
the
angular
2
app
on
my
Windows
machine
I've
got
a
virtual
machine
running
here
as
well.
That's
running
Linux
and
that's
where
my
dspace
5
rest
api
and
a
regular
dspace
5
out
of
the
box
d
spaces.
A
Five
is
running
and
that's
what
I
just
showed
off
their
so
now
we
come
to
today.
I
am
very,
very
firmly
to
camp
everybody.
I
talked
to
is
very
very
firmly.
Everybody
on
this
prototype
has
been
very
very
firmly
over
in
the
JavaScript
angular
to
camp.
We
need
to.
We
need
to
be
doing
this.
This
is
where
the
future
of
DS
base
can
really
be
achieved
in
a
much
more
easy
fashion
than
trying
to
build
this
still
on
a
Java
platform,
with
lots
of
layers
of
JavaScript
on
top
of
it.
A
But
as
of
just
a
little
while
ago,
two
three
weeks
ago,
angular
2
is
now
released.
Its
first
release
candidate-
it's
not
out
in
production-
that's
worth
noting,
but
there
are
sites
we're
using
it
already
in
production,
a
couple
of
them
here:
Capital,
One
and
weather
com.
Google
is
moving
most
to
their
products
over
like
google
adwords
and
things
like
that
as
we
speak.
So
it's
it's
moving
forward
very,
very
rapidly.
I
expect
the
final
release
of
angular
2
will
probably
be
out
sometime
this
summer.
There's
not
a
firm
date
on
that.
A
They
promised
definitely
this
year,
but
it's
moving
so
rapidly
that
I'm
guessing
it's
probably
going
to
be
sometime
this
summer
or
early
fall
and
I
should
mention
that
in
that
two
and
a
half
months
of
us
achieving
all
of
that,
we
also
were
working
with
a
beta
for
the
most
that
time.
Other
the
last
few
weeks,
we
we
kept
hitting
little
things
in
that
beta,
as
you
may
imagine.
If
it
is
not
perfect,
we
hit
little
things,
so
we
always
had
to
hit
little
bugs.
We
report
him
back.
A
We
gave
more
feedback
back
to
hang
to
the
angular
team
and
and
kept
that
process
going,
but
that
was
also
a
part
of
building
all
of
this,
and
it's
kind
of
gone
brought
us
to
the
fact
of
you
know
if
you're
not
convinced,
why
really
should
we
be
using
angular
2?
Here's
a
couple
reasons
why
I
think
it's
very
important
first
off
angular
is
the
most
popular
framework
out
there.
A
This
is
angular
1,
angular
2
is
still
new,
but
there's
a
massive
adoption
moving
towards
angular,
2
and
I,
don't
perceive
that
angular
is
going
to
lose
their
their
massive
user
base
anytime
soon,
angular
1
has
extensive
third-party
modules.
Angular
2
has
a
lot
of
them
already
and
more
in
the
works
we
used
about
three
or
four
to
achieve
what
we've
done
up
there
in
terms
of
file
upload
modules,
bootstrap
modules,
other
things
to
achieve
this
very
quickly.
A
Angular
2
is
also
exposing
Lee
Java,
like
it's
amazing,
the
experience
of
work
with
angular
2
as
a
Java
programmer,
but
at
the
same
point
in
time,
it's
stuff
that
JavaScript
folks
can
really
get
into
there's.
This
idea
of
everything
on
the
web
page
is
a
component.
You
can
extend
components.
You
can
move
things
around
much
easier
to
edit
your
user
interface.
However,
you
want
and
as
I
showed
well
there's
also
HTML,
like
templates,
which
makes
it
easy
to
customize
as
well
and
as
I
showed.
A
You
don't
need
to
be
running
JavaScript
on
the
client
actually
even
use
angular
2.
This
is
the
everything
as
a
component
sort
of
idea
here
that
all
of
these
this
is
the
home
page.
So
the
sidebar
is
its
own
component.
Sidebar
consists
of
sidebar
sections.
You
can
move
those
around
as
you
need.
There's
a
breadcrumb
component
that
controls
where
you
are
within
the
application.
A
There's
a
news
component
there's
a
tree
component:
you
can
extend
components
in
a
way
such
that
you
could
have
a
basic
tree
that
deals
with
communities
and
collections,
but
maybe
I
want
items
a
little
bit
different
when
I
have
a
list
of
items
or
tree
of
items.
So
I
can
just
extend
that
component
and
change
its
very
slightly
for
items
to
make
it
look.
A
How
I
want
it
to
look
and
that'll
all
still
work
within
this
this
whole
framework,
but
one
of
the
questions,
I
guess
out
of
this
one
of
my
questions
that
I
would
assume
you'd
want
to
be
asking
is
how
do
we
get
here?
What
are
we
going
next?
What's
the
plan
here
and
I
want
to
I'm
rushing
here
a
little
bit.
Cuz
I
want
to
make
sure
I
have
plenty
a
time
for
questions
and
I
realize
we're
getting
short
with
my
demo,
but
the
roadmap
27
is
essentially
two
main
points.
It's
that
rest
api
point.
A
A
For
too
long
we've
been
trying
to
work
with
two
parallel
code
bases
at
a
UI
level,
and
it
really
hampers
our
development
process.
It
hampers
our
ability
to
add
the
features
that
people
actually
want
and
a
bit
and
the
ability
to
redesign
interfaces.
All
of
that
has
been
hampered
by
this
process
of
doing
too
much
in
parallel,
the
timeline
goals
would
be
to
have
a
beta
and
training
by
next
open
repositories.
A
A
We'd
love
to
have
some
user
interface
user
experience
designers
to
help
us
make
this
a
much
better
user
experience
to
really
kind
of
turned
East
based
on
its
head
and
see
what
we
can
do
to
achieve
a
better
experience
for
repository
managers
for
the
users
for
sysadmin
for
all
those
sort
of
people.
We
want
some
continued
accessibility,
testing
I
think
we're
going
to
get
that
along
the
way
as
well.
A
But
we
want
to
make
sure
that
we're
meeting
all
the
accessibility
needs
that
we
strive
for
dspace
and
eventually,
obviously
we'll
be
getting
to
needing
more
and
more
translators.
I'll
mention
we
did
actually
prove
out
the
translation
thing
as
well.
We
do
have
internationalization
in
our
proof
of
concept.
I
didn't
show
that
off,
but
we
can
achieve
internationalization
within
angular
2
as
well.
So
if
you
want
to
join
email
me
contact
me,
the
goal
here
is
to
work
pretty
rapidly
and
sprint
like
sort
of
more
organized
in
a
way
than
we've
worked
in
the
past.
A
It's
not
going
to
be.
Let's
wait
around
see
what
comes
to
us
it's
going
to
be.
This
is
what
we
need
and
let's
see
how
we
can
achieve
it
and
who
wants
to
grab
this
and
take
this
little
piece
and
who
wants
to
grab
this
little
piece
and
take
this
and
let's
go
off
and
move
this
thing
forward
as
quickly
as
we
can.
Another
aspect
of
this
is
honestly
I
mean
I,
said
this
in
all
my
talks
these
days,
but
we'd
also
encourage
funds
as
well.
A
If
you
don't
have
a
developer
that
you
want
to
give
or
you
don't
know
if
thoughts
you
want
to
give
on
the
user
experience
or
whatever
else
you
can
also
help
by
funding
ups.
So
that's
another
way
to
give
back.
Financial
contributions
are
critical
for
dspace.
They
help
fund
my
role.
If
we
had
more
of
them,
we
could
fund
more
of
more
Tim's
or
more
whoever.
We
need
to
work
on
this,
and
it
also
gives
you
more
of
a
say
in
the
roadmap
and
governance.
A
If
that's
of
entrance
to
your
institution,
I
should
mention
as
well
before
we
get
the
questions
here
that
we've
been
doing
well.
I've
been
doing
a
d
spaced
videos
off
this
YouTube
of
our
constant
progress.
Is
we've
been
leading
up
here
to
open
repositories?
If
you
hadn't
seen
those
posts
that
started
probably
about
a
month
ago
or
so,
then
you
should
go
back
and
go
ahead
and
watch
those
videos
I
plan
to
continue
that
process.
A
So
we
can
keep
the
community
in
the
loop
where
we're
going
where
we're
at
and
get
questions
as
we
go
and
comments
and
suggestions
as
we
go
so
stay
tuned
to
the
YouTube
channel,
I'll,
keep
posting
and
spam
and
the
list
with
that
sort
of
stuff
to
keep
you
all
involved
as
well.
But
that's
it
that's
it
for
me.
Hopefully
I'll
often
have
time
for
questions.
E
Okay,
first
tim
and
all
the
others,
I
would
like
to
thank
you
for
leapfrogging
to
what
the
state
of
the
art
in
web
development.
It's
really
awesome
to
see.
Thank
you
very
much
for
that
reform
and
I'm
I
have
a
question
regarding
the
build
process.
Okay,
will
it
stay
with
maven
and
then
and
phase
and
building
are.
A
You
probably
not,
but
that
means
this
will
be
worked
out
with
the
proof-of-concept.
We
really
were
just
trying
to
build
against
existing
dspace
5
so
for
the
the
future.
I
showed
this
to
I've
got
some
extra
slides
here
at
the
end
that
I
showed
to
the
committers
earlier
this
week
and
I
had
proposed
this.
This
is
not
by
any
means
final
and
it's
a
vastly
simplified
model.
4D
space
Evan.
A
It
doesn't
speak
to
the
build
process,
but
I
want
to
find
ways
to
to
simplify
our
architecture
even
further,
namely
moving
of
the
all
of
our
various
web
apps
into
a
single
web
app
that
can
be
that
back
end
web
app,
which
can
simplify
the
build
process
and
simplify
the
upgrade
process
and
try
and
be
able
to
get
to
the
point
where
you
cut
aunt
out
and
cut
things
off
that
we
don't
need
to
be
doing
during
that
installation.
I
don't
have
an
exact
answer,
but
but
the
goal
is
to
get
there.
So
that's
promising.
D
B
Not
not
technical
at
this
time.
Okay,
Europe
you're,
talking
about
the
aspirant
baser
days
approach
that
for
a
development.
Okay,
but
do
you
already
have
a
documented
backlog
with,
with
the
at
least
expected
their
due
date,
so
for
some
given
the
functionalities,
either
in
the
the
rest
api
or
in
the
the
web
interface
or
on
the
swamp,
and
that.
A
Will
be
what
we're
working
will
I'll
be
working
on
right
after
open
repositories,
the
goal
up
till
now,
because
we
only
have
that
this
two-and-a-half
months
to
try
and
do
a
prototype
get
our
decision
made.
It
was
all
about
getting
here
and
showing
you
guys
what
we
had.
So
the
next
stage
is
going
back
and
doing
the
detailed
planning
of
these
are
the
things
that
are
missing
in
the
rest,
api
that
we
need
to
achieve
and
lets.
You
know
earmark
each
of
those
and
see
who
we
can
get
interested
knows.
A
These
are
the
things
we
want
to
achieve
next
in
the
user
interface
to
start
to
actually
move
it
into
being
more
dspace
like
in
nature-
and
I
don't
mean
d
space
like
in
the
old
way
of
doing
things,
but
I
mean
d
space
like
and
actually
meeting
all
the
same
features
things
of
that
nature,
so
that
will
be
happening
right
after
open
repositories.
So
we're
not
there
yet.
Okay.
A
We
met
on
Monday.
This
was
the
D
cat
and
developer
meeting.
That
was
a
workshop.
It
was
listed
as
a
workshop,
but
yeah
yeah,
so
I
presented
a
version
of
this
there
and
talked
it
through
with
the
D
cat
and
commit
her
folks
in
that
meeting,
which
is
where
some
of
the
extra
slides
that
get
a
little
bit
more
technical
are
and
I
didn't
have
time
to
do
them
here.
C
C
A
Just
for
the
future
to
move
to
a
richer
data
made
it
a
format
that
is
on
our
roadmap
going
forward.
It's
probably
not
going
to
be
unless
we
so
I
should
answer
this
in
a
way
in
two
different
ways.
So,
right
now,
it's
not
currently
on
the
roadmap
4d
space,
seven
to
enhance
the
metadata
capabilities
of
the
underlying
d
space.
However,
if
somebody
is
very
interested
in
helping
make
that
happen,
I
think
there's
opportunities
there,
because
it
is
of
high
interest
to
others
in
the
community.
A
So
if
we
get
enough
community
members
interested
in
helping
try
and
achieve
that,
it
could
happen
in
parallel
to
some
of
these
other
efforts,
but
if
we,
but
otherwise
it's
not
really
and
part
of
that
dspace
roadmap,
because
of
the
fact
that
there
is
so
many
things
that
will
have
to
do
at
the
rest
api
level
and
to
build
the
whole
new
user
interface.
And
we
want
to
achieve
this
as
quickly
as
possible.
A
You
saw
this
is
only
a
year
and
a
half
time
line,
which
is
pretty
quick
to
build
a
whole
user
interface,
a
whole
new
user
interface,
but
I
think
it's
achievable.
If
we
can
get
folks
behind
it,
so
it's
really
the
highest
priority
of
those
two
things
and
then,
after
that,
other
things
like
enhancing
metadata
and
stuff
like
that.
Will
pop
up
Tom
yeah,
Andre
Andre
us
back
there
behind
you,
you
don't
want
to
walk
all
the
way
down
and
come
back
I.
F
Just
do
stress
the
discussion
about
rich
data
model
in
the
space
on
Monday.
We
had
a
workshop
and
also
we
start
the
discussion
between
the
space
and
the
space
Chris.
That
is
an
extension
that
just
try
to
address
some
of
the
major
issue
of
the
database
of
the
data
model.
So
I
won't
again
to
offer
our
have
ability,
as
the
space
chris
developer,
to
work
to
with
the
community
to
give
a
rich
data
model
to
2d
space.
F
So
in
this
regard,
for
instance,
we
are
completely
unable
to
provide
rest
api
for
displaced
crease
to
move
ahead.
It
do
forward
to
this
base
7
user
interface.
So
if
you
fall
in
the
trees,
I
need
over
each
user
rich
data
model
in
this
space.
Please
join
the
conversation
of
the
developer
mailing
list
and
try
to
see
if
the
space
crease,
the
our
current
idea
can
fit
your
requirements.
Yep.
A
And
I
should
mention
that
dspace
Chris
discussion
is
just
in
the
start,
so
we're
talking
about
how
to
bring
more
of
that
data
model.
That
Richard
data
model
in
2d
space
out
of
the
box
is
what
Andre
is
pointing
out
and
so
will
be
many
more
discussions
within
decad
developers
on
the
mailing
lists
that
will
be
coming
with
that
over
there
we
have
10
minutes
a
couple.
A
Would
love
to
do
that,
but
I
we
need.
We
need
folks
who
can
help
move
that
forward
I'm
going
to
be
busy
enough
trying
to
get
these
two
tests
on
up
here
and
getting
everybody
else.
Moving
with
that,
but
I
would
love
to
see
triple
I
F
integration
with
D
space.
Yes,
so
yeah!
If
there's
other
common
folks
are
interested
in
that
I
encourage
you
to
try
and
get
together
and
let's
see
if
we
can
make
that
happen.