1 person found this helpful
You are right, the external integration that you are talking about was done via a plugin. In general, the best practice is to exhaust other integration options first, before moving down the path of a plugin. That said...
You could use OpenSearch, but that doesn't really bring the content into Jive, it simply calls out when a search is made. Also, you don't really know who is the search is performed on behalf of--no user info is passed along.
The feed into sharepoint is an interesting idea. Robert Fernandes, do you have any thoughts on that?
If you don't have a lot of internal developers, there are some of out Technology Partners that have done work in this space, notably The specified item was not found.. They might have some ideas on what's possible as well.
Mark - Thanks for the response. It may not be a show stopper if we lose who performed the search. A lot of our content is open and gets accessed by non-logged in users, but I do agree that is valuable information to keep track of. Do you know of any implementations where OpenSearch was used for something like this? I have not done much research on it, but I think the user has to click an extra link to show OpenSearch results because they are not automatically included inline with everything else. If that is the case that may be enough to eliminate it as a possibility. If nothing else seems like a good fit I was thinking the worst case scenario is creating new documents or updating existing documents via API calls each night.
Robert Fernandes - Can you comment on Sharepoint being a possibility for this?