search agent, email alert

Next topic

Author	Message
stephane francois	Saturday 23 June 2007 3:40:50 am Hello, My first post here. Ez i amazing. I'm thinking about creating a website like monster.com based on EZ, but i can't figure out how to allow job seekers to create search agent (receive new offers matching their criterias through e-mail). It's not simple notification, and it's not newsletter either. Did anyone ever do such a thing before ?
stephane francois	Tuesday 26 June 2007 10:17:10 am Anyone ?
Heath	Tuesday 26 June 2007 11:55:58 am I think a system like you describe would be useful, yet I've not heard in passing of such a thing to date (at least not publicly). It would seem like a fair amount of development. While the surrounding components would seem simple enough. The saving of a search in the way you describe to use again later seems more complicated. I think it might be most powerful when combined with more powerful search engine backends (rather than the current php implementation) yet ... this alone would not be enough. Perhaps a template which queries eZ content objects created to store the user submitted agent match criteria might be a simple start to building a proof of concept for which a php developer could create the automated agent. This is a gross simplification as you don't pickup a monster.com ready to go.... Still with eZ there is nothing we can not create. Have you written any functional requirements for your solution you would be willing to share? hth Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org
André R.	Tuesday 26 June 2007 12:01:41 pm Hi, I don't think I've seen something like this before. The easiest would probably be to use newsletter with a custom cronjobs that only send out emails if there are more then 2 new jobs for instance. But could also be solved with a cronjob (script), fetching all new content of type class 'job', and generate the email for it. Then fetch all users with attribute 'send_new_jobs_on_mail' set to true, and send out the pre generated mail to them one at a time. fetching from php example: http://ez.no/community/forum/developer/fetchobjecttree_not_sorting_correctly/(offset)/0#msg133910 examples of cronjobs are on the contribution are of this site and the cronjob folder in eZ Publish. EDIT: seems like you need to loop true every user to see what kind of jobs they want and create the mail for them based on that if there are any new mail in that categories. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
stephane francois	Tuesday 26 June 2007 2:34:40 pm Hi, thanks for your reply. No Heath, i haven't done any specification yet, but if i do, i'd be glad to share it. André, you're right, i would need to loop on every user to check witch job matches their criteria. The thing is i'm a newbie, i've never made any extension before, and i think it'd be a bit hard to start with that. What do you think about this solution : - one node for each job category (when someone tryes to publish an offer, it automaticly is stored in the corresponding node) - users are allowed to create notifications for each node, so they receive notifications for each new offer published. ?

eZ debug

Timing:	Jan 18 2025 21:00:14
Script start
Timing:	Jan 18 2025 21:00:14
Module start 'layout'
Timing:	Jan 18 2025 21:00:14
Module start 'content'
Timing:	Jan 18 2025 21:00:14
Module end 'content'
Timing:	Jan 18 2025 21:00:14
Script end

Main resources:

Total runtime	0.6416 sec
Peak memory usage	4,096.0000 KB
Database Queries	65

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0049	587.9063	152.6250
Module start 'layout'	0.0049	0.0028	740.5313	39.4297
Module start 'content'	0.0078	0.6324	779.9609	605.1563
Module end 'content'	0.6402	0.0014	1,385.1172	16.1797
Script end	0.6416		1,401.2969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.4663	16	0.0002
Check MTime	0.0013	0.1963	16	0.0001
Mysql Total
Database connection	0.0008	0.1172	1	0.0008
Mysqli_queries	0.5851	91.1817	65	0.0090
Looping result	0.0006	0.0993	63	0.0000
Template Total	0.6108	95.2	2	0.3054
Template load	0.0017	0.2580	2	0.0008
Template processing	0.6091	94.9276	2	0.3045
Template load and register function	0.0002	0.0250	1	0.0002
states
state_id_array	0.0014	0.2127	1	0.0014
state_identifier_array	0.0007	0.1049	2	0.0003
Override
Cache load	0.0013	0.2033	35	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0842	3	0.0002
Fetch class attribute name	0.0013	0.1953	7	0.0002
XML
Image XML parsing	0.0011	0.1763	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0020	7	0.0000
General
dbfile	0.0018	0.2840	24	0.0001
String conversion	0.0000	0.0013	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 20 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs