Bug #6224

inconsistencies with subjects and places browse

Added by Tim Hutchinson over 8 years ago. Updated over 8 years ago.

Status:InvalidStart date:01/17/2014
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Taxonomy / Term
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

I'm not sure if this is still in progress (I hadn't seen this functionality before), but for what it's worth, for both subjects and places:
  • on the main browse page, only the treeview is shown; the treeview/list/search toggle is not available
  • after you select a term, BOTH the treeview and list appear. In the header, you can click on list and then treeview to get just the list or just the treeview
  • browsing through the list (either with just the list or both list and treeview), after a term is selected, the list jumps back to the first page (with the treeview, the position in the list is retained after selecting a term)

History

#1 Updated by Dan Gillean over 8 years ago

  • Category set to Taxonomy / Term

Hi Tim,

This is a sponsored redesign we are just finalizing.

The Treeview/List/Search tabs don't appear on the landing page because they are redundant there - the main body of the page is the list (and can be sorted either alphabetically, or by most recent), and there is a large search bar at the top of the page.

The idea was that the treeview is both navigational and contextual, meaning yes, it will show you where you are when a term is selected - while the list is simply an A-Z opportunity to browse all terms, regardless of hierarchies, since the treeview can make it hard to see nested terms if you are not familiar with its operation. It can be browsed in the list tab without changing the position of the treeview, and if a user flips back to the treeview tab to browse there, the list position is maintained until the user selects a new record.

I hadn't considered making the list appear in the place where the record currently is, as it was meant to emulate the taxonomy's landing page list (in alphabetical sort) - but it's an interesting idea. At this point, though, I think we have gotten client acceptance on the way it is, and so revisions may have to wait to post-2.1.

Of course, I intend to add documentation for these new features before it is released (likely in April), which I hope will clarify the functionality - but the idea was to make these 2 taxonomies more publicly visible, since the term descriptions were previously hidden and we have some users who like to build detailed hierarchical place taxonomies with the Google static maps, etc.

I'm considering marking this issue invalid, but I wanted to leave it open and unscheduled for a bit to continue this discussion. Any valuable revisions that come out of it could be assigned to a future release for consideration.

#2 Updated by Tim Hutchinson over 8 years ago

Hi Dan, thanks for the detailed background. So I wonder if the only buggy behaviour is having both the list and treeview appear at once? But feel free to mark it invalid, since I seem to have discovered this mid-stream, and it turns out points 1 and 3 are feature requests :)

#3 Updated by Dan Gillean over 8 years ago

Tim, do you mean both the treeview and the list are available on the term page in their respective tabs (this is the expected behavior)? Or do you mean they somehow are both visible at once when you first land on the term page?

In our test environment, the default when you land on the term page is to have the treeview visible - you need to flip the tabs to see the list or the search. I haven't seen the behaviour you're describing, but i'll want to make sure there's not a problem in the code before we make it publicly available.

#4 Updated by Tim Hutchinson over 8 years ago

It turns out our themes hadn't been rebuilt with the latest update. They are now, so I'm not getting that behaviour anymore.

So the entire report is now invalid :)

#5 Updated by Dan Gillean over 8 years ago

  • Status changed from New to Invalid
  • Target version set to Release 2.1.0

Ok, good to know! Thanks Tim.

Also available in: Atom PDF