Feature #11955

Add hierarchical (treeview-based) browse page to explore all holdings in AtoM

Added by Dan Gillean over 1 year ago. Updated about 1 hour ago.

Status:VerifiedStart date:01/30/2018
Priority:MediumDue date:03/02/2018
Assignee:Corinne Rogers% Done:

0%

Category:Search / BrowseEstimated time:112.00 hours
Target version:Release 2.5.0
Google Code Legacy ID: Tested version:2.5
Sponsored:Yes Requires documentation:Yes

Description

This new feature will provide users with an additional way of browsing records held in AtoM - via a full-page version of the full-width treeview that contains all descriptions.

This new browsing mode will be disabled by default in new installations. An administrative setting will be available for users to toggle on the display of Hierarchical browse page. When enabled, a new link will appear on the archival description search/browse page, labelled "Browse by hierarchy." Clicking it will take users to a full-page, full-width treeview containing all top-level descriptions in AtoM.

As with the current description treeview, each description in the hierarchical browse page that has children will display an “expand/collapse” icon which can be clicked to display all the children of that description. Any child descriptions that in turn have children, will also be expandable.

The Browse by hierarchy treeview will have the same functionality as the standard treeview, except:

  • All description titles from any level in the catalogue database will be shown,
  • The detailed archival description metadata will not be displayed,
  • The treeview will use the entire display area of the page, so the “gripper” to expand and shrink the vertical size of the treeview pane will not be necessary,
  • When a user clicks a description title in the Hierarchy browse page,they will be redirected to the related archival description view page with the standard treeview. The user should then be able to return to the hierarchy browse page, in the state they left the page (showing the clicked description in the tree, and with all the parent nodes open). This is especially important in case the user clicks the wrong description.

No filters or facets will be available on the Hierarchy browse page. On the archival description view page, a link back to the Hierarchy browse page will be provided when the setting is enabled.

additions.csv Magnifier - will add f16-f30 to the collection, using parentID (4.41 KB) Dan Gillean, 04/30/2018 07:25 AM

isad_0000000001.csv Magnifier - Import first, will create a collection with file-level children, f1 to f15 (5.02 KB) Dan Gillean, 04/30/2018 07:25 AM


Related issues

Related to Access to Memory (AtoM) - Bug #12179: Fix sort order in treeview Verified 04/30/2018

History

#2 Updated by Mike Cantelon over 1 year ago

  • Status changed from New to In progress

#3 Updated by Mike Cantelon about 1 year ago

  • Status changed from In progress to Feedback

Hi Nick. Aside from backporting this as-is to the client, can I create a pull request for this for qa/2.5.x?

#4 Updated by Mike Cantelon about 1 year ago

  • Assignee changed from Mike Cantelon to Nick Wilkinson

#5 Updated by Nick Wilkinson about 1 year ago

  • Assignee changed from Nick Wilkinson to Mike Cantelon

Yes Mike, please go ahead.

#6 Updated by Mike Cantelon about 1 year ago

  • Status changed from Feedback to QA/Review
  • Assignee changed from Mike Cantelon to Dan Gillean

I forgot to make a PR and just merged it... luckily I think the code's pretty clean (other than a comment TODO that I'll remove in a subsequent PR). Anyways, it's available for QA in qa/2.5.x.

#7 Updated by José Raddaoui Marín about 1 year ago

Oh, that's bad ;(

I could have added some feedback about the move job and the importance of the sort order in the full-width treeview ... I think Dan will follow-up with some findings about this.

#8 Updated by Dan Gillean about 1 year ago

Hi Mike,

Please see the following post in the user forum - Radda thinks that the behavior I saw there originates with this development:

I'll add the 2 test CSVs here as well. I first imported isad-000001, then the additions csv. Let me know if you have any questions.

#9 Updated by Dan Gillean about 1 year ago

One thing I've realized that has resulted from this:

When I was first testing the hierarchy browser, the sorting seemed completely aribitrary and we talked about sort options, in comments 12-14 on the related client ticket. You implemented a new sort order, changing it from sorting by lft - but I didn't realize this would affect the full-width treeview everywhere in AtoM!

We're seeing the consequences of that now with the behavior described on the forum post above. Mike, I'm wondering if there might be any way that the hierarchy browser can keep the sort you gave it, but elsewhere in description view pages, it still sorts by lft, so it is consistent with the manual sort option on the sidebar treeview?

#10 Updated by Mike Cantelon about 1 year ago

I didn't think changing the sort globally would affect anything, but seems it has so I'll add some logic so it only sorts that way on the hierarchal browse page.

#11 Updated by Mike Cantelon about 1 year ago

  • Related to Bug #12179: Fix sort order in treeview added

#12 Updated by Mike Cantelon about 1 year ago

I've updated #12179 with a PR to fix this issue.

#13 Updated by Dan Gillean about 1 year ago

  • Status changed from Feedback to Verified
  • Assignee deleted (Mike Cantelon)

Looks good - the sort issues are resolved here, and maintained elsewhere. Drag and drop is disabled in Hierarchy browser (as it should be).

Thanks!

#14 Updated by Corinne Rogers about 1 month ago

  • Assignee set to Corinne Rogers

#15 Updated by Dan Gillean about 1 hour ago

Some docs added to 2.5 in: https://github.com/artefactual/atom-docs/pull/77

See: https://www.accesstomemory.org/docs/latest/user-manual/access-content/browse/#desc-browse-archival-descriptions

However, the setting (found in Admin > Setting > Treeview) to enable and disable the feature has not yet been covered.

Also available in: Atom PDF