Chris Beer
Chris Beer
Is there a real-world use case for a single exhibit to show every indexed item? I know there's one the single-exhibit case (using the application-wide`Spotlight::Engine.config.filter_resources_by_exhibit = false`), but I'm not...
It looks like bibtex requires a year field for most types of citations (not allowed for manuals, optional for booklet, misc, and unpublished works). There's also a `month` and `day`...
Here's some odd differences: Different years: ``` 3876636 OLD: Hill, R. (1997). On Beulah Height. HarperCollins. NEW: Hill, R. (1998). On Beulah Height. HarperCollins. 317712 OLD: Vandier, J. (1952). Manuel...
Can you rebase this? 😬
Isn't this a PURL problem? There's logic here to handle the catalog ids: https://github.com/sul-dlss/purl/blob/04df4215f02e6731a38aeb6ef785d32dfc03aacf/app/models/public_xml.rb#L20 but that's not used for collection ids: https://github.com/sul-dlss/purl/blob/main/app/models/public_xml.rb#L30
Is there no hope doing this upstream/when we're initially constructing the text?
Spotlight is a good example where its use of document presenters and components doesn't neatly align with Blacklight's limited notion of search results and single document pages, and where `document_presenter_class`...
Yes, spotlight, blacklight-gallery and who-knows-what-else could all provide their own `document_presenter` implementations to just get the document presenter instance they actually want. It seems like an anti-pattern to force each...
Unlike #3333, I think this one is ok, right?
Before: After: