-
Notifications
You must be signed in to change notification settings - Fork 13
TST: Fix expected bib results #83
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
Conversation
bd16269 to
3136c6a
Compare
3136c6a to
384ba60
Compare
Codecov Report
@@ Coverage Diff @@
## master #83 +/- ##
==========================================
+ Coverage 87.55% 89.77% +2.22%
==========================================
Files 5 5
Lines 217 225 +8
==========================================
+ Hits 190 202 +12
+ Misses 27 23 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
actually before releasing, I'd like to ensure this was the intended behavior (cc @oesteban) |
| \tauthor = {Vladimir Fonov and Alan C. Evans and Kelly Botteron and C. Robert \ | ||
| Almli and Robert C. McKinstry and D. Louis Collins}, | ||
| \ttitle = {Unbiased average age-appropriate atlases for pediatric studies}, | ||
| \tjournal = {{NeuroImage}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little nervous that doi.org are changing their responses. They used to generate Lastname_year identifiers, and now these seem to be only year.
We probably can have a regexp to override whatever ID they generate to the template name.
However, I'm less happy with the references not having a journal entry. Before we go ahead we need to understand why these are changing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, looking more into it, it does seem like a bug. Looks like crossref should have a fix out today, dunno if doi.org will follow suit but we could always switch over to crossref since they have an API as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doi.org just redirects POST requests over to crossref
No description provided.