Currently, the ACS is using Royce's v1.0 software and v2.0 hardware--Royce, I am guessing at the version numbers!--but the current system uses a text file based lookup list for members, who are each assigned an access code (or a unique keycard code.)
See Access Control System in the Notebook for background
Royce has installed software permitting a database lookup for access to the building, but we have not linked the ACS software to the database (MySQL) running on the server.
If we setup the database managing access control would be much easier--so that's step one. Step two, however, could prove interesting:
- Each member is assigned a private key and public key when they join.
- The member uses their private key to open the door (via database lookup, according to the access policy for their membership or use.)
- The member gives away their public key to their friends, contacts, and visitors.
- When member guests arrive at the space, they enter the public key into the door system.
- The ACS looks up the member associated with the public key in the database, and then notifies the member that their guest is present using any number of options: text, email, IFTT update, tweet; whatever the member prefers.
- Thus, the public key becomes both a doorbell and a calling card--"I am here to meet you at the space" as well as "I was at the space to meet you, but you weren't there."
I know this second use is more conceptual, but I think it would be simple to implement--perhaps we can hook it into Drupal's messaging system and use all the inbuilt modules for sms and tweets and whatnot. Or perhaps we could use Tropo for this.
What do you think?