Open LukasWallrich opened 1 year ago
Also, since you are giving such nice status updates, might it be worth including the number of duplications and potential duplicates? I imagine that that is something nearly every user will want to know right after running dedup_citations?
All great suggestions! I have now fixed most of these issues. Haven't added the N potential duplicates message yet - might want to make some improvements to manual dedup functionality first.
Copying two things here from a CiteSource issue:
When using dedup_refs, I encountered a few minor issues:
unique
is grouped, which can lead to issues in further analysis (e.g., when using summarise). Maybe betterungroup()
it before returning?Joining, by = "record_id"
is shown in between your status updates - maybe specifyby =
in all join calls?It would also be better practice to use
message()
rather thanprint()
for the status updates - for example when one wants to use ASySD in a Rmd document where the status updates are not very helpful.