At first I was getting a little confused with FO, but I am finding it VERY powerful.
The more I play (and break) with it, the more I am learning. I am now almost to the point to go live (LOT more to do, but I think I can work my way through it) but I trying to come up with a 'model' that I would like to use to deal with objects. As I could think if one was to have many employee's (by full time and contractors) and clients, handling LOTS of objects could be a pain over time.
The best way for me to explain is through an example:
Lets say I just hired some one (contractor that I might want to bring on full time, but only for temp/trial bases) but I don't want to give them all of the objects (Notes, Documents, Tasks etc) at one time. Now lets say that after this given time I no long wish to use them and there account is deleted. But I don't want to loose those objects.
What would be a good practice on handling objects in this manner? Creating a workspace JUST for these objects, and assign them to users when needed? I suppose one could also have a few parent workspaces that they could be assigned over time. And then moved up higher in the workspace chain for that workspace.
And above would also apply to companies/clients.
Hope that wasn't too confusing, as I am still trying to work it out myself. So any ideas and practices any of you use would be great to hear. I can really see the possibilities of OF and I just want to look down the road how to be able to use it in an effective manner.
Thanks and looking forward to any replies.