Image
EAN-139780761854302   EAN-13 barcode 9780761854302
Product NameSynergistic Collaborations: Pastoral Care And Church Social Work
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:9.17 inches / Length:6.1 inches / Weight:0.56 pounds / Width:0.35 inches
Amazon.comA Buy on Amazon ~ 0761854304
SKU9780761854302_NW
Price New21.99 US Dollars    (curriencies)
Price Used8.75 US Dollars    (curriencies)
Width0.38 inches    (convert)
Height9.16 inches    (convert)
Length6.1 inches    (convert)
Weight9.12 ounces    (convert)
AuthorVelmarie L. Albertini, Jonathan C. Grenz
Page Count158
BindingPaperback
Published12/13/2010
Long DescriptionSynergistic Collaborations is a valuable resource for Christian ministers and social workers seeking to extend outreach ministries and new ways to collaborate with community organizations as they serve hurting people. This unique book combines case studies, theological reflections, reality dialogue questions, personal experiences, and research that broaden readers' understanding of the synergistic relationship that naturally exists between pastoral care ministry and social work practices. The authors challenge contemporary perceptions concerning how churches might help people affected by issues related to mental illness, poverty, HIV/AIDS, substance abuse, homelessness, and domestic violence. With the aim of ameliorating existing church ministries, this book offers opportunities to build the knowledge base and skills of readers as they explore Christian ministries in relation to the many personal and social problems people face in our rapidly changing culture and society.
Similar Items9781938248016: A Framework For Understanding Poverty; A Cognitive Approach
9780757520198: A Framework For Understanding Poverty; A Cognitive Approach
9780962363429: Church Social Work: Helping the Whole Person in the Context of the Church
9781434799807: Letters From A Skeptic: A Son Wrestles With His Father's Questions About Christianity
9781142768386: Letters From A Skeptic: A Son Wrestles With His Father's Questions About Christianity
9780778301042: Letters From A Skeptic: A Son Wrestles With His Father's Questions About Christianity
9780851114941: The Universe Next Door: A Basic Worldview Catalog, 5th Edition
9780830838509: The Universe Next Door: A Basic Worldview Catalog, 5th Edition
9780789483935: The Universe Next Door: A Basic Worldview Catalog, 5th Edition
9780707302850: The Universe Next Door: A Basic Worldview Catalog, 5th Edition
9780670019069: The Universe Next Door: A Basic Worldview Catalog, 5th Edition
9780827221390: Loving Wisdom: Christian Philosophy Of Religion
9780805411638: Experiencing Ministry Supervision
9780801031403: Living At The Crossroads: An Introduction To Christian Worldview
Created11-22-2012 6:56:25pm
Modified06-18-2016 10:58:47pm
MD5806c8e60ba7e7f961354ba3e0dd3f823
SHA2560348e527a66f170ed6c123bca85dafdf3ecf8218de30d3da97669cd6ae994f98
Search Googleby EAN or by Title
Query Time0.0274110

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share