Commit Graph

13 Commits (ff38f063d0f997c869e42c0a730f9eb2a6f16ecf)

Author SHA1 Message Date
eric 9da195dcc8 remove south, fix migration problems 2016-07-21 16:09:42 -04:00
eric 45d96f21bc Add explanation of verification options 2013-12-02 00:46:25 -05:00
eric 92aee28538 users can't join unapproved libraries 2013-12-01 19:20:42 -05:00
eric ff0f7e5446 can now create and admin user validation 2013-11-30 15:40:45 -05:00
eric ccb1f0dd86 create and edit Library objects, which now have names and owners 2013-11-27 22:14:52 -05:00
eric 7454101dd4 remove code that forbids overlapping blocks 2013-10-31 18:10:01 -04:00
eric 78d7f1291a use longs, not ints 2013-10-31 18:00:58 -04:00
eric e6573ac0c5 library user can buy a library license 2013-10-15 16:18:30 -04:00
eric eb9cc878ce add email authentication 2013-10-10 22:31:31 -04:00
eric 9929452ebc LibraryUser replaces LibraryCard, used for all backends, has datestamp 2013-10-10 15:56:40 -04:00
eric d99aaa97c9 card number authentication!
create libraries and administer them in admin.
card patterns mimc ezproxy format
http://www.oclc.org/support/services/ezproxy/documentation/usr/number.en
.html
after you join a library, it appears in your explore bar
2013-10-10 02:41:50 -04:00
eric 439169a1ab Implemented IP authentication
libraries get associated with a library_block table (IP ranges)
moved superlogin here
IP stuff mostly copied from
https://github.com/benliles/django-ipauth/blob/master/ipauth/models.py
The model is that you need to be in an allowed IP range to "join" a
library. Once you've joined, you can use your login from anywhere. to
use that library.
Asign IP ranges in admin
2013-10-08 15:37:22 -04:00
eric ab473f5411 libraries, phase 1.
admin can create a library connected to a user
other users can "join" the library
2013-10-02 12:02:08 -04:00