Display 'Year Registered' facet on all doi list pages#950
Display 'Year Registered' facet on all doi list pages#950
Conversation
📝 WalkthroughWalkthroughThe permission guard Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This is working as expected. It is already in production at https://doi.test.datacite.org/providers/dc/dois. All I did was make it available on other pages. @codycooperross had questions about the data accuracy. I looked at that and determined that it is a lupo problem. I filed a lupo issue at: datacite/lupo#1497. This should be considered work separate from this PR. There was another problem noted by @KellyStathis at https://bracco-6k5h0fyjm-datacite.vercel.app/repositories/datacite.kelly/dois. There is no 'year registered' facet on that page even though there should be. I looked into that and found that it is because there is no data returned from lupo for that facet. It is working as expected on other pages. It could either be the problem mentioned above, or perhaps a data integrity problem in staging. Again, this should be considered work separate from this PR. |
Purpose
closes: https://github.com/datacite/product-backlog/issues/635
preview: https://bracco-6k5h0fyjm-datacite.vercel.app/
This might be on hold due to the accuracy of the facet data as returned by lupo. I created an issue in lupo for that: datacite/lupo#1497.
Approach
Remove the access check on displaying that facet.
Open Questions and Pre-Merge TODOs
Learning
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Reviewer, please remember our guidelines:
Summary by CodeRabbit