Auto-tagging on ingest is the process of assigning the tag automatically to the incoming message according to the rules run on the backend.
Your internal IT Team communicates and approves the rules with your dedicated Sedna Account Manager.
- How does it work?
One of the most commonly used auto-taggers is called Optimistic Job Reference Tagger.
Each customer who has it enabled has their own specifications, but all of them are based on the same general rule.
The Optimistic Job Reference Tagger is commonly used in conjunction with the Veson IMOS integration and provides a way to “optimistically” match a message subject that may only contain partial details of a voyage (e.g. vessel name, voyage number) against a voyage type Job Reference based on the attributes that are stored against the Job Reference.
When a new voyage is created in IMOS it will automatically create the corresponding job tag in SEDNA via the integration, populated with the relevant attributes (voyage number, vessel name and etc) that are used in the auto-tagger configuration. This data will then be stored in SEDNA’s database - to be used as a reference when a message is received. Whenever the voyage is updated in IMOS the new data will be pushed via API and update the record in SEDNA’s database. Normally, the job tag is displayed as “[VESSEL NAME]-[voyage number]”.
This is a summary of how the Optimistic Job Reference Tagger works and applies the tags which are generated and pushed into Sedna with the required attributes:
Message arrives in Sedna -> auto-tagger analyses the subject line and tries to find the best match by following the below rules.
- Look for an exact Job Reference match in the subject, if none found, then:
- Look for a vessel name in the subject or the vessel email in the “from” field, then once matched:
- Look for a Voyage number present in the subject
If no Voyage Number found, then:
- Get Latest COMMENCED / ENROUTE Job reference in subset
- Get Latest SCHEDULED Job reference in subset
- Get Latest COMPLETED Job reference
The auto-tagger will scan the subject line and rules until it finds the first match.
- Can you provide a specific example?
-Message received in Sedna with the subject line: ‘Paradise Island - please schedule’
-Expected job reference tag to be auto-applied:
- The job reference tag PARADISE ISLAND-9 has the following attributes sent to Sedna by IMOS
- The Optimistic Job Reference Tagger will inspect the subject line to find the match:
- Does ‘Paradise Island - please schedule’ subject line contain the exact match of the job tag?
- It has no exact match
- Does the subject line contain the vessel name that matches any of the job references?
- It does contain the vessel name for Job tag PARADISE ISLAND-9 and vessel name is "PARADISE ISLAND".
- Does the subject line contain a voyage number?
-No it doesn’t
THEN
- Get Latest COMMENCED / ENROUTE Job reference in subset:
-”PARADISE ISLAND-9" has the most recently commenced date:
"commencedDateTime":"2022-09-09T06:24:00""
THEN
The Optimistic Job Reference Tagger will apply the PARADISE ISLAND-9 to the message.
Please note the Optimistic Job Reference Tagger logic can be different for each of the customers, some customers may have a different tagger or combinations of taggers applied to certain teams.
- What are the tags that are considered for auto-tagging?
Job reference tags that have specific attributes assigned based on the customer needs such as vessel name, voyage number, refno and etc.
Such tags are generated based on the API integration set up between Sedna and the customer's system of record. The most common systems of record are:
- Dataloy
- Veson (IMOS)
- Shipfix
- Shipamax
- Abraxa
- AXSMarine
You can request integration with a system of record through the Connected Apps section.
The job reference tags with attributes can also be created using the ‘Manage Job Tags’ feature if such is enabled in the customer’s Sedna account.
- What should I do if the message was not auto-tagged though it should have been or an incorrect tag was applied?
Please raise a ticket with Sedna Support providing the following details:
-Message IDs where the job reference tag was supposed to be applied. You can copy the message ID here
- Job reference tag name that you expected to be applied.
- Explanation why you expect this tag to be applied.
- Message ids where the job tag was applied correctly if any.
Comments
0 comments
Please sign in to leave a comment.