Closed eblondel closed 9 years ago
to be precise, and as far as I understand it, we do not need an enrichment of the asfis-worms
mappings. we need to extract the subset ofworms
of all the species whose code occurs in the asfis-worms
mapping. in particular, we do not need to add more information to that mapping, rather produce a second, separate datasets.
Thanks @fabiosimeoni indeed on this i had a doubt ;-) At now the output is a csv asset. The only additional column is the ASFIS alphacode, but if you want i can remove it, no problem, so it the logic will be strictly a filter. Let me know
tell you what, leave it as it is since it's just an extra field. it cannot do much harm and may turn out to be an optimisation. will check with @cbaldassarre. thanks!
is it everything ok? if yes, please close the ticket.
am waiting for C.Baldassarre to give the OK, only he can judge the data. will close as soon as I know something.
On 28 Jan 2015, at 12:49, Emmanuel Blondel notifications@github.com wrote:
is it everything ok? if yes, please close the ticket.
— Reply to this email directly or view it on GitHub.
The new glue has been implemented. I've pushed the 2 assets to Grade. The code hierarchy dataset is named worms-subset-hierarchy
, and the derived codelist (handling name, rank & author) is named worms-subset-codelist
.
To add some glue for enriching the
asfis
-worms
pure code mapping withworms
detailed (textual) information. The requirement has been extended to provide the taxonomic code hierarchy covering the ASFIS species list.Inputs:
comet
mapping xml asset,worms
dataset as csv asset.Outputs:
CsvAsset
,CsvAsset