You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stumbled upon an interesting case today with the latest contribution from TUHH (#93). As it turned out, the file was already enriched with all relevant metadata (in the old schema, though)
Here are the first 3 entries from the original file:
And here is the result from the automated metadata enrichment. As you can see, there are several differences in the publisher and issn columns (journal_title also often differs, although not in these first 3). On the other hand, the original file contributes much more information in the license column, where crossref will often report "NA" values.
Question is: How should we proceed in such cases? Where should crossref (or Pubmed or DOAJ) imports overwrite existing data?
As for the current task, I decided to replace the journal_title, publisher and ISSNs with crossref imports but keep the license column.
The text was updated successfully, but these errors were encountered:
Stumbled upon an interesting case today with the latest contribution from TUHH (#93). As it turned out, the file was already enriched with all relevant metadata (in the old schema, though)
Here are the first 3 entries from the original file:
And here is the result from the automated metadata enrichment. As you can see, there are several differences in the publisher and issn columns (journal_title also often differs, although not in these first 3). On the other hand, the original file contributes much more information in the license column, where crossref will often report "NA" values.
Question is: How should we proceed in such cases? Where should crossref (or Pubmed or DOAJ) imports overwrite existing data?
As for the current task, I decided to replace the journal_title, publisher and ISSNs with crossref imports but keep the license column.
The text was updated successfully, but these errors were encountered: