►
From YouTube: DSpace Dev Show & Tell : 2018-06-26 - OR2018 Recap
B
Fantastic,
so
what
I
was
going
to
suggest
me
Tim
you
and
I
we
can
start
out.
Maybe
you
and
I
can
share
some
takeaways
from
the
conference
point
to
some
some
relevant
links.
I
know
in
particular
pointing
to
your
demo
link
will
be
useful.
Folks
haven't
seen
that
yet
and
then
we
can.
We
can
open
things
up
to
questions
from
folks.
We've
got
a
couple
couple:
people
who
don't
have
mic
access
so
we'll
we
can
use
both
the
chat
in
the
audio
for
questions
that
folks
might
have
about
the
conference.
B
B
Sure
I
can
start
off.
So
all
of
what
I'll
do
is
I'll
share
some
links
here
in
the
zoom
chat
and
then
copy
those
the
same
links
back
over
to
the
wiki
page
after
words,
but
I
wanted
that.
The
first
thing
that-
and
this
was
a
really
nice
surprise
for
me
at
the
conference,
Tim
and
aundrea
bully
me
and
I-
gave
a
workshop
on
using
the
D
space
7,
REST,
API
and
I
think
that
the
thing
that
was
most
interesting
to
me
was
we
had
about
I,
think
40
40
to
50
folks
in
attendance.
B
B
I'm
sharing
here
in
the
chat,
a
link
to
the
slides
that
we
put
together
as
well
as,
in
addition,
those
slides,
will
link
out,
but
there's
there's
a
set
of
exercises
that
we
also
created
sort
of
to
help
people
step
through
using
the
REST
API.
So
this
these
this
material
is
there.
If
any
of
you
have
an
interest,
you
can
sort
of
use
this
material
to
ramp
up
on
the
D
space.
Seven
rest
API
and
we've
got
a
sprint
coming
up
in
a
couple
weeks.
B
So,
as
the
code
is
written,
the
supporting
documentation
to
go
along
with
the
code
will
just
sort
of
be
generated
and
be
available
for
folks.
So
that's
that's
a
some
material
I
definitely
recommend
to
people
and
then
what
I'll
do
since
we're
kind
of
just
if
we're
sort
of
taking
turns
here,
I
can
I'll
just
mention
a
couple
of
other
things
that
I
presented
and
then
I'll
take
a
turn
sharing
some
of
the
highlights
from
some
of
the
plots
I
attended
and
then
probably
ask
Tim
to
do
the
same.
B
So
if
any,
if
folks
have
questions
along
the
way
feel
free,
either
to
chime
in
the
audio
channel
or
to
post
a
message
in
the
chat.
So
another
talk,
I
was
excited
to
present
Claire
Knowles
from
University
of
Edinburgh
and
I
shared
sort
of
our
approaches
to
trying
to
introduce
triple
AF
presentation
of
images
into
our
repository,
and
so
it
was.
It
was
interesting,
just
kind
of
hearing
that
sharing
our
common
stories
along
the
way
of
you
know
what
we
wanted
to
accomplish
and
the
ways
in
which
it
caused
it.
B
The
existing
repository
model
sort
of
doesn't
exactly
work
when
you're
working
with
triple
AF.
So
some
of
the
you
know
sort
of
new
approaches
to
content
that
we've
each
taken
on
in
trying
to
integrate
triple
I,
have
so
so
very
excited
by
the
possibility,
think
it
it
offers
ways
to
present
material
that
hasn't
been
possible
before,
but
it
also
sort
of
the
the
notion
of
what's
a
collection
or
what's
an
item,
those
those
concepts
become
a
little
bit
blurred
when
you
start
working
with
triple
AF
content,
so
that
was
a
another
one.
B
There
was
another
talk
that
I
gave
with
it
was
I
was
part
of
a
panel.
Several
folks
were
presenting,
and
this
particular
talk
was
on
developerworks
paces.
So
several
folks
were
sharing
the
different
tools,
different
approaches
that
they're
using
for
working
with
their
repository
software.
So
we
had
there
was
a
talk
on
vagrant
on
docker
and
then
I
shared
some
work.
B
I've
done
using
running
D
space
on
a
codenvy
on
the
codenvy
service,
which
is
essentially
it's
sort
of
like
docker
in
the
cloud
and
an
interesting
way
to
provide
a
full
development,
build
test
environment
that
can
run
within
the
tab
of
a
browser
or
that's
accessible
from
the
tab
of
a
browser.
So
anyway,
just
kind
of
sharing
reasons.
Why?
B
So
that
was
another
one
that
was
exciting
to
put
together,
and
the
last
one
I
wanted
to
share
is
the
display
in
D
space
6,
there's
a
set
of
tools
for
reporting
on
content.
It's
really
designed
for
repository
managers.
This
has
been
in
D
space
6
since
the
first
release
the,
but
it
seemed
like
as
as
D
space
6
adoption
has
grown.
B
This
is
a
probably
a
good
time
to
remind
people.
The
functionality
is
there,
so
this
presentation
kind
of
went
through
and
described
what
the
tools
are
able
to
do
and
how
to
access
and
make
use
of
these
reporting
tools
so
Drew,
particularly
if
you've
just
upgraded
to
D
space.
6
I'd
I'd
recommend,
if
you,
if
you
did
decide
to
enable
the
REST
API,
take
take
a
look
at
these
tools
and
see
if
they
could
be
helpful
for
repository
management
and
those
sites
should
should
be
able
to
help
out
there.
B
So
those
are
some
of
the
the
key
presentations
that
that
I
made
that
I
wanted
to
highlight,
and
then
I'm
gonna
just
pop
up
and
mention
some
other
notes
that
I
took
during
the
conference.
That
I
was
particularly
excited
about,
as
I
mentioned.
I
really
was
like,
wouldn't
what
are
the
best
things
for
me
was
just
again
getting
a
better
sense
of
that.
B
B
That
are
being
integrated
into
the
code
base
and
and
just
getting
a
better
big
picture
understanding
of
some
of
those
components.
I
found
both
of
the
keynote
speakers
at
the
conference
pretty
interesting.
The
the
first
speaker
was
talking
about
having
developed
a
fan,
fiction,
site
and
sort
of
wanting
to
provide
preservation
and
access
to
fan
fiction
that
has
been
contributed
by
multiple
authors
for
many
years,
but
kind
of
an
interesting
thing
she
was
describing
was
often
the
authors
of
fan
fiction.
B
The
closing
keynote
was
a
speaker
from
Israel
who
has
maintained
I,
guess
the
largest
collection
of
digitized
material
written
in
Hebrew,
and
just
he
had
some
stunning
statistic
like
that
there
were
I
forget
there
was
some
number
he
quoted
like
7
million
Hebrew
speakers
in
the
world,
and
this
particular
site
has
like
5
million
unique
monthly
visitors
each
month.
So
just
like
that
this
is
such
a
useful
resource.
That's
such
a
large
percentage
of
the
Hebrew
speakers
in
the
world
or
actually
visit
this
site
to
access
digital
digital
content.
B
B
It's
like
an
open
hardware
component
and
this
open
hardware
component
emulates,
the
Amazon
s3
interface,
so
they're,
sort
of
I
guess
using
api's
as
if
they're,
using
a
cloud
service,
but
then
relying
on
local
hardware
components,
I,
just
I
thought
it
was
intriguing
to
hear
that
developments
have
been
made
in
that
space.
I.
Don't
I,
don't
necessarily
imagine
that
something
I
would
be
looking
at
for
us,
but
but
just
thought.
B
It
was
interesting
to
hear
that
such
a
thing
existed
and
they
were
using
something
called
get
an
X
to
track
changes
to
large
files
and
just
just
from
taking
a
look
at
what
get
an
X
is.
Is
it
it's
like
it?
It
simulates
checking
something
in
to
get
so
it
does
sort
of
the
fixity
checking
of
agat
operation
without
actually
making
a
copy
of
the
material.
So
it's
I
guess
particularly
well
designed
for
really
really
huge
assets
and
provide
some
some
integrity
checking
over
the
material.
B
So
so
that
would
that
was
one
that
was
one
I.
Just
I
was
intrigued
that
such
a
project
existed.
We
we
use
academic
preservation,
trust
as
a
preservation,
repository
and
I
was
just.
I
I
was
excited
to
hear
a
presentation
from
the
lead
developer
of
that
system.
Talking
about
building
a
tool
to
create
bag
files
for
ingest
into
the
their
ap
trust,
preservation,
repository
and
we've
got
some
custom
code.
We've
written
that
performs
that
operation,
so
I'm
excited
just
to
hear
that
a
component
may
come
along.
B
That's
provided
that
we
mabel
replace
our
custom
software
with
something
from
the
AP
trust
community
itself.
But
what
was
particularly
intriguing
to
me
was
this.
Application
has
been
built
on
electron.
An
electron
is
the
platform
that
underlies
both
the
github
desktop
software
and
the
atom
editor.
So
it's
a
it's
a
framework
produced
by
github,
that's
meant
to
be
cross-platform
and
I
just
did
assumed.
B
So
anyway,
was
just
just
kind
of
intriguing
to
hear
this
technology
being
used
in
our
you
know:
library,
technology
space,
so
those
were
those
are
the
key
highlights
that
I
wanted
to
mention,
and
you
know
feel
free
to
ask
questions
now
and
then
what
we
can
do
is
have
Tim
Tim
sort
of
describe
his
experience.
Also
I
see
that
BKA
Elm
has
joined
and
I'm
not
actually
sure
who
that
is
so.
If
you
want
to
do
a
quick
introduction,
either
by
audio
or
by
chat,
be
great
to
know
where
you're
joining
from
so.
B
A
Okay
and
I
will
note
actually
that
well,
while
you're
typing
in
things
I'm
going
to
add
in
a
couple
links
here,
because
I
was
gathering
links
while
Terry
was
talking,
some
of
the
talks
were
recorded,
but
only
in
the
one.
There
was
one
room
particular
that
that
had
the
recorded
talk
so
I
just
pasted
in
these
links,
so
there's
a
YouTube
channel
that
has
all
the
recorded
talks,
which
was
about
one
fourth
of
the
talks.
There
were
four
rooms
going
on,
but
it
included
both
keynotes.
A
So
Terry
mentioned
both
the
keynote
speakers
they're,
both
in
that
recorded
sessions
and
the
YouTube
channel
and
I
would
recommend
giving
them
a
quick
view.
If
you
get
a
chance
there
they're
a
little
long
and
that
they're
both
about
an
hour
or
so
but
they're
quite
inspiring
and
interesting
sort
of
talks
to
just
kind
of
sit
with,
maybe
over
a
lunch
or
something
and
only
the
ballroom,
a
talks
were
recorded.
A
So
the
full
conference
schedule
is
that
second
link
anything
in
the
ballroom
a
you
can
find
in
that
YouTube
channel
as
being
previously
recorded,
and
you
can
kind
of
watch
your
own
desire.
But
there
were
three
other
rooms
that
that
were
not
recorded
and
are
not
available.
Unfortunately,
but
just
wanted
to
note
that
as
other
resources
here.
B
A
Sounds
good
and
then
I
did
want
to
note
that
I
did
send
an
E,
a
summary
which
I'll
link
in
here
again
to
the
DSPs
community
list
kind
of
giving
an
overview
of
some
of
the
dspace
talks,
the
more
dspace
specific
roadmap
talks.
Things
were
working
on
the
workshops
that
we
that
we
performed
earlier
on
day,
one
at
open
repositories,
things
of
that
nature.
A
So
if
you
haven't
seen
that
email
summary
that
has
a
lot
of
the
links
that
I'll
be
sharing
here
as
well,
Terry
already
mentioned
that
there
was
on
the
first
day
day
one
we
had
two
workshops.
The
first
was
that
REST
API
workshop
that
Terry
noted,
which
was
taught
by
Andrea
Bellini
Terry
and
myself.
The
links
to
that
are
here.
So
we
have
both
the
the
slides
are
available,
as
well
as
online
exercises,
which
Terry
had
mentioned.
A
I
won't
go
into
that
in
any
more
detail
other
than
to
kind
of
just
second
Terry's
mention
of
those,
but
we
did
also
have
a
second
workshop
that
same
day
on
the
angular
user
interface,
which
was
primarily
tart
taught
by
art
Lowell,
but
I
also
kind
of
contributed
at
the
beginning
of
that.
This
is
a
second
updated
talk
based
on
the
presentations
at
open
repositories
last
year,
so
we
gave
a
similar
angular
UI
workshop
last
year.
A
This
was
kind
of
an
updated
version
of
that
with
the
latest
code
base
and
we
have
the
slides
available
publicly,
as
well
as
the
resources
around
how
how
the
or
what
resources
aren't
used,
especially
during
the
walkthrough
portion
of
the
of
the
workshop,
the
second
half
of
it.
So
if
you're
interested
in
learning
a
little
bit
more
about
the
angular
user
interface
and
just
how
to
code
and
angular,
this
is
a
good
place
to
kind
of
get
started.
A
It
kind
of
walks
through
some
of
the
syntax
of
the
angular
user
interface
and
angular
in
general
typescript,
which
is
the
language
it's
built
in,
which
is
very
similar
to
JavaScript
and
walks.
Through
a
couple
exercises
near
the
end,
around
kind
of
making
small
modifications
to
the
D
space,
angular
user
interface
to
get
a
sense
of
how
things
interact
and
how
you
would
make
various
changes
within
that
layer,
so
that's
worth
looking
at
as
well
as
you're,
starting
to
get
more
familiar
with
D
space.
Seven.
A
At
a
general
standpoint,
the
main
talk
that
I
gave
was
the
D
space
7
update,
talk,
which
was
near
the
end
of
the
conference
on
Thursday.
It
was
not
recorded,
but
I
did
record
a
demo
of
D
space
7
afterwards.
So
that's
here,
the
slides
themselves
are
at
that
tiny
URL
and
I
rerecorded
the
demo
and
put
it
up
on
YouTube
after
open
repositories
was
over.
A
So
if
you
haven't
had
a
chance
to
watch
that
demo,
we
got
a
couple
news
in
AHS,
and
people
were
pretty
happy
afterwards
got
a
lot
of
compliments
afterwards
on
the
work,
that's
gone
into:
D
space,
7
and
and
how
it's
looking
so
far,
the
slides
themselves
cover
a
little
bit
more
than
the
demo.
So
there's
a
little
bit
more
detail
in
there
around.
What's
coming
in
D
space
7.
A
Some
of
the
features
around
not
only
just
the
angular
user
interface
in
the
REST
API,
but
also
that
we're
going
to
be
adding
in
a
new
concept
called
configurable
entities
and
that's
kind
of
a
data
model
layer
enhancement
to
allow
items
to
to
represent
actual
types,
I
actually
have
typed
items.
So
an
item
could
actually
be
not
just
a
generic
concept
of
it.
You
know
it's
metadata
and
files
by
default,
but
that
an
item
could
represent
something
like
it
could
be
an
article
item.
A
It
could
be
a
journal
item
and
then
you
can
actually
relate
those
together.
You
can
say
this
journal
issue
item
relates
to
several
article
items
and
we
can
actually
store
those
relationships
within
d
space
in
this
configural
entities
model,
and
you
can
also
build
new
types
of
relationships
within
d
space.
So
we're
also
talking
about
representing
people
as
items.
So
an
author
could
be
an
item
and
an
author
could
have
his
own
relationship
with
the
various
articles
that
he
or
she
wrote.
A
So
you
could
represent
those
in
sort
of
an
author,
splash
page
or
an
author
profile
page
within
the
dspace
user
interface.
This
is
a
newer
concept
within
dc-7
and
we're
still
building
it
out.
So
we
don't
have
a
demo
of
that
within
that
recorded
demonstration.
But
I
want
to
promote
this
because
we
will
be
creating
a
brand
new
configurable
entities
working
group
coming
up
here
within
the
next
month.
Sometime
in
July.
A
C
A
There
was
also
more
information
about
configurable
entities,
specifically
that
came
out
just
after
open
repositories
in
a
statement
from
the
steering
group
and
I'll
just
link
that
in
here,
so
this
was
post
Oh,
our
post
Oh
are
2018
and
it
just
has
links
off
to
some
of
the
resources
around
why
this
decision
was
made
and
what
the
general
design
is
is
we're.
Building
we're
building
from
is
linked
off
from
there
as
well
and
I,
see
Jordan
asked
the
entities
of
D
space.
Seven
are
the
ones
already
available
in
D
space
Chris.
A
So
it's
definitely
in
lining
us
up
with
these
space
Chris,
but
whether
that
all
happens
in
D
space
7
or
whether
part
of
it
happens
in
D
space
7
and
the
rest
of
it
happens
in
D
space
8.
That's
still
yet
to
be
decided
based
on
how
much
can
achieve
and
the
development
in
the
coming
months,
because
we're
not
wanting
to
delay
dspace
Evan
for
several
years,
we're
really
pushing
hard
to
get
that
out
in
early
2019
and
we'll
get
as
many
of
these
entities
into
it
as
we
can
by
2019.
A
So
there's
more
information
about
each
of
those
there.
If
you
want
to
learn
a
little
bit
more
about
that,
let's
see
the
other
thing
that
I
did
want
to
mention.
That's
coming
in
D
space
7.
Besides
the
angular
UI,
the
rest,
api
and
configurable
entities
is
we
have
other
alignment
with
the
next-generation
repositories,
recommendations
which
I
just
mentioned
so
we're
working
towards
having
resource
sync
out-of-the-box
in
D
space,
7,
there's
links
to
that
out
of
that
slide
deck
or
that
D
space
7
update
slides.
A
So
there's
that
coming
there's
also
a
support
for
sign
posting
which
will
be
coming
in
D
space.
7.
That's
another
recommendation
out
of
the
next-gen
generation
repositories.
This
is
more
for
for
kind
of
harvesters
or
machines.
It's
basically
a
best
practice
for
embedding
information
about
your
repository
within
HTTP
headers,
and
it's
kind
of
a
more
important
for
for
harvesters
or
or
spiders
or
things
of
that
nature,
because
it
allows
us
to
do
things
like
when
a
spider.
Harvester
is
hard.
A
Dean,
say
an
item
item
splash
page
rather
than
them
having
to
download
the
entire
item,
splash,
page
and
search
for
the
link
to
the
PDF
within
that
item,
splash
page
instead
via
signposting,
we
can
provide
a
direct
link
to
the
PDF
within
the
HTTP
headers
and
when
it's
in
the
HTTP
headers,
that
means
they
not
only
don't
have
to
download
the
entire
HTML.
They
can
just
grab
the
headers,
but
it
also
allows
them
to
jump
immediately
to
download
the
PDF
if
that
spider
is
really
interested
in
and
gathering
PDFs
or
things
of
that
nature.
A
There's
more
information
at
signposting
org
on
that,
and
that's
also
linked
off
the
slide
deck
as
well,
so
that
was
all
presented
as
part
of
the
dspace
7
update.
I
also
gave
that
demo
of
of
how
the
angular
user
interface
currently
looks
right
now,
including
some
flashy
demonstration
of
the
of
the
submission
and
workflow
functionality.
I
won't
go
through
that
here
today,
just
because
that
is
available
on
YouTube
and
I'm,
trying
to
think.
A
We
essentially
mean
we
want
to
have
something
that
is
testable
by
the
community,
that
community
members
can
download,
install
locally
and
start
to
bang
against
and
report
bugs
back
on.
It
may
not
have
every
single
feature
in
there
yet,
but
hopefully
it
has
95%
of
the
features
that
are
coming
into
East
Bay
7
would
be
in
that
beta,
so
give
a
really
good
sense
of
what
these
be.
7
is
going
to
look
like
me
the
end
of
this
year
and
then
the
next
deadline
would
be
a
initial
release
candidate,
which
would
be
feature
complete.
A
That
would
come
in
early
2019.
It
would
be
another
opportunity
to
folks
to
download
and
bang
on
it
report
bad
bugs
or
issues
they're
seen
and
then
shortly
thereafter
from
that
we
would
put
out
the
final
release,
hopefully
within
a
matter
of
weeks,
but
it
really
is
dependent
on
the
number
of
bugs
we
locate
and
things
of
that
nature.
But
the
overall
goal
is
early
2019.
We
would
have
these
days
seven
out
and
at
open
repositories
2019.
A
We
would
do
more
user
training
and
upgrade
training
and
things
of
that
nature,
how
you
can
customize
your
user
interface
and
things
of
that
nature,
for
that
would
be
of
interest
to
most
institutions
wanting
to
install
and
use
these
base.
Seven,
and
the
last
thing
that
I'll
mentioned
that
I,
promoted
kind
of
throughout
the
conference
is
the
upcoming
dspace
seven
sprints,
which
Terry
mentioned
as
well.
A
The
DCA
seven
Sprint's
are
listed
from
this
tiny
URL.
The
next
one
is
coming
up
in
July
here,
July
9th,
through
20th
I,
believe
it
yet
9
through
20th
there's
no
requirements
for
for
how
much
time
you
put
into
a
sprint,
you
could
come
in
and
join
for
one
week.
You
could
join
and
just
grab
a
ticket
or
two
and
help
out,
but
we
will
have
coaches
available
to
help
you,
along
with
actually
fixing
bugs
or
making
small
improvements
to
the
REST
API
and
the
angular
UI.
A
The
last
time
we
ran
these
sprints
in
May
we
had
several
new
people
who
had
never
worked
with
D
space
7
before
Terry
mentioned
that
he
didn't
have
a
whole
lot
of
experience
with
the
new
REST
API.
But
yet
he
learned
a
lot
on
on
the
ground
there
and
then
helped
us
with
some
of
the
training
at
open
repositories.
We
also
had
a
couple
folks
who
had
never
even
submitted
a
pull
request
to
DS
Base
ever
submitted
their
very
first
pull
requests
as
part
of
those
DS
base.
A
7
sprints,
so
we'd
encourage
you
to
join
up.
If
this
is
at
all
interesting
to
you,
no
real
experience
required.
We
would
recommend
having
experience
with
DS
base,
of
course,
just
to
know
the
concepts,
but
you
don't
really
need
to
know
D
space
7.
It's
really
an
opportunity
to
just
kind
of
dive
in
and
start
to
really
learn
in
a
hands-on
fashion
and
have
those
coaches
available
on
slack
to
kind
of
help
out
on
a
day
to
day
basis,
to
really
kind
of
help.
A
You
get
past
any
roadblocks
that
you
get
along
the
way
and
I
see
drew
mentioned
a
direct
link
to
the
road
map.
The
road
map
is
is
in
the
the
slide
deck
from
open
repositories.
We
do
have
a
a
road
map
on
the
wiki,
but
I
admit
that
I
have
been
so
busy
since
open
repositories
that
I
have
not
had
a
chance
to
sync
that
up
completely
with
what
was
presented
at
open
repositories.
A
So
if
you
look
at
the
the
road
map
is
in
the
slide
deck,
that's
called
our
2018
D
space
7
in
this
tiny
URL.
It
lists
that
road
map
for
D
space
7.
We
do
also
have
a
wiki
road
map
which
is
listed
here,
but
those
URLs
seem
to
have
smashed
together.
Apologies
on
that,
let
me
try
and
separate
those
out,
so
here's
the
first
one
and
then
I
get
the
second
one
here,
there's
the
second
one
okay,
so
there
is
a
wiki
Road
map.
A
And
I'm
trying
to
think
there's
anything
else
to
note
I
think
that's
the
the
basics
of
it.
Also
in
my
in
my
email
summary
to
the
to
the
mailing
list,
I
did
also
mention
the
repository
rodeo,
which
is
something
that
I
did
not
present
on,
but
marine
Walsh
who's
on
our
steering
group
presented
the
D
space
overview
there.
A
So
that
also
gives
you
different
perspective
on
what's
going
on
in
the
D
space
world
and
she's
got
a
more
non-technical
perspective
as
a
repository
manager,
so
that
the
slide
deck
from
that
is
linked
here
and
there
was
this
panel
was
actually
recorded.
So
it's
worth
watching
that,
if
you're
interested
in
this,
the
repository
rodeo
panel
is
a
panel
where
all
of
the
repository
systems
basically
give
brief
updates
on
what
has
gone
on
over
the
last
year.
A
What's
going
on
with
like
fedora
with
sam
vera,
with
with
eprints
with
dspace,
of
course,
and
any
of
the
repository
platforms
that
were
there
at
open
repository.
So
it
gives
you
a
good
sense
of
kind
of
an
overview
of
what
everybody's
been
working
on,
what
the
directions
are
of
each
of
the
platforms.
So
if
that's
of
interest
the
slide
deck
is
there
and
the
full
panel
was
recorded
and
could
be
streamed
off
youtube
there
and
I
think
that's
all
that
I
really
had
to
report
on
I'd
meant
I
admit.
A
My
attendance
at
o
R
was
was
I,
got
yanked
into
a
lot
of
site
meetings
which
happens
at
open
repositories,
so
I
did
not
get
to
get
to
see
as
many
of
the
sessions
as
Terry
noted,
but
I
did
enjoy
the
the
plenary
speakers,
the
opening
and
closing
plenaries.
Those
were
quite
quite
inspiring.
Quite
useful.
I'd
recommend
giving
them
a
try
on
YouTube
and
and
we'll
see
what
other
sort
of
links
we
can
gathered.
Other
resources
I
think
from
open
repositories
that
Terry
was
working
on
so
I
think
that's
it
for
me.
Basically,
yeah.
B
A
C
Had
a
question
about
the
changes
to
the
API
in
dspace
7,
our
metadata
librarian
has
done
a
lot
of
really
useful
work
in
writing.
Python
scripts,
that
code
against
first
the
D
space,
5
API,
and
then
we've
updated
it
for
the
36
API
and
we're
now
using
those
on
a
regular
basis
in
order
to
do
bulk,
uploads
and
various
metadata
remediation
activities.
For
our
repository,
it
sounds
like
since
you're
changing
the
the
underlying
structure
that
the
API
is
built
on.
C
Obviously,
there's
there's
going
to
be
some
changes
there
and,
as
you
come
up
with
a
new
entity,
so
there
are
going
to
be
changes
on
that
level,
but
will
the
the
API
itself
or
the
the
operations
that
continue
to
that
have
existed
in
the
past
and
exist
in
the
future?
Are
those
likely
to
change?
Well,
we
probably
need
to
rewrite
all
of
those
scripts,
or
are
you
making
an
effort
to
keep
the
the
coding
interface
for
those
those
stable
features,
stable.
A
A
So
in
dspace,
seven,
yes,
the
rest
api.
Well,
I'll
give
you
two
to
answers.
First
off
the
the
D
space.
Six
rest
api
is
being
ported
to
the
D
space
seven
code
base,
so
it
will
be
still
available
in
D
space
seven,
but
it
will
be
deprecated
because
part
of
D
space,
seven
is
where
we're
rebuilding
that
REST
API
from
the
ground
up.
So
we
basically
will
have
to
rest
api's
in
d
space,
seven
alone,
as
if
d
space,
eight
only
the
new
restive
api
will
be
available.
A
So
so
you'll
you'll
have
an
opportunity
to
be
able
to
still
use
that
existing
REST
API,
as
is
in
D
space,
7
and
then
port
over
your
scripts
to
the
new
D
space.
Seven
rest
api.
The
reason
why
we
are
doing
that
is
because
the
old
rest
api,
the
one
that's
in
d,
space,
6
and
below,
is
not
very
feature
full.
It
doesn't
provide
a
whole
lot
of.
It
doesn't
actually
provide
access
to
all
the
features
within
d
space
and
it's
also
very
sort
of
custom.
A
We've
taken
a
major
step:
well,
we
took
a
step
back
first
to
analyze
that
and
make
sure
we,
it
wasn't
really
possible
to
move
forward
on
the
angular
UI
and
we
realized
very
early
on
that
with
the
angular
UI,
we
needed
to
modernize
the
REST
API,
both
in
terms
of
just
making
it
feature
'full
so
that
you
could
access
everything
through
the
REST
API
in
d
space
as
well
as
we
needed
to
align
it
better
with
a
lot
of
the
modern
best
practices
around.
How
do
you
build
a
modern,
REST
API?
A
How
do
you
ensure
that
it
is
easy
to
use
and
sort
of
self
documenting,
and
so
that's
what
we've
done
in
D
space
7?
So
we
have
a
demo.
Let
me
show
you
the
demo.
Rest
API
is
linked
here.
It's
hosted
by
for
science,
one
of
our
service
providers
and
if
you
go
to
that
site,
you'll
notice,
there's
actually
a
user
interface
here,
which
is
not
something
we
built.
This
is
a
third-party
tool
called
the
Hal
browser
and
it
it's
it's
one
of
these
things
that
we've
aligned
with
in
terms
of
best
practices.
A
So
you
can
now
actually
browse
our
new
REST
API
through
this
hal
browser,
because
we've
we've
got
a
REST
API
that
aligns
with
the
hal
data
format
and,
and
you
can
go
scroll
down
and
there's
links
down
there
in
the
lower
left.
You
can
click.
Those
are
all
of
our
endpoints
that
are
currently
available
in
the
d
space.
A
Seven
rest
api:
you
can
click
into
any
one
of
those
and
get
a
sense
of
how
they're
how
it
responds
and
how
you
can
interact
with
it
because,
as
you
browse
down
to
each
link,
there's
there's
links
underneath
those.
So
it
gives
you
suggestions
on
where
to
go
next
in
terms
of
what
you
can
do
at
each
of
these
endpoints.
So
it's
almost
self
documenting
in
a
way
already,
but
there's
also
going
to
be
a
next
step
that
if
you
look
down
to
that
links,
section,
there's
several
columns
in
that
table.
There's
a
docs
column.
A
That's
immediately
to
the
left
of
the
get
column.
Currently,
there's
nothing
there,
but
it
will
be
there.
There's
going
to
be
links
where
you
can
actually
clink
click
into
the
documentation
from
this
user
interface
and
actually
see
the
documentation
and
that
documentation
is
automatically
generated
based
on
the
D
space.
Seven
rest
api's
integration
tests.
A
So
it's
basically
a
way
that
we're
coding
the
rest
api
that
allows
it
to
be
self,
describing
self
documenting
much
easier
to
interact
with,
and
it
also
aligns
with
all
the
best
practices
and
standards
out
of
a
modern
rest
api,
and
it
also
provides
all
the
features
that
we
need
out
of
the
angular
UI.
So
this
is
kind
of
why
we
have
had
to
deprecate
the
old
rest
api
in
favor
of
this
new
one.
A
B
One
of
the
features,
particularly
of
the
new
REST
API
that
I'm
excited
about
this
is
this-
is
still
in
development.
There's
going
to
be
a
parameter
that
you
pass
in
when
you
make
a
request
called
projection
and
that
will
sort
of
help
how
much
content
comes
back
so
I,
don't
know
if
you've
tried
with
the
older
rest
API
to
like
crawl,
the
hierarchy
and
it's
you
kind
of
either
run
into
a
challenge
of
either
you
don't
get
enough
information
back
or
you
you
kinda
almost
down.
B
This
need
to
pull
the
whole
community
collection,
all
the
data
about
each
object
back
in
order
to
construct
or
replicate
the
hierarchy,
and
so
there's
going
to
be
an
intelligent
way
to
say,
I'm.
Looking
for
this
collection
or
I'm
looking
for
this
community
and
here's
the
projection
of
it
that
I'm
looking
at
and
it
will
the
way
I'm
understanding
it
is.
If
you're
sort
of
navigating
down
the
tree,
you'll
get
the
right
returned
objects
to
help.
B
You
descend
the
hierarchy
and
if
your
focus
is
really
going
up
the
hierarchy,
you
can
also
set
your
objects
in
a
way
that
you'll
get
the
right
objects
to
navigate
up
the
hierarchy,
so
I
think
there's
a
more
there's
going
to
be.
You
know,
in
addition
to
the
fact
that
it's
going
to
support
all
the
operations
of
the
UI
I,
think
it's
going
to
even
solve
some
of
the
things
that
were
difficult
with
the
old
API
yeah.
A
And
I
see
Drew
responded
positively,
so
good
to
hear
that
you
think
the
direction
is
good
here,
because
we're
very
excited
about
this
as
well.
People
don't
tend
to
get
excited
that
much
about
a
REST
API.
But
but
if
you
talk
to
all
of
us
about
it
these
days,
we're
like
wow.
This
is
so
awesome,
so
so
yeah
you're,
gonna
I,
think
there'll
be
a
lot
more
opportunities
to
really
build
things
against
this
new
REST
API
going
forward.
B
B
B
B
Well,
Tim
Tim's
been
kind
enough
to
capture
these
recordings
and
get
those
posted
so
we'll
we'll
add
that
to
the
wiki
page
and
then,
as
Tim
was
talking,
I
went
through
and
added
to
the
wiki
page
for
today's
meeting.
All
of
the
links
I
I
may
have
duplicated
a
couple
links
more
than
once,
but
anyway,
everything
that
we
shared
at
least
a
link
to
it
should
be
there
if
you
need
to
find
it
again.
A
Thank
you
all,
and
definitely
let
us
know
if
you
have
ideas,
further
developer,
show-and-tell
meetings
coming
forward,
because
I
agree
that
I
see
drew
noted
that
they're,
very
valuable
sessions
and
I
think
these
are
a
good
point
for
us
to
all
kind
of
touch
base.
So
let
us
know
if
you
have
ideas
of
other
things,
we
can
kind
of
help
folks
get
up
to
speed
with
or
anything
that
you'd
like
to
present.