standoff enrichment: suttaplex about suttacentral HOT 3 OPEN

I have crafted another mock-up based on your style here Bhante, based on all data that could be incorporated at present:

If this breaks any design principles would be good to know, but some notes on these choices are:

• I've placed only the speaker with the most words and location (actually it's initial location) since these are likely the most relevant to the reader. I could easily write something up that drops the pin correctly inside the thumbnail, it's not really useful at that size but is pretty! Another option would be to place these two buttons exactly where you put the initial mock-up.
• I've used "catalogues" to describe what these data to be displayed are, since it matches the dictionary definition quite well of what a catalogue is, even though common usage is more like an index between texts rather than inside texts. Another option is "indexes" . Another way of thinking about it is features common across texts in an enumerated form; a single word that encapsulates that eludes me.
• Some of these might be better as a single-line display, if only to fit more on the page. The whole list of lists and speakers for DN1 actually is gigantic, so it might be worth populating any web mock-up with the real data for DN1 since DN1 or DN16 would be the upper limit of how much to display.

This would go some way to please those asking the indexes be "more prominent" https://discourse.suttacentral.net/t/please-make-the-indexes-more-prominent/26415/11

From a technical point of view, these "catalogues" might be a bit heavy to load, so I would suggest it be like a click-to-load display if this whole choice is decided to be congruent. It might even be better to have each catalogue type nested in the same way as other suttaplex data.

My GUI skills are quite rusty, I thought I might be given a branch on bilara-data that'd be used to discuss how the data might look and integration with suttaplex API! I bet that breaks bilara. If this mock-up is promising, maybe the initial location and main speaker should placed with blurbs jsons. Also a script to get the current SC indexes entries in the same format as the other data might be a next step.

from suttacentral.

Bhante, I'm getting the following error when I try to view your branch:

from suttacentral.

I don't know if this is still being considered, but I'm not sure exactly how this enrichment will be helpful to the user. I'm trying to come up with scenarios but am not having much luck.

For example, does it really help me when viewing a suttaplex card to know where the sutta takes place? Are people that in touch with places that they would open a sutta or not based on where it happened? And if I want to see all the suttas that happened in Kusinara, for example, I would just do a search for kusinara. With locations we have the overwhelming majority taking place in Savatthi with Rajagaha as a distant second. Then there is a long tail with everything else.

I'm seeing even less use for the speaker. In the Pali suttas, the vast majority of suttas are spoken by the Buddha. Sariputta and Ananda come in a distant second and third. After that there is a long tail of people that could easily be found simply by searching the names.

Seeing a list of topics on the suttaplex cards could indeed be helpful for the user to decide if they want to read a sutta or not. But my own experiencing creating an index has shown me that pinning down a sutta as to the topic can be much more difficult than it seems at first glance. A quality and useful index is very subjective. If we are going to be showing the topics included in each sutta, then the data becomes less effective as a total index. Unless in addition to tagging with topics we were also to rate the overall importance of that sutta for this topic.

I'm not opposed to the concept, but I'd love to see some user stories. Otherwise it feels like a solution in search of a problem.

Speaking of search, would there be some way that this standoff data could be tied into search?

from suttacentral.