<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="../xsl/priorityoutcomes.xsl"?>
<PriorityOutcome xmlns:gms="http://www.govtalk.gov.uk/CM/gms-xs" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.esd-toolkit.org/psto/xmlschemas/PriorityOutcome-v1.0.xsd">
	<BasicInfo>
		<Reference>R3</Reference>
		<Definition>Online facilities to be available to allow one stop direct access and deep linking to joined up A-Z information on all local authority services via website or shared telephone contact centre using the recognised taxonomy of the Local Government Category List (Authorities using alternative service taxonomies (e.g. seamlessUK) should plan for migration to the LGCL by December 2005)</Definition>
		<SuggestedSponsor>Director of Corporate Services.</SuggestedSponsor>
	</BasicInfo>
	<Benefits>
		<Customer>New options for access to information for a wide range of customer groups.</Customer>
		<Customer>Information available outside normal contact hours or from distance in the case of non-residents.</Customer>
		<Customer>Information about services from more than one Council available at the same place</Customer>
		<Council>Because information held in common, can be used to serve a variety of channels, ensuring consistency of response</Council>
		<Council>More efficient distribution of customer access also, because on the web, it may redirect demand that would otherwise have come in over the telephone or face to face (more expensive channels)</Council>
		<Council>Options to integrate information services from multiple councils.</Council>
		<Council>Option to link to Directgov</Council>
	</Benefits>
	<OutcomeRequirements Councils="true">
		<p>This outcome covers the issues surrounding A-Z information on council websites, information sharing between councils and links to Directgov. To fulfill the requirements of the outcome councils have to make A-Z information available on their websites as well as to call handling staff, and to categorise that information according to the Local Government Category List (LGCL) or the Integrated Public Sector Vocabulary (IPSV).</p>
		<p>IPSV will replace the LGCL, the seamlessUK taxonomy and the Government Category List (GCL) for use across the public sector. From Summer 2005, the e-Government Metadata Standard (e-GMS) will recommend the IPSV as the mandatory encoding scheme for subject metadata in place of GCL.</p>
		<p>Councils who have already invested in tagging their service descriptions to LGCL (or any other list such as seamlessUK) should continue to do so, but look to migrate to IPSV by December 2006 – noting that the esd-toolkit provides a mapping from LGCL to IPSV.</p>
		<p>Councils who have not made significant strides in tagging their service descriptions should adopt IPSV.</p>
		<p>Up until December 2006, A-Z information can be based on either LGCL or IPSV, but after that, it should be based on IPSV.</p>
		<p>Guidance on the use of LGCL, IPSV and cross-references between the vocabularies is published at <a href="http://www.esd.org.uk/standards/" target="_blank">www.esd.org.uk/standards</a>.</p>
		<p>A number of other issues should be considered:</p>
		<p>The Local Directgov Project is working with the national portal for Government services Directgov (<a href="http://www.direct.gov.uk" target="_blank">www.direct.gov.uk/</a>), to establish the infrastructure by which Local Government can contribute content. At this stage, a local authority would be advised to ensure that the means by which they hold their A-Z type information is readily extractable into an XML format, although this is not mandatory at present.</p>
		<p>The Local Authority Websites (LAWS) project, in conjunction with the esd-toolkit has produced a mapping from the LGCL to the IPSV. This provides some comfort that this information can be provided over a National Infrastructure as well as in a purely Local Government domain.</p>
		<p>The A-Z list of services must be “joined-up”- meaning it should have all council services listed in one place in two-tier areas. As a minimum it should include as many of the services on the LGCL as possible, although many councils will want to include services provided by partner agencies, such as the Citizen’s Advice Bureaux, as well as relevant services provided by neighbouring councils. Most councils will want to maintain the list and keep it up to date by use of a database with a number of nominated list editors, each being responsible for a group of service entries, although other approaches are acceptable. Some content managements systems support this – although councils should be careful to ensure that use of multiple category lists is supported if this is a facility they require.</p>
		<p>Links themselves should, as a minimum, be “deep” links to pages giving detailed information on services.</p>
		<p>Once the lists have been compiled they should be displayed on the council website and as a resource to staff handling telephone or personal callers. In making the lists available, councils should consider search mechanisms and different approaches to cross-referencing and indexing of the lists to make them easy to use. </p>
		<p>In addition to the above, A -Z lists compiled by counties should include all the services provided by their districts. Approaches to syndicated content should be considered in this regard.</p>
	</OutcomeRequirements>
	<Exemptions>
		<p>A -Z lists from districts should as a minimum include all the services provided by their county, and should ideally include the services provided by all the other districts as well.</p>
	</Exemptions>
	<SupportingInformation>
		<LGSLReferences>
			<Comment>All LGSLs relating to information</Comment>
		</LGSLReferences>
		<Checklists>
			<ChecklistItem>A to Z list</ChecklistItem>
			<ChecklistItem>Available on website and to call handling staff.</ChecklistItem>
			<ChecklistItem>XML output enabled</ChecklistItem>
		</Checklists>
		<SupportingProducts>
			<Definition>
				LAWS
			</Definition>
			<Technology>C</Technology>
			<Technology>D</Technology>
			<Technology>E</Technology>
			<Technology>F</Technology>
			<Technology>G</Technology>
			<Technology>H</Technology>
			<Technology>M</Technology>
		</SupportingProducts>
	</SupportingInformation>
</PriorityOutcome>
