Point taken about IVAC ... Confusion. But (as I say) it's a design choice.
Personally, I think I would shy away from codes (for the manufacturer
etc.) - I have had a lifetime of that! I believe I would just stick with directory folders named Alaris, Eschmann, IVAC
et al simply following what was written on the kit itself. And then hope for the best! After all, someone with "dominant" powers (as you put it) could always come along and tidy things up later.
Also about the power of the search facilities. Although it seems that you need to be on line to gain full use of those. Maybe you could have it (optionally) search the current hard-drive and (or) network as well. Or indeed any other source available to the native machine:- memory stick, USB link to another machine (via software "by others"), a
Wi-Fi or
Bluetooth link ... or any other means (just as long as the PC can "see it").
Meanwhile, maybe you need to say a few things about file naming conventions. For instance, every model folder likes to have a Folder.jpg file (for the "picture") ... and it looks like the service manual .pdf needs to be (re)named Service.pdf in order for it to appear in the correct panel (window). Similarly with Operators.pdf and Results.xls. And Spares.xls
etc. Am I right?
I'm interested in the ID_xxxxxx.txt business, by the way. What is the "spec" - format - for that? I'm guessing it can just provide a pointer indicating model (type \ manufacturer \ model) only, but not for each of the (what could be many) individual items of equipment within that sub-set. And ... how does (can) it link to a database, I wonder? More information, please!
A configurable folder browser? Anyone else remember (amongst others) PC-Tools?
