IA2 developed Software:
Contact: S. Zorba
APOGEO (Automatic POrtal GEneratOr) is a tool that automatizes the creation of web interfaces for querying astronomical archives.
An administrator performs a configuration process, guided by a graphical wizard and then the application is able to generate a war package that is ready to be deployed on an application server (like Tomcat or GlassFish).
Generated applications support following features:
- Query the astronomical archive retrieving metadata selected by the user;
- Enable or not file download to the users according to the configured data access policies;
- Asynchronous creation of tar files to allow users downloading multiple files;
- Download of tabular data using the VOTable standard;
- Interoperability with external applications using the SAMP IVOA standard;
All new IA2 archives will be developed using APOGEO.
This tool is currently under development.
How it works
A preliminary configuration step consists in creating a TAP_SCHEMA, a particular schema defined in VO Standards for storing metadata about the astronomical archive. This can be done using the TAP_SCHEMA Manager application.
Then the portal administrator can use the PortalGenerator Wizard, that guides he or she during the configuration process. The administrator logs in into the PortalGenerator application and then can modify an existing portal configuration or create a new one.
The first step consists in defining connection strings for accessing the TAP_SCHEMA and the astronomical archive database, then the user has to select a main table, that will be used by the generated portal in the FROM clause of its SQL queries. The user can also select one or more secondary tables and how should they be joined on the main table.
Each portal needs to have a main grid, but other secondary grids can be added. The secondary grids will be placed into a tabbed panel that can be optionally activated, allowing an advanced search mode. This has been used for implementing searching on single telescope instruments, but a grid isn’t bind to a specific table, so other uses of this feature are possible.
Other optional settings include:
- specification of data access policies (for managing private resources);
- logging settings (logs are saved into a dedicated database table);
- files retrieval configuration (by path on physical disk or by URL);
- login system settings (using a set of LDAPs or Shibboleth - this part is currently a work in progress);
In the final step of the wizard there is a button "Generate site" that create a war package. This file can be downloaded and deployed on an application server.
Currently we support GlassFish and Tomcat but other application servers can be supported including proper libraries.