-
Notifications
You must be signed in to change notification settings - Fork 2
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
Revise document title for joins #493
Comments
@rlskoeser @richmanrachel @mrustow I think this might make sense for two – I don't quite agree that it's easier on the eyes, but having more specific examples and context would be helpful to see the issue – reading this, my perception is that a sweet spot for the 3+ shelfmarks is if they appeared as a subtitle right below the doc title in the search results – there really shouldn't be two lines of document title. Can you say more about "will help scholars keep track of this most crucial data point."? Are you saying this because it's not appearing on the search results? If so, then having them appear right below the title might make them more readable than as the document title |
Originally posted by @mrustow in #532 (comment) |
Originally posted by @gissoo in #532 (comment) |
Probably related to #154 as well. |
Actually these might be two separate issues—the one referenced in the original description seems to be about the document detail page, and the rest is about the way a document title will appear in search results (e.g. the + indicator for joins, the above screenshot, etc). In a sense the two questions are, with special consideration for large joins with many shelfmarks:
|
@blms - thank you for redirecting the conversation here. I agree that the issue is about the titles and should be discussed here.
@mrustow - what were your comments regarding changing the font type to include all elements of the join in the title, and/or implementing a new design where the shelfmark stays stable on the side as you scroll? |
|
Did we have a design already for that, or is this something @gissoo would need to come up with? And should this be MVP, or do we want to settle on something simpler for MVP like just displaying the full set of shelfmarks in the same font? This is what PGPID 5626 looks like now, so likely we'll want to adjust it somehow before MVP:
OK—did we decide this should be post-MVP? And does @gissoo agree with the proposed solutions (listing all shelfmarks in search results, separated by plus sign)? |
We are actually already displaying all the shelfmarks in the search results — which I guess is not the design. I noticed at some point the discrepancy between search and document detail but forgot to follow up. As a minimum first step, @blms can we wrap individual shelfmarks in a tag and add a |
@blms - I think the current design is okay for MVP. While it bothers me, I don't think it's worth designing something new and holding up progress. |
@blms, since we have changed our minds about this a few times no design work was taken into account for it. Note: I also agree with Rachel about the second option regarding Marina's comment – the plus sign is more clear. |
@gissoo Sounds good, thank you for weighing in! @rlskoeser Should we remove this issue from MVP and move the revised title for the doc detail view to #547? (I know that was what this issue was originally about, but the discussion here seems more useful post-MVP) |
@blms that sounds like a good solution to me! |
@rlskoeser I think what we have (full display of all shelfmarks in joins in search results, and document detail page) is exactly what Marina wants. Closing! |
@rlskoeser and @gissoo - Marina and I just met and we agree that we need to have the full set of shelfmarks in the title (especially if the join is only 2, we might be flexible about 3+).
Although I initially thought it would be repetitive to have the shelfmark in the title and listed again below, Marina has convinced me that this repetition is productive as it's "easier on the eyes" and will help scholars keep track of this most crucial data point.
Originally posted by @richmanrachel in #460 (comment)
The text was updated successfully, but these errors were encountered: