Projects/Blue Sky ideas!

From OpenCATS

OpenCATS New System and Project Page

This is the page for the launch of a completely fresh OpenCATS that is:

free and clear of any of the current license restrictions
community driven
clean fresh architecture
currently called OSATS (in SVN)

1 Getting started
- 1.1 Introduction
2 Ideas
3 Framework

Getting started

Introduction

Use the page below or new pages to document needed features, planning, links etc. A lot of discussion has already taken place on the forums

Ideas

Logical design

workflow was clearly articulated in a historic post from mabdalla
what's great should collate what we really love about the existing app
what sucks should collate what we really hate about the existing app
i wish it did - needs to summarise the wish list for the app...

User Interface

The first thing I would like to see is a frontend interface that would allow a user to input their own application online.

The front-end interface should be useable as a separate module installable on a web-server, which can communicate back to the ATS server. 
For example the Joomla Module available for OpenCATS can be installed on a remote Joomla instance, and will talk back to OpenCATS using MySQL and FTP.
There are tweaks for MySQL query caching that make the speed for the remote site very fast.

Naming

Drop the C in the name: Become OpenATS

--good idea --RussH 23:35, 5 February 2009 (UTC)
an existing issue with domain parking would be an issue, but you can always go the firefox and dropbox route and just prefix the domain with 'get'

Design

Agree a language / platform etc

  Localization should be introduced to the system using resources sheets or at least by imitating the current way that CATS
  does translate the system into several other languages. Later we can ask volenteers from each culture to localize the
  interface into their own language.

Expand data model to include credentials, licenses and verification trail/history on education, experience and skills

Implement the HR-XML specification for import/export to and from the ATS

Agree a set of standard api's

  I believe this is a very important seperation point between modules/applications and the core system entities such as user
  management, security and privacy. Once a set of standard api's are agreed on, application can use these api's to access the
  system features and provide their own functionality.

Adding a reporting module / application

  This basically requires use of a reporting tool like crystal reports or any other OS php/mysql tool.

Enhancing the current Calendar Module

  There is a Calendar module already existing in the current system and i think we will have to develop it further for
  scheduling purposes in later iterations.

Adding an emailing module / application

  This should be on top of our priorities. Email is at the heart of the system and many recruiter/candidate interactions
  should be managed through it. A email marketing campagin module should be introduced and this can be similare to what
  SugarCRM's email management module currently offers. More on this later.

Features

Resume Import and Parsing
- Parse converted resumes to extract the primary pieces of important data like Name, Phone, email
- Consider parse to XML hierarchy (see below) for future skills, dates etc parsing would have a better foundation to build on
- Appears to be open standard already for HR-XML Resumes at http://ns.hr-xml.org/2_5/HR-XML-2_5/SEP/Resume.html

I'd like to see a frontend interface users could use to find and apply for openings. One thing I think would also be great is to impliment 3 sections:

Position Openings
Applications
Questionaires

The admin would create job openings and diffrent questionaires, and for job opening x you'd have to complete questionaire x, for job openinging y you need questionaries x and y completed.

Next the user (or the admin for users who mail it it) would add their resume, the resume should be indexed to be searchable and the user can identify the open positions they want to be considered for, and link their resume to those.

When you search for an applicant you get though groups, in this order:

1. Users who meet search criteria and have asked to be cconsidered for the job you are currently searching for a canidate for

2. Users who match your serach criteria but have not specifically asked to be considered for the job you are currently searching for a canidate for

3. Users who don't match your search but have asked to be considered for the job you are currently searching for a canidate for

These are just my ideas as a business person on what I would like to see in an ATS.

Framework

OR mapper
MVC
Symfony with Doctrine
- http://www.symfony-project.org
  - Symfony is an easy to use, robust web development framework built on MVC architecture. Symfony provides tools, framework, architecture, and ORM to build complex applications that are faster and bug free. Additionally, it uses best development practices and integrates with other essential third party applications.
- http://www.doctrine-project.org/

Retrieved from "http://opencats.org/documentation/Projects/Blue_Sky_ideas!"

Search

Navigation