Skip to content

Jago Brown

My feedback

2 results found

  1. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jago Brown commented  · 

    What ever the IP field in usage reports should only store "valid" v4 of v6 Ip addresses and maybe NULL
    Jago

    An error occurred while saving the comment
    Jago Brown commented  · 

    My Ticket Question: Can Proquest allow the IP field in the usage report to store both IPv4 & IPv6? I think this might solve the problem described.

    We are building a database table to store weekly usage data but have found that the IP data has invalid IP addresses.
    i.e. not IPv4 or IPv6

    e.g. we have 2 records in our Proquest usage data where the IP = "2405:8100:8000:"

    This looks like a truncated IPv6 address. The result is, importing to our database fails as the IP column rejects as invalid: "2405:8100:8000:"

    Jago Brown supported this idea  · 
  2. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jago Brown supported this idea  · 
    An error occurred while saving the comment
    Jago Brown commented  · 

    In the absence of an API to pull ebook usage data we are manually downloading CSV reports at ....ebookcentral.proquest.com/libCentral/UsageReportSearch.aspx

    This makes it time consuming getting this data into our database and more prone to errors than consuming APIs which we can do for LMS, SIS & Attendance data!

    Kind regards

    Jago Brown

Feedback and Knowledge Base