BUG: Definition section settings of the BWS

1. Create a BWS on the word "light"

2. Expand the Definition section and note the contents.

3. Under settings in the header line, switch to a collection unlikely to contain definitions e.g. a collection of your journals. Note it returns "no results".

4. Under settings switch to "All Resources" - note there is no "reset to default" option. Your results will return to your original contents.

Bugs/expectations:

an explicit reset to default rather than expecting the user to know "All Resources" is the default (assuming that is the intended behavior)
a screening of collection names to show only potentially valid collections i.e. they contain one or more resources of a resource type that could be used in the Definitions section

Note: in playing with the options, I did create Definitions sections that included all resources (literally). Unfortunately, I do not know the steps to recreate them so the bug is unreported.

Find more posts tagged with

Comments

Tonya J Ross

an explicit reset to default rather than expecting the user to know "All Resources" is the default (assuming that is the intended behavior)

This seems to fit with precedents set elsewhere in the app, such as the resource dropdowns in the search panel or in the visual filters panel.

a screening of collection names to show only potentially valid collections i.e. they contain one or more resources of a resource type that could be used in the Definitions section

I can make a case for that suggestion.

MJ. Smith

https://community.logos.com/discussion/comment/419450#Comment_419450

This seems to fit with precedents set elsewhere in the app

But is the default to All Resources itself a bug? It was treated as a bug elsewhere in the beta testing.

Tonya J Ross

https://community.logos.com/discussion/comment/419456#Comment_419456

I'm not sure I understand what you mean. Are you saying that the Definition section should use something other than All Resources as its default behavior? Or that the label 'All Resources' is the issue? (In which case, I would defer back to the precedent I mentioned previously.) Or perhaps I am misunderstanding you entirely...

MJ. Smith

https://community.logos.com/discussion/comment/421929#Comment_421929

In the beta the issue had come up, the thinking being that by default definitions ought to include definitions rather than everything that used the word as a head(?) word. I'm not sure what Logos' intention is ... or the degree to which it matches what the average user would expect for definitions.

Tonya J Ross

https://community.logos.com/discussion/comment/422341#Comment_422341

I see. That's a good question. I'm not sure what the expectation for that section should be. I will see if I can get that point clarified.