Parsing SOF Example 🔍

In this video, I will go over an example of parsing an sof.

The first thing I do is click on the first magnifying glass to see where my SOF events start.

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.

Next, I will scroll through to see which pages I want to be analyzing.

In this case, I've started on page three as seen on the top left here, and my SOF is only that page.

If I keep scrolling, I see that there are a couple of delays shown on the next page that have also been highlighted.

And the parser's done a good job of ignoring all of the other pages.

For the purpose of this example, I want to filter only for page three.

To do that, I can use the events filter on the top right of the screen.

Here I can either use a dropdown or type in a custom page list and we'll focus on page three and apply.

Now if I scroll down, those events that were highlighted have been removed.

I can hover over this highlighted line to return back to the first event card.

Now in this example, I will first look if there are any errors.

In this case, there aren't any.

The parser did a very good job.

I can remove this date to force an error to show up.

It will be highlighted in red.

Now if I toggle, this will remain, but it will hide everything else so I can focus on it.

To update a time or date, I can either use the calendar module or I can type in in the format shown here.

This one happened on 23rd of July, 2025 at 1758.

As soon as I entered that in, the error disappeared and so my card disappeared.

I can untoggle the show errors to show all of my cards again.

If cards are parsed out of chronological order, you will see a yellow highlight.

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.

Let's say this was actually 2024, but it parsed all 2025.

You can go to this bulk update event button and pick the pages to apply it to.

In this case it's all of page uh3, but if you have specific lines you can add them here.

I'll just do line 1 through 20 for this example here I can pick a date in 2024 and I only want to update the year.

If you want a Bulk update tagged.

You can do that here as well.

Now you can see all of my dates for those first 20 lines have updated.

If you're not sure what line a card is on, you can see it here at the top left of the card.

After line 20, we should see it return to 2020.

Now it's time to go through and confirm all of the events and times were parsed correctly.

Usually I'll just scroll through and it automatically will highlight the line for me that I'm supposed to be looking at.

Obviously now my dates are wrong since I just changed them.

But you can see it's picking up most of the events.

Even this one, it picked up both vessel arrived and nor tendered.

On this one you can see that the date is highlighted in yellow.

This is because the date actually happened before.

Before the last card.

This is just a quick warning to let you know.

Maybe you should look at it.

Because generally sofs, are in chronological order, but not always.

In this case it looks correct.

You can continue down This is one I would definitely check.

The parser assumes that every event happens over one line.

And in this case it took two lines for this event.

I always like to check those to make sure it picked up both the event first line and the time properly.

This one looks good.

Continue to look through and just double check.

In this case, it picked up an other.

This means that, it wasn't able to match Commence Crane's inspection with anything in the Voyager dictionary.

I would potentially check this one as well.

We only have inspect holds and inspect cargo.

So in this case other is probably correct.

If I want to add the comment, I can here.

Now I know what it says.

At this one it was able to get the documents completed time even though it was handwritten.

The ones after this I do want to remove because.

Because it actually doesn't have a time.

It made the assumption to hold the time from the last event, but that's not necessarily correct.

So I'm going to unclick these to remove them from my validated SOF events.

In the event that the parser picked up a timestamp event, but you really needed a duration, you can switch them.

By adding the duration event within the event card, it will pick up the time that was already connected.

And if there are two times on the line, it will pick up both times.

And all you'll need to do is add, the duration event name here.

Duration events have both a category and an event.

So this one would potentially be process and something about a survey surveying draft instead of this was draft survey complete?

If it was instead the whole start and end of the draft survey, it would be a duration stamp like this.

The times are red because a duration event by definition has to be greater than zero minutes and these have the same time.

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.

I can update this time to be 9 o' clock and then I can remove my original timestamp event by deleting it here.

I can also now remove this one since it's repetitive, either by deleting it or simply hiding the card.

Now everything looks good to go and I'm ready to calculate my late time.