Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
FreERMS is an electronic resource management system for libraries. It is written in PHP using the symfony framework (1.4). It has been tested on a Linux system with PHP 5.3.
PHP JavaScript Shell

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
apps
config
data
lib
test
vendor
web
.gitignore
.gitmodules
.travis.yml
LICENSE
README.md
symfony

README.md

FreERMS

FreERMS is an electronic resource management system for libraries. It is written in PHP using the symfony framework (1.4). It requires PHP 5.3, and has been tested on Ubuntu Linux systems.

symfony is very well documented; the project homepage is http://www.symfony-project.org/

Installation

  • Clone the FreERMS git repo

    /home/fred$ git clone https://github.com/yitznewton/freerms.git
    
  • FreERMS requires a slightly modified version of symfony. It is registered as a submodule of the FreERMS git repo; if you are installing manually, the symfony 1.4 filesystem should be symlinked or added as vendor/symfony-1.4

    The modified repo is https://github.com/yitznewton/symfony1

  • Add a symlink in /web pointing to the symfony assets directory, or copy it, e.g.:

      /home/fred/freerms/web$ ln -s ../vendor/symfony-1.4/data/web/sf
    
  • Specify your database connection in config/databases.yml

  • Add missing directories:

    /home/fred/freerms$ mkdir cache log
    
  • Install sfGuardPlugin and publish plugin assets:

    /home/fred/freerms$ ./symfony plugin:install sfDoctrineGuardPlugin
    /home/fred/freerms$ ./symfony plugin:publish-assets
    
  • Run a Doctrine build.

    /home/fred/freerms$ ./symfony doctrine:build --all
    
  • Clear symfony's internal cache (incidentally, always a good idea if something looks inexplicably broken during installation or update):

      /home/fred/freerms$ ./symfony cc
    
  • Create a superuser:

    /home/fred/freerms$ ./symfony guard:create-user jimbo mypassword
    /home/fred/freerms$ ./symfony guard:promote jimbo
    

At this point, you will be able to set your web server's document root to symfony's web directory, and connect to the /backend.php app with the user you have just created.

In order to use the public-facing app, you will need to associate your user with one or more libraries, by selecting them as "groups" in the user's record, which you can edit by clicking "Users" in the backend area. Libraries are added as groups when you create them. You can also add arbitrary groups (academic programs, for example) which are not libraries.

sfDoctrineGuardPlugin documentation is available at http://www.symfony-project.org/plugins/sfDoctrineGuardPlugin

Reports

In order to use the reports app, you must install the flot plotting library in /web/js/vendor/flot, and the Bluff chart library in /web/js/vendor/bluff. They are available at the following addresses, respectively:

Basic setup

After accessing the /backend.php admin area, you will need to define your libraries and IP ranges. You can then add databases. You must specify an on- and off-campus access action for each (see below).

After selecting subject for each database, you can choose specific databases to feature on the homepage via /backend.php/databases/featured, or on subject pages via each subject's admin page.

Theming

You can support multiple templates for the frontend app ('layouts' in symfony terms) by adding them to apps/frontend/templates/. They can then be called by one of the following methods:

  • Passing the layout name in the URL as the site parameter
  • Passing the layout name in the URL as the layout parameter
  • Using the layout name as the most specific segment of the server host name, e.g. foo_layout_name.erms.example.com

If you supply a mobile layout with the suffix _mobile, e.g. foo_mobile, mobile users under that layout will be shown that template. You can allow them to select the non-mobile theme by sending them to a URL which has the force-no-mobile parameter set to a true value, e.g. http://erms.example.com/?force-no-mobile=1. It can then be reverted with e.g. http://erms.example.com/?force-no-mobile=0.

Fine-grained access control

In addition to the normal library-level filtering of access, you can impose additional requirements; for example, if a given database is licenced only for a specific acadmic program. Add this program as a group, and associate the relevant users. Then add this group's name in the database's Access control field. If you need to require multiple groups in AND or OR logic, use symfony's credential syntax, as described at http://www.symfony-project.org/gentle-introduction/1_4/en/06-Inside-the-Controller-Layer#chapter_06_sub_complex_credentials

To allow all onsite users, add onsite as a value.

Access actions

A number of standard access actions are included with FreERMS, including one for ticket-based EZproxy authentication, and ebrary single sign-on. Inevitably, however, some resources will require local customization.

To add a custom access action, create a new PHP class at /apps/frontend/modules/access/actions/XYZAccessAction.class.php which extends baseAccessAction. FreERMS will call the execute() method of the AccessHandler instance when a user requests the resource.

Alternate authentication

To use an authentication system other than sfDoctrineGuardPlugin, you will need a customized class which implements freermsSecurityUser. In doing so, Touro College (the sponsor of FreERMS's development) extended the sfDoctrineGuardPlugin user class, overriding certain key methods.

You may also want a customized DataService class to include local user data in the usage logs.

Because of security concerns, Touro is not including their customizations in the main repository. Please contact yitznewton@hotmail.com if you wish to discuss the details.

Usage logs

Usage of databases and access of URLs are logged in the database_usage and url_usage tables of FreERMS's database. At present, these need to be queried by hand. A reporting module is planned.

Something went wrong with that request. Please try again.