Jonathan Brier

Crosscheck of import data: Crossref display vs json vs Import - In this case the JSON had more data than displayed in terms of number of authors while the wikidata...

> Crosscheck of import data: Crossref display vs json vs Import - In this case the JSON had more data than displayed in terms of number of authors while the...

A much broader data handing issue than #2731 is a Crossref trove of unescaped items: &,   and so many more https://search.crossref.org/search/works?q=%26amp%3B&from_ui=yes Issue reported to Crossref asking to flag in...

https://github.com/WDscholia/scholia/issues/2726#issuecomment-3607349056 Crossref has identifed some parsing issue on their side for escape and it will fix some of the escape issues.

> I have looked on the first one and that also has resulted in a double entry in Wikidata https://www.wikidata.org/w/index.php?title=Q56592178&redirect=no and https://www.wikidata.org/wiki/Q34370207 I have fixed some of it: https://www.wikidata.org/w/index.php?title=Q34370207&diff=2411334406&oldid=1808308676 but...

@fnielsen It was just reported back to me at least one of the et al instances may be by practice and across an entire journal. From my report with Crossref...

@larsgw Sorry, [P393](https://www.wikidata.org/wiki/Property_talk:P393) might make more sense given the type constraints applied. I didn't see that one when I stumbled across [P9767](https://www.wikidata.org/wiki/Property_talk:P9767).

Well I just tested the version properties on one of my papers and the P9767 at least with the current constraints is flagged just like the software version while the...

There is a broader data quality issue for escaped characters in Crossref metadata than just & ... I've reached out to Crossref if they can scan for these. I've also...

[10.21980/j8ph1b](https://doi.org/10.21980/j8ph1b) is another example, but this looks like it may be a data migration issue as the as the article is from 2022 and the 10.21980 was migrated from DataCite...