EPIC: transforming data to support BIBFRAME
(UXPROD-4216)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | EPIC: transforming data to support BIBFRAME |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Doug Loynes | Assignee: | Anuar Nurmakanov |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | bf-alpha, bf-beta | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | EPIC: transforming data to support BIBFRAME |
| Development Team: | Citation |
| PO Rank: | 0 |
| Description |
|
Current situation or problem: The scope of the BIBFRAME project encompasses interoperability with FOLIO modules (e.g. mod-search, data import, data export, etc.) to support cataloging functions and synchronize collections stored as MARC records and as BIBFRAME resource descriptions. The scope also encompasses creating a data graph of resources representing the library's collections and providing tools for managing the data graph from within the BIBFRAME editor application (Marva). However, the architecture decisions around schema differ markedly between FOLIO and Data Graph. These discrepancies will need to be addressed and resolved as a condition for the production release of BIBFRAME. In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |