By kaizerking on
1.I have a content type job_per_template a recruiter creates jobs using term reference fields
2.I have applicants who have created profile2 profile using the term reference fields using the same vocabulary.(I dont know if it advantageous to use same fields if it is, i'll use same fields if required)
3. I want to create a view listing all the jobs matching applicant's profile.
I am trying to use contextual filters, But there is not enough help docs I could read and do
can some one help please?
Comments
no option to attach the exported view:(
There is no option to attach the exported view which i tried to create
any help please
any help please
help requests
kaiserking, as a general rule of thumb you should wait at least 24 hrs before asking your help requests again. Most people will ignore them if you keep impatiently posting. All the same,
There is an excellent, extensive, and in-depth screencast series on the views module at http://vimeo.com/21051899. The series is long, but you should be able to figure out what you need from it.
Thank you for your valuable advice but that doesnt solve my prob
I went through all those video tutorials, what is not covered in them is how to use a joined (through relations) table field as filter to filter nodes could you please help, I have create all the view structure and selected the contextual filters, It seems you have every good knowledge about this can you please help me? I can share login details to my site if you can , i have been trying to get this thing work for long time
I'm flattered that you think
I'm flattered that you think that I "have every good knowledge about this." Based on your profile, you've been using drupal much longer than I have. I'm not really an expert, but I'm willing to try to help.
So, I'm trying to understand. Do you need the job view to
a) automatically load only the jobs that match the resume
b) allow users to search through the jobs
c) forbid users to even see jobs that do not match their resume
I can show you how to do b) pretty easily. I would have to research how to do a) or c). They might require another module. Let me know what you need.
a and c are true
Exactly
1. the job list view will have only jobs that match resume Term reference fields
2. I already have this with Search APi, I am disabling it intentionally, I know that is pretty easy using exposed filters.I do not want search facility, means search is not allowed
3. forbid users to even see jobs that do not match their resume, Yes
once I get this view i am planning to use 'rabit hole' module or 'Restrict node page view access' module to prevent users accessing the nodes through URL change
We have a helper module Taxonomy Entity Index to get all the term reference fields in to one table it also supports view
Options i have to achieve my requirement:
1.Term Access module
Advantages:This module is the best and simple and can be manged per content type
Why I cant use:
a)This only supports core profile doesn't support profile2 issue has been created there is no reply from maintainers,How ever maintainer says it can be implemented to match any term reference field of entity type with term reference field of any entity type
b)Both the users(roles) should have the term reference field, in my case recruiter will not have profile at all
2.ABT(Access By Term module
No advantage this controls access per field i.e settings are done at term reference field
Why I cant use:
a)This only supports core profile doesn't support profile2 , issue has been created there is no reply from maintainers
b)Both the users(roles) should have the term reference field, in my case recruiter will not have profile at all
c) this has been recently patched to support role reference it will work if profile2 is supported
3. Create a view of content type job_per_template and use contextual filters to get only matching jobs and restrict access to results, Which I am trying now :)
Contextual filters (or
Contextual filters (or arguments in drupal 6) filter content based on what a user types into the browser's url window. I don't think these are what you want. I think that if you stick with option 3. you just want plain old filters.
As it is, I have 2 ideas.
1) Taxonomy terms and the Token Filter module
Attach tags to profiles based on the information that users enter into their profiles.
Attach tags to jobs based on profile categories.
Install and enable the Token Filter module.
Filter your view based on tags.
Insert a token that links the filter to the current user.
2) profile fields and the Token Filter module
Filter your view based on the fields in their profile.
Install and enable the Token Filter module.
Insert a token that links the filter to the current user.
I should admit that I've never used the Token Filter module but it looks promising.
I'd be happy to take a look at your site if I have the time and you want to give me the link.
Let me know if you email me though so your message doesn't end up lost in my spam folder:-)
here is my contact
I am sending login details through your contact form
venky.subramanyam@gmail.com
I've wrestled with this for a
I've wrestled with this for a few hours with no success. Sorry!
never mind, you have more knowledge than yesterday
Thanks, never mind, you have more knowledge and wiser than yesterday:)
do you know coding?
a=1, b=2, c=3... That's about
a=1, b=2, c=3...
That's about the extent of my "coding" knowledge:-)
can any one help plz
can any one help plz
Let me know if you ever
Let me know if you ever figure this one out. I'm still keeping my eyes out for a solution.
Contextual filter is to be used I dont know how to use that
Contextual filter is to be used I dont know how to use that
Profile2 and contextual filters doesnt work together
There are issues , Some one helped me with a work around using panels, it is half way and once it is finished i'll update here on how it is done,
astanley86 tried helping he almost got it using panels, But I have filed collection field where one of my filter term resides, and there is no support for filed collection for that
tried using
I tried using Views default argument from Context and
Views Arguments Extras,modules
But without any success,may be I am not using correct context need help on that
@kaiserking As to your
@kaiserking
As to your previous doubt
We can use a "apply" flag to jobs ( content type ) and the flag can now be related to the applicant who flagged ( applied ) to the job
Seeing the Recruiter part, the job ( content type ) that recruiter has created, he will be able to see the no.of applicants who flagged ( applied ) to the job!
Now comes the part of Job Notification!
We have a Field_collection JOB PREFERENCES where in some taxonomy terms are used for Industry Fields and Occupational fields, which are believe are the primary criteria on job search!
Say an example: I'd love to be notified about Jobs for "Computer Engineer" and "Storage Administrator"
In that case we can use Flag Terms to Flag Taxanomy terms to user's Job preferences. When a job ( content ) is posted related to these jobs, Rules can be used to automatically post a notification to the user!
Does this sound good to go?
what you are talking is job book marks
@sk8erboi , What you are saying about flagging is job book marks which is already existing,also there is saved search facility in recruiter for this
About job preferences,The whole point is to let the system decide the candidate's suitability to the job,
in job preferences candidate enters the data which may not be relevant to his actual experience job preferences is a kind of candidates objective in general resume usage
it seems the views profile 2 and user relation ship is broken
May be this is the reason it is not workingViews broken relationship. but not sure no one confirmed, even the module maintainers are busy pushing this non working module to D8 core, and don't have time to attend issues
now trying with flag
I am trying to flag the term by user using rules
it works fine with the single value fields
but if a field is multi value field and user can select a term more than once, then once flagged term will remain flagged, because if you try to unflag the unchanged value and flag update field the term will be unflagged even the term exists in another field.because you cannot flag a term more than once. and there is no way you can check if the term is used more than once when you want to change flag using rules.
still trying , my thought process is:
it will be better, if we can list all the terms in view and first unflag all unchanged and then flag all updated (saved) terms that way we can get all the terms flagged by user and and filter content a per the terms flagged by user
using flags
Using flags is a good option i believe, but flagging terms is what i have not yet tried. But when we do want to get jobs matching the users interest, what we can do is even something like this.
Have a view.
On load of the job-search view, user preferences can be passed as arguments.
Against this, rules can be used to compare user preferences to the fields in the jobs posted.
I am still into some tough works until i see you back soon!