...
- The namespace in the input model of data to score. This allows different Score runs to be performed for different types of data, for example to score authors, publications, and journals separately.
The URI on which to compare an individual in the input model to an individual in VIVO. For example,
No Format http://xmlns.com/foaf/0.1/firstName
to compare authors by their first names.
- The algorithm with which to run the comparison. An algorithm takes two strings and returns a floating-point number between 0.0 and 1.0. A 0.0 indicates complete rejection, while a 1.0 indicates a complete match. For example, the equality test algorithm takes the two strings and determines whether they are precisely the same string. If so, it returns 1.0; if not, it returns 0.0. Other algorthmsalgorithms, such as Levenshtein differencedistance, perform a more thorough comparison of the strings and can return values in-between one and zero inclusively.
- The weight of the particular comparison. This is typically a number between 0.0 and 1.0 and is multiplied by the output of the algorithm to get the score value for that pair of items and that URI. A lower weight means that this particular comparison is less important than others for this run.
...
At this point Score is finished. All it does is generate these values. It is Match that determines what to do with them.
Arguments
Short Option | Long Option | Parameter Value Map | Description | Required |
---|---|---|---|---|
i | inputJena-config | CONFIG_FILE | inputJena JENA configuration filename | true |
I | inputOverride | override the JENA_PARAM of inputJena jena model config using VALUE | false | |
v | vivoJena-config | CONFIG_FILE | vivoJena JENA configuration filename | true |
V | vivoOverride | override the JENA_PARAM of vivoJena jena model config using VALUE | false | |
s | score-config | CONFIG_FILE | score data JENA configuration filename | true |
S | scoreOverride | override the JENA_PARAM of score jena model config using VALUE | false | |
t | tempJenaDir | DIRECTORY_PATH | directory to store temp jena model | false |
A | algorithms | for RUN_NAME, use this CLASS_NAME (must implement Algorithm) to evaluate matches | true | |
W | weights | for RUN_NAME, assign this weight (0,1) to the scores | true | |
F | inputJena-predicates | for RUN_NAME,match | true | |
P | vivoJena-predicates | for RUN_NAME, assign this weight (0,1) to the scores | true | |
n | namespace | SCORE_NAMESPACE | limit match Algorithm to only match rdf nodes in inputJena whose URI begin with SCORE_NAMESPACE | false |
Usage
Explanation
No Format |
---|
# Execute Score for Departments $Score $SCOREMODELS -n ${BASEURI}org/ -AdeptId=$EQTEST -WdeptId=1.0 -FdeptId=$UFDEPTID -PdeptId=$UFDEPTID |
...
- Create a vivoClone
- Create an inputClone
- Place both vivo and score into same dataset.
- Build the Query using buildSelectQuery
- Apply the query to the dataset.
- For every result:
- Build a score record.
- Build a fragment of the sparql SPARQL statement
- Send SPARQL fragments to loadRdfToScoreData