Commissioned Metadata Project -
Alright, I realize how unreasonable it is to expect you guys to work on v1.7 stuff before you even get 1.6 into beta.
I probably don't have enough money to make this a reality so I'll withdraw this and wait for your development to naturally progress.
I'll be back when 1.7 is out 
I would like to pay to help fast track the development of the Metadata extension to moinmoin. I would not make any claim to these features being proprietary due to my financial assistance in development. I fully intend this metadata feature to go gpl, as planned. Acceptance of this offer will require the acceptance of the project roughly defined below.
Once these features are in a usable state, I would like to commission an implementation of this metadata and other technologies related to moinmoin for a proprietary, non-distributed setup of moinmoin and related softwares to include...
On every wiki page:
- 4 string fields
- 1 boolean field
- 2 floats
and on every user account:
- 4 string fields
- 2 floats
The floats would be generated internally, never shown to users. The string fields would be exposed to users via a custom theme, and would be available to be changed. The boolean field will be defined at the time of article creation.
Further, I would like to define, and have developed, specific search behavior, conditional to these variables.
First, In the same way moinmoin has two search functions, title and text, there should be two search functions dependent on the value of the boolean field. e.g. search articles with true, search articles with false.
Second, the searchable index should have the option to be limited to those articles where specific string fields match the corresponding string fields for each user. e.g. only search articles where articlestring4==userstring4
Third, the searchable index should have the option to be limited to those articles where article float values are within a certain range as compared to user float values. e.g.
userfloat1=x searches only where x-4 < articlefloat1 < x+4
Finally, after restricting the searchable pages as described above, a search on article text should be performed.
This, plus a few custom pages to aquire string values for users when they are not yet defined provides a technical skeleton for the proprietary modifications I would like to commission from moinmoin developers.
I would appreciate an opportunity to discuss this further with moinmoin developers.
I can be reached at <ryanfelder AT yahoo DOT com>
Comments
"Restricting" or "Limiting" search is usually done by adding an AND term to the search, so e.g. if you want to limit to pages with KEY equals VAL, then search terms would look like "KEY:VAL userterm1 userterm2 ..." and then it would only find results where KEY is VAL.
For some limited fields, this is already implemented in xapian search, so the task would be to extend and/or generalize this.
The float stuff is a bit harder, but can be done by filtering search results by this metadata value (I don't think xapian can do this).
Then, we should have separate metadata before beginning this (work on this has been done by HeinrichWendel in moin/1.7-storage branch, but we need to do some more work until this can get merged: ACLs, new backend that really stores data and metadata separately, migration script for attachments).
Finally, there is user interface stuff needed for handling metadata (and, in general: mimetype items).