►
From YouTube: 2018-02-23 Meeting of the DSpace Entities Working Group
A
Recorded
session,
okay,
hello,
so
I'm
sharing
my
screen,
can
you
see
I
just
prepared
this
small
presentation
and
for
this
meeting
and
I
will
just
want
to
review
some
of
the
prior
meetings?
I
would
say:
topics
first,
the
the
motivation
that
bring
us
all
to
to
this
group.
Then
we
had
a
deep
drive
dive
into
this
phase
Chris
and
how
he
can
manage
manage
outdoors.
A
A
We
then,
at
that
time
we
could
see
the
the
installation
process
configuration
and
some
examples
on
what
we
could
do
with
this
base.
Chris
then,
on
our
last
meeting,
we
spoke
a
little
bit
about
the
this
place
that
model
about
our
needs
for
some
specific
entities.
What
entities
could
be
inserted
or
be
as
default
in
this
space,
and
today.
A
A
A
I
will
keep
this
step.
This
is
some
of
the
concepts
that
that
we
defined
entity
entity
identify
what
is
an
entity
identifier
content.
What
is
a
field
type
or
what
could
be
complexed
fields
or
entity
relationship?
This
is
some
definition,
and
this
is
the
the
main
concerns
that
we
are
having
the
spoke
speak
speaking
on
our.
A
Meetings,
the
the
data
model,
complexity
versus
the
flexibility,
what
we
want
to
where
we
want
to
draw
a
line
here,
also
the
need
to
have
nested
metadata,
because
this
space
only
relies
on
this
flat
metadata
and
we
need
to
wouldn't
we
need
this
place
to
be
more
configurable
and
what
is
should
be
the
default
and
what
should
be
available
to
the
user
interface
and
how
entities
can
relate
and
with
with
each
other.
What
is
the
data
model
that
could
support
that?
A
A
A
And
that
that
that
is
on
our
documents,
that
is,
it,
is
shared
and
can
be
discussed
and
can
be
commented.
I
will
stop
here.
We
I
have
more
slides,
but
I
will
stop
here.
This
presentation
and
I
want
to
focus
on
these
questions
and
I
think
we
would
like
to
to
to
get
near
to
to
some
decisions.
What
we
want
to
do
before.
B
Yeah
Thank,
You,
Paula
and
and
I
think
these
are
really
good
questions
that
you
brought
up
and
I
agree
with
some
of
it
with
some
of
the
points
that
you
put
it
out
in
the
document
here
around
like
the
normalization
issue,
I
think
that's
there's
definitely
some
improvements
that
could
be
made
in
the
giant
table.
Example.
You
had
the
document
with
all
the
nulls.
That's
obviously
not
ideal.
This
team
that.
A
A
A
Fields
or
field
values
with
other
entities,
we
you,
you
can
see,
projects,
researcher,
page
or
profile
organization,
units
dynamic
and
they
all
have
new
values
and
also
they
have
text
value
link.
If
this
was
a
link,
this
is
trunk.
Truncated,
I
dreamed,
I
can't
see
file,
name
double
value.
This
isn't
a
numeric
value,
I
think
so.
A
B
B
C
C
Normalized
normalizing
table,
for
example,
this
this
kind
of
table
can
be
divided
in
many
tables
and
we
have
to
join
them,
but
we
have
bad
results
in
performance.
So
yes,
so
we
decided
that
it's
not
a
good
structure
for
a
database
artist,
but
s
conserve
performance.
We
have
better
results
using
these
structures
structure,
then
using
more
atomic
tables.
C
B
B
I'm
curious,
though,
to
hear
from
others
as
well
who
brewed
this
document
to
see.
If
anything
has
popped
out
to
you
as
being
something
we
should
concentrate
on
a
little
bit
more
discuss
a
little
bit
more
or
something
that
you
either
agree
strongly
with
or
disagree
strongly
with
or
just
have
questions
about.
D
I
think
also
regarding
the
experience
with
this
base
crease
in
terms
of
developments,
we
have
now
the
capacity
to
look
at
this
and
say:
ok.
This
is
better.
This
way
these
parts
we
can
simplify.
We
can
make
this
more
simple
in
this
space,
so
I
think
we
have
already
some
things
where
we
can
look
at
and
try
to
orient
in
in
some
aspects.
D
If
we
should
make
the
same,
if
we
should
make
it
different,
but
I
think
we,
we
need
to
be
flexible
enough
to
maintain
this
place
as
a
repository
platform
that
can
be
able
to
be
integrated
in
different
services
and
I.
Think
that
the
flexibility
and
the
simplicity
will
be
the
core
values
we
should
consider
this
way.
D
Another
aspect
is
also
the
real
it's
about
this
new
model
of
the
space,
because
we
are
developing
now
some
tests
regarding
use
of
different
types
of
metadata
metadata,
not
in
a
flat
structure,
and
we
really
need
to
have
a
global
solution
for
the
space
and
not
only
some
plugins
or
developments
folder.
So
I
think
it's
important
to
try
to
not
try
to
this
and
try
to
to
make
this
a
little
bit
of
a
reality
in
the
space,
or
at
least
how
can
we
make
this
reality
of
this
place
and
make
the
next
steps
for
that.
B
Thank
You,
Jose
and
I
agree
with
that
I'd
like
to
turn
this
into
a
reality
as
soon
as
we
can,
but
with
the
realization
that,
obviously
we
want
to
try
and
make
sure
that
we're
going
towards
the
the
the
same.
The
same
vision
in
the
end
were
aligning
the
the
work
with
towards
that
vision,
of
course,
which
is
pretty
much
I.
Think
what
you
were
saying
as
well
so
I
think
we're
all
in
agreement
on
that
or
others
do
others
want
to
add
any
thoughts
into
here.
B
A
B
So
so
the
other
thing
that
I
added
some
other
comments
in
here
I,
don't
think
we
need
to
go
through
all
of
them,
but
but
I
saw
that
Apollo.
You
had
responded
to
them
around
the
table
structure
and
things
like
that.
Those
were
mostly
nitpicky
things,
I
wasn't
taking.
Offense
I
was
just
thinking
that
the
topic
here
was
a
little
bit
off
in
terms
of
the
discussion
so
like
on
page
okay,.
A
B
B
That
that
were
that
more
tables
is
bad
in
some
way
and
that
we
would
accept
dspace
Chris
all
at
all,
as
as
it
is,
which
I
don't
think,
we've
ever
really
discussed
yet
so
so
it's
just
kind
of
worth,
noting
that
I
think
that
the
the
structuring
configurations
area
here
we
might
want
to
kind
of
look
at
a
little
bit
more
as
to
whether
this
is
important
to
keep
as
part
of
this
document
or
what
the
main
point
is.
What
I
was.
A
A
A
Eventually
put
the
number
of
tables,
but
I
saw
that
this
best
crease
has
some
redundancy
on
the
the
structure.
These
22
tables.
They
they
also
repeat
for
other
entity
type
for
I,
was
such
a
page
on
the
researcher,
page
or
organization
unit.
You
have
the
same
that
you
have
a
pattern
that
repeats
for
every
type
of
entity.
B
B
C
I
think
in
this
way
there
are
much
much
more
users
than
can
configure
the
the
user
interface,
also
without
any
expertise
in
database
modeling,
because
if
you
talk
on
tabs
boxes,
there
are.
These
are
concepts
that
are
more
familiar
to
every
kind
of
user
instead
of
tables
attributes
in
a
referential
integrity
and
so
on
so
I
think
this
kind
of
mixing
database
concepts
and
user
interface
concepts
can
help
many
users
in
being
able
to
configure
him
there.
This
base
Chris
instances,
even
if
they
they
don't
know
anything
about
database
modeling,.
B
A
One
at
one
of
the
the
comments
that
I
put
in
one
in
this
thread
is
the
I
think
we
should
draw
a
line
where,
where
we
want
or
one
we
want
our
database
or
database
that
database
to
be
able
to
store
what
what
is
the
bounds
or
the
limits
and
I
think
one
limit
is
the
the
presentation
layer,
I
think
it
it
should
be
outside
the
displace
database.
I.
B
A
B
B
D
What
this
base
now
provides,
for
example,
if
I
want
to
configure
an
input,
forms
I
need
to
edit
an
XML
file
I.
Do
it
one
time,
maybe
two
times
three
years
we
can
change
or
configure
something
else
or
add
some
collections,
for
example,
to
a
specific
form.
I
think
we
can,
for
example,
easily
add
this
on
the
user
interface,
but
we,
if
we
don't
have-
and
if
we
have
something
easy
to
configure
for
this
kind
of
aspects
that
we
made
one
or
two
times
per
year.
D
I
think
it's
not
critical
aspects,
while
it's
on
the
user
interface
anyway,
I
think
in
the
future.
It's
normal
and
I
think
the
recent
features
goes.
This
way
it's
basically
to
have
a
dashboard
of
administration
of
the
whole
repository
where
we
can
configure
associate
things
on
the
user
interface.
By
now,
for
example,
we
can
register
new
metadata
schema,
had
some
elements,
qualifiers,
etc.
D
We
we
can
have,
as
I
have
already
said
in
the
last
meeting,
I
think
some
kind
of
predefined
configurations
for
specific
use
cases
of
the
repository.
So
if
you
have
a
scientific
repository,
we
can
have
specific
objects
that
we
can.
We
can
input
or
fill
in
the
database
to
create
a
structure
that
is
usually
used
for
an
institutional
repository.
D
If
we
have
something
more
focused
on
research,
data
or
digital
library
or
the
national
resources,
we
can
have
other
different
types
of
brain
configurations,
for
example,
for
the
repository
and
I
think
this
is
a
way
where
we
can
give
to
the
developer
that
will
install
the
space,
something
that
is
almost
ready
to
use
and
I.
Remember,
for
example,
when
I
I
started
looking
for
this
space,
maybe
10
12
years
ago,
I.
D
Remember
the
the
blue
layout
with
this
base
logo
that
we
can
see
in
many
many
many
configurations
and
installations
of
the
space,
because
people
don't
have
the
capacity
or
the
possibility
or
I,
don't
know
to
just
change
the
display
slope
or
put
the
institutional
logo.
But
if
we
have
this
configured
in
the
administration,
for
example,
just
to
upload
an
image
in
dimensions
that
can
be
fit
for
a
specific
logo,
it
will
be
easy
to
configure.
D
D
If
we
look,
for
example,
I
make
sometimes
the
comparison
with
the
current
CMS,
like
WordPress
or
Drupal,
or
any
others
that
we
can
easily
choose
a
different
template,
we
can
easily
put
some
CSS
select
a
specific
color
for
the
other
change
the
and
we
do
this
easily
on
any
wall
system.
So
I
think
we,
we
should
think,
but
I.
D
D
B
A
B
While
you're
doing
that,
Paulo
I
do
want
to
first
off
thanks
thanks
for
sharing
that
that
point
of
view
Joe's
a
the
one
thing,
I
will
note
there
is
ironically
well
well
you
say
that
these
things
are
not
very
as
important
or
they
only
get
changed
infrequently.
Ironically,
the
requests
that
I
hear
most
from
dspace
users,
from
like
D
Kat
and
from
other
folks
at
conferences
is
they
want
to
be
able
to
do
things
like
manage
those
input,
forms
manage
the
submission
process
and
things
from
the
admin
user
interface.
D
D
F
B
Think
the
only
reason
I'm
poking
at
this
a
little
bit
I
agree
with
that.
I
agree
that
it's
less
it's
lower
priority,
but
the
only
reason
I'm
poking
at
this
is
because
it
goes
back
to
this.
This
section
of
the
document
that
the
paolo
had
mentioned
and
that
I
had
that
I
commented
on
is
that
there
was
a
discussion
here
about
DS
based
Chris.
Has
all
these
extra
tables
to
store
this
user
administrative,
stuff,
user
interface,
administrative
stuff?
B
So
the
reason
I'm
poking
at
this
is
because
I
think
we
should
be
analyzing
that,
as
part
of
the
bigger
picture
here,
some
what
we
can
decide
that
we
don't
want
to
do
it
right
now,
but
I
think,
since
these
days
chris
has
this
functionality
in
there.
It
is
worth
analyzing
whether
the
way
these
base
Chris.
Does
this
aligns
with
the
views
of
how
we
think
these
bays
should
go
forward?
What
that
roadmap,
our
vision
looks
like
or
whether
it's
doesn't
align
as
well
as
it
does
it
may,
because
they
already
have
these
features.
B
E
B
B
G
B
You're
saying
that
the
D
space
Chris
structure
is
complex,
but
part
of
the
reason
it's
complex
is
to
be
able
to
support
this
use
case.
If,
if
we're,
if
we're
looking
at
the
the
complexity
versus
the
vs.,
just
how
the
D
space
model
is
I,
think
we
need
to
analyze
which
parts
of
D
space
Chris
are
for
this
bit
specific
use
case
of
the
admin
user
interface
and
which
parts
of
D
space
Chris
are
just
for
the
data
model,
because,
because
we're
analyzing.
E
B
We
don't
need
all
these
tables
and
we're
going
to
try
and
build
it
ourselves
and
as
we
build
it
ourselves,
we're
gonna
realize
that
down
the
line
as
we
get
Z
space
ad
space
9,
and
we
want
this
complexity
in
this
admin
UI.
We
have
to
go
to
the
same
same
sort
of
route.
So
that's
where
I'm
trying
to
get
at.
A
B
B
G
I
agree
with
what
you're
saying
Tim
that
we
should
definitely
analyze
it,
because
it
is
a
very
wanted
feature
in
D
space
but
I.
My
first
did
the
first
thought
and
it
could
be
wrong,
but
the
first
thought
that
came
up
in
my
head
when
you
said
that
was
that
I
think
that
maybe
the
the
angular
UI
will
give
us
other
opportunities
here
and
where
you
don't
necessarily
have
to
store
it
in
this
way
in
the
data.
G
G
A
G
For
example,
you
could
have
a
mechanism
where
you
you
build
all
of
that
and
store
it
in
I.
Forget
the
names
that
Redux
or
that
that
date,
a
model
in
the
JavaScript
and
then
send
it
has
one
right
to
I
mean
it
will
work
slightly
different
I,
don't
want
to
go
into
yeah
technical
detail,
but
you
have
more
opportunities
there
and
there
might
even
be
for
angular
certain
things
available
as
libraries
to
do
this.
Plus
you
can
do
inline
editing.
B
Don't
have
to
get
into
too
much
I
get
the
point
and
I
do
agree
that
you're
right,
we
don't
want
to
make
this
three
four
year,
five
year
project
to
try
and
get
this
implemented
or
get
it
started,
so
maybe
maybe
the
best
way
to
go
forward.
This
is
to
look
back
at
this
analysis
document
that
Paolo
wrote
up
and
and
start
to
tease
apart,
which
things
are
this
the
second
tier,
the
second
step,
the
admin
user
interface,
things
and
which
things
are
actually
just
getting.
The
basic
data
model
changes
recently
sees
yes,.
F
B
Agreed,
yes,
I
think
that's
what
what
I?
What
is
lacking
right
now,
here's
some!
What
is
that
it's
kind
of
all
kind
of
lumped
together,
especially
in
that
default,
structuring
configuration
section,
which
is
where
I
added
all
those
comments,
because
I
think
we
need
to
to
change
this.
So
it's
more
talking
about
the
default
structure
and
configurations
only
related
to
the
data
model
that
basic
data
model
that
first
step
the
first
stage
and
then
separate
out
the
user-interface
question.
That's
stage
when.
A
B
B
How
could
we
achieve
that
in
d
space
knowing
and
then
looking
at
that
and
knowing
that
we
also
have
the
second
stage
that
will
be
coming
up
eventually,
which
is
more
around
okay.
Then
you
know
what
would
the
second
stage
look
like
where
we
can
start
to
deal
with
administrative
capabilities
at
the
user
interface
level,
but
kind
of
just
separating
those
out
into
two
stages
more
clearly,
so
that
we
could
analyze
them
a
little
bit
easier?
Lumping
them
together,
I
think
is
too
confusing,
at
least
to
me.
Okay,.
A
G
F
G
Say
well
one
thing
so
sorry
so
I.
What
I
think
would
be
best
at
this
point
is
to
have,
like
you
said,
focus
on
on
how
the
entities
are
stored,
how
the
relationships
are
stored,
etc
and
then
keep
everything
else
in
line
with
how
D
space
works
right
now,
so
that
we
can
easily
tackle
it
as
a
follow-up
project.
G
G
Okay,
now
are
you
gonna
go
and
take
a
look
at
how
to
do
all
of
this
in
the
user
interface
that
we
just
have
to
do
have
to
replace
at
that
underlying
system
and
the
user
interface
for
the
input
forms
and
that
everything
is
replaced
all
at
once,
so
that
we
don't
anything
that's
in
between
of
what
we
have
now
in
dspace
or
what
these
face
Chris
does.
It
should
be
one
of
the
two,
but
nothing
in
between
that's
something.
I
was.
G
Because
if
you
do
it
completely
in
line
with
input,
forms
like
you
could
use
the
same
elements
to
one
box
or
two
box
and
use
the
metadata
registry
and
have
a
metadata
registry
schema
separate
for
authors
and
so
you're.
Just
extending
it
slightly
to
support
multiple
entities
then
later
on,
we
don't
make
it
too
difficult
for
ourselves
to
do
something
to
have
that
be
implemented
in
the
UI
to
have
it
customizable
in
the
UI,
and
just
only
have
I
mean
in
in
theory.
F
B
Yeah
yeah
I
can
I
agree
with
that
and
I
think
it's
that
first
stage
that
we
need
to
analyze
a
little
bit
more
into
how
we
would
get
to
that
that
sort
of
first
stage
and
whether
dspace
Chris's
structure
helps
us
get
there
better
or
something
we
could
build
off
of
or
whether
we
feel
that
it's
more
of
an
inspiration
to
build
to
modify
the
existing
data
model
in
ways
that
are
laid
out
in
this
document.
Yeah.
G
I'm
thinking
about
I'm
sorry,
it
may
be
slowed
down
the
discussion
going
through
the
document,
but
we've
done
something
similar
and
in
other
projects
with
datasets
and
things
like
that
and
the
extension.
You
have
to
build
us
to
extend
how
you
make
the
relationship
between
different
objects
in
the
whole
submission
steps.
So,
let's
say
you're
creating
an
author.
How
do
I
attach
that
to
items
in
these
space?
Do
I
use
the
author
field
and
do
I
base
it
on
the
name.
Do
I
need
something
more
do
I
need
identifiers.
G
How
do
I
do
that
because
you
don't
want
to
create
an
author
object
for
every
author,
that's
in
the
Republic,
or
you
only
want
to
do
it
for
a
number
of
authors
and
then
that
I
think
is
the
more
important
extension
to
think
about
in
the
user
interface.
How
do
you
make
those
relationships
and
what
is
mandatory
and
what's
not.
B
G
B
So
it's
kind
of
around
the
the
idea
of
having
those
core
entities
in
place
with
the
ability
to
then
extend
it
for
Chris
specific
use
cases
which
is
with
dc-based
Chris's
around
or
just
leave
those
core
entities
and
use
it
as
an
institutional
repository
and
and
potentially
have
an
external
Christian
working
with
or
not.
But
but
I
do
recall
kind
of
discussing
that
briefly,
we
didn't
really
come
to
like
a
conclusion
about
it,
but
I
know
that
we
had
mentioned
that.
That's
a
necessary
use
case.
Okay,
because.
G
B
E
A
B
The
the
brainstorm
that
you
got
that
you
were
about
to
go
over
at
the
end
of
this
document,
I
think
it'd
be
useful
to
have
everybody
sort
of
look
at
that
in
more
detail
before
the
next
meeting,
especially
on
Draya,
Bellini
and
I
can
also
pass
that
off
to
the
committers
group,
the
dc-based
committers
group,
to
see
if
any
of
them
have
any
thoughts
on
these,
these
brainstorms
around
data
modeling,
and
perhaps
we
can
concentrate
more
on
that
for
the
next
meeting.
Okay,
okay.
Does
that
make
sense?
Yes,
good.
G
A
A
G
Because
what
I
was
thinking
is
that
I
mean,
if
let's
say
we
would
use
the
normal
display.
Seven
input
forms
to
describe
an
author.
You
might
already
be
able
to
start
working
a
little
bit
on
the
submission
in
d
space
7
and
get
some
knowledge
on
that
which
is
kind
of
a
prerequisite
to
to
implement
this
project.
G
B
I
think
that
code
is
very
close,
though,
to
be
honest
from
what
I've
heard
from
from
Andreea,
it
seems
like
it's.
It's
it'll
be
ready
within
the
weeks
or
this
month,
or
not
this
month
next
month,
sometime
within
weeks
or
a
month
here
that
the
submission
and
working
process
should
be
ready
to
go.
But
again,
that's
probably
an
Andreea
questions.
B
A
B
Yeah
I
think
they're
likely
are
some
things
that
can
be
done
in
parallel.
You
may
just
have
to
begin
work
on
D
space
6,
while
these
basics
dwell
dspace
7
is
still
in
progress,
knowing
that
there
are
certain
things
that
change
in
D
space
eV
and
not
sit
not
too
much
significantly,
but
the
submission
stuff
does
change
a
little
bit,
but
but
but
we'll
just
have
to
look
at
that
as
we
make
this
decision
and
get
this
moving
forward.
I.
B
Is
changing
slightly?
It
still
uses
configuration
files
which
are
similar
to
the
current
input
forms
and
similar
to
the
submission
XML
or
the
item
submission
XML,
they're
very
similar
in
nature,
but
they
are
not
identical
because
we
ran
into
challenges
with
using
angular
and
arrest
API
on
top
of
the
existing
D
space
6
configuration
files,
so
we
had
to
update
the
config
files
to
better
align
with
how
angular
and
a
REST
API
can
report
that
information
up
so
so
they're
very
similar.
G
G
You
need
to
know
how
the
new
user
interface
allows
you
to
browse
through
items,
and
that
way
you
can
think
about
how
we
browse
through
authors
as
different
entities
and
how
you
could
browse
through
the
relationships
and
a
search,
how
to
show
it
in
the
search
and
so
I
mean
it
would
be
useful
to
start
also
participating
a
bit
in
the
D
space.
7
development
just
to
be
able
to
have
the
necessary
experience
to
start
on
this
project.
B
Yeah
I
agree
with
that.
Eventually,
it's
gonna
have
to
get
updated,
2d
space
7
and,
if
you're
willing
to
take
to
help
out
on
D
space
7,
it
will
you'll,
learn
it
a
lot
more
rapidly
as
to
how
you
can
design
this
properly.
Otherwise,
you
will
be
limited
to
design
it
on
D
space
6
and
then
having
to
update
to
support
these
space
7
at
a
later
time
and.
G
A
G
However,
they
probably
would
be
good
to
talk
a
little
bit
with
drow
and
see
if
he's
open
to
you
guys
joining
the
some
of
the
after
it's
on
on
D
space.
The
Saturn,
because
I
mean
at
learning
curve
and
attaining
that
knowledge
to
be
able
to
do
something
like
this.
Adding
extras
on
display.
Seven
will
not
be
easy
and
there
will
also
not
be
documentation
available.
G
G
So
that's
a
way
for
all
of
us
to
be
very
aligned
on
everything
and
it
you
know
fitting
in
the
workflow
or
the
the
working
order,
that
for
scientists
working
in
as
well
what
everyone
is
focused
on,
because
Korea's
not
here
now,
because
he
wants
to
focus
probably
on
some
other
work.
He
has
to
urgently
do
might
also
be
an
holiday,
but
so
I
think
that
would
just
help
align
everything
with
it.
I
don't
know
if
Jim
what
you
think
yeah.