search

IATA-Cargo / ONE-Record

This repository contains the documentation & specs for the ONE Record standard.
https://onerecord.iata.org
MIT License
102 stars 51 forks source link

[Ontology] changeRequest: emergencyContact as an object and link it for the whole shipment (not only per item) #167

Closed LauraWeissgerber closed 1 year ago

LauraWeissgerber commented 1 year ago

In our API it is possible to set a emergency contact for the whole requested shipment.

In the current specification you have two ways to set an emergency contact: BookingOptionRequest - Shipment - Piece - Item - ItemDg - emergencyContact (so you have to do it for every item) BookingOptionRequest - party - company - companyBranch - person - contact

Would it be possible to have a "shortlink" to an emergencyContact? For the sales part we currently do not need item information in the BookingOptrionRequest. My proposal: "emergencyContact" as a new object and link it to BookingOptrionRequest - Shipment: BookingOptionRequest - Shipment - emergencyContact - person

lambertciata commented 1 year ago

In the first way, ItemDg is used when there are dangerous goods declared, so it is specific.

The second way is the right one but I reckon it is a "long way" to get this information. My suggestion would be to add a contactPerson at Shipment or BookingShipment to fulfill that requirement.

LauraWeissgerber commented 1 year ago

I just saw there is the possibility to link it in this way: BookingOptionRequest - parties - partyDetails / company - companyBranch - person - contactType BookingOptionRequest - parties - partyDetails / company - companyBranch - person - firstName BookingOptionRequest - parties - partyDetails / company - companyBranch - person - lastName

I will close this task. This is okay like that :-)