The thing is, the API is already there and it is definitely robust enough. The problem lies in so many different modules all trying to display it in so many different ways. As a developer, I cannot assume an install has another module installed to display this, or collect specific items.

Bump!

Thought I'd bring this issue back to the forefront. Couldn't it be possible for instance extend the [UserId] tag and use it in the profile properties area allowing the use of the tag and add a custom value or  [tabid] link to display that information on a users profle. This would pull values from 3rd party modules such as forums, picture galleries, news articles, etc. and display that value on a person's DNN profile, thus also adding a link on that person's profile and directing the viewer to the 3rd pary module or DNN module for the data.

I don't think this can be currenlty done by adding a new profile field, but it may be a good starting point.

So, lets say:

1. New Profile Property: "My forum posts"
2. Data Type: "URL" (which is currenlty not an option)
3. Default value: ???, and etc, etc.

Of course the values pulled from any other modules would most likely have to be a value of numbers or amounts such as "My Forum Post 300" but turn that value into a link going to the list of that person's posts. More thoughts? This is the wave of the future!!! CAMBRIAN Right?

Cheers!

I don't really think you will be able to integrate a profile property for "My Forum Posts". There are way too many factors involved to expose this type of functionality across multiple modules. The main challenge here is the data used is always going to vary module to module. However, the profile properties are capable of doing whatever you wish now for storage you just need to find a way to use that data commonly across multiple modules (ie. API).

CAMBRIAN allows the offloading of several things, ie comments, ratings, categories, tagging, etc. So, even w/ CAMBRIAN you need the following to occur: The CAMBRIAN API completed, modules using the API properly. Even with both of those completed, there are still things like display data in various areas of your site that require additional development, which would be custom at this time. Going back to the "My Forum Posts", you would need a centralized profile area on your site, integration w/ that module/API one way or another in the forum module, plus a custom work done in the profile module to link to the "My Posts" area of the forum you are using.

In short, I am excited about CAMBRIAN but I hope the community understands this is not the answer for everything that is module integration. The forum module will definitely be one of the ones following the API as much as possible as it progresses, but to have the type of integration mentioned here I think we are still two years away.

As for the comment on points, this would have to be exposed at the core level and then implemented in modules. You would, however, do this in a logging provider and then modules if you wished too. (We have done that before).