►
Description
Image licensing and more
A
B
B
Can
you
see
my
screen
yeah,
okay,
so
basically
I
added
new
subsection
to
Vicki,
so
we
had
phase
1
section
with
list
of
stories,
and
here
is
two
that
basically
outlines
the
kind
of
goal
of
that
phase
to
allow
user
to
license
the
image
and
saved
license
image
file
into
magenta
media
gallery.
And
this
is
the
list
of
stories
associated
with
this
face.
C
A
B
So,
let's,
let's
see
if
we
can
achieve
that,
so
the
first
story
in
this
face
basically
sign-in.
I
isolated
that
into
a
separate
can
abuse
case
because
it
can
be
triggered
from
two
different
places
like
a
separate
signing
when
just
user
decides
to
authorize
themselves
and
Adobe
stock
without
outside
the
licensing
process,
and
this
the
same
process
will
happen
when
user
tries
to
license
the
image.
But
just
let's
discuss
the
first
case
when
user
is
outside
the
licensing
process,
just
entered
Adobe
stock
and
once
to
signing.
B
So
the
main
business
objective
is
to
allow
user
to
authorize
themselves
in
Adobe
stock
and
have
that
authentification
lasted
for
a
while,
so
whatever
their
lifetime
of
the
Adobe
stock
token
is,
that
should
be
the
authentification
lifetime,
in
mention
the
admin
for
that
particular
user.
So,
let's
say:
if
I
am
an
admin
user
load
in
information
panel
and
goes
through
that
use
case,
I
will
have
I
will
be
authorized
in
Adobe
stock,
on
only
for
my
admin
account
for
a
certain
period
of
time
that
I
love
the
stock
supports.
A
B
Yeah,
so,
basically,
somewhere
on
Adobe
stock
greed.
This
is
for
Eugene
to
define
where
the
sling
should
be.
There
should
be
a
limo
that
user
can
activate
and
the
login
process
starts
and
when
the
login
process
starts,
adobe,
login,
pop-up
window
appears
and
all
of
the
supported
login
options
are
there
and
user
falls
the
steps
that
prompted
by
this
well,
it's
pop-up
and
basically
what
we
are
concerned
about
the
end
state
of
this
authorization
process
that
adobe
legend
returns.
B
So
if
the
login
was
successful
and
user
is
authorized,
stocks
societ
the
pop-up
just
shuts
down
automatically
and
instead
of
signing
link
user
sees
the
username
he
authorized
with.
But
if
the
authorization
wasn't
successful,
their
login
pop-up
still
displays
and
still
open
and
stays
open
until
user
decides
to
click
it
and
on
Adobe
stock
side
and
admin
panel.
Nothing
changes
so,
as
I
said
this,
if
their
authorization
was
successful,
it
should
last
for
the
time
that
is
supported
by
the
API,
and
this
authorization
is
valid
only
for
the
current
admin
user.
C
C
B
Yeah,
so
there
is
a
separate
use
case,
user
license
and
image
and
sorry
user
story
and
within
this
user
story,
I
just
reference
the
authorization
steps
in
another
story.
So
basically,
my
suggestion
is
to
start
with
the
login
process
separately
outside
of
the
licensing
process
and
then
reuse.
The
same
process
in
licensing
basically
build
on
top
of
it.
In.
A
A
D
A
D
D
That
would
be
the
story
21
or
or
it
could
be
broken
out
into
its
own
thing
and
then
so
basically
I
would
say.
First
we
need
to
sign
in
the
user
somehow
through
some
mechanism
and
then
once
the
users
signed
in
we
get
a
token
and
it
can
be
used
for
licensing
an
image.
It
can
also
be
used
to
show
a
little
message
to
them
with
their
name
to
show
them
that
they
are
signed
in,
but
I
don't
know-
maybe
maybe
this
makes
sense
already,
but
also
I'm
kind
of
thinking
ahead
to
like.
D
D
B
Because
this
is
something
that
would
make
sense
for
them
and
then
we
can
broke.
We
can
break
it
down
more
granular,
as
you
suggested,
but
just
like
the
user
story
need
to
have
the
implication
from
user
perspective,
so
there
should
be
some
UI
UI
for
use.
You
know,
so
that's
why
that
if
I
try
to
take
out
the
log
in
and
have
some
UI,
that
is
meaningful
minimum
UI.
That
is
meaningful
for
that
use
case.
Sure.
D
And-
and
the
other
thing
is,
is
that
it's
it's
a
big,
it's
kind
of
a
big
request,
I
think
I.
Think
it's
I
think
we
should
keep
the
UI
separate
from
the
process
of
adding
a
UI
that
says,
log
in
sign
in
sign
out
shows
the
name
shows
the
status
and
all
that
kind
of
stuff.
I
think
that
should
be
a
separate
story
from
the
work
needed
to
do
the
authentication
it's
kind
of
to
work
to
do.
The
authentication
is
more
back-end,
whereas
I'm
thinking
that
the
actual
UI
that
says
sign
in
is.
B
I,
don't
know
if
that
matches
what
you
are
talking
about,
but
from
my
perspective,
whatever
work
would
do
in
the
scope
of
the
Adobe
login
implementation.
It
needs
to
be
separated
from
the
stock
implementation
itself,
so
basically
it
should
be
able
for
any
developer
to
reuse.
This
implementation
in
any
surprising
module.
B
C
Oh
they'll
be
expecting
that
Adobe
stock
will
already
have
it
open
where
you
try
to
provide
some
requests
for
license
in
or
something
else.
Oh,
we
have
separate
service
or
authentication,
and
we
should
expend
some
token
already
exists
and
we
divide
it
to
the
two
separate
modules
and
two
separate
bundles
and
one
will
provide
support
and
the
second
one
just.
A
As
its
art
that
the
traveler
plans,
actually,
we
would
like
to
move
for
the
notification
to
separate
module
and
possibly
separate
package.
We
do
have
the
notification
engine
enabled
right
now
it
is.
It
is
possible
to
add
second
method
of
identification
alone.
We
exist
in
one
not
place
an
existing
one,
but
one
who
is
existing
one
exists.
One
can
be
turned
off
in
this
case,
but
in
general
you
have.
This
story
is
when
we
will
divide
it
by
tax.
A
It
looks
like
we
will
have
to
implement
on
the
the
UI
part,
as
the
backend
part
is
already
present
in
our
develop
branch.
So
we'll
add
a
sign-in
link.
We
will
add
some
J's
that
will
start
the
process.
We
do
have
a
callback
controller
where
we
get
our
code
and
the
only
thing
we
will
need
to
do
is
to.
A
A
B
Okay,
I
understand,
silence
has
no
question,
so
the
next
story
is
basically
licensing
an
image
to
the
main
advantage
of
that
function
and
obviously
license
for
user
to
being
able
to
license
the
image
directly
in
magenta
admin
and
programmatically
save
the
licensed
image
into
an
idiot
gallery.
So
as
a
precondition.
So
we
need
to
mention
that
user
is
authorized
and
the
admin
panel
he
already
found
image
and
that
he
wants
to
license,
and
he
sees
the
detail
of
that
image.
Details
of
that
image.
B
B
If
user
confirms,
basically,
he
is
navigated
to
the
media
gallery
interface
and
to
the
current
folder
that
was
open
in
that
media
gallery
and
she's.
The
image
appear
in
that
folder
we're
still
but
trying
to
figure
out.
What
is
the
naming
convention
need
to
be
for
that
file?
So
this
is
like
something
that
it's
not
finalized
itself,
so
that
should
be
definitely
some
meaningful
name
for
sure.
B
But
what
is
the
format
it's
still
under
this
yeah
so
and
that
image
has
selected
and
ready
to
use
in
any
Content
where
the
magenta
media
gallery
was
called
from
so
in
case
user
doesn't
confirm
their
licensing
basically
they're,
just
he
just
like
closest
their
pop-up
and
nothing
happens.
Yeah!
That's
it.
A
Between
in
between
our
design
screenshots,
so
we
can
use
it
for
implementation,
but
I
see
that
Yujin
joined
the
call.
Actually
I
have
a
question
about
the
first
story
that
we
we
just
pass
about
the
design
like
just
available
or
when
we
will
be
able
to
see
the
design
of
sign-in
link.
Where
should
we
put
it.
E
A
E
E
A
E
B
A
Direction
at
least
identification
is
implemented,
and
the
next
step
is
to
get
user
quote
and
display
the
pop-up
with
information
about
user
credits
and
button
to
confirm
or
cancel
the
purchase.
That
probably
will
be
the
first
task,
and
the
second
task
is
actually
request
a
license
and
an
image
and
loading
saving
the
full-size
licensed
image,
and
that's
it
for
it.
At
the
end
of
the
licensing
process,
we
can
reuse
the
same
flow
as
we'd
already
use
for
saving
ready
image.
B
B
And
that
story
is
I
hope,
very
small
one.
So
the
purpose
of
this
story
to
help
users
identify
the
images
that
have
been
already
licensed
under
his/her
name
in
the
search
image
grid.
So
basically,
when
user
sees
the
images
in
the
grid-
and
there
are
some
images
that
have
been
already
licensed-
users
see
some
label
on
the
image
that
indicates
that
this
particular
image
was
was
licensed
directly
in
the
grid.
So
user
doesn't
need
to
open
image
details
to
see
that.
So
this
is
something
that
somehow
Eugene
to
define.
C
B
A
C
A
Seen
we
can
request
this
license
field
from
a
data
stack
API
during
perform
in
the
search
request
and
use
the
this
field
value
for
our
eye
defect,
identification
if
the
image
is
licensed.
However,
as
far
as
I
see
from
the
documentation,
there
are
several
values
that
can
be
returned
in
his
license:
field
of
Adobe
stock
API.
D
D
A
D
A
D
A
D
A
D
You're
not
asking
for
licensed
assets
you
that
we
don't
have
a
filter
to
give
you
licensed
assets.
All
we
can
do
is
say
when
the
data
comes
back,
show,
show
a
field
that
says
whether
it
is
licensed
or
not,
and
if
it
is
licensed,
it
will
give
you
one
of
those
string,
values,
standard
extended,
okay,
so
right
before.
B
D
B
A
Okay,
so
in
this
case
we
are
going
to
merge
the
result
of
the
search
request
to
API,
together
with
information
from
our
database
to
identify
if
images
saved
in
the
current
Magento
instance,
and
in
case
it
is
saved.
Oh,
we
are
going
to
show
the
different
version
of
of
license
button
so,
instead
of
license.
B
A
Yeah
also
in
the
scope
of
the
story,
I
want
to
bring
up
the
question
about
the
multiple,
multiple
instances
of
a
single
image
in
magenta
like
if
admin
user
would
like
to
save
an
image,
the
same
image
from
Adobe
stock
II,
the
first
folder
of
media
gallery,
and
then
repeat
the
separation,
the
second
folder
of
media
gallery.
Should
we
allow
it?
B
Most
likely
that
could
happen
not
intentionally
by
just
by
mistake,
and
this
is
something
that
we
at
least
need
to
inform
the
user
about,
but
like
from
my
perspective,
their
image
management
once
the
image
is
saved
into
magenta.
Media
gallery
need
to
happen
on
media
gallery
site.
So
if
user
wants
to
move
the
image
from
one
folder
to
another,
there
is
functionality
in
mentioned
the
media
gallery.
To
do
that.
We
shouldn't
like
use
a
lot
of
stock.
To
do
that,
so
I
would
prefer.
B
My
suggestion
is
to
to
kind
of
prevent
users
from
saving
the
same
image
in
two
different
folder
structure,
just
to
prevent,
like
the
content,
duplication
that
most
likely
happened
accidentally.
But
it's.
It
still
can't
happen.
I
believe-
and
this
is
like
something
that
maybe
we
need
to
discuss,
because,
for
example,
what
will
happen
if
different
users
licensed
the
same
image
and
different
Adobe
stock
IDs
and
save
that
image
into
the
media
gallery
will
be
the
same
image
or
it
will
be
completely
two
different
images
that
have
no
connection
with
each
other.
It.
F
C
C
F
Okay,
sorry,
just
and
what
about
next
possible
functionality,
for
example,
is
an
old
licensing
which,
at
the
folder
name
a
yes
and
then
I,
just
not
accidentally,
but
I,
understand
that
what
I
want
to
have
this
image
at
the
folder
be,
for
example,
yes,
but
I
do
not
save
it,
because
it's
already
gays
but
I
assign
it
to
be
folder
B,
because,
just
if
it
is
possible
to
assign
image
to
the
folder
and
not
to
move
it
physically.
What.
D
F
B
C
C
I'm
going
to
add
one
one
simple
case:
let's
imagine
that
we
will
have
you
know
hundreds
of
folders
in
our
media,
magenta,
media
gallery
and
I'm,
trying
to
say
exactly
this.
This
image,
you
know
my
folder
number
1025
and
is
the
message
that
I
already
have
this
image,
but
I
don't
know
which,
for
there
can't
this
English
but
I
need.
B
C
B
No
you,
you
did
not
just
see
that
you
already
have
the
image
you're
actually
navigated,
to
the
folder,
where
image
is
and,
like
you
see
the
image
selected
on
that
folder.
So
this
is
like
the
intended
use
case,
but
my
questions
like
I
wasn't
sure
how
to
handle
the
situation
when
the
image
was
licensed
under
someone's
name
and
technically
it
it's.
But
from
my
understanding
this
image
that
licensed
under
someone
else
name
should
be
stored
in
magenta
media
gallery
with
exactly
the
same
parameters
as
if
I
would
license
it.
B
B
B
B
A
The
image
is
not
licensed,
it
will
say,
license
and
save
second
states
Eve.
The
image
is
licensed,
but
is
not
downloaded,
we'll
call
it
something
like
download
and
the
source
stage.
When
the
image
is
licensed
and
these
downloaded,
we
will
just
name
it
select
and
when
you
click,
when
admin
user
clicks
a
button,
each
will
open
the
folder
in
media
gallery
where
this
image
is
start
and
select
image
to
be
ready
to
insert
it
right.
Yeah.
A
B
B
B
A
C
A
D
I'm
I'm
I'm
on
a
and
I'm
outside
of
the
house
now
I'm
in
a
car
I
think
yeah
I
mean
if,
if
you
allow
the
person
user
to
download
a
preview
multiple
times
to
different
folders
and
then
later
they
replace
that
with
a
licensed
image
that
then
you
might
have
to
go
through
and
check
for
all
instances
other
than
that
could
get
really
messy.
So
maybe
you
should
only.
B
B
C
Probably
we
should
name
images,
both
images,
preview
images
and
licensed
images
with
the
same
name.
It
helped
us
replace
the
image
when
we
trying
to
license
it.
For
example,
we
don't
load
it
preview
with
the
name.
You
know
preview,
one
two,
three
edit
this
image
to
the
several
content
pages
and
we
need
just
replace
the
image
with
the
same
name.
Entry.
Try
also
try
to
avoid
the
content
of
days.
B
C
B
The
concern
was
like
Adobe
stock
ID
I
mean
that
naming
convention
to
me
works
for
preview
purse
and
then
just
like
by
itself,
because
preview
is
not
gonna,
be
published
on
the
life
website
right,
but
for
the
images
that
are
going
to
be
published
on
the
website
of
Sam
in
email.
This
kind
of
naming
file
not
ideal.
B
A
C
A
C
A
C
B
A
E
E
D
E
E
The
title
URL
friendly
title:
we
can
convert
it
and
put
it
in
the
field
if
they're,
okay,
with
that,
it's
okay,
if
they're
not
they
can
change
that.
But
what
I
see
right
now,
titles
in
Adobe
stock,
they're,
pretty
long
because
author
tries
to
you
know
make
it
search
findable.
So
he
puts
all
the
keywords
in
the
title
so
that
that
is
I
see
a
problem
if
we
just
convert
the
title
blindly
so.
E
B
C
A
C
B
A
E
A
So,
basically,
if
there
is
any
record
for
yeah,
there
are
two
conditions.
First,
one
is
that
we
do
have
a
record
in
the
database
for
the
media
ID
for
the
Adobe
ID
of
the
omission.
Second
condition
is
that
file
is
still
present
in
file
system
from
our
records,
and
then
we
can
say
that
there
is
either
preview
or
licensed
image
saved
already.
B
B
A
There
are
no
no
dependency
that
they
can
see.
Actually,
the
only
thing
we
have
to
agree
on
is
that
a
preview
and
license
will
have
the
same
name
and
was
image
saved
in
any
way,
is
it
preview
or
license
want
some
particular
image
with
media
ID
on
other
beside
is
saved.
We
are
not
updating
the
image
name.
A
C
A
C
B
C
Let's
imagine
sand.
We
can't
rename
these
images
and
you
save
image
from
the
Adobe
stock
with
any
names
that
we
want,
for
example,
Adobe,
stock
underscore
ID
and
after
a
user,
if
you
want
it
will
rename
this
image
also
named.
If
you
want,
we
can
handle
this
event
and
just
a
correct
name
in
our
database
and
when
we
decide
to
license.