[Noisebridge-discuss] Door Access Control

Robb Pope dijjital at gmail.com
Tue Jan 18 12:07:01 PST 2011


nice one, great systems there.

On Tue, Jan 18, 2011 at 12:01 PM, Jordan Bunker <bunker.jordan at gmail.com>wrote:

> May I recommend a visit to hackcess.org? It's a wiki I set up for
> hackerspaces to share their RFID access system information. It was part of
> the Open Door Hackathon that we had a little while ago. It sounds like the
> access system from 23b Shop might be your best bet.
>
>
> On Tue, Jan 18, 2011 at 1:41 PM, Robb Pope <dijjital at gmail.com> wrote:
>
>> 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)?
>>>
>>> Jared-
>>>
>>>  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.
>>>>
>>>> -ryan
>>>>
>>>> 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
>>>> enabled
>>>> > door access control system and I wanted to get some input on features
>>>> you
>>>> > think would be useful in a good all purpose door system.  I'm planning
>>>> on
>>>> > making it RFID with the ability to interface to it via computer
>>>> software.
>>>> > Here's a list of features I'm considering including.
>>>> >
>>>> > · Entrance Logging:   admins will be able to see at a glance who has
>>>> used
>>>> > the entrance through the SmartDoor Control software interface.  Date
>>>> and
>>>> > time will be logged for each “door event” (any time a user opens the
>>>> door
>>>> > via the RFID card system).
>>>> >
>>>> > · User Managemert:  through the software interface, admins will be
>>>> able to
>>>> > add, and delete users from any of the SmartDoor systems.  Users are
>>>> stored
>>>> > in the system by their actual name, not card ID.  This simplifies
>>>> finding
>>>> > entries in the log and managing the user database.
>>>> >
>>>> > · Scheduling:  Using the software interface, admins can set specific
>>>> times
>>>> > or ranges of time/dates that a user’s card will remain active.  This
>>>> allows
>>>> > certain users to have access to a space during specific hours or dates
>>>> only.
>>>> >
>>>> > · Remote Access:  The admin can trigger a door open event directly
>>>> through
>>>> > the software on their computer.  Additionally the admin has the
>>>> ability to
>>>> > trigger a door open event remotely from another location by dialing
>>>> into the
>>>> > network.
>>>> >
>>>> > · SMS Notification:  Choose to be notified via SMS when specific users
>>>> enter
>>>> > 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
>>>> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>>>>
>>>
>>>
>>
>> _______________________________________________
>> Noisebridge-discuss mailing list
>> Noisebridge-discuss at lists.noisebridge.net
>> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.noisebridge.net/pipermail/noisebridge-discuss/attachments/20110118/b51ad1c3/attachment.htm 


More information about the Noisebridge-discuss mailing list