Click on images to see them in full screen

Door Tablet TXT/CSV


The Door Tablet server interfaces with the world’s most common platforms: MS Exchange, IBM Domino and Google Calendar. There are cases where the scheduling system does not offer modern services or programming capabilities but is able to generate simple text files, containing room schedules.

The following will apply to this type of implementation:

  1. Read only - the system can read schedules and does not offer manipulation of schedules or the creation of bookings from tablets
  2. Source system shares a folder with the Door Tablet server where text files are deposited
  3. Text files need to follow format definitions as listed below
  4. Room records may be created automatically in Door Tablet if a special file named "roomlist.txt" using the "Synchronise" function

Server configuration
The setup is simple, just open the system profile and set the following fields. Please note that the "Read Only Appointments" will be automatically set for you and you cannot "un-set" it

Time Zones
The Door Tablet system works in UTC. When you post schedules you use your local time, for example 09:30. Door Tablet will need to convert your local time to UTC and this is done by you specifying the time zone in the system profile. So, if your server is installed in Calfornia, your setup would look like this:

Test your folder
You can easily test that the server can access files in the shared folder. And if you created a room list, the test will try to read the room list and report back, as follows:

And the result...

How to create files for use by Door Tablet
The server will read files in the folder you specify in the system profile. The folder may be local where the Door Tablet server runs but may also be a network share. The following rules apply:
  1. A special file named "roomlist.txt" may be added, which allows the automatic creation of room record in Door Tablet
  2. For schedule files, only files that were created or modified today are processed
  3. If you use a single file, the file name must be called "schedule.txt". If a file was not created or modified today it will be ignored and no schedules will be available, unless a "date specific file" is available, see below
  4. If you use multiple files, file names must match the resource key name as created in the system (see below). All files extension must be "txt". If a file was not created or modified today it will be ignored and the resource considered free the entire day, unless a "date specific file" is available, see below
  5. The content if each file follows a simple format where each line is a single reservation, and in the case of "roomlist.txt", each line represents a room

Date specific files
You may create schedule files ahead of today and not worry about their time stamp or whether your system is dropping schedules to the folder on particular day, as long as these have been created in advance. You can create and update schedule files in advance. The key point here is that file name follow a very specific naming convention that is easy to follow and implement. The rules apply to both single schedule file or the more efficient multiple files option. To create a date specific file, using the following convention:
  1. Start with the room key, for example "rk1000"
  2. Add Year, Month, Day of the month, separated by underscore (_) and zero padded to two digits. For example "_2015_08_23"
  3. Add the ".txt" extension
For example: rk1000_2015_08_23.txt, or for a combined schedule: schedule_2015_08_23.txt
Remember to pad month and day with zeros to two digits. January is 01 and the ninth of the month is 09

Order of file checks
The following order applies when schedule files are searched:
  1. Check folder exists
  2. Look for base file using "roomKey.txt" or "schedule.txt"
  3. Check if the above file is there and was created or modified today, otherwise continue
  4. Look for Date specific file, and use it if found (no creation or modification time checks)
Please note that if a file is malformed it will be ignored and a message will show on the server console

File formats
Room List
Most columns are required while optional columns must be included and left blank. Columns in order from left to right:
  1. Key - a unique key for the room in the entire system. For example: "CLASS261"
  2. Room name - a name. For example: "Auditorium" or "Ocean" (if left blank, the room key will be used instead)
  3. Room location - The location where the room is. For example: "Humanities" or "North Wing". (optional) If you leave this blank you will need to add this manually later when activating the room using the Web UI
  4. Capacity - number of seats (optional)
  5. Groups - a text list (coma delimited) of all the groups the room belongs too. For example: "Classes, Disabled Access". (optional) Please note that if you use this column the column separator cannot be a coma

Please note that Door Tablet mandates two types of uniqueness when processing rooms. Both require that such unique values are across the system:
  1. Room key. For example, using the above: rk1001
  2. Room Name and Room Location as a pair (separated with a slash). For example, using the above: Red/HQ

The file format, weather you use a single or multiple files, is identical. Most columns are required while optional columns must be included and left blank. Columns in order from left to right:
  1. Room key - the same as listed as room key. For example: "CLASS261"
  2. Unique ID - meeting ID, must be unique in the whole system. Any length. For example: "rgjvbwebunerw842375983245kwjfdnvksfdjnv84395729834"
  3. Start time - the start of the meeting in 24 hours format, including minutes separated with ":". Do not need to pad the hour or minutes with 0. For example: 9:00 or 14:30
  4. End time - the end of the meeting in 24 hours format, including minutes separated with ":". Do not need to pad the hour or minutes with 0. For example: 11:15 or 17:30
  5. Subject - a description of the meeting. For example: "Molecular Chemistry - CM04/6" (optional, may be blank)
  6. Owner - who owns or responsible for the booking. For example: "Albert Einstein, PhD" (optional, may be blank)
  7. Owner email - the email address of the owner (optional). Note that the email address does not show and is only used for reminders
  8. Participant - how many people in the meeting
  9. Private - Y/N if the meeting is private. Optional - must be "Y" to be private, otherwise public. If a schedule is private the owner and subject will not show.

You use a delimiter as the one you specify in the system profile. Do not use any quotes or double quotes for strings and of course you must ensure that the delimiter is not used within the data.

Single or Multiple files
You have a choice in how you extract files to the shared folder. When a room schedule is requested, following will take place:
For a single file...
  1. The first file that was created or modified today is opened
  2. The file is read line by line
  3. If the first column equals the name of the requested resource, the line is used, all other lines are ignored
  4. If a wayfinding request is made for a group of rooms, the process repeats for each room in the group
When using multiple files...
  1. The file relating to the resource is opened
  2. Each line is read and expected to be part of today's schedule
  3. If a wayfinding request is made for a group of rooms, multiple files are opened and each fully read
It is warmly recommended that you use multiple files since its considerably faster and efficient

Sorting order
You must list entries in the order they happen during the day, morning ones first. Door Tablet will not sort your lists

Sample files
The following files exploit different features of the technology. Click on a file then save it to your disk.

File type
Sample file
Room list
Room schedules for today
Room schedule for a specific day
Room schedule for a number of rooms for today
Room schedule for a number of rooms for a specific day