S LocationData table: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 22: | Line 22: | ||
{{Todo | {{Todo | ||
| who = Tina | | who = Tina | ||
| question = locationData | | question = locationData | ||
* the process to import from wiki should run a consistency check on the start and end dates to ensure there is no overlap of same attribute | * _dev_CCMDB - the process to import from wiki should run a consistency check on the start and end dates to ensure there is no overlap of same attribute | ||
* _dev_CFE - include this in the import of s_ tables at startup; there was a second s_ table to pull into CFE, emailed Julie for which one | |||
| todo_added = 2022-02-10 | | todo_added = 2022-02-10 | ||
| todo_action = 2022-02-10 | | todo_action = 2022-02-10 | ||
Revision as of 14:13, 10 February 2022
The s_LocationData table in CCMDB.accdb contains the possible values for the metadata for locations. See Location metadata storage.
Data Structure
| field | type | description |
|---|---|---|
| location_name | text | unique ID, name of the location in s_dispo table and Boarding Loc and on this wiki |
| attribute | text | name of the attribute, e.g. "bed count" |
| value | text | value of the attribute, e.g. "15" in case of bed number |
| Start_DtTm | date | when this location-attribute-value combination becomes active |
| End_DtTm | date | when this location-attribute-value combination stops |
End_DtTm is not needed for complete info, and in fact could become inconsistent, but it will make it easier to use this data in queries. Since updates will be rarer than use we decided to include the End_DtTm explicitly.
|
locationData
|
|
Related articles
| Related articles: |