Commit Graph

10 Commits (96f40a85149541ba8e2dcc525b4220fbfbd2492f)

Author SHA1 Message Date
eric 0600078c27 empty the repair migration 2016-07-29 18:49:08 -04:00
eric 4ff63359b3 migration to repair db
The migrations needed to migrate our db to django 1.8 are as follows:
django-admin.py migrate default 0001_initial --fake
django-admin.py migrate --fake-initial auth
django-admin.py migrate default 0002_add_related_name --fake
django-admin.py migrate core --fake
django-admin.py migrate libraryauth
django-admin.py migrate --fake-initial
2016-07-28 10:10:05 -04:00
eric d8eb4297d9 migrations 2016-07-21 15:38:09 -04:00
eric b1e1b9ff5d clean up migration 2013-12-02 10:21:29 -05:00
eric ccb1f0dd86 create and edit Library objects, which now have names and owners 2013-11-27 22:14:52 -05: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