ERM Sample Data

What kind of ERM data is needed?

• Organizations data

• Agreements data

• License data

Ideas for data:

• 3 fully connected Agreements

  • Connections to inventory (via POL), POLs, invoices, organizations, licenses, eUsage

  • Agreements would represent the following:

    • One with Agreement lines linked to EBSCO KB through eHoldings

    • One with Agreement lines linked to GOKb

    • One with unlinked Agreement lines

  • Review multiple supplementary properties

  • Sample licenses

    • We would need to check reference data to make sure licenses can be populated.

    • It’s good to have one term for each type (text, integer, pick list …) and with different visibility

Okay not to populate

• Dashboard (however there might be some sample data from a repository in UK)

• ERM Comparisons

Not sure whether we could populate eUsage Data, but it would be good to test cost-per-use

• ERM SIG would like to see eUsage data populated

• eUsage provider with necessary credentials

• Populate some reports

Some desire to test edge cases, e.g., large loads, not sure whether this would be feasible with Snapshot

Q&A

What test data is already available to populate any local test environments?

How is test data imported automatically at the moment?

Who will take care that test data is imported regularly and is available in FOLIO snapshot?

Connection to GOKb

• Is the data in there in a push method or a load method? We think it is a load method

• Can there be synchronized packages in Snapshot? Right now they are all “synchronizing,” and there are no e-resources.

If we created some data in FOLIO, could we export it via the API, store it in JSON, and then add it to the Github repository for loading when Snapshot is rebuilt?

Can we periodically review to keep sample data current and meeting needs?