EPIC: cataloging in BIBFRAME / Linked Data (UXPROD-4215)

[UXPROD-4224] Feature: Navigate Bib Resource | BF Cataloging Created: 19/Apr/23  Updated: 18/Dec/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: EPIC: cataloging in BIBFRAME / Linked Data

Type: New Feature Priority: TBD
Reporter: Doug Loynes Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: bf-alpha, bf-beta, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Front End Estimate: Large < 10 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: Large < 10 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Citation
PO Rank: 0

 Description   

NAVIGATE BIB RESOURCE

Purpose / Objective

  • As a cataloger, I need the ability to (1) navigate the fields that makeup a BIBFRAME resource and (2) navigate across the windows and panels that make up the BIBFRAME application so that I can complete creating or editing a record efficiently

Current state / Problem statement

  • Navigation panel in MARVA allows catalogers to jump to different fields for Work and Instance
  • The navigation panel, however, lacks vertical scrolling
  • Some catalogers expressed a preference to show only "relevant" fields in the navigation panel, and hide other fields to improve navigation

In scope

  • Resource navigation panel layout / functionality
  • Navigating between panels in BIBFRAME
  • Keyboard navigation – the system should allow the cataloger to navigate using the keyboard only

Out of scope

  • Navigation requirements specific to creating authority resources (as applicable)
  • Related to 'Customize'
  • Related to 'Create' with respect to templates

Considerations / Questions

  • How should the BIBFRAME navigation panel organize fields? E.g. show every field by logical grouping independent of whether the field has a value? Group the fields that have a value and provide the option to see all fields?
  • Challenges/complications of supporting keyboard shortcuts


 Comments   
Comment by Doug Loynes [ 20/Nov/23 ]

Discussed with LC Nov. 15 - some antipathy towards navigation within the UI. Strong preference for a UI where navigation would be superfluous because the information needed is readily available and the need to have a navigation utility is low. That will still need to be addressed in the design and in useability testing. 

Generated at Fri Feb 09 00:38:13 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.