The social network of informal collaboration in financial economics shows how financial economists work together. Academics frequently discuss their work with their colleagues: at conferences, when holding a visiting position at another department, or in casual discussions with other faculty members around the water cooler.
They exchange new ideas, point to emerging trends, share new literature and critize each others work, all of which can be subsumed as social informal collaboration. Typically, authors acknowledge informal collaboration in a separate footnote in a published article. We use these acknowledgements to create the social network of informal collaboration in financial economics. It links authors and acknowledged commenters by undirected and weighted links. The network allows us to study network effects and the dissemation of information in a large scientific setting.
We set up this website because we thought our colleagues might be interested to learn about patterns of informal collaboration and see where they are in our data. And of course because we had fun setting up the website.
Co-Pierre is a Senior Lecturer at the African Institute of Financial Markets and Risk Management at University of Cape Town, a Research Economist at Deutsche Bundesbank, and a Policy Associate at Economic Research Southern Africa. He is working on financial and economic networks, agent-based modelling, and microeconomics of banking. The views on this website are not the views of Deutsche Bundesbank.
Michael E. Rose
Michael E. Rose has been a PhD student at the African Institute of Financial Markets and Risk Management at University of Cape Town since April 2015. He works on social networks in financial and economic applications. He has been visiting De Nederlandsche Bank and Deutsche Bundesbank in 2016 and is also a Research Affiliate at Kiel Institute for the World Economy.
This website is being developed using Flask and all the source code is hosted on a private GitHub repository. As soon as we make our data public, we make the repository public as well, so that everyone can suggest changes or report error issues. We also use Google Analytics (but without User ID feature) to learn about our visitor's behaviour.