Jobeet: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| (26 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
{{TOCright}} | {{TOCright}} | ||
<blockquote> | <blockquote> | ||
"[http://www.ens.ro/2012/03/21/jobeet-tutorial-with-symfony2/ Jobeet]" - originally, a Symfony tutorial app use case that is a fully functional jobs site . | "[http://www.ens.ro/2012/03/21/jobeet-tutorial-with-symfony2/ Jobeet]" - originally, a Symfony tutorial app use case that is a [http://jobeet.org fully functional jobs site] . | ||
* [http://www.intelligentbee.com/blog/?s=jobeet Chapters up to 19] for Symphony 2. | * [http://www.intelligentbee.com/blog/?s=jobeet Chapters up to 19] for Symphony 2. | ||
* [http://symfony.com/legacy/doc/jobeet/1_2?orm=Propel Original Jobeet (Symfony 1)] | * [http://symfony.com/legacy/doc/jobeet/1_2?orm=Propel Original Jobeet (Symfony 1)] | ||
| Line 9: | Line 9: | ||
The laconic/DRY design package in the next § moves with working target. Other top level stuff below it. | The laconic/DRY design package in the next § moves with working target. Other top level stuff below it. | ||
== Day | == Day 0 Refactor for DS == | ||
[[File:jobeet.jpg|thumb|275px|left|Figure 1: Image of Sensio Jobeet]] | [[File:jobeet.jpg|thumb|275px|left|Figure 1: Image of Sensio Jobeet]] | ||
=== Story Rewrites / Additions === | === Story Rewrites / Additions === | ||
| Line 16: | Line 16: | ||
==== F0: The user is defined per PM ==== | ==== F0: The user is defined per PM ==== | ||
The tutorial did not really address registration or the like, there's actually only admin and anonymous class and the later are created and defined by use of the job posting form. In Jobim, a DS/PM SSO is operative | The tutorial did not really address registration or the like, there's actually only admin and anonymous class and the later are created and defined by use of the job posting form. In Jobim, a DS/PM SSO is operative. | ||
==== F1: On the homepage, the user sees the active biz cases ==== | ==== F1: On the homepage, the user sees the active biz cases ==== | ||
The homepage displays the lines of biz and the cases the practitioner wants to pursue, exemplifying the refactoring of the original. | |||
The search function is essentially the same but with the shown altered target domain and changes in the field targets as well. | |||
==== F5: A user posts a job ==== | ==== F5: A user posts a job ==== | ||
The Post a Job form becomes sensitive to the users PM role: | |||
===== none ===== | |||
The original function of the posting form is preserved for the anonymous user. The disposition of the post is determined by the practitioner and may be either kept local or posted to the general PJS. | |||
===== customer ===== | |||
A posting by a customer is interpreted as a job order in PM/PJS. | |||
===== merchant/peer ===== | |||
A posting by a user with this role is a job order which the user is handling as a broker. | |||
==== F6 A user becomes a LoBAffiliate ==== | ==== F6 A user becomes a LoBAffiliate ==== | ||
==== F7 A LoBAffiliate | |||
[[File:jobim.jpg|thumb|275px|right|Figure 2: Image of Jobim]] | |||
This is automatic based on the user having merchant/peer role. | |||
==== F7 A LoBAffiliate retrieves the current active job list ==== | |||
The LoBA may select from either the practitioners cases, all those active in PJS , or both. | |||
==== F8 A mobile app for iOS and Android ==== | |||
"Jobim", as a product name, is only used for the Cordova app of this feature: | |||
# webviews for non-desktop form factors. | |||
# adds a notification service to the affiliate service as originally defined and modified per the reinterpretation of affiliation | |||
# other controls/subfeatures. Small factors will have a small subset of other feature sets, but are the target of the notification service | |||
==== F9 JobsSite Entity and Job Form changes for it ==== | |||
Elements are added to both model and view to associate a jobs site such as Craigslist (that is the specific main target), Monster, etc. with the Job posting/order. | |||
==== B3 An admin manages the affiliates and jobs sites pulls ==== | |||
PJS is populated largely from feeds from jobs sites stimulated by the job postings and collected either by agents running in the practitioners domains or by PJS itself (i.e. in my domains). | |||
==== F10 PJS is populated with scrapes from job sites ==== | |||
This is done in PJS but the FE for it is here. | |||
<hr> | <hr> | ||
| Line 33: | Line 80: | ||
# CategoryAffiliate is replaced in the model by LoBAffiliate | # CategoryAffiliate is replaced in the model by LoBAffiliate | ||
The first refactoring was <html><a href=http://jobeet.meansofproduction.biz>complete</a></html> in early | The first refactoring was <html><a href=http://jobeet.meansofproduction.biz>complete</a></html> in early 2014-05. | ||
<blockquote> | <blockquote> | ||
