Reason for this PR
As seen in #67 , our data often contains multiple author entries referencing the same physical person. Some of these Entries have more information attached to them than others. Examples include missing information regarding Affiliation and ORCID.
Changes in this PR
This PR extends the CrossRef prefill-cache step by accumulating information from different Author objects representing the same physical person. A combination of given, family and name is used to uniquely identify authors, meaning that Author objects with the same name will be seen as representing the same physical person. For those objects, the affiliation entries will be accumulated. An oRCID entry will be set to the accumulated object if it is found in any of the matching Author objects.
The same logic is applied on-the-fly by adding a new AuthorsCache to the WorksCache. On every WorksCache.set it will update the accumulated author information from the new publication, and on every WorksCache.get it will retrieve the latest accumulated author information and attach it to the returned Works object.
This PR also includes a freshly generated version of the works-cache.json file.
This PR also contains a (currently inactive) approach to adding ORCID links to author names in the ReuseMetrics.vue page. However, this feature has currently been deactivated because it breaks the text filter of the author-name column, which is afaik not acceptable behavior.
Reason for this PR As seen in #67 , our data often contains multiple author entries referencing the same physical person. Some of these Entries have more information attached to them than others. Examples include missing information regarding Affiliation and ORCID.
Changes in this PR This PR extends the CrossRef
prefill-cachestep by accumulating information from differentAuthorobjects representing the same physical person. A combination ofgiven,familyandnameis used to uniquely identify authors, meaning thatAuthorobjects with the same name will be seen as representing the same physical person. For those objects, theaffiliationentries will be accumulated. AnoRCIDentry will be set to the accumulated object if it is found in any of the matchingAuthorobjects.The same logic is applied on-the-fly by adding a new
AuthorsCacheto theWorksCache. On everyWorksCache.setit will update the accumulated author information from the new publication, and on everyWorksCache.getit will retrieve the latest accumulated author information and attach it to the returnedWorksobject.This PR also includes a freshly generated version of the
works-cache.jsonfile.This PR also contains a (currently inactive) approach to adding ORCID links to author names in the
ReuseMetrics.vuepage. However, this feature has currently been deactivated because it breaks the text filter of the author-name column, which is afaik not acceptable behavior.