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

[UXPROD-4277] Feature: BIBFRAME editor decoupled from FOLIO | BF Cataloging Created: 09/May/23  Updated: 16/Jan/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: SAReviewRequired, loc_candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Development Team: Citation
PO Rank: 0

 Description   

As a cataloger, I need the ability to catalog resource descriptions through a BIBFRAME editor, whether or not my institution has deployed FOLIO as its ILS solution.

In scope

  • BIBFRAME editor as a stand alone cataloging application
  • Core functionality supported to create, store, publish, resource descriptions
  • Extensibility of application, not tied to FOLIO operations

Out of scope

  • Partnering with an institution and/or commercial organization who plans to use Marva as a front-end BIBFRAME editor with a non-FOLIO back end application.
  • There is no requirement for EBSCO to demonstrate that the integration can be developed into production – only that Marva would be available as a stand-alone

Questions

As features are defined for BF Alpha, BF Beta, Ramsons, and Sunflower, consider how the feature set to support interoperability with FOLIO factors into decoupling the module from FOLIO  



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

Architectural decision to decouple BIBFRAME from FOLIO made early in the project. 

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