[SUP-65] EBSCO KB Title-Package does not always display as an agreement line Created: 13/Mar/22  Updated: 04/Apr/22  Resolved: 04/Apr/22

Status: Closed
Project: Support
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P1
Reporter: Khalilah Gambrell Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: Support, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: Bienenvolk
Affected Institution:
5 Colleges, Villanova University
RCA Group: TBD

 Description   

This issue is happening on Kiwi, Lotus, and Snapshot environments 

  1. Go to Agreements app
  2. Add a EBSCO KB package as an Agreement line. As expected displays as an Agreement line. 
  3. Add the EBSCO KB title-package:  title No Regrets in package EBSCO Ebooks (https://folio-snapshot.dev.folio.org/erm/eresources/19-5207-28110772)
  4. Return to the Agreement record. Problem Notice that the title-package name does not display. Only thing returned is # of titles selected/total # of titles in package  
  5. I inspected the code, the link to the title is returned <a href="/eholdings/resources/19-5207-28110772"></a> - https://folio-snapshot.dev.folio.org/eholdings/resources/19-5207-28110772. Also in reviewing Developer tools, I cannot see any errors. 
  6. Also note the linked Agreement displays on the eholdings record https://folio-snapshot.dev.folio.org/eholdings/resources/19-5207-28110772


 Comments   
Comment by Owen Stephens [ 14/Mar/22 ]

Potentially caused by a failure to parse dates from the title level. Seeing the following in the JSON for the Entitlements (in Agreements)

"reference_object": {
        "error": "java.util.concurrent.ExecutionException",
        "message": "java.time.format.DateTimeParseException: Text '1/1/2021 12:00:00 AM' could not be parsed at index 0"
}
Comment by Owen Stephens [ 14/Mar/22 ]

Looking at the response from eHoldings I'm seeing dates like:

"managedCoverages": [
    {
        "beginCoverage": "1/5/1990 12:00:00 AM",
        "endCoverage": "12/31/9999 12:00:00 AM"
    }
],
"customCoverages": [
    {
        "beginCoverage": "8/13/2018 12:00:00 AM",
        "endCoverage": "9/13/2018 12:00:00 AM"
    }
]

Khalilah Gambrell We are expecting the coverage dates to be in the format yyyy-MM-dd, which is also the format specified in https://developer.ebsco.com/knowledge-services/holdingsiq/reference#/ - has this changed?

Comment by Khalilah Gambrell [ 14/Mar/22 ]

Hey Owen Stephens. Checking with Spitfire if we changes the date format for API GET /eholdings/resources/{resourceId}

Comment by Owen Stephens [ 14/Mar/22 ]

Khalilah Gambrell thanks - although also possible its HoldingsIQ where the change lies?

Comment by Khalilah Gambrell [ 14/Mar/22 ]

Owen Stephens, is Agreements calling HoldingsIQ directly? Or is it calling mod-kb-ebsco-java? 

Comment by Owen Stephens [ 14/Mar/22 ]

Khalilah Gambrell Always mod-kb-ebsco-java - the question in my mind is whether you parse the dates from HoldingsIQ or just use them as you are given them

Comment by Khalilah Gambrell [ 14/Mar/22 ]

Owen Stephens, it is a HoldingsIQ change

Comment by Anya [ 14/Mar/22 ]

SUPPORT: Khalilah Gambrell / Owen Stephens should we close this ticket?

Comment by Khalilah Gambrell [ 14/Mar/22 ]

Anya - keep ticket for now. I will update once I get HoldingsIQ feedback.

Comment by Anya [ 28/Mar/22 ]

Support: Khalilah Gambrell  is there an update on this?

Comment by Khalilah Gambrell [ 29/Mar/22 ]

Owen Stephens - I verified that dates are now returning in the right format. Can you verify that the issue is resolved?

Comment by Owen Stephens [ 31/Mar/22 ]

Yes - this is resolved Khalilah Gambrell Anya

Comment by Anya [ 04/Apr/22 ]

Support: this is resolved in what release? Or did this not need a release... 

Comment by Owen Stephens [ 04/Apr/22 ]

Anya No need for a release as it was a HoldingsIQ API issue not a Folio issue

Comment by Khalilah Gambrell [ 04/Apr/22 ]

no release required since it was EBSCO KB work. 

Comment by Anya [ 04/Apr/22 ]

Support - Owen Stephens/ Khalilah Gambrell so this ticket can be closed? 

Comment by Owen Stephens [ 04/Apr/22 ]

Yes as far as I'm concerned

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