Dear developers,
Recently, I intended to add my repository to various registries such as OpenAIRE, Baase Search, OpenArchives, and others. However, it has come to my attention that the validation tests performed by these registries reveal critical errors in the OAI interface of Tainacan, rendering it currently unsuitable for integration with the mentioned registries. The technical support team at OpenAIRE has assisted in identifying these issues.
- baseURL supplied https://files.fti.dp.ua/wp-json/tainacan/v2/oai does not match the baseURL in the Identify response https://files.fti.dp.uawp-json/tainacan/v2/oai/. The baseURL you enter must EXACTLY match the baseURL returned in the Identify response. It must match in case (http://Wibble.org/ does not match http://wibble.org/) and include any trailing slashes etc. Also missing “/” before wp-json, and unnecessary “/” after oai
- Lists of metadata critical error: https://files.fti.dp.ua/wp-json/tainacan/v2/oai?verb=GetRecord&metadataPrefix=oai_dc&identifier=ListMetadataFormats@https://files.fti.dp.ua/wp-json/tainacan/v2/oai
- List sets critical error: https://files.fti.dp.ua/wp-json/tainacan/v2/oai?verb=GetRecord&metadataPrefix=oai_dc&identifier=ListSets@https://files.fti.dp.ua/wp-json/tainacan/v2/oai
Furthermore,
- When I use taxonomies for specific Dublin Core metadata, these metadata fields remain empty during the data element structure check through the OAI interface: https://files.fti.dp.ua/wp-json/tainacan/v2/oai?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:files.fti.dp.ua:[item-ID]
Additionally,
- The functionality to add and map additional DC metadata is not working at either the repository or individual collection level. The ability to add and map new metadata elements will enable better integration and compatibility with registries.
I would greatly appreciate it if you could address these issues as soon as possible.
Thank you for your prompt attention to this matter.
Sincerely,
Yurii