So we (finally) updated our Newforma server & clients last night - woohoo!
And w/ the re-index some ungodly-long filepaths were found, so many that my normal bounce-on of the auto-email alert would have been pointless... but seizing the opportunity to settle a curiosity, I set on little Dynamo study.
You see, whilst Newforma might auto generate/send a .msg in a html-like format:
HEADER
Project: JobNumber - JobName
Folder: FolderName
Files:
* FileName (list)
FOOTER
it/they don't offer up the same in a useful (to me) .csv format. No bother, save the .msg as a .txt then pick it apart with Dynamo then re-write it... easy, no?
Sure, so, I trim out the header & footers, then start using string-splits... and I end up with a structured list following the form:
>Project
>>Folder
>>>File
So far so good. But then I hit a stumbling block, and suspect I went the wrong way "cleaning" the list(s) - because instead of getting a transposable list structure I can readily export to Excel, my grouping of files-under-folders-under-project (which isn't how the Newforma auto-report comes at all, unhelpfully) just doesn't want to play nice. 
_____________

I know I've got to add the column headers as first items at some point, which may potentially require I use list cycles, but for the life of me I'm stuck at making that list-structure make sense for the excel write node. 
Attached is my fugly (annotated) dyn & sample .txt file (that handles all the conditions that can/do occur in the Newforma report original .msg) and I'm fairly certain there are far cleaner, quicker and surer ways of handling this that one or more of you might see instantaneously. Would be most appreciative if you'd take a look!