Changes between Version 1 and Version 2 of Ticket #204
- Timestamp:
- 12/07/09 13:10:55 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #204 – Description
v1 v2 1 == As a == 2 3 admin 4 5 == I want to == 6 7 input government data in a constrained way 8 9 == so that == 10 11 you get consistency in the db which is easily searched, discovered and automatically linked. 12 13 == implementation == 14 1 15 Form has fields suitable for government data. 2 16 (related to custom excel importer ticket) 3 17 4 Each form schemas is made available (or not) in the pylons config, along with the default schema for new packages. If there is more than just the 'basic' schema available then the 'new package' form has at the top a drop-down to select the schema with a 'switch' button. This submits the form's current data and parameter schema=xyz and the form arrives back populated with the existing options. No data should be lost switching views.18 In pylons config specify the form schema to use - whether the existing one or the government one. 5 19 6 When you edit a package it detects the schema based on the extra fields that are present. 7 8 On submission, during validation, warn if a field isn't completed (unless it's optional - agency, maintainer, maintainer_email) 20 '''On submission, during validation, warn if a field isn't completed (unless it's optional - agency, maintainer, maintainer_email)''' 9 21 10 22 === Simple fields === 11 23 12 name, title, notes, author, author_email, maintainer, maintainer_email, license (default OKFN Open::Crown Copyright), 13 co_id, precision, taxonomy url, agency 14 15 === Field data processed === 16 17 * tags - in addition to words entered here, search for known keywords in other fields: title, notes, department, agency, geographic coverage & categories. 24 * all basic ckan fields 25 * default license to OKD::Crown Copyright 26 * co_id, precision, taxonomy url, agency 18 27 19 28 === Date fields === … … 23 32 * date_released 24 33 25 * dat a_updated34 * date_updated 26 35 27 36 * temporal_coverage_from, temporal_coverage_to - two date fields combined … … 37 46 Editable combo 38 47 39 * update_frequency - selections: never mweekly, monthly, annually, discontinued48 * update_frequency - selections: never, weekly, monthly, annually, discontinued 40 49 41 50 * geographic_granularity - selections: national, regional, local authority, ward, point … … 54 63 55 64 * categories - multi values from strict selection of ONS categories. Stored as comma-separated. 65 66 === Field data processed === 67 68 * tags - in addition to words entered here, search for known keywords in other fields: title, notes, department, agency, geographic coverage & categories. 69 70 71 === Future - optional === 72 73 Each form schemas is made available (or not) in the pylons config, along with the default schema for new packages. If there is more than just the 'basic' schema available then the 'new package' form has at the top a drop-down to select the schema with a 'switch' button. This submits the form's current data and parameter schema=xyz and the form arrives back populated with the existing options. No data should be lost switching views. 74 75 When you edit a package it detects the schema based on the extra fields that are present. 76