Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Location and Item Status Not Translated from Codes to Text

    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    In the Primo English language Locations tab, I can see location, item type and item status translated to text.
    However, in Portuguese, the same information is displayed as the code, not as the text.

    The question to ask here is: “What TRN files are used by the DLF queries?
    The answer can be found in KB # 29549:
    . . .
    “The API response may be altered using trn and tag files.“
    KB # 29899 indicates that these files are now located in the aleph/dlf_<lng> directory on the a-tree.

    These are the relevant trn (translation) files:

    Looking at your Aleph server, we see no localization (u-tree/alephe_root) for dlf_por:

    Also, in the generic setup (a-tree/aleph_root), we see that there is no dlf_por localization.

    Note that global settings should appear in dlf-global.trn. For example, this is the dlf-global.trn line that translates the z30-item-status.
    z30-item-status ITEM-STA S z30-sub-library z30-item-process-status

    Please add dlf_por trn files to $alephe_root and test again (it recommended to add this directory in the u-tree/alephe_root, not in the a-tree/aleph_root).

    If all the other standard language setup is in place, the act of creating dlf_por should resolve this problem (you may need to force a web page reload, for example, in IE CTRL-F5 in order to see the change in the dlf response via the browser, but the change should be immediately apparent via a dlf command in the server , for example:

    >> wget -O test "http://yourserver:1891/rest-dlf/record/ABC01001190602/items?noItems=100?=por&view=full" ; ; cat test | xmllint --format - | grep z30-item-status | grep -v code

    • Article last edited: 10/8/2013