Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COUNTER 5 Usage Imports #660

Merged
merged 108 commits into from
Sep 1, 2020

Conversation

queryluke
Copy link
Contributor

Feature

Makes the usage module compatible with COUNTER 5 reports. Backwards compatible with COUNTER 4.

Requirements

Run usage/install/protected/next/001-01.sql against your development database.

Testing

  • Create new SUSHI COUNTER 5 services and test with various vendors
  • Download various COUNTER 5 reports from vendors and manually upload
  • Test with SUSHI COUNTER 4 vendors
  • Test with COUNTER 4 reports from vendors

queryluke and others added 30 commits November 10, 2019 11:58
…s-3.0.1-compat

ERM-56: Long load times in the Resources module
ERM-24: Linking to license terms from EBSCO Full Text Finder
…mpat

ERM-16: Activating holdings managed in EBSCOadmin
…d-sites-3.0.1-compat

ERM-59: Cannot remove Authorized Sites from Access information in Resource records
…1-compat

ERM-55: SUSHI Harvesting and Import Issues
…h-by-date

ERM-67: Searching by Date Created in Resources module doesn't generate accurate results
@andyp-uk
Copy link
Contributor

andyp-uk commented Aug 6, 2020

Note the Apache user should have full permissions to the usage/counterstore folder where applicable, in common with usage/logs and usage/archive folders.

$this->logStatus("Report was queued for processing, but was not processable after 3 retries.");
$this->saveLogAndExit($reportLayout);
}
sleep(1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should back out this commit. Using JSTOR as the only example of a vendor that returns error 1011 that we are aware of, the wait time varies considerably, depending on the number of reports you request and the date range you specify. Even with a very long sleep interval, I don’t get any reports more often than I do. The user can always manually rerun the import from the console.

@andyp-uk
Copy link
Contributor

andyp-uk commented Sep 1, 2020

We will need to rename this file to match the version number of the release.
usage/install/protected/3.0.2/001-000.sql

@andyp-uk
Copy link
Contributor

andyp-uk commented Sep 1, 2020

@rtatterson has tested these changes and reports no problems.

@andyp-uk andyp-uk merged commit 9d82d12 into coral-erm:development Sep 1, 2020
@andyp-uk andyp-uk added the enhancement This is an enhancement (not a bug) label Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This is an enhancement (not a bug)
Projects
None yet
4 participants