|
(on the assumption, that we will have a JSON schema which can map one-to-many license terms)
I have tried to use the current (Daisy) agreement export to create items in GBV union catalogue, and from the obvious gaps I hope we will get a fair idea how "full Agreement export" could look like.
- License Terms: Term->Value, visibility, public note (internal note = optional: we use it to copy relevant parts from the legal text for easy reference, but you may not want to show this to the public)
- Organisation ID of the tenant/library to which the data pertains (current Agreement export has no information about the tenant. If you want to batch process exports for multiple tenants by 3rd party, e.g. VZG, you must be able to map to the user in the target database).
- ID and roles of the organisations involved (may not be the same as provided by package/platform, eg. consortium vs. publisher)
- Agreement ID (not package ID) is needed to bullet proof identify existing items for update
- AgreementStartDate/AgreementEndDate (e.g. if you want hide/unhide agreements Jan 1st)
- Do titles inside an agreement still have an individual ID (TIPP in GOKb?). These IDs would have more potential use then the redundant IDs for identifier namespaces in the current agreement export.
I have attached a "full" export in XML from a legacy KBplus subscription which worked fine for our needs.
|