<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:"Arial Narrow"}
@font-face
{font-family:Consolas}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
pre
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black}
span.Pr-formataoHTMLChar
{font-family:Consolas;
color:black}
span.EstiloDeEmail19
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.EstiloDeEmail21
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.TextodebaloChar
{font-family:"Tahoma","sans-serif";
color:black}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:70.85pt 3.0cm 70.85pt 3.0cm}
-->
</style><style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" lang="PT-BR" link="blue" vlink="purple" bgcolor="white">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi,<br>
<br>
as we are testing ISIS-OAI-Provider (for a new ABCD-release) we stumbled over the following problem : when using a non-standard wxis (e.g. BigISIS or FFI), adding this as the 'isis_key_length' in the oai-databases.php with the line :
<br>
isis_key_length=bi<br>
or<br>
isis_key_length=ffi<br>
and copying the BigISIS or FFI wxis.exe as resp. wxisbi.exe or wxisffi.exe in the oai-isis-provider cgi-bin folder (all this as per the instructions), the verbs work well, including the 'listrecords', but in that one we have the following special result :<br>
- the identifier is correctly read from the database-records (proving that the right wxisbi.exe or wxisffi.exe is used)<br>
- the metadata fields (taken from a file .i2x) however give the error : <br>
|fatal error|unavoidable|recread/check/base|<br>
which means that the wrong wxis was used, whereas it is supposed to be the same one as for the identifier-field (which worked well).<br>
Now, the difference is that, as I suppose (but a lot of documentation is still missing...) for the identifier-field the IsisScript 'getidentifiers.xis' is used and for the metadata the 'getrecord.xis' IsisScript. The difference is that in the first case no
isisxml is used and in the second case it is used.<br>
So my suspicion is for something to be wrong with the isisxml code and non-standard wxis. This is supported by another long-standing problem which we have reported on earlier without any reaction : also the XML-parser runs into empty output when calling non-standard
wxis from the BVS Site (whereas the same wxis.exe works very well when called directly in iAH with the same database). So I suppose this might be based on the same issue and a solution would therefore be even more welcome as it would solve two problems in
one catch.<br>
<br>
Thanks for your attention and hoping someone at BIREME/BVS can look into this,<br>
<br>
<div><br>
<div class="BodyFragment"><font size="2"><span style="font-size:10pt;">
<div>Egbert de Smet<br>
Universiteit Antwerpen </div>
</span></font></div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px"></div>
</div>
</body>
</html>