https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17785
--- Comment #13 from Pablo AB <[email protected]> --- I found this issues: a. "FAIL baseURL supplied [...]" from openarchives.org validation site b. "FAIL Bad earliestDatestamp [...]" c. validator.oaipmh.com warning about Content-Type d. Koha XML output doesn't validate against OAI-PMH XML schema. (In reply to Tomás Cohen Arazi from comment #11) > (a) Our fix for the XSLT masked the underlying bug (our code doesn't know > about the proxypass we do, and then Plack answers what he knows, > /opac/oai.pl). So this bug should be reopened? bibkat.no doesn't fail beacause it doesn't use Plack? To test I found this command useful: curl -s "https://sites/cgi-bin/koha/oai.pl?verb=Identify"; | xmllint --format - | grep baseURL > (b) earliestDatestamp is read directly from the DB and not formatted as > rfc3339 as it should). (b) responseDate is well formed, earliestDatestamp is not. From XSD: "Tightened definition of UTCdatetimeType to enforce the restriction to UTC Z notation." responseDate and expirationDate should be YYYY-MM-DDThh:mm:ssZ https://www.openarchives.org/OAI/openarchivesprotocol.html#DatestampsResponses So Koha should convert to this format what it gets from the DB. (In reply to Tomás Cohen Arazi from comment #12) > According to my interpretation of the spec, the test is not correct: > https://www.openarchives.org/OAI/openarchivesprotocol.html#HTTPResponseFormat (c) You are right, seems a problem of that validator. I'll contact site creator (Vangelis Banos). Also acording to RFC7303 (9.2) which obsoletes RFC3023 (3). On websites returning text/html validator.oaipmh.com oddly say they return a correct text/xml. This problem is very common. A FOAF tested al the URLs from http://opendoar.org/OAIbaseURLs.php and get 575 text/xml 468 text/html 307 application/xml (d) Koha XML sometimes invalid, tested with: wget -q "https://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"; wget -q "https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=ListSets"; -O test.xml xmllint --noout --schema OAI-PMH.xsd test.xml - When no set is defined Koha incorrectly output <ListSets/>. A set (child element of ListSets) should always be there, minOccurs default value is 1. Otherwhise should be: <error code="noSetHierarchy">No sets defined</error>, AFAIK even if tehere is no error. - setDescription is not a string, is descriptionType ##other, "defined by a community" (?) https://www.w3.org/TR/xmlschema-0/#ref34 https://www.w3.org/2005/07/xml-schema-patterns.html https://www.openarchives.org/OAI/2.0/guidelines-repository.htm#setDescription https://www.openarchives.org/OAI/openarchivesprotocol.html#Set and 4.6 ListSets > Examples -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
