Changes between Version 2 and Version 3 of BluePrint/Requests/2.0


Ignore:
Timestamp:
09/19/21 20:30:50 (4 months ago)
Author:
Fran Boon
Comment:

PE Location/Timeframe

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Requests/2.0

    v2 v3  
    1818* REQ & INV should both be able to operate without the other
    1919 * This is currently the case & shouldn't get broken by this restructure
     20* Enable support in SAFIRE for Requesting Consumables/Assets (by Item Type, possibly Named as well)/People (by Job Title, possibly Named as well)
    2021* Enable support for future implementation of [https://docs.oasis-open.org/emergency/edxl-rm/v1.0/EDXL-RM-SPEC-V1.0.html EDXL-RM]
    2122
     
    3031
    3132== Proposal 2 ==
     33Replace both req_need & req_req (& associated tables) with:
    3234{{{
    3335=> req_availability (inc commit_status)
     
    4547 * e.g. an external acquisition request would be referenced as document in the inv_send, but not establish an internal req_acquisition record.
    4648 * The internal req_aquisition entity would be to store outgoing requests only (if requesting to another entity in the same system then it would only be seen like this to the requesting entity).
     49* req_availability
     50 * has a timeframe
     51 * might be anonymous
     52 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,
     53org=>office address, site=>site location) if not explicitly provided
     54* req_acquisition
     55 * has a timeframe
     56 * might be anonymous if using a pick-up mode using an identity-proxy (i.e. ticket, or voucher)
     57 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,
     58org=>office address, site=>site location) if not explicitly provided
    4759
    4860== SHARE ==