Known Issues
- Accessing JSON content using Firefox
- Accessing JSON content using Internet Explorer
- Accessing SKOS content using Internet Explorer
- Diacritic searching using the SRW/U interface
- Handling of the HTTP Accept header using the REST interface
- Handling of the HTTP Content-Location header using the REST interface
- Retrieving MARC (ISO 2709) content using the SRW/U interface
- Retrieving JSON content using the SRW/U interface
- Accessing JSON content using Firefox
-
When accessing JSON content using Firefox you will be presented with a dialog box to download the content to your computer. Firefox presents the dialog box because it does not recognize the MIME type, e.g., application/json. You can download the MIME Edit Firefox extension to open JSON content in the application of your choice.
- Accessing JSON content using Internet Explorer
-
When accessing JSON content using Internet Explorer you will be presented with a dialog box to download the content to your computer. Internet Explorer presents the dialog box because it does not recognize the MIME type, e.g., application/json. Internet Explorer can support additional MIME types by modifying the Windows registry. For a discussion on how Internet Explorer handles MIME types, see the following articles on MSDN:
A sample registry extension document that could be merged into the Windows registry would look like:
Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/json] "CLSID"="{25336920-03F9-11cf-8FD0-00AA00686F13}" "Encoding"=hex:08,00,00,00 - Accessing SKOS content using Internet Explorer
-
When accessing SKOS content in Internet Explorer you will be presented with a dialog box to download the content to your computer. The reason why Internet Explorer presents the dialog box is because it does not recognize the MIME type, e.g., application/rdf+xml. Internet Explorer can support additional MIME types by modifying the Windows registry. For a discussion on how Internet Explorer handles MIME types, see the following articles on MSDN:
A sample registry extension document that could be merged into the Windows registry would look like:
Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/rdf+xml] "CLSID"="{48123BC4-99D9-11D1-A6B3-00C04FD91555}" "Encoding"=hex:08,00,00,00 - Diacritic searching using the SRW/U interface
-
Searching for terms with the SRW/U interface that contain diacritics will return no hits. Examples demonstrating this issue can be found when searching for the following terms in the preferredTerm index:
- GSAFD: "Romans à clef"
- FAST: "Rāmacandran"
The suggested work around is to remove any diacritic marks before attempting to search.
- Handling of the HTTP Accept header using the REST interface
-
The REST interface does not properly handle the HTTP Accept header when multiple content types are specified or the content types have a quality associated with them. The suggested workaround is to specify the specific content type you want to retrieve in the Accept header when dereferencing a generic resource URI.
- Handling of the HTTP Content-Location header using the REST interface
-
The REST interface does not properly generate the URI found in the HTTP Content-Location header to accurately reflect the vocabulary or concept identifier accessed.
- Retrieving MARC (ISO 2709) content using the SRW/U interface
-
The SRW/U interface does not allow you to retrieve content using the MARC (ISO 2709) schema. This is a limitation of the SRW/U server that the Terminology Web Service project is using. The suggested workaround is to access the content through the REST interface.
- Retrieving JSON content using the SRW/U interface
-
The SRW/U interface does not allow you to retrieve content using the JSON schema. This is a limitation of the SRW/U server that the Terminology Web Service project is using. The suggested workaround is to access the content through the REST interface.
