-
Notifications
You must be signed in to change notification settings - Fork 31
Database Documentation
adamjl217 edited this page Jun 27, 2018
·
4 revisions

Batch table:
- Batch Id
- Primary Key
- Batch End Date
- Batch Name
- ‘YYMM MMMDD curriculum’ format
- Batch Start Date
- Batch Location Id
- References the Batch Location
- Curriculum Id
- References the Curriculum
Batch Location
- Batch Location Id
- Primary Key
- Location Name
- Describes where the batch is located
- 1 Revature LLC
- 2 UMUC
- 3 USF
- 4 SkySong
- 5 Tech Incubator
- 6 CUNY
Associate Table:
- Associated Id
- Primary Key
- First name
- Last name
- Batch Id
- References the associated Batch
- Client Id
- References the associated Client
- End Client Id
- References another associated End Client
- Marketing Status Id
- References the Marketing table, and describes the status (Mapped: Training, Mapped: selected, Unmapped: open, etc)
- Client Start Date
- User Id
- References the User object, which contains username and password
- Staging Feedback
- Input by staging manager for how an associate performed while in staging
Placement Table:
- Placement Id
- Primary Key
- Placement End Date
- Null if not confirmed
- Placement Start Date
- Associate Id
- References the Associate
- Client Id
- References the Client
- End Client Id
- References the End Client
Interview Table:
- Interview Id
- Primary Key
- Interview Date
- Associate Id
- References the Associate
- Client Id
- References the Client
- End Client Id
- References the End Client
- Interview Type Id
- References the Interview Type
- Date Associate Issued
- Date the interview was given to an Associate
- Date Sales Issued
- Flag Reason
- Job Description
- Is Client Feedback Visible
- Yes/No (1/0)
- Is Interview Flagged
- Associate Feedback
- Feedback given by the associate on how the interview went
- Client Feedback
- Feedback given by the client on how the interview went
- Question Given
- Were questions provided to the associate (?)
- Was 24 hour notice given
- Yes/No (1/0)
Marketing Status Table:
- Marketing Status Id
- Primary Key
- Referenced by Associate
- Status Name:
- MAPPED: TRAINING indicates all associated from the moment they start training
- MAPPED: RESERVED indicates all associates that have been promoted and are in staging, before interviews
- MAPPED: SELECTED indicates associated that have had an interview and received feedback for selection
- MAPPED: CONFIRMED indicates associates which have documentation paperwork for starting at client location
- MAPPED: DEPLOYED indicates associates that are currently at the client location
- UNMAPPED: TRAINING –Associates that are training and not mapped
- UNMAPPED: OPEN indicates associates who have gone through interview process and were not selected by client and are in
- staging, or associates that have returned from previous projects and are free to interview with any client
- UNMAPPED: SELECTED indicates an unmapped associate who has been selected after an interview
- UNMAPPED: CONFIRMED indicates an unmapped associate who has been interviewed and provided paperwork for a start date
- UNMAPPED: DEPLOYED indicates an unmapped associate who is currently working at a client location
- DIRECT PLACEMENT: represents associates that have been hired directly by client
- TERMINATED: associate is no longer with the company for whatever reason
Client Table:
- Client Id
- Primary Key
- Referenced by Associate , Interview
- Client Name
End Client Table:
- Client Id
- Primary Key
- Client Name
- Name related to end client of an account holder, typically represents the client location an associate is being sent to.
- Can be the same as account holder.
Interview Type Table:
- Interview Type Id
- Primary Key
- Interview Type Name
- Name related to the circumstance of interview, being phone, skype, inhouse, ect..
Curriculum Table:
- Curriculum Id
- Primary Key
- Curriculum Name:
- Name referring to specification of a batch
- 1 JTA
- 2 Java
- 3 .Net
- 4 PEGA
- 5 DynamicCRM
- 6 Salesforce
- 7 Microservices
- 8 SEED
- 9 Oracle Fusion
User Table:
- User Id
- Primary Key
- Username
- For login
- Hashed Password
- For login
- Note: if the password is not hashed, the user will never be allowed to login (due to business logic)
- Role Id
- References the Role Type
- Describes what kind of user is logging in (admin, associate, etc)
- Is Approved
- Yes/No (1/0)
- Describes if the user will be able to login
Role Table:
- Role Id
- Primary Key
- Role Name
- Describes the role of the user
- 1 Admin
- 2 Trainer
- 3 Sale-Delivery
- 4 Staging
- 5 Associate