Page Comparison

Suggestions SLUB:

(1) Cost per download/search per

agreement (=> TR_J1;

TR_B1; DR_D1)* +

 also relevant for UBL

(2) Searches/Download price development per agreement over several (last 5)

years (=> TR_J1;

TR_B1; DR_D1)* + also relevant for UBL * ... Counter Reports (Counter_5), used in the SLUB

1&2 are very similar, difference: 1 for the current year, 2 for the develpoment over some year

(3) Comparison of the use/download of the current year vs. archive years for/by the last ten publishing

years (TR_J4)* + also relevant for UBL

Question: frontfile & backfile may be purchased separately and then may be handeled by different agreements.

Axel: Statistics server only used JR 5 (R4) for cost per use statistics, difficult to decide. National licenses in Germany often cover backfiles with moving walls (they don’t have to be paid by the institution), those backfiles should not be considered in cost per use statistics. 

Nicole Hügel: Sometimes the titles are still included in the agreement and have to be paid for nonetheless

Helge: Matter of perspective: Interested in agreement/what you pay for it vs. Interested in specific title, as it appears across multiple agreements/vendors

Jessica: Also consider Open Access usage, use J3 reports

(4) Downloads (total item requests) by month ; downloads (unique item requests) by month ; searches by

month (=> TR_J1; TR_B1; DR_D1)* + also relevant for UBL

Nicole Hügel: Which metric should be used, unique or total item requests? SLUB and Leipzig use total item requests and the moment, to be able to compare to Counter 4.

Helge: Ideally, both should be available and the user should be able to choose.

Kristen: There can be a difference between download and visualization of reports. Download can be much richer, for different use-cases.

(5) Percentage of titles without usage in an agreement, dispersion of usage over all titles (with several limiting values);

configurable + also relevant for UBL

* ... Counter Reports (Counter_5), used in the SLUB

Kristen: Question about differences between resource types, there are different reports for ebooks, journals, data bases - are there agreements that have mixed resource types?

Helge: Where do the holding information come from? One or several lists?

Kristen: Current plan is agreement lines. Take a look at Folio at the end of the call.

Suggestions UBL:

Please see above +

(6) Cumulative access per journal/title and time in an agreement (=> TR_J1;

TR_B1; DR_D1)

Martin: Should be covered by other reports above.

(7) Special cases, f.e.: Nature journals: one agreement, but the individual journals still have prices and can be canceled and ordered, unlike many other packages. So in this case a report, that

shows the costs / benefits per agreement and per title

would be useful.

Kristen: We should be able to cover all of those reports, as they seem to rely on similar data. Are there other requirements

Jessica: IR-M1 (?) streaming video usage would be helpful as well.

Helge: Relys on two sets of data: Holdings contained in agreement and usage data.
It might be neccessary to include external data (what school has paid for it, …). Data might be contained in Folio.
Kristen: We have connectzion between agreement line and POL, so order might e source. Are there other places in Folio with data that should be accessed?

Helge: Is it possible to add tags to an individual journal?

Axel: Is eholdings app scope of project? Eholdings data is hard to extract (problem for LDP as well).

Kristen: We will definetely supoort the internal KB (at the moment GOKB), and try to make this available for all knowledge bases, but it might be a question of capacity for eholdings at some point. EBSCO is also working at an integration of their usage consolidation service to Folio at the moment. 

Potential new backend module could be able to provide data to the LDP.

Agreements app

Agreement lines show the content covered by the agreement. They link to resources from a knowledge base, theses can be packages or single titles.

• Kristen: The agreement lines might be a mix of resource types, a question will be how to handle that in reporting

Link from Agreement line to Purchase order line

Click on a title opens the title view, a title might be part of none, one or several agreements. Information on different ways to purchase the title

• Kristen: In this view we might display usage data on title level, agreement independent.

Agreements app: Usage data accordion > link to eUsage app, where harvesting can be configured and reporst an be downloaded.

• Kristen: Connection between agreement and usage data provider makes sure to pull in the right data from the correct platform/vendor when reporting from agreement perspective

The usage data accordion (or an additional one) will be the place to view statics and visualizations from the agreement record

We will start prototyping reports and visualizations.

Maybe next week a first report prototype will be ready to talk through.