Policies for Duke Web Editors and Managers
If you’re a web content editor, communicator, or website manager at Duke, please read this section to learn how to
get support for your site’s data feed from Scholars@Duke. This section assumes that you are working with someone
like a web developer or programmer to build your website, and you’re acting as the business owner or customer. The
developer you’re working with could be a Duke web developer, a vendor, or Duke Web Services.
Planning for Launch Day
 Before your website launches, you and your development team should have a maintenance agreement to ensure
that support policies and processes are clearly understood, including support of Scholars data feeds.
 Make sure that the development team knows how to get help with questions about any of the data feed
methodologies discussed later.
 Know your local Scholars power user and familiarize yourself with user resources on the Scholars Support
(http://about.scholars.duke.edu/support-duke-faculty-delegates)page. You need to serve as the first level of
support for questions about Scholars data, so you’ll need to understand the basics of where Scholars data comes
Even though you are not responsible for technical details, we recommend that you read this document and explore
the links to supporting documentation. This understanding will help you communicate with the development team.
Go-Live and Maintenance
If you have questions about Scholars data after your website goes live, here’s how to troubleshoot the problem and
contact the right group for help:
 First, determine if the problem is with Scholars or with the data feeds.
 If you have questions about data being fed from Scholars, please check the faculty member's
Scholars@Duke profile to see if the data is correct in Scholars.
 If data needs to be corrected in dFac, Elements or another source system, contact your power user
(http://about.scholars.duke.edu/locate-power-user) to find out how to get it updated.
 If data looks OK in Scholars, then the problem is not in Scholars. Do not contact the Scholars team!
Your development team may have answers.


 Next, report the problem to your development group, explaining that the data looks OK in Scholars, as follows:
 If the developer or vendor determines that the Scholars widgets or the SPARQL endpoint is not working
as they should be, then the developer should submit a Help ticket to the Scholars team. We need
technical details from the developer, so it’s important that they contact us directly.
 If the developer or vendor uses the Scholars Drupal module, the developer or vendor must determine if
the module is working correctly and if not, they should contact Duke Web Services at oit-
 If Duke Web Services developed your website or system, or if you have a support agreement with Duke
Web Services, contact them at oit-dws@duke.edu.
 Training on Scholars and Elements is available for those who’d like to learn more. Please refer to the Scholars
Support (http://about.scholars.duke.edu/support-duke-faculty-delegates)or attend a Scholars/Elements training