Hi Joe:

On Mon, 10 May 2010, Joe Blaylock wrote:
> I've pushed the branch 'citesummary2b' (head is commit number 7c36d).
> It adds the calculation of h values to the citesummary stats page.

Some comments:

* We need to graphically separate h-index numbers from the breakdown
  numbers, currently they are visually mixed up.  For example, we could
  introduce a new leading text in bold that would say ``Additional
  Metric'' or something of the kind before printing the h-index and the
  self cite numbers.  Alternatively, I guess I would simply display
  h-index after Average and before Breakdown sections, and print it in
  bold.  It is a summary quantity, so we can as well display it next to
  other summary quantities, before doing the detailed breakdown.

      Total number of citations:        5       5
      Average citations per paper:      1.7     1.7
      h-index [?]:                      2       2
      Breakdown of papers by citations:
      Renowned papers (500+)            0       0

  Also, I would use the full term `h-index' instead of `h'.

* To make a better connection to the other existing cite summary
  template functions, please call it tmpl_citesummary_h_index(), though
  you may need to modify tmpl_citesummary_overview() concerning the
  Breakdown output line and stuff.

* Indeed I think it would be good to create a new Invenio help page,
  such as /help/citesummary, that would explain stuff, instead of
  pointing to SPIRES, be it only for the fact that the Invenio cite
  summary pages use slightly different terminology, and in order not to
  drive users away from the site where they are, even more so because
  INSPIRE and SPIRES UI is very similar, so they may get confused as to
  where they land.

* Instead of underlinking the h, I'd prefer putting a small `?' after
  the text (as in: h-index [?]) that would bring people to the proper
  help page section.  This would be useful for other terms such as
  ``citable papers'' as well.  We already use this
  question-mark-links-to-help technique to some extent, mostly on the
  admin pages like `/admin/bibharvest/oaiharvestadmin.py', but we have
  not generalized it quite enough yet.  Maybe it is time we start doing
  so, and not only for the admin pages, but for the user pages too.

Best regards
--
Tibor Simko

Reply via email to