EMBOSS Provenance Example
An e-scientist looks at a value within the myGrid information repository (MIR) and wonders:
- Where did this come from? (Do I really trust this data?)
If the same workflow was run at different times, the results may differ. For example,
EmbossProvenanceExampleResults
Example result
For example I look at the value
<get_outfileReturn xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xsd:string">Local: XLRHODOP_1_1 vs Consensus
Score: 408.33
XLRHODOP_1_1 1 MNGTEGPNFYVPMSNKTGVVRSPFDYPQYYLAEPWQYSALAAYMF 45
::||: :: :::: ::: : :::: : ::::::: : :: :
Consensus 82 FAGTKSLRTPANLLVLNLAFSDFCMMASMSPVMAINCFYGETWVL 126
XLRHODOP_1_1 46 LLILLGLPINFMTLFVTIQHKKLRTPLNYILLNLVFANHFMVLCG 90
: ::::: : ||::: : ::: : :|: : : | :
Consensus 127 GPLGCDIYAALGSLFGCVSIWSMCMIAFDRYNVIVKGINGTPLTI 171
XLRHODOP_1_1 91 FTVTMYTSMHGYFIFGQTGCYIEGFFATLGGEVALWSLVVLAVER 135
| | ::: :: |: |::::: :|: |:| : :: |
Consensus 172 KTAIMKILFIWMMAVFWTLMPLFGIWSRYVPEGNLTSCSIDYLTR 216
XLRHODOP_1_1 136 YMVVCKPMANFRFGENHAIMGVAFTWIMALSCAAPPLFGWSRYIP 180
::: : :::: :: ::: : ::| :: : |::
Consensus 217 DWNPRSYLITYFLFVYFFPLFIICYSYWFIIAAVAAHEKAMRDQA 261
XLRHODOP_1_1 181 EGMQCSCGVDYYTLKPEVNNESFVIYMFIVHFTIPLIVIFFCYGR 225
| : : : :: : : :::: : :: :::
Consensus 262 KKMNVKSLRSNEDQCAQSAEIRLAKVALTTISLWFMAWTPYAIIA 306
XLRHODOP_1_1 226 LLCTVKEAAAQQQESATTQKAEKEVTRMVVIMVVFFLICWVPYAY 270
::::: : | : : :::: ::| :: |
Consensus 307 YFGLFGIDGALTPLTTIWGALFAKASSCYNPIVYAISHPKYRAAL 351
XLRHODOP_1_1 271 VAFYIFTHQGSNFGPVFMTVPAFFAKSSAIYNPVIYIVLNKQFRN 315
: :::|:: | : :: : | : :::::: ::::
Consensus 352 KEKCPMCVCGETDEPSPDAPQSDATTTSEAASKAPAAIEFPDDNI 396
XLRHODOP_1_1 316 CLITTLCCGKNPFGDEDGSSAATSKTEASSVSSSQVSPA 354
:::: :::| ::::::::: :: : : : ::::::|
Consensus 397 FIVNSSVNGPTVKREKIVQRNPINVRLGIKIEPRDSRAA 435
</get_outfileReturn>
Example provenance
The metadata for this value includes a workflow provenance record.
This indentifies:
Not included
- workflow definition - the workflow source in WSFL that was given to the enactment engine.
- service metadata - the provenance record has details of the invocation of a service from the prespective of the enactment engine, but it does not have any metadata that might be available from the service itself.
- why - any additional annotation that the user who ran the workflow might want to include, for example
--
MarkGreenwood - 21 Jan 2003