Challenge #20: List Parsing

[afnfyz]

This was quite difficult.

Spoiler

I had all the values parsed out, finding the patterns that made each of them unique wasn't too hard but the logic of creating headers and record ids to group by totally skipped my mind so had to go and approach the problem differently. Learned a lot from this.
Still ended up with ~40 records short though. Must have been due to some error in the logic I used during parsing.

[shrestha_nitesh]

 

[iamBenSmith]

Spoiler

[AndrewDMerrill]

This was tough, and I definitely didn't find all the structures that would have helped me simplify my workflow.

Spoiler

[ds_tomalexsmith]

Spoiler

 

[Rob-Silk]

My solution below:

Spoiler

[caitlynmcintyre]

I was so confident about this but the random inconsitencies absolutely killed me. I have four records that don't match the example output as i extracted the trailing numbers into the Phone column.

I'm not familiar enough with US addressing to know if this is some sort of extra postal code but looked like phone numbers to me

Spoiler

[BrianJohnson]

I'm better at parsing thanks to the challenge

[Krzysiek]

MySolution

[Zhengyi]

This is a great challenge. It took me so much time to compare my output with the solution output because my workflow gave me several more records than the answer and then I have to find out the abnormal records and adjust my regex_match formular to correctly flag the abnormal records. Teach me to carefully investigate the output file in real work situation when there is no standard answer there.