[Babase] revised ranker ready for testing
Jun Yang
junyang at gmail.com
Wed May 7 22:09:57 EDT 2008
Hi Tabby:
Just to be sure before I change the code---is the following what you want?
1. In general, we will turn off the check that requires ranking
start/end dates to fall on the beginning and the end of a month. In
other words, you can create rankings that span an arbitrary period.
(Note, however, that there is still a difference between the ranking
period and interaction matrix period---the former specifies whom to
include in the ranking, and the latter specifies the period from which
interactions will be counted. We do not enforce that the two periods
are the same.)
2. The interface will not allow you to save a ranking if its ranking
start/end dates do not fall on the beginning and the end of the same
month. (Currently the database design is hard-coded to assume that a
ranking must be for one specific month.) However, you can still save
the ranking to an XML file on your local drive. Furthermore, you will
be warned when creating a ranking that cannot be saved in the
database.
Does the above sound right?
--- Jun Y.
On Mon, May 5, 2008 at 2:07 PM, kfenn <kfenn at princeton.edu> wrote:
> Hi Jun,
>
> Thanks for all the updates you have made. I've been using Ranker the last
> two days and it is hugely improved. It seems the A code is only picking up
> that which it should.
>
> Unfortunately, I've found one issue so far that's still significant enough
> to keep me from being able to run the ranks:
>
> Ranker is dropping some individuals from the cumulative matrix I need to
> create for each group. The attached word doc shows an example of this: FAC
> disappears from the Jan-June matrix depending on the month of ranking I
> choose. (The problem seems to be Ranker only uses the individuals in that
> appear in the "Ranking" month, rather than incorporating all individuals
> from the "Interactions" date range.) It's not an option to skip the month
> of ranking, nor is it an option to input the start date as Jan and the end
> date as June...Ranker wants the start and end date to be in the same month.
> Can we make the program less "fool-proof" by allowing the ranking start and
> end date to NOT be within the same month? This seems like the only way to
> get around dropping individuals from a 6 month or 1 year long matrix. The
> database managers will just have to be careful not to try to save the
> rankings from cumulative matrices.
> Of course I'm open to any other possible workarounds.
>
>
> Thanks!
> Tabby
More information about the Babase
mailing list