"
Team:TU Delft/Software/part-search
From 2010.igem.org
| Line 5: | Line 5: | ||
You can use this server to browse parts by category, as specified by each part in the partsregistry editor. | You can use this server to browse parts by category, as specified by each part in the partsregistry editor. | ||
It also supports a range of other webservices that can be used by javascript or other applications, described [http://igempartview.appspot.com/api.jsp here]. | It also supports a range of other webservices that can be used by javascript or other applications, described [http://igempartview.appspot.com/api.jsp here]. | ||
| - | |||
| - | + | ===Why make another webservice?=== | |
| + | The current partsregistry [http://partsregistry.org/Registry_API web interfaces] are pretty limited. | ||
| + | * There is no interface to search for parts. | ||
| + | * The XML interface cannot be used by scripts that are not on the partsregistry wiki, due to [http://en.wikipedia.org/wiki/Same_origin_policy Same-Origin-Policy] | ||
| + | |||
| + | This service supports a webservice mechanism called [http://en.wikipedia.org/wiki/JSON#JSONP JSONP], which allows team wiki javascript to query part information (properties, categories, or DNA sequence) in a dynamic way, something that is not possible with the current [http://partsregistry.org/Registry_API registry API]. | ||
===Implementation=== | ===Implementation=== | ||
The server uses the [http://partsregistry.org/DAS_-_Distributed_Annotation_System DAS server] to look for new parts, and the [http://partsregistry.org/Registry_API#XML_Part_Information XML Part information] to read part information. It refreshes it's content once a week (Look [http://igempartview.appspot.com/content_update.jsp here] for accurate update information). | The server uses the [http://partsregistry.org/DAS_-_Distributed_Annotation_System DAS server] to look for new parts, and the [http://partsregistry.org/Registry_API#XML_Part_Information XML Part information] to read part information. It refreshes it's content once a week (Look [http://igempartview.appspot.com/content_update.jsp here] for accurate update information). | ||
| + | |||
| + | The service runs on [http://code.google.com/intl/nl-NL/appengine/ Google App Engine], so uptime is pretty ok. There are no server maintainance costs, because it will be able to run within the [http://code.google.com/intl/nl-NL/appengine/docs/quotas.html free quota's] of Google App Engine. | ||
<html><h2><a href="http://igempartview.appspot.com/iphone.jsp">iPhone part browser app</a></h2></html> | <html><h2><a href="http://igempartview.appspot.com/iphone.jsp">iPhone part browser app</a></h2></html> | ||
Revision as of 19:22, 25 October 2010
Part search server
Because the partsregistry has limited search capabilities, a search service was created, running at: [http://igempartview.appspot.com igempartview.appspot.com]. You can use this server to browse parts by category, as specified by each part in the partsregistry editor. It also supports a range of other webservices that can be used by javascript or other applications, described [http://igempartview.appspot.com/api.jsp here].Why make another webservice?
The current partsregistry [http://partsregistry.org/Registry_API web interfaces] are pretty limited.
- There is no interface to search for parts.
- The XML interface cannot be used by scripts that are not on the partsregistry wiki, due to [http://en.wikipedia.org/wiki/Same_origin_policy Same-Origin-Policy]
This service supports a webservice mechanism called [http://en.wikipedia.org/wiki/JSON#JSONP JSONP], which allows team wiki javascript to query part information (properties, categories, or DNA sequence) in a dynamic way, something that is not possible with the current [http://partsregistry.org/Registry_API registry API].
Implementation
The server uses the [http://partsregistry.org/DAS_-_Distributed_Annotation_System DAS server] to look for new parts, and the [http://partsregistry.org/Registry_API#XML_Part_Information XML Part information] to read part information. It refreshes it's content once a week (Look [http://igempartview.appspot.com/content_update.jsp here] for accurate update information).
The service runs on [http://code.google.com/intl/nl-NL/appengine/ Google App Engine], so uptime is pretty ok. There are no server maintainance costs, because it will be able to run within the [http://code.google.com/intl/nl-NL/appengine/docs/quotas.html free quota's] of Google App Engine.
iPhone part browser app
The TU Delft team is working on an iPhone app to allow quick lookup of part properties, and browse parts by category. The new webservice above is being used for this.
iPhone apps have to be approved by Apple before they end up in the App Store. Once this is done for our app, details will be put on this page: http://igempartview.appspot.com/iphone.jsp
