It seems unlikely to me that there's much demand for this field at all, never mind demand for keeping both an ISIN and a national number, so I don't think we need to separate it. The search function could use namespace as a disambiguator for numbers, or users who encounter more than one flavor could use a prefix to separate them if the formats happen to collide, eg cusip-123456789 and wkn-123456789.
As it happens cusip is 9 characters, sedol is 7, wkn is 6, and ISIN is 12 so there's no collisions among those 4. Regards, John Ralls > On Jan 22, 2022, at 9:35 AM, Frank H. Ellenberger > <frank.h.ellenber...@gmail.com> wrote: > > Hi Thomas, > > Am 21.01.22 um 21:39 schrieb Thomas: >> And because of that, I am struggling to do a matching based on that >> field. As my bank, denotes the WKN (a unique identifier), > > The WKN is only unique inside the german markets. If you also have a > french bank, they might send the SEDOL instead. > > But ISIN would be unique. It is "DE"<WKN><checkdigit>. > > I wonder if we should at some point separate ISIN as gloal unique > identifier from the catch-all field "ISIN, CUSIP or other identifier". > > Namespace+Symbol is the current unique identifier. > ISIN would be unique while NSINs like WKN have the implicit assumption > all securities are emitted in the same country. > > Regards > Frank > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
