nulib / digital-collections Goto Github PK

Description

Construct details row component and child components. See attached screenshot.

Done Looks Like

• Metadata is populated and correctly linked.
• More Details and Cite This Item buttons handle click event and take user to respective section on the page.
• Image permalink generated and copy to clipboard functionality is wired up (separate issue).
• Download options provided. (Maybe push this off until later).
• Social media links/components work.

Tasks

• Metadata is populated and correctly linked.
• More Details and Cite This Item buttons handle click event and take user to respective section on the page.
• Image permalink generated and copy to clipboard functionality is wired up (separate issue).
• Download options provided. (Maybe push this off until later).
• Social media links/components work.

Description

Need to wire up / re-use or re-purpose the forthcoming "faceting" component to work with the Collection Items view page.

Done Looks Like

• Collection items view page items can be filtered by faceting solution.

Tasks

• See how much of existing faceting component can be used for this view / data.
• Add 'About' section to faceting component.
• ...more to come.

Description

Create Collection Items component and child components.

Done Looks Like

• Collections can be clicked into, and display items from within the collection.
• Faceting, About, and Filter data are present on the page.
• A direct route is created for navigation within the app.

Tasks

• Wire up Solr Queries
• Implement faceting solution/component
• Create React Router route.
• ...more to come.

Description

The Search results page will have a facet component, which will filter search results views. This could spawn child issues as we move through it.

Done Looks Like

• Search results in the list are able to be filtered through the faceting UI in the left-hand side of the page (see screenshot).

Tasks

(These tasks are now irrelevant and should be replaced by Reactive Search components / Elastic Search queries)

• Create faceting component
• Figure out what terms, metadata, we want to facet by (new issue?)
• Create and wire up the new Solr queries
• Create nice UX flow for updated faceted results on search results page.

Description

We'll need a pagination solution for global search results, and potentially other places in Digital Collections site?

Done Looks Like

• Pagination is in place with reasonable default.

Tasks

• Look for existing React component solution. (Reactive Search?)
• Create and/or implement pagination container component.

Descriptions

Make these buttons scroll down to their respective tabs as in the mockups.

Done Looks Like

The buttons are clickable and go to either About or Cite tabs.

Description

Keep the global search bar closed on page load (or entering a new view) by default on every page except homepage.

Done Looks Like

• When entering a new route or page view, the global search bar is closed by default.

Tasks

• Hook into current jQuery or find what code is controlling the opening / closing of the search bar
• Fix so that it's closed by default.
• Fix so it opens on homepage.

Description

Initially needed for search results page, but also a site-wide need for a "loader" visual cue React component.

Done Looks Like

• Look for existing preferred NU Global Marketing loader.
• Decide on loader.
• Implement on Search Results page
• Implement across carousels?

child of https://github.com/nulib/next-generation-repository/issues/664

child of #23

attributes like genre and collection need to link to the search results for that related query. For example clicking 'shabby chic' should take the user to the search results of all genres with 'shabby chic'

Description

Import Universal Viewer and wire up into the page.

Done Looks Like

• Universal Viewer properly displays an item.

Tasks

• Install UV
• Knowledge spike to see how it works, passes in params.
• Ensure we have all proper data UV needs to work.
• Create some types of parsing feature to translate Solr data to what UV requires.
  ... more to come.

child of #23

Description

Clean up the UI on the Reactive Search results page to match rest of site, global marketing theme. See attached pic.

Done Looks Like

• All Reactive search components have a seamless look & feel with rest of application.

Tasks

• Sidebar text styles
• Search bar
• Individual facet items (under search bar).
• Handle long text descriptions under each display panel.
• Style pagination

Description

A lot depends upon the new search route using reactivesearch and the new indexer.

child of https://github.com/nulib/next-generation-repository/issues/574

Description

How should these faceted items be generated? Hard coded by certain terms, metadata, or should this all be dynamically pulled from whatever is in Solr?

Tasks

• Determine how we arrive at what facets get displayed.

depends on https://github.com/nulib/next-generation-repository/issues/640
depends on https://github.com/nulib/next-generation-repository/issues/639

Facet on the desired fields.

Description

Master issue for search related issues for Digital Collections front-end.

parent of #33
parent of #35
parent of #378 (nulib/next-generation-repository#378)
parent of #36
parent of #37
parent of #45
parent of #46
parent of #47
parent of #49
parent of #50
parent of #51
parent of #53
parent of #54
parent of #112
parent of #122
parent of #123

Description

Clean up the UI for Sign In / Sign Out link and dropdowns. See attached image.

Description

Create the search results page for site wide, global searches against Solr for Digital Collections

Done Looks Like

• Search submission searches active Solr data.
• Search results page displays results, which link to individual collections/works, however this flow will go.

Tasks

• Create a Search results route via React-router.
• Create Search results container component which handles network communication.
• Create Search results child components which display search results.

Description

Create the root component structure for Item Detail page. Create the route and route matching and link from home page carousel.

Done Looks Like

• Framework of Item Details page exists.

Tasks

• Set up initial container component structure with child components.
• Set up routing.

child of #23

Description

There are timing issues in DOM rendering with NU Global Marketing's collapse plugin. Should bypass their plugin and use a React community component.

Done Looks Like

• Collapsible components behave as expected and visually appear like the mockups.

Tasks

• Install a React collapsible component
• Port over the collapsible styles from NU Global Marketing into the component itself.

Description

UV embedded player is not reloading and displaying the updated item when route and item reload on Item Details page.

Done Looks Like

When clicking on a carousel item in the Item Details page, the UV embed player content updates along with rest of the page.

Description:

As pictured in mockup

https://nulib.github.io/next-gen-front-end/item.html

Description

Clean up error handling in the elasticsearch-api.js getItem() method. Unneccessary try catch, looks like elasticsearch is handling this already.

Description

Create component(s) to display metadata on the Item Data tab.

Done Looks Like

• Item details metadata is displayed to the page, and proper links provided.

Tasks

• Verify we can get all the proper data from Solr query to populate metadata in comp.
• Create a display component for each metadata data section.

Description

Create react component and components for the Item Details page. This is a master issue.

parent of #26
parent of #27
parent of #28
parent of #29
parent of #378 (https://github.com/nulib/next-generation-repository/issues/378)
parent of #101
parent of #91
parent of #89
parent of #82
parent of #81
parent of #78
parent of #72
parent of #57
parent of #30
parent of #114
parent of #115
parent of #116
parent of #120

Description

We are currently displaying the urls for rights statement and license on the Item Detail page. We need to display the labels, as shown in the mockup.
https://nulib.github.io/next-gen-front-end/item.html

depends on https://github.com/nulib/next-generation-repository/issues/604

Description

Clean up the item details row.

Done Looks Like

• Activate the More Details and Cite This Item buttons.
• Clean up display on Permalink form input.
• See if we can override the social icons so they layout horizontally and have NU styling.

Tasks

• Clean up display on Permalink form input.
• See if we can override the social icons so they layout horizontally and have NU styling.

Description

Create component(s) to display metadata on the Cite this Item tab.

Done Looks Like

• Cite this item metadata is displayed to the page, and proper links provided.

Tasks

• Verify we can get all the proper data from Solr query to populate metadata in comp.
• Create a display component for each metadata data section.

Descriptions

Write full, well documented unit tests for all global search components.

Done Looks Like

• Jest unit tests and mock api calls made for all global search components.

blocked by #54

child of #276

Description

Fix failing tests which are temporarily disabled in Layout.test.js

Done Looks Like

All tests are enabled and pass.

child of #178

Description

Implement collapse components to the Collections Item Detail sidebar filter categories.

Description

Currently the global search functionality just searches "title_tesim[]" property of a Solr document. Clarify what exactly we want to search for.

Tasks

• What Solr properties are relevant for searches?
• What's standard procedure in Solr?
• How do Solr document rankings impact query results?

Description

Create the 'find this item' tab in the Item Details view

Done Looks Like

• Tab is created on the item detail pages
• Newly created tab contains the headers detailed in the image

Description

If we no longer need the console logs of output for the elastic search api file, we should remove them as it might be slowing down page rendering.

Description

We should re-visit how to get Autocomplete wired into the global search. Currently the global search is not using a ReactiveSearch component. Let's re-attempt to plug in the ReactiveSearch "Search" component and see if we can figure out the flow of searching on any screen, and being re-directed to the Search Results screen.

Done Looks Like

• Autocomplete works in global search
• A search kicked off on any screen successfully navigates to the Search route and displays search expected search results.

Description

Show display_date rather than date on the item details page as this is the human readable version of the EDTF date.

Example: "circa January 1984?" will display rather than "1984?-01~"

Done Looks Like

• Front end uses display date

Description

Master issue for the Digital Collections Collection Items view:

Child issues

parent of #39
parent of #40

Description

This section (attached image), looks messy and may look better dropping to 2 - 2 column areas instead of 3 - 1. Drop Social media icons to the right of "Download image" boxes.

Description

Show visual feedback the Copy to Clipboard functionality was successful.

Done Looks Like

User gets some kind of visual feedback it was successful.

Description

Wire the search results individual item results into a component.

Done Looks Like

• Search results items are live, real data from Donut.

Tasks

• Parse out appropriate info to display in each item.
• Distinguish between a collection and image item.
• Display IIIF representation of item.

Description

Investigate integrating http://dc.stack.rdc-staging.library.northwestern.edu/reactivesearch with existing search box

Description

Ensure breadcrumbs component exists, and works with React router as a site-wide re-usable component.

Done Looks Like

• Breadcrumb navigation works as expected.

Tasks

• Verify current state of breadcrumbs.
• Drop into Item detail component.
• Write tests.

child of #23

Description

When adding a new collection or item, there's a missing image in the homepage carousel(s). We should hardcode in a default image as a fallback.

Done Looks Like

• Default image displays when adding a new collection or item and not choosing a representative image.

Tasks

• Add a default image to application (I have one from global marketing).
• Add logic to check for presence of a representative image, and code for either case.

Description

Continue the pattern of container component abstraction by breaking current GlobalSearch component into a container which handles data and redux integration, then passes down props and dispatch props to children.

Done Looks Like

• GlobalSearch becomes GlobalSearchContainer and children components are created.
• Search functionality works exactly the same.

To Do

• Refactor GlobalSearch into GlobalSearchContainer.
• Create child components.

child of #276

Description

Create carousels for the Item Details page for Library division and Collections.

Done Looks Like

• Carousel is created for Library division
• Carousel if created for Collection
• Item image itself is represented.

Tasks

• Determine what data we need to represent Library Division in a Solr query.
• Determine what data we need to represent Collections in a Solr query.
• Implement Library Division images in the carousel and carousel section component.
• Implement Collection images in the carousel and carousel section component.
• Represent work image below carousels.

Description

Write full, well documented unit tests for all search results page components.

Done Looks Like

Jest unit tests and mock api calls made for all search results page components.

blocked by #54

child of #276

Description

UV embed player on Item Details view doesn't always update to the latest selected item.

Tasks

• Do some console logging to figure out consistent patterns in the timing in order to trouble-shoot.
• See if there's a better way to re-initialize the UV script, and/or display a new item (best case) without re-adding the uv embed script to the page and re-initializing.

Description

Currently clicking on carousel items in the Item Details page doesn't navigate to the new view. Figure out where this is failing and fix.

Done Looks Like

• Clicking on carousel items navigates to expected item view page.

Description

The Collection item page should display thumbnails of all collection images instead of a the collection itself.

Done Looks Like

• Collection item page displays all items underneath the collection.

Tasks

• Create query to retrieve all collection items.
• Display all collection items in a photo grid.