Single database table for multiple workareas?

rach

I've had a look at the documentation for OD 611, and I'm beginning to think that what I want to do isn't possible, at least not the way I imagined it. At least, using DAS, the naming convention is storename_datacategory_datatype__branchname_areaname. I can't quite figure it out for DataDeploy.

Each department and school is in its own workarea. I would like to have a news template in each workarea, and have the dcrs deploy to a single database table. The point would be to control access so that users could only update items for their department or school, but to share the content across all of them. That is, they could then generate pages choosing from all the news items submitted from all the different workareas.

Is this possible? If so, I'll plough through and figure it out, but if not I'll have to come up with another solution.

Adam Stoller

I've had a look at the documentation for OD 611, and I'm beginning to think that what I want to do isn't possible, at least not the way I imagined it. At least, using DAS, the naming convention is storename_datacategory_datatype__branchname_areaname. I can't quite figure it out for DataDeploy. Each department and school is in its own workarea. I would like to have a news template in each workarea, and have the dcrs deploy to a single database table. The point would be to control access so that users could only update items for their department or school, but to share the content across all of them. That is, they could then generate pages choosing from all the news items submitted from all the different workareas. Is this possible? If so, I'll plough through and figure it out, but if not I'll have to come up with another solution.

Perhaps you should be concentrating on deploying (and accessing) the data from the staging area instead of from the individual workareas ?