Versions Compared

Old Version 59

changes.mady.by.user Ivan Masár

Saved on

compared with

New Version 60

changes.mady.by.user Bram Luyten (Atmire)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: info on stop words configuration

...

  • Old JSP

    Code Block
    <p>Results <%= r.getFirst() %> to <%= r.getLast() %> of <%= r.getTotal() %></p>

  • New JSP

    Code Block
    <fmt:message key="jsp.search.results.text">
<fmt:param><%= r.getFirst() %></fmt:param>
<fmt:param><%= r.getLast() %></fmt:param>
<fmt:param><%= r.getTotal() %></fmt:param>
</fmt:message>

  • Messages.properties

    Code Block
    <p>jsp.search.results.text = Results \{0\}-\{1\} of \{2\}</p>

    (Note: JSTL 1.0 does not seem to allow JSP <%= %> expressions to be passed in as values of attribute in <fmt:param value=""/>)

Configuring stop words for search

The list of stop words is configured in DSAnalyzer.java. Like any other change in the DSpace source code, you are required to rebuild DSpace after modifying the list of stop words.

To Do

  • In the servlet code:
    • In `AuthorizeAdminServlet`, some English is passed for direct display in the title through the attribute `edit_title`. E.g. "Item".
  • `config/dstat.map`
  • Support for easy customisation of UI without needing to fork language bundles.
  • Display dates, numbers etc. according to Locale. (JSTL has tags for this)
  • Searching in non-Western languages such as Chinese; Lucene cannot parse/separate words
  • Multi-lingual metadata. Submission forms do not include language info for metadata. (The "language" DC field relates to the language of the content, i.e. the bitstreams.)
    • HPCLab, University of Patras, has submitted a new patch addressing this issue, against 1.4.2 (including the I18N patch) here. Please test and verify in order to remove from to-do.
  • Author and title ordering.
  • Browse controls ("Jump to" 0-9, A-Z) – support for other characters
  • Use of Collator fixes non-English language sort order problems. Not developed but small. No schema changes. JimDowning
  • i18n of non-Web UI – e.g. command line tools like the import/export tools. Currently the dictionaries are only stored in the .war file, so other parts of code won't have access to them.

...