Skip to content
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

Optimize display of name variants #330

Open
ahankinson opened this issue Dec 18, 2024 · 3 comments
Open

Optimize display of name variants #330

ahankinson opened this issue Dec 18, 2024 · 3 comments

Comments

@ahankinson
Copy link
Contributor

ahankinson commented Dec 18, 2024

The name variants section in a Person record is very long and not terribly useful. Look at https://rism.online/people/55803

a. removing it altogether (good for search, but not necesarrily for display)
b. hiding it in some sort of spoiler tag?
c. display it in one long string with semicolon separators.

@BaMikusi
Copy link
Collaborator

Frankly, I tend to disagree -- to my mind the name variants are often the most intriguing part here. Needless to say: not when they simply represent a random set of orthographic nuances, but if there is a bit more system to the differences, this can prove an interesting read.

Which is to say that IMO removing this altogether cannot be an option -- also because there is nothing more annoying than searching for a concrete word and then not being able to locate it on the page found (the OPAC did this for diverse note fields and drove me crazy even before my comeing to RISM).

So, if you want to make the display a bit more focused (which of course makes sense also in this case), I would suggest (as in many similar situations) to show the first few lines and offer the user the option to enlarge by a click. (A long string would spare space but would make it rather difficult to skim the variants in search of the relevant differences, which is probably the typical approach for anyone actually looking at this list closely.)

Besides, it would surely be good to hear which solution @alexandermarxen might find the most appropriate, who of course knows this part of the data better than anyone.

@lpugin
Copy link

lpugin commented Dec 19, 2024

I looked at a few examples and I find it OK as it is. Maybe we would limit the list to 10 or 15, and then have a "show all" link?

@alexandermarxen
Copy link

A list with at least 5 (preferably 10-15) and a ‘show all’ link would be the best solution. The separation with a semicolon would be problematic in some cases, as it is sometimes unclear where a new name begins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants