NavList:

Collaborative writing can be contentious, particularly so if consensus on the technical matters is not achieved.

Moreover, I adjusted and tweaked the Transcript for what seemed like an infinite number of times, as one suggestion after another came from various NavList'rs over the years.  Some good, some fantastic and some....well, not so good to be kind.

Collaboration indeed!  Without NavList, this paper would never have been even started, let alone finished.  Sure, I found the logbook on my own after looking at tens of thousands of Google results.  Most just junk, but then this pearl popped out.  But without George Huxtable's initial "A hah!" moment, the Transcript would have gone nowhere.  So NavList was instrumental in starting the paper. 

The Transcript went through several revisions but eventually George and I decided to write a paper.  That fell short, as Cape Belsham bedeviled us.  Henry Halboth was extremely helpful in discussion, but again, consensus eluded the team.

Finally, where but NavList could two such excellent colleagues as Lars and Robin be found to push forward.  Several more revisions of the Transcript occurred, but offline.  They never made it onto NavList as we felt sure of a paper.  Consensus on Time, Cape Belsham and Longitude was truly the most difficult to achieve.  That is fundamentally due to Frank Worsley's uncertainty.  We had to untangle his guesses!!  No mean feat that.

So NavList played an integral role in the investigation, throughout the entire life of the project.  Much like Andrés, I find NavList to be a fantastic resource.  For this project, no NavList would mean no Paper.

If the reader manages to get all the way through to the acknowledgments, NavList is specifically credited, along with a few select individuals.  As this paper will be referenced for a very long time to come by other scholars, authors and the public, NavList will also be noticed.  And that is a good thing, as NavList deserves the attention.

Brad