Changes between Version 14 and Version 15 of BluePrint/Requests/2.0


Ignore:
Timestamp:
09/20/21 06:44:30 (2 years ago)
Author:
Fran Boon
Comment:

Proposals -> Phases

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/Requests/2.0

    v14 v15  
    2525* Enable future support for implementation of [https://docs.oasis-open.org/emergency/edxl-rm/v1.0/EDXL-RM-SPEC-V1.0.html EDXL-RM]
    2626
    27 == Proposal 1 ==
     27== Phase 1 ==
    2828* REQ should only have a single Requests system, for which the req_need model is more suitable.
    2929* req_req should be stripped down to it's logistics core usecase & moved to inv_req
    … …  
    3434 * req_job moved to req_need_job
    3535
     36=== SHARE ===
     37There are also some models which are just used by SHARE & should be moved to that template (as share_*):
     38* req_need_line
     39* req_need_response
     40* req_need_response_line
     41* req_need_response_organisation
     42* event_event_need_response
     43
    3644=== Pros ===
    37 * Easy to implement
    38 * Req becomes cleaner
     45* Fairly easy to implement
     46* Req becomes cleaner & ready for Phase 2
    3947* Logistics templates, like RMS, don't need to enable the Req module
    40 === Cons ===
    41 * Still end up with 2 separate Requests systems
    4248
    43 == Proposal 2 ==
    44 Replace both req_need & req_req (& associated tables) with:
     49=== Issues ===
     50* Still have 2 separate Requests systems
     51
     52== Phase 2 ==
     53Move req_need (& associated tables) to SHARE.
     54
     55Replace with a new Requests model:
    4556{{{
    4657=> req_availability (inc commit_status)
    … …  
    6879 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,
    6980org=>office address, site=>site location) if not explicitly provided
    70 === Pros ===
    71 * End up with a single Requests system
    72 === Cons ===
     81
     82=== Issues ===
    7383* Using pe_id for requester means that we are directly accessing a !SuperEntity, which is bad for permissions (can't differentiate by instance_type)
    7484* HRM (~mandatory model) has a link to Req (optional module) which should be avoided
    75 
    76 == SHARE ==
    77 There are also some models which are just used by SHARE & should be moved to that template (as share_*):
    78 * req_need_line
    79 * req_need_response
    80 * req_need_response_line
    81 * req_need_response_organisation