S LocationData table: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) mNo edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The '''s_LocationData''' table in [[CCMDB.accdb]] contains the possible values for the metadata for locations. See [[Location metadata storage]]. | {{DISPLAYTITLE:s_LocationData table}}The '''s_LocationData''' table in [[CCMDB.accdb]] contains the possible values for the metadata for locations. See [[Location metadata storage]]. | ||
== Data Structure == | == Data Structure == | ||
| Line 10: | Line 10: | ||
|| '''location_name''' || text || unique ID, name of the location in [[s_dispo table]] and [[Boarding Loc]] and on this wiki | || '''location_name''' || text || unique ID, name of the location in [[s_dispo table]] and [[Boarding Loc]] and on this wiki | ||
|- | |- | ||
|| ''' | || '''attribute_name''' || text || name of the attribute, e.g. "bed count"; there should be a wiki page for each of these to explain how they are used and how they tie into queries and reports | ||
|- | |- | ||
|| ''' | || '''attribute_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 | || '''Start_DtTm''' || date || when this location-attribute-value combination becomes active | ||
| 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 | * No longer applicable, we discussed today that we will need multiple start and end dates and that it maybe should be stored on wiki. | ||
--- | |||
* _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 | ||
| Line 32: | Line 35: | ||
[[Category: Data structure]] | [[Category: Data structure]] | ||
[[Category: S dispo table|*]] | [[Category: S dispo table | *]] | ||
[[ | [[Category: Location Information | *]] | ||
Latest revision as of 15:27, 17 May 2023
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_name | text | name of the attribute, e.g. "bed count"; there should be a wiki page for each of these to explain how they are used and how they tie into queries and reports |
| attribute_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: |