You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although Ebsco has always provided a titles list webpage to scrape and feed into the Ebsco list.json, they have now reformatted their title list webpage and they are also linking to xls formatted versions of their database specific title lists. Does this open up any new programmatic avenues for refreshing the Ebscohost list.json and also updating the dozens of Ebsco pkb files that we can harvest as xls rather than html? Take a look to see what I mean https://www.ebsco.com/title-lists It seems like this could be an easier source of Ebsco database shortcode conversion to long name conversion, but also a method of updating the Ebscohost pkb files. Thanks for taking a look at this. :)
The text was updated successfully, but these errors were encountered:
Adding some caveats to this discussion. I have noticed the Ebsco provided list of database titles is not always accurate and in some cases is missing some databases. Is there a way to update list.json but potentially leave in manually added shortcodes:longName key:values that are added, rather than wiping the list.json clean every time a new list.json is harvested programmatically?
Although Ebsco has always provided a titles list webpage to scrape and feed into the Ebsco list.json, they have now reformatted their title list webpage and they are also linking to xls formatted versions of their database specific title lists. Does this open up any new programmatic avenues for refreshing the Ebscohost list.json and also updating the dozens of Ebsco pkb files that we can harvest as xls rather than html? Take a look to see what I mean https://www.ebsco.com/title-lists It seems like this could be an easier source of Ebsco database shortcode conversion to long name conversion, but also a method of updating the Ebscohost pkb files. Thanks for taking a look at this. :)
The text was updated successfully, but these errors were encountered: