Thread: Database Structure JobRoller

Database Structure JobRoller

Hi, I am looking at JobRoller as a solution for a recruitment agency client, but the admin tools aren't sufficient in their requirements for searching and managing candidates. Can you advise the rough schema/db structure so I can see if it is feasible for us to buy JR and use for the front end, but develop our own phpapp to handle 'backoffice' functions and manage candidates/CV's. Paticularly interested in how many tables there are to store jobs, candidates and resumes and how many joins etc. Is it a relatively flat structure with a table for each?

Many thanks.

And also I would be grateful if you could advise whether records can just be inserted straight (directly) into the DB (resumes, users, employers, jobs) without breaking the front end - or whether it's a bit more complicated than that?

JobRoller uses it's own tables only for storing job packs, job alerts and orders, the rest is managed by the WP database. If you were to import data directly via the database side, you would firstly need to import all your posts and users to WP tables ('wp_posts' and 'wp_users'). After having this data imported, you will need to update the post type of your posts to 'job_listing' using an MySQL Update. From there you should be able to update all the additional data directly from the backend or frontend (custom fields, user roles, etc...). Thanks.

Thanks Pepsi. So basically if I wrote an app (or say used a MySQL query editor) to INSERT and UPDATE jobs, resumes, users and applications then there is no reason why this would not break the front end and any changed data would be updated in the front end. To maintain continuity between the frontend and our new 'backend' then we're planning to use existing JR/WP tables for all the jobroller content - and just create additional tables for any additional information to be captured in the backend. Does this sound like it would work to you? If so I can go ahead and get my client to purchase :-)
Also while I am here - can you confirm if the Eva theme is responsive yet? Thanks again!

As long as you've done things right at your end then it should work fine. We have had customers who have done the same kind of thing in the past with our other theme, ClassiPress before the .csv importer was implemented (i.e. they had an existing Classifieds site they wanted to migrate data over to ClassiPress and imported the ads from the database side).. This kind of thing is ultimately outside the scope of what we officially support, but if you've got the ability to do this then there's no reason why it shouldn't work.

The Eva child theme is not a product created by AppThemes, so you can communicate directly with the developer on the Marketplace page for the product here in the comments section if you wish, however there does appear to be a recent comment regarding responsiveness. Thanks.