►
From YouTube: DataHub 201: Business Glossary
Description
Chris Collins (Acryl Data) provides an overview of everything you need to know about creating and managing a Business Glossary in DataHub during the June 2022 Town Hall.
Learn more about DataHub: https://datahubproject.io
Join us on Slack: http://slack.datahubproject.io
Follow us on Twitter: https://twitter.com/datahubproject
A
All
right,
hey
everyone,
so
yeah,
as
Maggie
said
today,
I'm
going
to
be
talking
about
the
business
glossary
and
data
Hub,
so
talking
about
these
glossaries
what
they
are
and
how
you
can,
how
you
can
use
them
for
your
team's
benefit
all
right
before
we
get
more
into
specifics.
Let's
tackle
first
things.
First,
what
even
is
a
business
glossary?
A
A
business
glossary
is
a
place
where
organizations
can
centrally
Define
and
organize
assets
through
terms
that
are
used
by
the
business.
The
goal
of
the
glossary
is
to
create
a
single
source
of
Truth
when
it
comes
to
Industry
field
or
company,
specific
terms,
phrases
or
acronyms.
As
you
can
imagine,
there
can
be
a
lot
of
those
when
everyone
is
aligned.
You
can
leverage
your
business
glossary
on
data
Hub
to
organize
data
assets
using
the
shared
vocabulary.
A
The
days
of
misunderstanding,
a
metric
or
phrase
are
long
gone,
I'm,
happy
to
say,
and
now
you
can
accurately
describe
different
assets
within
your
organization
for
your
business
needs.
Not
only
will
your
business
rooms
be
less
ambiguous
when
describing
your
data,
but
by
assigning
terms
to
different
assets,
you're
also
grouping
them
together
for
discoverability.
A
You
can
easily
see
all
the
different
assets
assigned
to
a
term
by
just
checking
out
the
terms
page
and
seeing
all
of
its
related
entities.
I'll
go
more
into
details
about
this
and
other
specific
use
cases
as
well
in
a
little
bit,
but
now
that
I've
hopefully
sold
you
on
the
importance
of
a
business
glossary.
Let's
go
into
some
specifics
around
how
to
create
a
glossary
on
data
Hub
and
get
it
working
for
you
and
your
needs
so
yeah
creating
your
glossary.
A
There
are
two
ways
that
you
can
create:
a
business
glossary
and
data
Hub.
Today,
first
ingest
your
glossary
via
yaml
file,
with
your
terms
and
definitions
or
you
can
create
it
via
the
UI
foreign,
for
your
glossary
looks
like
this
snippet
here
you
define
the
structure
and
Fields
of
your
glossary
and
then
ingest
using
the
data.
Hub
command
line
tool
ingesting
via
yaml
file
has
the
benefit
of
checking
in
code
and
tracking
your
changes
through
to
your
glossary
through
Version
Control
like
GitHub.
A
However,
it
may
be
less
accessible
for
non-technical
users,
as
you
can
imagine
all
right
and
then
creating
to
the
UI.
This
involves
going
to
your
glossary
and
data
Hub
and
from
here
you
can
create
terms
and
term
groups
to
organize
terms
under
simply
click
the
menu
and
open
a
modal
to
create,
as
you
can
see
in
some
of
the
screenshots
here.
In
contrast
to
creating
your
glossary
via
yaml,
creating
through
the
UI
may
be
more
accessible
for
non-technical
users,
but
doesn't
give
you
that
benefit
of
tracking
change
and
distribution
control.
A
But
it
is
a
lot
easier
to
make
small
changes.
Ad
hoc
changes
all
that
sort
of
stuff
all
right
so
now
that
you've
actually
gone
through
the
work
of
creating
your
well
thought
out.
Business
glossary.
Let's
talk
about
adding
your
terms
to
different
data
entities,
so
there
are
several
different
ways.
You
can
go
about
accomplishing
this,
including
through
the
UI
on
an
entity
stage
using
the
new
CSV
feature
that
was
just
demoed
by
Audi
Joe.
Thank
you
for
that.
A
I'll
do
a
great
demo
and
using
Transformers
so
first
adding
through
the
UI,
adding
glossary
turns
to
entities
to
the
UI
is
as
simple
as
finding
the
entity
you
care
about.
You
got
to
go
to
its
page
and
then
just
click,
the
add
term
Button.
As
you
can
see,
I've
circled
in
green
in
the
modal
that
pops
up,
you
can
then
navigate
through
your
glossary
and
select
the
term
you
want,
which
is
easier
now
than
ever.
It
was
before
another
option
that
I
mentioned
before
is
adding
terms
to
entities
with
your
new
CSV
ingestion
feature.
A
This
allows
you
to
set
multiple
terms:
do
more
bulk
actions
just
by
setting
the
entities
and
providing
earns
attitude.
Just
went
over
this
just
kind
of
kind
of
Move
On
by
and
not
waste
your
time
and
then
finally,
you
can
use
Transformers
within
your
ingestion
recipe.
To
also
add
terms
when
ingesting
your
data,
there's
a
few
different
options
that
we
provide
out
of
the
box
here.
So
first,
you
can
add
terms
to
all
the
data
sets
you're
ingesting
like
Transformer
number
one
or
you
can
specify
data
set
name
patterns
targets.
A
Only
specific
data
sets
that
you
want
like
Transformer
to,
or
you
can
specify
specific
schema
fields
that
you
want
to
add
terms
to
as
well
like
Transformer
3..
Finally,
you
can
always
write
custom
Transformers
to
add
glossary
terms,
however
you'd
like,
but
these
are
the
three
that
we
provide
right
here.
All
of
this
is
as
well
documented
on
our
docs
site.
I
would
definitely
check
it
out
if
you
guys
have
any
further
questions.
A
I
put
the
link
here,
but
also
ask
questions
and
Slack
cool
now
that
your
glossary
is
all
put
together
and
data
assets
are
tagged
terms.
Let's
talk
about
a
couple
different
use
cases
for
the
business
glossary
and
data
hub
for
our
first
use
case.
Imagine
you're
at
an
organization
that
has
different
kpis
that
are
important
to
different
areas
of
the
business.
Previously,
a
kpi
was
just
a
concept
that
you
were
supposed
to
just
kind
of
know,
and
you
knew
it
was
relevant
to
your
data
and
your
organization,
but
you
weren't
really
sure.
A
Where
or
how
now
with
datahub's
business
glossary,
you
can
actually
have
a
material
presence
of
what
was
previously
just
a
concept.
Not
only
is
it
a
real
entity
that
you
can
reference,
it's
actually
with
your
data
alongside
it,
not
just
in
notion
or
Google,
Docs
or
somewhere
else
out
there
in
The
Ether
with
this
comes
the
ability
to
easily
see
all
assets
relevant
for
this
kpi
all
on
the
same
platform,
curious
about
how
your
company
calculates
return
rate.
A
So
let
me
move
this
thing:
okay,
cool!
So
you
know
you
collect
the
address
of
some
of
your
users
and
you're
curious
about
this.
You
know
you
have
an
address
glossary
term
and
you
want
to
know
more,
so
you
can
navigate
to
your
glossary
and
find
this
address
term
that
you
care
about
to
do
a
little
bit
of
Investigation
I
know
address
is
under
personal
information.
You
could
have
always
looked
here
and
found
it
so
now
we're
at
our
ads
address
page.
A
This
term
page
is
actually
going
to
tell
you
exactly
what
an
address
is.
So
at
least
you
know
what
you're
talking
about
street
addresses
here
and
not
something
like
an
IP
address,
so
we're
reducing
mbu
to
here
already
from
here.
You
can
also
see
the
source
of
the
definition.
If
you
wanted
to
go
check
that
out,
that's
a
new
feature
that
we
added
back
that
was
previously
lost,
and
then
you
can
also
check
out
the
related
entities
Tab
and
see
all
of
the
different
entities
that
have
been
tagged
with
this
term.
A
A
So
I'm
going
to
go
to
this
related
entities
Tab
and
now,
for
the
first
time
you
can
actually
control
different,
contains
and
inherits
relationships
through
the
UI
by
adding
different
terms
to
link
them.
So
in
this
situation,
I
know
that
address
is
sensitive
and
I'm
going
to
say
that
I
want
to
add
an
inheritance
relationship
between
this
address
and
say
that
it
inherits
from
something
that
I
know
another
term
that
I
know
we
have
sensitive.
A
Let's
add
it
and
boom
there
we
go.
It
is
now
inheriting
from
sensitive,
but
not
only
this.
You
can
actually
go
to
the
sensitive
term
page
and
check
out
its
related
entities.
Tab-
and
here
you
can
check
out
one,
not
only
all
the
entities
that
are
tagged
with
sensitive,
but
also
all
the
entities
that
are
tagged
with
the
terms
that
directly
inherit
from
this
sensitive
term.
As
you
can
see,
address
we
just
added
as
inherits
from
sensitive.