-
Notifications
You must be signed in to change notification settings - Fork 4
Using the Library
Chuck May edited this page Mar 20, 2015
·
9 revisions
Everything starts with getting an instance of the Staging
object. There are DataProvider
objects for each staging algorithm and version. The Staging
object is thread safe and cached so subsequent calls to Staging.getInstance()
will return the same object.
For example, to get an instance of the Collaborative Staging algorithm
Staging.getInstance(CsDataProvider.getInstance(CsVersion.v020550));
The staging entity supports the following APIs:
API | Description |
---|---|
findMatchingTableRow | For a given table, return the index of the row that matches the key/value combination |
getInputs | Looks at all tables involved in the mapping and returns a list of input keys that may be used during staging |
getInvolvedSchemas | Return a list of schema identifiers which the specified table is used in |
getInvolvedTables | Return a list of tables identifiers involved in the specified schema |
getOutputs | Looks at all tables involved in the mapping and returns a list of output keys that may be created during staging |
getSchema | Return a schema based on schema identifier |
getSchemaIds | Return the complete list a schema identifiers |
getTable | Return a table based on table identifier |
getTableIds | Return the complete list of table identifiers |
isCodeValid | Return true if the passed field and value are valid in the specified schema |
isValidHistology | Return true if the histology is valid |
isValidSite | Return true if the primary site is valid |
lookupSchema | Look up a schema based on a set of inputs |
stage | Stage a case |
Supported Algorithms
Getting Started
API Documentation
- findMatchingTableRow
- getInputs
- getInvolvedSchemas
- getInvolvedTables
- getOutputs
- getSchema
- getSchemaIds
- getTable
- getTableIds
- isCodeValid
- isValidHistology
- isValidSite
- lookupSchema
- stage
Technical Specifications