Q: How do I know if this is the right tool for me?
Each situation is unique, but a successful CarolinaContent project might include items such as:
- A large volume of content and documents.
- Content that has long term value for the university. (IE — a Web site for a quick project that will only be relevant for a short period of time might work better in another tool)
- A need for strong version control, rollback and archiving capabilities.
- Content that will be repurposed in multiple pages and sections.
- Content that is both public and restricted, based on an LDAP/Onyen security model.
- A need for an approval workflow model.
Items not typical of a CarolinaContent project include:
- Transactional or web-application functionality
- E-commerce
- Sites with a very specific or small target audience
Q: What are some other campus groups that will be using Oracle UCM system?
Web Services plans to migrate and build new sites in the UCM for selected key campus administrative units, such as Human Resources, Finance and the main University Web site.
Will this replace all other CMS tools on campus?
Ultimately the project is intended to provide an enterprise Web content and document management solution for the entire campus. However, there is no such thing as a “one size fits all” CMS. CarolinaContent will not replace all other CMS tools on campus. It’s all about selecting the right tool(s) for the job. In some scenarios, a “hybrid” solution that leverages multiple tools may be the answer. A small blog may not need the robust feature set of an enterprise CMS. Other sites may be a great fit for a straightforward CarolinaContent implementation.
Q: What type of governance is in place for the tool?
As part of our support plan for CarolinaContent, we intend to establish a governance structure. However, during the initial phase of the project (its.unc.edu and help.unc.edu), these requests are reviewed by the manager of ITS Web Services, Jeremy Davis, in collaboration with the CIO and Deputy CIO.
Continue reading