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 | ||
| Attachments: |
|
| Epic Link: | BIBFRAME Thin Thread Epic |
| Development Team: | Citation |
| Report Functional Area(s): |
Metadata Management
|
| PO Rank: | 0 |
| Description |
|
Current situation or problem: The thin thread for the BIBFRAME project must support cataloging profiles for Work, Instance, and Item in order for catalogers to search for resource descriptions, edit resource descriptions, and/or create new resource descriptions. The profiles must fully support and align with the profiles created by the Library of Congress for BIBFRAME 2.0. In scope At minimum, the profiles needed for the thin thread must include:
Additionally, there may be more supplementary profiles referenced from Work, Instance, and Item that could be included as part of the thin thread. Collectively, the profiles covered in the thin thread define the BIBFRAME 2.0 schemas needed to conduct end to end cataloging for selected workflows. The profiles will be used to
For a list Library of Congress BIBFRAME profiles, see Github repository: https://github.com/lcnetdev/bfe-profiles/tree/main/profile-prod/src Out of scope
NOTE: Profiles for other BIBFRAME 2.0 categories (e.g. Agents and Identifiers) will be used selectively. Only a subset of profiles in these categories will be included within scope; not every profile within a given category will need to be supported for the thin thread. Use case(s) Proposed solution/stories For the Thin Thread, we will initially focus on loading sample records from the Library of Congress directly into the database. Eventually, the Thin Thread will need pipelines for transforming MARC records into BIBFRAME. The files supplied by LC are in RDF/XML format, and will need to be converted into JSON - the preferred format for the database - and then loaded into the test BIBFRAME database. We can investigate data utilities for executing the conversion to JSON and load the converted files accordingly. Links to additional info Questions
|