Skip to content

CDM v5.4 documentation migration to quarto and bugfixes - #800

Open
clairblacketer wants to merge 29 commits into
mainfrom
develop
Open

CDM v5.4 documentation migration to quarto and bugfixes#800
clairblacketer wants to merge 29 commits into
mainfrom
develop

Conversation

@clairblacketer

Copy link
Copy Markdown
Contributor

This is a bugfix release of CDM v5.4 prior to releasing CDM v5.5. It also includes the migration of documentation from rMarkdown to Quarto thanks to @MaximMoinat.

@MaximMoinat MaximMoinat left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Minor comment on further cleaning the field level csvs.

@@ -1,552 +1,552 @@
cdmTableName,cdmFieldName,isRequired,cdmDatatype,userGuidance,etlConventions,isPrimaryKey,isForeignKey,fkTableName,fkFieldName,fkDomain,fkClass,unique DQ identifiers

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The unique DQ identifiers column seems redundant as it is populated with NA for all rows. Can we remove this column?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I will remove

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I propose to remove the v6.0 documentation. It should not be used and having it here creates maintenance overhead and might confuse people.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have kept it because some folks in the community requested it. I did remove links to 6.0 from the website though so the only way to get to it is direct urls. Is that enough do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants