another cross dependency: updateFrequency FK from DataSet to pkg_mgmt

[gastil]

If someone wanted to install only the lter_metabase schema, they would get errors for items that depend on things in pkg_mgmt, such as:

pg_restore: [archiver (db)] could not execute query: ERROR:  schema "pkg_mgmt" does not exist
    Command was: ALTER TABLE ONLY "DataSet"
    ADD CONSTRAINT "FK_DataSet_UpdateFrequency" FOREIGN KEY ("UpdateFrequency") REFERENCES pkg_mg...

[atn38]

How do people only install lter_metabase? Not sure if we have self-contained schemas as a goal.

…

On Tue, Oct 8, 2019, 14:50 Gastil ***@***.***> wrote: If someone wanted to install only the lter_metabase schema, they would get errors for items that depend on things in pkg_mgmt, such as: pg_restore: [archiver (db)] could not execute query: ERROR: schema "pkg_mgmt" does not exist Command was: ALTER TABLE ONLY "DataSet" ADD CONSTRAINT "FK_DataSet_UpdateFrequency" FOREIGN KEY ("UpdateFrequency") REFERENCES pkg_mg... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#79?email_source=notifications&email_token=AKAZD5RC6TSWFZZB4LUDXD3QNTQBHA5CNFSM4I6WLPX2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HQOEXHA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKAZD5TYONGHMJOO2TCQP43QNTQBHANCNFSM4I6WLPXQ> .

[gastil]

Discussion here with Mob, Li and Gastil reached decision: We want new mb users to have to install pkg_mgmt. Only a few columns in pkg_mgmt.pkg_state are required. We could arrange column order to place those to the left side of the wide table. pkg_state should be the parent of lter_metabase.DataSet since changes we want changes to Revision to cascade. Not much changes in DataSet in the life of a dataset whereas pkg_mgmt is the most oft edited table in the database. Datasets begin their life in pkg_mgmt in as status anticipated before they exist in DataSet.

We are uncomfortable with nickname and shortName both existing without an FK binding them to their dataset and between schemas. For human editors, this column is convenient for recognizing datasets. DataSet has title so if we do choose to remove from one table (rather than FK them), keep it in pkg_mgmt. What do others think?