Database content not discoverable in Primo.

We were expecting since full text is activated that meant our NZ collections should be discoverable in Primo. I understand that analysts will need to look at specific examples, but it seems this is not working as expected - at least not for all the collections. This means we will need to report issues as we find them.

My assumption is that we have to check that NZ collections are discoverable. Does Ex Libris have any instructions we can use to do this? With merged records and the use of metadata from different sources, I can see how this would be difficult to verify that a specific collection is discoverable or not.

Case #852010, 851956. etc.

Reported to Ex Libris. Narrowed the issue down to Databases. Testing out possible solutions.

Case #00850656, 00851297, 00851265,

Reported to Ex Libris. Developing instructions Slowly developing instructions to check for discoverabilty of NZ collections here.

Discussions can be found here.

Proxied OA collections

Reported issues with proxied OA Collections. Ex libris looking into it.

Case #852731, 851991, 850959, 850506, 850034, 847763, etc.

Reported to Ex Libris. They are looking into it.

Discussions can be found here.

Full Text Availability indication flag in brief record/No link in full record.

Reported issues with full text availability flag on brief results but no link in full record.

Case# 854035, 852793, 853274, 852728, 851265, etc

Reported to Ex Libris. No response from Ex Libris yet.

Discussions can be found here.