And once we have out of the edit and the lead job functionalities like I already mentioned earlier,
we'll actually switch gears and work on a stats page.
And once we're done with that, we'll swing back to all jobs and complete the search functionality now
for both the stats and the search form.
It would actually be very useful if we were to have more jobs since that way.
It's going to be easier to set up all of our upcoming functionalities like, for example, pagination,
the chat data.
Now, just to showcase that in the complete application for one of my dummy users, I created way more
jobs.
So in this case, I have 78.
I'm not where you can clearly see that nice imagination.
And I hope we will, paginated 10 jobs per page.
But I mean, the code is going to be there so you can always set up differently.
So let's say, if I navigate to page number four, then I display these jobs and hopefully you see where
I'm going.
And the same goes for stats.
Or technically, yeah, we can set it up with just three jobs.
So I was going to be pending interview and then declined.
But I think it just looks nicer if we have way more data, and it's definitely the case for charts where
it will display last six months.
So essentially how many applications we have sent out in the last six months, and this is the case
where I don't want to display just one job.
It's much more nicer if I have some actual data.
Now, since we have the add jam functionality, you can definitely add the manually one by one.
It is definitely an option, but I'm going to take a different route and instead I'm going to use the
site by the name of macro.
And yes, the link is in the read me so you can always navigate here.
And essentially, it's a place where you can get random data.
And what's really, really, really, really, really cool is the fact that you have tons of options
over here as far as the types, so you can get some nice data.
And also, it's very specific.
For example, we can add a date and time that matches exactly what we have in the Mongo DB.
This just makes our life way easier.
So once you navigate here, you'll see the screen and we'll start everything from scratch.
And here's what I'm trying to do.
So if we go back to the job on the model, these are properties that we're setting up.
So now what I want to do is set them up in the macro.
So make sure that the proper names are exact.
Otherwise, you'll get some errors and the setup is not going to work for you.
So one by one, let's add them up and I'm going to start over here by pretty much removing all of them.
And let's start with a company.
So I'm going to go here with the company.
When we click here on a type, I notice, like I said, you have tons of options over here now.
In my case, I'm going to go with fake and then company name.
So that is what I'm going to run and we're going to go with another field.
And I'm looking for position.
And here let's go for a job title.
I'm going to click on.
And then we go with job and then title, so we select this one then instead of the status, which I
believe is the next one, we're going to go with a job location and then we'll set up the statuses,
the job types and created by it just because we'll use the same thing when we use the custom list.
So I think it just makes a little bit more sense.
So we'll switch the order around.
So we're going to go with another field.
I'm looking for the job and then make sure that it's also capital because we'll be inserting this in
a database and I'll do that programmatically.
But still, the property names need to match.
Let me repeat that property names need to match.
So in this case, if it's job location, make sure that it's also the same over here.
And in here, we're looking for a city basically will get some.
Dummy values for two cities, one, let's go with another field, and this is the case where we use
that custom list because remember, we are using them.
So for the job that we have full time, part time remote and internship and those are the possible values.
Now they don't have this as their type and therefore in here we'll go with the job one type one.
Let's look for that custom list custom list.
And of course, I need to learn how to spell that custom list.
And then we just need to pass here the items.
Now one thing here is that we don't need to add those quotes.
So let me go back to the job type.
And first, I'm going to select that.
All right, but we have to remove those quotation marks.
At least that's what I was doing.
So I'm going to do the same thing right now as well.
So sure, there are no quotation marks.
And the same thing will do for status.
So let's add this one, and let's add another field.
And remember, we are going for status, still going to be a custom list.
But in this case, I'm looking for these values.
Vinyl copy and paste.
And same deal that's remove those marks one by one.
More than.
And once we have the status next up, we have the created by.
So that's the user that creates job because we still want to tie this to one user, since that is how
our application works.
And effectively, we'll do the same thing where we'll use the custom list.
But in this case, we'll just pass one value.
So all those jobs will be tied to that specific user the way we set it up.
First, I want to go back to the postman when I walk in, and once I'll do that, I'll get back my token.
And then I want to go back to all the drums.
Now this point, John has two jobs, and what I'm interested is the John's idea here.
So that's the one that we want to add in the macro.
So let's copy that one and add another field.
Remember, this is created and by custom list same deal.
And then we just copy this one value.
So now I'll be setting up those jobs with John's idea.
And lastly, I also want to add creative ad.
Now, why do I want to add that?
Well, because when it comes to the charts we are displaying here last six months.
So how many applications we send out in order to do that?
We need to have different dates.
So if I'm just going to create all those jobs at the same time, it's not going to make any sense.
I'm just going to have, I don't know whatever, 75 jobs with the same date.
And that's why we'll actually provide created that, which remember, is provided by the time stamps
just to showcase that.
Let's go back over here to the postman.
And you asked this creator that essentially this just means when the job was created.
Now what's really cool is the fact that when we're adding this programmatically, which we're going
to do in next video.
If we provide created out with the value, it will automatically set it up.
So even though we are creating that job right now, we can add, let's say, a past date to it.
Hopefully that makes sense.
And now let me go back to the mackerel and again, make sure that the field name is exactly the same.
So we're looking for creative that.
In this case, we're looking for a date.
So we're going to go here with date time and it's really up to you.
You can go with one year, but since there's going to be something that I want to showcase as far as
months and years in the mango, I'll actually go back.
I don't know.
Maybe two years.
So we're going to go here with 2019.
And then when it comes to format, we want to go here with this show.
And again, this is not cool thing where we actually can match exactly what the Mongo DB has.
So we're going to go here with our show.
And then when it comes to format, first of all, will go with John.
And then if you want, you can go a thousand lines, meaning thousand rows.
And essentially, that means that we will create those thousand jobs over here.
But in my case, am I going to do that?
Like I said, I'm going to be that drastic.
I'm going to go with just 75 and I'm not going to include values.
Least that's the option that I took.
Now we will download, but for the time being, I just want to preview what is going to be the result.
And essentially, this should look almost the same that we currently have in apportionment.
Where we have a company position, job, location, job type, status created by our childish values
of shame, and surely it is John's idea.
And when it was created.
And now notice how these values are different.
And once we have this one place, then we'll right away go with download data again.
You can do that in the previous screen, but we can also do it over here.
We download the data.
We get back.
MOC data, Jason.
And now let me navigate to my downloads.
And in here, I'm looking for Armonk data, but I will right away rename it.
Mark, we're going to go with mark and hyphen baydar.
That's just my preference when it comes to the naming.
And then we want to drag this sucker to our job before, and we want to place it in the road.
Since we'll use it in a server, we want to place road.
So let's get it over here and then navigate back to my project.
And as a side note, if you want to certify this, essentially if you want to see more powers, you
have just saved file, have a code automatically certify that.
So essentially, it's not going to be minified.
And if this is what you have in your project?
Awesome.
Now we're ready to move on to the next step.
Where will programmatically add them to our MongoDB database?