# # Copyright (C) 2005 Richard Cameron, CiteULike.org # All rights reserved. # # This code is derived from software contributed to CiteULike.org # by # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # 3. All advertising materials mentioning features or use of this software # must display the following acknowledgement: # This product includes software developed by # CiteULike and its # contributors. # 4. Neither the name of CiteULike nor the names of its # contributors may be used to endorse or promote products derived # from this software without specific prior written permission. # # THIS SOFTWARE IS PROVIDED BY CITEULIKE.ORG AND CONTRIBUTORS # ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED # TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR # PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS # BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE # POSSIBILITY OF SUCH DAMAGE. # # Each plugin needs a description so the driver can advertise the details # to the users on the site plugin { # Integer version number for the plugin code. When this number is incremented, # CiteULike may reparse all existing articles with the new code. version {1} # The name of the plugin, as displayed on the "CiteULike supports..." page name {Cell} # The link the front page of this service url {http://www.cell.com} # Any additional information which needs to be displayed to the user. # E.g. "Experimental support" blurb {} # Your name author {Fergus Gallagher} # Your email address email {fergus@citeulike.org} # Language you wrote the plugin in language {perl} # Regular expression to match URLs that the plugin is # *potentially* interested in. Any URL matching this regexp # will cause your parser to be invoked. Currently, this will # require fork()ing a process, so you should try to reduce the number # of false positives by making your regexp as restrictive as possible. # # If it is not possible to determine whether or not your plugin is # interested purely on the basis of the URL, you will have a chance # to refine this decision in your code. For now, try to make a reasonable # approximation - like, check for URLs on the right hostname # # Note: Some universities provide mirrors of commericial publishers' sites # with different hostnames, so you should provide some leeway in your # regexp if that applies to you. # # CELL itself is http://www.cell.com/abstract/xxxxx # Other are http://www.cell.com/journalname/abstract/xxxxx regexp {http://www\.cell\.com/([^/]+/)?abstract/.*} } # # Linkout formatting # # CiteULike doesn't store URLs for articles. # Instead it stores the raw ingredients required to build the dynamically. # Each plugin is required to define a small procedure which does this formatting # See the HOWTO file for more details. # # The variables following variables are defined for your use # in the function: type ikey_1 ckey_1 ikey_2 ckey_2 # format_linkout CELL { return [list "Cell" "http://www.cell.com/${ckey_1}/abstract/${ckey_2}"] } # # TESTS # # Each plugin MUST provide a set of tests. The motivation behind this is # that web scraping code is inherently fragile, and is likely to break whenever # the provider decides to redisign their site. CiteULike will periodically # run tests to see if anything has broken. # Please provide as comprehensive a set of tests as possible. # If you ever fix a bug in the parser, it is highly recommended that # you add the offending page as a test case. # # This is the RIS test (break with BibTeX - so delete when stable) # test {http://www.jove.com/index/Details.stp?ID=1067} { formatted_url {DOI http://dx.doi.org/10.3791/1067} formatted_url {{Journal of Visualized Experiment} http://www.jove.com/index/Details.stp?ID=1067} linkout {DOI {} 10.3791/1067 {} {}} linkout {JOVE 1067 {} {} {}} doi 10.3791/1067 year 2009 month 1 day 19 type JOUR plugin_version 1 issue 23 title {Calcium Imaging of Cortical Neurons using Fura-2 AM} journal {Journal of Visualized Experiments} abstract {Calcium imaging is a common technique that is useful for measuring calcium signals in cultured cells. Calcium imaging techniques take advantage of calcium indicator dyes, which are BAPTA-based organic molecules that change their spectral properties in response to the binding of Ca2+ ions. Calcium indicator dyes fall into two categories, ratio-metric dyes like Fura-2 and Indo-1 and single-wavelength dyes like Fluo-4. Ratio-metric dyes change either their excitation or their emission spectra in response to calcium, allowing the concentration of intracellular calcium to be determined from the ratio of fluorescence emission or excitation at distinct wavelengths. The main advantage of using ratio-metric dyes over single wavelength probes is that the ratio signal is independent of the dye concentration, illumination intensity, and optical path length allowing the concentration of intracellular calcium to be determined independently of these artifacts. One of the most common calcium indicators is Fura-2, which has an emission peak at 505 nM and changes its excitation peak from 340 nm to 380 nm in response to calcium binding. Here we describe the use of Fura-2 to measure intracellular calcium elevations in neurons and other excitable cells.} author {Barreto-Chang {} {} {L Barreto-Chang, Odmara}} author {Dolmetsch {} {} {E Dolmetsch, Ricardo}} status ok }