dev-q-and-a2 | Codeforscience.com

Fri, 2012-09-07

We know you're problem solvers by nature but we still want to back you up. Don't let anything stop you because there will be another live online developer Q&A session!

Remember, to troubleshoot any technical problems you face during app development, you can join Elsevier Developers google group or directly email developers-elsevier@googlegroup.com at any time. This is just another option.

Topic: CFS Singapore Developer Q&A
Date: Wednesday, September 12
Time: 8:00pm, Singapore Time

Submit your questions here to get your Q's addressed first during the session.

1. Go to https://reedelsevier.webex.com/reedelsevier/j.php?ED=189457612&UID=495007572&RT=MiMxMQ%3D%3D

2. If requested, enter your name and email address.

3. Leave the password empty; this meeting does not require a password.

4. Click "Join".

_{We encourage you to check webex requirements ahead of the session as it requires installation of a plugin and may require a Java install. For access questions and issues, email r.kwakkelaar@elsevier.com}

For your reference, here are the questions and answers from session #1.

Q: Can we use a .NET application and communicate with it from our SciVerse application? Where can the application be hosted?
A: SciVerse does not provide any hosting capabilities for server-side components developed in conjunction with the SciVerse application. The application can be hosted on resources provided by the developer or in the Cloud. There is no restriction on the technology used to develop the component. Anything that has a URL can be communicated with from your SciVerse application using the gadgets.io.makeRequest API.

Q: Is there an API that can provide information about search results on the SD search results page?
A: Developers can use the gadgets.sciverse.getResults() API to retrieve information about specific results or the gadgets.sciverse.getAllResults() API to retrieve information about all results being displayed. These APIs are available on the SD, Scopus, and Hub Search Results pages.

Q: For one paper in ScienceDirect, I would like to obtain the XML format of its references and the papers that cite it. However, I could not find any direct APIs to retrieve the information. Is there any fast way to achieve the goal?
A: There isn’t a direct way to get this information.

Reference information can be retrieved using one of the following methods:

By calling the Content Retrieval using: http://api.elsevier.com/content/article/DOI:<DOI>?view=FULL. The XML in the response will contain information about the references. Here’s a sample of some of the information included:

Under originalText -> xocs:docs -> xocs:meta, there will be a xocs:references element:

<xocs:references>

<xocs:ref-info refid="bib1">

<xocs:ref-normalized-surname>BALASUBRAMANIAN</xocs:ref-normalized-surname>

<xocs:ref-pub-year>2005</xocs:ref-pub-year>

<xocs:ref-first-fp>20</xocs:ref-first-fp>

<xocs:ref-last-lp>27</xocs:ref-last-lp>

<xocs:ref-normalized-initial>P</xocs:ref-normalized-initial>

</xocs:ref-info>

<xocs:ref-info refid="bib2">

<xocs:ref-normalized-surname>BAO</xocs:ref-normalized-surname>

<xocs:ref-pub-year>2000</xocs:ref-pub-year>

<xocs:ref-first-fp>3347</xocs:ref-first-fp>

<xocs:ref-last-lp>3358</xocs:ref-last-lp>

<xocs:ref-normalized-initial>Z</xocs:ref-normalized-initial>

</xocs:ref-info>

<xocs:ref-info refid="bib3">

<xocs:ref-normalized-surname>BENNETT</xocs:ref-normalized-surname>

<xocs:ref-pub-year>1980</xocs:ref-pub-year>

<xocs:ref-first-fp>454</xocs:ref-first-fp>

<xocs:ref-last-lp>461</xocs:ref-last-lp>

<xocs:ref-normalized-initial>D</xocs:ref-normalized-initial>

</xocs:ref-info>

</xocs:references>

There will also be a ce:bibliography-sec element that looks like the following:

<ce:bibliography-sec>

<ce:bib-reference id="bib1">

<ce:label>Balasubramanian and Kandlikar, 2005</ce:label>

<sb:reference xmlns:sb="http://www.elsevier.com/xml/common/struct-bib/dtd">

<sb:contribution langtype="en">

<sb:authors>

<sb:author>

<ce:given-name>P.</ce:given-name>

<ce:surname>Balasubramanian</ce:surname>

</sb:author>

<sb:author>

<ce:given-name>S.G.</ce:given-name>

<ce:surname>Kandlikar</ce:surname>

</sb:author>

</sb:authors>

<sb:title>

<sb:maintitle>Experimental study of flow patterns, pressure drop, and flow instabilities in parallel rectangular minichannels</sb:maintitle>

</sb:title>

</sb:contribution>

<sb:host>

<sb:issue>

<sb:series>

<sb:title>

<sb:maintitle>Heat Transfer Eng.</sb:maintitle>

</sb:title>

<sb:volume-nr>26</sb:volume-nr>

</sb:series>

<sb:date>2005</sb:date>

</sb:issue>

<sb:pages>

<sb:first-page>20</sb:first-page>

<sb:last-page>27</sb:last-page>

</sb:pages>

</sb:host>

</sb:reference>

</ce:bib-reference>

</ce:bibliography-sec>

References can also be retrieved from Scopus using the Abstract content: http://api.elsevier.com/content/abstract/DOI:<DOI>?view=REF. The XML will contain the following:

<author-list>

<ce:initials>P.</ce:initials>

<ce:indexed-name>Balasubramanian P.</ce:indexed-name>

<ce:surname>Balasubramanian</ce:surname>

<ce:given-name>Prabhu</ce:given-name>

<preferred-name>

<ce:initials>P.</ce:initials>

<ce:indexed-name>Balasubramanian P.</ce:indexed-name>

<ce:surname>Balasubramanian</ce:surname>

<ce:given-name>Prabhu</ce:given-name>

</preferred-name>

</author>

<ce:initials>S.G.</ce:initials>

<ce:indexed-name>Kandlikar S.G.</ce:indexed-name>

<ce:surname>Kandlikar</ce:surname>

<ce:given-name>Satish G.</ce:given-name>

<preferred-name>

<ce:initials>S.G.</ce:initials>

<ce:indexed-name>Kandlikar S.</ce:indexed-name>

<ce:surname>Kandlikar</ce:surname>

<ce:given-name>Satish G.</ce:given-name>

</preferred-name>

<ce:e-address type="email">sgkeme@rit.edu</ce:e-address>

</author>

<ce:initials>S.G.</ce:initials>

<ce:indexed-name>Kandlikar S.G.</ce:indexed-name>

<ce:surname>Kandlikar</ce:surname>

<ce:given-name>Satish G.</ce:given-name>

<preferred-name>

<ce:initials>S.G.</ce:initials>

<ce:indexed-name>Kandlikar S.</ce:indexed-name>

<ce:surname>Kandlikar</ce:surname>

<ce:given-name>Satish G.</ce:given-name>

</preferred-name>

<ce:e-address type="email">sgkeme@rit.edu</ce:e-address>

</author>

</author-list>

<sourcetitle xmlns:ait="http://www.elsevier.com/xml/ani/ait" xmlns:cto="http://www.elsevier.com/xml/cto/dtd" xmlns:xocs="http://www.elsevier.com/xml/xocs/dtd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Heat Transfer Engineering</sourcetitle>

</volisspag>

<citedby-count xmlns:ait="http://www.elsevier.com/xml/ani/ait" xmlns:cto="http://www.elsevier.com/xml/cto/dtd" xmlns:xocs="http://www.elsevier.com/xml/xocs/dtd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">36</citedby-count>

<scopus-id>14644398506</scopus-id>

<ce:doi xmlns:ait="http://www.elsevier.com/xml/ani/ait" xmlns:cto="http://www.elsevier.com/xml/cto/dtd" xmlns:xocs="http://www.elsevier.com/xml/xocs/dtd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">10.1080/01457630590907167</ce:doi>

</reference>

To retrieve Citation information, the document can be retrieved from Scopus using the DOI (http://api.elsevier.com/content/abstract/DOI:<doi>?view=FULL). In the response, there will be a “link” element with an attribute ‘rel’ that has a value of “cited-by”. This href attribute for that element will contain the Content API call that needs to be used to retrieve the citations for the document.

Primary Links Singapore

Live Developer Q&A Session #2 on Wed 9/12 8pm