Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

EGI-InSPIRE:Na3 Scrap room

From EGIWiki
Jump to navigation Jump to search

This page is the "internal wiki" of NA3. It serves as an area where ideas, suggestions, useful information, links can be collected. The activity management contributes, as well as monitors the content of the page and incorporates contents from here into the EGI user support processes.

Please note that because this page can be read by anybody, sensitive information should be collected in separate documents with restricted accessibility (e.g. a GoogleDoc) and only links to these documents should be inserted here!

RT Requirements vs Market place


In terms of requirements solving market, there is a suggestion to make access right to all SSO accounts to take the ticket (aka, become the Owner of the ticket). The Owner could indicate that ticket/requirement was taken and is in the solving process after the solution will be provided by the Owner.

New UCST Web Pages - under construction

Ideas and suggestions for EGI User & Community Support Team web-pages. The UCST’s intent is to create a new set of web pages that are accessed initially from the website, thus simplifying the ‘User’ experience and entry into all Support services through a single entry point. This area is being used for the development of the new site prior to going live.

Check this page.

Owner of this section is Richard McLennan, UCST


This section has been established in order to capture ideas and suggestions for EGI User Community workshops - all inputs should be posted to


A key element of the EGI task in its contribution towards “enabling collaboration and exploring research opportunities” is achieved firstly through the twice yearly Technical and User Forums and secondly, through other meetings and workshops. The User Forum held in April 2011 in Vilnius, Lithuania revealed a growing desire amongst the user communities for such ‘collaboration and exploration’ to be achieved through smaller and more focused meetings which should be much more involving for individual specialist users. Furthermore, feedback drawn from requirements submitted through EGI’s Requirements Tracker (RT) system reveals that there is a growing call for carefully targeted events that must be tailored to the needs of specific parts of the community, either to ‘inform and educate’ or to help clarify and specify what are initially no more than vaguely stated requirements.

Now that the RT system has been up and running since September 2010,’s User Community Support (UCS) team has acquired a fair number of user requests for new features and new configurations to be added to the EGI supported infrastructure. The total number of such requests submitted to UCST by Jun 2011 stood at 233. All of the tickets submitted are analysed as a matter of course and distilled into general themes in order to drive them towards successful resolution through appropriate channels. Invariably, there is a great deal of work that still needs to be completed in order to translate these general requirement ‘Themes’ towards solutions. In some cases, the solution is one of collective training and education while in others, work must start by producing a clear, tight and unambiguous ‘Statements of Requirement’ that can be effectively passed as guidance to Technology Providers so that they may in turn develop the needed solutions. What is clear is that a most practical way forwards is through the use of targeted Workshops whereby interested parties can be brought together for brainstorming, interactive learning, sharing best practices, building relationships, data gathering and problem solving.

Aims and Outcomes

In order to contribute to the creation of ‘Sustainable user services for sustainable user communities’, the UCST will continuously plan and conduct targeted workshops with the following two principal outcomes in mind:

  • Training, Education & Standards. T&E Workshops shall focus on sharing practices and procedures so that EGI as a service provider and user communities (as service users) can work towards increasingly common standards. As a by-product, UCST will aim to publish the standards as EGI reference documentation.
  • Definition of clear ‘Statements of Requirement’ (SOR). UCST shall assemble focus groups to discuss, brainstorm and clarify specific RT ‘Themes’ such that technical ‘Statements of Requirement’ can be properly and fully defined. These SORs shall subsequently be submitted to Technology Providers in the normal way via the normal Technical Coordination Board route.


The programme detailed in this document covers a series of targeted workshops that will be conducted over the period Jun to Dec 2011.

Workshop Events and Themes

Planning steps

Recognising that all such events represent a cost in terms of resources (be they financial, human or both), every workshop event shall aim to be cost effective by being constrained to be as small and short as practicable given the outcome that needs to be achieved. Once the ‘Theme’ or training purpose of a workshop has been identified, the following 5 key steps shall form the core process for planning the events:

  • Definition of Workshop Goal(s) (the desired Outcomes).
  • Selection of appropriate target group or specific individual attendees.
  • Selection of Venue for event – notwithstanding the suitability of a venue for any given event, the objective shall be to minimise downtime imposed by running the workshop.
  • Definition of the detailed working Agenda.
  • Documentation of findings and follow up plan – training workshops will result in documented standards and processes; fact finding events will lead to documented SORs.

Conduct of Workshops

UCST workshop events will normally be limited to a maximum of 30 participants and last no more than 2 working days. Events focused on training can be expected to comprise groups of nearer 30 people and be shorter in duration, while those seeking to gather hard data for generating ‘SORs’ are likely to be smaller groups (closer to 12-15 – for larger gatherings, effectiveness will be achieved through the use of ‘breakout sessions’) and may last up to 2 days. Breakout sessions to stimulate critical discussion and hence achieve output are a recognised element of successful workshop events and will be a routine part of each type of workshop.

Workshops will routinely start with some form of ‘scene setting’ introduction which will normally be briefed by UCST staff. Case studies will be used as much as possible.

Preparation Activities

There are a number of tools available to assist in preparation of workshops and these will be used extensively to ensure attendance, productivity and effectiveness of the events are optimised.

  • RT: Requirements Tracking system gathers user inputs from which UCST analysis can derive ‘Themes’ and some of the broad issues that need to be resolved.
  • User / customer surveys: Zoomerang survey tool will be used to refine the content and agenda that needs to be covered during intended workshops (as well as confirming the broader support for the proposed theme).
    • NGIs and VRCs will be directly canvased for their support/perceived need for issues to be more fully explored.
  • Scheduling: Doodle polls are used extensively as the means for identifying the optimum timing for such events.


Table 1 beneath details the intended Workshop events for the period up to Dec 2011 and readers are invited to provide constructive comments for additions, changes and deletions as applicable by e-mail to . Events planned for the 2011 Technical Forum are described in more detail in Table 2.

Table 1: UCST Workshops Phase 1 – Period 1 June to 15 Dec 2011

Serial Date Theme Remarks (supporting evidence etc) Target Audience: Desired Outcome
MAPPER/PRACE/EGI collaboration Initial presentation agreed to form a ‘Task Force’ to drive for a demonstration of MAPPER through 2 applications MAPPER Task Force (MTF) and leadership SOR. Definition of strategic objectives for activity plus clarification of customers and their requirements
Portal technologies for EGI Communities Explore emerging technologies and requirements for development of portals, portlets and i-frames TF11 event (see Table 2) T, E & S. Draft SORs.
Data management – best practices and requirements Present emerging data management issues and explore avenues for further developments as seen from user perspective. TF11 event (see Table 2); Technology providers (developers) and users. T, E & S. Draft SORs
Virtual Research Communities Promote available tools/services; explain RT and requirements gathering; seek VRC involvement in providing / adding local tools to EGI ‘service catalogue’. TF11 event (see Table 2)- VRC leadership. T, E & S. Train and Educate – establish best practice
EGI / NGI Roadshows – to include "Training tools, services and requirements” How to bring in more users and communities? Roadshow type event to promote EGI services and tools, and to seek NGI feedback on expand the customer base. To inc the new Training Marketplace. In particular, to enthuse NGIs to start encouraging their communities to load all potential Training and supporting material. TF11 event (see Table 2). Multi event type workshop to be delivered broadly. Note this can be seen as a ‘Train the Trainer’ function. T, E & S

Note T, E&S = Training, Education & Standards

Event titles & discussion

Proposed event titles

  • Single sign-on
  • Virtual Organisations (VO)
  • Persistent storage
  • User Support
  • Training and consultancy
  • Web-service interfaces
  • Workflows
  • Global scope
  • Integration with cloud systems and volunteer desk-top systems

Event titles for discussion

  • Science Field: Earth Science
  • Event Title: Data management, modeling, simulation and vizualisation
  • Technology providers: Grid - gLite, Cloud computing - StratusLab, Data management - EUDAT,...

  • Science Field: Astronomy & Astrophysics
  • Event Title: Grid computing and data management
  • Technology providers: Grid - Unicore, Data management - Unicore,...

  • Science Field: Computational Chemistry
  • Event Title:
  • Technology providers:

  • Science Field: Life Sciences
  • Event Title:
  • Technology providers:


GGUS Tools/Reports

We are investigating if relevant NA3 metrics GGUS related could be gathered from these links:

Metrics reports

Escalation reports

Report generator

GGUS Ticket Timeline Tool

Relevant documentation:

GGUS User Guide


Usability inspection

Apple Human Interface Guidelines

Task-Centered User Interface Design

Usability Study

MediaWiki tools

sorting table xample


Doc2Wiki Publisher

Taken from Sun Wiki Publisher homepage
The Sun Wiki Publisher enables you to create Wiki articles on MediaWiki servers without having to know the syntax of the MediaWiki markup language. Publish your new and existing documents transparently with the Writer to a wiki page.

Status  : tested and it works reasonable well
Caution  : be careful not to overwrite wiki pages
HowToDoIt : ...

Embedding slides