-
Notifications
You must be signed in to change notification settings - Fork 1
T card Project Specification
Tom Grundy edited this page Nov 17, 2017
·
6 revisions
Click Here to read important notes about this project specification.
This spec is broken into three parts: 'requirements', 'nice-to-haves', and 'ideas'. All items should begin in 'ideas'. If the items in the 'ideas' section get fleshed out and agreed upon to a sufficient level of detail, they can get promoted to 'requirements' or 'nice-to-haves' as appropriate.
- sign-in interface: fast electronic sign-in at the logistics table (by whatever means) is the entry point for this whole process
- networked: server/client configuration on a local wifi network, without internet access
- real-time updating: new sign-ins from any node should be visible to all other nodes 'instantly'
- cross-platform: Windows server; Windows, iOS, Android clients
- robust: double-redundant or better real-time automatic backups both digitally and on paper (to networked printer); also fault-tolerant enough to allow the system to keep working - on paper if needed - if any or all parts of the system fail for any duration
- xml-based T-card file format (.tml?): one file for each human - each county keeps updated .tml's ready to go for mutual aid - privacy factors in here somehow
- categorization: accommodate the various T-card data fields and figure out how to display and group them appropriately
- touch-screen interface: ops could build teams on a large touch-screen inside the trailer, with an interface that looks and behaves like a T-card sleeve (and updates are instantly visible on all other nodes)
- automatic printing of names, callsign, etc on assignment forms: does sarsoft already provide for this in any way? If not, can the sarsoft-generated assignment form PDF be a fillable form that this program can automatically fill out and print?