review and edit the following notes took during a meeting with the product owner and developers:

Agenda

Challenge 1: Job metrics via API A recruiter who uses the Job poster API i.c.w. PBP currently does not know how its jobs are performing (Progression in a way). Recruiter must have at least the following information: Number of views Number of clicks on job Number of applications completed Budget (per vacancy)

Challenge 2:. PBP jobs older than 60 days When a PBP job is older than 60 days, the recruiter currently has to go through a manual process to copy the contents of the job and then use it in a new job. This method is not workable for larger quantities of PBP jobs that need to be online longer than 60 days.

Challenge 3: Migration vacancies NAME_1 has tested the new Job poster API and indicates that everything works for you. They wonder how we will handle migrating the jobs that are currently posted via the old Multiposter API. How can we migrate this efficiently?


Discussions


Challenge 1:

We will return the metrics in the summary endpoint

We will only return the remaining budget.

Budget will come from the job-manager, other data will come from the reporting-service.

We should return the metrics in the summary endpoint adding all the metrics in the response.

We discussed the possibility of Deleted jobs being handled in a later phase. But NAME_2 suggested creating a new projection for the Summary endpoint, and then delete jobs from the projection after X months. (X to be defined). So we decided to go with the projection idea.

For Challenge 2:

We proposed posting the same job again or duplicating it. We decided to NAME_3 this one for now as this is a complex challenge.


For Challenge 3:

We don’t know yet how many jobs need to migrate. NAME_4 is going to get more information about the migration.

We will have a meeting with NAME_5 to discuss the requirements.

Challenge 3 is the most important/urgent one.

 The letter m should appear at least 6 times.
user