Library Data Platform (LDP) 1.0 (UXPROD-1881)

[UXPROD-1438] Implement a process for tracking data-related API schema changes Created: 17/Jan/19  Updated: 16/Sep/20  Resolved: 24/Mar/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Library Data Platform (LDP) 1.0

Type: New Feature Priority: P2
Reporter: Nassib Nassar Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: ldp-platform, mandatory, po-mvp, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-1414 Complete the documentation of data at... Closed
Relates
relates to DEBT-2 No automatic schema/data migrations Closed
Epic Link: Library Data Platform (LDP) 1.0
Development Team: Prokopovych
PO Rank: 120.2
Rank: Chalmers (Impl Aut 2019): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R1
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

After documentation of data attributes in Folio module APIs is completed ( https://folio-org.atlassian.net/browse/UXPROD-1414 ), it will be very important for developers in the reporting effort to keep track of data-related API schema changes in new versions of the Folio modules, so that the reporting system can continue to ingest Folio data. A process is needed for managing and tracking these API changes and partnering with developers in reporting to understand the significance of the changes.

This issue is a blocker for the entire Library Data Platform reference implementation epic ( https://folio-org.atlassian.net/browse/UXPROD-1128 ). It is needed to maintain compatibility with the rest of the Folio ecosystem.



 Comments   
Comment by Nassib Nassar [ 17/Jan/19 ]

Please recommend a developer to estimate the BE.

Comment by Kristin Martin [ 30/Apr/19 ]

This appears to be a NFR, so Chicago is not ranking.

Generated at Fri Feb 09 00:15:35 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.