Jobeet: Difference between revisions
No edit summary |
|||
Line 13: | Line 13: | ||
The first refactoring was <html><a href=http://jobeet.meansofproduction.biz>complete</a></html> in early 20114-04. | The first refactoring was <html><a href=http://jobeet.meansofproduction.biz>complete</a></html> in early 20114-04. | ||
<blockquote> | |||
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. | |||
</blockquote> | |||
=== 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 == | == Carries Symfony-Drupal Salient == |
Revision as of 10:39, 29 April 2014
Original Function
"Jobeet2" is what the Symfony developers call an example app that is a jobs site used as a model use case of their framework.
- Chapters up to 19 for Symphony 2.
- Original Jobeet (Symfony 1)
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
- Jobs are actual completed jobs in such lines of business
- 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.