►
From YouTube: Humans of DataHub: Atul Saurav
Description
We are back with another round of Humans of DataHub! This week we are joined by Atul Saurav, Senior IT Architecture Design Manager, Data Governance at Genworth Financial.
Atul shares his journey to DataHub, his learnings along the way, and what features and use cases he's most excited about. You don't want to miss this conversation!
Learn more about DataHub: https://datahubproject.io
Join us on Slack: http://slack.datahubproject.io
Follow us on Twitter: https://twitter.com/datahubproject
A
B
I
mentioned
we
are
a
financial
services
organization,
which
means
we
have
offerings
and
insurance
we
have
offering
from
annuities.
We
have
offering
them
mortgage
insurance
and
so
on.
It's
a
primarily
if
you
look
at
it
from
the
suit
and
financial
services
domain.
My
role
in
the
organization
is
I
am
the
architect
of
digital
University
in
the
organization,
and
what
that
means
is
that
in
a
financial
service
or
insurance,
which
has
always
been
regulated
industry,
the
concept
of
governance
is
nothing.
It's.
A
B
Been
around
but
what's
new
and
what
I
am
particularly
excited
about
is
how
we
are
approaching
them.
It
has
always
been
a
very
manual
collaborative
stuff.
It
continues
to
remain
collaborative,
but
we
are
slowly
trying
to
remove
that
manual
aspect
of
it.
I
mean
most
of
it
automated,
so
people
can
start
seeing
value
in
the
data
that
they
have
and
use
smallest
lead
time
possible.
A
Awesome
so
you
know
when,
like
how
did
you,
how
did
you
even
find
out
about
data
like
what
brought
you
to
the
community?
Obviously,
if
you're
working
towards
automated
data
governance,
you
came
to
the
right
place,
we're
so
happy
to
have
you
but
yeah.
How
did
you
find
out
about
us
and.
B
B
I
remember
this
yeah
I
was
like
yeah.
This
is
very
interesting
and
what
particularly
excited
me
about
the
talk
was
you
talk
to
some
of
the
challenges
that
we
were
going
through,
so
the
challenges
that
we
are
going
through
are
things
like
hey.
We
have
this
process
this
pipeline
that
feeds
the
stable
and
we
want
to
be
able
to
understand
the
lineage.
We
want
to
be
able
to
understand.
What's
going
on
so
your
governance,
how
about
you
figure
out
all
your
stuff
for
me
and
you
wish
to
find
it
for
you
sure.
A
It
should
be
easy
right.
It.
B
B
Yeah
you've
got
to
do
this,
so
I
was
totally
thrilled
with
the
talk
met,
srishanka
right
after
the
talk,
but
then
at
that
point
we
had
already
signed
a
contract
with
one
of
the
commercial
products
which
was
out
there.
B
And
we
kept
looking
at
data
hub
from
that
point
in
time,
but
we
were
like
this
thing
extends
for
so
many
years,
which
means
that
we
want
to
go
in
the
direction.
Then
it's
not
going
to
be
happening
sooner
than
that
sure
they
were
kind
of
withheld
by
a
little
bit
of
that
and
we're
also
like
okay,
let's
see
where
we
can
get
it,
what
we
have
right
because
we've
invested
so
much.
B
So
that's
what
was
going
on
for
quite
some
time,
but
we
were
able
to
leverage
a
lot
of
that
learning
from
the
other
commercial
offering,
and
we
were
so
happy
that
some
of
those
challenges
that
we
had
in
the
product,
so
what
happens
is
when
I
speak
to
challenges.
That
probably
should
be
more
specific.
B
Counts
towards
your
license
and
generate
being
a
company
that
grew
over
Acquisitions
in
past
many
years.
We
have
a
lot
of
data
across
lot
of
different
data
sources,
which
is
just
there
because
of
the
nature
of
the
company
sure
right
sure.
So
all
those
pricing
models
just
didn't
make
any
economic
sense.
B
A
B
That
was
our
challenge
right
initially,
when
we
did
work
with
other
products
also,
we
would
constantly
meet
users
and
they
would
say
okay.
This
is
great,
but
where
is
my
stuff
here?.
A
B
You
can
look
for
it
and
there'd
always
be
things
which
were
not
there,
because
we're
always
focused
on
saying
okay,
what
is
important
for
the
organization,
because
we
can
only
have
X
number
of
connections
based
on
their
life,
sure
sure,
so
they
would
always
come
up
with
something
which
we
had
not
cataloged
and
that
brought
down
the
level
of
trust
in
what
we
were
trying
to
offer
to
them,
and
that
was
like
a
huge
setback.
Every
you
make
two
steps
forward.
One
step
back,
two
step
forward,
one
step
back.
B
A
B
It
you'll
find
it
not
there.
Let
me
know
because
it
has
to
be
done
everything
right
and
that's
quite
compelling
in
itself,
because
any
data
users
and
even
me
if
I,
go
in
that
space
and
I'm
working
in
that
who
knows
analyst
ETL,
developer,
bie
report,
writers,
data
scientist,
whoever
I
usually
come
in
with
a
perspective
of
I,
know
district.
Is
that
correct?
B
Or
is
that
event
true,
because
there's
probably
more
data
data
out
there
and
if
I
don't
do
that
due
diligence,
then
I
may
just
be
portraying
a
partial
picture
with
the
limited
knowledge
of
the
data
that
I
have
right
so
being
able
to
create
that
full
picture
of
the
United
landscape
in
the
organization.
That's
really
exciting.
That's.
A
Amazing
yeah
and
I
love
that
I
mean
I.
Don't
love
the
idea
of
losing
trust,
but
I
I
think
we
I
hear
this
a
lot
from
community
members
like
we
really
the
level
of
trust
when,
when
end
users
come
in,
it's
so
important
for
that
investment
right
and
it's
also
extremely
easy
to
start
losing
trust
very
fast.
Yeah.
B
A
And
so
it's
like
you
get
a
few
chances
to
get
people
to
understand
what's
going
on.
Why
is
this
worth
their
attention
and
then,
if
there's
just
these
kind
of
glaring
gaps
with
seemingly,
you
know
not
of
very
easy
to
understand,
reason
why
right
like
if
you're
living,
if
you
have
a
limited
number
of
connectors-
and
you
just
had
to
choose
a
few
like
that's,
not
a
good-
that's
not
like
a
clear
reason
for
them
to
understand
why
it
might
be
missing
right.
A
A
So
thinking
about
you
know
your
your
work
within
data
Hub
now
and
kind
of
rolling
it
out
within
your
organization.
What
are
some
of
the
most
powerful
use
cases
or
features
within
data
Hub
that
you're
seeing
either
kind
of
like
a
lot
of
excitement
about,
or
you
know,
maybe
like
higher
adoption
just.
B
People
have
been
asking
for
polymer
lineage
sure
we
had
that
in
our
previous
product
that
we
were
working
with,
and
we
had
mixed
kind
of
reviews
about
that
from
our
users,
because
some
users
totally
loved
it.
Some
users
were
like
this
is
not
true.
It
can't
be
so
complicated,
yeah
and
you're
like
okay.
A
B
He
probably
was
trying
to
solve
some
problem
that
you're
not
aware
of
yeah,
or
maybe
he
overcomplicated
it,
because
he
did
not
understand
something
right
right
and
you
could
specify
it
for
that
person
right
and
that
data
becomes
much
more
robust
and
much
more
usable,
much
more
trustworthy.
Just
based
on
that
discussion,
even
though
it's
really
powerful,
we
are
kind
of
stepping
slowly.
A
B
That
as
I
believe,
it
will
slowly
mature
and
we're
happy
to
contribute
ideas
on
that
as
well.
Based
on
our
past
learning
being
able
to
model
new
Concepts
into
Data
Hub
with
minimal
code,
that's
pretty
powerful
data
Hub
and
comes
with
most
commonly
observed
kinds
of
Concepts,
but
it
doesn't
prohibit
us
from
creating
something
new
which
we
feel.
A
B
That's
really
exciting
the
actions
framework
that
came
in
earlier
this
year,
that's
also
pretty
powerful.
We
intend
to
use
it,
we
have
not
used
it
yet,
but
it's.
B
Action
framework
is
like
hey,
so
if
I
tag
something
here
and
there's
an
action
looking
for
the
tag
and
based
on
that
I
can
trigger
some
events,
that's
pretty
powerful.
Then
we
totally
want
to
leverage
that
I'm.
A
Curious
what
the
model
extension
I
agree
like
I
think
it's
like
the
no
code
metadata
modeling
to
me
is
one
of
the
most
powerful
things
that
we
can
offer
right
where
it's
like
we're
gonna
we're
gonna
start
with
the
bare
bones
of
you
know
we
have
data,
sets
dashboards,
charts
glossary
chart.
You
know
tat
like
all
of
these
things
that
we
know
are
common
across
data
Stacks,
but
maybe
your
organization
talks
about
or
thinks
about
entities
in
a
slightly
different
way.
A
B
Not
a
company
Secrets
just
about
how
you
look
at
things
right,
so
I
mean
data
processes
and
data
pipelines
are
great
right.
That's
the
reality
or
that's
the
physical
reality
of
how
things
are
laid
out
in
the
organization,
but
there's
always
an
abstraction.
On
top
of
it,
yeah
which
people
usually
talk
about
like
business
processes
and
such.
B
B
Now,
if
you
look
at
it
from
a
data
lineage
perspective,
that's
a
fairly
complicated
lineage,
only
bracket
sure
right.
So
someone
who
is
like
totally
aware
of
exactly
all
those
intricacies.
They
can
benefit
a
lot
from
the
lineage
because
they
can
go
in
and
say.
Okay,
if
we
have,
if
we
are
capturing
this
new
attribute
from
a
user,
then
where
are
does
it
impact?
What
does
it
mean
and
things
like
that,
but
from
a
person
who
is
maybe
new
to
that
space
or
who
wants
to
understand
things
at
a
higher
level.
B
I
want
to
say:
okay,
so
we
launched
this
new
feature,
new
coverage
new
product.
What
not
and
I
want
to
see.
How
does
it
impact
or
how
are
things
going
on
with
this
new
launch?
A
B
B
A
B
Because
we
want
to
be
able
to
annotate
that
graph
and
make
it
really
rich
and
be
able
to
query
it
in
all
different
ways.
Yeah
so
I
think
yeah,
that
being
able
to
introduce
new
Concepts
into
the
craft
being
able
to
form
those
connections
being
able
to
portray
that
picture
at
different
levels
in
the
organization.
So
people
can
still
even
value
out
of
it.
A
A
It
can
become
really
easy
to
lose
the
conceptual
mapping
to
the
business,
yeah
right
and
so
I
really
like
that
idea
of
how
do
you
tie
a
data
entity
back
to
a
flow
and
or
a
workflow,
or
you
know
really
like
the
inner
workings
of
the
business
right
and
make
it
a
little
bit
more
concrete
and
not
just
we
have
thousands
of
pipelines
and
they're
all
equally
as
important
yeah.
B
B
Does
that
rubber
totally
and
one
of
the
discussions
we
were
in
recently
was
all
about
okay,
we
are
all
starting
to
use
AI,
machine
learning
and
stuff,
because
now
regulation
is
just
catching
up
space.
So
it's
like
you've
got
to
be
aware
that
thing
is
going
to
land,
and
you
know
it's
going
to
land
yeah.
B
A
A
So
I
mean
it
sounds
like
you
have
plenty
of
you
know
existing
use
cases
and
places
that
you
want
to
go
or
plus
you
want
to
leverage
data.
Hub,
I'm,
curious
kind
of
thinking
forward.
I
mean
now
what
we're
in
kind
of
Q4
or
wait
are
we
in
Q4
geez?
Yes,
we
are
yes.
A
In
Q4
of
2022,
we
made
it
my
goodness
so
thinking
through
you
know
kind
of
the
next
six
months,
12
months
kind
of
specifically
within
the
data
Hub
product
space.
Are
there
any
kind
of
like
use
cases
you
you
want
to
see
us
tackle
or
features
or
like
different
types
of
support
that
you're
excited
about.
B
So,
like
I
said,
we
are
closely
observing
how
the
column
level
lineage
yeah,
because
we
have
seen
both
sides
of
it
and
some
users
in
your
organization
still
are
actively
looking
for
it.
So
that
is
one
thing
that
we
are
closely
following:
I
believe
the
low
code.
A
B
Because
there's
definitely
some
scope
for
improvement
there,
where
it
can
get
much
better
because
usable
patterns
occur
all
the
time.
It's.
A
B
How
do
we
add
more
of
those
so
it
becomes
much
more
powerful,
so
that
is
that
space
one
of
the
other
areas
was.
B
Scale
and
performance,
so
we
because
of
how
we
are
where
we
are
today,
we
do
bring
in
a
lot
of
content,
so
just
based
on
the
pure
ingestion
of
metadata
at
a
data
set
level
right,
we
are
a
pretty
decent
size,
deployment,
Plus
data
and,
as
we
go
into
column
level,
lineage
that
is
going
to
explode.
B
B
The
architecture
is
very
well
thought
of
and
something
I'm
really
happy
about
how
you
guys
have
done
that.
But
then,
as
they
go
into
the
column
level
content,
it
will
get
really.
B
To
everything
yeah,
the
users
like
us,
who
want
to
say,
hey
I,
want
to
bring
in
my
own
Concepts
and
I
want
to
further
enrich
this
country
right,
I'm
very
excited.
So
it
sounds
like
a
good
opportunity.
A
Well,
you
know
I
think
with
the
column
level,
lineage
stuff
in
particular,
I
I,
I'm
excited
well,
I
will
be
part.
I
will
be
reaching
out
to
partner
with
you
on
this,
because
I
I
really
want
to
understand
how
we
surface
it
in
a
way,
that's
actually
meaningful
for
end
users,
because
not
only
the
performance
part
of
it
right,
you're,
gonna,
go
I
mean
orders
of
magnitude
of
complexity
just
from
processing,
but
then
you
there's
a
human
at
the
end
of
that.
That
needs
to
make
sense
of
it.
So
how
do
we?
A
A
How
do
we
actually
like
show
that,
in
a
way
that
people
can
look
at
and
say,
cool
I
am
now
better
informed
and
not
more
confused
right,
so
yeah
I
think
that's
going
to
be
a
really
exciting
kind
of
challenge
for
us
to
not
just
say,
like
kind
of
take
calm
level
lineage
off
the
box,
but
actually
make
it
or
take
it
off
of
the
list,
but
actually
make
it
a
an
impactful
and
like
reliable
resource
for
folks
yeah
very.
A
Course
I
mean
you're,
just
like
you'll
talk
to
me
about
this
stuff
all
day,
I
love
it
all
right.
One
final
question
for
you
and
I
love:
I
love
this
one.
A
B
Still
very
fertile
and
growing
out
there
yeah
a
lot
of
problems
which
are
unsolid
a
lot
of
really
looking
problems
which
are
unsolved,
which
have
to
be
solved,
but
so
it's
a
really
exciting
space
to
be
in
data
Hub
community
in
particular,
I
have
found
to
be
very
responsive,
supportive,
welcoming
I
mean
there's
a
getting
started,
Channel
introduce
yourself
and
those
two
channels
are
really
great
right,
because
I
came
in
I
introduced
myself
and
there
were
a
couple
folks
who
said
hey
and
that's
always
nice
to
hear
from
someone
totally
it's
like
you
can
go
on
those
communities
and
when
you
say
something
and
the
new
one
responds
and
who
knows
you
probably
post
a
question
and
you're
like?
B
B
A
A
I
love
that
I
I,
really
I,
take
I.
Take
a
lot
of
pride
in
the
fact
that
you
know
we're
as
a
community
grows
like
people
are
still
feeling
that
sense
of
welcoming
and
that
sense
of
you
know
if
I
post
a
question
I'll
get
a
response,
but
also,
if
I
just
say:
hi,
yeah,
I'm
so
and
so
I'll
also
get
a
response
right
like
there's
just.
B
B
A
A
A
Fantastic
partner
in
the
community
and
we're
just
I'm
I'm
personally
so
pleased
to
be
working
with
you
and
I
know
that
the
rest
of
the
core
team.
B
Is
awesome
likewise
Maggie
I
think
I'm
able
to
work
or
do
what
I'm
supposed
to
do
better
because
of
all
the
support
I
get
from
you
all
amazing,
pretty
thankful
for
that.
That's.
A
Well,
thank
you
so
much
and
we'll
see
you
we'll
see
you
on
slack
thanks
a
tool
sure.