[Noisebridge-discuss] Door Access Control
dijjital at gmail.com
Tue Jan 18 19:41:06 UTC 2011
hehe, this isn't a system for noisebridge per-se. I'm asking the community
of hackers for ideas about cool features for a general door access system.
So, yes, logging is important to many people who might use this system. As
is the ability to schedule times when certain people would have access (in
the case of a business or school regulating when employees or students can
have access to company or school resources).
On Tue, Jan 18, 2011 at 12:16 AM, Jared Dunne <jareddunne at gmail.com> wrote:
> I think Ryan has a good point regarding privacy concerns for something like
> this. Perhaps the audit trail/logging feature should be Opt-in for users
> that want to leave the digital footprints. By default user privacy is
> respected, but if they want others to know when they are in the space then
> they could opt-in to triggering "door events". I can see "door events"
> being awesome hook-ins for door/entry related hacks or personalization of
> space, but some won't want the system to do anything besides get them into
> the space.
> Robb, thanks for working on this. I'd love to be able to get into the
> space more easily. I also have some fun ideas that would benefit from "door
> events". When are you typically around working on this project (or others)?
> On Mon, Jan 17, 2011 at 11:21 PM, Ryan Rawson <ryanobjc at gmail.com> wrote:
>> - Protects the user's privacy - do not allow anyone, including admins
>> and root level users, the ability to log, track, audit, or otherwise
>> track the movements of any/all users.
>> On Mon, Jan 17, 2011 at 7:35 PM, Robb Pope <dijjital at gmail.com> wrote:
>> > Hey noisebridgers, I'm knee deep in the process of developing a web
>> > door access control system and I wanted to get some input on features
>> > think would be useful in a good all purpose door system. I'm planning
>> > making it RFID with the ability to interface to it via computer
>> > Here's a list of features I'm considering including.
>> > · Entrance Logging: admins will be able to see at a glance who has
>> > the entrance through the SmartDoor Control software interface. Date and
>> > time will be logged for each “door event” (any time a user opens the
>> > via the RFID card system).
>> > · User Managemert: through the software interface, admins will be able
>> > add, and delete users from any of the SmartDoor systems. Users are
>> > in the system by their actual name, not card ID. This simplifies
>> > entries in the log and managing the user database.
>> > · Scheduling: Using the software interface, admins can set specific
>> > or ranges of time/dates that a user’s card will remain active. This
>> > certain users to have access to a space during specific hours or dates
>> > · Remote Access: The admin can trigger a door open event directly
>> > the software on their computer. Additionally the admin has the ability
>> > trigger a door open event remotely from another location by dialing into
>> > network.
>> > · SMS Notification: Choose to be notified via SMS when specific users
>> > the building. Optionally control the system via SMS
>> > _______________________________________________
>> > Noisebridge-discuss mailing list
>> > Noisebridge-discuss at lists.noisebridge.net
>> > https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>> Noisebridge-discuss mailing list
>> Noisebridge-discuss at lists.noisebridge.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Noisebridge-discuss