Changes between Version 22 and Version 23 of BluePrint/Requests/2.0


Ignore:
Timestamp:
09/20/21 12:27:36 (8 months ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Requests/2.0

    v22 v23  
    2727
    2828== Phase 1 ==
    29 * REQ should only have a single Requests system, for which the req_need model is more suitable.
    30 * req_req should be stripped down to it's logistics core usecase & moved to inv_req
    31  * Remove types (so remove support for Simple, Skills, etc)
    32  * Similarly req_req_item/req_commit/req_commit_item/req_approver/req_req_tag/req_order_item/req_project_req should be moved to inv_req_item/inv_commit /inv_commit_item/inv_req_tag/inv_req_approver/inv_req_item_order/inv_req_project
    33  * Also move associated !Controllers/Classes/Functions/View
    34  * Remove current req_skill/req_commit_person/req_commit_skill models
    35  * req_job moved to req_need_job
    36 
    37 === SHARE ===
    3829There are also some models which are just used by SHARE & should be moved to that template (as need_*):
    3930* req_need_activity
     
    4334* req_need_response_line
    4435* req_need_response_organisation
    45 * req_need_sector
     36* req_need_sector (can be simply removed, as unused)
     37* event_event_need
    4638* event_event_need_response
     39
     40Whilst doing these, also copy the other req_need models in so that it is self-contained.
     41* req_need
     42* req_need_contact
     43* req_need_item
     44* req_need_organisation
     45
     46=== Status ===
     47* Complete
     48
     49== Phase 2 ==
     50* REQ should only have a single Requests system, for which the req_need model is more suitable.
     51* req_req should be stripped down to it's logistics core usecase & moved to inv_req
     52 * Remove types (so remove support for Simple, Skills, etc)
     53 * Similarly req_req_item/req_commit/req_commit_item/req_approver/req_req_tag/req_order_item/req_project_req should be moved to inv_req_item/inv_commit /inv_commit_item/inv_req_tag/inv_req_approver/inv_req_item_order/inv_req_project
     54 * Also move associated !Controllers/Classes/Functions/View
     55 * Remove current req_skill/req_commit_person/req_commit_skill models
     56 * req_job commented until Phase 3
    4757
    4858=== Pros ===
    4959* Fairly easy to implement
    5060* Req becomes cleaner & ready for Phase 2
    51 * Logistics templates, like RMS, don't need to enable the Req module
     61* Logistics templates, like RMS, don't need to enable the Req module & have a simpler requests system to maintain
    5262
    5363=== Issues ===
    5464* Still have 2 separate Requests systems
    5565
    56 == Phase 2 ==
    57 Move req_need (& associated tables, including event_event_need) to SHARE & CCC templates (SHARE can have req_need not be length=64).
     66== Phase 3 ==
     67Move req_need (& associated tables) to CCC template (SHARE is already isolated now).
    5868
    5969Replace with a new Requests model: