Voyager Workspace
06:42
Parsing SOF Example 🔍
Alison Lindsay
7 days ago
1 view
Copy link
Transcript
Comments
Settings
Transcript
Copy
00:00
In this video, I will go over an example of parsing an sof.
00:05
The The first thing I do is click on the first magnifying glass to see where my SOF events start.
00:13
If I have a really long document and a lot of the pages are not, SOFA helps me quickly find the one that I'm looking for.
00:20
Next, I will scroll through to see which pages I want to be analyzing.
00:27
In this case, I've started on page three as seen on the top left here, and my SOF is only that page.
00:34
If I keep scrolling, I see that there are a couple of delays shown on the next page that have also been highlighted.
00:42
And the parser's done a good job of ignoring all of the other pages.
00:46
For the purpose of this example, I want to filter only for page three.
00:51
To do that, I can use the events filter on the top right of the screen.
00:57
Here I can either use a dropdown or type in a custom page list and we'll focus on page three and apply.
01:05
Now if I scroll down, those events that were highlighted have been removed.
01:08
I can hover over this highlighted line to return back to the first event card.
01:15
Now in this example, I will first look if there are any errors.
01:20
In In this case, there aren't any.
01:22
The parser did a very good job.
01:24
I can remove this date to force an error to show up.
01:30
It will be highlighted in red.
01:32
Now if I toggle, this will remain, but it will hide everything else so I can focus on it.
01:37
To update a time or date, I can either use the calendar module or I can type in in the format shown here.
01:46
This one happened on 23rd of July, 2025 at 1758.
01:59
As soon as I entered that in, the error disappeared and so my card disappeared.
02:03
I can untoggle the show errors to show all of my cards again.
02:07
If cards are parsed out of chronological order, you will see a yellow highlight.
02:14
Let's make this 10 If in the event the parser picked the wrong month or the wrong year, you can use a bulk update to make a change quickly.
02:25
Let's say this was actually 2024, but it parsed all 2025.
02:30
You can go to this bulk update event button and pick the pages to apply it to.
02:35
In this case it's all of page uh3, but if you have specific lines you can add them here.
02:41
I'll just do line 1 through 20 for this example here I can pick a date in in 2024 and I only want to update the year.
02:54
If you want a Bulk update tagged.
02:56
You can do that here as well.
02:59
Now you can see all of my dates for those first 20 lines have updated.
03:04
If you're not sure what line a card is on, you can see it here at the top left of the card.
03:10
After line 20, we should see it return to 2020.
03:16
Now it's time to go through and confirm all of the events and times were parsed correctly.
03:23
Usually I'll just scroll through and it automatically will highlight the line for me that I'm supposed to be looking at.
03:31
Obviously now my dates are wrong since I just changed them.
03:35
But you can see it's picking up most of the events.
03:38
Even this one, it picked up both vessel arrived and nor tendered.
03:42
On this one you can see that the date is highlighted in yellow.
03:47
This is because the date actually happened before.
03:50
Before the last card.
03:51
This is just a quick warning to let you know.
03:54
Maybe you should look at it.
03:55
Because generally sofs, are in chronological order, but not always.
04:00
In this case it looks correct.
04:01
You can continue down This is one I would definitely check.
04:05
The parser assumes that every event happens over one line.
04:09
And in this case it took two lines for this event.
04:13
I always like to check those to make sure it picked up both the event first line and the time properly.
04:20
This one looks good.
04:21
Continue to look through and just double check.
04:24
In this case, it picked up an other.
04:26
This means that, it wasn't able to match Commence Crane's inspection with anything in the Voyager dictionary.
04:36
I would potentially check this one as well.
04:41
We only have inspect holds and inspect cargo.
04:44
So in this case other is probably correct.
04:47
If I want to add the comment, I can here.
04:56
Now I know what it says.
04:57
At this one it was able to get the documents completed time even though it was handwritten.
05:05
The ones after this I do want to remove because.
05:08
Because it actually doesn't have a time.
05:11
It made the assumption to hold the time from the last event, but that's not necessarily correct.
05:17
So I'm going to unclick these to remove them from my validated SOF events.
05:24
In the event that the parser picked up a timestamp event, but you really needed a duration, you can switch them.
05:33
By adding the duration event within the event card, it will pick up the time that was already connected.
05:40
And if there are two times on the line, it will pick up both times.
05:44
And all you'll need to do is add, the duration event name here.
05:49
Duration events have both a category and an event.
05:52
So this one would potentially be process and something about a survey surveying draft instead of this was draft survey complete?
06:00
If it was instead the whole start and end of the draft survey, it would be a duration stamp like this.
06:07
The times are red because a duration event by definition has to be greater than zero minutes and these have the same time.
06:15
So if I go back to the SOF and I see okay, the commence of the draft survey started the event before at 9 and it ended at 10.
06:23
I can update this time to be 9 o' clock and then I can remove my original timestamp event by deleting it here.
06:30
I can also now remove this one since it's repetitive, either by deleting it or simply hiding the card.
06:37
Now everything looks good to go and I'm ready to calculate my late time.
Comments