Overview recordings and links
...
- Dashboard
- eHoldings
- ERM Comparisons
- eUsage
- Licenses
- Local KB Admin
- Notes
- Orders
- Organizations (including Interfaces)
- Users App
- Tags
...
| Displayed information | Rules for calculating |
|---|---|
| Period start and Period end dates in the Agreement view | If there is a current period defined for the agreement (a period that has a Start date in the past and an End date in the future (or no End date specified), the "Period start" and "Period end" dates in the Agreement view will reflect the current period start and end. If the Agreement does not have a current period, then the Period start and Period end will reflect the earliest start date (out of all the agreement periods) and the latest end date (also out of all the agreement periods). This is so that for historical agreements you always see the full time that agreement ran for. |
| License and Business Terms | The license and business terms for an agreement are calculated based on the "Controlling License" (a linked license with the status of "Controlling") and any Current Amendments (Amendments on the Controlling License that have been given the Status (this agreement) of "Current" The terms of any current amendment will add to and (where necessary) override the terms stated in the underlying license. For a controlling license with a single current amendment:
Where there are multiple “current” amendments, the terms from the amend will be applied in order of the amendment start date. So in the case of licenses or amendments having different values for the same term, the value from the amendment with the most recent start date will be used as the correct value for that term in the agreement. |
E-resources covered by this agreement: Current / Future / Dropped / All | This field is only relevant and calculated when the agreement contains agreement lines based on resources in the Agreements internal knowledgebase. ... (work in progress!)... |
...
Describe and include any permanent links such as a link structure to records, searches, etc
Considerations for Implementation
...