:TITLE:Development roadmap :INC:index :SUB:Some notes This TODO list is just a place for Yorhel to write down his plans and ideas for the upcoming versions of VNDB. Keep in mind that probably not everything written down here will actually see the light of day.

The full source code of the site is available on a git repository, you can use it to track changes to the code or even to run your own version of VNDB.

There is a beta version of VNDB available for testing. New features will be implemented there and tested before getting uploaded to the actual website. Everyone is free to play around and use that beta version as a sandbox. Keep in mind, however, that all changes you make on the beta are not permanent, and will be reverted whenever the beta is synchronised with a more recent version of the database.

Feel free to comment about the TODO list and to suggest new features on the discussion board or on IRC.

Last update: 2009-02-12

:SUB:Next version (2.3)
  1. Catalog numbers for releases (done)
  2. Changing release statusses from VN page using AJAX (done)
  3. Random VN quotes on footer of every page (done)
  4. Platform icons on homepage (done)
  5. Tagging system (...will take a while)
:SUB:(Hopefully) soon
  1. Advanced notification system
  2. More VNList filters & stats
  3. Release calendar
:SUB:Later
  1. Filters on /v/* to exclude blacklisted and/or VNs on a users list from the results
  2. Producer relations
  3. VN Staff and Character database
    Probably not going to make it into VNDB, unless someone wants to be in charge of this
  4. Soundtrack listing
    Work together with VGMdb.
  5. Manga relations
    Looking for a good and comprehensive manga database fetch info from
  6. Reviews
  7. Walkthroughs/guides?
    Let each user maintain his own walkthrough, or just one collaboratively edited walkthough per VN?
  8. Image quality/resolution field to releases
  9. Some kind of minimal API for the hardcore VNDB fans (most likely using the JSON-RPC 1.0 Specification)
  10. Automatic uploading of cover images from a URL
  11. Scans of the packaging for releases
  12. Store which fields have been changed for revisions using one-character-code indicators
  13. Improved platform for fan translations (separated from releases)
  14. 'currently down/offline' flag for official website links
:SUB:Technical things that need improvements

(I'm not expecting anyone to understand this, just random notes for myself)

  1. Set PostgreSQL charset to UTF-8
  2. Make use of PostgreSQL's fulltext search functionality to power the VN search
  3. Proper implementation of the 'hidden' flag for v/r/p entries
  4. Let VNDB and Multi communicate via SQL (and use schemas to separate the tables)
  5. More secure login system
  6. Use PostgreSQL stored procedures to insert revisions (using composite types, arrays, etc as arguments)
  7. Update the users.c_changes column on hiding/unhiding an item