You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some classification systems (e.g. ISIC) have numerous different versions of the classification system.
It would be good to track this in a user-facing in, for example, the individual *_classification datasets, while recognizing that that column would never actually be used in the code.
My proposal would be that:
the *_classification datasets gain a column indicating this information if necessary
the sector_classifications dataset keeps only the crucial columns used by the code (e.g. sector, borderline, code, code_system)
jdhoffa
changed the title
feat: *_classification files gain version column
feat: *_classification files gain column indicating the version or revision of the bridge, if necessary
Mar 6, 2024
jdhoffa
changed the title
feat: *_classification files gain column indicating the version or revision of the bridge, if necessary
feat: *_classification files gain column indicating the version or revision of the bridge, if relevant
Mar 6, 2024
Some classification systems (e.g. ISIC) have numerous different versions of the classification system.
It would be good to track this in a user-facing in, for example, the individual
*_classification
datasets, while recognizing that that column would never actually be used in the code.My proposal would be that:
*_classification
datasets gain a column indicating this information if necessarysector_classifications
dataset keeps only the crucial columns used by the code (e.g.sector
,borderline
,code
,code_system
)cc @jacobvjk
AB#10174
The text was updated successfully, but these errors were encountered: