<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Rationalisation of the durbar move: A step towards good governance in Jammu and Kashmir</title>
  </titleInfo>
  <name type="personal">
    <namePart>Wani, Aijaz Ashraf and Parray, Janan Ahmad</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="text">Indian Journal of Public Administration</placeTerm>
    </place>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>70(1), Mar, 2024: p.140-157</extent>
  </physicalDescription>
  <abstract>Digitisation of records and the subsequent implementation of e-Office1 software in various Durbar Move2 offices of the Union Territory (UT) of Jammu and Kashmir (J&amp;K) has changed the concept and nature of governance significantly. With the implementation of e-Office software in various departments of the Civil Secretariat, there has been a significant impact on the governance efficiency and service delivery in the UT. The present paper attempts to understand, examine, and analyse the impact of e-Office software on the delivery of governance services in J&amp;K. It is an endeavour to understand how the new system of e-Office enables the administrative apparatus and enables the governance to be more responsive, accountable, transparent, and citizen-friendly. – Reproduced 

https://journals.sagepub.com/doi/full/10.1177/00195561231204609
</abstract>
  <relatedItem type="host">
    <name>
      <namePart>Indian Journal of Public Administration  </namePart>
    </name>
  </relatedItem>
  <recordInfo>
    <recordCreationDate encoding="marc">240328</recordCreationDate>
  </recordInfo>
</mods>
