"
Team:SUSTC-Shenzhen-A/Notebook/search result
From 2012.igem.org
(→7.19) |
|||
| Line 7: | Line 7: | ||
We chose mysql as database for its search functions. | We chose mysql as database for its search functions. | ||
| - | ==='''7. | + | ==='''7.18'''=== |
For the division of work had been decided, members of databases started to analyse the mysql files and collect all the titles. By comparing the database and the website, we found that the database was incomplete, which didn't contain the description written by different authors, and the structure was totally different from the website. In order to build a part-name-based search result, we needed to search whole database again when SE returned us the part name and collected the result. | For the division of work had been decided, members of databases started to analyse the mysql files and collect all the titles. By comparing the database and the website, we found that the database was incomplete, which didn't contain the description written by different authors, and the structure was totally different from the website. In order to build a part-name-based search result, we needed to search whole database again when SE returned us the part name and collected the result. | ||
| + | |||
| + | ==='''7.19'''=== | ||
| + | Considering there were a lot of data titles and some of them contained few data, we tried to pick only necessary parts out. This day we were devoted into select data from several tables. | ||
| + | |||
| + | ==='''7.20'''=== | ||
Revision as of 09:22, 26 July 2012
Contents |
brief introduction
Search result group includes six members. The main goal of this group is to create an interface to accept the result(part name) of bio-brick searching (which is sent by the SE group), and show the details of this part.
In this part, database was the most important thing and five members were successively working on it.
Our members used database of an iGEM software team （求网址）at first. The database, which was contained parts of data of the website, included 13 tables, whose structure was different from the website, so it's inconvenient to search parts and get detailed result. Through several days "struggle", our group succeeded in loading data from xml which was provided by partsregistry.org and saved as sql file.
We chose mysql as database for its search functions.
7.18
For the division of work had been decided, members of databases started to analyse the mysql files and collect all the titles. By comparing the database and the website, we found that the database was incomplete, which didn't contain the description written by different authors, and the structure was totally different from the website. In order to build a part-name-based search result, we needed to search whole database again when SE returned us the part name and collected the result.
7.19
Considering there were a lot of data titles and some of them contained few data, we tried to pick only necessary parts out. This day we were devoted into select data from several tables.
