Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for corrected assertions in docmap #92

Merged
merged 11 commits into from
Jun 20, 2024

Conversation

nlisgo
Copy link
Member

@nlisgo nlisgo commented Jun 19, 2024

Implemented parsing and generation of corrected assertions in docmap. Tests and fixtures were updated to verify this new feature. An additional correctedDate field was added to preprints and reviewed preprints. A new corrected status was also added to AssertionStatus.

Implemented parsing and generation of corrected assertions in docmap.
Tests and fixtures were updated to verify this new feature. An
additional correctedDate field was added to preprints and reviewed
preprints. A new corrected status was also added to AssertionStatus.
Improve readability by splitting imports from 'docmap-generators' into separate lines.
scottaubrey
scottaubrey previously approved these changes Jun 20, 2024
Copy link
Member

@scottaubrey scottaubrey left a comment

Choose a reason for hiding this comment

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

Looks OK to me. Is the intention to generate entries in client for each corrected date? It looks like we won't be able to link a specific URL from the output but I assume this is OK? Any, good first pass at understanding it, thanks!

src/test-fixtures/docmap-parser.ts Outdated Show resolved Hide resolved
…preprints-issues#1120]

Update the correction structure in the docmap-parser and its test cases. Now, instead of an array of dates, the 'corrections' field holds an array of objects with a 'correctedDate' field.
nlisgo and others added 8 commits June 20, 2024 12:20
…ues#1120]

Update a comment in the docmap-parser to accurately reflect the function's purpose. It now states 'Update preprint with corrections'.
…prints-issues#1120]

Update test and fixture in docmap parser to check for corrections on a
published version of record. Test and fixture names have been changed
to reflect this update.
…enhanced-preprints-issues#1120]

In the docmap-parser and its corresponding test file, a new 'content' field
has been added to the 'Correction' type. This field is populated with the
URLs of the corrected versions of records.
…reprints-issues#1120]

Refactored the way content is filtered in the docmap-parser. Previous
method used a filter then map combination, but it has been replaced
with a more efficient reduce method. This enhancement is specifically
for the parsing of 'web-page' type content with valid URLs.
…d-preprints-issues#1120]

This commit introduces a new function, getPublishedOutput, in docmap-parser.
This function checks the length of preprintOutputs and versionOfRecordOutputs
and returns the first item if there's one, otherwise it returns false. The
existing function getPublishedVersionOfRecord has been updated to use the newly
implemented getPublishedOutput function.
@nlisgo nlisgo marked this pull request as ready for review June 20, 2024 14:48
@nlisgo nlisgo merged commit b78e2a0 into main Jun 20, 2024
2 checks passed
@nlisgo nlisgo deleted the version-of-record-corrected branch June 20, 2024 14:53
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.

3 participants