You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a new library that is using Alma for the digital collections. Their OAI is only available to approved IP addresses. Our DL IP addresses are on the list, but if you need to see the OAI in the browser I will need to give them your IP address.
The qdc importer recognizes the OAI and finds the set name (ATLA) but does not import anything. I think it is not recognizing the fields.
Comparing their OAI to a CONTENTdm OAI that I can import from, the difference is they are using alma schemas and CONTENTdm uses worldcat. And they have oai_qdc:dc where CONTENTdm has oai_qdc:qualifieddc
We have a new library that is using Alma for the digital collections. Their OAI is only available to approved IP addresses. Our DL IP addresses are on the list, but if you need to see the OAI in the browser I will need to give them your IP address.
The qdc importer recognizes the OAI and finds the set name (ATLA) but does not import anything. I think it is not recognizing the fields.
The base URL is https://julac-hkbu.alma.exlibrisgroup.com/view/oai/852JULAC_HKBU/request
Comparing their OAI to a CONTENTdm OAI that I can import from, the difference is they are using alma schemas and CONTENTdm uses worldcat. And they have oai_qdc:dc where CONTENTdm has oai_qdc:qualifieddc
Adding XML file of the OAI to slack https://assaydepot.slack.com/files/U034217KP3L/F07009REGCQ/hongkong.xml
The text was updated successfully, but these errors were encountered: