Epic to link all support issues located in Dev projects (SUP-12)

[SUP-13] date display in RTAC Created: 06/Aug/20  Updated: 21/Dec/21  Resolved: 17/Aug/20

Status: Closed
Project: Support
Components: None
Affects versions: None
Fix versions: None
Parent: Epic to link all support issues located in Dev projects

Type: Bug Priority: TBD
Reporter: Anya Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2020-08-06-06-22-45-579.png    
Sprint:
Epic Link: Epic to link all support issues located in Dev projects

 Description   

Patrons are seeing date/time in RTAC display in discovery platform that is being provided via FOLIO and it is causing confusion due to the format and spacing.

https://edge-washjeff.folio.ebsco.com/prod/rtac/folioRTAC?mms_id=d4df9b97-fef0-52db-9577-bf7c4f093d2f&apikey=eyJzIjoibVdFQ1dENVA4YyIsInQiOiJmczAwMDAxMDI0IiwidSI6ImZzMDAwMDEwMjQifQ

AN gtm.d4df9b97.fef0.52db.9577.bf7c4f093d2f

Currently EBSCO has a workaround that is on a "do not use this" but this is only a temporary fix.



 Comments   
Comment by Molly Driscoll [ 07/Aug/20 ]

Feedback from Adam Walsh (LSE Manager, EBSCO): "I don’t suppose the JIRA might include or be extended to remove due-time entirely or at least break it down so we can use it or not."

Some sites have wanted to use due time, so removing it entirely is not ideal.

Comment by Kelly Drake [ 12/Aug/20 ]

Support SIG discussion 8/10/20:The date/time format sent in RTAC is the standard format for all API date fields. Changing this format in one API would be substandard.
While it is possible that another field/element could be added to RTAC it might be preferable for the Discovery layers to interpret the data per institution.

Also the due date is supplied to discovery layers via several apis. EDGE-RTAC, RTAC, and for VuFind - Inventory/instance - so changes would have to be made to each.

Comment by Kelly Drake [ 17/Aug/20 ]

Support SIG decided, and Anya agreed, that this was a Discovery issue

Generated at Thu Feb 08 22:21:03 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.