EPIC: cataloging in BIBFRAME / Linked Data
(UXPROD-4215)
|
|
| 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, bf-alpha, bf-beta | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Release: | Ramsons (R2 2024) |
| Epic Link: | EPIC: cataloging in BIBFRAME / Linked Data |
| Front End Estimate: | XL < 15 days |
| Front End Estimator: | Nikolai_Litvinenko |
| Front-End Confidence factor: | 100% |
| Back End Estimate: | XL < 15 days |
| Back End Estimator: | Punnoose Kutty Jacob Pullolickal |
| Back-End Confidence factor: | 100% |
| Development Team: | Citation |
| PO Rank: | 0 |
| RCA Group: | TBD |
| Description |
|
In scope
Related to UXPROD-4599 - whose scope is limited to executing the Work entity and the Instance entity We need to understand the mechanics of how Hubs work in LC's BF modelling in order to capture the scope and requirements for fulfilling the contractual obligations. Hubs employs the library practice of 'collocation' in order to identify definitive works in a collection. "[C]ollocation is attained by clustering item descriptions by . . . authors . . . and titles. These clusters are done by indexing. Authors’ names may vary, work titles may vary, and work content may vary but bringing together descriptions using different criteria gives the end user the ability to find the most useful resources for their needs."
Out of scope
Use case(s) All components that make up LC's BIBFRAME 2 Monograph profile must be displayed in production in Marva, inclusive of
Indexing rules and routines
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 Hubs "Hubs are abstract resources that function as a bridge between <multiple> Works. In this way, they function as aggregation and collocation resources. They make it possible, for example, to gather all of the <non-English> translations of Mark Twain’s Tom Sawyer or to capture in which other BF Works Francisco Tarrega’s Capricho árabe are included. [H]ubs perform three functions as aggregators: as subjects, as related works, and as Works in the RDA sense. Hubs, being BF Works, can be used as Subjects to describe other Works." LC recently released version 2.3 of its BIBFRAME ontology. Prior to 2.3, Hubs were defined as a subclass of 'Work.' With the release of version 2.3, Hubs have been redefined as one of the ontology's basic model classes. Questions
|