X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=heikki%2FREADME-HEIKKI;h=05718861e702ee4607ce8fd91d4d41aec2ea3c20;hb=533ff0b399b62625ddd68e1a59cb34ef70795bf9;hp=77977e8b3107b619575abfddc462a4c1a6ff57a2;hpb=e0f2463e427ca3f445b92636bb90c36792e85a50;p=pazpar2-moved-to-github.git

diff --git a/heikki/README-HEIKKI b/heikki/README-HEIKKI
index 77977e8..0571886 100644
--- a/heikki/README-HEIKKI
+++ b/heikki/README-HEIKKI
@@ -18,3 +18,47 @@ Wed 20-Nov-2013 Make a script that tests ranking against yaz-zserver
 (as that is the default config). Mostly to have a script to build on later.
 
 Thu 21-Nov-2013. Start my own complete config
+
+Fri 22-Nov-2013. Adam defined a new sort type, relevance_h, and put it place
+in the code. Now I have a place to implement my stuff. Relevant places:
+ pazpar2_config.c:1020  - minor
+ session.c:1318 - call relevance_prepare_read also for my type
+ reclists.c:104 - parse params
+ reclists.c:166 - compare function (for quicksort)
+ relevance.c:417 - calculate score
+         (same function as for relevance, but with extra arg for type)
+
+The compare function compares positions, when sorting by Metadata_sortkey_position
+This loops through the records (in the cluster) and finds the smallest rec->pos
+and then compares those.
+
+Next: See if I can implement a round robin.
+ - clients.h declares int clients_count(void)
+ - rec->client is a pointer to the client, but we don't have an ordinal from that
+   - keep an array of structs with the pointer, and locate the client number that way
+ - robin-score = pos * n_clients + client_num
+
+relevance_new_rec is called every time a new record pops up. One or more to count_word,
+exactly one to done_rec. That's where I can compare to the ranking of the previous
+record. struct_relevance is one structure I have for myself, global (for the user
+session), so I can keep my stuff in there, possibly an array of things for each target.
+
+I should also add stuff directly to the client, and to the record, as I need.
+
+Next: Plot the tf/idf scores against round-robin sorted order. Will be messy,
+but later when we get a target that returns sorted records, it will make sense.
+
+
+Wed 27-Nov
+Setting up multiple SOLR targets in the same pazpar2
+ - Add #999 to the z-urls, so pazpar2 won't merge them. Different number for each
+
+This URL shows the databases, with their numbers
+http://lui.indexdata.com/solr/select?q=database:*&facet=true&facet.method=fc&facet.field=author_exact&facet.field=subject_exact&facet.field=date&facet.field=medium_exact&facet.field=database&rows=0&facet.mincount=1
+
+Add this to the target defs
+<set name="pz:extra_args" value="fq=database:4902">
+
+After this, it should be possible to get records from different databases, some
+with many records, some with a few. This is a good testing ground for merging
+rankings! Test first with a round-robin, and plot the scores.