Peter
lmtoconnor
I’ve been using ARBIL to add a Spanish title translation and Spanish description field to every IMDI file in my corpus and am in general thrilled with the fact that I could transform my entire corpus in a few days’ time. Bravo!
I have experienced a problem in the process of exporting from ARBIL and then uploading to LAMUS. If I merely click on the highest node name in ARBIL as the export and then click on that same highest node name for the upload to LAMUS, in LAMUS I can only see this node at the Corpus level. No detail. This means I cannot replace IMDI files to individual sessions. It seems a Submit and subsequent New Workspace in LAMUS will “solve” the problem. This was my process:
- shake my fist at the uncooperative Corpus node, Save and Logout from LAMUS
- modify another node in ARBIL, export at highest-node level
- select existing workspace in LAMUS, upload this second set from ARBIL at the subnode level. Unlinked files showed all sessions for this second set plus the Corpus node from the previous upload.
- replace the IMDI files for the second set, then Submit workspace in LAMUS
- open a new workspace in LAMUS – and bingo. In the Unlinked Files workspace, the uncooperative Corpus node was gone, with all the individual sessions in view. I replaced all the IMDI files.
This would seem to be a problem in the cooperation between the two programs, more than a problem specific to ARBIL, but it certainly cost me some extra time this week.
Loretta