support citations for datasets about lter-core-metabase HOT 3 OPEN

(c) A cross-reference table

DataSetID integer NOT NULL,
pub_id varchar NOT NULL,
relationship varchar NOT NULL,
notes text,
CONSTRAINT data_pub_xref_pk PRIMARY KEY ("DataSetID",pub_id,relationship)

• I include relationship in the pk because, theoretically, a paper could appear in more than one of those elements. Not likely, and I will entertain argument to remove that from pk.
• All three of those pk columns must be a controlled vocab. The relationships can be in a CHECK constraint for the three elements you mentioned, plus 'undefined' for wiggle room. Obviously the parent for DataSetID table DataSet. The parent for pub_id will be whatever that site uses locally. That does present an install challenge.
• Because we want to keep our core-mb at 4th normal form.
• Because the biblio schema already supports pub_id (although I forget the name of that column, but you get the idea.) A site may have another schema for pubs, as MCR does, but still want to use that schema together with core-mb.
• How the citation text string or pieces are stored is outside the scope of core-mb and within scope of a biblio schema. Ideally that biblio schema is within the same database as core-mb so it is accessible to VIEWs and and FKs.

from lter-core-metabase.

Side comment: usageCitation within the EML is not how I want to manage that information. External tools allow us to add such relationships after a revision of a dataset gets its doi minted. You can see how, otherwise, one has a chicken-and-egg conundrum.

from lter-core-metabase.

I see your point about usageCitation.

How would you enforce (0, 1) between a dataset and a publication for referencePublication?

from lter-core-metabase.