Some Profiles do not load publications (no Bibliographic section)

[asuccurro]

See e.g.:

https://www.profiles-ngs-cn.uni-bonn.de/display/275638
https://www.profiles-ngs-cn.uni-bonn.de/display/275639
https://www.profiles-ngs-cn.uni-bonn.de/display/39915
https://www.profiles-ngs-cn.uni-bonn.de/display/39920
https://www.profiles-ngs-cn.uni-bonn.de/display/39919

...

[faubulous]

The reason why there were no updated publications since August 7 is most likely an error in the keyphrases.txt file of an imported dataset. The first line was %% which means an empty keyphrase. The Profiles RNS import scripts probably stopped after this line which means that the system had no seed keyphrases to look for publications. I will create a new issue for the Profiles RNS Manager application to ignore empty keyphrases upon import.

With the other publications it seems to be a bit more complicated:

39915: He has published for University of Bonn which is included in the keyphrases for seed publications. However, no publications match any of the seed keyphrases.
39920: There is no publication on PubMed that could be linked to her profile as she has never published for the organization that is mentioned in her affiliation.
39919: I also assume that Pofiles RNS has no matching keyphrase for his affiliations.

[faubulous]

I made a query to list all profiles that have no publications in order to be able to judge if changes to the keyphrases actually made an effect. Here's the list of all profiles without publications:

https://www.profiles-ngs-cn.uni-bonn.de/display/39915
https://www.profiles-ngs-cn.uni-bonn.de/display/39920
https://www.profiles-ngs-cn.uni-bonn.de/display/39919
https://www.profiles-ngs-cn.uni-bonn.de/display/39923
https://www.profiles-ngs-cn.uni-bonn.de/display/39901
https://www.profiles-ngs-cn.uni-bonn.de/display/364501
https://www.profiles-ngs-cn.uni-bonn.de/display/364503
https://www.profiles-ngs-cn.uni-bonn.de/display/364508

[faubulous]

According to Nic Brown from the Harvard Profiles RNS team this is an internal issue where the disambiguation engine cannot handle multiple affiliations. A fix was developed and is being integrated into the next release in about 3 weeks from now.