ITSRM Content Management Infrastructure Coordination

1. ITSRM Content Management Infrastructure Coordination David Foster IT June 2010

2. Background • Motivation • While sharepoint has become the recommended tool for creating collaborative sites it has been questioned as the best, or even appropriate, tool for content management and web content application development. • Strategy • The intention is to organise meetings and collect information that will drive decision making for IT support for content management infrastructure. • The activity is entitled: ENTICE “Enterprise Needs for Tools and Infrastructure for Content Exploitation” • Stakeholders • There are a number of key stakeholders that have been identified as they have expressed already interest in the problem (HR, DG-COM, Experiments). • The intention here is to ensure that all potential stakeholders who wish to actively participate have the opportunity to do so. • Status • One meeting has been held with the known interested parties and established there is indeed a need and interest to discuss this issue and make recommendations, especially as these will have resource implications. • http://indico.cern.ch/conferenceDisplay.py?confId=95230 • This is not a meeting on the philosophy of communications CERN-wide but is to discuss the tools and infrastructure the applications and site developers use. This meeting concentrates on the “How” and in particular the services IT can offer. • The “What” is discussed in other places (e.g. LOG)

3. Objectives • What services should IT be providing to support the user communities? • After the first meeting, Opensource stack seems to be reasonable – but we need to agree on many details. • Need to define the service specification and resource it accordingly. • How does this fit into the bigger picture? • 1. We need to identify what content is important for people and needs to be accessed. • 2. We need to identify how that content can be accessed (syndicated). • Authoring and Retrieving • 3. We need to identify what tools people need to access content. • Authoring and Retrieving

4. The sort of things that might be discussed • Will a LAMP stack be acceptable as LAOP replacing MySQL with Oracle? • What interface methods need to be supported to which repositories? • Would a service description that includes a framework for only Drupal be acceptable? • How should the service be requested by the user and what controls should be in place? • How will the service be supported? VM’s or dedicated boxes? What are the implications? • The advantages of centralised security scans to be debated. Would that allow user installable modules freely? • Do we need an application module repository and  how would it be managed? • Do we understand how the back-end for the websites can be made scalable using the open-source tools? • If there is a central Drupal service what should the upgrade policy be, for example to Drupal 7? • What will the backup/restore policy be? • How should the sharepoint service be extended? Will sandboxing enable usable installable Webparts?

5. Initial Work Plan

6. Actions from the first meeting • CMS indicated they had planned to do a survey to bring together requirements and possible implementation ideas across the experiment. It was decided that this would be good to do together with ENTICE as a single exercise. • A framework for general information gathering by the end of May. • Next meeting to finalise the framework early June • Information gathering using the framework in June • Meeting to discuss results early July The next meeting is scheduled for the 9th June Additional requests for participation should be sent to david.foster@cern.ch