That’s unfortunate, becuase that’s where the files need to be to be visible from the web via DNS (if you want to see those files by going in a browser to your domain). SOmehow, they managed to find their way to the “mycontent” directory (which is good, so they can be seen).
Which is “OK”, I suppose, if that’s really where you want them to be - they won’t be visible from the web if they are there - see my comment above.
How your "scripts’ might be affecting any/all of this are an unknown to me, as I don’t know what you are running. You will not be able to delete the dataglob folder, as you don’t own it (root does), but you can , and probably should delete any references to it in any paths you insert into your scripts (it is not needed by the script(s)). If a script “display” that as part of a path that you did not enter yourself, that is “ok”, because the dataglob will show up in some environment/system variables. Did you read the wiki and forum posts about "dataglobs); all this is explained there.
for the purposes of the operation of your site, that’s exactly what you have. The dataglob directory simply symlinks to /home/account.
The two issues you are having are not related. Your “content” needs to be at least a directory level beneath /home/myaccount (or /home/.dataglob/myaccount - which, for you purposes, should be considered to be the same directory) to be visible form the web.
I suspect your Dreamhweaver / ftp settings need tweaking - content for display needs to go below the /home/myaccount/ level under the default Dreamhost setup. I suppose you could have re-assigned the directory for your domain to be /home/myaccount, but that would be very foolish from a security standpoint.