For single-verse ranges:
Order by the sum of three fields:
VID
Sub-position-index (0..40) that takes the highlighted-starting-position of the text-portion relative to the bigger text.
Offset - which is a modifier that changes based on moderator-re-ordering input.
For multi-verses:
if the query-range fully covers the lwc-range, put them at the start of the lwc-range, ordered by the overlap-coverage percentage, before the detailed individual verse-notes (as above)
if the query-range does NOT fully cover the lwc-range, put them at the bottom of the query-range, ordered by overlap-coverage percentage.
Example
lwc1=v1-v21 (hele hoofstuk)
lwc2=v2-v3
lwc3=v1-3
lwc4=v1-2.
Dan is daar nog 20 detail nodes vir elke vers.
Die order moet dan wees, vir 'n query of v1-v3:
lwc3 eerste, omdat dit 'n multi-vers is, en dit 100% match met die query.
lwc4, omdat die starting point dieselfde is, en omdat die 100% met die query overlap, maar die comment se verhouding met die query is laer op 66%.
20 x detail nodes van vers 1;
lwc2, omdat die starting point v2 is, en die overlap is 100% vir die res.
20 x detail nodes van vers 2;
20 x detail nodes van vers 3;
lwc1 - omdat die overlap nie 100% is nie, en dit dus ook gedeeltelik irrelevante goed bevat (ordered by overlap)
NB - vir multi-vers gaan ons nooit custom re-ordering kan doen nie....
For single-verse ranges: Order by the sum of three fields:
For multi-verses:
Example lwc1=v1-v21 (hele hoofstuk) lwc2=v2-v3 lwc3=v1-3 lwc4=v1-2.
Dan is daar nog 20 detail nodes vir elke vers.
Die order moet dan wees, vir 'n query of v1-v3:
NB - vir multi-vers gaan ons nooit custom re-ordering kan doen nie....