►
From YouTube: catalog explanation
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi,
this
is
Frederick
speaking
about
the
catalog,
so
I
thought
I
would
do
a
really
quick
rundown
of
what
is
in
the
space
catalog
to
help
us
clear
out
where,
in
the
navigation,
we
should
put
this
item.
So
imagine
that
I
work
on
my
project,
which
is
called
Big,
Pipeline
and
I,
want
to
write.
Acicd
configuration
I
work
in
an
org
that
is
called,
let's
say:
evil,
org
and
evil.
Org
really
wants
me
to
get
this
done,
so
they
have
prepared
a
bunch
of
components
that
they
make
available
to
all
the
projects
within
their
organization.
A
So
I
am
here
right
and
I
am
in
this
project,
and
I
want
to
go
and
see
all
of
the
components
that
I
have
available
for
this
project.
It
has
been
proposed
that
I
could
go
through
the
explore
menu
to
do
this.
The
problem
is
you
see
here
we
have
this
I
mean
you
call
switch
contacts
and
you
have
things
like
your
work
and
explore
and
admin
area
which
are
categories
that
will
not
show
me
things
about
this
project,
but
about
me
as
a
user
right.
A
So
if
I
go
into
the
Explorer
I
will
see
all
the
projects
or
groups
or
stuff
that
I
have
access
to.
I
can
browse
multiple
things.
The
problem
is
a
catalog,
it's
not
a
thing
that
I
have
access
to
and
that
I
browse
multiple
catalogs
I
can't
have
here
the
ICD
catalog,
because
I'm
no
longer
under
the
big
pipeline,
namespace
I'm,
not
even
under
any
namespace
right
I,
am
at
the
root
of
my
instance,
and
so
in
this
context,
I
I.
A
If
we
have
a
menu
here
that
says
the
ICD
catalog
and
I
collect,
where
am
I
taken,
where
do
I
go?
Why
do
I
default
to
the
first
of
the
list
of
all
the
catalogs
I
could
have
access
because
I
could
have
you
know
any
of
these
projects
here,
but
have
a
different
catalog.
It
could
be
under
different
namespaces
and
see
here.
This
one
is
under
admin
right
me,
SS
username
space,
so
I
could
have
a
catalog
for
administrator.
I
could
have
one
for
Kristin
thunk
right.
A
So
we
can't
just
have
one
item
that
takes
you
to
a
catalog.
We
need
a
way
to
just
say
which
catalog
and
so
explore
would
not
work
for
this.
We
would
need
something
called
catalogs,
plural,
where
you
would
click
and
you
would
see
all
of
the
catalogs
you
have
access
to,
but
that's
kind
of
pointless
because
you
don't
want
to
browse
data
logs
outside
of
their
scope.
You
want
to
see
like
right,
I
started
from
I'm
in
big
Pipeline
and
I
just
want
to
see
the
components
that
I
want.
A
I
can
see
from
this
project,
so
I
would
go
and
explore
oh
and
either
projects
or
this
new
item,
cicd
catalogs
click
see
all
of
the
namespace
and
then
go
back
into
the
namespace
of
the
big
pipeline,
so
that
doesn't
work.
What
we
want
is
if
I'm
in
big
pipeline
from
here
somewhere
I
need
to
be
able
to
say,
click
right.
This
is
the
namespace
catalog
and
you
can
see
here
we
go
into
the
pipeline
editor.
We
have
a
a
link
for
now
here.
So
I'm
in
I
want
to
write
my
pipeline.
A
Oh
when
the
browse
the
catalog
components
right,
I
am
in
root.
My
username,
my
name
space,
my
project
and
I'm.
Seeing
all
the
resources
that
are
shared
to
our
namespace,
it
is
under
the
project,
but
I
still
can
get
all
of
the
components
all
the
way
up
to
the
rooting
space
of
my
organization,
and
this
is
where
it
is
shared
across
project,
but
I
might
not
have
access
to
other
projects
under
that
namespace
right
like
it's,
so
it
is.
A
This
is
where
it
is
a
per
project
basis,
but
you
may
get
projects
from
anywhere
under
your
name
space,
and
this
is
if
you're
wondering
why
it's
because
ACI
CD
component
repo
is
actually
a
it's
a
project
right
like
this
right
here:
The
Adventure,
Time,
Jake
and
others
components
repo
14.
This
is
a
project
if
I
go
and
I
I
can
go
and
explore
and
I
can
go
and
look
at
all
projects,
components,
repo
14..
A
So
the
reason
why
it
may
feel
confusing
is
that
your
component
is
actually
a
repo.
So
you
can't
it's
a
project
under
the
hood.
It
is
a
project,
so
you
need
a
link
that
you
know
will
take
you
to
a
page
where
you
see
all
of
these
projects
that
are
on
there
the
same
namespace
as
you
that
are
specifically
CI
resources
project,
not
generic
project,
and
this
is
where
I
think
the
confusion
starts
from
the
component
is
not
just
a
thing
that
you
share,
which
is
why,
at
first
we
thought
and
build.
A
We
would
have
like
a
catalog
option
and
you
could
put
it
would
be
taken
straight
to
where
it
was
before
here
where
I
could
see.
Okay,
this
is
what
all
I
have
access
to.
It
may
be
that
we
need
to
clarify
this.
We
say
repository
of
this
particular
compost
available
in
this
namespace,
and
then
we
have
a
learn
more
and
then
we
have
like
a
very
generic
link.