PKP Bugzilla – Bug 5396
Move reviewer interests to article_search tables
Last modified: 2010-06-28 11:48:10 PDT
We should move the reviewer interests to article_search tables (or some table adapted/abstracted from them) to allow for boolean searching of reviewer interests. See http://pkp.sfu.ca/support/forum/viewtopic.php?f=2&t=6072&p=23225#p2322
I've implemented this in a new table (interests) thats fairly generic, i.e. it uses assoc_type/ID for identifying users--So this could be extended to other keywords. This structure will work well for the advanced reviewer search in OMP, but I'm not sure how it will work for searching reviewer interests in OxS--I might have to look into indexing the table (or implementing what's going into OMP in OxS at the same time, e.g. filtering reviewers on whatever interests the editor selects). http://github.com/mcrider/pkp-lib/commit/9fb2fe9ac9d9cc467ca844b396366b9ed176bddf http://github.com/mcrider/omp/commit/44d6d41639f25312c955f3d16644af0dbd87ef3f http://github.com/mcrider/ojs/commit/54a929c698a2c132b98e1e23ee72eb9f0dbc3005 http://github.com/mcrider/ocs/commit/e019f42b87d8db291538b6770b329e4f9cc1455f
Pushed to official, now using the controlled_vocab tables for storage. http://github.com/pkp/pkp-lib/commit/3db25a4a686b6dc0d33d8557c4597e8f309b4417 http://github.com/pkp/omp/commit/28ab471381086e1a2475163340bb59e9cee83304 http://github.com/pkp/ojs/commit/f26c44e0f0dcbd4a4f5a09775509f48fae5d259f http://github.com/pkp/ocs/commit/15bc8efa575c03359deeee4ab608f5254c35b3fd
Matt, I'm not able to save my reviewing interests in either OJS or OCS HEAD at the moment -- the reviewer interests field appears, but no text that I add there appears to be saved.
Fixed... I forgot to port the latest small change from OMP to the other apps. FYI, the change was in the JS to automatically name the keywords (grouped as an array of hidden inputs) based on the keyword input's ID. So, $("#interests").tagIt({...}); Will create a keyword input control, and as keywords are entered, they are stored in 'interestsKeywords' (and can be accessed through the Form class using that name). They were previously named just 'interests', which wouldn't work if there are multiple keyword inputs on one page. http://github.com/pkp/ocs/commit/49185292b4614f5fe92fd2f1425e503c975301f2 http://github.com/pkp/ojs/commit/bef6942654732e9eaaca2a712e48148f3dd6d5d4