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

[UXPROD-4598] Feature: Wireframes | BF Alpha Created: 14/Dec/23  Updated: 08/Feb/24

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
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines MODLD-244 BE API for New Search based on Work In Progress
defines UILD-188 SPIKE: Front End refactoring In Progress
defines MODLD-231 SPIKE: Back End Marva Refactoring Closed
defines MODLD-237 BE API for Wireframed Marva UI Closed
Release: Ramsons (R2 2024)
Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Front End Estimate: XXXL: 30-45 days
Front-End Confidence factor: 70%
Back End Estimate: Medium < 5 days
Back-End Confidence factor: 100%
Development Team: Citation
PO Rank: 0
RCA Group: TBD

 Description   

Current situation or problem:

The Thin Thread relied on the most basic of interfaces to support cataloging workflows. 

BIBFRAME Alpha (roughly scheduled for April 2024) will incorporate wireframes designed by the EBSCO UX team, based on a series of user sessions to understand the challenges and preferences end users articulated. 

The BIBFRAME module should provide a general 'look and feel' of other FOLIO applications, particularly FOLIO Inventory. 

Search options and how they are displayed to the end user, should be consistent between FOLIO Inventory and BIBFRAME - but not identical. 

Search results and editing mode will not be identical with FOLIO Inventory and have more leeway for taking a new approach.

In scope

Cataloging workflows inclusive of

  • search
  • search indexes
  • search filters
  • search results
  • advanced search
  • edit mode / create mode
  • contextual help / warnings / error messages
  • dashboard

Out of scope

  • Data.Graph integration
  • Manager view of Marva
  • System administrator view of Marva

Use case(s)

  • Search
    • adhere to the search layout supported in FOLIO Inventory
    • where search indexes and search box contained in upper left of search screen
  • Search indexes
    • Thin Thread limited to keyword search of four indexes: ISBN, LCCN, Title, Contributor
    • Q: will the BIBFRAME module need to support a general keyword index?
  • Search filters
    • Filters will need to be available to end users for refining a search result set
    • A challenge for filtering is that Work entities and Instance entities have different properties that can be filtered on
    • Candidate filter categories:
      • By format
      • By edition
      • By language of the Work
      • By subject
  • Search result sets
    • Search result sets will need to support the ability to compare and select Instance resource descriptions and Work resource descriptions
    •  
    • Search result set screen will need to support certain actions and functionality, including:
      • displaying the full resource
      • comparing two resource descriptions side by side
      • selecting a resource for editing (and opening the resource in edit mode)
      • refining search queries
      •  
    • Catalogers have expressed interest in a search result design where Instance resource descriptions are clustered around corresponding Works
  • Advanced search
    • Advanced search will closely follow the design and format of advanced search in FOLIO Inventory
    • Inclusive of the index types supported: 
      • keyword
      • phrase
      • exact phrase
    • Boolean operators supported:
      • AND
      • OR
      • NOT
        • NOTE: advanced search in FOLIO Inventory does not support explicitly building queries with nested parenthesis. Will need to fully understand how queries are parsed in FOLIO Inventory in order to replicate in Marva
    •  
  • Edit mode / Create mode
    • Edit mode will allow catalogers to edit all components of a resource description for both the Work entity and the Instance entity
    • Editing existing resources
    • Creating new resources from scratch
    • Creating a new Instance or Work by copying / duplicating an existing resource
    • Compact views of a resource (e.g. displaying only fields with values)
    • Full views of a resource (e.g. displaying all fields whether or not they have values)
    • Supporting fields with literals
    • Supporting fields with lookups
    • Supporting fields that are repeatable (or non-repeatable)
    • Taking actions on cataloging work (save resource, close resource, suppress resource from patron view)
    • Previewing a resource in BIBFRAME view; and in MARC view
    • Navigation within the interface (e.g. jumping to specific fields in an entity)
    •  
  • contextual help / warnings / error messages
    • Providing end users with assistance in to understand BIBFRAME principles and rules
    • Enforcing certain normalization rules for data input
    • Enforcing certain validation rules for saving resource descriptions (driven primarily by MARC validation)
    • Displaying warning messages to illustrate best or preferred cataloging practices, without preventing the end from saving a record
    •  
  • Dashboard
    • Ability for end user to see completed work
    • Ability for end user to see existing work / work in progress (NOTE: systemic constraint on 'work in progress' with FOLIO; BIBFRAME will support whatever is possible on the platform)
    • Ability to see graphical representation of productivity (e.g. number of new resources created) over defined time periods (today, this week, this month)

Proposed solution/stories

Links to additional info

Questions

  1. To what degree will the wireframes conform with standard FOLIO iconography? Is there room to deviate where recommended by the UX team?
  2. Accounting for design decisions that could impact the BIBFRAME module as a stand alone application -->  open source libraries available outside of FOLIO
  3. Determine needs for basic search, specifically whether libraries need a general keyword search across indexes

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