[E] Allow parsing issue-only journal sources#198
Merged
scryptmouse merged 3 commits intomainfrom Jan 29, 2026
Merged
Conversation
When a hierarchical entity is getting mapped from harvesting, e.g. a journal article, it's possible for the volume to be present but not the issue. We need to exclude those structs in that case.
* Allow for parsing cases where there is an issue, but no volume, and
add an example template for such a use case
* Add `ifinteger` liquid tag; simplify making new `if#{logic}` liquid
tags and standardize testing
* Improve testing of parsing journal sources for various outcomes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.