Using references to search results in Book: Unterschied zwischen den Versionen

Aus DRV STRING
Wechseln zu: Navigation, Suche
(Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''(Using references to search results in Book)'' == '''Module:'''Handling: Booking administration == Description == Co…“)
 
K
 
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 2: Zeile 2:
 
[[Kategorie:UseCases]]
 
[[Kategorie:UseCases]]
  
−
== Use Case: ''(Using references to search results in Book)'' ==
+
== Use Case: ''Using references to search results in Book'' ==
  
 
'''Module:'''Handling: Booking administration
 
'''Module:'''Handling: Booking administration
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 18: Zeile 18:
 
* Human lookup in a brochure
 
* 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'''.
  
−
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, 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 ==
 +
Changes:
 +
* All attributes in <code>Object</code> become optional
 +
* New Element SearchResultReference <code>CDATA</code>.
 +
Example:
 +
<syntaxhighlight lang="XML">
 +
<StringBookRequest>
 +
<Accommodation TourOperatorCode="NEC" TravelType="BETT">
 +
<Objects>
 +
<Object ID="01">
 +
                                <!-- using a search result reference rather than an object description --> 
 +
<SearchResultReference>
 +
                                    <![CDATA[6ba7b810-9dad-11d1-80b4-00c04fd430c8.]]>
 +
</SearchResultReference>
 +
</Object>
 +
</Objects>
 +
</Accommodation>
 +
</StringBookRequest>
 +
</syntaxhighlight>
  
 
== Response Data ==
 
== Response Data ==
−
  unchanged
+
No change.

Aktuelle Version vom 14. Dezember 2016, 07:44 Uhr


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 instead of entering 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 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, 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

Changes:

  • All attributes in Object become optional
  • New Element SearchResultReference CDATA.

Example: 

<StringBookRequest>
	<Accommodation TourOperatorCode="NEC" TravelType="BETT">
		<Objects>
			<Object ID="01">
                                <!-- using a search result reference rather than an object description -->   
				<SearchResultReference>
                                     <![CDATA[6ba7b810-9dad-11d1-80b4-00c04fd430c8.]]>
				</SearchResultReference>
			</Object>
		</Objects>
	</Accommodation>
</StringBookRequest>

Response Data

No change.

Von „http://string.drv.de/wiki/index.php?title=Using_references_to_search_results_in_Book&oldid=180“