|
From: Chalk, S. <sc...@un...> - 2006-03-21 00:47:33
|
At last weeks PittCon working group meeting, suggestions were made regarding the converter and I have addressed those in an update today. You will find example files for download on the converter page (fad.coas.unf.edu/animl/jcampconversion.php). These are 2D data files only. In addition, I have increased the upload file size and changed the error message (sorry Maren). Through putting this converter together I have come across some issues that need to be thought about on this list. I reported some of them at the meeting last week but have thought of some more so I have summarized them below. 1) How does any converter appropriately identify that it did the conversion? Do we need a "Conversion" Action in the AuditTrail? 2) Where should any JCAMP comments be put in the AniML file? 3) Instrument Vendor specific parameters should go where? (until the vendors add their module) 4) If a piece of header information has no obvious place to go in the AnIML file where should it be put? (or does this suggest a change in the ATID is needed?) 5) If a value is required in an AnIML document but is not available in the JCAMP file (or any other source file/datasystem) what should be put there? Default value? No value (empty element)? 6) To go along with 5)...if a required field is defined with enum list what should be chosen if there is no data available? Add an "Unknown" enum value to each such list? Sorry for so much detail, but I got stimulated at PittCon ;) Stuart Chalk |