Free web database maker software for linux

Web Reference Database is a bibliographic manager that can import and export references in various formats (including BibTeX, Endnote, MODS XML, and OpenOffice).
It can make formatted lists of citations in HTML, RTF, PDF, or LaTeX, and offers powerful searching, rich metadata, and RSS support
Enhancements:
- This release offers major function enhancements and bugfixes.
- Batch import from various bibliographic formats (including BibTeX, Endnote, RIS, ISI, and MODS XML) is now supported, as is import from a PubMed ID.
- An OpenDocument spreadsheet for use with OpenOffice.org can be exported, and formatted citation lists can be generated as HTML, RTF, PDF, or LaTeX. An SRU/W service and support for unAPI, OpenURL, and COinS metadata have been added.
- These allow the data to be used by the next generation of bibliographic clients.
- A new command line client is also included.

RPM Package Maker is a frontend for other linux tools in order to help linux users to create RPM packages quickly and easily.
Since version 0.8 minimal spec files are kept in:
/usr/src/packages/SPECS/mini
Enhancements:
- Small improvements and bugfixes

Wikidbase is an idea that combines the functionality of a database system and a wiki web application.
The wikidbase concept is based on the view that non-technical users of a database system (i.e. those who are the experts of the nature of the data they handle) should be able to create and evolve their database model over time (i.e. without paying a database expert over and over again to do it).
This is particularly relevant to non-profit and charity organizations.
Furthermore, since the designer of a conventional database system cannot foretell all future demands of the system, it is highly likely that a database model will be frozen too early, causing problems later on when the requirements of an organistion change - as they so often do.
A conventional database is a system for information storage and retrieval that is highly optimised through organisation of the data into a rigid model; as such, whilst being highly optimised, it is not easy for a non-technical user of the system to later change the model (e.g. to add or change fields, or tables), change reports and queries, or alter the data-entry interface.
A wiki is a website that allows non-technical users to easily edit the contents of webpages, allowing them to add images, alter styling, etc. A wiki can be likened to an unstructured database, since there is no predetermined modal for the information that will be stored, and so a wiki can be used to store highly flexible data - and lots of it - (wikipedia, a web wiki-based encylopedia, is a good example of this). Unlike a structured database, however, information held in a wiki can usually only be retrieved by string searches, and it is not possible, therefore, to retrieve structured information from the wiki (e.g. a list of phone numbers or email addresses for all staff members).
Wikidbase can be thought of as more than just a database, as a rich groupware application that will be capable of storing and organising all sorts of information (e.g. fully relational data, plain old information pages, files, images, media, semi-structured data, shared calendar type information, etc.). Wikidbase will be released as open source under the GPL licence (i.e it will be free).
Enhancements:
- Minor optimizations have been made and work begun on calendar-view enhancement and user authorization.
- The database model has been updated for future optimization.
- Some screencasts are available.

DMO stands for "Database of Managed Objects." This is a tool for documenting all objects within a data center.
Database of Managed Objects provides an object-based overlay on a MySQL database, with a Web-based interface, which allows new objects to be defined in a hierarchy.
Each object can have attributes defined, which are inherited by objects below in the hierarchy. Information can be imported in CSV or XML format, and reports can be produced in XML, CSV, PDF and HTML formats.
DMO uses PHP and MySQL to support documentation of all network and system objects within your computing environment. It offers a Web interface that enables easy navigation through objects, instances and attributes, with XML and access controls.
Enhancements:
- This is the first significant release of DMO for nearly two years.
- It works with Linux and Windows (XAMPP), but should work well with any LAMP stack including PHP4.
- New features include much more graphical viewing, as well as mapping objects onto maps with drill-down to additional layers of maps following dependency trails, a new Flash viewer for browsing through objects, and the ability to create chains of objects based on any attribute type (where any other object can be an attribute of any other object).

Irregular Operations Database is a project used for tracking flight delays.

Irregular Ops is a CGI script for intranet use to track irregular operations (flight delays) for scheduled airlines.

XAO::Web is a part of XAO open source web services suite. It allows to build dynamic web content using data, templates and external input.
The distinguishing feature of XAO::Web is in its modular design where almost every aspect of functionality can be altered and alterations can be re-used. No complex code is embedded in the templates which allows to upgrade code and templates separately or maintain multiple visual representations of the same functionality at the same time.
Installation
perl Makefile.PL
make
make test
sudo make install
Saying "install XAO::Web" from the CPAN shell is a good way too:
perl -MCPAN -eshell
install XAO::Web
Using CPAN shell is usually the best way because all dependencies will be resolved automatically.
If you do manual installation then XAO::Web depends on at least the following modules (look into Makefile.PL or just watch closely the output of `perl Makefile.PL for additional dependencies):
XAO::Base
XAO::FS
Digest::MD5
Error
MIME::Lite
Test::Unit
When you run "perl Makefile.PL" you will be asked for XAO::Web test database. That database is only used when you do `make test and it have to exist. It does not matter what is inside the database, it will be completely wiped out for each test case.
Normally the database should be the same that you have used for XAO::FS tests and in case of MySQL is usually test or test_fs.
The directory where templates get installed is the same that you gave to XAO::Base when you installed it. Normally that directory is /usr/local/xao -- we will assume that for the rest of the document.
Main features:
- Perl code is not mixed with templates. Templates can be normal HTML files if no processing is required.
- A specific site can replace or modify standard XAO::Web objects if required by overriding or extending their methods. You do not need to re-implement entire object to make a site specific change. In case of system object upgrade or bug fix there is no need to alter site-specific changes normally.
- Site can create any extension objects or embed third-party extensions as well.
- One server can serve arbitrary number of XAO::Web sites each with however extended functionality without creating any conflicts. That includes different modifications to the system objects for different sites.
- Not limited to Web environment, allows to build any dynamic content -- content of mail messages or reports for instance.
- Works with CGI or mod_perl (mod_perl is recommended for production grade sites).
- If used in mod_perl mode improves performance by using caching of configuration, parsed templates, database handlers and so on.
- XAO::Web is by default integrated with XAO::FS (see XAO::FS) as a database layer, but this is not a requrement -- if for any reason a different database must be used for a site it can be easily and gracefully achieved.
- Hosting providers can allow their customers to build very complex sites without allowing them to execute arbitrary code, by allowing to modify only templates.
Enhancements:
- Fixed a problem with Web.pm for mod_perl usage, introduced last minute just before releasing 1.06

TagCloud Maker Class is a class that takes a single dimensional array of terms and outputs a piece of HTML with each term wrapped in a span tag with an ID that you can define in your CSS.

TagCloud Maker Class script can be called either as an object or as a static class.

Check out the example page. The keywords from the sample page come from the last 30 entries of my blog. Ill admit I cheated and just open the database and pull them from there instead of trying to call my blog w/curl or fopen and parse it. (Although that would have been cooler.) I then ran each blog entry against Yahoos Term Extraction API to get the terms. Then I pumped that array into my new TagCloud maker. The important code you cant see from the index.php is below.


require_once(TagCloud.php);
$x = TagCloud::fetch_cloud($thisArray,...,tagcloud_,http://www.technorati.com/tags/%s);
$o = new TagCloud($thisArray,...,tagcloud_,http://www.technorati.com/tags/%s,10,weight,2);
$o->get_cloud();
$y = $o->output_cloud;

As you can see, I used 2 different methods of creating the 2 lists. The first is just calling the object::method statically with all the necessary parameters. This is by far the easiest way to use this class and unless you need something special, its the way I recommend. The second way it to instantiate an object. I pass all the variables into the constructor but you could just as easily use the setters to set them all. (dont know why you would but hey, I spent an extra 15 minutes creating getters and setters so use them, by all means use them!)