
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
In order to promulgate blacklight's stellar handling of non-latin text, the demo app should leverage the non-latin text in the demo data.
1. Non-latin should be displayed (search results and show view)
2. vernacular should be a part of fielded searches
It doesn't seem worth it to change Matt's quicky ruby indexer.
The solrmarc indexer can do this handily, but hooking it up to blacklight is tricky (partly due to it being in java)
Erik said he could set up a way to do a test index with his ??streaming?? live update code ... perhaps that's the way to go?
This has been done:
vernacular searchable for all fields searches.
spelling suggestions cope w vernacular
|
|
Description
|
In order to promulgate blacklight's stellar handling of non-latin text, the demo app should leverage the non-latin text in the demo data.
1. Non-latin should be displayed (search results and show view)
2. vernacular should be a part of fielded searches
It doesn't seem worth it to change Matt's quicky ruby indexer.
The solrmarc indexer can do this handily, but hooking it up to blacklight is tricky (partly due to it being in java)
Erik said he could set up a way to do a test index with his ??streaming?? live update code ... perhaps that's the way to go?
This has been done:
vernacular searchable for all fields searches.
spelling suggestions cope w vernacular
|
Show » |
|