Update and extend a small Python software with a webfrontend to a central configured solution
Budget: €250 – €750 EUR
We have a small Python unicorn solution that works as a standalone solution on Debian systems. It is an access solution with serial RFID readers and release via GPIOS. The RFID cards are currently managed via a web front end (unicorn) on each individual system. In the web frontend you can also read a log file in which all card actions are saved.
There are now several systems and these are to be configured centrally via a web front end. The web portal is to be expanded for this purpose.
The current data structure is:
Card pool: UserID; cardnumber;
Customer: Name;Company;Email;
Card assignment: customer <-> card
and some reports.
The configuration is carried out by admins.
In the future, it should be possible to centrally manage the cards for several systems.
The new parent structure would then be:
Group admin: own system groups; Own system card pool; own system users;
Groups: Locations; System IDs
The group admin can then create system groups and assign cards to their users and assign system groups to these cards.
The changes relevant to the individual systems should then be made available for download for the corresponding systems. If a system has an Internet connection, it should periodically log on to the portal, check whether there is a new configuration, download it if available and integrate it into its own local database, and then transfer the most recent log file of all card movements to the portal database.
Another required feature: if a local system is connected to the portal, there should be the possibility to download the complete user card authorization database for that system.
The local systems should only be expanded. They should be able to work as standalone systems!
There are now several systems and these are to be configured centrally via a web front end. The web portal is to be expanded for this purpose.
The current data structure is:
Card pool: UserID; cardnumber;
Customer: Name;Company;Email;
Card assignment: customer <-> card
and some reports.
The configuration is carried out by admins.
In the future, it should be possible to centrally manage the cards for several systems.
The new parent structure would then be:
Group admin: own system groups; Own system card pool; own system users;
Groups: Locations; System IDs
The group admin can then create system groups and assign cards to their users and assign system groups to these cards.
The changes relevant to the individual systems should then be made available for download for the corresponding systems. If a system has an Internet connection, it should periodically log on to the portal, check whether there is a new configuration, download it if available and integrate it into its own local database, and then transfer the most recent log file of all card movements to the portal database.
Another required feature: if a local system is connected to the portal, there should be the possibility to download the complete user card authorization database for that system.
The local systems should only be expanded. They should be able to work as standalone systems!