►
From YouTube: Magento MSI Open Grooming. December 6, 2018
Description
Discussion on Distance-Based Algorithm
and how is better to incorporate one into MSI
what the issues we have with Google Maps API
and what should be done to increase geocoding accuracy for Source Selection.
A
Let
me
see
the
recording,
so
today
gonna
be
first
meeting
her
grooming
meeting,
where
we
will
discuss
the
scope
of
milestone,
33
and
the
pink
and
the
all
possible
features
which
get
to
the
scope
of
the
milestone
3.
We
already
had
several
features
which
been
already
started
and
we
even
have
several
requests
devoted
to
some
of
the
stories
in
the
scope
of
this
backlog,
and
probably
probably
we
can
start
discussion
from
from
the
features
already
started
and
like
currently
in
any
scope
of
milestone.
A
3,
we
have
like
bunch
of
bang
Banga
stories,
2
story
devoted
to
the
source
in
stock
configuration
api.
This
these
stories
were
started
in
a
previous
milestone
by
by
Sergey
in
and
Ricardo,
and
currently
this
pull
request
was
a
bit
abandoned.
I
know
the
last
time
Fergie
was
working
on
it.
He
he
made
all
the
tests
green,
but
but
we
were
really
at
the
time
of
release
testing
and
we
were
at
the
time
of
the
regression
and
the
stabilizing
the
mainline
branch.
A
That's
why
Sergey
switched
to
the
bug,
fixing
and-
and
we
need
to
get
back
to
these
stories
and
and
to
to
recap
what
the
question
we
have
there,
because
there
were
several
questions
regarding
the
UI
and
the
usability
and
probably
the
first.
We
need
to
do
in
this
cup
of
the
stories
to
clarify
what,
whether
first
of
all,
whether
we
need
to
involve
some
USB
share
least
or
designers,
to
help
us
or
we
are-
we
are
good
with
the
decision
we
already
made
in
this
proposal
stories.
A
The
next
story
in
in
the
scope
of
backlog
is
for
is
to
provide
full
support
for
multi
source
of
multi-source
into
b2b
addition
and
currently
large
working
on
the
on
several
issues
from
this
track,
and
all
that
issues
were
found
by
Vadim
so
by
another
guy
from
the
tech
division
and
currently
Lars
took
the
ownership
over
this
track.
Another
story
is
to
provide
full
support
of
multi-sourcing
for
elastic
search
adapter.
A
Currently,
as
you
know,
we
provide
the
compatibility
with
elastic
search
just
on
the
default
just
on
the
default
stock,
and
there
are
some
gaps
for
custom
stocks,
especially
regarding
the
search
functionality.
The
search,
layered,
navigation
and
so
on.
So
this
is
an
independent
track
and
probably
said
it,
and
probably
it
should
be
grown
separately
and
some
some
some
tasks
should
be
created
in
this
couple
district
to
provide
all
possible
search,
related
functionality
based
on
the
elastic
search
adapter.
A
The
next
story,
currently
in
the
scope
of
milestone
3
backlog,
is
to
provide
the
multi-sourcing
support
for
bundled
product.
This
story
is
especially
important
for
us
because,
because
currently,
the
bundled
product
is
the
last
product
time
type,
which
is
not
supported
yet
for
multi
sourcing,
and
actually
this
means
that
bundle
product.
A
We
provide
the
bundle
product
support
just
for
default
stock,
so
so
the
mod
which
we
call
single
stock
mod
and
for
all
the
merchants
who
have
bundled
products,
they
can
keep
the
bundle
products
on
the
default
source
in
default
stock
or
to
provide
old
way
of
handling
bundle.
Products,
for
example,
as
streaks
guys
from
the
Strix
agency,
implemented
that
in
the
scope
of
their
their
release,
which
they
did
at
the
beginning
of
November.
A
A
We
have
an
MSI
and,
last
but
not
least,
the
store
pick
up
support
for
multi-sourcing
because,
after
especially
after
the
release
of
emissary,
we
have
quite
a
lot
of
requests
regarding
regarding
the
store,
pick
up,
support
and
based
on
based
on
the
current
architecture
of
MSI.
This
support
is
pretty
pretty
easily
to
a
completion.
So
we
just
need
to
discuss
whether
I
can
I
can
describe,
for
example,
how
the
store
pickup
can
be
implemented.
A
Based
based
on
existing
MSI
architecture-
and
we
will
just
discuss
whether
whether
the
priority
of
this
story
is
high
enough
to
be
taken
for
milestone
3
in
any
case,
I
know
that
guy
from
Vimal
agency
already
started
to
work
on
a
project
where
they
want
to
introduce
the
store
pickup,
and
they
made
some
consultation
with
me
house
in
store.
Pickup
functionality
could
be
properly
implemented,
based
on
the
based
on
the
way.
How
ms
is
implemented
right
now
so
currently-
and
we
don't
have-
we
don't
have
dedicated
item
here,
but
I
will
I
will
edit.
A
So
this
is
like
a
general
general
improvement
on
on
the
performance
side,
because,
as
I
already
mentioned,
especially
in
especially
in
a
single
stock
mode,
we
have
the
slide
performance
degradation
because
of
the
because
of
the
fall
back
to
to
our
legacy
indexation
process.
So
probably
it
should
be
introduced
separately.
Currently
we
have
a
dedicated
ticket
and
week.
Our
new
contributor
is
working
on
this
potential
improvement
investigation.
So
so
this
is
another
bullet
point
to
the
to
the
milestone
through
backlog.
A
So
today,
I
I
propose
to
discuss
in
details
the
distance
based
everything,
because
we
already
have
this
functionality
implemented,
and
we
have
our
main
contributor
who
created
these
functionalities,
and
so
I
expect
that
this
conversation
gonna
be
fruitful
and
we
can
finalize
all
the
acceptance
criteria
and
whether
anything
else
should
be.
It
should
be
introducing
the
scope
of
the
story.
A
Also,
let
me
let
me
introduce
some
some
feedback
based
on
the
code
review.
I
I
did
for
this
pull
request,
because
initially,
initially
we
tested
the
pull
request
and
from
the
beginning,
Laurie
and
Swala
found
found
the
border
issue
which
did
not
did
not
allow
them
to
to
test
request
out,
because
from
the
beginning
they
got
the
error
message
not
allowing
them
to
just
get
the
geo
coordinates
for
like
latitude
and
longitude.
A
B
A
It's
still
under
investigation.
The
main
are
the
main
points
which
I
noticed
during
the
code
review.
I
would
not.
I
would
not
mention
all
of
them,
because
the
pull
request
is
pretty
big
one.
So
it's
almost
three
thousand
lines
of
code,
but
there
is
a
pretty
important
scene
which
need
to
be
mention
that
we
apply
the
same
policy
regarding
the
regarding
zip
code
support
as
for
Magento.
A
So
since
since
2.3
that
Oh,
when
MSI
was
firstly
publicly
released
in
the
general
availability
as
a
general
availability
release,
we
should
apply
the
backward
compatibility
policy
for
all
the
codes,
or
least
in
the
scope
of
the
MSI.
So
currently
we
are
not
able
to
make
refactoring
drop
in
drop
in
like
public
methods
of
the
class
or
removing
the
constructor
dependencies
or
introducing
the
mandatory
input
parameters
for
for
object
constructors.
So
we
should
keep
the
same
policy
as
magenta
as
magenta
follows.
A
So
all
these
changes
should
be
introduced
in
a
backward
compatible
way
because,
like
we
used
to
to
make
all
the
changes
for
MSI,
not
keeping
backward
compatibility
policy-
and
all
of
that
was
true
before
before
the
MSI
release,
taking
into
account
the
general
availability
release
is
launched,
we
we
have
to
keep
these
policies,
so
this
is
pretty
pretty
important
stuff
and
we
will.
We
will
attract
attention
to
all
the
blue
request
for
for
MSI
code
and
also
to
request
which
apply
the
changes
to
already
released
code
should
should
follow
the
backward
compatibility
policy.
A
And
by
the
way
that
was
mentioned
urine
during
the
demonstration
on
a
weekly
demo
regarding
the
licensing
and
whether
we
are
able
freely
able
to
freely
use
this
database
database
of
the
zip
code,
zip
code
provided
by
this
external
service
and
I,
looked
through
the
license
agreement
of
this
creativecommons.org,
and
actually
they
allow
to
use
the
database
of
the
zip
codes.
But
we
have
to
mention
the
URL
to
the
service.
A
C
A
A
D
Sorry
I
had
an
issue
with
my
microphone,
so
I
good
thing,
I
fixed
it
yeah.
My
question
was
similar:
it's
run
where
this
has
to
show
up.
Is
it
sufficient
to
put
it
in
the
source
code
or
do
we
have
to
put
it
in
the
UI
or
I?
Guess
just
one
two
CLI
command
runs.
Where
do
they
have
any
more
detail
about
where
it
needs
to
show
up.
A
E
E
E
C
D
A
More
or
actually
I'm
just
looking
at
this
at
this
point
that
they
want
that.
It
should
be
indicated
if
you
modify
the
material
and
actually
we
can't
say
whether
the
data
was
modified
or
not
because
potentially
like
it
could
be
customized
by
the
search
party
developers
and,
for
example,
additional
data
could
be
installed
as
well,
or
this
data
could
be
refined
somehow,
and
we
can
just
say
whether
it
was
used
as
this
or.
A
D
A
A
A
So
actually,
this
point
is
just
on
the
middle
of
the
country,
and
you
can
see
from
the
response
that
Google
was
not
able
to
specify
that
the
city
and
region
and
the
resolving
would
be
much
more
accurate.
If
you
will
just
specify
zip
here
in
this
particular
case,
the
make
as
a
Google
mechanism
will
determine
that
this
data,
so
88
triple
0,
is
if
the
postcode,
but
not,
for
example,
like
home
number
or
street
address
or
whatever,
and
in
this
particular
case
you
see
that
this
city
and
the
region
with
determined.
A
C
A
A
A
A
A
Just
country
code,
so
we
okay,
but
Google,
is
not
smart
enough
to
understand
the
magenta
country
codes
and
that's
why,
for
example,
if
you
provide
this
coordinate
with
the
with
the
zip
code
for
Milan
city
and
also
specifies
the
country
code
for
Italy,
like
I-80,
we
are
still
getting
the
address
in
Virginia.
And
but
if
you
specify
the
Italy
here
so.
C
A
So
at
least
it
would
be
much
easier
if
you
just
the
country
values
of
the
full
name
of
the
country,
so
like
even
I,
I
just
tested
it
today
that
even
specifies
a
zip
code
and
the
full
country
name
gives
us
much
better
results
than
the
country
code
and
the
the
value
of
Z
without
specifying
zip
explicitly
and
another
thing.
I
was
just
thinking
matter,
whether
it
makes
sense
or
not
just
to
because
currently
like
I
was
tested.
All
this
chin.
A
All
these
changes
just
checking
the
geo
coordinates
given
by
the
given
by
the
result
of
request
to
the
Google
Maps
API,
but
maybe
it
makes
sense
to
introduce
small
google
map
here
and
just
show
that
the
marker,
because
it
would
be
the
most
visible
wave
for
merchants
to
see
whether
the
je
coding
made
correctly
or
not
and
taking
into
account
that
this
is
just
for
internal
for
admin
part.
So
it
would
not
take
too
much
Jo
request.
So
merchants
no
need
to
pay
for
this
request.
Okay,.
C
And
because
what
do
you
think
about
feeling?
Also
state
and
provinces,
street
name
and
city
you're
missing
them?
Because
in
this
way
you
can
have
an
immediate
feedback,
because
even
with
google
map
we're
not
okay
yeah,
if
you're
using
good
map.
Of
course,
you
have
a
Google
API,
but
maybe
you
have
an
API
that
is
not
valid
for
map
and
buried
for
geocoding
and
so
on
and
can
be
messy
sometime
I.
A
C
C
A
D
A
C
A
Don't
think
we
need
to
introduce
it
to
magenta
in
general
and
we
did
not
want
entry,
because
we
already
had
several
conversation
regarding
whether
Google
Maps
should
be
introduced
to
magenta
in
general,
but
it
always
was
postponed
because,
especially
when
Google
Maps
changed
the
licensing,
because,
okay,
how
from
the
beginning,
it
was
possible
to
use
Google
Maps
for
free
even
for
commercial
purposes,
but
probably
two
or
three
years
ago.
They
reconsider
their
license
agreement.
A
A
Just
I
just
why
I
raised
this
question
regarding
Maps,
because
I've
seen
that
there
is
a
point
to
mistake
and
incorrect
not
actually
incorrect,
recording
but
the
issue
that
Google
can't
recognize
correctly.
What
we
would
address
data
we
provided.
So
we
can
refine
it
specifying
the
zip
and
providing
the
correct
country
name,
which
would
be
recognizable
by
Google,
but
still
it
could
be,
could
be
an
issue
and
if
we
will
just
provide
the
marker,
it.
C
A
C
A
C
D
Mean
it
will
resolve
this
to
something
it
may
be
completely
wrong
like
in
the
middle
of
the
ocean
I'm
either
we
have,
we
can
allow
them
to
override
it
by
entering
coordinates,
which
they're
unlikely
to
know,
because
it's
it's
a
shipping
address
of
a
customer.
It's
not
an
address
they're
familiar
with
or
we
allow
them
to.
You
know
again
drag-and-drop
a
point
which
you
can
do
with
Google
integration
as
well,
but
how
would
they
know
the
correct
place
to
get
it?
It's
also
not
an
address
they're
familiar
with
yeah.
It
makes
sense
actually
yeah.
C
D
The
way
it
works
already
is
that
these
are
all
proposed
to
shipments
so
that
they
have
the
ability
to
override
that
that's
already
built
in
yeah
I.
Think
if
we
get
a
failure
or
some
sort
of
error
in
geocoding
from
Google,
they
would
surface
that
yeah.
It
makes
sense.
Okay,
but
it
looks
like
I,
don't
know
whether
Google
will
return
errors
there
like
in
the
examples
you
were
walking
through
there
Igor.
It
seems
like
it's
trying
to
fail
in
a
friendly
manner,
and
do
it
do
its
best
guests,
depending
on
the
information
you
give.
It.
D
C
A
A
D
D
A
F
A
F
F
C
Another
problem
in
the
others
parsing
is
that
I'm
not
respecting
actually
the
Google
order,
I'm
not
seeing
now,
because
first
I'm
sending
the
street
address
and
Google
wants
the
postcode.
Usually
so
so
maybe
it's
just
a
matter
of
order.
Looking
back
I
mean
to
the
previous
problem,
yeah
and
I'm
missing,
even
some
some
punctuation.
D
A
C
F
A
So
yeah,
by
the
way,
is
it
because
there
is
educated
component
filtering
for
the
postal
code
and
we
can
specify
that
postal
code
is
independent
component
filter
in
at
the
same
as
country.
So
this
problem,
you
should
work.
So
as
the
only
question
we
have
whether
whether
we
need
to
use
Google,
Maps
and
I
showed
it
whether
we
need
to
play
the
map
to
improve
the
visibility,
is
ability
and
etc,
or
we
were
still
procedurally
the
same.
You
I
already
have.
A
D
It
depends:
are
you
proposing
that
we
add
it
would
really
be?
It
could
be
two
maps.
One
of
this
will
actually
no,
we
wouldn't
show
this
or
so
so,
just
a
map
of
the
delivery
address
we
could
show
that,
but
if,
if
it's
just
informational,
it's
unclear
what
the
merchant
admins
going
to
do
at
that
point.
So
if
they
can't
update
the
address,
it's.
D
D
A
D
C
E
D
D
Then
Google
verified
address
essentially
yeah,
something
like
that.
So
again,
that's
just
informational,
but
if
it
looks
completely
wrong,
they
can
you
know:
do
some
lookup
themselves
go
back
in
and
edit
the
shipping
address
if
they
want
switch
an
algorithm?
So
there
are
some
steps
they
could
take.
Okay,.
A
So
the
decision
we
made
regarding
the
stories
that
we
are
not
introduced
in
any
any
GI
modification,
except
that
will
provide
that
some
text
text
text
notification
regarding
how
Google
recognized
the
address
at
the
time
of
the
source
selection
algorithm
just
to
make
sure
that
you
will
recognize
the
shipping
address
correctly
and
will
just
improve
the
Google
geocoding
request.
We
are
the
more
refined
and
the
precise
like
address
formatting,
specifying
the
postal
code
and
and
the
country
code
there
yeah.
D
A
A
And
looks
like
we,
we
finalized,
it
leaves
the
product
requirement
for
the
distance
based
algorithm
and
we
can
proceed
to
other
stories.
Yeah
Thank,
You
Ricardo
for
your
purses,
rattle
I,
believe
we
got
pretty
fruitful
discussion
and
finalize
the
set
of
the
excellence
criteria
and
so
mark.
You
will
contact
the
you
again
or
guardian
yogin
bono
regarding
the
UI
yeah,
okay,
cool
so
looks
like
that's
all
for
today.
Thank
you
guys
for
your
time
and
Mark.
You
will
be
able
on
Tuesday
if
I'll
schedule
the
meeting
for
the
same
time
as
today.