WEBVTT

00:00:00.000 --> 00:00:07.050 align:middle line:90%


00:00:07.050 --> 00:00:10.330 align:middle line:84%
Work in my field of
research, it tends

00:00:10.330 --> 00:00:11.680 align:middle line:90%
to be very multidisciplinary.

00:00:11.680 --> 00:00:13.420 align:middle line:84%
For example, I'm an
engineer, but I also

00:00:13.420 --> 00:00:17.520 align:middle line:84%
tend to work in applied
mathematics or in statistics.

00:00:17.520 --> 00:00:22.120 align:middle line:84%
And I found that you cannot, you just
cannot, know everything that you need

00:00:22.120 --> 00:00:23.750 align:middle line:90%
to progress your work.

00:00:23.750 --> 00:00:25.250 align:middle line:84%
So for example,
on a regular basis

00:00:25.250 --> 00:00:28.090 align:middle line:84%
I would consult, during
this project specifically,

00:00:28.090 --> 00:00:30.910 align:middle line:84%
aerodynamicists or
structural engineers

00:00:30.910 --> 00:00:33.580 align:middle line:84%
or bioengineers,
mathematicians, statisticians,

00:00:33.580 --> 00:00:36.860 align:middle line:84%
physicists, and all
sorts of other people.

00:00:36.860 --> 00:00:41.680 align:middle line:84%
And I think it's very important
to have a varied partnership

00:00:41.680 --> 00:00:45.250 align:middle line:84%
of collaborators, so
that you can reach out

00:00:45.250 --> 00:00:48.700 align:middle line:84%
to those with better
expertise when

00:00:48.700 --> 00:00:54.130 align:middle line:84%
the time arises for you to ask
questions along your research.

00:00:54.130 --> 00:00:59.990 align:middle line:90%


00:00:59.990 --> 00:01:02.720 align:middle line:84%
When participating
in research projects,

00:01:02.720 --> 00:01:07.460 align:middle line:84%
sharing data is inevitable,
but it's oftentimes also

00:01:07.460 --> 00:01:09.750 align:middle line:84%
the most sensitive
part of the project.

00:01:09.750 --> 00:01:12.050 align:middle line:84%
This is because
every partner would

00:01:12.050 --> 00:01:16.770 align:middle line:84%
have something valuable and
proprietary to add to the work

00:01:16.770 --> 00:01:18.320 align:middle line:90%
so that it progresses.

00:01:18.320 --> 00:01:21.830 align:middle line:84%
The situation is
complicated even further

00:01:21.830 --> 00:01:25.740 align:middle line:90%
when industry is in the project.

00:01:25.740 --> 00:01:27.710 align:middle line:84%
This is because
potential leaks in data

00:01:27.710 --> 00:01:29.610 align:middle line:90%
can cost them millions of pounds.

00:01:29.610 --> 00:01:33.800 align:middle line:84%
So what I tend to do is,
when I store information,

00:01:33.800 --> 00:01:38.030 align:middle line:84%
I use secure repositories that
provide the maximum protection

00:01:38.030 --> 00:01:39.420 align:middle line:90%
that is available there.

00:01:39.420 --> 00:01:41.360 align:middle line:84%
And when I share
it, it's usually

00:01:41.360 --> 00:01:43.059 align:middle line:90%
via encrypted connections.

00:01:43.059 --> 00:01:50.100 align:middle line:90%


00:01:50.100 --> 00:01:53.640 align:middle line:84%
Regulations definitely
do exist, especially

00:01:53.640 --> 00:01:57.330 align:middle line:84%
when we talk about differences
between academia and industry.

00:01:57.330 --> 00:01:59.160 align:middle line:84%
In my experience,
these differences

00:01:59.160 --> 00:02:02.820 align:middle line:84%
would mainly be in terms of
again, data sharing, and access

00:02:02.820 --> 00:02:06.780 align:middle line:84%
to data or models,
and similar things.

00:02:06.780 --> 00:02:10.219 align:middle line:84%
However, in my practice,
this has never been an issue.