Using references to search results in Book - Versionsgeschichte

Holtermp am 14. Dezember 2016 um 07:44 Uhr

2016-12-14T07:44:46Z

← Nächstältere Version		Version vom 14. Dezember 2016, 07:44 Uhr
Zeile 21:		Zeile 21:

	The use case makes '''no assumption about the structure''' of the id, any structure might be possible (e.g. UUID, xml, json). Consequently the reference in the StringBookRequest should be CData		The use case makes '''no assumption about the structure''' of the id, any structure might be possible (e.g. UUID, xml, json). Consequently the reference in the StringBookRequest should be CData
			The configuration query has to show if this mechanism is supported by the operator system.



	== Request Data ==		== Request Data ==

Holtermp am 24. November 2016 um 13:12 Uhr

2016-11-24T13:12:46Z

← Nächstältere Version		Version vom 24. November 2016, 13:12 Uhr
Zeile 8:		Zeile 8:
	== Description ==		== Description ==

	Consider the following situation: We have searched for a specific product e.g. a flight. We have selected a search result that we want to book. Sometimes it can be preferable or even necessary to use a reference to the search result ~~than~~ to ~~enter~~ the description of the product that is to be booked.		Consider the following situation: We have searched for a specific product e.g. a flight. We have selected a search result that we want to book. Sometimes it can be preferable or even necessary to use a reference to the search result instead of entering the description of the product that is to be booked.
	Examples:		Examples:
	* We search for flights and the airline CRS returns search results containing ids that '''have to be used''' to book the flight.		* We search for flights and the airline CRS returns search results containing ids that '''have to be used''' to book the flight.
Zeile 20:		Zeile 20:
	The use case does '''not require''' any kind of search result to contain an id. But '''if a search result contains''' an id that can be used for booking, the STRING-Booking-Interface should be able to use that by '''referencing that id'''.		The use case does '''not require''' any kind of search result to contain an id. But '''if a search result contains''' an id that can be used for booking, the STRING-Booking-Interface should be able to use that by '''referencing that id'''.

	The use case makes '''no assumption about the structure''' of the id ~~search result~~, any structure might be possible (e.g. UUID, xml, json). Consequently the reference in the StringBookRequest should be CData		The use case makes '''no assumption about the structure''' of the id, any structure might be possible (e.g. UUID, xml, json). Consequently the reference in the StringBookRequest should be CData

Holtermp am 23. November 2016 um 15:14 Uhr

2016-11-23T15:14:50Z

@@ Zeile 2: / Zeile 2: @@
 [[Kategorie:UseCases]]
-== Use Case: ''(Using references to search results in Book)'' ==
+== Use Case: ''Using references to search results in Book'' ==
 '''Module:'''Handling: Booking administration
@@ Zeile 18: / Zeile 18: @@
 * Human lookup in a brochure
 == Request Data ==
 == Response Data ==

Holtermp: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''(Using references to search results in Book)'' == '''Module:'''Handling: Booking administration == Description == Co…“

2016-11-23T14:50:17Z

Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''(Using references to search results in Book)'' == '''Module:'''Handling: Booking administration == Description == Co…“

Neue Seite

[[Kategorie:UseCases]]

== Use Case: ''(Using references to search results in Book)'' ==

'''Module:'''Handling: Booking administration

== Description ==

Consider the following situation: We have searched for a specific product e.g. a flight. We have selected a search result that we want to book. Sometimes it can be preferable or even necessary to use a reference to the search result than to enter the description of the product that is to be booked.
Examples:
* We search for flights and the airline CRS returns search results containing ids that '''have to be used''' to book the flight.
* We search for flights and the search result is '''very complex''': departure and arrival location and time, compartment class, booking class for every segment... it might be more convenient to simply reference the search result instead of copying all the search result detailed

The use case is '''independent of the type of search''' that delivered the search result. Examples might be
* DRV Suchschnittstelle
* Any kind of tour operater / CRS export
* Human lookup in a brochure

The use case makes '''no assumption about the structure''' of the id search result, any structure might be possible (e.g. UUID, xml, json).

The use case does '''not require''' any kind of search result to contain an id. But '''if a search result contains'' an id that can be used for booking, the STRING-Booking-Interface should be able to use that by '''referencing that id'''.

== Request Data ==

== Response Data ==
unchanged