BIBFRAME Thin Thread Epic
(UXPROD-4318)
|
|
| Status: | In Progress |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | BIBFRAME Thin Thread Epic |
| 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: | BIBFRAME Thin Thread Epic |
| Development Team: | Citation |
| Report Functional Area(s): |
Import and Export
|
| PO Rank: | 0 |
| Description |
|
Current situation or problem: For the BIBFRAME thin thread project, we will need the ability to load and populate the BIBFRAME database with records and resource descriptions created outside of the thin thread environment. The source records will need to be processed so that they map to and align with the BIBFRAME 2.0 JSON schemas used for building out the BIBFRAME database on the backend and supporting BIBFRAME cataloging workflows on the front end. In scope
Out of scope
Use case(s) The Library of Congress has supplied EBSCO with sample resource descriptions contributed to its BIBFRAME database; and a parallel set of MARC records where the resources were initially cataloged in its Voyager application. Both sets of sample records are in RDF/XML format. Proposed solution/stories For the Thin Thread, we will initially focus on converting RDF/XML records into JSON, and then load the files into the test BIBFRAME database. We can investigate data utilities for executing the conversion to JSON and load the converted files accordingly. Eventually, the Thin Thread will require pipelines for transforming MARC records into BIBFRAME, as it will be more common for catalogers to select an existing MARC record and perform copy cataloging in BIBFRAME. Links to additional info Questions |