<form id="package-edit" class="package_create_form ckan" method="post" 
  py:attrs="{'class':'has-errors'} if errors else {}"
  xmlns:i18n="http://genshi.edgewall.org/i18n"
  xmlns:py="http://genshi.edgewall.org/"
  xmlns:xi="http://www.w3.org/2001/XInclude">
 
<div class="error-explanation" py:if="error_summary">
<h2>Errors in form</h2>
<p>The form contains invalid entries:</p>
<ul>
  <li py:for="key, error in error_summary.items()">${"%s: %s" % (key, error)}</li>
</ul>
</div>
 
<fieldset>
  <legend>Basic information</legend>
  <dl>
    <dt><label class="field_req" for="title">Title *</label></dt>
    <dd><input id="title" name="title" type="text" value="${data.get('title', '')}"/></dd>
    <dd class="instructions basic">The title of the data set.</dd>
    <dd class="instructions further">The main subject of the data should be clear. For cross-government data requirements, such as spend data, specify the public body the data belongs to or its geographical coverage, in order to distinguish your data from other similar datasets in data.gov.uk. If the data relates to a period of time, include that in the name, although this would not be appropriate for data which is updated over time. It is not a description - save that for the Abstract element. Do not give a trailing full stop.</dd>
    <dd class="hints">e.g. Payments to suppliers with a value over &pound;500 from Harlow Council</dd>
    <dd class="field_error" py:if="errors.get('title', '')">${errors.get('title', '')}</dd>
 
    <dt><label class="field_req" for="name">Identifier *</label></dt>
    <dd><input id="name" maxlength="100" name="name" type="text" value="${data.get('name', '')}" /></dd>
    <dd class="instructions basic">A public unique identifier for the dataset</dd>
    <dd class="instructions further">It should be roughly readable, with dashes separating words.</dd>
    <dd class="hints">Format: Two or more lowercase alphanumeric, dash (-) or underscore (_) characters. e.g. uk-road-traffic-statistics-2008 or local-authority-spend-over-500-harlow</dd>
    <dd class="field_error" py:if="errors.get('name', '')">${errors.get('name', '')}</dd>
 
    <dt><label class="field_req" for="notes">Abstract *</label></dt>
    <dd><textarea cols="60" id="notes" name="notes" rows="15">${data.get('notes', '')}</textarea></dd>
    <dd class="instructions basic">The main description of the dataset</dd>
    <dd class="instructions further">It is often displayed with the package title. In particular, it should start with a short sentence that describes the data set succinctly, because the first few words alone may be used in some views of the data sets. Here is the place to state if there are any limitations or deficiencies to the data in order to enable users to evaluate the information; even incomplete data may be adequate for some users.</dd>
    <dd class="field_error" py:if="errors.get('notes', '')">${errors.get('notes', '')}</dd>
  </dl>
</fieldset>
 
<fieldset>
  <legend>Details</legend>
  <dl>
    <dt><label class="field_opt" for="date_released">Date released</label></dt>
    <dd><input id="date_released" name="date_released" size="40" type="text" value="${data.get('date_released', '')}" /></dd>
    <dd class="instructions basic">The date of the official release of the initial version of the dataset</dd>
    <dd class="instructions further">This is the date that the data was officially released</dd>
    <dd class="hints">DD/MM/YYYY</dd>
    <dd class="field_error" py:if="errors.get('date_released', '')">${errors.get('date_released', '')}</dd>
 
    <dt><label class="field_opt" for="date_updated">Date updated</label></dt>
    <dd><input id="date_updated" name="date_updated" size="40" type="text" value="${data.get('date_updated', '')}"/></dd>
    <dd class="instructions basic">The date of release of the most recent version of the dataset</dd>
    <dd class="instructions further">This is not necessarily the date when it was updated on data.gov.uk. As with 'Date released', this is for updates to a particular dataset, such as corrections or refinements, not for that of a new time period.</dd>
    <dd class="hints">DD/MM/YYYY</dd>
    <dd class="field_error" py:if="errors.get('date_updated', '')">${errors.get('date_updated', '')}</dd>
 
    <dt><label class="field_opt" for="date_update_future">Date to be published</label></dt>
    <dd><input id="date_update_future" name="date_update_future" size="40" type="text" value="${data.get('date_update_future', '')}"/></dd>
    <dd class="instructions basic">When the dataset will be updated in the future, if appropriate</dd>
    <dd class="hints">DD/MM/YYYY</dd>
    <dd class="field_error" py:if="errors.get('date_updated', '')">${errors.get('date_updated', '')}</dd>
 
    <dt><label class="field_opt" for="update_frequency">Update frequency</label></dt>
    <dd>
      <select class="short" id="update_frequency" name="update_frequency">
        <py:for each="freq_name, freq_desc in c.update_frequency">
          <option value="${freq_name}" py:attrs="{'selected': 'selected' if data.get('update_frequency', '') == freq_name else None}" >
            ${freq_desc}
          </option>
        </py:for>
      </select>
      <label class="inline" for="update_frequency-other">Other: 
        <input class="medium-width" id="update_frequency-other" name="update_frequency-other" type="text" value="${data.get('update_frequency-other', '')}"/>
      </label>
    </dd>
    <dd class="instructions basic">How frequently the dataset is updated with new versions</dd>
    <dd class="instructions further">For one-off data, use 'never'. For those once updated but now discontinued, use 'discontinued'.</dd>
    <dd class="field_error" py:if="errors.get('update_frequency', '')">${errors.get('update_frequency', '')}</dd>
 
    <dt><label class="field_opt" for="precision">Precision</label></dt>
    <dd><input id="precision" name="precision" size="40" type="text" value="${data.get('precision', '')}"/></dd>
    <dd class="instructions basic">Indicate the level of precision in the data, to avoid over-interpretation.</dd>
    <dd class="hints">e.g. 'per cent to two decimal places' or 'as supplied by respondents'</dd>
 
    <dt><label class="field_opt" for="url">URL</label></dt>
    <dd><input id="url" name="url" type="text" value="${data.get('url', '')}"/></dd>
    <dd class="instructions basic">The Internet link to a web page discussing the dataset.</dd>
    <dd class="hints">e.g. http://www.somedept.gov.uk/growth-figures.html</dd>
    <dd class="field_error" py:if="errors.get('url', '')">${errors.get('url', '')}</dd>
 
    <dt><label class="field_opt" for="taxonomy_url">Taxonomy URL</label></dt>
    <dd><input id="taxonomy_url" name="taxonomy_url" size="40" type="text" value="${data.get('taxonomy_url', '')}"/></dd>
    <dd class="instructions basic">An Internet link to a web page describing the taxonomies used in the dataset, if any, to ensure they understand any terms used.</dd>
    <dd class="hints">e.g. http://www.somedept.gov.uk/growth-figures-technical-details.html</dd>
    <dd class="field_error" py:if="errors.get('taxonomy_url', '')">${errors.get('taxonomy_url', '')}</dd>
  </dl>
  </fieldset>
<fieldset>
  <legend>Resources</legend>
  <table class="flexitable">
    <thead>
      <tr>
        <th class="field_req resource-url">URL*</th>
        <th class="field_opt resource-format">Format</th>
        <th class="field_opt resource-description">Description</th>
        <th class="field_opt resource-hash">Hash</th>
      </tr>
    </thead>
    <tbody>
      <py:for each="num, res in enumerate(data.get('resources', []) + [{}])">
      <tr>
        <py:for each="col in c.resource_columns">
        <td class="resource-${col}">
          <input name="resources__${num}__${col}" type="text" value="${res.get(col, '')}" class="${'medium-width' if col=='description' else 'short'}" />
        </td>
        </py:for>
        <td class="resource-id"><input name="resources__${num}__id" type="hidden" value="${res.get('id', '')}" /></td>
      </tr>
      </py:for>
    </tbody>
  </table>
  <div class="instructions basic">The files containing the data or address of the APIs for accessing it</div>
  <div class="instructions further">These can be repeated as required. For example if the data is being supplied in multiple formats, or split into different areas or time periods, each file is a different 'resource' which should be described differently. They will all appear on the dataset page on data.gov.uk together.<br/> <b>URL:</b> This is the Internet link directly to the data - by selecting this link in a web browser, the user will immediately download the full data set. Note that datasets are not hosted by data.gov.uk, but by the responsible department<br/> e.g. http://www.somedept.gov.uk/growth-figures-2009.csv<br/><b>Format:</b> This should give the file format in which the data is supplied. You may supply the data in a form not listed here, constrained by the <a href="http://data.gov.uk/blog/new-public-sector-transparency-board-and-public-data-transparency-principles" target="_blank">Public Sector Transparency Board's principles</a> that require that all data is available in an 'open and standardised format' that can be read by a machine. Data can also be released in formats that are not machine-processable (e.g. PDF) alongside this.<br/></div>
  <div class="hints">Format choices: CSV | RDF | XML | XBRL | SDMX | HTML+RDFa | Other as appropriate</div>
  <div class="field_error" py:if="errors.get('resources', '')">Package resource(s) incomplete.</div>
</fieldset>
 
<fieldset>
  <legend>More details</legend>
  <dl>
    <dt><label class="field_req" for="published_by">Published by *</label></dt>
    <dd>
      <select id="published_by" name="published_by">
        <py:for each="published_name, published_desc in c.publishers">
          <option value="${published_name}" py:attrs="{'selected': 'selected' if data.get('published_by', '') == published_name else None}" >
            ${published_desc}
          </option>
        </py:for>
      </select>
    </dd>
    <dd class="instructions basic">The organisation (usually a public body) credited with or associated with the publication of this data.</dd>
    <dd class="instructions further">Often datasets are associated with both a government department and an outside agency, in which case this field should store the department and "Published via" should store the agency. When an organisation is not listed, please request it using the form found in your data.gov.uk user page under the "Publishers" tab. An asterisk (*) denotes an pre-existing value for this field, which is allowed, but the current user's permissions would not be able to change a package\s publisher to this value.</dd>
 
    <dt><label class="field_opt" for="published_via">Published via</label></dt>
    <dd>
      <select id="published_via" name="published_via">
        <py:for each="published_name, published_desc in c.publishers">
          <option value="${published_name}" py:attrs="{'selected': 'selected' if data.get('published_via', '') == published_name else None}" >
            ${published_desc}
          </option