Access to Tideworks about draynut HOT 3 OPEN

1. Is Container Depots expected to be considered as any other terminal? Should other elements be considered from the PDF?
2. Is there any difference in hierarchy for the different entries here?
3. What happens when we don't have a Terminal code? Is there always going to be one?

from draynut.

1. We understand what a Container Depot is to a human being, we need to understand what should it mean to a computer within this specific workflow. There is no specified mechanic (if any) as to what happens when the Terminal is a Container Depot within the provided data model / sites/ APIs and Dictionary nor we've seen any such data in the PDFs. Is there a specific workflow to be defined here?

2. A Hierarchy implies that a given object governs another. It is unclear how Container Depot would show up in any input (please see the other ticket where we ask about all the possible inputs to the system which need to be accounted for, what types of PDFs and what types of content). It is also unclear whether the mention of Container Depot in a PDF order should be governed by another process and therefore how should that be reflected in the data model. Current policy is, should Container Depot be mentioned, add it like a job to a specific Terminal with no further actions/entities defined.

3. No. If there's no terminal code, then there's no terminal, if there's no terminal, then there's no data from the terminal, no Status flag and no scrapping. This is very critical as the availability flag and any other data from the terminal depends on validating the Terminal as the rightful one. The process of pattern matching to validate a Terminal is associated to a job in the data model and with no further references in the input PDF other than 'city' is complex and cannot be guaranteed for the scope of this PoC.

from draynut.

4. Is Antillean Marine really without any public data?

from draynut.