We currently provide a mapping AsymUnit.auth_seq_id_map which maps the internal 1-based seq_id to an 'author-provided' number. On discussion with PDB, this should map to the "corrected" author-provided numbering which is used in legacy PDB files, and maps to atom_site.auth_seq_id and pdbx_poly_seq_scheme.pdb_seq_num.
However, there is another "original" author-provided numbering which maps to atom_site.pdbx_auth_seq_id and pdbx_poly_seq_scheme.auth_seq_num. We should also support this numbering, perhaps via AsymUnit.orig_auth_seq_id_map, by reading/writing the various scheme tables. No need to output pdbx_auth_seq_id though as this is only intended for internal use.
We currently provide a mapping
AsymUnit.auth_seq_id_mapwhich maps the internal 1-based seq_id to an 'author-provided' number. On discussion with PDB, this should map to the "corrected" author-provided numbering which is used in legacy PDB files, and maps toatom_site.auth_seq_idandpdbx_poly_seq_scheme.pdb_seq_num.However, there is another "original" author-provided numbering which maps to
atom_site.pdbx_auth_seq_idandpdbx_poly_seq_scheme.auth_seq_num. We should also support this numbering, perhaps viaAsymUnit.orig_auth_seq_id_map, by reading/writing the various scheme tables. No need to outputpdbx_auth_seq_idthough as this is only intended for internal use.