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.eu.
VT Science Gateway Primer/appdb
Project output - AppDB recommendations
Recommendations on how to improve the data structure of the EGI Application Database, to better support science gateway developers, are recoded in this wiki page.
1. Within the Science Gateways category we need two subcategories concerning the type of the gateway:
a. SG framework (Generic DCI gateway framework)
b. SG instance (Application-specific science gateway)
2. In both subcategories we need two subcategories concerning the status of the gateway:
a. Production level (available for external users)
b. Prototype level (tested by a selected set of users)
3. In both subcategories we need science subcategories like chemistry, biotechnology, earth, astrophysics, etc.
Use cases:
a. A typical scientist would like to search the data base in the following way:
"I am interested in an Application-specific science gateway that is in production in the area of astrophysics. Using the subcategories she can quickly to the right set of gateways containg only a small number of gateways that all satisfies her requirements."
b. A biotechnology gateway developer would like to see if there is any generic gateway framework that is in production and from which she can build a SG instance.
4. Free tags should be available. These could be used by the Science Gateways software for example to:
a. Define each application a specific SG is offering (Science Gateways can offer access to one or more software packs)
b. Provide a better categorization of a SG software register. For example, which enabling technology is the SG based on? Later on, this information will be valuable to assess how different technologies are being uptake by SG developers. We are aware of the AppDB gadget and that is easy to build customized AppDB queries.
5. An AppDB software (e.g. SG related entries) should be able to cross-reference with other software already in AppDB. For example, if a SG is based on the WS-PGRADE/gUSE enabling technology, then somewhere in the description of the SG this could be referenced.
a. We are aware that AppDB uses permalinks
b. Are there other ways this could be accomplished?
Status
- Recommendations already recorded as a requirement in the EGI RT system (#4520).