PDB identification code: Difference between revisions
From Proteopedia
Jump to navigationJump to search
Eric Martz (talk | contribs) |
Eric Martz (talk | contribs) |
||
| Line 30: | Line 30: | ||
==Future Plans for Expanded PDB Codes== | ==Future Plans for Expanded PDB Codes== | ||
In May, 2017, the [[Protein Data Bank]] announced plans to introduce, later in 2017, an expanded PDB accession code with versioning<ref>PDB News May 17, 2017: [https://www.wwpdb.org/news/news?year=2017#5910c8d8d3b1d333029d4ea8 Revise Your Structure Without Changing the PDB Accession Code and Related Changes to the FTP Archive].</ref>. The new codes will have the format | In May, 2017, the [[Protein Data Bank]] announced plans to introduce, later in 2017, an expanded PDB accession code with versioning<ref name="news1">PDB News May 17, 2017: [https://www.wwpdb.org/news/news?year=2017#5910c8d8d3b1d333029d4ea8 Revise Your Structure Without Changing the PDB Accession Code and Related Changes to the FTP Archive].</ref>. The new codes will have the format | ||
<blockquote> | <blockquote> | ||
'''pdb_00001abc''' | '''pdb_00001abc''' | ||
</blockquote> | </blockquote> | ||
In addition to increasing the number of possible accession codes from ~4 x 10<sup>4</sup> to >10<sup>12</sup>, this will facilitate "will enable text mining detection of PDB entries in the published literature"<ref name="news1" />. | |||
==See Also== | ==See Also== | ||
