Reports created for Cross-Publication EAR must handle large amounts of data. Consider these tips to help reports run more efficiently.
Define the purpose for the report as narrowly as possible while still getting the desired information. Consider whether two more limited reports would work instead of one more expansive report.
Views already have complex filtering. Adding a complex filter structure to complex data sources may cause a report to time out when run.
Consider the order of filters to minimize the number of records the system is required to process. Example: To filter against Additional Manuscript Detail (AMD) values, set a filter for the AMD description also. Filter on description first, and then the system will have fewer records to look at for the value.
Consider the size of data fields. Example: To filter by publication, use the Publication Code field to filter results rather than the Journal Full Title field. Include the Journal Full Title field in the report for reference. Similarly, use Document ID rather than Manuscript Number field and People ID fields rather than name fields.
If reports are often run against the same subset of publications, consider creating a Publication Group made up of that subset of publications. A drop-down list of defined Publication Groups appears on the Cross-Publication EAR menu page. Select the Publication Group before running the report, and the system will run the report only against the data for that Publication Group. Using a Publication Group replaces the need to create filters on a report to limit results to the subset of publications.
Similarly, when creating or editing a report, select the Publication Group, so that previewing the report runs only against the data from the Publication Group.
Note: Publication Groups are configured by a system administrator. See Configure Enterprise Analytics Reporting and Cross-Publication Enterprise Analytics Reporting.
To return to previous page click ALT + left arrow