Requirements for Neighborhood Data
General Information
- The import file can have multiple neighborhoods, with different names.
Hood Import
- Each row must represent a single neighborhood.
Identify a Building
The import uses the following columns to identify a building and you must include both or one of the columns in the import.
- Building Number
- Building
Identify a Floor
The import uses the following columns to identify a floor and you must include both or one of the columns in the import.
- Floor Number
- Floor
Identify an Neighborhood
The import uses the following columns to identify an org unit mapping and you must include either all columns or one of the columns in the import:
- Building Number
- Building
- Floor Number
- Floor
- Hood
Data Dictionary
The table below lists the columns and the required columns and values are shown in blue text.
|
Column Name |
Description |
Data Type |
Max Length |
Column Required |
Value Required |
Unique in this file |
|---|---|---|---|---|---|---|
|
Building Number |
Unique identifier for the building. |
Text |
20 |
Yes |
Yes |
Yes |
|
Building |
Name of building e.g. 'Headquarters', 'Park Tower', '210 Park Ave'. |
Text |
150 |
Yes |
Yes |
Yes |
|
Floor Number |
Unique identifier for the floor e.g. 02. |
Text |
20 |
Yes |
Yes |
Yes |
|
Floor |
Name of the floor e.g. Ground Floor, Mezzanine, 2nd Floor, 3rd Floor. |
Text |
20 |
Yes |
Yes |
Yes |
|
Hood |
Allocate the workpoint(or space) to a hood. |
Text |
50 |
No |
No |
Yes |
|
Workpoints |
Number of workpoints. |
Integer |
32-Bit |
No |
No |
Yes |
|
Administrator Comments |
Any comments from the Administrator. The comments will display in the Neighborhood form's Overview tab, refer to Neighborhood Details Form. |
Text |
100 |
No |
No |
No |
|
Wayfinding Comments |
Comments for a room or workpoint that will show in the Wayfinding interface. |
Text |
100 |
No |
No |
No |
|
Tags |
An existing tag can be applied to a team. For more information, refer to Tagging. |
Text |
200 |
No |
No |
No |
| Any custom fields? |