This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Page tree
Skip to end of metadata
Go to start of metadata


TitleProactive repository health check
Primary ActorRepository Administrator, Preservation Archivist
ScopeOrganization (black-box)
LevelVery High Summary
Story (A paragraph or two describing what happens)

The repository should proactively provide the capability to check and provide status on its contents out of the box. This could include the following:

  • Maintain a registry of items (objects / resources) in the repository.
  • Out of the box, routinely check the validity of all items at a frequency easily specified by a system administrator. For example, the default frequency could be annually, but easily configurable to quarterly. These checks may take considerable time and could be asynchronous.
  • Log the results and notify the administrator of any errors.
  • Provide the capability to obtain the overall health of the repository at any time, returning relatively recent rollup results. For example:
    • Results could include how many items were checked in the last day/week/month/quarter year, any items that have not been checked in more than 3/6/12 months, and summary success / failure of the checks.
    • Results could be summarized daily with the most recent daily result provided back to the original requester.