Page History

...

In theory the developer could at this point implement only doLoad () by mapping content to a coding scheme object and persisting it before turning control over to BaseLoader which will call this the doLoad method and set default load options in its load method.  The other option is to implement doLoad and override the load method which sets up end user option choices for the loader.   Most loaders implement the load method, customizing load options to provide to the end user.  In the case of the MedDRA loader, a CUI load option is provided to the end user.

Beyond these methods, where a coding scheme object is passed to LexEVS, the structuring of the loader. code is largely and necessarily left up to the developer.  However a few common patterns are fairly consistent in this implementation.  Generally speaking, there is a central mapping where the coding scheme object is built.  Other classes, when necessary, are supportive to this central class. 

These classes are generally classified by those that are responsible for either reading a source file or accessing an API that reads the file for you and those that map objects created from that file into LexEVS coding scheme metadata, entity and relationship objects.  A third category will include accessing LexEVS persistence mechanisms and passing these values to the database.