[CollEc] New CollEc

[Düben, Christian]

I can come up with rankings and with an exportable text file. But that has to wait. Over the past few months I spent much of my time on GraphEc, CollEc and teaching and neglected my research. With multiple upcoming conferences and potential research visits, that needs to change. I have to spend the next weeks on research. My suggestion is to keep both versions of CollEc running for now and to postpone the official transition between versions until October. Until then, we could run the web application at e.g. collec2.repec.org to highlight the upcoming transition.

The text in the Shortest Paths tab mentions the potential existence of multiple shortest paths. And that is addressed by the choice between the binary case and three transition function cases.

Which shortest path is displayed in the Shortest Paths tab does not affect the computed centrality measures. For closeness the number of shortest paths between two authors does generally not matter. Only the distance between the two people is considered. And the code deriving betweenness internally computes all shortest paths, but only writes the resulting betweenness result to disk.

I know how it feels to spend multiple days on a bug. I faced such issues when fixing Shiny's internal reactivity.

Christian Düben
Research Associate
Chair of Macroeconomics
Hamburg University
Von-Melle-Park 5, Room 3102
20146 Hamburg
Germany
+49 40 42838 1898
christian.dueben at uni-hamburg.de
http://www.christian-dueben.com


-----Original Message-----
From: Thomas Krichel <krichel at openlib.org> 
Sent: Montag, 10. August 2020 14:31
To: Düben, Christian <Christian.Dueben at uni-hamburg.de>
Cc: CollEc Run <collec-run at lists.openlib.org>
Subject: Re: New CollEc

  Düben, Christian writes

> It does not have rankings.

  Rankings are the flesh and blood of RePEc. We need to have
  something like the current

ftp://ftp.repec.org/CollEc/CollEc.txt

  CZ uses this. 

> The shortest paths can be accessed through the Shortest Paths tab.

  I understand this, and I can access a path, but I'm warned that
  there may be many.

> But I did not yet implement a functionality to export them.

  I think we need to get that done.

  If I was more advanced with ArchEc, I would love to help.
  I just spend one week just fixing one bug ... and there are
  more. 

-- 

  Cheers,

  Thomas Krichel                  http://openlib.org/home/krichel
                                              skype:thomaskrichel