Roadmap

As part of the Digital Campus Design and Infrastructure initiative, Content Systems maintains several applications that provide content for UITS via single-sourcing — which allows authoritative information to be delivered for multiple uses and to multiple destinations — with several more in the queue for future development. Our primary direction for 2019 is to take intentional steps toward integrating these various applications and building a cohesive platform for content management at Indiana University.

2019 Quarterly Overview

Application Description Quarter
CCore Services FKA Serif, a directory of UITS services 1
CCore People FKA UITS OrgCharts and IT Pro database 1,2
CCore Knowledge FKA Knowledge Management System (KMS) 1,2
CCore Assets Rich-media asset management 1,2
CCore Dashboard Entry point for CCore review and notifications 2
CCore Edit Unified edit access for authorized users 2,3
CCore News FKA IT News 3
CCore Initiatives Large-scale endeavors with promotional content 3
CCore Projects Specific timeline-driven deliverables 3

Q1 2019

Project visibility and communication

Laying the groundwork for public discussion and transparent development

  • Branding for CCore suite and applications complete
    • Communicating the new names to system users and developers, so they may continue to use these services.
    • Updated documentation, product descriptions, and roadmap information on GitHub and the IU Developers website.
  • Improve development process transparency and provide structured processes for clients to submit issues, bugs, and feature requests.
    • For each existing application, we will create a GitHub project with a public backlog of known issues and feature requests.
    • A process will be created to respond to each GitHub issue, either accepting the issue, merging it with another issue, modifying the issue, or rejecting it. This will all be done in plain sight within GitHub.
    • Publish project pages with information about work currently planned or in-process for each application, as well as information about planned changes in future sprints.
  • CCore Services v1.0 (fka Serif) in production
  • CCore People MVP: Initial (read-only) deployment of People, as replacement for IT Pro Database, in partnership with ITCP and SSL; import and sanitization of Structure data from WCMS
    • Prototyping of People admin client, for maintaining both organizational units, their structure, and membership (by HR, IT managers, and administrative assistants) and profile pages (by managers and individuals)
  • Redesign the administrative interface for CCore Knowledge (fka KMSED) using Rivet and making modifications to better integrate with CCore Services; make the IU Knowledge Base Rivet-compatible.
  • Migrate CCore Knowledge to latest version of Java
  • Work with IT Communications Office (ITCO) and Knowledge Management (KM) to scope initial requirements for CCore Assets, a digital (rich-media) asset management system, including prototypes.

Q2 2019

Unifying existing applications

Building robust associations into CCore data and creating a standard model and workflow for content managers

  • Deliver UITS Services Directory, service profile pages, and search returns from CCore data.
  • Build cross-application tools and awareness into administrative and editing environments.
    • CCore Knowledge key terms currently present in CCore Services can serve as a model and potentially as code on which to iterate.
  • Begin integration of CCore Assets as a microservice into People and other CCore applications.
  • Deployment and ongoing refinement of CCore People admin client
    • Link CCore Services records to specific People units
    • Begin leveraging People data for CCore and other DCD application authorization
  • Use CCore Knowledge tools (KMS editing environment) for content management functions across the CCore suite.
    • Add value quickly by adapting tools to check and track links, map metadata for search, etc.
    • Work with ITCO and other stakeholders to determine workflow processes and content lifecycle needs, with an eye toward creating robust and flexible standards across all of CCore.
      • As standards mature, begin design of CCore Dashboard (and/or Workflow).
    • Investigate feasibility of expanding KMS editing environment into a full CCore Edit application.
  • In collaboration with UITS site stakeholders, create consumer API endpoints that deliver useful coordinated information from across multiple content types, built to facilitate delivery of UITS pages and tools; with input from the developer community, APIs will have thorough documentation, and will emphasize open endpoints where possible to encourage broad adoption.
  • Develop, plan, and prototype technology for unified logging and analytics, including visualization — consider Elasticsearch (with Logstash and Kibana) and Google Analytics.

Q3 2019

Expanding the suite

Adding new content types and incorporating stakeholder feedback

  • Consult stakeholders and collect requirements for a CCore Initiatives application; prototype an application and an API solution that collates relevant projects/services/groups/tasks as needed.
  • Build a support widget that leverages the geolocation API.
    • Collaborate with other teams, particularly those working on IU Mobile, to investigate other content whose value could be increased with location awareness.
  • Begin refactor of IT News into CCore News.
  • Consult with ITCO, SC, and other stakeholders on the value and priority of other content needs (e.g. Promotions, Announcements).

Q4 2019

Powering UITS

Delivering the initial version of the new UITS site and leveraging the benefits of single-sourced content

  • UITS site delivers Services, Initiatives, and a location-aware support widget from CCore data.
    • All data has been vetted and revised by content managers; DCD will carry out any batch imports, sanitization, etc.
    • All services have a brief entry, with description and CTA, which can be returned in search results and the Services Directory; all services can have a full profile view, with People, Knowledge, and Status information included.
    • All initiatives use centralized, single-sourced content, which can be easily included in pages maintained in WCMS if needed.
  • CCore also provides data to deliver org/structure pages and a UITS staff list.
  • Prototype CCore Projects.
    • Determine end-user/delivery requirements, data structure, workflows, etc. for Projects information
    • Develop further consumer APIs, with payloads that match page needs and thus improve the end-user experience.
    • For specific delivery to the new UITS site
    • For delivery via WCMS chunks