Last week we had a WebCast as part of Oracle's WebCenter in Action webcast series, "ResCare Solves Content Lifecycle Challenges with Oracle WebCenter", where customer Joe Lichtefeld from ResCare and Wayne Boerger & Doug Thompson from TEAM shared how Oracle WebCenter is powering and allowing ResCare to solve content lifecycle challenges, reduce compliance and business risks, and increase adoption of intranet as primary business communication tool.
In case you missed it, here's a recap of the Q&A.
Joe Lichtefeld, ResCare
Q: Did you run into any issues in the deployment of the platform?
A: We experienced very few issues when implementing the content management and search functionalities. There were some challenges in determining the metadata structure. We tried to find a fine balance between having enough fields to provide the functionality needed, but trying to limit the impact to the contributing members.
Q: What has been the biggest benefit your end users have seen?
A: The biggest benefit to date is two-fold. Content on the intranet can be maintained by the individual contributors more timely than in our old process of all requests being updated by IT. The other big benefit is the ability to find the most current version of a document instead of relying on emails and phone calls to track down the "current" version.
Q: Was there any resistance internally when implementing the solution? If so, how did you overcome that?
A: We experienced very little resistance. Most of our community groups were eager to be able to contribute and maintain their information. We had the normal hurdles of training and follow-up training with implementing a new system and process. As our second phase rolled out access to all employees, we have received more positive feedback on the accessibility of information.
Wayne Boerger & Doug Thompson, TEAM Informatics
Q: Can you integrate multiple repositories with the Google Search Appliance?
A: Yes, the Google Search Appliance is designed to index lots of different repositories, from both public and internal sources. There are included connectors to many repositories, such as SharePoint, databases, file systems, LDAP, and with the TEAM GSA Connector and the Oracle Content Server. And the index for these repositories can be configured into different collections depending on the use cases that each customer has, and really, for each need within a customer environment.
Q: How many different filters can you add when the search results are returned?
A: Presuming this question is about the filtering on the search results. You can add as many filters as you like and it can be done by collection or any number of other criteria. Most importantly, customers now have the ability to limit the returned content by a set metadata value.
Q: With the TEAM Sites Connector, what types of content can you sync?
A: There’s really no limit; if it can be checked into the content server, then it is eligible for sync into Sites. So basically, any digital file that has relevance to a Sites implementation can be checked into the WC Content central repository and then the connector can/will manage it.
Q: Using the Connector, are there any limitations around where in Sites synced content can be used?
A: There are no limitations about where it can be used. When setting up your environment to use it, you just need to think through the different destinations on the Sites side that might use the content; that way you’ve got the right information to create the rules needed for the connector.