Skip to main content
Support - EBSCO Help

Holdings Management - Coverage Dates

Coverage Dates

Title-Level Custom Coverage

Enter Custom Coverage dates by enteringBegin and End dates in the fields provided or by clicking the appropriate dates in the pop-up calendars when you click into a field. To indicate that your coverage is current and ongoing, leave the End Date field empty.
Note: If you have more than one coverage date range to add, click the Plus button to add another range.  When entering multiple custom coverage dates, you must enter dates in descending order.

For example, your custom coverage dates may resemble:

Coverage Dates


Package-Level Custom Coverage

Applying Custom Coverage at the Package level is a convenient way to update coverage for all Titles in the Package.  Package-level coverage can be overridden at the Title level as long as the Custom Coverage specified at the Title level is within the range specified at the Package level.

For example, if you have set your Package coverage to be 3/22/2005 – Present and you attempt to specify Title coverage outside of that range, you will see an error message upon save:

Custom Coverage - Package


Uploading Holdings

When uploading holdings, enter custom coverage for titles with coverage different than the default coverage or for titles with coverage not managed by EBSCO. Click here to see supported date formats.


Custom Coverage Display

Custom Coverage dates will impact the following downstream applications (if they are enabled for your library): Publication Finder, Full Text Finder, EDS, MARC, PubMed, Google Scholar, KBART and Naver.  

Note: For Publication Finder and Full Text Finder, you can specify a Coverage Statement to replace the dates.  See the Coverage Display setting.


Titles Ordered Through EBSCO

For Titles ordered through EBSCO Subscription Services (ESS), EBSCO will set the Coverage.  The EBSCO set coverage can be overwritten, if desired.  Clicking “Revert to EBSCO coverage” will easily revert to the EBSCO provided dates.

EBSCO will update coverage as follows:

  • Order has not been renewed (Subscription date has expired)
    • Then: Custom coverage start = Blank AND Custom coverage end = blank and custom coverage statement will = NoAccess
  • Future order (Subscription has not begun)
    • Then: Custom coverage start date = display date provided by ESS AND Custom coverage end date = display date provided by ESS
  • Outside of managed coverage date
    • Then: Custom coverage start date = display date provided by ESS AND Custom coverage end date = display date provided by ESS