No - they're changing the auth_asym_id. See https://www.wwpdb.org/documentation/carbohydrate-remediation:
Oligosaccharide molecules are classified as a new entity type, branched, assigned a unique chain ID (_atom_site.auth_asym_id) and a new mmCIF category introduced to define the type of branching (_pdbx_entity_branch.type) . wwPDB:<https://www.wwpdb.org/documentation/carbohydrate-remediation> wwPDB: Worldwide Protein Data Bank. Carbohydrate Remediation. As the PDB archive grows, and the related science and techniques evolve, the 3D structures represented in the Core Archive require ongoing improvement ("remediation") to ensure consistency, accuracy, and overall quality. www.wwpdb.org ________________________________ From: Greg Couch <gr...@cgl.ucsf.edu> Sent: 04 December 2020 18:51 To: Luca Jovine <luca.jov...@ki.se>; Mailing List CCP4 <CCP4BB@jiscmail.ac.uk>; Mailing List PDB, <pd...@sdsc.edu> Cc: Tristan Croll <ti...@cam.ac.uk> Subject: pdb-l: Re: [ccp4bb] Coming July 29: Improved Carbohydrate Data at the PDB -- N-glycans are now separate chains if more than one residue mmCIF has two different chain ids. One the the label_asym_id which is used for internal consistency with the entities. The other is the auth_asym_id which is whatever the author chooses. If the glycans are separate entities, then the label_asym_id HAS to be different for each instance of an entity. But the auth_asym_id could be the same for all covalently bonded units. In ChimeraX, we use the label_seq_id for the chain id when constructing the molecule and we use the auth_asym_id for the chain id in the user interface. -- Greg ######################################################################## To unsubscribe from the CCP4BB list, click the following link: https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=CCP4BB&A=1 This message was issued to members of www.jiscmail.ac.uk/CCP4BB, a mailing list hosted by www.jiscmail.ac.uk, terms & conditions are available at https://www.jiscmail.ac.uk/policyandsecurity/
