Tmp Project Collection: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
The Critical Care and Medicine Database has a flexible method of quickly adding additional values required for temporary projects.  
The Critical Care and Medicine Database has a flexible method of quickly adding additional values required for temporary projects.  


For a list of projects we have collected, see [[:Category:Project]].  
For a list of projects we have collected and their collection instructions, see [[:Category:Project]].  


{{Discuss | who=Tina | question=Something I need to write up one day...}}
== Storage as attribute-value groups ==
Adding an actual new field to our database is not trivial, so in to get maximum flexibility our temporary project data is stored in attribute-value groups rather than in new fields for each project. The [[L TmpV2 table]] stores the data.
* [[L TmpV2 table|L TmpV2]].project stores the project (or attribute name); there is no tight convention; but a lot of projects only need one entry but some need more, and for those two similarly named project entries will be used.  
* [[L TmpV2 table|L TmpV2]].item contains the value for that project
* there are also a boolean, integer, real and notes field in each record of [[L TmpV2 table|L TmpV2]] that can be used to store additional data
The '''project''' and '''item''' fields are limited to entries in [[S tmp table]], which are supplied in a drop-down.  


[[Category:TmpV2 | *]]
[[Category:TmpV2 | *]]

Revision as of 15:41, 30 October 2018

The Critical Care and Medicine Database has a flexible method of quickly adding additional values required for temporary projects.

For a list of projects we have collected and their collection instructions, see Category:Project.

Storage as attribute-value groups

Adding an actual new field to our database is not trivial, so in to get maximum flexibility our temporary project data is stored in attribute-value groups rather than in new fields for each project. The L TmpV2 table stores the data.

  • L TmpV2.project stores the project (or attribute name); there is no tight convention; but a lot of projects only need one entry but some need more, and for those two similarly named project entries will be used.
  • L TmpV2.item contains the value for that project
  • there are also a boolean, integer, real and notes field in each record of L TmpV2 that can be used to store additional data

The project and item fields are limited to entries in S tmp table, which are supplied in a drop-down.