You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on our earlier understanding, fulfilment was supposed to have an address object which denoted the location that particular session would be delivered. Refer below sample schema:
But in current 1.x core schema, fulfilment no longer have a schema that can hold an address in any shape or form. Instead, now locations are stored at provider level and each item holds an array of location_ids.
This doesn't translate well to mentoring scenarios like:
A session (item) having multiple slots (fulfilments) which are delivered at different locations at different times.
Ideally having locations in fulfilment enables the above scenario. Please advice on how to proceed forward with this.
Subsequently, what will the intent of a search request looks like when searching for "sessions by location"? Is this a fair representation (Adapted to latest location schema):
If this is a fair representation, We are interested in understanding the required granularity of location. Like if we specify a city, do we need to specify state and country too, or is city code enough to uniquely identify the location?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Based on our earlier understanding, fulfilment was supposed to have an address object which denoted the location that particular session would be delivered. Refer below sample schema:
But in current 1.x core schema, fulfilment no longer have a schema that can hold an address in any shape or form. Instead, now locations are stored at provider level and each item holds an array of location_ids.
This doesn't translate well to mentoring scenarios like:
Ideally having locations in fulfilment enables the above scenario. Please advice on how to proceed forward with this.
Subsequently, what will the intent of a search request looks like when searching for "sessions by location"? Is this a fair representation (Adapted to latest location schema):
If this is a fair representation, We are interested in understanding the required granularity of location. Like if we specify a city, do we need to specify state and country too, or is city code enough to uniquely identify the location?
cc: @ravi-prakash-v, @aks30, @vijiurs, @kiranharidas187
Beta Was this translation helpful? Give feedback.
All reactions