Guidance on selecting and entering URLs into the esd-toolkit
Guidance for web managers
OUR OBJECTIVES
To improve accessibility to public services via the Internet by bringing together Directgov and Local Authority online services into a single offering: |
For further information please contact your Local Directgov Engagement |
The Local Directgov Programme has asked every English Local Authority to provide a set of URL data to enable the Directgov website to deep-link into the Local Authority website. The data is to be collected in two phases:
- initially for a set of 65 Priority services (112 interactions) by 9th December 2005
- later for a more comprehensive set of services and interactions (to be defined) by March 17th 2006.
Three alternative methods of data collection have been specified:
i) manual entry into the esd-toolkit;
ii) data transfer by a spreadsheet/CSV or,
iii) XML format file.
When entering data manually or by data transfer please adhere to the following good practice:
When entering URLs please take into account the following good practice:
Where an external party / other authority / authority's agent provides the Local Authority Service:
- For interactions which are implemented through a link to a specialist external service (e.g. payments, or links to the planning portal):
Choose the page from which the service is accessed from the Local Authority website, rather than the external service itself (allowing the user to see the context first).
- If the service/interaction is not provided in the authority's main site, but in another under the control of the authority or its agents (e.g. housing services provided through the site of an ALMO or leisure service provided by a contractor):
It is acceptable to select a link directly into that site. (However, if you wish to ensure that the user understands the relationship between the authority and that organisation, you may wish to select the page in the authority's main site from which that third party site is accessed).
- External sites over which the authority has no influence:
It is NOT good practice to select a URL from an independent third party site over which the authority has no influence (e.g. independent bus company). (The user will be confused as to why he/she has been redirected to a "non-council" site).
- Where a service is provided by the county (when the district is entering URLs) and vice versa:
The district should leave the field blank as the county will enter the URL. URLs should not be recorded in esd-toolkit if:
- the service is provided by an LA of another tier for the same location
If the service/interaction is not represented on the authority's website:
- If the service/interaction is not provided by the Local Authority:
If the service/interaction is not represented on the authority's website (because the authority does not provide it), the field should be left blank. In this scenario the user will be sent to the page for the "Providing information" interaction for the service or (if there is no "Providing information" page) to the contacts page of the site.
URLs should not be recorded in esd-toolkit if:
- the LA does not support the service interaction
- If an LA does offer a service but it is only by telephone or face to face:
Then the URL field should be blank. In this scenario the user would be sent to the contacts page:
URLs should not be recorded in esd-toolkit if:
- the LA does not support the service interaction via the Web
NB: It is good practice for every service provided by a Local Authority to have a providing information page on their website.
- If an LA does offer a service but not all interactions are available through the web:
Then the URL field for any interaction not available on the web should be blank. In this scenario the user will be sent to the page for the "Providing information" interaction for the service or (if there is no "Providing information" page) to the contacts page of the site.
- Where URLs for service interactions are not included in an LA's BVPI157 calculations:
This should not happen - every service delivered through a Web site should be included in BVPI157 calculations.
- Where there is a different URL for audit trail than landing page
The esd-toolkit can hold more than one address for the same service/interaction/channel. The first is passed to LDG. In the rare cases where an LA wants to record one URL as a landing page and a second for audit trail, esd-toolkit will accommodate that and these addresses should be in that order.
General Guidance:
- For the "providing information" interaction:
Where there is more than one possible page, you should normally choose the first of those pages (so that the user benefits from the whole set of information about the service).
- For interactions which have an e-form on the site (e.g. an application form):
Choose the page from which the e-form is accessed, rather than the e-form itself. (Many e-forms are introduced with some basic context or instructions before the form itself is accessed. This allows the user to see these details first). It is not good practice to enter a URL that links straight through to a document such as a PDF.
- Selecting the same page for more that one interaction:
It IS acceptable for the same page to be selected for more than one interaction within the same service, or more than one service, if that is the best page for each of the required combinations.
- The citizen should be routed to the best available page for the service / interaction.
For further information please contact your Local Directgov Engagement |