Metadata Record Export
(UXPROD-652)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Metadata Record Export |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Magda Zacharska | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Metadata Record Export |
| Development Team: | None |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R2 |
| Rank: 5Colleges (Full Jul 2021): | R2 |
| Rank: MO State (MVP June 2020): | R1 |
| Rank: U of AL (MVP Oct 2020): | R2 |
| Description |
|
Current situation or problem: The existing implementation of the data export mapping profile supports instance, holdings and item fields that were determined by Data Export MM SIG Subgroup as the first priority and are listed here: https://docs.google.com/spreadsheets/d/1XvHmToGQwhzmMNlQ5-l1QTEDyUtDpdn_/edit#gid=1869895650 The properties without JIRA ticket assigned on the spreadsheet are not implemented yet. In scope In scope for this feature would be to support remaining fields
Questions Should we implement all the remaining fields or it would require further prioritization? |