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

Timestamp:

09/19/21 20:30:50 (18 months ago)

Author:

Fran Boon

Comment:

PE Location/Timeframe

BluePrint/Requests/2.0

@@ -18 +18 @@
 * REQ & INV should both be able to operate without the other
  * This is currently the case & shouldn't get broken by this restructure
+* Enable support in SAFIRE for Requesting Consumables/Assets (by Item Type, possibly Named as well)/People (by Job Title, possibly Named as well)
 * Enable support for future implementation of [https://docs.oasis-open.org/emergency/edxl-rm/v1.0/EDXL-RM-SPEC-V1.0.html EDXL-RM]
 
@@ -30 +31 @@
 
 == Proposal 2 ==
+Replace both req_need & req_req (& associated tables) with:
 {{{
 => req_availability (inc commit_status)
@@ -45 +47 @@
  * e.g. an external acquisition request would be referenced as document in the inv_send, but not establish an internal req_acquisition record.
  * 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).
+* req_availability
+ * has a timeframe
+ * might be anonymous
+ * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,
+org=>office address, site=>site location) if not explicitly provided
+* req_acquisition
+ * has a timeframe
+ * might be anonymous if using a pick-up mode using an identity-proxy (i.e. ticket, or voucher)
+ * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,
+org=>office address, site=>site location) if not explicitly provided
 
 == SHARE ==