2024-04-17 Meeting notes

Demo on how Agreements Local KB is used in practice

@Sabrina Bayer

Slides

• University Library Regensburg

• will use GOKb as external data source

• THWS is first implementer library - started last autumn

• University Library Regensburg and TU Munich started in March 2024 with Poppy, waiting for Patch

• ebook package

  • 1 agreement for an ebook package

  • AGLs for each year

  • each AGL linked to single package

• Pick & Choose

  • 1 agreement for a P&C package

  • AGLs for each title or P&C package

  • P&C packages are local package with purchased titles from a platform

• ebooks: single purchase

  • one agreement for each platform

• eJournal packages

  • 1 agreement for an ejournal package

• eJournal single titles

  • agreement for each title or agreement for each publisher

• Databases: with fulltexts

  • 1 agreement for each database

  • AGLs for all packages contained

• databases without fulltexts

  • 1 agreement for database

  • AGLs linked to package in local KB

Additional fields on AGLs are used if packages are not in local KB

Suppl. properties: DBIS-ID (perhaps better in GOKB)

Dataflows

Already working: EZB > GOKb > FOLIO internal KB

Next steps

• FOLIO > EZB

• FOLIO > DBIS

• FOLIO > Union Catalogue

• FOLIO > ZDB

• Future: FOLIO ERM > Linking Server

Questions:

Are those P&C packages local ones?

Yes

Re. single subscriptions: Have you considered to create one GOKb package per publisher, e.g. a T&F package that contains your single subscriptions and link this package as AGRLine to the T&G agreement?

is possible, but not yet decided

different ways will work differently

Felix' suggestion will work best if there is one order, e.g. a package order

in eholdings subgroup there was a long discussion on individual ebook purchases being managed to Inventory and wanting to see this linked up to agreements

Are you storing the number of concurrent users in the license record as well?

Owen: That would only work if all the resources in the agreement have the same number - not where you can purchase different numbers for each single book etc.

Felix: Hey Owen, the same is true if you store the number in the AGR note field, if you have multiple resources linked as AGRLines. But maybe the numbers are stored in the AGRLine note, let's see what Sabrina has to say ;)

Owen: If the journal single titles from a publisher are covered by a single license, I would say having single agreement per publisher makes sense.

Sabrina: different libraries are reponsible for different agreements, with one license

Felix: It can be tedious to create many many AGRLines, one for each title. That's just one of our lessons learned.

Owen: True. This could be automated if you have someone able to work with the APIs/Postman

Felix: We've 'automated' it by creating one KBART file and upload it into GOKb. Then it's only one action to link this package as AGRLine.

and are you storing the Information wether the licences can possibly being upgraded?

No

sometimes it is important for acquisitions to upgrade concurrent users; if there are not sufficient

Would be true for particular titles

Helge: conditions change frequently, will be updated

fi data was given to GOKb at same time as package data it would be more up to date > maybe GOKb would be a better place (sync to FOLIO or point to publisher side)

Karina: would be difficult to keep up to date

Felix in chat: Isn't GOKb mainly about access, not acquisition?

Agreed. But if it is true for everyone, it could be part of GOKB

Martina: there is the option to add concurrent users in orders in POL

Owen could be added in when linking from AGL to POL

Subgroup likes the idea of displaying # of concurrent users in Agreements

Sometimes there are DRMs > further limitations would need to be recorded > we would need a field on POL

DRMs should rather be recorded in ERM

Upgrade options

Karina: should be on AGL

I can see a list of things that we need to capture here where the options need to be stored somewhere: Concurrent users (can do in Orders but not displayed in Agreements), DRM (no option to store right now as far as I know), Upgrade options

Helge: Concurrent users is just one parameter of DRM. Perhaps the most importatnt at the moment. But there may be others.

Look at having fields at AGL level to define number of concurrent users or using suppl. properties

look at other related needs

look at recording DRMs

Import only local packages for my institution/curator group in the Local KB

@Owen Stephens

Implementer topic ERM implementers

postponed

Implementer topic: Show the e-resources with their tags in the accordion element „E-Resources in package“ on package level

@Owen Stephens

Implementer topic ERM implementers

postponed