more.zites.net

For the second exercise of my Information Retrieval course at the university I had to do implement a relevance feedback system - so I thought: Why not build it upon drupal's search?

So that's what I did. The result is a working proof of concept module, which you can find in my sandbox and test at the demo site.

The system has two operation modes: One that uses "implicit feedback" and one that let's the user give "explicit feedback". The implicit feedback mode just tracks which search results the user has viewed, takes these results as relevant to generate an optimised search query and shows the improved results to the user.

The explicit system works the same way, but provides some UI for users to mark results as relevant and non-relevant, as you can see on the screenshot:

You can test the system at the demo site, which runs in explicit feedback mode. Once you have provided three positive results as feedback the system makes use of the Rocchio algorithm to generate an optimised search query and redirects you to the improved search results.

I've just committed a major update to the pageroute module. I've reorganized the page types and created a new one: the node management type.

The node management page allows one to add/edit/delete nodes from a configurable content type. It shows a themeable list of already created nodes and allows editing and deleting if the user has access.

The node management page type was the last important piece missing for nodeprofiles: A userfriendly way to create several nodes of the same type.

I've separated the modules into own projects, as they are not only for nodeprofiles useful.

Now there are the following drupal projects:

Node Profile
Node Family
Views Fusion
Pageroute

I've created an updated version of the firefox search plugin. (there was already a plugin which still used drupaldocs.org and so was broken)

additional to the updated HEAD plugin i added a plugin for 4.7.

i've started development of the node relations module, i called it nodefamily module.

As the module might be useful not only for profile nodes, I've written it generally, so that it may be used without nodeprofiles at all.

i started with the development of the usernode module, which cares for creating/deleting a node, whenever users are added/deleted - so other modules can rely on that a node exists for each user.

it already does its job, however the views integration is still missing.

I've just created a project page on drupal.org:
link

I decided to call the project: nodeprofile

-fago

I'll try to work out a rough implementation proposal here.

user node-type

Its necessary, that for every user automatically exists a node in the system. A module has to care for creating/deleting this node, whenever users are added/deleted - so other modules can rely on that a node exists for each user, if the module is activated.

I've got a google Summer of Code project :) (what's soc?)
Of course, Drupal is my mentoring organisation. My project is:

Node Profile Module and CCK

This drupal module will build user profile's as nodes, which opens the opportunity to use the Content Construction Kit (CCK) (view full project description).