The Columbia Social Work Review was founded in 2003 and is an annual peer-reviewed journal for up-and-coming scholars in the field of social work to share their research with faculty, fellow students, and the wider scholarly community. The mission of the Columbia Social Work Review is to publish original academic writing on social work practice, education, research, policy and theory from the perspective of social work students. The Review strives to enrich the scholarly nature of our school and the profession by providing a forum for the exchange of innovative ideas. 

Open Access Policy

Columbia Social Work Review is an open access journal which means that all content is freely available without charge to the user or his/her institution. Users are allowed to read, download, copy, distribute, print, search, or link to the full texts of the articles in this journal without asking prior permission from the publisher or the author. Authors retain their copyright and agree to license their articles with a Creative Commons "Attribution" License. You can read more about Creative Commons licenses at creativecommons.org.

Columbia Social Work Review is a no-fee journal. Authors are not charged for the publication of their articles.

Archiving Policy

Columbia Social Work Review is distributed through Columbia University’s Academic Commons. Academic Commons is Columbia University’s institutional repository, offering long-term public access to research shared by the Columbia community. A program of the Columbia University Libraries, Academic Commons provides secure, replicated storage for files in multiple formats. Academic Commons assigns a DOI and accurate metadata to each work to enhance discoverability.

Files uploaded to Academic Commons are written to an Isilon storage cluster at Columbia University and replicated to an identical system at a secure, offsite facility. The local cluster stores the data in a "best protection possible" policy which provides, at a minimum, guaranteed protection against the loss of any two disks or any one node. When sufficient capacity is available, this is increased automatically. Multiple snapshots are replicated to our disaster recovery site every two hours. The secondary cluster employs the same protections as the primary cluster and both conduct integrity scans to validate that data has not been altered at any point during rebalancing, snapshot, or replication processes.