►
A
Okay,
we
are
now
recording,
so
this
is
our
first
meeting
of
the
D
space.
Seven
entities
work
in
group,
which
is
a
follow-up
to
an
initial
D
space
entities,
working
group
that
occurred
starting
last
winter,
basically
back
in
November,
December
of
2017
and
kind
of
went
until
spring
spring
time
of
this
year.
A
So
this
is
the
follow-up
group
for
for
actually
taking
the
efforts
of
that
working
group
forward
and
moving
them
towards
D
space,
seven
specifically,
and
to
start
off
this
first
meeting,
though
I
thought
we
could
do
some
quick
introductions,
I
think
most
people
may
I
see
a
lot
of
familiar
names.
Most
people
may
know
one
another
from
other
groups
here
there,
but
this
gives
us
an
opportunity
to
just
make
sure
we
know
who
everyone
is
before
we
get
started
with
this
meeting
so
I'd
like
to
go
around
here
and
do
a
quick
introduction.
A
You
just
give
your
name
the
institution,
you
work
at
anything
else.
You
want
to
say
that
comes
to
mind
with
regards
to
entities,
if
there's
something
major
interest
to
you
here,
but
I'd,
ask
that
we
keep
it
kind
of
brief.
Since
we
got
a
pretty
packed
agenda,
this
first
time
around
and
I
will
call
out
names
because
I
think
in
zoom
here
pretty
much.
A
So
I'll
kick
off:
I'm
Tim
Donnie,
who
of
course
from
Duras
space,
the
D
space
tech
lead
so
I'm
going
to
be
the
acting
chair
of
this
group
trying
to
keep
discussions
moving
forward
and
I'm
also
going
to
be
bringing
things
back
to
the
steering
in
leadership,
although
we
have
several
other
stirring
and
leadership
folks
on
this
call
as
well.
So
I'd
encourage
you
to
keep
me
honest
on
that
and
also
help
bring
back.
This
is
the
discussions
to
our
leadership
and
steering
group
as
they
move
along
so
I'll
hand
things
over.
Let's
see
Mikaela.
B
Of
course,
thinking
and
gonna
medium,
they
work
forward
through
space
responsible
for
the
International
membership
and
partnership
program
after
spaceman
I'm
here
to
support
the
activities
of
movement
to
have
team
and
the
other
leaders.
The
president
is
work
to
bring
the
issues
and
share
the
activities
of
this
work
with
the
governments
of
these
banks.
Thank.
C
E
Hello,
I'm
Andrea
Bellini
from
Italy
I'm,
the
technical
leader
of
the
for
science
with
provider
I'm
also
the
leader
of
the
rest,
api
subgroup
for
this
place,
seven
a
long
time,
Committee
of
the
space
and
one
of
the
creator
of
this
place,
Chris.
That
is,
as
you
probably
know,
one
flavor
of
entities
for
the
space
we
like
to
bring
back
to
experience
of
this
place.
Chris
of
discreet.
F
H
Steven
her
in
University
of
Minnesota
I'm,
the
metadata
strategist
here
and
I,
have
been
advising
and
assisting
with
the
D
space
institutional
repository
and
have
a
long-standing
interest
in
how
we
manage
entities
that
are
not
resources
in
this
kind
of
a
system.
So
I'm
here
as
much
for
curiosity
as
anything
else
but
I
do
have.
A
strong
interest
sounds
great.
Welcome,
Steven
josée,
oh.
I
I
A
Great
Paula,
yeah
I
think
we
hope
it
solves
everybody's
problems
as
well.
Okay,
so
so
let's
go
ahead
and
get
started
here.
Thank
you
for
the
introductions,
everybody
and
welcome
everyone
as
well.
I
am
going
to
go
through
a
couple
of
just
sort
of
introductory
things
today
in
terms
of
talking
about
how
this
working
group
came
about
and
talking
through,
like
the
scope
and
deliverables
of
this
working
group,
so
I'm
kind
of
referring
to
and
I
realized
I
didn't
share
the
well
I
shared
the
agenda
via
slack.
A
But
if
you
have
not
joined
that
channel
I'd
highly
encourage
it,
that's
where
I'll
be
sending
all
meeting
reminders
and
we
may
have
discussions
between
meetings,
things
of
that
nature,
but
going
back
to
the
scope
and
deliverables
of
this
working
group,
I'm
going
to
assume
that
most
of
you
have
probably
already
had
a
chance
to
see
our
working
group
wiki
page,
which
I'll
link
in
here
into
zoom
as
well.
The
wiki
page
has
the
scope
and
deliverable
scope
and
objectives
near
the
top
along
with
the
deliverables.
A
The
as
I'd
mentioned
in
introductory
here.
This
working
group
is
a
follow-up
to
an
initial
dspace
entities.
Working
group,
the
dspace
entities
working
group
was
formed.
I
believe
it
was
in
last
November
I,
don't
remember
the
exact
dates
of
when
it
happened,
but
it
happened
sometime
like
last
November
or
December
and
worked
on
basically
starting
to
plan
out.
A
The
the
goal
here
is
to
really
look
at
how
we
can
achieve
an
idea
of
configurable
entities
in
D
space
7
and
do
it
within
within
the
D
space
7
data
model.
In
a
way
that's
not
going
to
affect
the
D
space
7
timeline,
so
we're
really
trying
to
work
towards
keeping
D
spaced
released
timelines
on
schedule.
A
What
that
means
is
essentially
we're
looking
towards
a
D
space,
7
beta
by
the
end
of
this
year
by
state
December
sometime
in
December,
with
a
final
release
of
D
space
7
early
next
year,
so
our
scope
is
rather
tight.
In
terms
of
that,
we
want
to
try
and
see
what
we
can
achieve
in
D
space.
7.
There's
a
lot
of
opportunity,
though,
to
to
push
certain
features
or
certain
needs
off
to
D
space
eight.
A
If
we
needed
to,
though,
ideally,
if
we
can
work
quickly
and
work
more
collaboratively,
we
will
hope
to
achieve
as
much
as
we
possibly
can
within
that
D
space
7
release
to
at
least
build
the
groundwork
for
this
idea
of
additional
entities
within
D
space.
So
so
that's
kind
of
the
basics
of
where
this
working
group
came
from.
A
A
So,
as
noted
at
open
repositories,
and
also
as
part
of
that
that
steering
group
reports,
the
goal
here
that
that
steering
that
steering
was
really
looking
towards
was
to
try
and
achieve
an
idea
for
configurable
entities
where
entities
are
typed
items
with
defined
relationships.
So,
as
we
all
know,
items
in
D
space
have
metadata
and
0
more
files.
A
The
idea
here
would
be
it
allow
us
to
create
different
types
of
items
that
can
store
different
types
of
entities,
so
you
could
have
a
person
entity,
article
project,
those
can
actually
have
stored
relationships
and
they
even
contributor
interface
views
or
behaviors,
and
this
is
a
bit
of
a
new
idea.
The
user
interface
views
and
behaviors
is
a
little
bit
more
from
a
dspace
seven
realm
in
terms
of
the
flexibility
that
that
has
been
enabled
from
our
new
D
space.
A
So
this
is
all
kind
of
the
the
vision
for
what
we're
trying
to
achieve
and
how
we
want
to
try
and
get
there,
but
this
working
group
is
really
charged
with.
How
do
we
make
this
a
reality?
So
how
can
we
bring
this
down
to
earth
and
sort
of
make
sure
that
we're
moving
in
the
best
direction
for
D
space
as
a
whole,
as
well
as
as
for
D
space
7,
specifically,
so
that's
kind
of
where
we're
coming
from
here,
I'm
gonna,
stop
the
screen
share
it.
A
You
bump
up
my
chrome
view
here
and
collapse,
our
sidebar,
so
that's
kind
of
going
over
the
the
scope
and
objectives
at
a
higher
level
and
in
terms
of
where
we're
trying
to
what
we're
trying
to
achieve
here,
there
is
much
more
information
on
the
various
links
within
this
wiki
page.
If
you
want
to
dig
in
deeper,
if
you
need
a
little
bit
more
background
in
terms
of
the
deliverables,
these
deliverables
are
not
necessarily
set
in
stone
in
terms
of
how
they
are
worded
right
now.
A
But
I
would
like
to
get
sort
of
your
approval
and
QA
around
these
right.
Now,
a
little
bit
of
discussion
around
these
within
this
initial
meeting
to
make
sure
we're
all
on
the
same
page,
to
make
sure
we
know
where
we're
going.
But
these
are
the
the
high-level
goals
that
we
need
to
sort
of
achieve
to
make
this
a
an
achievable
task
for
D
space
7
and
what
based
on
what
steering
has
proposed
for
all
of
this.
But
there's
plenty
of
opportunity
here
for
us
to
define
and
tweak
these.
A
So
the
timelines
here
are
kind
of
loose,
but
these
are
kind
of
timelines
that
I
set
in
place
based
on
the
goal
of
getting
dspace
7
into
beta
by
December,
which
really
means
we
would
have
to
move
quickly
here.
But
I
want
your
feedback
on
whether
you
think
this
is
achievable
not
just
in
this
meeting
but
in
the
upcoming
meetings.
Here.
As
we
start
to
dig
deeper
into
what's
here
so
far,
well,
we
can
build
from
the
starting
point.
Here
is
not
necessarily
from
nothing.
A
This
prototype,
however,
is
not
necessarily
it's
not
been
approved
by
anybody.
I'll
just
put
it
straight
out
that
way,
we
need
that's
part
of
the
the
first
goal
of
this
group.
Is
this
group
has
this
initial
opportunity
to
start
to
look
at
this
prototype
and
assess
it
and
see
whether
we
think
this
is
a
good
direction
for
D
space
and
D
space
7?
Does
this
seem
like
a
model
that
fits
well
with
the
needs
of
D
space
with
what
we
would
like
to
achieve
out
of
entities
with
the
statement
that
steering
put
out
and
how?
A
What
is
this
prototype
aligned
with
those
needs
and
goals?
If
we
like
the
prototype,
this
could
be
a
quick
jumpstart
for
us
and
we
can
start
to
build
from
this
and
enhance
it
or
restructure
it.
However,
we
need
to
and
start
to
move
that
forward
rapidly
in
line
with
D
space
7
timelines,
but
if
we
don't
like
the
prototype
for
some
reason
or
another,
this
is
also
an
opportunity
that
we
can
either
adapt
parts
of
it.
A
If
we
want
to
D
space
and
D
space
7,
we
can
pull
the
pieces
that
we
like
out
and
start
moving
forward
with
those
we
also
have
the
opportunity
to
really
if
we
wanted
to,
we
could
rip
it
all
apart
and
start
from
scratch.
Obviously
that's
harder
to
do
within
our
timelines,
but
it's
another
goal
that
we
can
move
towards.
If
we
really
see
that
that's
the
feedback
out
of
this
group
in
terms
of
that
early
prototyping,
we
can,
we
can
rip
it
all
apart
and
start
from
scratch
as
needed.
A
A
If
we
like
the
prototype,
our
road
map
will
be
based
off
that
prototype
and
what
we
want
to
achieve
and
fix
and
cleanup
in
the
coming
months
to
to
make
this
achievable.
If
we
don't
like
the
prototype
than
this,
then
this
implementation
roadmap
needs
to
work
on
what
we
don't
like
and
how
we
want
to
start
differently
and
how
we
want
to
build
this
in
differently
in
terms
of
trying
to
align
this
with
these
space.
A
That
I
know
are
interested
in
this
work
that
are
not
able
to
attend
today
and
start
to
implement
entities
or
as
much
as
we
can
implement
4d
space
7
per
that
defined
roadmap,
and
the
end
goal
here
is
to
really
create
a
pull
request.
Along
with
documentation
around
that
pull
request
and
submit
that
into
review
the
review
process,
the
normal
review
process,
we
would
get
reviewed
by
ad
space
committers
by
the
existing
D
space,
7
working
group
and
start
that
process
of
getting
this
work
in
2d
space
7.
A
So
the
goal
for
that
is
to
try
and
get
that
done
by
end
of
November.
I
know
that's
really
tight,
but
we
just
want
to
get
it
done
as
soon
as
possible
and
and
keep
the
D
space
seven
working
group
in
the
loop
here
as
well
as
the
committers.
So
we
can
kind
of
move
that
in
2d
space,
seven
as
much
as
we
can
and
then
as
sort
of
a
wrap-up
phase.
There's
the
opportunity
for
this
group
to
also
define
or
draft
up
a
post,
Eastbay,
seven
roadmap.
A
So
what
are
the
things
we
don't
think
can
get
in
2d
space
seven
and
that
we
would
propose
that
steering
and
leadership
and
other
groups
start
to
look
at
after
that
D
space
7
release.
So
once
all
four
of
these
tasks
are
done,
the
goals
of
this
working
group
are
complete
and
I
would
then
ramp
down
this
working
group.
There
would
be
no
more
work
to
be
achieved
by
this
particular
working
group,
and
essentially,
we
would
actually
merge
with
the
D
space.
A
So
that's
a
lot
of
me
talking
I
want
to
hear
questions,
comments,
feedback
from
all
of
you,
I'm
gonna,
stop
sharing
my
screen
here,
real
quick
just
because
that
way
I
can
see.
If
there's
any
been
any
textual
comments.
I
can't
really
see
those
as
easily
well
I'm
screen
sharing.
But
does
anybody
have
any
comments?
Questions
thoughts
on
those
objectives,
the
timelines
which
I
know
are
are
quite
quite
strict
and
and
quite
tight
or
anything
around.
What
we're
trying
to
achieve
in
this
working
group.
A
Looks
to
be
muted,
so,
if
anyone's
trying
to
talk
I'm,
not
hearing
you
I'm
not
seeing
any
questions
Wow.
So
that
was
crystal
clear
to
everyone.
I
know
a
lot
of
you.
Some
of
you
were
in
the
the
entities
working
group
before,
but
I
just
want
to
make
sure
there's
no
disagreement
around
where
we're
starting.
Where
we're
going.
A
Okay,
so
if
you
do
have
any
thoughts
that
come
up
after
this
meeting,
I
would
encourage
you
just
share
them
via
via
slack,
especially
slack
will
be
the
main
channel
for
for
discussions
between
meetings.
For
this
group
we
don't
have
like
a
group
mailing
list
or
anything
so
to
drop
a
node
in
the
entities
working
group
channel
or
something
if
you
do
end
up
having
questions
around
the
goals.
The
guidelines,
what
our
scope
is
for
this
group,
but
with
that
I
guess
we'll
move
forward
to
the
next
topic
on
our
agenda,
then.
A
So
next,
up
on
the
agenda
is
to
start
to
actually
introduce
some
of
the
higher-level
concepts
behind
the
the
early
prototype,
which
is
where
we're
going
to
begin
our
assessment.
So
I
am
going
to
ask
that
we
try
and
keep
this
brief,
because
the
the
goal
here
is
really
to
just
sort
of
give
a
high-level
overview
of
what
the
documentation
has
and
where
you
can
start
to
begin
commenting
on
it
and
reviewing
it.
A
We
will
be
doing
much
deeper
dives
in
future
meetings,
but
I
want
to
give
us
a
chance
to
just
get
that
overarching
overview
and
then
start
to
define
together
how
we
want
to
structure
the
assessment
period
here
and
when
we
would
like
to
have
our
next
meeting.
But
with
that
I'm
going
to
go
ahead
and
give
things
over
to
leave
in.
If
you
want
to
go
ahead,
I
don't
know
if
you
want
to
share
your
screen
or
how
you
want
to
start
this
high-level
overview,
but
I'm
going
to
hand
it
over
to
you.
F
F
What
I'm
gonna
do
this
is
the
same
table
of
contents,
roughly
as
what
is
in
the
documentation,
I
assume
everybody's,
seeing
the
link
to
the
Google
document.
That's
linked
off
of
the
wiki
page
that
Tim
created
with
a
very
detailed
documentation
about
the
the
prototype,
so
that
has
everything
it
has
links
to
the
code.
It
has
links
to
the
demo
site
that
we
put
up
and
has
all
of
the
details
and
explains
everything
in
detail.
F
You
can
build
it
yourself,
so
there
is
their
links
to
the
github
and
everything.
So
you
can
build
dspace.
If
you
can
build
dc-7,
you
could
use
the
darker
and
then
update
the
code,
etc,
etc.
So,
but
it
starts
off
from
the
high
level
specifications
that
were
in
the
original
proposal.
So
this
is
again
a
link
to
the
original
proposal.
I'll
share
the
slides
in
slack
after
the
presentation,
high
level
specifications
were
want
to
avoid
hard
coding.
F
Any
particular
object
model
to
to
start
from
the
D
space
item,
object,
3
to
make
sure
that
those
items
can
be
typed
and
relations
can
be
created,
and
for
that
the
implementation
of
that
data
model
is
configurable.
So
the
implementation
is
ready,
the
prototype
there,
the
documentation
link,
is
here.
The
angular
and
the
rest.
Api
code
are
available
on
our
github.
There
is
a
demo
server
here
where
you
can
click
around
and
see
how
things
work
in
these
based
on
so
configuration
of
the
entity.
F
Types
I'll
just
like
very
quickly
go
over
all
of
the
different
sections
here
of
the
the
documentation
just
to
briefly
introduce
what's
in
the
documents,
so
that
it
makes
a
little
bit
easier
for
you
to
read
through
and
to
to
check
out
all
of
the
details,
configuration
of
the
entity
types
and
the
relations
that's
done
through
an
XML.
This
is
an
example
of
a
relationship
between
a
publication
and
a
person
with
tannerite
label
and
a
cardinality.
F
This
is
the
link
to
that
section:
a
documentation
and
the
XML
file
to
configure
the
data
model
can
be
processed
into
the
database
by
a
script,
and
it
will
read
each
relationship
in
the
configuration
file.
So
this
is
the
initialized
entities
dog
Java
class,
where
you
can
see
how
we
process
that
XML
file
and
actually
create
the
entity
types
and
the
relationships
that
are
in
the
entities.
F
Id
I
know,
I'll,
give
a
few
screenshots
on
a
quick
demo
in
terms
of
slides
so
that
you
have
an
idea
of
what
that
means
more
exactly
then
database
storage,
so
the
type
of
the
ante
is
stored
in
the
item
table.
There
are
two
new
tables
want
to
store.
The
relationship
configuration
so
one
row
per
relationship
type
from
the
XML.
So
what
you
saw
there,
the
relation
between
publication
and
person
will
be
one
row
in
that
table
and
then
the
actual
relations
for
each
of
the
the
publications
and
persons
that
are
in
the
the
system.
F
You
will
have
one
row
that
stores
that
relationship
between
those
two
specific
entities-
the
default
dspace
database
tables-
have
not
been
modified.
An
entity
type
is
just
item
metadata.
That
was
also
quite
important
to
us
because
we
do
realize
that,
and
that
was
also
in
the
original
proposal,
that
there
will
be
a
lot
of
people
who
still
just
want
to
use
G
space
for
what
it
is
today
and
for
its
ease
of
use
and
simplicity,
and
so
for
everyone
who
has
that
use
case.
F
F
Then
the
next
part
is
a
Java
API.
So
that's
also
quite
limited
in
terms
of
changes,
so
the
implementation
only
requires
a
class
to
retrieve
the
relationship
schema
to
identify
so
a
second
class
to
identify
the
entity
type
of
the
current
item,
three
to
identify
which
relations
can
be
created
for
the
current
items
type
and
then
retrieve
all
of
the
current
relations
to
that
item,
and
again
here
is
the
link
to
that
particular
section
about
the
job
API
with
code
examples
and
everything
in
the
document.
F
The
rest
api,
that's.
On
top
of
the
java
api
has
been
extended
to
have
entity
type
relationship,
type
and
a
relationship
so
that
you
can
access
all
of
those
through
the
rest
api
for
all
those
objects.
There
are
services
that
have
been
created
so
that
you
can
easily
create
retrieve,
update
and
delete
entity
types
relationship,
types
and
relationships
and
again
the
link
to
that
section
of
the
documentation,
angular
UI,
so
that
will
there
is
there
three
main
components
here.
One
is
to
display
the
relations
on
the
entity
on
the
item
pages.
F
So,
on
a
particular
entity
item
page,
you
want
to
be
able
to
show
which
relations
it
has
and
that
for
that
we
have
an
entity
types
which
are
component
in
angular
and
we
have
an
entity
type
decorator
custom
item
pages
to
be
created
based
on
the
entity
type.
So
you
want
to
probably
have
different
visual
representation
for
different
entities,
and
in
order
to
do
that,
there's
an
initial
component
to
find
in
angular
that's
called
entity,
page
fields
component.
F
This
can
be
extended
even
further,
but
that's
basically
the
only
section
where
you
know
the
source
code
will
need
to
be
modified
based
on
the
model.
So,
besides
the
this,
you
basically
don't
have
to
do
any
code
customization
to
introduce
different
entities.
Only
if
you
want
to
have
different
displays
for
different
entities,
I'll
show
some
examples
of
those
later
and
then
a
third
component
is
a
virtual
metadata.
That's
another
thing
I
was
important.
Is
that
you
don't
want
to,
of
course,
do
Kait
metadata.
F
So
and
for
that
I'm
sorry,
there
is
a
virtual
metadata
where
you
can
easily
configure
that
you
want
to
show
that
orchid
on
the
metadata
of
that
particular
item,
an
article
in
that
case
and
to
ensure
that
that
metadata
is
available
independent
of
how
you
retrieve
that
metadata.
So
either.
If
you
retrieve
the
metadata
of
that
article
through
oai
or
to
rest
or
any
other
means
that
the
metadata
is
there
without
duplication.
F
I'll
show
an
example
of
that,
as
well
later
on,
then
there's
configuration
of
other
functionality
to
support
different
entities.
What
we've
done
so
far,
but
this
can
be
fleshed
out
further
and
more
implementation
can
be
done.
What
we've
done
so
far
is
to
provide
a
facet
for
different
and
for
the
different
entities
so
that
in
the
search
you
can
you
have
a
search
facet
with
all
the
different
entities
and
you
can
filter
for
a
particular
entity.
Then
you
have
the
option
to
create
separate
discovery
pages
with
a
predefined
filter.
F
Another
thing
that
we've
already
implemented
in
the
prototype
is
batch
import
so
that
you
can
easily
already
load
data
to
work
with
the
prototype,
so
you
have
a
batch
import
for
different
entity
types.
The
entity
type
is
sorry.
This
is
part
of
the
metadata.
So
that's
easy
to
add.
That
was
also
you.
One
of
the
high-level
goals
is
to
make
sure
that
if
you
want
to
add
support
for
entities
to
an
existing
dspace
functionality
that
the
work
should
be
as
minimal
as
possible,
so
entity
type
is
part
of
the
metadata.
F
Then
there
are
two
areas
which
currently
have
not
been
implemented
in
the
prototype.
We
do
have
specifications
an
idea
of
how
we
would
like
to
do
this
in
the
prototype,
but
at
the
moment,
submission
and
workflow
is
not
been
added
to
the
master
branch
of
D
space
7.
So
it's
not
possible
at
this
moment
to
implement
this.
F
Now,
for
the
example
just
checking
the
time
briefly,
so
those
5
minutes
that
was
quick,
so
I
specifically
did
not
use
the
Chris
use
case
as
an
example
just
to
also
highlight
that
you
can
also
build
other
data
models
and
in
the
demo
and
in
the
prototype
code,
you'll
find
two
models
you'll
find
and
this
journal
compound
object
model
as
well
as
some
of
the
Chris
entities.
So
you
can
also
see
how
two
of
those
data
models
can
be
combined
in
one
implementation.
F
F
F
If
we
then
click
on
the
2018
volume,
this
is
a
volume
of
a
journal.
Again,
it's
an
item
page
or
the
thumbnail,
a
title,
the
volume,
the
issue
date
and
the
description
has
native
metadata
and
then
two
relations,
one
that
points
to
the
journal
that
this
volume
is
a
part
of
and
one
to
the
issue
that
exists
in
this
volume.
F
Then,
to
show
the
virtual
metadata,
this
is
the
REST
API
and
point,
and
you
see
here,
the
properties
of
environmental
and
architectural
phenomenology,
vol
29
2018,
and
you
see
your
two
metadata
fields
but
I've
zoomed
in
on
here
in
this
red
box.
This
journal
identifier,
is
SN
and
journal
titled.
So
those
are
two
metadata
fields
that
look
like
they're
part
of
this
volume,
but
they're
actually
only
stored
in
the
journal
and
not
in
the
volume
and
they're
just
being
represented
here
and
has
virtual
metadata.
But
you
can't
tell
the
difference
so.
F
Then
diving
deeper
into
the
hierarchy
here.
You
now
have
the
issue
of
the
volume
of
the
journal,
so
we're
again
here
at
the
top
the
volume
links
it
links
to
the
volume,
so
it
shows
which
volume
that
this
is
part
of,
and
then
here
it
shows
the
articles
in
the
volume.
So
there's
only
one
article
in
this
particular
volume.
Here
again
you
see
the
virtual
metadata
that
you
are
showing
the
date
of
the
article
and
the
author
of
that
article,
that's
being
represented
through
virtual
metadata.
F
Then
we
go
down
to
the
article
page,
which
has
a
date
and
could
have
a
thumbnail.
Has
a
title
doesn't
have
abstract
URI
or
collection,
but
it
could
have
it
I.
Sorry,
it
is
in
the
articles
collection
and
then
here
you
see
the
author,
the
organizational
units
and
a
journal
issue.
The
journal
issue
is,
of
course,
what
we've
already
seen
before,
and
so
this
is
the
the
journal
issue
that
this
article
is
part
of,
but
when
you
see
here
at
the
top
is
the
author
of
this
article,
which
is
also
being
represented
as
an
entity.
F
So
this
is
also
a
separate
entity.
Being
an
author
and
team
that
is,
has
a
relationship
with
an
article,
and
so
you
can
see
that
the
the
job
title
of
this
person,
including
spelling,
error
and
everything-
and
you
can
click
on
that
author
and
then
go
to
that
authors
page
with
an
email
address,
with
an
orchid,
a
birthdate,
a
staff
ID
and
the
relations
that
this
author
has
two
other
objects
in
the
repository.
F
So
this
person
is
related
to
a
number
of
publications,
a
thesis,
some
articles,
a
book
with
again
virtual
metadata
of
the
the
date
of
that
publication
and
all
of
the
co-authors
and
then
projects
which
is
also
an
entity
in
this
model.
So
there
are
projects
here
and
there
are
three
projects
that
this
person
is
related
to
a
virtual
metadata
of
the
status
of
the
projects
or
delayed,
completed
or
ongoing.
F
F
Sorry
in
the
beginning
of
the
slides
here,
demo
server,
you
can
click
around
and
see
it
for
yourself
and
see
how
it
works
and
then,
for
some
of
the
other
functionalities.
I
just
highlighted
the
search.
So
here
you
have
the
entity
type
facet
currently
in
the
prototype.
It
just
displays
like
the
the
raw
value
of
the
the
entity
type,
but
of
course
it
could
have
a
label
where
it
has
a
nicer
representation
than
org
unit,
for
example
in
a
nicer
name.
F
So
here
in
the
search,
you
now
see
everything
you
see
a
test,
article
test
article,
the
louver
I
think-
was
a
project
or
an
org
unit.
After
god,
admirer
was
an
org
unit,
and
so,
if
we
then
click
on
Journal
issue,
then
it
filters
it
down
to
only
the
items
that
are
of
type
Journal
issue:
okay,
I'm
still
within
time,
work
estimates.
F
This
was
a
slide
that
was
included
in
the
original
proposal
of
the
things
that
needed
to
be
done
to
create
this
generic
data
model,
and
you
can
see
that
everything
here
has
been
done,
except
for
the
changes
to
the
submission.
So
that's
still
a
few
days
of
work,
but
it's
not
a
lot
of
work.
If
you
compare
it
to
the
other
areas
and
then
we've
also
estimated
for
two
use
cases
what
the
amount
of
work
would
have
been.
F
So
the
simple
Chris
use
cases
is
not
a
full
Chris
use
case,
of
course,
but
a
simple
Chris
use
case.
Most
of
our
work
has
been
done,
except
for
the
submission
forms
for
the
same
reason
as
above,
and
the
same
applies
for
the
journal
use
case.
There
was
an
optional
automatic
setup
of
configurations
that
we
are
leaving
for
the
end
so
first
app,
we
would
like
to
see
more
discussion
on
the
prototype
before
we
start
implementing
the
optional
components.
A
A
If
there's
not
an
appropriate
place
to
to
track
the
specific
question
you
have
based
on
that
demo,
then
you
can
also
capture
them
inside
the
or
on
the
steering
or
not.
The
steering
group
capture
them
on
our
wiki
page
is
what
I'm
trying
to
say
our
working
group,
wiki,
wiki,
page
and
I'll
copy
them
into
the
the
next
meetings
agenda,
so
that
we'll
have
them
captured
there
as
well.
So
I
just
want
to
give
people
the
opportunity
to
start
to
capture
questions,
write
them
down.
A
Make
sure
that
we
are
are
answering
each
of
these
questions
along
the
way
and
ideally,
within
that
document,
to
start
with
and
as
we
dive
deeper,
we
can
start
creating
wiki
pages
or
whatever.
We
need
to
create
to
to
start
to
get
our
minds
around
this
prototype
and
what
we
like
and
don't
like
about
it
does
that
does
that
make
sense
anybody?
Is
there
any
any
questions
about
how
to
give
feedback
here
or
start
to
give
feedback.
A
Prototype
document
itself,
which
is
linked
off
of
the
agenda,
also
link
it
into
the
zoom
chat
here.
So
there's
a
wiki
doc
or
not
a
wiki
doc,
google
doc
I
can't
talk
today
it
seems
there's
a
Google
Doc
that
Lieven
kindly
wrote
here
that
goes
into
a
ton
more
detail
around
what
he
just
presented
so
I
would
propose
that
that
has
commenting
turned
on
on
it.
There's
already
been
comments
added
there.
A
Some
of
those
questions
together
make
sure
we
get
clarity
around
any
concerns
or
or
questions
about
how
this
all
kind
of
works
or
how
its
structured,
because
that
could
be
a
good
next
step
here
for
how
we
can
start
to
capture
that
feedback
and
make
sure
everybody's
concerns
are
answered.
Does
that
make
sense
mark
and
everybody
else,
I
guess?
Yes,.
A
A
So
I
would
like
to
hear
from
you
if
you
have
thoughts
on
the
best
way
to
assess
this
prototype.
We
are
a
semi
big
group,
I,
see
that
where,
let's
see
we're
currently
twelve
people
in
this
in
the
zoom
chat
or
zoom
meeting,
so
obviously
we
could
just
dive
in
all
together
in
the
next
meeting
and
start
going
through
the
documents
answering
those
questions
digging
deeper
in
areas
that
we
feel
need
to
be
dug
deeper
into.
A
We
can
do
that
sort
of
structure
for
our
next
meeting,
there's
also
the
opportunity
where,
if
there's,
if
not,
everybody
feels
you're
going
to
have
your
the
ability
to
analyze
this
in
more
detail
within
a
week
or
two
by
our
next
meeting,
we
could
start
to
split
off
into
like
a
little
subgroup
and
have
a
subgroup
dig
deeper
back
concerns
questions
to
the
bigger
group
and
sort
of
present
them
back
to
this
group.
That's
another
way
that
we
could
analyze
this
prototype
I'm
kind
of
curious.
A
What
folks
think
around
how
you
would
like
to
be
involved
in
this
analysis?
Would
you
like
to
see
this
discussed
in
every
single
meeting
for
the
coming
weeks
here?
Would
you
like
to
to
have
a
separate,
really
really
deep
dive
getting
into
the
code
installing
it
meeting
for
just
a
subset
that
can
bring
that
feedback
back?
What
do
you
think
would
work
Tim.
F
A
That
seems
reasonable
to
me
to
do
a
deep
dive,
because
that
should
allow
us
the
opportunity
to
give
feedback
into
this
as
to
whether
it
seems
to
align
well
with
what
people's
vision
is
as
well
as
just
you
know
whether
or
not
they
see
a
different
way
of
doing
things
here
in
certain
areas
of
the
prototype.
What
have
others
think
here?
I.
F
Everything
I've
showed
today
is
already
implanted.
There
is
code,
there
is
a
camel
service,
all
that
has
been
implemented
and
it's
has
been
implemented
against
the
dspace
seven-branched,
a
submission,
the
workflow
or
the
two
main
gaps
at
the
moment,
but
to
revise
that
implementation.
Yes,
and
if
you
split
it
up
in
the
subsections,
we
would
actually
need
six
meetings.
A
A
Data
model,
configuration
and
possibly
even
Java
API
could
all
be
one
meeting,
and
then
you
could
go
into
a
meeting
on
the
REST
API
and
possibly
the
angular's
in
a
separate
meeting.
I
don't
know,
but
but
it
might
be
doable
in
three
to
four
meetings
if
we
kind
of
match
these
up
with
things
that
seem
logically
reasonable
and
I
think
after
the
first
few
meetings,
we'll
start
to
get
a
good
sense
among
our
group,
whether
or
not
we
feel
there's
major
concerns
with
the
approach
or
whether
we
feel
it's
it's
worth
trying
to.
A
C
First,
thank
you,
leaving
for
all
the
work
at
now
and
you
put
into
this
I
think
document.
Documentation
is
really
helpful,
at
least
for
me
to
understand
the
ideas
of
the
implementations.
I
think
it's
a
good
start.
What
I
have,
on
my
mind,
is
not
to
discuss
how
we
use
two
entities,
but
we
need
to
to
look
into
how
it's
implemented,
but
also
some
use
case
we
will
have
to
discuss
those
identifiers
was
already
made.
That
seems
it
simple,
so
I
think.
C
If
you
try
to
go
through
the
packages
that
are
in
the
document,
we
always
will
hit
points.
We
will
have
to
also
look
at
your
other
other
parts
of
this,
so
it's
our
connections
between
those.
Maybe
it
would
be
possible
if
I
don't
know
if
it
would
work,
but
but
I
could
imagine
that
we
could
start
having
everybody
looking
into
the
document
adding
comments
there
and
then
maybe
we
just
shall
look
if
we
can
can
can
prioritize.
C
The
comments
can
put
together
coming
from
from
the
comments,
so
working
close
on
the
documents
close
on
the
on
the
comments
that
are
coming
up,
because
then
we
always
see
which,
on
which
point
we
don't
have
any
comments
which,
which
everybody
agrees
to,
in
which
point
we
need
something.
I
think
that
would
could
be
much
faster
than
really
going
into
step
by
step,
always
hitting
the
point
where
they
connect
to
each
other
and
so
on.
A
Yeah
I
think
that
makes
that's
good
feedback.
Pascal
and
I
would
want
that's.
Why
I'm
encouraging
folks
to
add
comments
immediately
is
because
I
think
that
will
immediately
point
out
the
areas
that
need
more
discussion,
and
so
it
might
know
which
which
areas
we
need
to
do,
that
deep
dive
for
an
entire
meeting
and
which
areas
we
have
general
and
folks
are
okay
with,
and
we
may
not
need
to
die
of
as
deeply
for
an
entire
meeting,
but
could
just
touch
on
it
briefly
and
move
along.
E
Thank
you
for
today,
more
I'm
very
glad
to
see
some
of
concept
of
displaced
place
received
in
the
proposal
like
the
mr.
metadata
to
different
search
for
different
entities
featured
that
I
didn't
recognize
I'm
a
bit
eat
I
need
to
check
what
is
happening
on
the
comment
that
I
made
to
the
general
approach
in
naval
because
I'm
going
to
add
this
comment
again
to
the
documentation,
but
essentially
that
we
need
to
have
a
very
deep
dive
into
data
model
structure,
because
I
really
now
our
comment
of
I
will.
E
We
have
raised
some
topic
for
discussion
about,
according
of
the
entity,
relation
into
database
and
some
advantage
and
disadvantage
to
do
that
and
something
that
that
need
to
be
addressed.
What
I
want
to
see
is
say
is
very
similar
to
what
Pascal
say.
There
are
a
lot
of
topic
that
area
related
to
order.
So
instead
we
have,
we
agree
about
two
data
model.
I
think
that
we
can
go
more
fastly
about
how
to
store
the
data
into
the
base
of
the
Geo,
API
and
so
on.
E
A
Okay,
yeah
I,
think
that
seems
reasonable
and
I'd
encourage
you
bring
your
comments
forward.
Andreea.
We
didn't
keep
comments
from
old
documents
into
this
new
document.
This
was
sort
of
a
fresh
write
up,
because
this
is
a
fresh
working
group
as
well,
so
bring
forward
comments
on
the
data
model,
and
that
could
be
the
place
that
we
can
start
with.
A
E
A
E
So
or
won't
you
ask
if
look
into
the
comments
in
my
comment,
if
you
feel
that
it
will
be
useful
to
have
a
very
high-level
presentation
about
this
point,
I
will
be
happy
to
prepare
some
presentation,
because
in
the
past
we
go
very
deep
about
technical
detail
and
some
aspect
making
think
more
complex
or
looking
more
complex
than
needed
instead
and
just
give
a
very
high
level
which
slide
that
make
think
more
easy
to
understand
and
more
easy
to
accept
because
you
know
too
difficult
er
into
the
day.
So
if
I
did
this
so.
E
K
E
Trying
to
keep
things
simple:
if
you
look
to
this
document,
there
is
a
part
about
the
recommendation.
What
at
the
organizational
level
how
to
manage
the
process,
then
at
the
technical
level
and
I
really
feel
that
these
are
still
relevant
for
the
prototype
and
completely
apply
to
the
present
time.
So
I
will
copy.
This
comment
on
the
relevant
section
of
the
prototype
documentation
as
well.
I
would.
A
Ask
that
we
update
this
for
the
prototype,
because
a
lot
of
this
language
is
still
around
dspace,
Chris
and
and
trying
to
implement
things
that
Alliant,
that
are,
that
that
have
the
existing
D
space
Chris
code,
so
I
think
we
should
revisit
your
comments.
Andrea
I
think
they're
important
comments,
but
I
think
we
need
to
have
a
higher
level
view
of
this,
because
it's
a
lot
of
text
and
it
would
be
nice
if
you
could
actually
bring
these
into
slides
or
some
sort
of
diagram
or
something
that
can
help
us
understand
the
salient
points.
C
A
E
A
And
so
we
can
dive
in
or
we're
at
time
here,
but
we'll,
let's
dive
in
door
on
our
next
meeting.
We
can
talk
about
this
if
you
can
have
that
sort
of
high
level
proposal
Andrea
what
you're
talking
about
here.
So
we
can
dive
into
this
and
discuss
it
and
see
what
other
others
think
around
the
data
model
proposals
and
we
can
move
from
there,
okay,
and
so,
since
we
are
at
time,
I
do
want
to
quickly
see
when
we
can
have
our
next
meeting.
Sorry.
A
K
A
Discussion,
thank
you.
Okay.
So
next
meeting
since
most,
the
folks
that
are
involved
with
this
are
in
the
United,
States
and
Europe
for
the
most
part,
I
would
propose
that
we
try
and
keep
meetings
around
this
time
of
day.
It
could
be
an
hour
earlier
or
an
hour
later
from
for
my
schedule
at
least
much
different
than
that
would
be
difficult
for
me
to
chair
the
meeting,
but
I
would
like
to
know
what
day
of
the
week
folks
could
meet.
I
would
like
to
make
this
a
weekly
meeting
if
possible.
A
I
realized,
though,
that
next
week
is
there's
a
German
user
group
meeting
so
I
know
Pascal
would
be
difficult
for
you
and
possibly
for
for
science
who
might
be
there
I'm,
not
sure
Pat
Myers
going
to
be
there
as
well,
but
I
would
like
to
see.
If
we
can
can
we
meet
next
week?
Do
we
need
to
do
a
two-week
a
meeting
in
two
weeks
or
should
I
just
do.
C
C
A
Yes,
that's
no
problem,
I
know,
there's
it's
just
it's
just
the
time
of
year.
No,
no
problem
Pascal.
How
about
this
I
will
send
out
a
doodle
poll
to
everybody
here
proposing
times
for
the
week
of
September,
17th
I'm
gonna,
try
and
do
it
earlier
in
the
week
just
because
that
tends
to
work
better
for
me,
so
maybe
Monday
Tuesday,
possibly
Wednesday,
but
I'll,
send
out
a
doodle
poll
to
everybody
here
and
let's
try
and
get
something
on
the
schedule
as
soon
as
possible.
F
F
F
A
Yeah
I
could
do
that.
I,
don't
want
to
keep
you
all
on
here.
I'll
send
out
a
massive
doodle
poll
and
we'll
we'll
try
to
at
least
get
the
next
two
meetings
scheduled.
I,
don't
know
if
we'll
be
able
to
get
the
next
four,
but
let's
try
and
get
the
next
two
on
the
calendar
and
and
we'll
see
how
this
works
out.
So.
G
Just
want
to
to
add
that
I'll
also
be
a
D
D
space
user
group
meeting
in
Germany
and
Andre
also
and
I'm
Michaela
I
think
we'll
also
be
there
so
next
week
there
will
be
four
of
us
missing
and
yeah
yeah.
The
other
suggestion
is
that
we
could,
if
we
could
use
the
same
day
as
the
developers
meeting,
maybe
one
hour
before
the
developers
meeting,
then
it
would
be
better
not
to
occupy
all
the
afternoons
for
these
base
meetings.
Yeah,
okay,.