By: Team 15-3 Since: Feb 2019 Licence: MIT

1. Introduction

slaveFinder() is a resume management application that helps recruiters manage most of the hiring process.

The application is optimized for those who prefer to work with a Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI). If you can type fast, slaveFinder() can get your resume management tasks done faster than traditional GUI apps.

Interested? Jump to the Section 2, “Quick Start” to get started or Section 5, “Command Summary” for the list of commands. Enjoy!

2. Quick Start

  1. Ensure you have Java version 9 or later installed in your Computer.

  2. Download the latest addressbook.jar here.

  3. Copy the file to the folder you want to use as the home folder for your Address Book.

  4. Double-click the file to start the app. The GUI should appear in a few seconds.

  5. There are two main Screen for this Software.
    All Jobs Screen: Two main list will show in this screen, one is for all applicants, the other is for all jobs openings.

    Ui

    Job Detail Screen: Four main lists will show in this screen, they are all applicants list and represent four stages of hiring process in a specific job.

    DisplayJob

  6. The GUI should start with some data preloaded to allow easier trying out of system

  7. Type the command clear to start with an empty addressbook instead.

  8. Type the command in the command box and press Enter to execute it.
    e.g. typing help and pressing Enter will open the help window.

  9. Some example commands you can try:

    • add n/John p/91757536 nric/S8761230Q e/john@example.com a/123 Disneyland g/Male r/Malay m/Psychology s/NUS gr/4.33 j/Manager: adds a person named John to all applicants database.

    • createJob jn/Manager: creates new job opening Manager.

    • addAll a jn/Manager : adds all applicants in the database to the applicants list of job Manager.

    • displayJob jn/Manager: displays the selection process for job opening Manager

    • list : Goes back to the list of all applicants and job openings.

  10. Refer to Section 3, “Features” for details of each command.

3. Features

Command Format

  • Words in UPPER_CASE are the parameters to be supplied by the user e.g. in add n/NAME, NAME is a parameter which can be used as add n/John Doe.

  • Items in square brackets are optional e.g n/NAME [pj/PASTJOB] can be used as n/John Doe pj/Software-Engineer or as n/John Doe.

  • Items with …​ after them can be used multiple times including zero times e.g. [pj/PASTJOB]…​ can be used as   (i.e. 0 times), pj/Software-Engineer, pj/Software-Engineer pj/Web-Developer etc.

  • Parameters can be in any order e.g. if the command specifies n/NAME p/PHONE_NUMBER, p/PHONE_NUMBER n/NAME is also acceptable.

  • But INDEX and FILTERLISTNAME should always be put follow on command word (preamble). INDEX and LISTNAME don’t have prefix before. e.g. n/NAME INDEX, n/NAME FILTERLISTNAME are not allowed

3.1.1. Import Resumes to slaveFinder() : importResumes

Given input resume txt files in placed in the specified folder, reads all the resumes and saves them into slaveFinder(). Format : importResumes path_to_folder

  • All the resume documents should be txt files and strictly follow the below format.

Name
Phone
Email
NRIC
Gender
Race
Address
School
Major
Grade
Lang,Lang,Lang
pastJob,pastJob,pastJob
jobsApply,jobsApply,jobsApply
interviewScore

  • All fields are to be populated, except for Programming Languages, Past Jobs, and Jobs Applied

    • For these fields, specify any number of items (zero or more), separated by commas

  • All the resume documents should be stored in one folder.

  • If the new added people is a new person to our company, slaveFinder will crawl the data from resume and add him/her as ADD command.

  • If the new added people is a person already in our storage, slaveFinder will crawl the data from resume and change his/her data as EDIT command.

  • We assume that applicants who want to apply HR’s company need to fill in a Resume Form (which format is strict) online.

    • The format will be refined in V2.0, applicant can provide a link of their real CV (prefer pdf formmat) when they fill in the Resume Form.

Examples:

  • importResumes C:\Users\MyName\Desktop\MyResumes
    Imports all resumes in the given path

  • To try this command with 1000 resumes, use the folder CVFolder found in the zip file of slaveFinder()'s release.

3.1.2. Open CV for potential applicants : openCV Coming in v2.0

Opens the real CV provided in Resume Form of applicants
Format: `openCV [FILTERLISTNAME] INDEX `

  • This command can be used in both All Jobs Screen and Job Detail Screen, when Screen is All JOb Showing Screen, FILTERLISTNAME should be empty.

  • When Screen is Job Detail Screen (four applicants lists shows), FILTERLISTNAME is needed.

  • FILTERLISTNAME indicate which Job list this command will be used.

  • Opens the CV of applicants at the specified INDEX. The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …​

  • Pontential candidate will be confirmed by FILTERLISTNAME (if any) and index and his/her CV will be opened for reference.

Examples:

  • openCV 1
    Opens the CV of the 1st applicants showing on All Allicants List

  • openCV applicant 2
    Opens the CV of the 2nd applicants showing on Allicants List in Job Detail Screen.

3.1.3. Adding a person: add

Adds a person to the address book
Format: add n/NAME p/PHONE_NUMBER nric/NRIC e/EMAIL a/ADDRESS g/GENDER r/RACE m/MAJOR s/SCHOOL gr/GRADE j/JOBS_APPLY

  • This command can only be used when All Jobs Screen shows. You can add applicants into All Aplicants list

  • n/: Name should only contain alphanumeric characters and spaces, and should not be empty.

  • a/: Address can take any values, but should not be empty.

  • nric/: NRIC must be unique. It must start with S, followed by exactly 7 numbers, and end with an alpabet in capital letter. It should not be empty.

  • p/: Phone numbers should only contain numbers, and it should be at least 3 digits long, and should not be empty.

  • e/: Email should be of the format local-part@domain, and should not be empty. "E.g. example@gmail.com"

  • g/: Gender should only be "Female", "Male" or "Others", and should not be empty.

  • r/: Race should only be "Chinese", "Malay", "Indian" or "Others", and should not be empty.

  • gr/: Grade should only contain positive numbers, and must be in exactly 2 decimal place. E.g. "4.64"

  • s/: School can take any values, but should not be empty.

  • m/: Major should only contain alphanumeric characters and spaces, and should not be empty.

  • j/: Jobs Apply must only contain one word. If two or more words, have to be connected by a dash. E.g. "Software-Engineer". It should not be empty. It can take more than 1 value. E.g. "j/Manager j/Sweeper"

  • is/: Interview scores field is optional, and must be exactly 5 set of numbers, each seperated by a comma. E.g. "1,2,3,4,5"

  • kpl/: Known Programming Language field is optional. It can take any values, and can take more than 1 value. E.g. "kpl/Java kpl/Python"

  • pj/: Past jobs field is optional, and past job must only contain one word. If two or more words, have to be connected by a dash. E.g. "Software-Engineer". It can take more than 1 value E.g. "pj/Manager pj/Sweeper"

Examples:

  • add n/John p/91757536 nric/S8761230Q e/john@example.com a/123 Disneyland g/Male r/Malay m/Psychology s/NUS gr/4.33 j/Manager

  • add n/Betty p/123 nric/S4444455Y e/betty@bet.com a/321 USS g/Female r/Others m/Life Science s/NTU gr/0.44 j/Helper is/1,2,1,10,5 kpl/Java pj/Chief-Executive-Officer

3.1.4. Listing all persons : list

Shows a list of all job openings and applicants in slaveFinder().
Format: list

  • Useful after using filter/displayJob which shows a subset of the all applicants list.

3.1.5. Editing a person : edit

Edits an existing person in slaveFinder().
Format: edit INDEX n/NAME p/PHONE_NUMBER nric/NRIC e/EMAIL a/ADDRESS g/GENDER r/RACE m/MAJOR s/SCHOOL gr/GRADE j/JOBS_APPLY

  • This command can only be used when All Jobs Screen shows. You can edit applicants in All Aplicants list

  • Edits the person at the specified INDEX. The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …​

  • Editting fields that allows more than 1 value will entirely replace the existing values.

  • Existing values will be updated to the input values.

Examples:

  • edit 1 p/91234567 e/johndoe@example.com
    Edits the phone number and email address of the 1st person to be 91234567 and johndoe@example.com respectively.

  • edit 2 n/Betsy Crower pj/Manager
    Edits the name of the 2nd person to be Betsy Crower and clears all existing past jobs and replace it with 'Manager".

3.1.6. Locating persons by name: find

Finds persons whose names contain any of the given keywords.
Format: find KEYWORD [MORE_KEYWORDS]

  • The search is case insensitive. e.g hans will match Hans

  • The order of the keywords does not matter. e.g. Hans Bo will match Bo Hans

  • Only the name is searched.

  • Only full words will be matched e.g. Han will not match Hans

  • Persons matching at least one keyword will be returned (i.e. OR search). e.g. Hans Bo will return Hans Gruber, Bo Yang

Examples:

  • find John
    Returns john and John Doe

  • find Betsy Tim John
    Returns any person having names Betsy, Tim, or John

3.1.7. Deleting a person : delete

Deletes the specified person from slaveFinder().
Format: delete INDEX

  • This command can only be used when All Jobs Screen shows. You can delete an applicant in All Aplicants list

  • Deletes the person at the specified INDEX.

  • The index refers to the index number shown in the displayed person list.

  • The index must be a positive integer 1, 2, 3, …​

Examples:

  • list
    delete 2
    Deletes the 2nd person in slaveFinder().

  • find Betsy
    delete 1
    Deletes the 1st person in the results of the find command.

3.1.8. Clearing all entries : clear

Clears all entries from slaveFinder().
Format: clear

  • This command can only be used when All Jobs Screen shows. You can clear all applicants in All Aplicants list

3.2.1. Create a Job Hiring Process: createJob

Create a Job hiring process with four person lists: "Applicants", "KIV", "Interview", "Shortlist".
Format : createJob [jn/JOBNAME]

  • JOBNAME indicate the job name. This name cannot contain spaces. Names with multiple words are separated by '-'. For example: IOS-Developer.

  • All people in the storage who want to apply this job will automatically be added in "Applied" list.

3.2.2. Delete the Job Hiring Process : deleteJob

Delete a Job Hiring Process and all its information
Format : deleteJob [jn/JOBNAME]

3.2.3. Displays one of the four persons list in a job : displayJob

Displays a Job
Format : displayJob [jn/JOBNAME]

  • Displays all four lists of a job at once

3.2.4. Add all shown persons in a list to another list : addAll

Adds all currently shown people in source list to the destination list
Format : addAll TO FROM(Optional) [jn/JOBNAME](Optional)

  • Filter function can be used to modify the displayed list before moving the people in the list

  • FROM input is optional and if not given, input list will be the displayed list of the entire directory.

  • JOBNAME input is optional if there is a currently displayed job. If provided, both source and destination will be of the provided job.

  • FORM and TO can only be one of the following applied, kiv, interview, shortlist

Examples:

  • list
    createJob jn/Lecturer

  • addAll applied jn/Lecturer
    addAll adds all in database to Lecturer Job

  • addAll kiv applied jn/Lecturer
    addAll adds all in applied list to kiv list in lecturer

3.2.5. Adds people using by index to a selected list in a Job : movePeople

 Moves a few people specified by index from a specified list to another list in a job.+
Format : `movePeople TO FROM INDEXES [jn/JOBNAME]`

  • FROM input can only be given if a job is displayed, input list will be the displayed list of the entire directory.

  • JOBNAME input is required only if there isn’t a displayed job. Should be omitted otherwise.

  • FORM and TO can only be one of the following applied, kiv, interview, shortlist

Examples:

  • list
    createJob jn/Lecturer

  • movePeople applied 1, 2 jn/Lecturer
    moves persons with index 1 and 2 to applied list in Lecturer

  • displayJob jn/Lecturer

  • movePeople kiv applied 2
    moves person 2 in applied list to kiv list in Lecturer

3.2.6. Adds people using by index to a selected list in a Job : remove

 Removes people from a specific list in Job+
Format : `remove FROM INDEXES [jn/JOBNAME]`

  • Only usage if on display job screen

3.2.7. Select people into "Interview" List: selectInterview Coming in v2.0

Select people from display board to the Job Hiring Process’s "Interviewed" list
Format : selectInterview [INDEX] [INDEX-INDEX] [all]

  • Edits the person at the specified INDEX. The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …​

  • At least one of the optional fields must be provided.

  • You can add all people on the Person Display List to the "Interview" list by using all parameter.

Examples:

  • selectInterview 2-10
    Selects the 2nd person to 10th people to the "Interview" list.

  • selectInterview 2 4 Selects the 2nd person and 4th people to the "Interview" list.

  • selectInterview all Selects all the people on the Person Display List to the "Interview" list.

3.2.8. Select people into "To be sent to boss" List: selectfinal Coming in v2.0

Select people from display board to the Job Hiring Process’s "To be sent to boss" List
Format : selectInterview [INDEX] [INDEX-INDEX] [all]

  • Edits the person at the specified INDEX. The index refers to the index number shown in the displayed person list. The index must be a positive integer 1, 2, 3, …​

  • At least one of the optional fields must be provided.

  • You can add all people on the Person Display List to the "To be sent to boss" list by using all parameter.

3.2.9. Generate a final report for the Job Hiring Process : report Coming in v2.0

Generate report.txt to show 3 categories of applicants for a specific role: "Applied", "Interview", "To be sent to boss". in a Job Hiring Process.
Format : report JOBNAME

3.3.1. Filter results : filter

Filter the people displayed on the Person List. Each filer has a name and can be delete, diplay result always base on all filter request.
Format: filter [FILTERLISTNAME] fn/FILTERNAME [n/NAME] pp/PHONE_NUMBER] [nric/NRIC] [e/EMAIL] [a/ADDRESS] [g/GENDER] [r/RACE] [m/MAJOR] [s/SCHOOL] [gr/GRADE] [is1/INTERVIEWSCORESQ1] [is2/INTERVIEWSCORESQ2] [is3/INTERVIEWSCORESQ3] [is4/INTERVIEWSCORESQ4] [is5/INTERVIEWSCORESQ5] [j/JOBS_APPLY]…​ [kpl/KnowPROGLANG]…​ [pj/PASTJOB]…​

  • This command can be used in both All Jobs Screen and Job Detail Screen, when Screen is All JOb Showing Screen, FILTERLISTNAME should be empty.

  • When Screen is Job Detail Screen (four applicants lists shows), FILTERLISTNAME is needed.

  • FILTERLISTNAME indicate which Job list this command will used.

  • FILTERLISTNAME can be full name of the job lists such as "Applicant", "KIV", "Interview", "Shortlist".

  • FILTERLISTNAME also can be prefix of the job lists such as "a", "k", "i", "s".

  • Multiple filters can be added to filter people. All the filter labels will show on the Filter Panel.

  • Applicant List always display people base on all undeleted filters. Persons matching all filters will be returned (i.e. AND)

  • The filter can be an empty filter without any filtering parameter. e.g. filter fn/empty All applicants will be matched in empty filter.

  • Filter Name can be any valid String except the String cotaining parameter’s prefixes

    • For example, _, Gender: Male, School: NUS, naming is difficult! can all be a valid filter name.

    • But s/nus, valid filtername n/ can not be a valid filter name and the string after the prefix will be regraded as corresponded information and parse into System.

  • For grade field (Grade and Interview Scores):

    • The Interview has five questions and all the value can be filter by gr/ or is[num]/ (num = {1,2,3,4,5})

    • The keyword is a range and splitted by ;.

    • The keyword should be in correct format. e.g. 3.2-4.3 5 - 6 3 - 1.

    • Persons' grade or scores are exactly equal to the Upper bound or lower bound will return.

    • The Upper bound can lower than lower bound, and no applicants will be matched.

    • Persons matching at least one keyword (range) will be returned (i.e. OR ). e.g. gr/3-4; 4-5 will match person with grade in range [3,4] and [4,5].

  • For other field:

    • The keyword can be any string and splitted by space.

    • The match is case insensitive. e.g hans will match Hans

    • The order of the keywords does not matter. e.g. Hans Bo will match Bo Hans

    • Only full words will be matched e.g. Han will not match Hans

    • Persons matching at least one keyword will be returned (i.e. OR ). e.g. Hans Bo will match Hans Gruber, Bo Yang

Examples:

  • filter fn/nus s/nus
    Shows all persons whose school is NUS in All Applicants List.

  • filter fn/nus s/nus m/CS
    Shows all persons whose school is NUS and major is CS in All Applicants List.

  • filter fn/nus s/nus
    filter fn/CS m/CS Shows all persons whose school is NUS and major is CS in All Applicants List.

  • filter fn/grade gr/4.8-5.0;3.0-3.1
    Shows all persons whose grade in range of [4.8,5.0] or [3.0,3.1] in All Applicants List.

  • filter Interview fn/nus s/nus
    Shows all persons whose school is NUS in Interview List in Job Detail Screen.

3.3.2. Delete a Filter : deleteFilter

Delete a filter showing on the display board and renew the update display people list.
Format: deleteFilter [FILTERLISTNAME] FILTERNAME

  • This command can be used in both All Jobs Screen and Job Detail Screen, when Screen is All JOb Showing Screen, FILTERLISTNAME should be empty.

  • When Screen is Job Detail Screen (four applicants lists shows), FILTERLISTNAME is needed.

  • FILTERLISTNAME indicate which Job list this command will used.

  • FILTERLISTNAME can be full name of the job lists such as "Applicant", "KIV", "Interview", "Shortlist".

  • FILTERLISTNAME also can be prefix of the job lists such as "a", "k", "i", "s".

  • You can only delete one filter perin one command. The filter label you delete will disappear on the Filter Panel.

  • Applicants List always display people base on all undeleted filters.Persons matching all filters will be returned (i.e. AND)

Examples:

  • filter fn/nus s/nus
    Shows all persons whose school is NUS in All Applicants List.

  • deleteFilter nus Shows all persons in All Applicants List.

  • filter Interview fn/nus s/nus
    Shows all persons whose school is NUS in Interview List in Job Detail Screen.

  • deleteFilter Interview fn/nus
    Shows all persons in Interview List in Job Detail Screen.

3.3.3. Clear a Filter List: clearFilter

Clear a filter showing on the display board and renew the update display people list.
Format: clearFilter [FILTERLISTNAME]

  • This command can be used in both All Jobs Screen and Job Detail Screen, when Screen is All JOb Showing Screen, FILTERLISTNAME should be empty.

  • When Screen is Job Detail Screen (four applicants lists shows), FILTERLISTNAME is needed.

  • FILTERLISTNAME indicate which Job list this command will used.

  • FILTERLISTNAME can be full name of the job lists such as "Applicant", "KIV", "Interview", "Shortlist".

  • FILTERLISTNAME also can be prefix of the job lists such as "a", "k", "i", "s".

Examples:

  • filter fn/nus s/nus
    filter fn/CS m/CS Shows all persons whose school is NUS and major is CS in All Applicants List.

  • clearFilter Shows all persons in All Applicants List.

  • filter Interview fn/nus s/nus
    filter Interview fn/CS m/CS Shows all persons whose school is NUS and major is CS in Interview List in Job Detail Screen.

  • clearFilter Interview
    Shows all persons in Interview List in Job Detail Screen.

3.4.1. Display Analytics : analytics

Display the analytics of applicants for desired job list (applicant, kiv, interview, shortlist) or all applicants.
Format : analytics LISTNAME or analytics (for all applicants)

  • LISTNAME indicate which Job list this command will be used.

  • LISTNAME can are the names of job lists such as "applicant", "kiv", "interview", "shortlist".

  • If no LISTNAME is entered, the analytis of all applicants in the slave system will be shown.

  • If have never used the DisplayJob command before, using analytics LISTNAME will be empty analytics.

  • If on all applicants and all jobs page, analytics LISTNAME will display analytics on the job last displayed using command DisplayJob

Examples:

  • analytics applicant

  • analytics kiv

  • analytics

3.5.1. Generate Interview Dates : generateInterviews

Generate interview dates for all applicants in slaveFinder(). Interview dates cannot be generated again if they are already present. Dates generated exclude weekends and block out dates(see below).

3.5.2. Generate Interview Dates for a particular job : generateInterviews jn/[JOB_NAME] Coming in v2.0

Generate interviews for applicants of a particular job in slaveFinder(). Interview dates cannot be generated again if they are already present. Dates generated exclude weekends and block out dates(see below).

3.5.3. Clear Interview Dates : clearInterviews

Clears the list of generated interview dates.

3.5.4. Clear Interview Dates for a specified job opening : clearInterviews jn/[JOB_NAME] Coming in v2.0

Clears the list of generated interview dates for the specified job.

3.5.5. Set maximum number of interviews a day : setMaxInterviewsADay [NUMBER]

Sets the maximum number of interviews to be generated in a day.

3.5.6. Set block out dates for interviews : setBlockOutDates [DD/MM/YYYY] OR [DD/MM/YYYY - DD/MM/YYYY] OR [DD/MM/YYYY], [DD/MM/YYYY - DD/MM/YYYY]

Sets the block out dates(unavailable dates) which the interviewer is not available for interviews to be scheduled.

3.5.7. Show interviews dates : showInterviews

Shows the list of dates which the interviewees in slaveFinder() are assigned. (Show is not considered an operation in terms of undo/redo, therefore when undo, the previous command before showInterviews is called)

3.5.8. Show interviews dates for a job opening : showInterviews jn/[JOB_NAME] Coming in v2.0

Shows the list of dates which the interviewees for the state job in slaveFinder() are assigned to.

3.5.9. Reschedule Person for interview: move jn/[JOB_NAME] nric/[NRIC] [FROM_DATE(dd/mm/yyyy)] [TO_DATE(dd/mm/yyyy)] Coming in v2.0

Reschedules a person scheduled to a particular date to another date. If to date is not present, the person is removed from that date.

3.5.10. Save interviews data Coming in v2.0

Scheduled interviews is automatically stored in a json file.

3.6. Other Basic Command

3.6.1. Viewing help : help

Format: help

3.6.2. Listing entered commands : history

Lists all the commands that you have entered in reverse chronological order.
Format: history

Pressing the ↑ and ↓ arrows will display the previous and next input respectively in the command box.

3.6.3. Undoing previous command : undo

Restores the address book to the state before the previous undoable command was executed.
Format: undo

Undoable commands: those commands that modify the address book’s content (add, delete, edit, clear, createJob, deleteJob, generateInterviews, setMaxInterviewsADay, setBlockOutDates, clearInterviews, filter, delete filter ).

Examples:

  • edit 1 n/Johnny
    list
    undo (reverses the edit 1 n/Johnny command)

3.6.4. Redoing the previously undone command : redo

Reverses the most recent undo command.
Format: redo

Examples:

  • edit 1 n/Johnny
    undo (reverses the edit 1 n/Johnny command)
    redo (reapplies the edit 1 n/Johnny command)

  • edit 1 n/Johnny
    redo
    The redo command fails as there are no undo commands executed previously.

  • edit 1 n/Johnny
    clear
    undo (reverses the clear command)
    undo (reverses the edit 1 n/Johnny command)
    redo (reapplies the edit 1 n/Johnny command)
    redo (reapplies the clear command)

3.6.5. Exiting the program : exit

Exits the program.
Format: exit

3.6.6. Saving the data

Address book data are saved in the hard disk automatically after any command that changes the data.
There is no need to save manually.

4. FAQ

Q: How do I transfer my data to another Computer?
A: Install the app in the other computer and overwrite the empty data file it creates with the file that contains the data of your previous Address Book folder.

5. Command Summary

  • Add add n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS g/GENDER r/RACE m/MAJOR s/SCHOOL [pj/PAST_JOB]…​ `
    e.g. `add n/James Ho p/22224444 e/jamesho@example.com a/123, Clementi Rd, 1234665 g/Male r/Chinese m/MATH s/NUS pj/Professor t/friend t/colleague

  • Clear : clear

  • Delete : delete INDEX
    e.g. delete 3

  • Edit : edit INDEX [n/NAME] [p/PHONE] [e/EMAIL] [a/ADDRESS] [g/GENDER] [r/RACE] [s/SCHOOL] [pj/PAST_JOBS] `
    e.g. `edit 2 n/James Lee e/jameslee@example.com

  • List : list

  • Help : help

  • History : history

  • Undo : undo

  • Redo : redo

  • Generate Interviews : generateInterviews

  • Set maximum number of interviews a day : setMaxInterviewsADay[MAX_NUM_INTERVIEWS]

  • Set block out dates for interviews : `setBlockOutDATES[DD/MM/YYYY OR DD/MM/YYYY - DD/MM/YYYY]

  • Clear interviews dates : clearInterviews

  • Read to slaveFinder() : readAll

  • Get ranked list : getRankedList

  • Filter search results : filter [FILTERLISTNAME] [fn/FILterName] [n/NAME] [p/PHONE] [e/EMAIL] [a/ADDRESS] [g/GENDER] [r/RACE] [s/SCHOOL] [pj/PAST_JOBS] `
    e.g. `filter fn/Chinese r/Chinese

  • Delete Filter search results : `deleteFilter [FILTERLISTNAME] [fn/FILterName] `
    e.g. `deleteFilter fn/Chinese `

  • Clear Filter search results : `clearFilter [FILTERLISTNAME] `
    e.g. `clearFilter `

  • Display Hiring Process : displayProcess

  • Display Analytics : analytics LISTNAME or analytics

  • Create Job : createJob [jn/JOBNAME]

  • Delete Job : deleteJob [jn/JOBNAME]

  • Display Job : displayJob [jn/JOBNAME]

  • Add All : addAll TO FROM(OPTIONAL) [jn/JOBNAME](OPTIONAL)

  • Move People : movePeople TO FROM(OPTIONAL) INDEXES [jn/JOBNAME](ONLY ON DEFAULT SCREEN)

  • Remove : 'remove FROM INDEXES [jn/JOBNAME]'