|This article is Deprecated and should no longer be used, but is still available for reasons of reference.|
THIS SITE WAS NEVER FINISHED. PLEASE DON'T USE IT.
About the table
Empowering scientific communities with tools that enable them to make use of European Grid Infrastructure services is important for the successful engagement of EGI with new users. Portal technologies play an important role within this respect. Portals can eliminate barriers of e-Infrastructure access, portals can seamlessly integrate grids and the web. Because of their strong relation to users, portals are typically geared to specific users, applications, scientific use cases. Several national and community-specific teams and projects offer portals and "portal builder technologies" in EGI. With such a diversity it can be difficult to make a decision on which portal to use as a scientist, which portal builder technology to use as a portal developer.
EGI responded to this need with the setup of a "portal technology comparison table". The table provides a review of existing and reusable portals, portal developer frameworks, portlets and components that exist within EGI. The table helps scientific communities and their software teams identify solutions that best meet their needs and should be considered when accessing or building portals.
The questions that are used within the table to describe and compare the different portals and portal frameworks have been defined through an open process during December 2011 - January 2012.
This section lists the questions that are used within the to describe and review portals and portal builder frameworks that exists for users of the European Grid Infrastructure. New entries can be added to the table as described on that page.
1. Name of the portal (P-GRADE Portal, WeNMR Portal) 2. Webpage of the portal 3. The described portal is: * a complete portal (can be used “as it is”, its features cannot be customised) * a portal framework (can be used “as it is”, and additionally features can be added, removed, changed) * a portal component (for example a portlet, or a library for portal developers)
4. Is the portal open source? Under what license? 5. Who are the potential users of the portal and what kind of skills do they need to have? (e.g., which programming language skills are needed if the technology is for portal developers) 6. What are the key features of the portal? (e.g., list of portlets in case of a complete portal) 7. What are the distinguished features of the portal? (features that make this technology different from similar solutions) 8. Which EGI services are accessible through the portal? (e.g., middleware services - gLite, ARC, Globus, Unicore; other services like a Helpdesk, a Requirements tracker, etc.) 9. What is the supported security model and technology? 10. Does the portal support workflow execution? If yes, for which workflow system? 11. Is the portal available for download, or is it hosted as a service?
Adding a new entry
New entries can be added to the table through this [LINK online survey]. The survey consists of two sections to collect basic and more detailed information about the technology to be added. If you wish to read the survey questions before filling the form please consult with this page. The survey is managed by the EGI.eu User Community Support Team, who validate the received information and add entries to the below, publicly accessible table. If you register your portal in the table please also consider registering it in the EGI Applications Database.
Changing an entry
Please email the requested change to the EGI.eu User Community Support Team - firstname.lastname@example.org.
EGI Portal Technology Comparison Table
The collected info is displayed in the following table.
Portal technology name
|Technology availability||Portal category||Software license||Security model||Target audience||Skills||Features||Key features||EGI services available||Workflow support||Science gateway/Portal examples|
||Open source (GPL)||n.a.||Portal developers||
||This allows the direcPylons is a Python web framework.t integration of all in-house/community python bioinformatics scripts.
Dirac API use Pylons.
|WMS, Storage Elements, VOMS, myproxy||n.a.|
|Drupal||Downloadable||Portal framework||Open source (GPL)||n.a.||
||One of the most useful and used frameworks for community websites.||
||n.a.||WeNMR science gateway|
|WS-PGRADE Portal||Hosted as a service||Complete portal||Open source (GPL)||n.a.||Researchers that want to create images and movies with own dataset||Portlet based||iPhone/Smartphone application linked to the portlet (in progress)||Middleware||n.a.||VisIVOWeb|
||Hosted as a service. Although the Python based validation component of the HADDOCK, CS-ROSETTA, UNIO and GROMACS portals is available as framework and can be downloaded.||Complete portal||Open source||n.a.||All portals are developed with common programming languages without specific frameworks apart from the Spyder python framework for data validation.||The list of automated grid submission and polling scripts used behind the portals is available here||Simplicity – combination of mainly python and shell scripting||gLite WMS and LB||n.a.|
||Hosted as a service||Complete portal||Open source. A valid license is needed for the use of one of the software portals (CYANA).||n.a.||Python-CGI, shell script and HTML||The list of automated grid submission and polling scripts used behind the portals is available here||Simplicity – combination of mainly python and shell scripting||gLite WMS and LB||n.a.|