Guidelines for Registry API use
Effective date: August 6th, 2018
The following are developer guidelines for Registry API use; this includes use of Registry Database dumps, XML Part information, FASTA files, wiki information, and web-scraping. Please note that these guidelines are not exhaustive and are subject to change.
If you are planning on using the Registry API and/or content, please contact firstname.lastname@example.org. We would like to know about your project and would be happy to offer guidance, review, and potential partnership.
All Registry content falls under Creative Commons Attribution-ShareAlike.
Registry parts can have a lot of information, but a few things must be displayed when these parts are presented in third-party applications or tools. We ask that you comply with these requirements when you display Registry parts and content.
Required Part Information
- Part Number (BBa_) with a link to that part page on the Registry
- ex: BBa_R0040, https://parts.igem.org/Part:BBa_R0040
- Date of Entry
- Reference/links to:
Recommended Part Information
- Part Short Description
- Part Type
- Part Sequence
- Experience Page, with a link to that part’s experience page on the Registry
- Design Page, with a link to that part’s design page on the Registry
The iGEM Logo is available in the following formats
The iGEM Foundation and the Registry do not provide any guarantees or validation on a part’s function, efficacy, safety, or use.
The iGEM Foundation and its programs run as an open community with thousands of members. iGEM is committed to protecting the privacy of our users and following privacy guidelines.
In regards to iGEM/Registry content, we prohibit any use of user (part authors, wiki contributors, etc.) information by any group that would infringe upon a user’s privacy. This includes associating, linking, or matching iGEM/Registry users and their content with personal information off-site.
Brand and Content Use
Do not use iGEM/Registry content to promote or market any product/service without explicit permission from the iGEM Foundation.
Do not use iGEM/Registry content to imply sponsorship, partnership, or association with the iGEM Foundation and its programs without explicit permission from the iGEM Foundation.
Modifications to Guidelines
We may change our API Guidelines at any time. The most recent version of our API Guidelines is reflected by the version date located at the top of this page. All updates are effective immediately upon notice, which we may give by any means, including, but not limited to, by posting a revised version of these guidelines or other notice on the Websites.
We welcome your feedback. If you have any questions or comments, please contact us at email@example.com.