►
Description
A brief overview of the background / prototype challenge which led up to the DSpace New User Interface (UI) Initiative.
https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Prototype+Challenge
A
Hello,
everyone-
this
is
tim
donaghy
from
dura
space,
and
this
is
the
first
of
many
video
updates
from
the
D
space
new
UI
initiative.
The
goal
of
this
initiative
is
really
to
build
a
new
user
interface
4d
space
to
replace
the
aging
XML
UI
and
JSP
UI,
and
it's
the
top
priority
in
our
roadmap,
as
was
presented
at
the
open
repositories
conference
in
2015
last
year,
and
this
first
video
I
really
just
want
to
update
people
on
where
we've
come
from
and
where
the
background
is
and
where
we're
sort
of
going
towards.
A
In
this
initiative,
just
in
case
you
haven't
had
a
chance
to
keep
up
on
the
wiki
and
other
places
that
word
has
kind
of
bubbled
out
little
by
little,
but
in
any
case,
back
in
late
2015,
we
had
ad
space
you
I
working
group
that
ran
a
UI
prototype
challenge
and
I'm,
showing
you
the
wiki
page
right
here
where
you
can
go
for
a
lot
more
information
about
that.
You
I
prototype
challenge.
You
can
see
what
the
guidelines
were
timelines
and
the
nine
prototypes
that
came
out
of
that.
A
So,
at
the
end
of
December,
we
had
nine
prototypes
at
as
I
had
just
mentioned
that
were
submitted
into
this
prototype
challenge,
and
the
UI
working
group
began
to
review
these
with
a
group
of
committees
and
other
people
who
joined
in
on
some
of
those
calls.
So
we
started
in
January
in
February
and
had
live
demos
and
discussions
that
were
recorded
and
they're
they're
linked
down
at
the
bottom
of
this
particular
wiki
page.
A
We
got
a
link
right
here
into
the
under
the
january/february
timeframe,
but
if
you
scroll
all
the
way
down,
you
can
watch
those
videos
for
any
of
those
initial
nine
prototypes,
but
from
there
in
February
we
started
to
gather
feedback
from
the
community.
So
we
had
a
public
feedback
form
we
advertised
on
the
lists.
We
encourage
people
to
go
and
watch
those
videos
and
give
us
your
feedback
on
which
ones
looked
interesting
and
the
initial
feedback
we
got.
Things
started
to
started
to
kind
of
gather
around
two
main
platforms.
A
It
wasn't
necessarily
two
prototypes,
but
it
was
platforms,
common
platforms
that
were
actually
shared
across
multiple
prototypes,
the
first
those
platforms
was
to
build
a
java-based
user
interface
so
similar
to
what
dspace
currently
has.
Currently
we
have
two
of
them.
We've
got
the
JSP
UI
in
the
XML
UI
and
they're,
both
based
on
Java,
underneath
with
slight
differences,
obviously
in
the
display
layer,
but
that
was
one
platform
was
to
modernize
at
a
Java
user
interface
level.
There
were
much
more
modern
platforms.
A
We
could
use
things
like
spring
boot
that
could
really
bring
our
user
interface
forward
and
make
a
large
leap
even
at
the
Java
level,
but
the
second
platform
or
framework
that
we
started
to
standardize
around
and
talk
around
was
actually
thinking
about,
moving
beyond
Java
and
particular
to
a
javascript
user
interface,
one
that
is
a
little
bit
more
of
a
modern
framework,
a
little
bit
easier
to
learn
and
pick
up.
There's
more
JavaScript
developers
out
there.
We
saw
advantages
to
actually
making
a
much
more
usable,
user-friendly
interface
user
experience.
A
A
The
main
thing
that
came
out
of
those
summit
discussions
was
really
that
there
was.
There
was
a
manner
there
was
a
good
amount
of
excitement
around
investigating
the
JavaScript.
You
I
platform
in
much
more
detail
to
run
an
extended
prototype,
the
main
pros
we
saw
there
the
main
advantages,
whereas
I
kind
of
mentioned
alluded
to.
Maybe
we
could
attract
some
new
developers.
We
could
build
a
much
more
modern
user
experience,
allow
much
more
dynamic
interaction
with
the
user
interface.
The
interface
could
be.
A
They
could
just
dig
into
the
the
JavaScript
layer
and
and
tweak
it
or
tweak
the
templates
at
that
layer.
So
there
were
a
lot
of
big
pros
that
the
steering
and
leadership
group
came
out
of
that,
but
the
main
kaun,
the
main
thing
that
was
against
it-
was
that
a
lot
of
these
JavaScript
frameworks,
especially
those
that
were
featured
in
the
initial
nine
prototypes,
had
some
disadvantages
in
terms
of
actually
being
indexed
by
search
engines.
A
During
those
discussions
we
started
to
realize
that,
while
that
is
a
disadvantage
to
the
existing
JavaScript
frameworks,
there
were
new
JavaScript
frameworks
just
on
the
horizon,
that
whose
goal
were
to
actually
improve
that
capability
to
allow
server-side,
rendering
or
server-side
building
of
the
user
interface
a
JavaScript
interface
one.
That
basically
means
is
that
Google
Scholar
could
and
exit
Google
could
index
it.
Yahoo
could
index
it
just
like
any
any
other
website.
A
Have
these
sort
of
SEO
capabilities
to
take
away
a
lot
of
the
long-term
disadvantages
that
people
have
been
saying
around
JavaScript
to
be
able
to
make
it
easier
to
index,
to
make
it
easier
to
work
with
and
make
pages
load
quicker
from
the
get-go.
So
there's
some
some
things
that
were
already
coming
out
in
angular
2.
It
was
in
beta
at
the
time
and
so
at
the
summit.