TYPO3 CMS is a Web Content Management System which features automatic creation of navigational menus, headlines, and other dynamic graphical elements, automatic conversion and scaling of images, the ability to present different templates based on variables such as client browser or country code, support for multiple templates on a site, and a built-in password-protection option. Pages can be timed to be shown on a certain date, be hidden on a certain date or just temporarily hidden. TYPO3 supports search in SQL-databases and redesigning of a website at once is just a matter of creating a single new template.
Permission Record Information Machine (PRIM) delivers database connectivity via a web browser. Users can have different database permissions (e.g. create tables, modify tables, etc.). PRIM has built-in database analytical tools such as graph displays, reporting, etc. English and Chinese (Big5) language support.
JWAA is a software framework for building dynamic Web applications as networks of first-class Java objects. XML is used for representing information normally coded as HTML. The XML files are automatically reloaded when they change. It has a "persistent forms" feature in which form data automatically persists in the database such that fields behave like pieces of paper that automatically preserve what's written on them. This default behavior is easily overridden. Invalid links are reported at XML load time via the browser, and are also recorded in log files.
OpenTicket functions as an incident manager, handling trouble-tickets and providing a mechanism for the resolution of all incidents. More specifically, openTicket serves as the Service Desk interface and handles the life cycle of incidents and service requests. The focus of openTicket is speed and efficiency. Unlike other call-tracking tools which offer a plethora of text fields, pull-down menus, and associated data, openTicket's interface is stripped down as much as possible without sacrificing key information. The benchmark used to determine efficiency is the 30-second test. If you know the user's name and you know the issue, it should take no longer than 30 seconds from the moment you begin looking up the user to the moment the ticket (including all relevant information) has been created and entered into the database.
ERW (Entities and Relationships on the Web) is an innovative system for handling complex databases using a Web browser. It uses the most recent standards endorsed by the W3C to offer to the user a sophisticated environment, similar to a dedicated client. Moreover, the user interface is generated in a completely automatic way starting from a conceptual description of the database by means of an XML-based description language for entity-relationship schemata. From the same description, you can also automatically obtain diagrams and documentation. ERW can be used for content management, in particular when the data is structured along complex relations.