Skip to content

Backwards concordance not the same as forward concordance tables #5

@zachariah-frost

Description

@zachariah-frost

Hi Insongkim,

I noticed when using your concordance package that when concording forwards, for example code 681510, it is identified as not changing between HS4 (2012) and HS5 (2017). However, when using the UN's HS tracker tool, it says that in this period, 681510 is split into 681510 and 962000. My suspicion is that this is due to which tables are used on the UN concordance tables website - HS2017 - HS2012 does not identify this change (there is a reference in the comments column, but not in the HS code column), and it is not recognised in your database within the package when looking at the hs5_hs4 data. If i'm correct in this, the code will have to be adapted to consider both forwards and backwards concordance - so will have to use as well the HS2012 - HS2017?

Kind regards,

ZF

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions