Steps to deploy new source content:

	1) Place the source files into the native-source folder
	2) Update the version number as appropriate in pom.xml
	3) Run a command like this to deploy - (vadev is a server name that must be defined with credentials in your maven configuration):
	
		mvn clean deploy -DaltDeploymentRepository=vadev::default::http://vadev.mantech.com:8081/nexus/content/repositories/termdata/
		
Note - new source content should not be checked into GIT.  When finished, simply empty the native-source folder.

For LOINC since loader 5.3, we require 3 files:
1) LOINC_2.54_MULTI-AXIAL_HIERARCHY.zip
2) LOINC_2.54_Text.zip  
3) (optional) LOINC_ReleaseNotes.txt


For LOINC since Loader 2.7 (till 5.3), we expect the csv distribution.  We require 5 files, in this case:
	1) loinc.csv
	2) map_to.csv
	3) source_organization.csv
	4) LOINC_V244_MULTI-AXIAL_HIERARCHY.CSV
	5) loinc_releasenotes.txt
	
For older versions of LOINC that predate the CSV distribution, the loader currently expects two files 
	1) - LOINCDB.TXT
	2) - LOINC_V240_MULTI_AXIAL_HIERARCHY.CSV


Each of these files should exist in the root of the native-source folder.
	
The version number in the multi-axial file can vary.
Note - Loinc also requires a classMappings file - which is part of the loinc-mojo project.  A new file should be generated 
when new data is downloaded (it comes from a non-computable PDF file).  See loinc-mojo\src\main\resources\classMappings-....
	
