Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Status Quo

The Reports and Warehouse tools are not necessarily linked, but together they serve the need to produce high-level reports of portfolio usage data across multiple sites. The tools are, by all accounts, difficult to use and maintain, and the consensus view is that a better long-term solution should be found.

The Reports tool suffers from unfixed blocker issues in the latest 2.7 testing. Community resource to resolve these issues and continue to maintain the tools has not come forward, while the maintenance team feels itself unable to address them.

Both of these tools have been provisional, and were never adopted as core tools.

Warehouse provides really only an API, and so can't be stealthed.

Proposal

Reports should be stealthed, and they should both now also be flagged for deprecation in the release notes. If community resource comes forward to fix and maintain them they may be restored to full service in a future version. If not, they may be removed entirely for 2.8, but this should also be used as an occasion to discuss and perhaps support alternatives.

Who would be affected

There are institutions using one or both of these tools in production (the known institutions include IU and RINET), and they would be affected by the blocker issues in any event, should they opt for 2.7.

  • No labels