Title: Message Title
|
|
|
|
The reason why this is failing is because the OAI-PMH schema definition defines the description element to be processed strictly.
That means parsers should be able of getting (downloading) the XSD definition from the web, basically, what is missing is the xsi:schemaLocation attribute for the XOAIDescription schema.
The easiest way to fix this would be to set a default description to include this attribute. Of course, an alternative would be to change the description and use another schema.
Ivan
Your proposal seems to be a bit difficult to implement as descriptions in XOAI are static content. So, either (1) we change that and make it dynamically generated or (2) the end user would need to be made aware that a new configuration file needs to be changed, both solutions require extra work.
I would say to be pragmatic, fix this issue the easiest way possible, and create an issue (improvement) and make a proposal to change this.
|
|
|
|
|
|
|
Check the OAI-PMH endpoint with a validator (eg. http://oval.base-search.net/) it reports an error:
"ERROR: Identify response well-formed but invalid: Element '{http://www.lyncode.com/XOAIConfiguration}XOAIDescription': No matching global element declaration available, but demanded by the strict wildcard., line 11"
This is basically a configuration ...
|
|
|
|
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
