Hi ozp,
This is often because of character encoding problems. OJS 1.x used ISO8859-1 by default for character encodings; character set conversion code exists in OJS 1.x's OAI feed software to provide standard UTF8-encoded output, but there are often problems with character set conversions.
You can check whether a problem exists at the data source end by using tools like "wget" and "xmllint"; for example, you can often fetch a bunch of records from an OAI data source using:
- Code: Select all
wget -O tmp.xml "http://url-to-oai-data-source?metadataPrefix=oai_dc&verb=ListRecords
Then, check the XML using:
- Code: Select all
xmllint --noout tmp.xml
Often the XML will not validate properly due to invalid character sets -- this confirms that the problem is the data source.
As for the reading tools -- this is a sidebar allowing users to interact with other resources such as search engines and dictionaries. When enabled, a sidebar will appear when viewing a record. There is a different set of reading tools available for each discipline included (e.g. Social Sciences) or you can customize your own.
Regards,
Alec Smecher
Public Knowledge Project Team
---
Don't miss the First International PKP Scholarly Publishing Conference
July 11 - 13, 2007, Vancouver, BC, Canada
http://ocs.sfu.ca/pkp2007/