Closes #234 Blog Post: How I Rebuilt a Lost ECG Data Script in R

[vbshuliar]

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

• Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
• Ensure your new post folder is of the form "posts/zzz_DO_NOT_EDIT_<your post title>". This is so that the post date can be auto-updated upon the merge into main.
• Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
• Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Community", "Conferences", "Submissions", "Technical") for your blog post. If you cannot find anything that fits your blog post, propose a new tag to the maintainers! Note: if you use a tag not from this list, the "Check Post Tags" CICD pipeline will error. We occasionally tidy up all tags for consistency.
• Add a short description for your blog post in the description field at the top of the markdown document.
• Blog post is short, personalized, reproducible and readable
• Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
  This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
• Address all merge conflicts and resolve appropriately
• Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR.
• Pat yourself on the back for a job well done! Much love to your accomplishment!

[manciniedoardo]

@reviewers: I will work with @vbshuliar for a first review cycle and once that is complete please feel free to add your own comments as well.

[vbshuliar]

@manciniedoardo I've added a bit of explanation for some of the eg script code bits to the post. Also, locally I am not getting any spelling errors. They are only in the pipeline.

[manciniedoardo]

@vbshuliar thanks for the post! I left a tonne of comments but don't be scared, it has the makings of a super post so thanks for your time 😄 !

[vbshuliar]

@manciniedoardo ,
Please check out the new version of the post. I tried to take all the recommendations into account.

[manciniedoardo]

Great job! Left another round of comments

[vbshuliar]

@manciniedoardo ,
Please, check out the new version of the post.

[vbshuliar]

@manciniedoardo I took all your feedback into account and prepared a new version of the post. Please, check it.

[manciniedoardo]

@vbshuliar looks great! I did one final round of review, but I think it's ready for other reviewers too now @gigikenneth @kaz462

[vbshuliar]

@manciniedoardo Please, check the new version with all the recommendations implemented.

[manciniedoardo]

LGTM!

[StefanThoma]

Minor changes requested.

[StefanThoma]

LGTM, thanks for the quick updates!