'Favourites' list and 'comparison' tool - are these feasible with modx?

Hi
I need to know if the following things will be feasible with modx, with or without extra core development:

* Within a user login area the ability to search items and save them to a ’Favourites’ list, which are then available whenever the user logs in
* A ’comparioson’ tool - i.e. selecting, say, 3 properties and being able to compare them against each other - so all 3 called and visible

There is a development budget available if anyone is interested ;-)
Thanks in advance!

They’re all possible, wouldn’t require core development but would require data modeling and front end snippet development. How are the things getting into the database in the first case?

They’d all be entered by the site administrators and users can then select them for favourites - sorry i can’t be clearer right now as it’s quite formative at the moment.

But the crux is that the site is populated with properties by the admins - each property with varying individual detail - users can create accounts, select and save favourites within their accounts, compare properties at both front end and within their account, create virtual pets ... oh, that’s later ...

What do you think?

Entirely doable. How many properties? This would determine whether or not it should be pages or a custom module using xpdo to access the data?

Sorry for the delay in response. Great that it’s all doable

I don’t know how many properties right now but i envisage that this number would grow and shrink over time, but most probably grow. I’ll find out how many are likely first up and update as soon as i know.
Thanks

okay - first off there will be about 30 villas.

Entirely doable. How many properties? This would determine whether or not it should be pages or a custom module using xpdo to access the data?

Would 30 properties make it pages or xpdo?
Thanks

30 villas are way within the modx document capacity. You would need to develop the comparison system yourself (i think) but you could use TVExplorer to handle search/filtering.

AjaxSearch now handles TVs as well so this can also be used, but I think that TVExplorer is closer to what you need.

For the comparison you could probably use Ditto with a wrapper snippet to retrieve the documents to compare either from a cookie value or a url parameter.

Okay, I get the jist of it - and thanks very much for the feedback - but the development would be a bit out of my grasp right now, at least for a short deadline if the job comes off. So this would be something i could hopefully do with a few support tickets ... sound possible/likely?