Merge branch 'dev' into fix/local-deploy

Author: maxceem

README.md

@@ -234,7 +234,8 @@ To be able to change and test `taas-es-processor` locally you can follow the nex
 | `npm run cov`                                                                                                             | Code Coverage Report.                                                                                                                              |
 | `npm run migrate`                                                                                                         | Run any migration files which haven't run yet.                                                                                                     |
 | `npm run migrate:undo`                                                                                                    | Revert most recent migration.                                                                                                                      |
-| `npm run demo-payment-scheduler`                                                                                          | Create 1000 Work Periods Payment records in with status "scheduled" and various "amount"                                                           |
+| `npm run demo-payment-scheduler`                                                                                          | Create 1000 Work Periods Payment records in with status "scheduled" and various "amount"                                                                         |
+| `npm run emsi-mapping`                                                                                                    | mapping EMSI tags to topcoder skills                                                                          |
 
 ## Import and Export data
 
@@ -348,3 +349,8 @@ When we add, update or delete models and/or endpoints we have to make sure that
 - **DB Migration**
   - If there are any updates in DB schemas, create a DB migration script inside `migrations` folder which would make any necessary updates to the DB schema.
   - Test, that when we migrate DB from the previous state using `npm run migrate`, we get exactly the same DB schema as if we create DB from scratch using command `npm run init-db force`.
+
+## EMSI mapping
+mapping EMSI tags to topcoder skills    
+Run `npm run emsi-mapping` to create the mapping file    
+It will take about 15 minutes to create the mapping file `script/emsi-mapping/emsi-skils-mapping.js`

config/default.js

@@ -214,5 +214,17 @@ module.exports = {
     FIX_DELAY_STEP_ASSIGN_MEMBER: parseInt(process.env.PAYMENT_PROCESSING_FIX_DELAY_STEP_ASSIGN_MEMBER || process.env.PAYMENT_PROCESSING_FIX_DELAY_STEP || 500),
     // the fix delay after step of activate challenge, unit: ms
     FIX_DELAY_STEP_ACTIVATE_CHALLENGE: parseInt(process.env.PAYMENT_PROCESSING_FIX_DELAY_STEP_ACTIVATE_CHALLENGE || process.env.PAYMENT_PROCESSING_FIX_DELAY_STEP || 500)
+  },
+  // if a job reach this critier, system will automatically withdrawn other job applications.
+  JOBS_HOUR_PER_WEEK: 20,
+  // the mapping includes the status transformation when auto-withdrawn feature is performed on job candidates.
+  WITHDRAWN_STATUS_CHANGE_MAPPING: {
+    applied: 'withdrawn-prescreen',
+    'skills-test': 'withdrawn-prescreen',
+    'phone-screen': 'withdrawn-prescreen',
+    open: 'withdrawn',
+    interview: 'withdrawn',
+    selected: 'withdrawn',
+    offered: 'withdrawn'
   }
 }

package.json

@@ -11,6 +11,7 @@
     "init-db": "node src/init-db.js",
     "create-index": "node scripts/es/createIndex.js",
     "delete-index": "node scripts/es/deleteIndex.js",
+    "emsi-mapping": "node scripts/emsi-mapping/index.js",
     "index:all": "node scripts/es/reIndexAll.js",
     "index:jobs": "node scripts/es/reIndexJobs.js",
     "index:job-candidates": "node scripts/es/reIndexJobCandidates.js",
@@ -87,4 +88,4 @@
       "test/unit/**"
     ]
   }
-}
+}