Here is a list of additions, changes, and bug fixes the come with the release of Arbil 2.5. You can get the new version from the Arbil tool page.
1) The favorites can now be imported and/or exported via the option Import/Export favorites included in the right click menu of the Favorites tab. In addition, the favorites are now grouped by types so that, for example, all the actors dragged to the Favorites tab will be grouped under Actors(…). For more information on the functions related to the favorites have a look at section 3.5 in the Arbil IMDI manual, and section 3.4 in the Arbil CMDI manual.
2) The typechecking of a resource can now be “forced” manually through the option Force typechecking included in the context menu that appears when right-clicking a resource.
3) Nodes and fields can be deleted – when allowed by IMDI or CMDI – both from a single-instance table and from a several-instance table. In both cases you have to select the node/field, right click on it and select either the option Delete 1 field(s) “…” (single-instance table) or Delete field from all nodes (several-instance table). For more information, please refer to section 4.7 in the Arbil IMDI manual, and section 5.4 in the Arbil CMDI manual.
4) A View menu has been added to the menu bar. Through this menu you can change the font size, and also decide whether or not to see the selection preview table, that is the metadata table appearing at the top of the application page every time you select a node.
5) (For CMDI documents only) The Options menu now includes the option Show verbatim XML structure in tree for CMDI, which allows you to see the original structure of the CMDI files contained in the tree.
6) The option Add to Tree Root has been added to the context menu of the remote corpus. It will turn out useful whenever you have to work on a node located at a very low level of the tree. When selected it will create a copy of the node and place it either at the very beginning or at the very end of the remote corpus tree, i.e. in a more visible position. For more information, please refer to section 3.2.2 in the Arbil IMDI manual, and section 3.1.3 in the Arbil CMDI manual.
7) The CMDI profiles are no longer downloaded automatically with the profile list. You have to first select them if you want them to be downloaded. Alternatively, if you want all the profiles, you can use the option Download all from the Templates & Profiles panel (opened via the Options menu). Moreover, when you add a profile manually, you will see its full name displayed in the profile list, and not the name that derives from the schema location.
8) Your Local Corpus is stored in a storage directory. When you pass from one version of the application to another it can happen that more than one storage directory are selected. If this is the case, you will be notified through a warning message.
9) With regards to editing the metadata, you can now add new text to the existing one without replacing the latter. If you double click on the field you want to edit, or you select the field and press F2, the mouse cursor will be automatically placed after the last word of the already present string of text.
10) Language selection: Every time you add a new language to the IMDI language list, this will be automatically updated.
11) Arbil is now available also in German, Italian and Spanish. You will be asked to select you preferred language as soon as you run the application for the first time. However, you will always be able to change it via the option Select language in the Help menu.
12) When performing a node search, the search results that exactly match the search term(s) entered will get highlighted. In addition, if you get only one result from the search, this will be displayed as a single-row table, and not as a vertical table.
13) If during the import/export of metadata these will overwrite an already existing copy or file, you will get a message asking you whether you want to overwrite such matching files.
14) The log console has been made more configurable (see section 10.5 in the Arbil IMDI manual and section 10.4 in Arbil CMDI manual). The output of the console is now divided into different layers, which display different information depending on which one is selected (ALL, FINE, INFO, WARNING, SEVERE). The log console is opened via the Help menu.
15) Previously Arbil considered all XML files as CMDI files, and consequently it tried to process them, slowing everything down. Now it does not do this anymore, which means you can import corpora containing XML files keeping the import process reasonably fast.
16) Missing field descriptions have been added for a large number of field descriptions.
Known issues: the following points will be addressed in the future versions of Arbil.
17) The loading of the remote corpus nodes is momentarily very slow. This issue occurs, for example, when loading the remote tree for the first time, or when you select the option Show verbatim XML structure in tree for CMDI described in point 5 above.
18) The resources that are protected and therefore require authentication cannot be imported into the local corpus because the authentication mechanism does not allow this.
19) When showing IMDI metadata files in the form of IMDI formatted (option accessible via the local corpus nodes context menu), the formatting does not look as expected.
20) There is a problem with the Find and replace option, but it is only Windows- and Linux-related. The layout of the input boxes (i.e. the one used to define the term you intend to find and the one used to define the term to be replaced with) sometimes breaks in the two operating systems mentioned above.
21) The search interface for the remote search is not very intuitive. At the moment remote search requires two steps: first remote searching and then local filtering.