Loading Profile...
Co-Producing Content with multi CoPs - What CoP template does the page go to on the Live Site?
How does it work on the live site when 2 or more CoPs have their main category on a page?
We have a couple of content teams in co-production with other CoPs. I previewed one of those pages, and realized that the nav bars and Community pages can only link to one CoP.
How will the page "choose" which CoP template to fall into?
How have other CoPs managed this?
What are other co-production issues that I haven't thought of yet?
Thanks,
Sue Hawkins
We have a couple of content teams in co-production with other CoPs. I previewed one of those pages, and realized that the nav bars and Community pages can only link to one CoP.
How will the page "choose" which CoP template to fall into?
How have other CoPs managed this?
What are other co-production issues that I haven't thought of yet?
Thanks,
Sue Hawkins
I’m wondering
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
The best answer from the company
-
Hi Sue,
I actually led James astray on this. The logic on this has changed over time, and the way it has been implemented is a little complicated as it has gone through multiple contractors and staff members manipulating the source code that makes it happen. (there's probably something to be said about the complicated nature of the terminology that is used about each CoP having their own site, and the complicated logic in the code to pull that off if this can't be easily explained in a sentence or two).
I told James incorrectly on the last part - I was confused by the code and we had different conditions for different pieces of content.
So how it works today:
If the content is categorized or tagged with the same tag that one or more communities is tagged with - you'll get the homage (the "This resource area was created by the:..." in the sidebar) of one of the communities for that piece of content.
( The one selected in code has to do with the order of the tags in database table that holds the ~4,000 current tags ). This is irrespective of how you got there, whether by browsing into the content or landing from a search for the first time.
Unless the piece of content is an event, the homage for an event will come from the community set by browsing other content (or no community if landing on an event from search for the first time).
How it will work
If you have been browsing the website, and have browsed through the index page for a community, and you click on a piece of content categorized/tagged with tags that belong to more than one community, including the community you were browsing - that community will stick. So you start with Sustainable Agriculture, click on an (article,news,faq,event,etc.), it will keep the homage of Sustainable Agriculture. If you've visited recently, and land on a piece of content from search, that again matches the community you were last browsing, the community will stick.
If you land on a piece of content from search, and haven't been browsing recently, one of the homages/communities will be picked. This selection will be at random and not dependent on the order of the tags table (which now contains ~6,500 tags from all four merged apps).
For the incredibly technically curious - here is the code change (and the change to random on top of the previous one )
I’m happy that it will be more consistent, bemused that it's still too complicated.
The company says
this answers the question
-
This reply was removed on 07/29/09.
see the change log -
Inappropriate?Hi Sue,
I apologize, there is actually a third case and a correction to the above as well. Let me start again:
I can't speak to how CoPs manage co-production, but i can answer one of your questions.
When two or more CoP main categories are associated with published content, a few things happen when it is presented on www.extension.org.
First, each community is listed just under the title of the article. This list is called the "Related resource areas".
Second, if the person has never visited www.extension.org and is coming from, say, Google, a community is just selected (the selection will always be the same). This selection affects the right sidebar (graphic/resource area links) on the page.
Lastly, if a person has already visited www.extension.org, the community they last viewed becomes "sticky" as the visitor goes from page to page. Therefore, no matter the categories on the content viewed, in this case, the sidebar stays the same.
Sorry for the confusion! James
I’m cheerful
-
Inappropriate?Hi Sue,
I actually led James astray on this. The logic on this has changed over time, and the way it has been implemented is a little complicated as it has gone through multiple contractors and staff members manipulating the source code that makes it happen. (there's probably something to be said about the complicated nature of the terminology that is used about each CoP having their own site, and the complicated logic in the code to pull that off if this can't be easily explained in a sentence or two).
I told James incorrectly on the last part - I was confused by the code and we had different conditions for different pieces of content.
So how it works today:
If the content is categorized or tagged with the same tag that one or more communities is tagged with - you'll get the homage (the "This resource area was created by the:..." in the sidebar) of one of the communities for that piece of content.
( The one selected in code has to do with the order of the tags in database table that holds the ~4,000 current tags ). This is irrespective of how you got there, whether by browsing into the content or landing from a search for the first time.
Unless the piece of content is an event, the homage for an event will come from the community set by browsing other content (or no community if landing on an event from search for the first time).
How it will work
If you have been browsing the website, and have browsed through the index page for a community, and you click on a piece of content categorized/tagged with tags that belong to more than one community, including the community you were browsing - that community will stick. So you start with Sustainable Agriculture, click on an (article,news,faq,event,etc.), it will keep the homage of Sustainable Agriculture. If you've visited recently, and land on a piece of content from search, that again matches the community you were last browsing, the community will stick.
If you land on a piece of content from search, and haven't been browsing recently, one of the homages/communities will be picked. This selection will be at random and not dependent on the order of the tags table (which now contains ~6,500 tags from all four merged apps).
For the incredibly technically curious - here is the code change (and the change to random on top of the previous one )
I’m happy that it will be more consistent, bemused that it's still too complicated.
The company says
this answers the question
-
Inappropriate?Hi Sue,
The logic described above was deployed as part of the merged release on August 12, 2009. -
EMPLOYEE
EMPLOYEE
