Topic 30: Changing for Use By to a Multivalued Table

fieldmuseum / EMu-Documentation

Field Museum documentation for EMu workflows, structural changes, and standardization.

14 stars 5 forks source link

Topic 30: Changing for Use By to a Multivalued Table #1116

Open rondlg opened 5 months ago

rondlg commented 5 months ago

DISCUSSION POINTS: Makes more sense to combine the for use by role with the role field into a single multivalued table so that they don’t become disconnected.

TraForUseByRef_tab
TraUserRole_tab

rondlg commented 5 months ago

DECISION(S): Merge

Data Changes Doc : Pre new development: Post development: row 43