-
Notifications
You must be signed in to change notification settings - Fork 65
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
COUNTER 5 Usage Imports #660
Conversation
Add sirsi help docs
Fix Localization Date issues
…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
Terms tool css update
Terms tool css update
…h-by-date ERM-67: Searching by Date Created in Resources module doesn't generate accurate results
Sirsi 3.0.1 1.0
Sirsi 3.0.1-1.1
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); |
There was a problem hiding this comment.
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.
This reverts commit 97a178f.
We will need to rename this file to match the version number of the release. |
@rtatterson has tested these changes and reports no problems. |
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