...
Integrating Mummi Thorisson's Ruby-based CrossRef lookup tool for searching and loading publications into VIVO, on GitHub along with OAuth work for retrieving information from a VIVO profile in another application- Improving and documenting the Harvester scoring and matching functions
Stephen is already working on updating the Harvester documents in general – not sure how much far into the scoring and matching documentation he will get
- Look for a poster by Joe McEnerney detailing a worked ingest example
| Anchor | ||||
|---|---|---|---|---|
|
Also referred to and documented as Multiple Language Support in VIVO
- Moving We are moving text strings from controllers and templates to Java resource bundles so that other languages can be substituted for English
- Internationalization We will support internationalization for ontology labels – important because much of the text on a VIVO page comes directly from the ontology
- We are translating text in JavaScript and in properties files
- There are many places to track down in page management, the index page controller, etc., but that process is going well
- The Site Admin page will be translatable
- but JSP pages left in the back end editing and supporting some ingest functions will not be translated, in part because we need to consider whether to put any available effort into moving them to FreeMarker as a higher priority, or perhaps at the same time as a way to kill two birds with one stone
Improving the VIVO editing interface(s) to support specification of language tags
- VIVO 1Improving the VIVO editing interface(s) to support specification of language tags. VIVO 1.5 will respect a user's browser language preference setting and filter labels and data property text strings to only display values matching that language setting whenever versions in multiple languages are available – but there has not yet been a way to specify language tags on text strings.s browser language preference setting and filter labels and data property text strings to only display values matching that language setting whenever versions in multiple languages are available – but there has not yet been a way to specify language tags on text strings.
- This affects the default data property editing form, editing multiple rdfs:labels, and any custom forms that add
- we need to design the UI
- if the editing user has Spanish as the preferred language, do you assume all text entered is in Spanish?
- if more than one version of a string or label is present in the data, do you offer both for editing?
- do we need a batch process to convert existing data to add language tags based on what is stated to be the default language of that VIVO installation?
- we need to design the UI
| Anchor | ||||
|---|---|---|---|---|
|
...