Currently, this site supports three products - Remository, Glossary and Remosef. The first two are major "components" and can be used in any recent version of Joomla! or Mambo. They are also available for Aliro. Remosef is currently only available for Joomla! 1.0.x but is likely to become available for Jooma! 1.5+. If there is sufficient demand, it could also be adapted to suit Mambo.
Remository is a highly capable file repository for use within one of the supported CMSs (Content Management Systems - currently Joomla! or Mambo or Aliro). It can organise files into folders (described in the system using the generic word "containers") that can be nested to an arbitrary depth. Files can be uploaded or downloaded by site visitors, subject to constraints configured by the site administrator.
There are three different ways in which files can be held by Remository:
- The most flexible is to store the files in the CMS database, which means that operations such as moving a file from one folder to another does not involve an operation on the disk system. Also, the database is not prone to the file permission problems that can create difficulty in some hosting situations, nor is it affected by the pernicious PHP safe mode.
- Database storage can become difficult if the volumes are very large. This may run up against issues of maintenance (depending on the extent of access to the server) or against hosting policies. So files can alternatively be located in the file system on the web server.
- Remository can also make available files that are located elsewhere on the internet. These are known as remote files and are defined by a URI (Uniform Resource Identifier, for example http://remository.com/downloads/filespec/).
Visitors can browse the file repository, starting at the topmost folders. Or there is a search facility in Remository; also an optional search plugin that will extend the CMS site search to include the file repository. Subject to possible constraints set by the site administrator, someone browsing the repository will be able to download any selected file. Subject to constraints, they can also upload a file to the repository, where it will typically be authorised before publication.
Constraints are flexible, and are applied at the level of a folder. It is possible to say what is permitted for visitors or for users who have logged in. (Administrators always get full access). Or it is possible to define groups of users who have upload or download rights. The latest access scheme is extremely powerful and flexible. In addition to role based access, it is possible to impose rules such as a limitation on the number of downloads in one day.
Display of file information can be enhanced by the use of thumbnails. For image files, these can be generated automatically when a user first uploads the file. Or an image file can be uploaded along with the file. Thumbnails are automatically resized according to an administrator configurable specification into two sizes. One is used for the thumbnails, and the other (larger) size controls a popup that is available by clicking on the thumbnail.
If you want to build a collection of terms and definitions, you need the Glossary component. Terms can be a single word or a phrase, and definitions can be almost arbitrarily long. The glossary is accessible through the user or administrator interfaces, which allow the entries to be listed.
For the user, they can be split into alphabetic sections. There is also a search facility that will accept regular expressions, making it potentially very powerful. Users may be permitted to enter new terms and definitions, subject to the site administrator's settings of the Glossary configuration.
The administrator can also list the entries, and has the ability to filter the entries either on the term, with the option of regular expressions, or on the definition using word search and boolean options such as a word preceded by - meaning that the word must NOT be present in the definition.
While the Glossary component by default creates a single glossary, it can also support multiple glossaries, and additional glossaries are easily defined by the administrator.
To convert the URIs on your site to user friendly form (some think this is also Search Engine Friendly) the new version of Remosef is extremely powerful. It stores its information in the database and in a cache, and can apply sophisticated rules to the creation of the best possible URI. Typically, the rules either involve direct substitution for a "raw" URI or the use of regular expressions to transform URIs in a variety of ways.
Not hosted here, but also developed by Martin Brampton, aTicket is a simple but powerful support ticket system for small to medium web based operations. Tickets can be raised either by email or using a web interface, and they can be tracked just using the email address of the ticket owner along with the ticket ID. Multiple projects can be supported, as can multiple support people. More information on aTicket can be found at its dedicated web site .