Closes #377 blog post closing the gap in exposure response data

[jeffreyad]

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/date_with_short_tile" and the blog post file and any other artifacts have informative but succinct names.
• 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", "Python", "Community", "Conferences", "Submissions", "Technical", "DEI") 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 (@aaehmann, @ashley-tarasiewicz, @chrisprice-phuse) as reviewers in the PR.
• Pat yourself on the back for a job well done! Much love to your accomplishment!

[github-actions]

❌ Preview removed.

This PR has been closed and the preview website has been removed.

[jeffreyad]

I heard from people on CDISC working group that they are interested in moving forward with either a Knowledge Article or Examples Document potentially positioning ER datasets as a subclass of ADPPK. I added a blurb about this to the blog.

[bms63]

I heard from people on CDISC working group that they are interested in moving forward with either a Knowledge Article or Examples Document potentially positioning ER datasets as a subclass of ADPPK. I added a blurb about this to the blog.

Hey @jeffreyad do you want me to do a quick review and get this published.

Unsure if others have time right now for review?

[jeffreyad]

I heard from people on CDISC working group that they are interested in moving forward with either a Knowledge Article or Examples Document potentially positioning ER datasets as a subclass of ADPPK. I added a blurb about this to the blog.

Hey @jeffreyad do you want me to do a quick review and get this published.

Unsure if others have time right now for review?

@bms63 sure, thanks!

[bms63]

@copilot can you add cran-release to any of the failing links for admiral, e.g. https://pharmaverse.github.io/admiral/reference/ should be https://pharmaverse.github.io/admiral/cran-release/reference/

Can you also change the date of the post from date: "2026-04-17" to date: "2026-04-30"

[Copilot]

@copilot can you add cran-release to any of the failing links for admiral, e.g. https://pharmaverse.github.io/admiral/reference/ should be https://pharmaverse.github.io/admiral/cran-release/referenc...

Done in commit b35062b:

• Updated the post date from 2026-04-17 to 2026-04-30
• Added cran-release to all failing admiral links across 7 posts (study_day, p_k__examples, admiral_130_documentation_go, date_functions_and_imputation, derive_param_computed, admiral_1_0, 12_admiral_release)

[bms63]

@copilot for links like https://pharmaverse.github.io/admiral/reference/filter_exist.html can you also add cran-release to them, so this one should be https://pharmaverse.github.io/admiral/cran-release/reference/filter_exist.html

[Copilot]

@copilot for links like https://pharmaverse.github.io/admiral/reference/filter_exist.html can you also add cran-release to them, so this one should be https://pharmaverse.github.io/admiral/cran-rele...

Done in commit b75608d. Fixed all remaining admiral reference/ links (filter_exist, filter_not_exist, filter_extreme, filter_relative, filter_joined) in admiral_filter_functions.qmd, plus articles/, news/, and dev/articles/ links in admiral_11_is_here.qmd and top-five-packages.qmd.

[bms63]

@copilot can you add the remaining failing links to the .lycheeignore file, the ones failing with an error message

[Copilot]

@copilot can you add the remaining failing links to the .lycheeignore file, the ones failing with an error message

Done in commit 350d110. Added the three remaining failing URLs (403 errors) to .lycheeignore:

• https://join.slack.com/t/pharmaverse/shared_invite/*
• https://phuse.s3.eu-central-1.amazonaws.com/*

[bms63]

k fixed a bunch of bad links due to some of the admiral and slack updates.

teal also has one that i queried about in their slack but we can leave as is

@jeffreyad let's start the ER revolution!!

[jeffreyad]

k fixed a bunch of bad links due to some of the admiral and slack updates.

teal also has one that i queried about in their slack but we can leave as is

@jeffreyad let's start the ER revolution!!

@bms63 thanks for fixing all the links! That was a good use of copilot! Yes, I was wondering if we want to find a new join Slack link that's consistent with the new policy.