Jobeet
Original Function
"Jobeet" - originally, a Symfony tutorial app use case that is a fully functional jobs site .
- Chapters up to 19 for Symphony 2.
- Original Jobeet (Symfony 1)
The laconic/DRY design package in the next § moves with working target. Other top level stuff below it.
Day 27 Refactor for DS
Story Rewrites / Additions
Jobeet for DS/PM is the heart of my use/implementation of the Public Job Shop. It retains much from the original, updated for Symfony 2 and inverted to its purpose in PM/PJS.
F1: On the homepage, the user sees the active biz cases
F5: A user posts a job
F6 A user becomes a LoBAffiliate
F7 A LoBAffiliate gets mobile notifications of a posted job
Meaning Here
In the context of my softwares, the Jobeet original use case has been reworked to a completely different use case and a serious production function in my space:
- Job Categories replaced by Lines of Business
- Two kinds of Jobs, those entered via Doctrine programmatically are actual completed jobs in such lines of business, others job orders
- CategoryAffiliate is replaced in the model by LoBAffiliate
The first refactoring was complete in early 20114-04.
The first refactoring is fairly superficial. The jewel of the refactoring centers on the LoBAffiliate and remodeling it as job sites such as Craigslist, monster, etc. The design intent is that the practitioner can look for related work and those recruiting can post jobs to the Public Market in addition to the attention of the specific practitioner, initially just me.
As a name for standard biz case working pattern
I'm also using this term to refer to an encapsulation of the standardized approach I've developed for working jobs. The specific elements vary, but a timeline, sources in FishEye/Git, and a support network as a WordPress multisite and generally included.
Carries Symfony-Drupal Salient
DS users (initially just my clients) will be able use my space without registration by supplying a single secret, generally known on a group basis. They then can access any resource for which they know another group secret, supplied either operationally and implicitly such as in a URI path member or explicitly bu supplying the role name/id secret.
Primary user identification is performed by a third party or transmitted cert.
