Reporting Feature Requests (UXPROD-1910)

[UXPROD-1870] SIP data format standards for reports Created: 10/Jul/19  Updated: 02/Aug/22  Resolved: 02/Aug/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting Feature Requests

Type: New Feature Priority: TBD
Reporter: Sharon Beltaine Assignee: Nassib Nassar
Resolution: Won't Do Votes: 0
Labels: ldp-platform, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Reporting Feature Requests
Back End Estimate: XXL < 30 days
Back End Estimator: Nassib Nassar
Development Team: Reporting
PO Rank: 0
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R5
Rank: Lehigh (MVP Summer 2020): R5
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Some libraries need the ability to generate reports that meet SIP (Standard Interchange Protocol) data format standards for libraries. See Andrea Loigman for more details on this issue.



 Comments   
Comment by Sharon Beltaine [ 15/Jul/19 ]

Reviewed by Reporting SIG on 7/15/19. Will ask rep from RA SIG to join to discuss in more detail at next Reporting SIG meeting.

Comment by Angela Zoss [ 12/Sep/19 ]

Clarification from Duke: We don't need reports in SIP2 format. We need FOLIO to support SIP2 communication format.

Comment by Erin Nettifee [ 02/Aug/22 ]

SIP isn't a reporting format; this is a "crossed wires" ticket and can be closed.

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