review Capistrano-scripted jobs

[candyhazlett]

• [ ] restore missing service.rb files for xml db tasks from pre-archimedes branch
• [ ] review/refactor capistrano-scripted jobs
  • [x] determine if they should be replaced with Rails jobs, or if the functionality is managed with the startup process configured for the newer version of Rails
  • [x] mailer functionality in User Controller: UsersController < CatalogController
  • [X] Solr connection and CRUD actions addressed in issue #85 - [ ] adding records to solr index - [ ] updating records indexed within solr
  • [ ] adding tei to xml db
  • [ ] loading view packages--create another task
  • [ ] generating html file associated with core file
  • [ ] generating core file metadata that's indexed in Solr

[candyhazlett]

This mostly involves making sure either the environment configuration or existing Rails jobs handle tasks related to app functionality, e.g., the EC2 instance for Solr does not need to be started by the app as it is maintained separately.

[candyhazlett]

For adding records to solr index and updating records indexed within solr tasks, jobs do exist to execute and resque is configured to create queue object and run job passed as parameter. However the code required to start that workflow after an object is created or updated does not exist in the current codebase and will need to be created. This code was handled, prior to Archimedes involvement, with helper methods on indexed object classes. e.g., Community#to_solr