Continuing in the series of fun recycling projects for these Dell Vostro 200 computers, I purchased a MagTek Dynamag USB-based swipe card reader for a new project to track visitors in the office’s entrance.
The solution includes an Ubuntu server which only runs a single application to receive the card swipe details, to find the Track 1 data and to then submit this information to a Microsoft IIS—based website. The pages here then offer up an API for the incoming card swipe details and an administrative page for registering new visitors, reviewing the log details and the visitors as seen, to include the ability to export those details to Excel. The data is stored in a Microsoft SQL Server database.
To save cost, I decided to have each visitor just use a magnetic swipe card already in their wallet. In this way, I wouldn’t have to buy a magnetic card encoder, purchase card blanks nor worry about designing or issuing them (or trying to get them back later).
Typical Cost of an Access Control System for Visitors
From this webpage 2016 Average Card Access Cost
“Expect to pay an average of $1,500 to $2,500 per door for a high-quality system for up to 150 people. … It will cost an average of $1,000 to $1,500 for the hardware for the door. It will cost an average of $3 to $5 per keycard. Monthly service fees can range from $10 to $100 per month.”
My total cost for this project was just eight hours’ labor plus the $48.36 for the card reader! This included the database and website coding plus the I.T. work to setup the Ubuntu server and to create the Python script to talk to the USB-based reader, to test everything and to write up the documentation. This isn’t bad, considering the cost of an average system.
In my quest for recycling old Dell Vostro 200 computers here at work I’ve recently had the pleasure of creating a document management system using the open-sourced Kloudspeaker software. It appears to be a mature project and installs easily.
It’s important to read through the documentation. Out-of-the-box it doesn’t do file uploads, for example, but the configuration may be modified to do so. And I found an issue with files larger than 2MB which again was fixed by reading the docs. It helps to have some reasonable system experience on your UNIX server because some of these issues are dealt with outside of the Kloudspeaker software’s configuration itself.
The interface is attractive throughout. The upper menu is responsive to changes in window size, buttons (like Upload) will optionally appear if the feature is turned on and if the user has the correct rights. Overall it just seems to work without problems.
Typical Cost of a Document Management System
From the webpage How Much Does a Document Management System Cost?
“[For a cloud-based system] …you should expect to invest between $20 and $50 per person per month, with the major variable being the level of service you subscribe to.
“[For an on-premised system] To start, you’ll have an up-front charge for your server and desktop licensing. This licensing tends run between $350 and $500 per person on average. Depending upon which features you sign up for, you’ll need to purchase the appropriate number of servers at the average rate of $5,000 to $6,000 per device. Ongoing support and maintenance will take the form of an annual per person fee, which will typically cost you around $40 per seat.”
Below is the list of things I needed to do to get the server running. I managed to do all of this in just under two hours. It then took me another two hours of finding over 300 contracts so that I could upload them into the system. All-in-all, that’s not bad (four hours’ labor + $0.00) for an excellent document management system that could have cost a lot of money!
- Boot from a (free) GParted disc on a Dell Vostro 200 computer to remove any existing partitions
- In BIOS, set the computer so that it will run without a keyboard without stopping during POST
- Boot from a (free) Ubuntu disc and install it as a server
- Choose server install
- Use entire disk with LVM
- Install GRUB
- Install OpenSSH server and LAMP
- Edit the /etc/network/interfaces file to give the server a static IP address
- Edit the /etc/apache2/apache2.conf file to give the webserver its name
- Create a CNAME record in my DNS server of contracts for this Intranet server
sudo apt-get update,
sudo apt-get upgrade and
sudo do-release-upgrade to make sure that I’m using the latest software
sudo apt-get install unzip to install this necessary software
- To pull the latest zip file from their website, in my home directory run the command
wget http://www.kloudspeaker.com/download/latest.php, run
unzip to expand the file structure and then copy this recursively to the /var/www/html area under a kloudspeaker folder name, remembering to use the -a option for the
sudo cp command to get hidden files as well
- Log into MySQL as the root user with
mysql -u root -p and then from this console, run
create database kloudspeaker; and then run
exit; to come out of the MySQL client
- Edit the /var/www/html/loudspeaker/backend/configuration.php file, setting the appropriate database credentials for the newly-created kloudspeaker database, as well as adding
"EventLogging" => array() to the list of plugins
- Edit the /etc/apache2/sites-available/000-default.conf configuration file to change the DocumentRoot to
- From another computer, visit the http://contracts/backend/install link to start their installation, verifying the database credentials and next, creating an administrative user for the software
- Back in a terminal, manually create a folder at the root with
sudo mkdir /files and subfolders below this to hold each subgroup
sudo chown -R www-data:www-data /files to make sure that the Apache service user can control the files uploaded into the system
- Edit /etc/php/7.0/apache2/php.ini to add these two lines:
upload_max_filesize = 40M and
post_max_size = 40M
sudo apt-get update and
sudo apt-get upgrade again to verify that your system is up-to-date after bringing in software
- Again from another computer, log into the website interface, creating users, groups, adjusting the access rights to the folders you’ve defined, making sure to test as a non-administrator user to verify the results
- Shut down the Ubuntu server, remove all peripherals and put the computer into the server room with only Ethernet cable and power cord connections, turning it back on
Now that everything’s installed and setup, you add the user accounts for the people who also need access. You use their email address so it will invite them to create their own passwords.
I’m very pleased with the way this has turned out and how little effort was required to get it going. I’d highly recommend this software for businesses.