FEATURE: Trillium - Executing Work entity components / Instance entity components
Description
Priority
Fix versions
Development Team
Citation
Assignee
Unassigned
UnassignedSolution Architect

Parent Field Value
None
Parent Status
None
blocks
defines
Checklist
hideActivity
Show:
Details
Details
Reporter

PO Rank
0
Front End Estimate
XXXL: 30-45 days
Front-End Confidence factor
90%
Back End Estimate
XXXL: 30-45 days
Back-End Confidence factor
100%
Release
Trillium (R2 2025)
Tech Design Ready
Yes
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 4, 2025 at 7:22 PM
Updated March 4, 2025 at 7:24 PM
TestRail: Cases
TestRail: Runs
This continues
In scope
This feature is closely aligned with
The Trillium scope is to be determined.
The scope of this feature is to execute Builde / BIBFRAME LITE to BIBFRAME* for components that make up the Work and Instance entities
BF2 Monograph profile only
Prioritized list of components that make up Work entity
Prioritized list of components that make up Instance entity
Indexing rules and routines for components in the Work and Instance entities
*Assume rules defined in BIBFRAME v.2.7 from the Library of Congress
Out of scope
BIBFRAME 2 Hub entity
BIBFRAME 2 Item entity
Use case(s)
All components that make up LC's BIBFRAME 2 Monograph profile must be displayed in production in the Linked Data Editor, inclusive of
literals fields
lookup fields
Indexing rules and routines
keyword for selected indexes (starting with ISBN, LCCN, Title, Contributor)
phrase for supported full text fields (TBD)
exact phrase for supported full text fields (TBD)
NOTE: will need to determine if the module will support a general keyword index against all (or defined subset of) entity components
Components treated consistently between BIBFRAME LITE and BIBFRAME 2
Components treated differently between BIBFRAME LITE and BIBFRAME 2 --> resulting in increased complexity of mapping
Proposed solution/stories
Links to additional info
Questions