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: | None | ||
| 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 |
| RCA Group: | TBD |
| Description |
|
Current situation or problem: Scope of this card is to determine bulk edit requirements needed to support Linked Data workflows. Day 1 functionality requires the ability to support parallel MARC-based and linked data-based cataloging workflows - recognizing that some libraries will continue to conduct some cataloging in MARC while transitioning other cataloging work to Marva. How the source of truth for any given title is managed is covered in the data governance feature,
Bulk edit functions need to be examined and explicitly called out in user stories to cover use cases in this interim state (where MARC and linked data operations co-exist).
In scope Data governance Out of scope Use case(s) Proposed solution/stories Links to additional info Questions Will libraries need to create / manage separate bulk edit jobs - one each for records where MARC is the source of truth and for where BIBFRAME is the source of truth? Can bulk edit operations be applied independent of the source of a title? If so, how will / must this affect data governance requirements? |