REQUIREMENTS:

1. You must have the ability to create a database and grant full permissions on a MySQL server.
2. Write access to your web server's documents folder.
3. (It is assumed you have a working MySQL database server and PHP-enabled web server.)
4. Any operating system capable of running the above.
5. WIKINDX uses PHP sessions - ensure that these have not been disabled in php.ini.
   

NB
1/ WIKINDX will neither create the database nor grant appropriate permissions (GRANT ALL) - you must do this manually then edit config.php. PHPMyAdmin users (for Windows users, this utility for managing MySQL databases comes with WAMP) can find instructions for this at http://wikindx.sourceforge.net/.
2/ Some PHP distributions (notibly on Linux Mandriva) come without PHP extensions that are standard on other distributions. Importantly, the XML extension must be enabled on Mandriva (and possibly other Linux distributions).
3/ The standard PHP/Apache installation has a memory_limit of 8 Megabytes configured in php.ini. In most cases, this is sufficient to run WIKINDX. However, there are some instances (PHP/Apache installations with particular configurations or extras, for example) where this memory limit may need to be increased. An indication of this is typically an unexpected blank page following a WIKINDX operation or, if error reporting is turned on (see wikindx3/config.php), an error message detailing a lack of memory. If either of these symptoms occur, increase php.ini's memory_limit in steps of 4 Megabytes until it is working again.

INSTALLATION:

1. Unpack and untar wikindx-xxxx.tar.gz or wikindx-xxxx.zip to a web server documents' folder of your choice.
   NB - It is important that the 'files/', 'attachments/', 'papers/' and 'styles/bibliography/' folders and the XML files within the 'styles/bibliography/xxx/' folders are writable by the web server user (usually 'nobody'). On *NIX, untar with the -p option to ensure that permissions are preserved (these permissions are 0777 to ensure that WIKINDX runs out of the box - you may wish to make them more secure).
2. Edit config.php as per the instructions in that file. If you have an existing v2.x database and wish to use that database with v3.1, then you should edit config.php to match the existing database. The first time you run WIKINDX v3.1, the database will be automatically upgraded. AS ALWAYS, YOU SHOULD BACK UP YOUR DATABASE FIRST.
3. Run WIKINDX through your web browser and complete the instructions there to finish the installation. Make sure you do this immediately as the first user will be prompted to enter a superadmin username and password.
4. Have fun!

NOTE:

1. If you have an existing WIKINDX v1.x database, you must still create a new database for v2 since the database structure has significantly changed. Within your WIKINDX web configuration it is then possible to transfer and convert this v1.x database to v2. (This option has been dropped in WIKINDX v2.2 with the assumption that there are few if any of these users left. If you do wish to convert a v1.x database, upgrade to WIKINDX v2.0.1 first, convert the database, then upgrade to a higher version.)
2. The files/ directory is used for the temporary storage of RTF, RIS, Endnote, BibTeX and other files for the user to download. The scripts within WIKINDX will mark these files for deletion after $WIKINDX_FILES_DELETE seconds have passed (see Admin|configure) since their last modification. This doesn't necessarily mean that they will be immediately deleted: they will be deleted the next time someone exports a file.
3. Language packs are available as separate downloads from the sourceforge site. They act like plug-ins so simply extract them (with their directory structure) to the languages/ directory to make them instantly available.
4. Bibliographic style packs are available as separate downloads from the sourceforge site. They act like plug-ins so simply extract them (with their directory structure) to the styles/bibliography/ directory to make them instantly available.
5. Since v3.2, there is an optional RSS feed. See README_RSS for details.