Tired of the academic grind, but still want to make a difference? Join @CrossrefOrg as a Principal R&D Developer where there is no REF and you don’t need to worry about your IF, but you’ll still make a big impact building Open Scholarly Infrastructure! https://t.co/chLljAXLHB
Come help @CrossrefOrg design and build a new generation of open scholarly infrastructure. We are hiring a Principal R&D Developer. https://t.co/chLljAXLHB
.@SDProc will be online following @emnlp2020's announcement today. Workshop date moved to *Nov 19*. Updates to changes to #sdp's submission deadlines will be announced. #clscisumm#laysumm#longsumm shared task registrations https://t.co/7NBD5hnlHz to remain open till April 30
@aarontay@CrossrefOrg Yes. "doi-asserted-by" tells you who provided "DOI" field for this reference: either the publisher (and we don't need to use any matching algorithm), or Crossref (using Crossref's matching algorithm).
@aarontay@CrossrefOrg "unstructured" field is just the input for the matching, the string representation of the reference. When there is "doi-asserted-by" = "crossref", ref's "DOI" field contains the target DOI found by our legacy matcher.