The way I do it is as follows, I have approx 1300 sidescan logs, many of which have marine archaeology appearing.
I save each track as a date and place, for example the 3rd run of the day in kilbeg would be called 3March2015Kilbeg3. Waypoints are not exclusive to a particular logfile, the structure will appear on many sidescan swaths, so I use a graphical database to display the entire set of tracks (not swaths) in an area, and can then pick out tracks which will intersect the relevant waypoint. Waypoints are generally the result of an aggregation of points. Similarly, if I'm looking for an area to survey I can base the survey on previous tracks, and cover an area at a new angle over new ground.
I use RM to analyze the swath and to grab georeferenced images of the section I'm interested in, these then go into the dataset for each waypoint. Each waypoint has its own folder which will contain all of the information relevant to it. I can use these images on survey charts to position myself exactly over whatever I'm looking at / filming or to run along it on the course I decide will give me optimum angles for sequences.
The interconnection of data can be quite tricky, particularly once you build up datasets with a wide variety of formats (sl2,sl3, gpx, jpg, mp4, drd, doc) etc all relating to one specific object.