Changes between Version 4 and Version 5 of LEGACY - CaTissueBulkOperations

Timestamp:

11/29/10 11:48:54 (13 years ago)

Author:

jeff.lusted

Comment:

--

LEGACY - CaTissueBulkOperations

@@ -3 +3 @@
 These are very high level points. I'll expand upon them as I learn more. But feel free to add/make changes, please.
 
-It is my understanding that bulk operations can be invoked either from the caTissue web interface or from the command line. In both cases the invocation is just a trigger mechanism. A piece of caTissue functionality then picks up a local CSV file (a file with a list of comma separated values) that depicts all the changes you want to make; ie: these are the bulk part of the operation. There is another file in an XML format that in its entirety does three things:
+It is my understanding that bulk operations can be invoked either from the caTissue web interface or from the command line. In both cases the invocation is just a trigger mechanism. A piece of caTissue functionality then picks up a local CSV file (a file with a list of comma separated values) that depicts all the changes you want to make; ie: these are the bulk part of the operation. There is another file (the template file) in XML format that in its entirety does three things:
 
   * Describes the comma separated file
@@ -11 +11 @@
 Both files are sent to the caTissue application for processing.
 
-=== Mapping File ===
-This is my name for the XML file.
+=== Template File ===
   * Is there an XML schema file for this?
   * It seems to me (as per the client API) there is a heavy premium on knowing how the domain objects fit together.