From d93d542adf9d26633b0f3cfa361277ca677c46f3 Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Wed, 24 Nov 2021 16:01:47 -0800 Subject: codespell fixes in proposals --- proposals/2021-10-28_grobid_refs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'proposals/2021-10-28_grobid_refs.md') diff --git a/proposals/2021-10-28_grobid_refs.md b/proposals/2021-10-28_grobid_refs.md index 3f87968..1fc79b6 100644 --- a/proposals/2021-10-28_grobid_refs.md +++ b/proposals/2021-10-28_grobid_refs.md @@ -59,11 +59,11 @@ attached reference-level key or id. We may want to do re-parsing of references from sources other than `crossref`, so there is a generic `grobid_refs` table. But it is also common to fetch both -the crossref metadata and any re-parsed references together, so as a convience +the crossref metadata and any re-parsed references together, so as a convenience there is a PostgreSQL view (virtual table) that includes both a crossref metadata record and parsed citations, if available. If downstream code cares a lot about having the refs and record be in sync, the `source_ts` field on -`grobid_refs` can be matched againt the `indexed` column of `crossref` (or the +`grobid_refs` can be matched against the `indexed` column of `crossref` (or the `.indexed.date-time` JSON field in the record itself). Remember that DOIs should always be lower-cased before querying, inserting, -- cgit v1.2.3