Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-25690

www.lsst.io: Create category pages for document series

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: www_lsst_io
    • Labels:
      None

      Description

      For each document series, programatically create a pre-filtered listing of documents in that series.

      By default, sort by handle, but also allow sorting by revision date.

      This change will allow us to keep the default listing in the advanced search page empty (requested in  DM-24956).

        Attachments

          Issue Links

            Activity

            Hide
            jsick Jonathan Sick added a comment -
            • We're now generating category-specific pages for browsing individual document series, such as /sqr/ for SQR technotes, and so on. These category pages use the Algolia search interface, but unlike the advanced search page (/search/) they sort records. For example, documents are sorted by their handle in descending order.

            When the user starts typing a query term, though, we immediately switch the sorting to a relevance-based order because that provides the best search experience. This is implemented through a customized SortBy widget that connects to the SearchState widget. This AutoSortBy widget sets the default value of the underlying <select> element, so the user can still override the sorting and have that choice persist if the query text is deleted, for example.

            • Re-ordered the controls in the SearchSettingsCluster to make space for a refinement list in the future to extend from the "clear all refinements" control.
            • The advanced search page no longer shows any results if the user hasn't entered a query yet (using the new NonEmptyHits component). This is appropriate because the advanced search page always sorts by relevance, but relevance is only meaningful if there is a query.
            • Category pages are now linked from the homepage.
            • In the footer, we now prompt for feedback by linking to different venues (some internal, some accessible to the community).

            See https://github.com/lsst-sqre/www_lsst_io/pull/16 for screenshots

            Show
            jsick Jonathan Sick added a comment - We're now generating category-specific pages for browsing individual document series, such as /sqr/ for SQR technotes, and so on. These category pages use the Algolia search interface, but unlike the advanced search page ( /search/ ) they sort records. For example, documents are sorted by their handle in descending order. When the user starts typing a query term, though, we immediately switch the sorting to a relevance-based order because that provides the best search experience. This is implemented through a customized SortBy widget that connects to the SearchState widget. This AutoSortBy widget sets the default value of the underlying <select> element, so the user can still override the sorting and have that choice persist if the query text is deleted, for example. Re-ordered the controls in the SearchSettingsCluster to make space for a refinement list in the future to extend from the "clear all refinements" control. The advanced search page no longer shows any results if the user hasn't entered a query yet (using the new NonEmptyHits component). This is appropriate because the advanced search page always sorts by relevance, but relevance is only meaningful if there is a query. Category pages are now linked from the homepage. In the footer, we now prompt for feedback by linking to different venues (some internal, some accessible to the community). See https://github.com/lsst-sqre/www_lsst_io/pull/16  for screenshots

              People

              Assignee:
              jsick Jonathan Sick
              Reporter:
              jsick Jonathan Sick
              Watchers:
              Jonathan Sick
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.