Identifying Lean Library Alternative API calls

Request from: Nanyang Technological University (Sean)

Original report:

I understand that Lean Library calls the open url link resolver to check what we have.

The issue we have right now is that it seems the calls that it makes does not contain sufficient information to be used in our final reporting.

For example, these are the calls that are likely from Lean Library:

http://ntu-sp.alma.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?debug=true&svc_dat=CTO&url_ver=Z39.88-2004&rft.isbn=0000000078

http://ntu-sp.alma.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?debug=true&svc_dat=CTO&url_ver=Z39.88-2004&rft.issn=0165-7208&rft.jtitle=Pharmacochemistry+Library&rft.atitle=Tetrahydroquinolines+and+Isoquinolines&rft.spage=273&rft.epage=295&rft.au=Satyavan+Sharma%2C+Nitya+Anand&rft.date=1997-01-01&rft_id=info%3Adoi%2F10.1016%2Fs0165-7208%2897%2980033-5

http://ntu-sp.alma.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?debug=true&svc_dat=CTO&url_ver=Z39.88-2004&rft.jtitle=Oxford+Handbooks+Online&rft.atitle=The+Changing+Popular+Images+of+Science&rft.au=David+A.+Kirby&rft.date=2017-06-06&rft_id=info%3Adoi%2F10.1093%2Foxfordhb%2F9780190497620.013.32

http://ntu-sp.primo.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?rft.epage=533&rft.volume=41&rft_id=info:doi/10.1177/0309132516646495&rft.jtitle=Progress in Human Geography&rft.aufirst=L&rft.issue=4&rft.aulast=Pulido&vid=65NTU_INST:65NTU_INST&institution=65NTU_INST&url_ver=Z39.88-2004&rft.date=2017&rft.spage=524&lang=en&rft.atitle=Geographies of race and ethnicity II: Environmental racism, racial capitalism and state-sanctioned violence&rft.title=Progress in Human Geography

And these are the calls made by other sources:

http://ntu-sp.primo.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.epage=470&rft.pub=ACM&rft.series=WWW '13&rft_id=info:doi/10.1145/2488388.2488429&rfr_id=info:sid/primo.exlibrisgroup.com-acm&resource_type=conference_proceedings&rft.isbn_list=145032035X&rft.isbn=9781450320351&rft.btitle=Proceedings of the 22nd international conference on world wide web&rft.genre=proceeding&rft.pages=459-470&vid=65NTU_INST:65NTU_INST&rft.date=2013-05-13&rft.spage=459&rft.au=Goldstein, Daniel&rft_dat=<acm>2488429</acm>,language=en&rft.atitle=The cost of annoying ads

http://ntu-sp.primo.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.epage=475&rft.volume=22&rft.pub=BRILL&rft.place=The Netherlands&rft_id=info:doi/10.1111/lands.12408&rfr_id=info:sid/primo.exlibrisgroup.com-brill&resource_type=articles&rft.jtitle=Journal of labor and society&rft.genre=article&rft.issue=2&rft.pages=461-475&vid=65NTU_INST:65NTU_INST&rft.date=2019-12&rft.spage=461&rft.au=Chan, Jenny&rft_dat=<brill>10_1111_lands_12408</brill>,language=en&rft.atitle=State and labor in China, 1978–2018&rft.eissn=2471-4607

Could you ensure the source field rfr_id is set whenever Lean Library makes calls? Because since it’s not set, our reports show that the source is Unknown.

Please see here for more info:

https://developers.exlibrisgroup.com/alma/integrations/discovery/xml-openurl/

https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/Alma_Analytics_Subject_Areas/Link_Resolver_Usage#The_Source_Field

Suggested solution by the client:

Could you ensure the source field rfr_id is set whenever Lean Library makes calls? Because since it’s not set, our reports show that the source is Unknown.

Explanation from LL:

Client wanted the Alternative API calls from Lean Library can be identified, so they can see from their reports how many API calls came from LL.

Update:

Added Ref ID but it did not work for the client.

Hi Clare,

I’ve added RFR_ID on 30 May. So by right in June we should expect all lean library sources to have the value LeanLibrary. But we found that it’s not the case for some still. See below.

I've checked several examples from June of calls that are coming in with an unknown source.
From what I can see, they are coming from Amazon-owned IPs, for example:
18.196.143.140 - most common IP
35.174.61.14
54.88.41.28

Here is a sample log from a request from 13/06/2023:
The request:
http://ntu-sp.alma.exlibrisgroup.com/view/uresolver/65NTU_INST/openurl?debug=true&svc_dat=CTO&url_ver=Z39.88-2004&rft.isbn=0000015857
The log:
18.196.143.140 "18.196.143.140" - - [13/Jun/2023:07:40:14 +0000] GET //view/uresolver/65NTU_INST/openurl-NIE?svc_dat=CTO&url_ver=Z39.88-2004&rft.isbn=0000015857 HTTP/1.1 200 2084 55 B351886DD6313B8B77689340323FE982.app04.ap01.prod.alma.dc05.hosted.exlibrisgroup.com:1801 0.055 http-bio-exec-39 - "GuzzleHttp/6.3.3 curl/7.58.0 PHP/7.3.33-7+ubuntu18.04.1+deb.sury.org+2" 12 14 2 9 0 0 0 2 0 0 openurl 1295 0 Pm9c95JszH - \"\"

The first IP is under Lean Library so how can we ensure that these requests are tagged with LeanLibrary?