WEBVTT

00:00:01.694 --> 00:00:07.844 align:middle line:84%
OK, lab 1.3 is different
than lab 1.1 and 1.2.

00:00:07.844 --> 00:00:09.499 align:middle line:90%
It is manual.

00:00:09.499 --> 00:00:11.124 align:middle line:84%
There are different
ways of doing this.

00:00:11.124 --> 00:00:12.666 align:middle line:84%
And I'm going to
show you some tricks

00:00:12.666 --> 00:00:16.604 align:middle line:84%
after you write the query and
answer the questions on what

00:00:16.604 --> 00:00:18.124 align:middle line:90%
to do.

00:00:18.124 --> 00:00:21.434 align:middle line:84%
When you look at the
lab data for this--

00:00:21.434 --> 00:00:24.764 align:middle line:84%
so if we go to a Lab 1.3, you're
gaining experience with SQLite.

00:00:27.654 --> 00:00:29.484 align:middle line:84%
We tell you how
to load this file

00:00:29.484 --> 00:00:31.824 align:middle line:90%
into DB Browser for SQLite.

00:00:31.824 --> 00:00:34.714 align:middle line:84%
This file is called
CallHistory.storedata.

00:00:34.714 --> 00:00:37.389 align:middle line:84%
So if you don't change Select
All Files from the dropdown,

00:00:37.389 --> 00:00:38.514 align:middle line:90%
you're not going to see it.

00:00:38.514 --> 00:00:40.514 align:middle line:84%
You're going to think
it's missing from your lab

00:00:40.514 --> 00:00:41.244 align:middle line:90%
directory.

00:00:41.244 --> 00:00:44.514 align:middle line:84%
Apple names databases with
weird file extensions.

00:00:44.514 --> 00:00:47.034 align:middle line:84%
CallHistory.storedata
is the primary database

00:00:47.034 --> 00:00:52.899 align:middle line:84%
on iOS devices storing calls and
FaceTime, all the good things.

00:00:52.899 --> 00:00:54.274 align:middle line:84%
So what you're
going to do is you

00:00:54.274 --> 00:00:57.514 align:middle line:84%
are going to write a query
meeting these specific items

00:00:57.514 --> 00:00:58.954 align:middle line:90%
here.

00:00:58.954 --> 00:01:02.356 align:middle line:84%
If you get stuck, remember,
you can always copy and paste.

00:01:02.356 --> 00:01:03.814 align:middle line:84%
If you're, like,
I really can't get

00:01:03.814 --> 00:01:07.654 align:middle line:84%
it to work, copy this, and paste
it into DB Browser for SQLite,

00:01:07.654 --> 00:01:09.824 align:middle line:90%
and it will work.

00:01:09.824 --> 00:01:12.944 align:middle line:84%
Once you get your query, don't
get excited and celebrate.

00:01:12.944 --> 00:01:15.084 align:middle line:84%
You have to actually
do some analysis on it.

00:01:15.084 --> 00:01:17.024 align:middle line:84%
So we want you to
do some ordering,

00:01:17.024 --> 00:01:19.304 align:middle line:84%
some saying where
something exists,

00:01:19.304 --> 00:01:22.424 align:middle line:90%
all the different things.

00:01:22.424 --> 00:01:25.004 align:middle line:84%
We are now going
to review lab 1.3.

00:01:25.004 --> 00:01:29.234 align:middle line:84%
If you are not ready, simply
press pause on this recording,

00:01:29.234 --> 00:01:32.544 align:middle line:84%
and continue when you
are ready for the review.

00:01:32.544 --> 00:01:34.074 align:middle line:90%
I have open lab 1.3.

00:01:34.074 --> 00:01:35.784 align:middle line:84%
I'm going to start
with Browse Data.

00:01:35.784 --> 00:01:37.354 align:middle line:84%
And you can see
under ZCALLRECORD,

00:01:37.354 --> 00:01:40.174 align:middle line:90%
I have a lot of information.

00:01:40.174 --> 00:01:42.534 align:middle line:84%
So what I need to do is
start writing my query.

00:01:42.534 --> 00:01:44.424 align:middle line:84%
And what I like to
do is start, just

00:01:44.424 --> 00:01:54.394 align:middle line:84%
like I did before, with
SELECT star FROM ZCALLRECORD,

00:01:54.394 --> 00:01:55.294 align:middle line:90%
and I Play.

00:01:55.294 --> 00:01:57.424 align:middle line:84%
Now, the reason I
don't do one line--

00:01:57.424 --> 00:01:59.884 align:middle line:84%
and you're going to
see this as a habit--

00:01:59.884 --> 00:02:02.194 align:middle line:84%
you can actually copy
and paste your query

00:02:02.194 --> 00:02:03.784 align:middle line:84%
into a tool like
Physical Analyzer,

00:02:03.784 --> 00:02:08.164 align:middle line:84%
and it would say error
line 10 position 18.

00:02:08.164 --> 00:02:10.954 align:middle line:84%
So then you scroll, and you're,
like, oh, I have a comma.

00:02:10.954 --> 00:02:13.204 align:middle line:84%
Or this, if you put
everything in one line,

00:02:13.204 --> 00:02:16.414 align:middle line:84%
it's going to say error
line 1, position 342--

00:02:16.414 --> 00:02:17.774 align:middle line:90%
not ideal.

00:02:17.774 --> 00:02:19.894 align:middle line:84%
So I like to have
it just clean so

00:02:19.894 --> 00:02:22.054 align:middle line:84%
I can also look at the
colorization in kind

00:02:22.054 --> 00:02:24.699 align:middle line:90%
of a line going down.

00:02:24.699 --> 00:02:26.074 align:middle line:84%
Now what we need
to do is we need

00:02:26.074 --> 00:02:28.424 align:middle line:84%
to follow what the lab
is telling us to do.

00:02:28.424 --> 00:02:32.134 align:middle line:84%
So what do we want it
to identify for us?

00:02:32.134 --> 00:02:34.144 align:middle line:84%
As we look, keep
in mind if this is

00:02:34.144 --> 00:02:36.394 align:middle line:84%
about to make you uncomfortable
with what we're doing,

00:02:36.394 --> 00:02:38.061 align:middle line:84%
just copy and paste
from the e-workbook.

00:02:38.061 --> 00:02:39.214 align:middle line:90%
That's what it's there for.

00:02:39.214 --> 00:02:41.914 align:middle line:84%
So the lab is telling
you, you want z_pk.

00:02:41.914 --> 00:02:43.444 align:middle line:84%
We want the primary
key because this

00:02:43.444 --> 00:02:46.922 align:middle line:84%
is a key way we can
detect deletion,

00:02:46.922 --> 00:02:49.464 align:middle line:84%
and that will make more sense
to you as the course continues.

00:02:49.464 --> 00:02:52.204 align:middle line:84%
So zaddress-- and I forgot
the z in front of it.

00:02:55.204 --> 00:03:00.814 align:middle line:84%
We need FROM
ZCALLRECORD no comma.

00:03:00.814 --> 00:03:01.594 align:middle line:90%
Excellent.

00:03:01.594 --> 00:03:04.964 align:middle line:84%
So now we have a little
bit of information here.

00:03:04.964 --> 00:03:06.754 align:middle line:84%
Now we want to keep
adding onto it.

00:03:06.754 --> 00:03:10.339 align:middle line:84%
Under zaddress, I'm
going to add ZORIGINATED.

00:03:13.534 --> 00:03:17.264 align:middle line:84%
And you'll notice capitalization
and such do not matter.

00:03:17.264 --> 00:03:26.924 align:middle line:84%
ZDURATION and
ZANSWERED no comma--

00:03:26.924 --> 00:03:29.484 align:middle line:90%
now we have additional columns.

00:03:29.484 --> 00:03:29.984 align:middle line:90%
Excellent.

00:03:29.984 --> 00:03:32.694 align:middle line:90%
Things are going well.

00:03:32.694 --> 00:03:34.244 align:middle line:90%
So now we want to do the date.

00:03:34.244 --> 00:03:38.604 align:middle line:90%
So we're going to add zdate.

00:03:43.904 --> 00:03:46.604 align:middle line:84%
And if I could quiz
you, it starts with 4.

00:03:46.604 --> 00:03:47.894 align:middle line:90%
Some of them start with 5.

00:03:47.894 --> 00:03:49.484 align:middle line:90%
It's a Mac datetime stamp.

00:03:49.484 --> 00:03:51.974 align:middle line:90%
Also, it's from an Apple device.

00:03:51.974 --> 00:03:55.121 align:middle line:84%
Now, keep in mind, Apple will
use Unix Epoch datetime stamps.

00:03:55.121 --> 00:03:56.954 align:middle line:84%
That's very important
that you realize that.

00:03:56.954 --> 00:03:58.994 align:middle line:84%
A lot of the third-party
apps will as well.

00:03:58.994 --> 00:04:01.544 align:middle line:84%
Apple native apps
will do it too.

00:04:01.544 --> 00:04:03.884 align:middle line:84%
So don't assume that every
single thing recovered

00:04:03.884 --> 00:04:06.434 align:middle line:84%
from an iPhone is going to
be a Mac datetime stamp.

00:04:06.434 --> 00:04:10.574 align:middle line:84%
You will see the 14,
15, 16, and so on.

00:04:10.574 --> 00:04:13.302 align:middle line:84%
You will not see Mac datetime
stamps on any Android ever.

00:04:13.302 --> 00:04:14.594 align:middle line:90%
If you do, that's really weird.

00:04:14.594 --> 00:04:17.254 align:middle line:90%
That does not belong.

00:04:17.254 --> 00:04:21.464 align:middle line:84%
OK, so now what we have to do,
let's convert this datetime.

00:04:21.464 --> 00:04:26.064 align:middle line:84%
So I'm going to do
datetime, zdate.

00:04:26.064 --> 00:04:33.524 align:middle line:84%
And the magic math, 978307200
comma single tick unixepoch,

00:04:33.524 --> 00:04:39.669 align:middle line:90%
single tick as date.

00:04:42.704 --> 00:04:43.364 align:middle line:90%
Beautiful.

00:04:43.364 --> 00:04:44.674 align:middle line:90%
We have timestamps now.

00:04:44.674 --> 00:04:46.987 align:middle line:90%
Excellent.

00:04:46.987 --> 00:04:48.904 align:middle line:84%
And if you wanted to do
local time, you could.

00:04:48.904 --> 00:04:50.764 align:middle line:90%
I'm keeping with UTC in the VM.

00:04:50.764 --> 00:04:53.384 align:middle line:84%
So if any of my timestamps
just look slightly different,

00:04:53.384 --> 00:04:55.127 align:middle line:90%
that's why.

00:04:55.127 --> 00:04:56.794 align:middle line:84%
And now we have to
rename these columns.

00:04:56.794 --> 00:04:58.754 align:middle line:84%
You should do what
makes sense to you.

00:04:58.754 --> 00:05:00.454 align:middle line:84%
So if mine differ
from the lab, I'm

00:05:00.454 --> 00:05:01.912 align:middle line:84%
just telling you
how I would do it.

00:05:01.912 --> 00:05:05.549 align:middle line:90%
Primary key AS from.

00:05:08.424 --> 00:05:11.284 align:middle line:84%
Now ZORIGINATED, this is where
this gets a little tricky.

00:05:11.284 --> 00:05:13.794 align:middle line:84%
We tell you in the
lab what it means.

00:05:13.794 --> 00:05:17.754 align:middle line:84%
We say, if ZORIGINATED
equals o, then it's incoming.

00:05:17.754 --> 00:05:19.374 align:middle line:90%
If it's 1, it's outgoing.

00:05:19.374 --> 00:05:26.734 align:middle line:84%
So I'm going to call this
ZORIGINATED AS 0 equals

00:05:26.734 --> 00:05:32.544 align:middle line:90%
incoming; 1 equals outgoing.

00:05:35.974 --> 00:05:38.774 align:middle line:84%
And I like to do Control-Enter
a few times to see how it looks.

00:05:38.774 --> 00:05:40.744 align:middle line:90%
OK.

00:05:40.744 --> 00:05:45.314 align:middle line:84%
ZDURATION here, this is going
to be duration in seconds.

00:05:45.314 --> 00:05:50.284 align:middle line:84%
So what I like to do is, I
would say Duration in Seconds,

00:05:50.284 --> 00:05:51.924 align:middle line:90%
so the person knows.

00:05:51.924 --> 00:05:54.984 align:middle line:84%
If it steps, in
meters, steps in feet--

00:05:54.984 --> 00:05:57.394 align:middle line:84%
include as much
information as you can.

00:05:57.394 --> 00:06:02.244 align:middle line:84%
And then for ZANSWERED, if it's
0, it is missed, if it's 1,

00:06:02.244 --> 00:06:04.114 align:middle line:90%
it is answered.

00:06:04.114 --> 00:06:09.339 align:middle line:84%
So 0 equals missed;
1 equals answered.

00:06:12.484 --> 00:06:15.304 align:middle line:84%
Now, you may look at this and
be, like, excellent; I am done.

00:06:15.304 --> 00:06:16.504 align:middle line:90%
No.

00:06:16.504 --> 00:06:19.794 align:middle line:84%
I want you to take
this a step further.

00:06:19.794 --> 00:06:21.944 align:middle line:90%
I want you to make this pretty.

00:06:21.944 --> 00:06:22.784 align:middle line:90%
Where?

00:06:22.784 --> 00:06:24.054 align:middle line:90%
I say this.

00:06:24.054 --> 00:06:27.744 align:middle line:84%
If you have thousands, and you
export this to a spreadsheet,

00:06:27.744 --> 00:06:30.374 align:middle line:84%
how many people are going to
remember that 1 or 0 equals

00:06:30.374 --> 00:06:31.599 align:middle line:90%
incoming or outgoing?

00:06:31.599 --> 00:06:33.224 align:middle line:84%
Wouldn't it be better
if it didn't even

00:06:33.224 --> 00:06:36.434 align:middle line:84%
have a typo like
outoing and said a word?

00:06:36.434 --> 00:06:39.557 align:middle line:90%
So I'm going to fix this.

00:06:39.557 --> 00:06:41.724 align:middle line:84%
First, I'm going to switch
this so it says outgoing.

00:06:44.381 --> 00:06:46.714 align:middle line:84%
And what I want to do is I
want to add a CASE statement.

00:06:46.714 --> 00:06:58.754 align:middle line:84%
So I'm going to say CASE when
ZORIGINATED equals 0, then

00:06:58.754 --> 00:06:59.254 align:middle line:90%
Incoming.

00:07:02.074 --> 00:07:10.856 align:middle line:84%
When ZORIGINATED
equals 1 then Outgoing.

00:07:10.856 --> 00:07:12.314 align:middle line:84%
And then you have
to end it, so I'm

00:07:12.314 --> 00:07:17.234 align:middle line:84%
going to say end
AS Call Direction.

00:07:21.884 --> 00:07:23.384 align:middle line:84%
And do you notice
how it has both.

00:07:23.384 --> 00:07:25.934 align:middle line:84%
It has the old, ugly way
and now the pretty way.

00:07:25.934 --> 00:07:30.414 align:middle line:84%
You can verify, OK, 0 is
incoming, one is outgoing,

00:07:30.414 --> 00:07:34.724 align:middle line:84%
and then get rid of the one
that is no longer needed.

00:07:34.724 --> 00:07:36.964 align:middle line:90%
That looks a lot better.

00:07:36.964 --> 00:07:39.914 align:middle line:84%
Let's do the same
thing with answered.

00:07:39.914 --> 00:07:46.894 align:middle line:84%
So I'm going to do CASE when
ZANSWERED equals 0, then

00:07:46.894 --> 00:07:49.754 align:middle line:90%
Missed.

00:07:49.754 --> 00:07:58.404 align:middle line:84%
When ZANSWERED equals
1, then Answered.

00:07:58.404 --> 00:08:03.702 align:middle line:90%
End AS Call Status, maybe?

00:08:03.702 --> 00:08:05.244 align:middle line:84%
I don't know what
we want to call it.

00:08:08.384 --> 00:08:10.544 align:middle line:90%
Comma, now you have that.

00:08:10.544 --> 00:08:11.414 align:middle line:90%
You verify.

00:08:11.414 --> 00:08:14.004 align:middle line:84%
You get rid of the
one that is ugly,

00:08:14.004 --> 00:08:18.174 align:middle line:84%
and now you have a lovely
query to work with.

00:08:18.174 --> 00:08:20.294 align:middle line:90%
It's not done, though.

00:08:20.294 --> 00:08:22.604 align:middle line:84%
Now we have to do some
additional things.

00:08:22.604 --> 00:08:24.584 align:middle line:90%
Now, what I want to show you--

00:08:24.584 --> 00:08:26.684 align:middle line:84%
and I mentioned
this just briefly--

00:08:26.684 --> 00:08:41.444 align:middle line:84%
if I do order by PK ascending,
you want to look for gaps.

00:08:41.444 --> 00:08:42.914 align:middle line:90%
What happened to 1?

00:08:42.914 --> 00:08:45.764 align:middle line:90%
What happened to 4 through 13?

00:08:45.764 --> 00:08:48.674 align:middle line:84%
That's a good way to know
the user deleted call logs.

00:08:48.674 --> 00:08:50.911 align:middle line:84%
And that is coming
in this course.

00:08:50.911 --> 00:08:52.994 align:middle line:84%
That's not what you're
expected to know right now.

00:08:52.994 --> 00:08:55.634 align:middle line:84%
But that is why I always
include that primary key.

00:08:55.634 --> 00:08:57.194 align:middle line:84%
It's a number one
example to show

00:08:57.194 --> 00:09:00.674 align:middle line:84%
you gaps in calls
or any database

00:09:00.674 --> 00:09:02.841 align:middle line:90%
on things that could be missing.

00:09:02.841 --> 00:09:04.674 align:middle line:84%
OK, so now we have to
answer some questions.

00:09:04.674 --> 00:09:05.634 align:middle line:90%
We did our query.

00:09:05.634 --> 00:09:06.834 align:middle line:90%
Everything is great.

00:09:06.834 --> 00:09:10.224 align:middle line:84%
So we need to know which
call log lasted the longest.

00:09:10.224 --> 00:09:24.844 align:middle line:84%
So I'm going to change this to
order by Duration in Seconds

00:09:24.844 --> 00:09:26.514 align:middle line:90%
descending.

00:09:26.514 --> 00:09:29.004 align:middle line:84%
And we can see we have one
that is 21 seconds in length.

00:09:32.244 --> 00:09:34.224 align:middle line:84%
And the next one, how
many incoming calls

00:09:34.224 --> 00:09:37.684 align:middle line:84%
were on the device, and how
many of those were answered?

00:09:37.684 --> 00:09:39.714 align:middle line:84%
So I'm going to do a
different order by.

00:09:39.714 --> 00:09:48.694 align:middle line:84%
I'm going to do order by
ZORIGINATED ascending comma

00:09:48.694 --> 00:09:51.522 align:middle line:90%
ZANSWERED descending.

00:09:51.522 --> 00:09:52.564 align:middle line:90%
Let's see how this works.

00:09:55.194 --> 00:09:56.274 align:middle line:90%
It did not like that.

00:09:56.274 --> 00:10:00.244 align:middle line:84%
Oh, I have a quote there
that does not make sense.

00:10:00.244 --> 00:10:03.654 align:middle line:90%
It made everything very unhappy.

00:10:03.654 --> 00:10:05.814 align:middle line:84%
OK, so now when I
zoom out, we can

00:10:05.814 --> 00:10:08.799 align:middle line:90%
see we have 42 calls in total.

00:10:13.314 --> 00:10:17.747 align:middle line:84%
We can see that 39 of
them-- now, remember,

00:10:17.747 --> 00:10:19.414 align:middle line:84%
you're not looking
at PK, you're looking

00:10:19.414 --> 00:10:20.524 align:middle line:90%
at this number over here.

00:10:20.524 --> 00:10:27.421 align:middle line:84%
39 of them are incoming,
and only three of those

00:10:27.421 --> 00:10:28.004 align:middle line:90%
were answered.

00:10:33.614 --> 00:10:37.794 align:middle line:84%
You could also do
order by ZORIGINATED,

00:10:37.794 --> 00:10:42.114 align:middle line:84%
or you could do where
Call Status is Answered.

00:10:42.114 --> 00:10:43.534 align:middle line:84%
There's so many
things you can do.

00:10:43.534 --> 00:10:45.754 align:middle line:90%
There's no right or wrong.

00:10:45.754 --> 00:10:48.834 align:middle line:84%
And then, what is the date and
time for the last outgoing call

00:10:48.834 --> 00:10:50.094 align:middle line:90%
made on the device?

00:10:50.094 --> 00:10:56.014 align:middle line:84%
So I'm going to do order by
the ZDATE, or just "Date"

00:10:56.014 --> 00:10:59.844 align:middle line:90%
in quotes, descending.

00:11:02.844 --> 00:11:07.074 align:middle line:84%
And what we're looking
for is outgoing call.

00:11:07.074 --> 00:11:09.844 align:middle line:90%
And we see 2/21 at 15:56.

00:11:09.844 --> 00:11:11.844 align:middle line:84%
So be careful that you
wouldn't choose incoming.

00:11:11.844 --> 00:11:15.004 align:middle line:84%
We're actually
asking for this one.

00:11:15.004 --> 00:11:17.284 align:middle line:84%
And I'm sure many of you
did many different things

00:11:17.284 --> 00:11:18.634 align:middle line:90%
in this lab.

00:11:18.634 --> 00:11:20.947 align:middle line:84%
Something that people always
want to do is try to--

00:11:20.947 --> 00:11:22.364 align:middle line:84%
like, oh, I hope
Heather zooms in,

00:11:22.364 --> 00:11:23.554 align:middle line:90%
so I can take a picture of that.

00:11:23.554 --> 00:11:24.304 align:middle line:90%
You don't have to.

00:11:24.304 --> 00:11:26.324 align:middle line:84%
This is in your
notebook for you.

00:11:26.324 --> 00:11:30.634 align:middle line:84%
So any time I could include a
CASE statement for you, I did.

00:11:30.634 --> 00:11:33.124 align:middle line:84%
You will see sometimes I
may name columns, things

00:11:33.124 --> 00:11:34.804 align:middle line:90%
that you don't like the name.

00:11:34.804 --> 00:11:36.724 align:middle line:84%
Or you may find that
you want something else.

00:11:36.724 --> 00:11:39.004 align:middle line:84%
Like a good example,
if you had this,

00:11:39.004 --> 00:11:41.914 align:middle line:84%
you may look and say, why
didn't she include ZLOCATION?

00:11:41.914 --> 00:11:42.904 align:middle line:90%
I want that.

00:11:42.904 --> 00:11:43.522 align:middle line:90%
Add it.

00:11:43.522 --> 00:11:45.064 align:middle line:84%
No one's stopping
you from adding it.

00:11:45.064 --> 00:11:54.724 align:middle line:84%
All you would have to do is
say ZLOCATION AS Location.

00:11:54.724 --> 00:11:59.844 align:middle line:84%
And now you have the location of
where the call took place from.

00:11:59.844 --> 00:12:03.754 align:middle line:84%
So here we can see the
location of these items.

00:12:03.754 --> 00:12:06.134 align:middle line:84%
It's pretty cool
what you can do.

00:12:06.134 --> 00:12:08.144 align:middle line:84%
OK, now I want to show
you something else.

00:12:08.144 --> 00:12:11.614 align:middle line:84%
This is my preferred way
of working in this lab.

00:12:11.614 --> 00:12:12.614 align:middle line:90%
I'm going to Close this.

00:12:15.314 --> 00:12:20.064 align:middle line:84%
I am going to open
Physical Analyzer

00:12:20.064 --> 00:12:24.294 align:middle line:84%
and show you one of the pros
of the SQLite Query Builder

00:12:24.294 --> 00:12:27.194 align:middle line:84%
that I did want to show
you earlier because you

00:12:27.194 --> 00:12:28.724 align:middle line:90%
have to earn easier things.

00:12:28.724 --> 00:12:30.824 align:middle line:90%
I personally do not use this.

00:12:30.824 --> 00:12:33.704 align:middle line:84%
Yes, I work at Cellebrite,
I prefer the DB Browser

00:12:33.704 --> 00:12:35.684 align:middle line:90%
that Ihad just shown you.

00:12:35.684 --> 00:12:38.324 align:middle line:84%
I stressed to Magnet so many
times that I prefer the DB

00:12:38.324 --> 00:12:40.304 align:middle line:90%
Browser that they also agreed.

00:12:40.304 --> 00:12:43.544 align:middle line:84%
And you can export straight
from axiom into DB Browser

00:12:43.544 --> 00:12:45.894 align:middle line:90%
instead of staying in the tool.

00:12:45.894 --> 00:12:49.194 align:middle line:84%
But what I'm about to show
you is a unique capability

00:12:49.194 --> 00:12:54.014 align:middle line:84%
that you can do in Oxygen as
well as Physical Analyzer.

00:12:54.014 --> 00:12:55.484 align:middle line:84%
I think you can do
it in AXIOM too;

00:12:55.484 --> 00:12:58.631 align:middle line:90%
it's just slightly different.

00:12:58.631 --> 00:13:00.964 align:middle line:84%
And how I'm going to load--
this is going to look weird.

00:13:00.964 --> 00:13:10.524 align:middle line:84%
I'm going to say File, Open
Case, Add, Common Source,

00:13:10.524 --> 00:13:12.682 align:middle line:90%
Storage Device, SD Card.

00:13:12.682 --> 00:13:14.974 align:middle line:84%
Now, this is weird because
that's not what we're doing.

00:13:14.974 --> 00:13:17.154 align:middle line:84%
But this is one of the few
that give you the option

00:13:17.154 --> 00:13:19.684 align:middle line:90%
to just select a folder.

00:13:19.684 --> 00:13:24.494 align:middle line:84%
I'm going to go
out to G, lab 1.3,

00:13:24.494 --> 00:13:27.759 align:middle line:84%
and I'm going to
select that folder.

00:13:27.759 --> 00:13:29.134 align:middle line:84%
It's not going to
parse anything.

00:13:29.134 --> 00:13:31.191 align:middle line:84%
I'm just going to
say Examine Data.

00:13:31.191 --> 00:13:32.649 align:middle line:84%
And it should take
a second to run.

00:13:37.024 --> 00:13:38.644 align:middle line:84%
This trick that
Ihad just shown you

00:13:38.644 --> 00:13:42.791 align:middle line:84%
is a great way to get any
folder into Physical Analyzer.

00:13:42.791 --> 00:13:44.374 align:middle line:84%
You will see that
you're going to have

00:13:44.374 --> 00:13:47.314 align:middle line:84%
to do this in section 5 a
lot because we take away

00:13:47.314 --> 00:13:48.356 align:middle line:90%
all the tools from you.

00:13:48.356 --> 00:13:50.564 align:middle line:84%
And you'll look at it and
be, like, what do I do now?

00:13:50.564 --> 00:13:52.034 align:middle line:90%
Well, you have a database.

00:13:52.034 --> 00:13:53.584 align:middle line:90%
So let's look at that database.

00:13:57.384 --> 00:14:03.804 align:middle line:84%
So I am going to say, I want to
open this in the SQLite Wizard.

00:14:03.804 --> 00:14:05.334 align:middle line:90%
I'm not even going to name it.

00:14:05.334 --> 00:14:07.104 align:middle line:84%
You can watch all
my Tip Tuesdays

00:14:07.104 --> 00:14:09.312 align:middle line:84%
and Ask the Expert if you
want to see how to name it.

00:14:09.312 --> 00:14:12.254 align:middle line:90%
I just want to show you a trick.

00:14:12.254 --> 00:14:13.724 align:middle line:90%
You click on ZCALLRECORD.

00:14:13.724 --> 00:14:16.484 align:middle line:84%
That table comes
over to the middle.

00:14:16.484 --> 00:14:18.484 align:middle line:84%
Something else I learned,
even though this is so

00:14:18.484 --> 00:14:21.584 align:middle line:84%
grayed out, it makes no
sense, if you click on it,

00:14:21.584 --> 00:14:23.014 align:middle line:90%
it actually works.

00:14:23.014 --> 00:14:26.224 align:middle line:84%
And what it does is it makes
the table smaller so that you

00:14:26.224 --> 00:14:27.574 align:middle line:90%
can see more things to check.

00:14:27.574 --> 00:14:29.574 align:middle line:84%
But it's kind of blurring
the view a little bit,

00:14:29.574 --> 00:14:30.814 align:middle line:90%
and I don't love that.

00:14:30.814 --> 00:14:34.144 align:middle line:84%
But I'm going to say Z_PK,
I'm going to checkbox this--

00:14:34.144 --> 00:14:43.384 align:middle line:84%
ZANSWERED, ZCALLTYPE,
ZORIGINATED, ZDATE, and I'm

00:14:43.384 --> 00:14:45.814 align:middle line:90%
going to click Preview.

00:14:45.814 --> 00:14:48.154 align:middle line:84%
And this is where people are,
like, are you kidding me?

00:14:48.154 --> 00:14:49.184 align:middle line:90%
There's all the answers.

00:14:49.184 --> 00:14:51.479 align:middle line:84%
So now what I need
to do is get--

00:14:51.479 --> 00:14:55.007 align:middle line:90%
let me Enlarge this.

00:14:55.007 --> 00:14:55.674 align:middle line:90%
What do we need?

00:14:55.674 --> 00:14:56.174 align:middle line:90%
ZNAME.

00:14:58.854 --> 00:15:01.224 align:middle line:84%
And let's run ZLOCATION because
I did like that one too.

00:15:01.224 --> 00:15:04.494 align:middle line:90%
And then we do Preview.

00:15:04.494 --> 00:15:05.334 align:middle line:90%
It was not ZNAME.

00:15:13.054 --> 00:15:13.554 align:middle line:90%
ZADDRESS?

00:15:16.854 --> 00:15:17.769 align:middle line:90%
Yes, there we go.

00:15:17.769 --> 00:15:18.894 align:middle line:90%
I want to get rid of ZNAME.

00:15:18.894 --> 00:15:19.894 align:middle line:90%
I'm going to Uncheck it.

00:15:24.494 --> 00:15:27.374 align:middle line:84%
So now you can see all of the
information at the bottom.

00:15:27.374 --> 00:15:28.544 align:middle line:90%
Now, what you can do--

00:15:28.544 --> 00:15:30.044 align:middle line:84%
and this is where people
usually get mad at me.

00:15:30.044 --> 00:15:31.614 align:middle line:84%
They're like, are
you kidding me?

00:15:31.614 --> 00:15:33.164 align:middle line:90%
You can rename it right here.

00:15:33.164 --> 00:15:50.229 align:middle line:84%
You can say PK Call
Status, Call Type--

00:15:50.229 --> 00:15:51.854 align:middle line:84%
I don't know what
you want to call it--

00:15:51.854 --> 00:15:54.834 align:middle line:90%
whatever you want to call it.

00:15:54.834 --> 00:15:56.504 align:middle line:84%
Oh, I know we're
missing ZDURATION.

00:16:08.097 --> 00:16:09.764 align:middle line:84%
I have to make this
a little bit larger.

00:16:09.764 --> 00:16:12.274 align:middle line:90%
I can't even see it.

00:16:12.274 --> 00:16:15.024 align:middle line:90%
There we go.

00:16:15.024 --> 00:16:15.774 align:middle line:90%
I can say Preview.

00:16:15.774 --> 00:16:19.284 align:middle line:84%
And you'll notice it starts
renaming them as I did that.

00:16:19.284 --> 00:16:21.009 align:middle line:90%
ZDATE, we can call it just Date.

00:16:25.144 --> 00:16:27.004 align:middle line:84%
Location-- and
you get the point.

00:16:27.004 --> 00:16:31.724 align:middle line:84%
It's making it pretty
without having to go through

00:16:31.724 --> 00:16:32.814 align:middle line:90%
and manually do all of it.

00:16:32.814 --> 00:16:34.814 align:middle line:84%
So it's doing all these
things, and the address,

00:16:34.814 --> 00:16:35.489 align:middle line:90%
we can do From.

00:16:41.044 --> 00:16:43.039 align:middle line:84%
And you could do
Duration in Seconds.

00:16:46.304 --> 00:16:47.884 align:middle line:90%
So now we have all that.

00:16:47.884 --> 00:16:49.624 align:middle line:90%
So it looks nice and pretty.

00:16:49.624 --> 00:16:52.144 align:middle line:90%
Now, Call Type, Call Status--

00:16:52.144 --> 00:16:54.386 align:middle line:84%
you could also clean
that up right here.

00:16:54.386 --> 00:16:55.594 align:middle line:90%
You could say, you know what?

00:16:55.594 --> 00:16:58.934 align:middle line:84%
I want to do a CASE statement,
and I want to write it here.

00:16:58.934 --> 00:17:03.064 align:middle line:84%
You could also do your
date timestamp conversion

00:17:03.064 --> 00:17:03.564 align:middle line:90%
right here.

00:17:03.564 --> 00:17:07.792 align:middle line:84%
Or what you can
do is press Next,

00:17:07.792 --> 00:17:09.584 align:middle line:84%
and you're going to
get these options here.

00:17:09.584 --> 00:17:11.054 align:middle line:84%
You can choose
from these models.

00:17:11.054 --> 00:17:15.034 align:middle line:84%
If you're like, OK, I
think this is a call log,

00:17:15.034 --> 00:17:16.954 align:middle line:84%
and you could say
this is a timestamp.

00:17:16.954 --> 00:17:18.824 align:middle line:84%
You drag it in, and
it's going to say, hey,

00:17:18.824 --> 00:17:20.434 align:middle line:90%
this is what I think it is.

00:17:20.434 --> 00:17:25.554 align:middle line:84%
I think this is going to be
the number of seconds UTC.

00:17:28.566 --> 00:17:30.524 align:middle line:84%
And you're, like, yeah,
that's a Mac timestamp,

00:17:30.524 --> 00:17:33.126 align:middle line:84%
and it's going to
fix it for you.

00:17:33.126 --> 00:17:34.834 align:middle line:84%
So there are so many
things you could do.

00:17:34.834 --> 00:17:36.424 align:middle line:90%
This is a different way.

00:17:36.424 --> 00:17:38.224 align:middle line:84%
It's not my preferred
way, but if it

00:17:38.224 --> 00:17:40.834 align:middle line:84%
makes you more comfortable to
sit there and check the boxes

00:17:40.834 --> 00:17:42.467 align:middle line:90%
until you learn, awesome.

00:17:42.467 --> 00:17:44.884 align:middle line:84%
Do what makes sense for you,
so you can take the most away

00:17:44.884 --> 00:17:45.592 align:middle line:90%
from this course.
